Вы находитесь на странице: 1из 196

Nokia Siemens Networks DX MSC / MSS / DX HLR, Rel. M14.3, Product Documentation, v.

DX MSC/SSP/IP - SCP Interface Specification

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

1 (196)

DX MSC/SSP/IP - SCP Interface Specification

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2009. All rights reserved.

2 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Contents

Contents
Contents 3 List of tables 5 List of figures 8 1 2 3 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5 4.4 5 5.1 5.1.1 5.1.2 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3 5.3.1 5.3.2 5.3.3 5.4 5.4.1 5.4.2 5.4.3 6 6.1 6.2 Changes in the document 9 Introduction 11 Changes in the DX MSC/SSP/IP - SCP Interface 13 Interface description: Call-related IN functions 15 Related specifications 15 Originating and terminating call models 15 Support of Core INAP 22 Support of the application context 22 Core INAP operations between SCF - SSF 22 Operations between SCF - SRF 23 Valid state transitions for the SSF FSM 24 Support of Core INAP parameters 26 MSC/SSP Core INAP configuration data 105 Interface description: Call-unrelated IN functions 115 Specifications and terminology 115 Related specifications 115 Terminology 115 IN mobility management 116 IN mobility management procedures 116 Mobility management state model in the VLR 117 Mobility management state model in the HLR 120 SCP load control 121 Support of Core INAP operations in IN mobility management 121 Support of Core INAP parameters in IN mobility management 122 IN supplementary service management 132 IN supplementary service management procedures 132 Support of Core INAP operations in IN supplementary service management 132 Support of Core INAP parameters in IN supplementary service management 133 IN Short Message Service 137 IN Short Message Service procedures 137 Support of Core INAP operations in IN Short Message Service 139 Support of Core INAP parameters in IN Short Message Service 140 Interface description: ASN definitions 153 ASN.1 definitions for extensions 153 ASN.1 definitions for operation data types 172

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

3 (196)

DX MSC/SSP/IP - SCP Interface Specification

Support protocol description 195

4 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

List of tables

List of tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Support for SSF - SCF Core INAP operations Support of SRF - SCF Core INAP operations Valid state transitions for the SSF FSM Valid state transitions SSF FSM 26 28 28 25 22 24

SSP support for ActivityTest operation in Detection Points

SSP support for ApplyCharging operation in Detection Points Support for ApplyCharging operation parameters 30

Support for ApplyChargingReport operation in Detection Points Support for ApplyChargingReport operation parameter 36 38 34

32

Table 10. Support for CallGap operation parameters

Table 11. SSP support for Cancel operation in Detection Points Table 12. Support for Cancel operation parameters 39

Table 13. SSP support for CollectInformation operation in Detection Points Table 14. Support for CollectInformation parameters 41 42

40

Table 15. SSP support for Connect operation in Detection Points Table 16. Support for Connect operation parameters 43

Table 17. SSP support for ConnectToResource operation in Detection Points Table 18. User interaction possibility for call parties in Detection Points Table 19. Support for ConnectToResource operation parameters Table 20. SSP support for Continue operation in Detection Points 52 56 51

50

Table 21. SSP support for EstablishTemporaryConnection operation in Detection Points 57 Table 22. Support for EstablishTemporaryConnection operation parameters Table 23. SSP support for EventNotificationCharging operation in Detection Points 64 Table 24. Support for EventNotificationCharging operation parameters 65 67 59

Table 25. SSP support for EventReportBCSM operation in Detection Points Table 26. Support for EventReportBCSM operation parameters 68

Table 27. SSP support for FurnishChargingInformation operation in Detection

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

5 (196)

DX MSC/SSP/IP - SCP Interface Specification

Points 71 Table 28. Support for FurnishChargingInformation operation parameter Table 29. SSP support for IntialDP operation in Detection Points Table 30. Support for InitialDP operation parameters 76 88 91 74 72

Table 31. Support for PlayAnnouncement operation parameter

Table 32. Support for PromptAndCollectUserInformation operation parameters Table 33. Digits, sent to the SCF, indicating what the subscriber has called Table 34. SSP support for the ReleaseCall operation in Detection Points Table 35. Support for the ReleaseCall operation parameter 95 93

94

Table 36. SSP support for the RequestNotificationChargingEvent operation in Detection Points 96 Table 37. Support for the RequestNotificationChargingEvent operation parameters 96 Table 38. SSP support for the RequestReportBCSMEvent operation in Detection Points 97 Table 39. Support for the RequestReportBCSMEvent operation parameters Table 40. SSP support for the ResetTimer operation in Detection Points Table 41. Support for the ResetTimer operation parameters 100 98

100

Table 42. SSP support for the SendChargingInformation operation in Detection Points 101 Table 43. Support for the SendChargingInformation operation parameters Table 44. The possible uses of the Trigger Criteria 111 103

Table 45. The states of the VLR functionality in Mobility Management State Models 117 Table 46. Support for SSF - SCF Core INAP operations in IN Mobility Management 122 Table 47. Support for the CallGap operation parameters 123 124

Table 48. SSP support for the Continue operation in the Detection Points

Table 49. SSP support for FurnishChargingInformation operation in the Detection Points 125 Table 50. Support for the FurnishChargingInformation operation parameter Table 51. SSP support for the InitialDP operation in the Detection Points Table 52. Support for the InitialDP operation parameters 128 126 127

6 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

List of tables

Table 53. SSP support for the ReleaseCall operation in the Detection Points Table 54. Support for the ReleaseCall operation parameter Table 55. Additional IN Mobility Management cause values 131 131

131

Table 56. Support for SSF - SCF Core INAP operations in the Supplementary Service State Model 133 Table 57. Support for the Connect operation parameter Table 58. Support for InitialDP operation parameters 134

135 137

Table 59. Support for the ReleaseCall operation parameter

Table 60. Support for SSF - SCF Core INAP operations in the Short Message Service State Models 139 Table 61. Support for the CallGap operation parameters 140 142

Table 62. SSF support for the Connect Operation in Detection Points Table 63. Support for the Connect operation parameters 142

Table 64. SSF support for the Continue operation in Detection Points

143

Table 65. SSF support for the FurnishChargingInformation operation in Detection Points 144 Table 66. Support for the FurnishChargingInformation operation parameter Table 67. SSF support for the InitialDP operation in Detection Points Table 68. Support for the InitialDP operation parameters 146 148 145 144

Table 69. SSF support for the ReleaseCall operation in Detection Points Table 70. Support for the ReleaseCall operation parameter 149

Table 71. SSF support for the RequestReportBCSMEvent operation in Detection Points 150 Table 72. Support for the RequestReportBCSMEvent operation parameters 150

Table 73. SSF support for the EventReportBCSM operation in Detection Points 151 Table 74. Support for the C (ERB) operation parameters 152

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

7 (196)

DX MSC/SSP/IP - SCP Interface Specification

List of figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Originating Basic Call State Model for PBX/trunk-originating calls Originating Basic Call State Model for mobile-originating calls Terminating Basic Call State Model for PBX-terminating calls Terminating Basic Call State Model in the VMSC Gateway Basic Call State Model in the GMSC 20 18 19 17

21

Mobility Management State Model in the VLR for inter-VLR location registration 118 Mobility Management State Model in the VLR for intra-VLR location registration 119 Mobility Management state model in the HLR SS-DP1: SS management 132 138 138 120

Figure 10. Mobile-Originating Short Message Service State Model Figure 11. Mobile-Terminating Short Message Service State Model

8 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Changes in the document

Changes in the document


Changes made between issues 6-0 and 50 The company and product names have been changed according to the official Nokia Siemens Networks portfolio naming. Changes made between issues 5-0 and 41 Section MSC software release information to SCP and usage description in Section Support of Core INAP parameters have been updated. Description has been added to Section MSC/SSP Core INAP configuration data. Table content has been updated in Section Support of Core INAP parameters in IN Short Message Service Addition information has been added to Section Support protocol description. Changes made between issues 41 and 40 Sections Operation: Continue (CUE) and Operation: Connect (CON) in Chapter Interface description: Call-related IN functions have been supplemented with gsmSSF preconditions. Changes made between issues 40 and 34

InitialDP and Connect operations


Call Deflection has been added to the GsmSupplementaryServiceList extension.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

9 (196)

DX MSC/SSP/IP - SCP Interface Specification

10 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Introduction

Introduction
This document specifies the Intelligent Network Application Protocol (INAP) for Capability Set 1 (CS1). The protocol provides the interface between the DX MSC/MSS/SSP/IP and the SCP. The protocol is Core INAP, as defined by the European Telecommunications Standards Institute (ETSI), applicable to the interfaces between the following functional entities:
.

Service Switching Function and Service Control Function (SSF SCF) Specialised Resource Function and Service Control Function (SRF SCF) concerning the internal SRF embedded in the MSC/MSS/SSP The interface between the SCF and the SRF located in an external IP does not belong to the scope of this document.

The protocol is also used in the call-unrelated functions between the SCF and the SSF located in the MSC/MSS/VLR and the HLR. Those interfaces are used for the call-unrelated IN functions.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

11 (196)

DX MSC/SSP/IP - SCP Interface Specification

12 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Changes in the DX MSC/SSP/IP - SCP Interface

Changes in the DX MSC/SSP/IP - SCP Interface


Call-related Continue (CUE) and Connect (CON) operations have been supplemented with gsmSSF preconditions on control relationship, basic call processing, and states of gsmSSF.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

13 (196)

DX MSC/SSP/IP - SCP Interface Specification

14 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

4
4.1

Interface description: Call-related IN functions


Related specifications
The described SSF-SCF and SRF-SCF interfaces are based on ETS 300 374-1: Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: Protocol specification, September 1994. All the restrictions and inconsistencies presented in this document, if not stated otherwise, refer to that specification. The CS-1 concept in the Basic Call State Models is based on ITU-T Q.1214 Intelligent Network; Distributed Functional Plane For Intelligent Network CS-1, October 1995.

4.2

Originating and terminating call models


The following figures present the implementation of the Originating Basic Call State Model (OBCSM) and the Terminating Basic Call State Model (TBCSM) in the DX 200 MSC/MSS/SSP exchange. The notes listed below for the Basic Call State Models are presented in the BCSM figures.

Note

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

15 (196)

DX MSC/SSP/IP - SCP Interface Specification

1)

2) 3)

Whether DP2 is mapped from DP2a or from DP2b, depends on the SSF_DP_I_PREANALYZED (002:0419) PRFILE parameter (see the MSC/SSP Core INAP configuration data). If DP2 is mapped from DP2a, the actions in PIC 2 after DP2a are performed in the beginning of PIC 3. The CLIR handling is done between DP2a and DP2b.

16 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

PIC 1 O_Null

Setup reception, creation of the BCSM

Get incoming circuit group data, Save TgKey received from circuit group (Trunk calls) Get PBX data, save TgKey received from PBX data (PBX calls) CLI screening Connect DP1 PIC 2 Collect_info, see Note 1 Collection of additional digits DP2a see Note 2 Collect info Short Number Analysis Pre-analysis (for dialled digits) DP2b DP2 Pre-analysis (for SCP given numbers) Priority analysis Short Number Analysis (PBX calls) Central Memory analysis to the B-number Save the TgKey received from the Central Memory DP3 Seizure of the outgoing circuit from RMA Start Outgoing CC, Reception of the ACM Reception of the Answer DP7 Start Charging Speech state A or B clears the call, stop the charging A/B clears the call in the speech state DP10 Clearing actions: function analysis charging information to the SCP Clearing actions: stop the charging EOS-analysis charging information to the SCP PIC 6 O_Exception DP9 Internal Actions PIC 5 O_Active Only charging limit warning DP8 PIC 4 Routing&Alerting Connect DP received from the EOS: DP4 RouteSelectFailure DP5 Busy DP6 NoAnswer PIC 3 Analyse_info Collect info Connect Collect info

CHA attribute analysis, ROU attribute analysis (save possible trigger)

Figure 1.

Originating Basic Call State Model for PBX/trunk-originating calls

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

17 (196)

DX MSC/SSP/IP - SCP Interface Specification

PIC 1 O_Null Setup reception, creation of the BCSM Save the TgKey received from VLR Connect DP1 PIC 2 Collect_info, see Note 1 Collection of additional digits DP2a see Note 2

Short Number Analysis Pre-analysis (for dialled digits) DP2b DP2 Pre-analysis (for SCP given numbers) Priority analysis, reservation of speech channel MOC attribute analysis, Origin analysis Central Memory analysis to the B-number Save the TgKey received from the Central Memory DP3 Barring analysis Start Outgoing CC, Reception of the ACM Reception of the Answer DP7 Start Charging Speech state A or B clears the call, stop the charging A/B clears the call in the speech state DP10 Clearing actions: function analysis charging information to the SCP Clearing actions: stop the charging EOS-analysis charging information to the SCP PIC 6 O_Exception DP9 Internal Actions PIC 5 O_Active USSD or charging limit warning DP8 PIC 4 Routing&Alerting Connect DP received from the EOS: DP4 RouteSelectFailure DP5 Busy DP6 NoAnswer PIC 3 Analyse_info Connect Collect info

CHA attribute analysis, ROU attribute analysis (save possible trigger)

Figure 2.

Originating Basic Call State Model for mobile-originating calls

18 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Setup reception, creation of the BCSM Get PBX data Save the TgKey received from PBX data Possible CLI enquiry DP12 Start PBX signalling or... ...create new leg if "Connect" from SCP Reception of ACM

PIC 7 T_Null

PIC 8 Select_Facility & Present Call Connect

Reception of the answer

PIC 9 T_Alerting

DP depends on the cause: DP13 Busy DP14 NoAnswer

DP15 PIC 10 Speech state A or B clears the call A or B clears the call in the speech state DP18 Clearing actions: function analysis Reports to SCP DP17 Internal Actions T_Active

Only charging limit warning DP16

Clearing actions: Stop charging of the released party

PIC 11 T_Exception

Figure 3.

Terminating Basic Call State Model for PBX-terminating calls

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

19 (196)

DX MSC/SSP/IP - SCP Interface Specification

Setup reception, creation of the BCSM VLR Enquiry Save the TgKey received from the VLR Possible CLI enquiry DP12 Paging DP12

PIC 7 T_Null

Error condition (not the clearing indicated by A)

DP12 Start outgoing signalling, if B free or.. ..create new leg if "Connect" from SCP Reception of ACM PIC 8 Select_Facility & Present Call Connect

A clears, stop the charging

Reception of the Answer

PIC 9 T_Alerting

DP depends on the cause: DP13 Busy DP14 NoAnswer

DP15 Speech state A or B clears the call Start the charging A/B clears the call in the speech state PIC 10 T_Active

USSD or charging limit warning DP16

DP18 Clearing actions: function analysis Reports to SCP

DP17 Internal Actions

Clearing actions: Stop charging of the released party

PIC 11 T_Exception

Figure 4.

Terminating Basic Call State Model in the VMSC

20 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Setup reception, creation of the BCSM Error condition (not the clearing indicated by A) Save the TgKey received from the HLR Enquiry Possible CLI enquiry

PIC 7 T_Null

DP12 Make the second HLR Enquiry if required DP12 Create new leg if "Connect" from SCP Reception of ACM PIC 8 Select_Facility & Present Call

A clears, stop the charging Reception of the Answer PIC 9 T_Alerting

Connect

DP depends on the cause: DP13 Busy DP14 NoAnswer

DP15 Speech state A or B clears the call Start the charging A/B clears the call in the speech state PIC 10 T_Active

Only charging l imit warning DP16

DP18 Clearing actions: Reports to SCP

DP17 Internal Actions

Clearing actions: Stop charging

PIC 11 T_Exception

Figure 5.

Gateway Basic Call State Model in the GMSC

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

21 (196)

DX MSC/SSP/IP - SCP Interface Specification

4.3
4.3.1

Support of Core INAP


Support of the application context
The following application contexts of the ETSI CS-1 Core INAP are supported:
.

Core-INAP-CS1-SSP-to-SCP-AC; the dialogue initiated by the SSP with InitialDP. Core-INAP-CS1-SCP-to-SSP-traffic-management-AC; the dialogue initiated by the SCP with CallGap.

4.3.2

Core INAP operations between SCF - SSF


The SCF-SSF operations, defined by the Core INAP specification ETS 300 374-1, are presented in Table Support of SSF - SCF Core INAP operations. The indication whether the implementation of the DX 200 MSC/MSS/SSP supports the operation in the OBCSM or in the TBCSM is marked with: S NS supported not supported

The SSF cannot send not supported operations to the SCF. If a not supported operation is received from the SCF, the SSF rejects the operation.

Table 1. Core INAP operation

Support for SSF - SCF Core INAP operations Nokia Siemens Networks' support in OBCSM
NS S S S NS S NS

Nokia Siemens Networks' support in TBCSM


NS S S S NS S NS

Note

ActivateServiceFiltering ActivityTest ApplyCharging ApplyChargingReport AssistRequestInstructions CallGap CallInformationReport

1) 1)

22 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 1. Core INAP operation

Support for SSF - SCF Core INAP operations (cont.) Nokia Siemens Networks' support in OBCSM
NS S S S S S S S S S S S NS S S S S S NS

Nokia Siemens Networks' support in TBCSM


NS S NS S S S S S S S S S NS S S S S S NS

Note

CallInformationRequest Cancel CollectInformation Connect ConnectToResource Continue DisconnectForwardConnection EstablishTemporaryConnection EventNotificationCharging EventReportBCSM FurnishChargingInformation InitialDP InitiateCallAttempt ReleaseCall RequestNotificationChargingEvent RequestReportBCSMEvent ResetTimer SendChargingInformation ServiceFilteringResponse

2) 2)

2)

2) 1) 2)

1)

1) 2)

The operation is specified more precisely than in the standard. Extensions have been specified for the operation.

4.3.3

Operations between SCF - SRF


The SCF-SRF operations defined by the Core INAP specification ETS 300 374-1 are presented in Table Support of SRF - SCF Core INAP operations. The indication whether the implementation of the DX 200 MSC/MSS/SSP with the internal IP supports the operation in the OBCSM or in the TBCSM is marked with:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

23 (196)

DX MSC/SSP/IP - SCP Interface Specification

S NS

supported not supported

Note that the table does not contain the interface between the SCP and the external assisting IP. The SRF cannot send the supported operations to the SCF. If a not supported operation is received from the SCF, the SSF/SRF rejects the operation.

Table 2. Core INAP operation

Support of SRF - SCF Core INAP operations Nokia Siemens Networks' support in OBCSM
NS S S S S

Nokia Siemens Networks' support in TBCSM


NS S S S S

Note

AssistRequestInstructions Cancel PlayAnnouncement PromptAndCollectUserInformation SpecializedResourceReport

1) 1)

1)

Extensions have been specified for the operation.

4.3.4

Valid state transitions for the SSF FSM


The valid state transitions for the SSF FSM are shown in Table Valid state transitions for the SSF FSM. The columns present the current state in which the operation or event occurs. The existence of an entry indicates that in the current state the operation/event is valid. The text of the entry indicates the transition to the state after processing the operation/event.

24 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 3. Operation
ActivityTest ApplyCharging Cancel(allRequests) CollectInformation Connect ConnectToResource Continue DisconnectForwardConnection EstablishTemporaryConnection FurnishChargingInformation ReleaseCall RequestNotificationChargingEvent RequestReportBCSMEvent ResetTimer SendChargingInformation

Valid state transitions for the SSF FSM State a Idle State c WfI
same same WfI Mon idle 1), Mon 2) WfEoUI idle 1), Mon 2) WfI WfEoTC same idle same same same same same same 4) same same 4) same 4) same 4) same 4) same 4) same idle same idle 1), same 2) WfI

State d WfEoU
same same 4)

State e WfEoTC
same same 4)

State f Mon
same same idle

Events
TDP-R (InitialDP) Tssf event - EDP-R event - EDP-N event - intermediate charging event event - charging report at end of call event - credit limit reached event - release call resources same 5) same 5) same 5) WfI idle WfI idle 1), Mon 2) same idle WfI idle 1), Mon 2) same idle WfI idle 1), Mon 2) same WfI idle 1), same 2) same idle 1), same 2) same idle

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

25 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 4. Operation for relaying to SRF


Cancel(invokeID) PlayAnnouncement PromptAndCollectUserInformation Events for relaying from SRF event - disconnect from SRF event SpecializedResourceReport ReturnResult from PaCUI

Valid state transitions SSF FSM State a Idle State c WfI State d WfEoU
same 3) same 3) same 3)

State e WfEoTC

State f Mon

WfI same 3) same 3)

WfI

1) 2) 3) 4) 5) Legend: State State State State State a: c: d: e: f:

There are no armed EDPs and no pending requests. There are armed EDPs or pending requests. Operation events for relaying to/from the SRF. The operation is saved and handled in the WfI state. The operation is saved and handled in the Mon state.

Idle Waiting For Instructions Waiting For End Of User Interaction Waiting For End Of Temporary Connection Monitoring

4.3.5

Support of Core INAP parameters


This information describes the support for the parameters of Core INAP operations, including the restrictions and inconsistencies in the ETS 300 374-1. The remark for an operation contains the following terms:

26 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Intermediate response: After receiving an InitialDP or EventReportBCSM operation, the SCF sends back one or more operations to the SSF/SRF. All but the last operation are intermediate responses that do not allow the CCF to proceed with the call handling. Final response: The last response operation from the SCF to the SSF is the final response, which allows the CCF to proceed with the call. After the final response, the SSF does not accept any further intermediate responses in that Detection Point (DP). Spontaneous operation: The SCF can send a spontaneous operation at any time during a dialogue with the SSF. In this case, the CCF is not necessarily stopped in any DP.

The parameter table contains the indication of support for the parameters, and possibly a reference to an explaining note. The SSF/SRF cannot send a not supported parameter to the SCF. If a not supported optional parameter is received from the SCF, it is neglected, and no error component is returned to the SCF. The supported extensions are also presented in the parameter table. If a not supported extension is received from the SCF with the criticality value 'IGNORE', it is neglected. The whole dialogue is aborted when the criticality value is 'ABORT'. Operation: ActivityTest (AT) Direction: Usage: SCF -> SSF The SCF checks the existence of a relationship between the SCF and the SSF. If the relationship still exists, the SSF will respond (with the ActivityTest operation RESULT). If no reply is received, the SCF assumes that the SSF has failed and takes the appropriate action. Associated operations: None. Comments: The SCF sends this operation as an intermediate response or a spontaneous operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

27 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 5. DP1
yes

SSP support for ActivityTest operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
yes

Parameters: Response:

None. The RESULT component is returned to the SCF immediately.

Operation: ApplyCharging (AC) Direction: Usage: SCF -> SSF 1. The SCF requests the SSF to return the charging-related information at the end of the call. 2. The SCF gives a time/pulse limit for the call, possibly with a request to give a warning before the limit is reached. Associated operations: ApplyChargingReport, RequestReportBCSM Comments: The SCF sends this operation as an intermediate response operation or as a final response to ApplyChargingReport to set a new limit. The use of this operation does not make the relationship between the SSF and the SCF a controlling relationship. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 6. DP1
yes

SSP support for ApplyCharging operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
no

DP9
no

28 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

DP10
no

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
no

DP17
no

DP18
no

spont
no

About the use of this operation:


For the coding of network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions. Setting a call limit with the operation is not permitted once charging has been started. In that case the 'Task Refused' error component is returned. Exception: The new limit from the SCF is accepted as a response to ApplyChargingReport even though charging has been started. Requesting for the hot billing record of the operation is not allowed once charging has been started. If the SCF requests the warning by sending the warningTime parameter, the MidCall DP must be armed before sending the related ApplyCharging to the SSF. This is because the warning report is the ERB operation from the MidCall DP. The SCF can request the hot billing record and give a limit by sending two separate ApplyCharging operations. The SSF then sends a separate ApplyChargingReport operation for the limit and for the hot billing record. The hot billing record request is accepted from a second SSF-SCF relationship even though the first SSF-SCF relationship has already requested a hot billing record. In that case the report is sent to both of the SSF-SCF relationships. The limit is not accepted from the second SSF-SCF relationship if the limit has already been set in the first SSF-SCF relationship, but the SSF returns the 'Unexpected Component Sequence' error message.

Parameters:
S NS supported not supported

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

29 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 7. Parameter

Support for ApplyCharging operation parameters Nokia Siemens Networks' support


S S NS NS 2 1

Note number

aChBillingChargingCharacteristics sendCalculationToSCFIndication partyToCharge extensions

The DX 200 MSC/SSP also allows the value FALSE. The SCF uses it when it gives a limit for the call, but has no further interest in it. The SSF releases the call without an ApplyChargingReport if the limit is reached. No extensions have been defined for this operation.

About the use of the parameters:


.

aChBillingChargingCharacteristics: The coding is network-specific. The DX 200 MSC/SSP supports the following data: . callTreatment: This parameter specifies which type of ApplyChargingReport it is requesting: The value 2 'currencyThresholdValue' is not in use. . hotBillingRecord . pulseThresholdValue . currencyThresholdValue is not supported. . timeThresholdValue When the pulse or time limit is reached and the SCF gives a new limit for the same call, the call treatment must be the same as in the original ApplyCharging operation.

30 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Threshold: The SCF can give the limit value. This parameter is not used in the hot billing record request. . pulseLimit: The SCF gives the limit value in terms of the number of charging units (Pulses) and tariffType. The tariffType should be zero. . chargeMessage: defined in ASN.1 definitions, but not used . time: The SCF gives the limit value in terms of the maximum duration of the call in seconds (Time). If the value 'callTreatment' is the limit for the call, the threshold value is reduced, although the call is free of charge. The limit for the call threshold value is reduced, although the call is free of charge. Note that if the SCF for some reason does not recognise the emergency call, and sets the threshold in the normal way, it does not receive the ACR from the SSF at all. Also, the threshold value 0 is not accepted by the SSF. In that case, the INAP error 'parameter out of range' is returned to the SCP. warningTime: With the warningTime, the SCF requests a warning in advance before the limit (Time/Pulse) runs out. The value is 0...255, indicating the time in seconds. Note that the warning is reported only in case the O_Mid_Call_DP in the OBCSM or the T_Mid_Call_DP in the TBCSM has been armed as an EDP-R, where the SCF can give the tone/announcement by using the ConnectToResource and PlayAnnouncement operations. The SCF can give the warning time only together with a call limit. If the warning time is greater than the call limit, the warning is reported immediately after the charging has been started.

sendCalculationToSCFIndication: If the SCF does not include this parameter with the value TRUE in the ApplyCharging operation, it does not receive any ApplyChargingReport back from the SSF. The default value is FALSE. partyToCharge: The parameter is not supported, the operation always concerns the calling/forwarding party in the OBCSM and the called party in the TBCSM.

Operation: ApplyChargingReport (ACR) Direction: Usage: SSF -> SCF

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

31 (196)

DX MSC/SSP/IP - SCP Interface Specification

1.

2.

The SSF sends the hot billing record to the SCF as a result of ApplyCharging at the end of the call or as an intermediate charging report. The SSF returns the remaining pulses/time at the end of the call if the given limit was not reached, or in case of an 'empty threshold' if the limit was reached before the end of the call.

Associated operations: ApplyCharging, Cancel Comments: The SSF sends this operation outside a DP during the call. At the end of the call, in the Disconnect DP (DP9/17), the SSF can be configured, so that the ACR is sent before the EDP-R or after the EDP-R. In case of an EDP-N, the ACR is always sent after the ERB. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 8. DP1
no

Support for ApplyChargingReport operation in Detection Points DP4


no

DP2
no

DP3
no

DP5
no

DP6
no

DP7
no

DP8
no

DP9
yes 2)

DP10
no

DP12
no

DP13
no

DP14
no

DP15
no

DP16
no

DP17
yes 2)

DP18
no

spont
yes 1)

1) 2)

The SSF sends the ACR outside the DP when the limit is reached or the call is released. As an option, the SSF can send the ACR in the Disconnect DP if it is armed as an EDP-R.

About the use of this operation:


For the coding of the network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions.

32 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

If an intermediate CDR is generated in the MSC, and a hot billing record is requested, the SSF sends an intermediate ApplyChargingReport to the SCF. It is up to the SCF to collect those reports, and possibly to combine them if needed. The last report can be noticed by the 'endOfCallIndicator' parameter. The intermediate CDR is generated in the following cases:
.

if the MS returns into radio coverage at the end of an IN announcement if the intermediate charging timer expires if the amount of charging pulses received from the network exceeds the defined limit if the number of channels in use or the coding method changes during the handover

The generation of the intermediate CDR is controlled by the INTERMEDIATE_CHARGING (001:0075) PRFILE parameter. An ApplyChargingReport cannot be sent during an announcement. The announcement is played, and after that the ACR is sent if, for example, the pulse limit reaches zero during a chargeable announcement. If a new limit is given, the spent pulses are reduced from the new limit. However, if the SCF does not give a new limit, it does not get information about the pulses that were spent after the limit was reached. If the last ApplyChargingReport is sent at the end of a call, that is, before entering the idle state of the BCSM, the Disconnect and Abandon DPs are reported first, if armed and met. After they are passed and served, the ApplyChargingReport is sent either in the TC-END, if the CS1_LAST_OP_IN_TC_END (002:0599) PRFILE parameter value is TRUE (default), or in the TC-CONTINUE, if the parameter value is FALSE.

Parameters:
S NS supported not supported

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

33 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 9. Parameter

Support for ApplyChargingReport operation parameter Nokia Siemens Networks' support


S

Note number

callResult

About the use of the parameters:


.

callResult
The coding is network-specific. The DX 200 MSC/SSP supports the following data: . callTreatment . With the 'callTreatment' the SSF tells which type of ApplyChargingReport is concerned: a hot billing record or a limit for the call. . The value 2 'currencyThresholdValue' is not in use. . reportInfo This parameter contains either the hotBillingRecord or the Threshold: . hotBillingRecord The hotBillingRecord is of a fixed length. The subparameters have no tags, but the SCF can separate them, since it knows the length of each subparameter. The SSF always includes all the tags in the parameter. In the number fields, 'F' is the filler for the unused digits at the end of the digit string. The time fields contain all zeros if the time stamp is not included. . callingPartyNumber The callingPartyNumber contains the number of the calling party known by the CCF when the report is generated. . calledPartyNumber The calledPartyNumber contains the number of the called party known by the CCF when the report is generated. . startTimeOfCall The time stamp when the subscriber charging was started, or the previous intermediate charging took place. . endTimeOfCall

34 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

The time stamp when subscriber charging was stopped, or the intermediate charging that concerns the report took place. . chargingPulses Collected charging units after the previous ACR with the hot billing record were sent, that is, it does not contain the cumulative sum of the pulses but the pulses from the previous intermediate charging. . redirectingPartyID The redirectingPartyID contains the number of the last redirecting party known by the CCF when the report is generated. . redirectionInformation The redirectionInformation is the data related to the last redirection. . callTime The duration of the call measured in a unit of 1/10 seconds. It indicates the duration calculated by the time charging process, not necessarily the same as (endTime) - (startTime). If an intermediate hot billing report is sent, the duration is calculated separately for each part. . chargingZone The value is 'used charging zone' or 'unused charging zone'. . Threshold A parameter which contains the remaining value of the time/pulse. A threshold value of zero indicates that the limit has been reached. . pulses: The tariffType parameter is always zero. . time: The unit is in seconds. endOfCallIndicator It indicates whether the report is the last ACR in the call. . The value FALSE indicates that an intermediate report is concerned, and the SCF waits for further ApplyChargingReports with the Hot Billing information. An intermediate report is generated when the intermediate charging is made in the MSC/SSP. . The value TRUE means the end of the call.

Operation: CallGap (CG)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

35 (196)

DX MSC/SSP/IP - SCP Interface Specification

Direction: Usage:

SCF -> SSF The SCF requests the SSF to reduce the rate at which specific service requests are sent to the SCF. Associated operations: None. Comments: The SCF sends this operation as a spontaneous operation. Support in DPs: The operation is not call-related, and the acceptance of it does not depend on any BCSM DP.

About the use of this operation:


With this operation, the SSF uses the pre-arranged end method. No response is sent to the SCF, and the SSF-SCF relationship is locally ended.

Parameters:
S NS supported not supported

Table 10. Parameter

Support for CallGap operation parameters Nokia Siemens Networks' support


S S S S NS 3 4

Note number

gapCriteria gapIndicators controlType gapTreatment extensions

1 2

1 2

The locationNumber is not supported. Duration is indicated in seconds. Values -1 (=infinite duration) and -2 (=network-specific duration) are not supported. The gapInterval is indicated in milliseconds. The resolution is 10 ms. informationToSend.inbandInfo.messageID.text and informationToSend.displayInformation are not supported. No extensions have been defined for this operation.

36 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

About the use of the parameters:


.

gapCriteria . calledAddressValue: It is received from the SCF, and it is compared to the called party address of the call. If the SCF gives the number, for example, in a national type, and it is an international number in the call, the gapping is not active. To cover the various possibilities, the SCF should set the gapping of various forms of the same called party number. . gapOnService: It compares the ServiceKey defined in the trigger data and the ServiceKey given by the SCF in the CallGap operation. . calledAddressAndService: The calledAddress received from the SCF is compared to the called party address of the call. The ServiceKey defined in the trigger data and the ServiceKey given by the SCF in the CallGap operation are compared. . callingAddressAndService: The callingAddress received from the SCF is compared to the calling party address of the call. The ServiceKey defined in the trigger data and the ServiceKey given by the SCF in the CallGap operation are compared. gapIndicators . Duration If the SCF sends the value -1 or -2, the operation is discarded. Yet, as the operation contains no result and no response operation exists, the SSF cannot indicate the case to the SCF. The SCF can check the existence of the call gapping by reading the cGEncountered parameter in the InitialDP operation. . gapInterval Resolution 10 ms means that the value received from the SCF in milliseconds is divided by ten to form the interval. The SCF must specify a value greater than 9, because values 0-9 give interval=0, and the gapping is not activated. controlType: ManuallyInitiated has a higher priority, so it replaces the previous gapping with the same criteria. A CallGap with sCPOverload is discarded if there is an active gapping with the same criteria and with controlType=manuallyInitiated. . sCPOverload . manuallyInitiated gapTreatment

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

37 (196)

DX MSC/SSP/IP - SCP Interface Specification

informationToSend: It contains the possible announcement or tone to be played to the calling party. If the call is gapped, a gap announcement or a tone is played. If the Failure Operation (FOP) parameter value is to release the call, the possible further terminating announcements, which would be played according to the end of selection analysis of the releaseCause, are suppressed in the MSC/SSP. releaseCause The cause code provided by the SCF is used in the release phase of the call in the MSC/SSP, if the call is gapped and the FOP parameter value requests to release the call. If the SCF does not provide the cause code, the MSC/SSP uses the cause value 'normal unspecified'. The gap announcement is played to the calling party both in the OBCSM and the TBCSM. The gap announcement is not supported in the answer and in the Disconnect DPs.

Operation: Cancel (CAN) Direction: Usage: SCF -> SRF/SSF The SCF requests the SRF to cancel the previous PlayAnnouncement or the PromptAndCollectUserInformation operation. The SCF requests the SSF to cancel all outstanding requests concerning EventReportBCSM, ApplyChargingReport, and EventNotificationCharging.

Associated operations: As stated above. Comments: The SCF sends this operation as an intermediate response to the SRF, or a spontaneous operation or a final response to the SSF. Support in DPs: The SSP supports the operation in DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 11. DP1


yes

SSP support for Cancel operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

38 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
yes

About the use of this operation:


In an error situation the SRF returns to the SCF error codes as follows: CancelFailed (operationNotCancellable)

Parameters:
S NS supported not supported

Table 12. Parameter

Support for Cancel operation parameters Nokia Siemens Networks' support


S S

Note number

invokeID allRequests

About the use of the parameters:


.

invokeID
This is possible only in the SCF-SRF relationship. The cancel operation has no extra priority in the message queue. If several successive user interaction operations are sent to the SRF, and one in the middle is cancelled, the cancel operation is still in the queue when the operation is executed.

allRequests
The use of this parameter disarms all pending requests.

Operation: CollectInformation (CI) Direction: Usage: SCF -> SSF The SCF requests the SSF to provide more digits for the destination address. Associated operations: RequestReportBCSMEvent

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

39 (196)

DX MSC/SSP/IP - SCP Interface Specification

The SCF arms EDP 2 as Request type and defines the amount of digits to be collected before reporting. Comments: Support in DPs: The SCF sends this operation as a final response operation. The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 13. DP1


yes

SSP support for CollectInformation operation in Detection Points DP4


no

DP2
yes

DP3
yes

DP5
no

DP6
no

DP7
no

DP8
no

DP9
no

DP10
no

DP12
no

DP13
no

DP14
no

DP15
no

DP16
no

DP17
no

DP18
no

spont
no

About the use of this operation:


If the CCF/SSF does not get the required amount of digits, the call is released, and the SSF-SCF relationship is ended by sending an RT to the SCF. In an error situation, the SSF returns the following error codes to the SCF:
.

TaskRefused, generic: Further collection of address digits is not possible anymore (for example, complete dialling received, address complete information is sent back because of user interaction). TaskRefused, generic: Charging has already been started when the CollectInformation operation is received.

Parameters:
S NS supported not supported

40 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 14. Parameter

Support for CollectInformation parameters Nokia Siemens Networks' support


NS

Note number

extensions

No extensions have been defined for this operation.

Operation: Connect (CON) Direction: Usage: SCF -> SSF The SCF requests the SSF to route or forward the call to a specified destination. In addition, the SCF can change the other call parameters that are included in the Connect operation, for example, the identification presentation form of the calling line. It is possible that the SCF does not change the called party number at all, but uses the Connect operation only for changing the other parameters. Associated operations: None Comments: The SCF sends this operation as a final response operation. . gsmSSF preconditions: A control relationship exists between the gsmSSF and the gsmSCF. . The basic call processing has been suspended at DP. . The gsmSSF is in state 'Waiting for Instructions', or in state 'Waiting for End of User Interaction'. Note that the acceptance of CON in state 'Waiting for End of User Interaction' is an optional functionality available with Feature 1774: IN User Interaction during Call Setup. For more information, see Feature 1774: IN User Interaction during Call Setup, Feature Description. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

41 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 15. DP1


yes

SSP support for Connect operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
no

DP8
no

DP9
no

DP10
no

DP12
yes

DP13
yes

DP14
yes

DP15
no

DP16
no

DP17
no

DP18
no

spont
no

About the use of this operation:


If the CalledPartyNumber of the InitialDP operation, or the destinationRoutingAddress of the previous Connect operation is not the same as the destinationRoutingAddress of the new Connect operation, the CCF makes the pre-analysis, and goes to the Analyse_Info PIC in the OBCSM. In the TBCSM, a new leg is created, and the changed CalledPartyNumber is analysed in the OBCSM of the new leg. If the SCF does not want to change the called party address, but rather another piece of information (for example, the calling party address), the SCF can copy the calledPartyNumber from the InitialDP operation into the destinationRoutingAddress of the Connect operation. In this case the number is not re-analysed in the OBCSM, and a new leg is not created in the TBCSM. If the SCF changes the called party address in DP1, the barring analysis is done for the number changed by the SCF. This is valid only in DP1. In all the other cases, the barring analysis is done for the dialled digits. For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. In an error situation the SSF returns error codes to the SCF, such as:
.

'UnexpectedDataValue: cutAndPaste value is out of range'

Parameters:
S NS supported not supported

42 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 16. Parameter

Support for Connect operation parameters Nokia Siemens Networks' support


S NS NS S S S NS S 1

Note number

destinationRoutingAddress alertingPattern correlationID cutAndPaste originalCalledPartyID routeList scfID extensions iNtoINServiceInteraction gSMSupplementaryServiceControl extraForwardCallIndicator serviceInteractionIndicatorTwo ext-BasicServiceCode suppressionOfAnnouncement genericNumber machineIndicator chargeNumber originationLineInformation carrierSelectionInformation transitNetworkSelection numberPortabilityInfo iNTriggerkey serviceInteractionIndicators callingParty'sNumber callingParty'sCategory redirectingPartyID redirectInformation

NS S S S S 1 and 2 1

1 2

The maximum length of the parameter is 32 digits. The screening and number incomplete indicators are included, if allowed by the NI_AND_SI_INAP_REDNB (002:0501) PRFILE parameter.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

43 (196)

DX MSC/SSP/IP - SCP Interface Specification

About the use of the parameters:


.

destinationRoutingAddress
When the cutAndPaste parameter is not present, the handling of the destinationRoutingAddress is the following: The CCF in the OBCSM uses the destinationRoutingAddress for routing as it had been received from the SCF. The CCF also sets the 'send completed' information to the destinationRoutingAddress, and sends the Address Complete message back. After that, the CollectInformation operation is not accepted from the SCF anymore. In the TBCSM the CCF creates a new leg, and the destinationRoutingAddress is analysed on that leg. A decision about the need to re-analyse the number is based on the digits only, for example, the Type of Number or numbering plan are not checked. The SCF can use any of the number formats specified by the ISUP, as long as the Type of Number and the digits match each other. For further information, see ETS 300 356-1: Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services, v4.2.1, July 2001 [ITU-T Q.761 to Q.764 (1999) modified].

alertingPattern
The parameter is not supported, the SSF does not read the parameter.

correlationID
The parameter relates to the assisting/handoff SSF case that is not supported. The SSF does not read the parameter.

cutAndPaste
This parameter informs the CCF about how many digits are cut from the beginning of a called party number. The digits given in the destinationRoutingAddress are pasted by the CCF to the front of the called party number after cutting the digits. If this parameter is included, the call stays in the set-up phase in the OBCSM (for example, the Address Complete message is not generated and more digits can be collected by the CCF from the incoming circuit after receiving Connect with cutAndPaste).

44 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

In the TBCSM which is in the VMSC, the existence of cutAndPaste prevents the creation of a new leg. In the TBCSM which is in the GMSC, a new leg is created if Connect with cutAndPaste is received by the CCF. A new called party number is analysed in the created leg. If this parameter is used when the SCF does not want to change the destinationRoutingAddress, the cutAndPaste and destinationRoutingAddress parameters receive the values: cutAndPaste=1 and destinationRoutingAddress=the first digit of the calledPartyNumber, the parameter of the InitialDP operation.
.

originalCalledPartyID
The parameter contains the subscriber number that was called originally in a call forwarding case. The parameter is coded according to ETS 300 356-1.

routeList
In Originating Basic Call State Models the routeList parameter is used for transmitting routing category information (1...255) for charging or routing purposes. For further information, see Feature 1237: A-Number Validation and Queries to Start External Services, Feature Description. In Terminating Basic Call State Models the routeList parameter is always ignored.

scfID
The parameter is related to the assisting/handoff SSF case that is not supported. The SSF does not read the parameter.

serviceInteractionIndicators
The parameter is not supported, the SSF does not read the parameter.

callingPartyNumber
If the SCF sends this parameter, it replaces the existing calling party identity in the CCF. The parameter is coded according to ETS 300 356-1.

callingPartyCategory
This parameter is mapped from the signalling to the DX internal format according to the signalling mapping document, see the Mapping of External Data, Operating instructions, INAP section . The parameter is coded according to ETS 300 356-1.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

45 (196)

DX MSC/SSP/IP - SCP Interface Specification

redirectingPartyID
The parameter contains the number of a subscriber who has forwarded a call. The parameter is coded according to ETS 300 3561.

redirectionInformation
The SCF is allowed to freely set the redirectionInformation, and also the redirection counter, according to the ISUP formats and codes, as specified in ETS 300 356-1.

Extensions:
Note that the criticality of every extension is IGNORE by default.
.

Extension: iNtoINServiceInteractions
The SSF does not use this information, only stores and passes it to the SCF in the next InitialDP operation if another triggering takes place in the same BCSM. With this information, the SCF Service Logic Program knows which new IN services are involved in that BCSM. The updating and use of the data is up to the SCF. The SSF does not study or edit it, only stores the information between successive triggerings.

Extension: gSMSupplementaryServiceControl
With this parameter, the SCF can override the following GSM supplementary services by deactivating the SS for that particular call: . CLIR, BAOC, BOIC, BOIC-exHC, and ODB in the OBCSM . CFB, CFNRy, CFNRc, CLIP, and CW in the TBCSM Note that in the G-TBCSM the SCF cannot override any GSM SS. If the SCF provides the CLI with the presentation indicator 'allowed' and gSMSupplementaryServiceControl with the CLIR, the CLI presentation will be restricted. The SCF should not give contradictory orders. Therefore, if the CLIR is overridden by this parameter, the presentation status in the CLI must also have the value 'allowed'. If the rule is violated, the call may be released because of the supplementary service activation violation. In DP1 and DP2, if the user invokes the CLIR with a prefix and the SCF overrides the CLIR without removing the prefix, the call is released because of the violation of SS service invocation.

46 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

In DP3 and after the gSMSupplementaryServiceControl, the parameter has no effect anymore, since the CLIR check has already been made. In those DPs the SCF can affect the CLIR by modifying the CLI.
.

Extension: extraForwardCallIndicator
This extension consists of two separate parameters: CBI and NTA. The extension is used only in the networks supporting the corresponding signalling parameters. . With the CBI (calling line identity barring indicator) parameter the SCF orders the SSF to forward the information that the calling party does not have the possibility to use the CLIR. . With the NTA (network translated address) parameter the SCF orders the SSF to inform that the called party address has been translated by the network. The SSF does not use the NTA parameter at all if it receives the CallOfferingTreatmentIndicator in the ServiceInteractionIndicatorsTwo Extension from the SCF. The SCF can only set the NTA parameter; if the parameter is already set, the SCF cannot override it.

Extension: serviceInteractionIndicatorsTwo
With this parameter, the SCF can control the interworking between some network supplementary services and IN services. For further information, see GSM 09.02, v5.x.y, Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification, (Release 96). . Forward ConferenceTreatmentIndicator: With the value rejectConferenceRequest, the SCF can reject the Multi Party service (MPTY) requests of the terminating MS. The parameter is also mapped to network signalling. For further information, see ETS 300 356-1. . Backward ConferenceTreatmentIndicator: With the value 'rejectConferenceRequest', the SCF can reject the Multi Party service (MPTY) requests of the originating MS. The parameter is also mapped to the network signalling. For further information, see ETS 300 356-1 . . CallDiversionTreatmentIndicator: With the value 'callDiversionNotAllowed', the SCF can reject the Call Diversion services. In the GMSC, the call will be offered towards the subscriber even if the CFU is active or it is released in the CFNRc (imsi detach). In the VMSC, the call is released in the CFNRc or CFB cases. In the CFNRy case, call offering is continued. The parameter is also mapped to the network signalling. For further information ETS 300 356-1.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

47 (196)

DX MSC/SSP/IP - SCP Interface Specification

CallOfferingTreatmentIndicator: The SCF can control the value of the related network signalling Call Offering parameter. CallCompletionTreatmentIndicator: With the value 'rejectCallCompletionServiceRequest', the SCF can reject the use of CCBS. The backward cause value 'CCBS possible' is replaced by the 'CCBS not possible' value in the REL message. SuspendTimer: With this parameter, the SCF can set the value to the suspend timer. Only the shorter values, as used in the network, are accepted (called party re-answer). ConnectedNumberTreatmentIndicator: The SCF can control the interworking with the COLP and COLR services. . The value presentationRestricted sets the presentation status of the connected number, additional connected number, and redirection number to the value presentation restricted. . The value presentCalledINNumber replaces the connected number with the received called party number, and removes the additional connected number and redirection number. . The value presentCalledINNumberRestricted replaces the connected number with the received called party number, and sets the presentation status of it as 'presentation restricted'. The value also removes the additional connected number and redirection number. SuppressCallDiversionNotification: With the value TRUE the SCF can suppress the Call Diversion-related backward information: generic notification indicator with the value 'call is diverting', call diversion information, redirection number, and redirection number restriction. SuppressCallTransferNotification: With the value TRUE the SCF can suppress the Call Transfer-related backward information: generic notification indicator with either the value 'call transfer, alerting' or 'call transfer, active', and call transfer number. AllowCdINNumberPresentationInd: With this parameter, the SCF can control the presentation status of the forward Called IN Number parameter.

Extension: ext-BasicServiceCode
With this parameter, the operator can offer a CAMEL-like functionality in the home PLMN INAP, see Feature 994: CAMEL, Phase 2, Feature Description.

Extension: suppression OfAnnouncement

48 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

With this parameter, the operator can offer a CAMEL-like functionality in the home PLMN INAP, see Feature 994: CAMEL, Phase 2, Feature Description.
.

Extension: genericNumbers
With this parameter, the operator can offer a CAMEL-like functionality related to the Additional CLI in the home PLMN INAP, see Feature 994: CAMEL, Phase 2, Feature Description.

Extension: presentationNumber
With this parameter, the SCP can control the network signalling Presentation Number parameter. If the Presentation Number exists in the Connect operation, it is used in the forward set-up information if it is supported in the existing network signalling.

Extension: machineIndicator
With this parameter, the SCP can control the network signalling Machine Indicator parameter. If the Machine Indicator exists in the Connect operation, and it is supported by the existing network signalling, it is used in the forward set-up information.

Extension: chargeNumber
The parameter contains the number to be charged, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: originatingLineInformation
The parameter indicates the Origination Line Information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: carrierSelectionInformation
The parameter contains the Carrier Selection Information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: transitNetworkSelection
The parameter contains the Transit Network Selection, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: calledDialledNumber
The parameter contains the called party number if the destinationRoutingAddress parameter includes the Routing Number.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

49 (196)

DX MSC/SSP/IP - SCP Interface Specification

Extension: numberPortabilityQueryIndicator
The parameter contains the Number Portability Query Indicator. For further information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: inTriggerKey
The parameter transmits the Service Set Index (1...1999) for triggering to the IN service in the existing BCSM. For further information, see Feature 1237: A-Number Validation and Queries to Start External Services, Feature Description.

Operation: ConnectToResource (CTR) Direction: Usage: SCF -> SSF The SCF requests the SSF to connect the call party to the SRF for user interaction. Associated operations: DisconnectForwardConnection Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 17. DP1


yes

SSP support for ConnectToResource operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
no

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
no

spont
no

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. If the SCF gives a chargeable announcement in DP1, DP2, DP3, or DP4, it must give the charging bases by using the SendChargingInformation operation before sending the ConnectToResource operation.

50 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

If the SCF orders a chargeable announcement for the Trunk-originating call in DP1 or DP2, the charging zone for the trunk circuit accounting has not yet been determined, and the charging cannot be successfully done. As a result, the trunk circuit charging does not match the same kind of charging in the other end of the trunk circuit. It is up to the SCF to decide whether such charging is applied to the use of trunk circuits and to decide whether chargeable announcements are allowed under those circumstances. The ConnectToResource operation causes the sending of the Address Complete information to the network. The CollectInformation operation is not allowed from the SCF after ConnectToResource. The user interaction is possible for various call parties in various DPs as follows:

Table 18. DP
1 2 3 4 5 6 7 8 9 10 12 13 14 15 16 17 18

User interaction possibility for call parties in Detection Points For called party
not possible not possible not possible not possible not possible not possible chargeable chargeable 1) chargeable, if A released not possible not possible not possible not possible chargeable/free chargeable 1) chargeable/free, if A released 2) not possible

For calling party


chargeable/free chargeable/free chargeable/free chargeable/free chargeable/free chargeable/free not possible chargeable 1) chargeable/free, if B released 2) not possible chargeable/free chargeable/free chargeable/free not possible chargeable 1) chargeable, if B released not possible

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

51 (196)

DX MSC/SSP/IP - SCP Interface Specification

1) 2)

Charging is on during the MidCall User Interaction. If the ACR is reported before the DP, the value 'free' has to be used. If the ACR is reported after the DP, the value 'chargeable' has to be used.

In an error situation the SSF returns the following error codes to the SCF:
.

UnexpectedComponentSequence: The operation is not allowed during the SRF-SCF communication. TaskRefused, unobtainable: A chargeable announcement is requested for the released party in DP9. TaskRefused, congestion: The SRF is out of service. TaskRefused, unobtainable: An announcement is requested to the suspended party.

Parameters:
S NS supported not supported

Table 19. Parameter

Support for ConnectToResource operation parameters Nokia Siemens Networks' support


S S

Note number

resourceAddress extensions party iNtoINServiceInteraction chargeableUserInteraction interceptAnswer serviceInteractionIndicatorsTwo serviceInteractionIndicators

NS

Only 'none' is supported.

About the use of the parameters:

52 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

resourceAddress
The SSF uses only the integrated SRF, and expects that no resource address is given. Zero is used as default. The SSF does not read the parameter.

serviceInteractionIndicators
The parameter is not supported. The SSF does not read the parameter.

Extensions: The criticality of every extension is IGNORE by default.


.

Extension: party
Only the legID is possible. It is not possible to have the user interaction with both parties at the same time. The legID indicates which party the user interaction concerns. If the extension is not included, the user interaction takes place with the controlling party: In the OBCSM, with the calling party, except in the Disconnect DP if the calling party has released; In the TBCSM, with the called party, except in the Disconnect DP if the called party releases. In DP1-DP6 and DP12-DP14 the user interaction is possible only with the calling party. In DP7 and DP15 the user interaction is possible only with the called party. In DP9 and DP17 the user interaction is possible only with the party that remains off-hook. In DP8 and DP16 the user interaction is possible with the calling or the called party. An announcement or a tone is connected to the party without disconnecting the speech path.

Extension: iNtoINServiceInteractions
The SSF does not use this information. It only stores it and sends it back to the SCF in the next InitialDP operation if another triggering takes place in the same BCSM. With this information, the SCF Service Logic Program knows which other IN services are involved in the call. The updating and use of the data are up to the SCF. The SSF does not study or edit it, but only stores the information between the succeeding triggerings.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

53 (196)

DX MSC/SSP/IP - SCP Interface Specification

Note that the parameter does not contain the information that is received from the SCF in the previous BCSM(s).
.

Extension: chargeableUserInteraction
With this parameter, the SCF indicates whether the charging is started in the MSC/SSP in the beginning of the user interaction. . If chargeableUserInteraction=FALSE, the user interaction is free of charge for the user. . If the SCF does not send the extension, it is set to TRUE as a default in the SSF. In this case the charging is started in the MSC/SSP, and the user interaction is chargeable for the subscriber.

Extension: interceptAnswer
With this parameter, the SCF indicates whether a two-way connection to the subscriber is required for the user interaction. This is needed if the PromptAndCollectUserInformation operation is used in the user interaction. If the BothwayThroughConnectionInd parameter is included in the ServiceInteractionIndicatorsTwo Extension, the SSF does not read this extension. . If interceptAnswer=TRUE, the connection from the A party to the switch remains a one-way connection. . If the SCF does not send the extension, it is set to FALSE as a default in the SSF. In this case the connection is made a twoway connection to allow the DTMF collecting from the user. It is necessary to use the value 'FALSE' in cases where the DTMF digits must be collected from the user, and the digits cannot be received if the answer message or progress message that supports the two-way connection request is not sent. If the user is a mobile subscriber who is within the MSC/ SSP area, the digits can be collected without sending the answer, because the connect message is sent to the MS. Depending on the PBX type, the DTMF digits can possibly be collected without sending the answer also in PBX originating calls. Note that if the function 'early connect' (making the through connection by the ACM message) is in use in the network, it is possible to collect the DTMF digits from the trunk line even if the answer is not sent. The instruction not_to_send the answer message is stored in the incoming signalling file. If the SCF sends the CTR with the InterceptAnswer = FALSE, the SSF sends backwards only the ACM, and the originating MSC, which has the 'early connect' function, makes the both way connection towards the MS.

54 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Extension: serviceInteractionIndicatorsTwo
With this parameter, the SCF can control the interworking between some network supplementary services and the IN services (see the ETS 300 356-1 V4.2.1 (2001-07) Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services [ITU-T Q.761 to Q.764 (1999) modified]). . Backward ConferenceTreatmentIndicator: With the value 'rejectConferenceRequest', the SCF can reject the Multi Party service (MPTY) requests of the originating MS. A related parameter is also supported in the network signalling. . CallCompletionTreatmentIndicator: With the value 'rejectCallCompletionServiceRequest', the SCF can reject the use of the CCBS. The backward cause value 'CCBS possible' is replaced with the value 'CCBS not possible' in the REL message. . BothwayThroughConnectionInd: With this parameter, the SCF can request the two-way through connection from the originating side. A related parameter is supported also in the network signalling. If received, the InterceptAnswer Extension is ignored. . UserDialoqueDurationInd: With this parameter, the SCF can request the use of the long waiting for the answer value for User Interaction. A related parameter is supported also in the network signalling. . ConnectedNumberTreatmentIndicator: The SCF can control the interworking with the COLP and COLR services. The value 'presentationRestricted' sets the connected number, the additional connected number, and the redirection number presentation status to the value 'presentation restricted'. The 'presentCalledINNumber' replaces the connected number with the received called party number, and removes the additional connected number and the redirection number. The value 'presentCalledINNumberRestricted' replaces the connected number with the received called party number with the presentation status 'presentation restricted', and removes the additional connected number and redirection number.

Operation: Continue (CUE) Direction: Usage: SCF -> SSF The SCF requests the SSF to continue the call processing from the DP where it was suspended because of the SCF inquiry. Associated operations:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

55 (196)

DX MSC/SSP/IP - SCP Interface Specification

None. Comments: The SCF sends this operation as a final response operation. . gsmSSF preconditions: A control relationship exists between the gsmSSF and the gsmSCF. . The basic call processing has been suspended at the DP. . The gsmSSF is in state 'Waiting for Instructions', or in state 'Waiting for End of Temporary Connection'. Note that the acceptance of CUE in state 'Waiting for End of Temporary Connection' is an optional functionality available with Feature 1592: IN-controlled Selective Ringback Tone. For more information, see Feature 1592: INcontrolled Selective Ringback Tone, Feature Description. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 20. DP1


yes

SSP support for Continue operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
no

About the use of this operation:


Because there is no error component for this operation (class 4 operation), the SSF aborts the dialogue in case an error occurs. (For example, if the SCF uses the External IP and sends the Continue operation before the External IP connection has been fully released. This means that the operation is received in the SSF state Waiting for End of Temporary Connection).
.

Parameters: None.

56 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Operation: DisconnectForwardConnection (DFC) Direction: Usage: SCF -> SSF The SCF informs the SSF that the user interaction (performed by the SRF) is over, and the connection to the SRF is not needed any more. Associated operations: ConnectToResource, EstablishTemporaryConnection Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the same DPs as with the operations ConnectToResource and EstablishTemporaryConnection.
.

Parameters: None.

Operation: EstablishTemporaryConnection (ETC) Direction: Usage: SCF -> SSF The SCF requests the SSF to connect the call to an external assisting IP for the user interaction. Associated operations: DisconnectForwardConnection, InitialDP Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 21.

SSP support for EstablishTemporaryConnection operation in Detection Points DP4


yes

DP1
yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
no

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
no

spont
no

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

57 (196)

DX MSC/SSP/IP - SCP Interface Specification

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. If the SCF gives a chargeable announcement in DP1, DP2, DP3, or DP4, it must give the charging bases by using the SendChargingInformation operation before sending EstablishTemporaryConnection. If the rule is violated, the SSF sends the error 'TaskRefused' to the SCF. If the SCF orders a chargeable announcement for the Trunk-originating call in DP1 or DP2, the charging zone for the trunk circuit accounting has not been determined yet, and the charging cannot be successfully done. As a result, the trunk circuit charging does not match the same kind of charging in the other end of the trunk circuit. The EstablishTemporaryConnection operation causes the sending of the AddressComplete information to the network. The CollectInformation operation is not allowed from the SCF after the EstablishTemporaryConnection. The connection towards the external IP is made using the ISUP signalling. The SSF indicates this capability by sending the iPAvailable parameter in the InitialDP operation. The disconnection of the SSP-IP leg can be made with two methods: 1. The SCF requests the SRF notification about the end of the user interaction, and does not allow the IP to perform the release. When the SCF receives the notification, it requests the SSF to release the SSP-IP connection, and gives the additional instructions for the call. This method is recommended. The SCF allows the IP to release the SSF-IP connection after the user interaction. In this case the SCF will have problems with guessing when the release of the IP is completed, and the SSF is ready to receive further instructions from the SCF. If the release is incomplete, that is, the SSF is not yet in the state 'Waiting For Instructions', the SSF rejects the operations coming from the SCF. Due to this timing problem, this method is not recommended.

2.

After the SSF has received the EstablishTemporaryConnection operation, it starts the TSSF timer with the value of MTMR defined in the trigger. If the timer expires, the SSF releases the SSF-SRF and SSF-SCF connections. If the default value is not long enough for the user interaction, the SCF can extend the value by sending the ResetTimer operation to the SSF.

58 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

In an error situation, the SSF returns to the SCF error codes as follows:
.

UnexpectedComponentSequence: The operation is not allowed in this DP. TaskRefused, unknown_operation: A free announcement requested but not possible.

Parameters:
S NS supported not supported

Table 22. Parameter

Support for EstablishTemporaryConnection operation parameters Nokia Siemens Networks' support


S S S S

Note number

assistingSSPIPRoutingAddress correlationID scfID extensions party iNtoINServiceInteractions chargeableUserInteraction interceptAnswer serviceInteractionIndicatorsTwo chargeNumber originationLineInformation carrierSelectionInformation transitNetworkSelection serviceInteractionIndicators

1 1 1

NS

The correlationID and scfID can be individual parameters, or they can be embedded in the assistingSSPIPRoutingAddress.

About the use of the parameters:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

59 (196)

DX MSC/SSP/IP - SCP Interface Specification

assistingSSPIPRoutingAddress: . In the embedded method, the SCF packs the scfID and correlationID parameters inside the IP routing address, which is the called party number in the ISUP IAM message towards the IP. The ISUP is required all the way between the SSP and the IP. . In a separate method, the IP routing address contains only the IP address, the scfID and the correlationID that the SCF sends in separate parameters. This requires ISUP version 2 support between the SSP and the IP. correlationID
The coding method of the correlationID is up to the SCF, and the decoding is up to the external IP. The SSF only passes the information to the IP.

scfID
The coding method of the scfID is up to the SCF, and the decoding up to the IP. The SSF only passes the information to the IP.

serviceInteractionIndicators
The parameter is not supported. The SSF does not read the parameter.

Extensions:
The criticality of every extension is 'IGNORE' by default.
.

Extension: party
Only legID is possible, it is not possible to have the user interaction with both parties at the same time. With the legID, the SCF indicates which party the user interaction concerns. If the extension is not included, the user interaction takes place with the controlling part: in the OBCSM with the calling party, except in the Disconnect DP if the calling party releases; in the TBCSM with the called party, except in the Disconnect DP if the called party releases. In DP1-DP6 and DP12-DP14 the user interaction is possible only with the calling party. In DP7 and DP15 the user interaction is possible only with the called party.

60 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

In DP9 and DP17 the user interaction is possible only with the party that remains off-hook. In DP8 and DP16 the user interaction is possible with the calling or called party. When an announcement or a tone is connected to the party, the speech path is disconnected and reconnected after the user interaction.
.

Extension: iNtoINServiceInteractions
The SSF does not use this information. It only stores it and sends it back to the SCF in the next InitialDP operation if another triggering takes place in the same BCSM. With this information, the SCF Service Logic Program knows which other IN services are involved in the call. The updating and use of the data is up to the SCF. The SSF does not study or edit it, but only stores the information between the succeeding triggerings.

Extension: chargeableUserInteraction
With this parameter, the SCF indicates whether the charging is started in the MSC/SSP at the beginning of the user interaction. . If the chargeableUserInteraction = FALSE, the user interaction does not start the charging in the MSC/SSP. However, if data has to be collected from a subscriber who is not a mobile subscriber in the MSC/VLR area of the MSC/SSP, the answer message has to be sent, and the charging can be started in some other element in the network. . If the SCF does not send the extension, it is set to TRUE as a default in the SSF. In this case the charging is started in the MSC/SSP, and the user interaction is chargeable to the subscriber.

Extension: interceptAnswer
With this parameter, the SCF indicates whether a two-way connection to the subscriber is required for the user interaction. This is needed if the PromptAndCollectUserInteraction operation is used in the user interaction. If the BothwayThroughConnectionInd parameter is included in the ServiceInteractionIndicatorsTwo extension, the SSF does not read this extension. . If the interceptAnswer=TRUE, the connection from party A to the switch remains a one-way connection. . If the SCF does not send the extension, it is set to FALSE as a default in the SSF. In this case the connection is made a bothway connection to allow the DTMF collecting from the user.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

61 (196)

DX MSC/SSP/IP - SCP Interface Specification

It is necessary to use the value FALSE in the cases where the DTMF digits must be collected from the user, and the digits cannot be received if an answer message is not sent. If the user is a mobile subscriber within the MSC/SSP area, the digits can be collected without sending the answer. Depending on the PBX type, the DTMF digits can possibly be collected without sending the answer also in the PBX-originating calls. Note that if the 'early connect' function (making the connection with the ACM message) is in use in the network, it is possible to collect the DTMF digits from the trunk line even if the answer is not sent. The instruction not_to_send the answer message is stored in the incoming signalling file. In that case when the SCF sends the ETC with the InterceptAnswer = FALSE, the SSF sends back an ACM only. The originating MSC having the function 'early connect' makes the two-way connection towards the MS.
.

Extension: serviceInteractionIndicatorsTwo
With this parameter, the SCF can control the interworking between some network supplementary services and IN services. For further information, see ETS 300 356-1. . Backward ConferenceTreatmentIndicator: With the value 'rejectConferenceRequest' the SCF can reject the Multi Party service (MPTY) requests of the originating MS. A related parameter is supported also in the network signalling. . CallCompletionTreatmentIndicator: With the value 'rejectCallCompletionServiceRequest' the SCF can reject the use of the CCBS. The backward cause value 'CCBS possible' is replaced with the value 'CCBS not possible' in the REL message. . BothwayThroughConnectionInd: With this parameter, the SCF can request the two-way through connection from the originating side. A related parameter is supported also in the network signalling. If received, the InterceptAnswerExtension is ignored. . UserDialoqueDurationInd: With this parameter, the SCF can request the use of the long waiting for the answer value for User Interaction. A related parameter is also supported in the network signalling. . ConnectedNumberTreatmentIndicator: This allows the SCF to control the interworking with the COLP and the COLR services.

62 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

The value presentationRestricted sets the connected number, additional connected number, and redirection number presentation status to the value 'presentation restricted'. The value presentCalledINNumber replaces the connected number with the received called party number, and removes the additional connected number and redirection number. The value presentCalledINNumberRestricted replaces the connected number with the received called party number which has the presentation status 'presentation restricted', and removes the additional connected number and redirection number.

Extension: chargeNumber
This parameter contains the number to be charged.

Extension: originatingLineInformation
This parameter indicates the Origination Line Information.

Extension: carrierSelectionInformation
This parameter contains the Carrier Selection Information.

Extension: transitNetworkSelection
This parameter contains the Transit Network Selection.

Operation: EventNotificationCharging (ENC) Direction: Usage: SSF -> SCF The SSF reports to the SCF the charging event that was previously requested by the SCF with the operation RequestNotificationChargingEvent. The supported charging event types are the (Finnish) national ISUP messages MPM and CHG. Associated operations: RequestNotificationChargingEvent, Cancel Comments: None. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

63 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 23.

SSP support for EventNotificationCharging operation in Detection Points DP4


no

DP1
no

DP2
no

DP3
no

DP5
no

DP6
no

DP7
no

DP8
no

DP9
no

DP10
no

DP12
no

DP13
no

DP14
no

DP15
no

DP16
no

DP17
no

DP18
no

spont
yes 1)

1)

The ENC is sent when the CHG message is received or when the storing limit of the pulses received in the MPM message(s) is reached.

About the use of this operation:


The ENC for ChargeMessages is sent immediately after the receipt of the appropriate message from the network. The ENC for ChargePulses can be sent according to the REC_PULSE_BUFFERING (001:0076) PRFILE parameter (see MSC/ SSP Core INAP configuration data):
.

immediately after reception of pulses after receiving a specified number of pulses and at the end of the call

If the SCF is no longer interested in the pulses, and cancels the collection by the RNC with the parameter 'monitorMode' = 'transparent', the SSF does not send any pulses to the SCF even though it had stored the pulses in the buffer.

Parameters:
S NS supported not supported

64 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 24. Parameter

Support for EventNotificationCharging operation parameters Nokia Siemens Networks' support


S S NS NS S 1

Note number

eventTypeCharging eventSpecificInformationCharging legID extensions monitorMode

No extensions have been defined for this operation.

About the use of the parameters:


.

eventTypeCharging
Indicates the type of the report, charging message or charging pulses, as requested by the SCF: . H'00 = MPM message . H'01 = CHG message

eventSpecificInformationCharging
Contains the CHG or the MPM message, depending on the eventTypeCharging parameter. The data includes either the isup_mpm or the charge_msg. . the isup_mpm contains:

- pulses (1 octet) - tariff_type (1 octet) 0b00000000 tariff type not indicated' 0b00000001 international call charge' 0b00000010 international call charge including' transit network compensation charge' 0b00000011 trunk call charge' 0b00000100 trunk call charge including network' ' compensation charge' 0b00000101 transit network compensation charge' 0b00000111 local network compensation charge' 0b00001001 local call charge' 0b00001010 special traffic charge' 0b00001011 charge for services that do not' ' need a concession' 0b00001100 all charges may not be covered by' ' these messages' - aoc_indicator (1 octet)
.

the charge_msg contains:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

65 (196)

DX MSC/SSP/IP - SCP Interface Specification

- tariff type - tariff one_time_charge multiplier: 1: 1/1000' 2: 1/100' 3: 1/10' 4: 1' 5: 10' 6: 100' 7: 1000' currency time_tariff tariff effect: 1: New tariff.' 2: Replacing tariff.' multiplier currency - signalling point (where generated) - origin: 0: CHG message is received from outgoing circuit.' 1: CHG-message is generated in own exchange.' 2: CHG-received from SCP.'
.

legID
The parameter is not sent to the SCF.

monitorMode
The parameter always has the value 'notifyAndContinue'.

Operation: EventReportBCSM (ERB) Direction: Usage: SSF -> SCF The SSF informs the SCF of the encountered callrelated event that has been previously requested by the SCF with the RequestReportBCSMEvent operation. Associated operations: RequestReportBCSMEvent, Cancel

66 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Comments:

Support in DPs:

The SSF sends this operation only after an armed Event Detection Point (EDP) has been encountered. If the DP is an EDP-R, the CCF is stopped until the final response from the SCF is received or the supervision timer TSSF expires (for timer information, see MSC/SSP Core INAP configuration data). If the DP is an EDP-N, the CCF continues immediately, and no response is expected from the SCF. The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 25. DP1


no

SSP support for EventReportBCSM operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
no

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
no

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. The last EventReportBCSM (EDP-N) is sent either in the TC-END, if the CS1_LAST_OP_IN_TC_END (002:0599) PRFILE parameter value is TRUE (default), or in the TC-CONTINUE, if the parameter value is FALSE.

Parameters:
S NS supported not supported

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

67 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 26. Parameter

Support for EventReportBCSM operation parameters Nokia Siemens Networks' support


S S S S S

Note number

eventTypeBCSM eventSpecificInformationBCSM legID miscCallInfo extensions noAnswerCause chargingBasis forwardedToNumber midCallInformation

1 2 3

1 2

DP values 1 and 12 are not sensible. The collectedSpecificInfo and the analysedInfoSpecificInfo have the maximum length of 32 digits. In the O_Disconnect and T_Disconnect DPs, the direction of the release is indicated by this parameter.

About the use of the parameters:


.

eventTypeBCSM
The SSF always includes this parameter. . In the OBCSM, the cause codes (see the Clear Code List, References) to affect DP4, 5, and 6 can be configured with the end-of-selection analysis. . In the TBCSM, the following internal cause values affect DP14:
b_answer_time_out, crct_released_by_co_exc, cf_ms_not_reply_notif_to_a, cf_ms_not_reply_no_notif_a, cd_t_lcf_no_answ_no_notif_to_a, cd_t_lcf_no_answ_notif_to_a
.

In the TBCSM, all other internal cause values which do not affect DP14, affect DP13.

eventSpecificInformationBCSM:

68 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Only the following subparameters can be filled by the SSF: . collectedInfoSpecificInfo . analysedInfoSpecificInfo . routeSelectFailureSpecificInfo . oCalledPartyBusySpecificInfo . oDisconnectSpecificInfo . tCalledPartyBusySpecificInfo . tDisconnectSpecificInfo
.

legID:
This parameter is used only in the Disconnect DP, and indicates which party is released. In the OBCSM, the controlling leg means the calling party; in the TBCSM, the controlling leg means the called party.

miscCallInfo:
The SSF returns the value that the SCF has requested with the RRB operation. If the data is request, the DP is handled as an EDP-R; if the data is notification, the DP is handled as an EDP-N.

Extensions:
The criticality of every extension is IGNORE.
.

Extension: noAnswerCause:
This is an additional piece of information in the event report from the O_No_Answer or T_No_Answer DP. With this parameter, the SSF sends the cause value to the SCF in the O_No_Answer and T_No_Answer DPs. The possible values are the following: . In the OBCSM, the cause is one of those that have been defined to meet the O_No_Answer DP in the end-of-selection analysis. . In the TBCSM, the internal cause can be: b_answer_time_out The internal cause (see the Clear Code List, References) is mapped to the INAP cause according to the INAP mapping document (see the Mapping of External Data, Operating instructions, INAP section).

Extension: chargingBasis

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

69 (196)

DX MSC/SSP/IP - SCP Interface Specification

With this extension, the SSF gives the SCF information about the charging parameters for the call, if available (for example, based on the charging analysis). The parameter contains the charging zone value valid at the moment for the charging. In the OBCSM, the parameter concerns the originating call charging; in the TBCSM, which is in the VMSC, it concerns the terminating call charging. In the TBCSM, which is in the GMSC, the charging zone value is not sent.
.

Extension: forwardedToNumber
This extension contains the 'C-number' applied to the active GSM or PBX call forwarding. The parameter is sent from the TBCSM in the VMSC. In the T_Busy DP, the value is the C-number of the CFB or of the CFNRc supplementary service, and in the T_No_Answer DP, the value is the C-number of the CFNRy supplementary service. In the T_Answer and T_Disconnect DPs, the parameter contains the C-number where the call has already been routed. The parameter is sent from the TBCSM in the GMSC. In the T_Busy DP, the value is the C-number of the CFB from the RCH, or that of the CFNRc from the RCH or from the second SRI-ACK, and in the T_No_Answer DP, the value is the C-number of the CFNRy from the RCH. In the T_Answer and T_Disconnect DPs, the parameter contains the C-number where the call has already been routed.

Extension: midCallInformation:
This parameter is available in DPs 8 and 16, and contains the MidCall code (for example, D5'H for threshold warning and D6'H for user midcall or other SS code that caused the encountering of the MidCall DP) and the possible USSD-string with a related coding scheme. The operator can define, using MML commands, which supplementary service codes cause encountering of the MidCall DP.

Operation: FurnishChargingInformation (FCI) Direction: Usage: SCF -> SSF The SCF gives the SSF charging-related information which is included by the SSF in the Call Detail Records (CDRs).

70 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Comments: Support in DPs:

The SCF sends this operation as an intermediate response or a spontaneous operation. The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 27.

SSP support for FurnishChargingInformation operation in Detection Points DP4


yes

DP1
yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
yes

About the use of this operation:


For the coding of the network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions. One FurnishChargingInformation operation or several successive operations, depending on the controlInformation parameter, create an IN CDR in the MSC. The amount of generated IN CDRs is stored in the related basic CDR, for example, in the MOC-CDR or the CF-CDR. If the SCF sends the FCI operation spontaneously when the release of the call is started by the CCF, the information can be lost. It is safer for the SCF to send the operation when the CCF is in the DP. The SCF should not send the FCI operation to the G-TBCSM together with the Connect operation. Since in this case the ROAMING CDR is not generated, the SSF does not have any CDR to tie to the IN CDRs. If the SCF sends the FCI operation to the G-TBCSM together with the Connect operation, the SSF will generate an IN CDR, and it will be sent to the billing system. Instead of sending the FCI to the G-TBCSM, it is recommended that the SCF sends the FCI operation to the OBCSM in the forwarding leg. Then the generated IN CDRs are tied to the FORWARDING CDR. In an error situation, the SSF returns to the SCF the following error codes:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

71 (196)

DX MSC/SSP/IP - SCP Interface Specification

UnexpectedComponentSequence: The operation is received when waiting for a new limit from the SCF (after the previous limit has been expired). UnexpectedDataValue: The ControlInfo is out of range. TaskRefused: The SCF requested a generation of the RCC CDR that is not possible.

Parameters:
S NS supported not supported

Table 28. Parameter

Support for FurnishChargingInformation operation parameter Nokia Siemens Networks' support


S

Note number

fCIBillingChargingCharacteristics

About the use of the parameters:


.

fCIBillingChargingCharacteristics
The coding is network-specific. The DX 200 MSC/SSP supports the following data: . controlInformation Using this parameter, the SCF can request the SSF to process the IN CDR as follows: add a new IN service information element, replace the previous element with a new one or remove the previous service information (if the serviceInformationLength is zero) and add data into the existing element. The SCF can also request the creation of a Remote Charging Control (RCC) CDR. The SCF can use the following values: . 00'H: Start the generation of a new IN CDR and store the previous one. . 10'H: Start the generation of a new CDR, overwriting the previous one that is not stored.

72 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

H'02: If there is no IN CDR open, start the generation of a new CDR, and leave it open. Store the previous IN CDR. If an IN CDR is already open, append the data into the IN CDR and leave it open. The maximum number of FCI operations for one IN CDR is 5 (with a maximum 62 octets of data in each). . H'01: If there is no IN CDR open, start the generation of a new IN CDR, and close it. Store the previous IN CDR. If an IN CDR is already open, append the data into the IN CDR and close it. . 03'H: Generate a Remote Charging Control (RCC) CDR. Note that in this case the MSC/SSP uses the serviceInformation parameter as well. If the SCF uses other values than specified, the SSF returns the error unexpectedDataValue. serviceInformationLength It indicates the amount of octets that the serviceInformation contains. The value must be in the range 0...310 (decimal). The SSP does not read the length from this parameter, but calculates it from the length of the received FCI operation. serviceInformation With this parameter, the SCF can give extra instructions for the billing system, for example, to perform reverse charging using the charged number included in the serviceInformation. It contains the charging data for the billing system provided by the SCF. For the SSF, it is transparent data, meaning that it has no influence on the charging functionality in the MSC/SSP, for example, on the generation of AoC parameters. The SSF copies this octet string into the IN CDR for the Billing System. The coding of serviceInformation must be agreed between the SCF Service Logic Program and the Billing Center. When the RCC CDR is concerned, the first octet of serviceInformation indicates the type of the RCC CDR: . 01: Create additional RCC CDR. . 02: Create replacing RCC CDR. Note that in the RCC case, if the following octets of the serviceInformation exist, they are ignored.
.

Operation: InitialDP (IDP) Direction: Usage: SSF -> SCF The SSF requests a service from the SCF when it detects an active trigger in a TDP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

73 (196)

DX MSC/SSP/IP - SCP Interface Specification

Associated operations: None. Comments: Before sending this operation, the trigger conditions and call gapping are checked. The CCF is stopped until the final response from the SCF is received. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 29. DP1


yes

SSP support for IntialDP operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
no

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. The InitialDP operation is sent to the SCF when:
.

The SSF functionality is active in the MSC/SSP. An armed TDP is encountered. The triggering conditions (if any) match. The SCF enquiry is not gapped. There is no controlling relationship from that BCSM to an SCF. There is no more than 1 monitoring relationship between that BCSM and an SCF. The maximum number of triggering, 10, from one BCSM has not been exceeded. The INAP protocol handler is capable of delivering the operation through the TC.

74 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Note that if the SSP detects the call to be an emergency call, the IDP operation is not sent to the SCF. The call is detected as an emergency as early as in DP1, if an emergency set-up is received from the MS (for example, the call is made without a SIM card). If a subscriber dials an emergency number, the call is not detected as an emergency call until DP2 (after the pre-analysis). When the SSF leaves the TDP, it is disarmed regardless of whether the triggering has taken place or not. If the SCCP segmentation is not used, the Core INAP operation must fit into one TC message. In theory, if the InitialDP is equipped with all its parameters including the extensions, this limit can be exceeded. However, this is not very likely because usually only a part of the parameters are available when the triggering takes place. To avoid an overflow in the TC message, the INAP protocol handler checks the length and leaves out the lower priority parameters, if there is no room left. The priority order from the highest to the lowest is the following. The parameters defined by ETSI always fit into the TC message.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o highLayerCompatibility originalCalledPartyID additionalCallingPartyNumber forwardCallIndicators iPAvailable bearerCapability Extension: iMSI Extension: TMSI Extension: gatewaySSFIndication Extension: iMEI Extension: gSMSupplementaryServiceList Extension: mSRN Extension: absSubscriber Extension: iNtoINServiceInteractions Extension: pNI Extension: oDB-info Extension: mSRoamingStatus Extension: cUG-info Extension: msClassmarks Extension: gSMLocationInfo Extension: usedSignalling Extension: chargingBasis Extension: extraForwardCallIndicator Extension: forwardedToNumber Extension: presentationNumber Extension: midCallInformation Extension: ext-BasicServiceCode Extension: serviceInteractionIndicatorsTwo Extension: machineIndicator Extension: timingAdvanceValue

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

75 (196)

DX MSC/SSP/IP - SCP Interface Specification

o o o o o o o o

Extension: Extension: Extension: Extension: Extension: Extension: Extension: Extension:

measuredCellList chargeNumber originatingLineInformation carrierSelectionInformation transitNetworkSelection numberPortabilityInfo localisedServiceArea eventTypeCobi

Parameters:
S NS supported not supported

Table 30. Parameter

Support for InitialDP operation parameters Nokia Siemens Networks' support


S S S S S NS S S S S 2 3 4 1 1 1

Note number

serviceKey calledPartyNumber callingPartyNumber callingParty'sCategory cGEncountered iPSSPCapabilities iPAvailable locationNumber originalCalledPartyID extensions iNtoINServiceInteractions iMSI iMEI TMSI gSMSupplementaryServiceList mSRN mSRoamingStatus pNI oDB-info cUG-info absSubscriber

76 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 30. Parameter

Support for InitialDP operation parameters (cont.) Nokia Siemens Networks' support Note number

msClassmarks gSMLocationInfo usedSignalling chargingBasis extraForwardCallIndicator gatewaySSFIndication forwardedToNumber midCallInformation ext-BasicServiceCode presentationNumber machineIndicator measuredCellList chargeNumber originationLineInformation carrierSelectionInformation transitNetworkSelection numberPortabilityInfo timingAdvanceValue localisedServiceArea eventTypeCobi highLayerCompatibility serviceInteractionIndicators additionalCallingPartyNumber forwardCallIndicators bearerCapability eventTypeBCSM redirectingPartyID redirectionInformation S NS S S S S S S 1 and 5 1 4

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

77 (196)

DX MSC/SSP/IP - SCP Interface Specification

1 2 3 4 5

The maximum length is 32 digits. The default is the normal MSC/SSP/IP capability. Concerns the routing to the external IP; the internal IP is available by default. With the GSM subscriber, the Cell Global Identity (CGI) or the operator defined location data is used. The screening and number incomplete indicators are included, if allowed by the NI_AND_SI_INAP_REDNB (002:0501) PRFILE parameter.

About the use of the parameters:


.

serviceKey
This parameter contains the value of the SKEY in the trigger file. The value is administered with an MML command.

calledPartyNumber
This parameter contains the called party number that the CCF has when the triggering takes place. For further information, see ETS 300 356-1. In DP1, it is the dialled number and it can also be a short number. In the other DPs, at least the pre-analysis has been made. It can also be an MSRN or a Hand Over number (if the TriggerKey has been found among the circuit group data). In a data call, when triggered from the CF leg, the SSF sends a secondary MSISDN number to the SCF.

callingPartyNumber
This parameter contains the calling party number that the CCF has at the moment the triggering takes place. For further information, see ETS 300 356-1. It can be missing if not received from the incoming signalling, even if it has been requested.

callingPartysCategory
The parameter is mapped according to the Mapping of External Data, Operating instructions, INAP section. For the coding, see the ETS 300 356-1.

cGEncountered

78 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

This parameter is sent if the call gapping is active for the ServiceKey, the called number, the ServiceKeyAndCallingNumber, or the ServiceKeyAndCalledNumber, but the triggering is not gapped. With this information, the SCF can check that the CallGap operation has been successfully processed in the SSF.
.

iPSSPCapabilities
This parameter is never sent to the SCF.

iPAvailable
This parameter is sent to the SCF if the MSC/SSP has the capability to make the connection to an external assisting IP, according to the orders received in the EstablishTemporaryConnection operation.

locationNumber
This parameter contains either the GSM CGI information or the location information defined by the user. The user-defined information is possible with Feature 688: Location Information to PSTN if the user has used that feature to define the value that is sent to the SCF. For the possible value, see Feature 688: Location Information to PSTN, Feature Description. In other cases, the CGI is sent using the ISUP locationNumber parameter with default values, but the NatureOfAddress must be '126', decimal. The digits are coded, so that the CC and NC are BCD coded, and the LAC and CI are HEX numbers. For example, the CGI with the values 'MCC=262', 'MNC=03', 'LAC=6060 (H'17AC)', and 'CI=606 (H'025E)' is coded as '62 F2 30 17 AC 02 5E'. This parameter always concerns the location of the calling party. For the called party location, the extension gSMLocationInfo is used. In trunk-originating call cases, the parameter is passed to the SCF as it has been received from the incoming signalling.

originalCalledPartyID
If the original called party identification has not been received from the incoming signalling, this parameter, if sent to the SCF, contains the ID of the forwarding party. For further information, see ETS 300 356-1.

highLayerCompatibility
When the SCF receives this parameter from the OBCSM, it concerns the calling subscriber. If it is received from the TBCSM, it concerns the called subscriber.

serviceInteractionIndicators

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

79 (196)

DX MSC/SSP/IP - SCP Interface Specification

This parameter is never sent to the SCF.


.

additionalCallingPartyNumber
In this parameter, the SSF sends to the SCF the corresponding parameter received from the trunk signalling, or, in the PBX case, the original CLI received in the set-up message. In mobile-originating calls, the parameter is not sent to the SCF. For further information, see ETS 300 356-1.

forwardCallIndicators The following indicators are implemented: . National/international . Interworking . End-to-end information: this parameter is always set to the value 'no end-to-end method available'. . ISDN user part . ISDN user part preference . ISDN access . SCCP method

bearerCapability
In a mobile-terminating call in the TBCSM, this is the BC of the called mobile subscriber that is stored in the VLR.

eventTypeBCSM
This parameter contains the DP where the triggering takes place.

redirectingPartyID
This parameter contains the last forwarding party in the first place. If this parameter is not sent by the SSF, the SCF should study the originalCalledPartyID. For further information, see ETS 300 356-1.

redirectionInformation
For example, the redirection counter indicates to the SCF that the call is a forwarded call. The parameter is coded according to ETS 300 356-1.

Extensions:
The criticality of every extension is IGNORE.

80 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Extension: iNtoINServiceInteractions . serviceKey . activity The SSF has stored the value of this extension from the operation Connect or ConnectToResource and sends it back to the SCF in case of retriggering in the same BCSM instance. The data is written by the SCF service programs that had been involved in the call before this service was activated. With this information, the SCF service programs know which other IN services are involved in the call. The updating and use of the data depends on the SCF. The SSF does not read or edit the data, it only stores the information between the successive triggerings. Extension: iMSI
In an MOC case the IMSI of the calling subscriber, and in an MTC case, the IMSI of the called subscriber is sent to the SCF. In a GSM forwarding case, it is the IMSI of the forwarding subscriber that is sent to the SCF.

Extension: iMEI
This parameter is possible only when the IMEI check is active, because it is only in that case that the CCF knows the IMEI. In a call forwarding case, the parameter is not sent. The SSF passes the IMEI of the calling MS (from the DPs of the OBCSM) or that of the called MS (from the DPs of the Terminating BCSM).

Extension: TMSI
In an MOC case the TMSI of the calling subscriber, and in an MTC case, the TMSI of the called subscriber is sent to the SCF. In a GSM forwarding case, it is the TMSI of the forwarding subscriber that is sent to the SCF. The TMSI is only sent to the SCF when a valid value is available.

Extension: gSMSupplementaryServiceList
With this extension, the SSF provides the SCF information about the active GSM Supplementary Services of the calling mobile subscriber (from the OBCSM), or the called mobile subscriber (from the TBCSM). With this information, the SCF Service Logic Program can control the interactions between IN and GSM Supplementary Services.

Extension: mSRN

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

81 (196)

DX MSC/SSP/IP - SCP Interface Specification

With this extension, the SSF tells the SCF the MSRN that has been reserved in the VMSC for the terminating call of the mobile subscriber. This extension is also used to pass the VLR address information to the SCF in the GMSC. . In the GMSC TBCSM, the information is the VLR address where the called mobile subscriber is roaming. . In the VMSC TBCSM, it is the real MSRN.
.

Extension: mSRoamingStatus
In the VMSC mobile OBCSM this parameter indicates the roaming status of the calling mobile subscriber. In the VMSC visited TBCSM, this parameter indicates the roaming status of the called mobile subscriber. The parameter is not sent from the gateway TBCSM. In a GMSC/VMSC GSM forwarding case, it is not sent from the forwarding OBCSM. The possible values are:
home_country another_country home_network another_network home_cntry_and_nw home_cntry_other_nw other_cntry_and_nw unknown = = = = = = = = 0x30; 0x40; 0x01; 0x02; 0x31; 0x32; 0x42; 0xff;

Extension: pNI
If the subscriber has the PNP service provisioned, this parameter indicates the allocated Private Number Index. Values 0...254 indicate the Private Number Index of the subscriber; value 255 indicates that the subscriber is a PNP-subscriber, but the PNI is unknown. The PNP function is realised by the optional Feature 141: Mobile Centrex. If the feature is not in use, no PNI is sent to the SCF.

Extension: oDB-info
With this extension, the SSF gives the SCF information about the GSM Operator Determined Barring feature. The Service logic can take this information into account in number translation services, when deciding if the subscriber is allowed to make the call or not.

82 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

If the SCF lets the call continue (with the same or changed called party address), the MSC/SSP makes the barring analysis for the original called party number (after the pre-analysis has been made for it), when it is triggered after TDP1. If the triggering takes place in DP1, the barring is checked for the given SCF number. Also, in this case, a pre-analysis has been made for the number.
.

Extension: cUG-info
From the OBCSM the SSF sends the SCF information about the GSM feature CUG concerning the calling subscriber, and from the TBCSM, the one concerning the called subscriber.

Extension: absSubscriber
This is additional information from the SSF to the SCF about the status of the called mobile subscriber. The SSF does not send this parameter from the OBCSM. In the VMSC TBCSM the SSF sends the parameter only from DP12 (after paging). In a busy case, the value 'no specific information' is used. If no page response is received from the MS, the value 'no page response' is used. The value 'imsi detached' is sent from the GMSC TBCSM DP12. . No specific information . IMSI Detach . No Page Response

Extension: msClassmarks
It contains, in case of an MOC, the MS classmark 2 of the calling MS, and, in case of an MTC in the VMSC, the MS classmark 2 of the called MS. The parameter is conditional: it is sent to the SCF if received from the MS.

Extension: gSMLocationInfo
With this extension, the SSF sends the location information of the called MS to the SCF, while the CS-1 parameter locationNumber always contains the location of the calling MS. After a successful paging, the location of the called party is sent from the TBCSM in the VMSC. This parameter contains either the GSM CGI information, or the location information defined by the user. The user-defined information is possible with Feature 688: Location

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

83 (196)

DX MSC/SSP/IP - SCP Interface Specification

Information to PSTN. For the possible value, see the corresponding feature description. (In the GMSC, the mSRN parameter is used to indicate the address of the serving VLR). If available, the location of the calling party is also sent in the locationNumber parameter.
.

Extension: usedSignalling
With this extension, the SSF informs the SCF about the capabilities of the incoming/outgoing signalling. The signallings are coded as follows: undefined_c BSSAP TUP,ITUP IUP,NUP ISUP DPNSS 30B+D R2 PAD --> --> --> --> --> --> --> --> --> SSF SSF SSF SSF SSF SSF SSF SSF SSF does not send the parameter sends (1) sends (2) sends (3) sends (4) sends (5) sends (6) sends (7) sends (8)

Besides the signalling code, the parameter contains the signalling version. The operator can define this value for the incoming or outgoing signalling with MML commands.
.

Extension: chargingBasis
With this extension, the SSF gives the SCF information about the charging parameters for the call, if available, for example, based on the charging analysis. The parameter contains the charging zone value for the charging valid at the moment. In the OBCSM, it concerns the originating call charging; in the TBCSM of the VMSC, it concerns the terminating call charging. In the TBCSM of the GMSC, the charging zone value is not sent.

Extension: extraForwardCallIndicator: . With the CBI parameter the SSF informs the SCF that the calling party does not have the possibility to use the CLIR. . With the NTA parameter, the SSF informs the SCF that the called party address has been translated by the network. This is sent only if the corresponding signalling parameters have been received from the network. Extension: gatewaySSFIndication

84 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

If the parameter is present, the triggering takes place in the TBCSM of the GMSC (where the HLR enquiry was made). If the parameter is absent, the triggering takes place in the TBCSM of the VMSC. The parameter is not sent from the OBCSM.
.

Extension: forwardedToNumber
The parameter is sent from the TBCSM in the VMSC. In the T_Busy DP, the value is the C-number of the CFB or that of the CFNRc supplementary service, and in the T_No_Answer DP, it is the Cnumber of the CFNRy supplementary service. In T_Answer and T_Disconnect DPs, the parameter contains the C-number if the call has already been routed. The parameter is sent from the TBCSM in the GMSC. In the Termination_Attempt_Authorized DP, the value is the C-number of the CFU, or that of the CFNRc supplementary service if it is received in first SRI-ACK. In the T_Busy DP, the value is the C-number of the CFB from the RCH, or that of the CFNRc from the RCH, or from the second SRI-ACK. In the T_No_Answer DP, it is the C-number of the CFNRy from the RCH. In the T_Answer and T_Disconnect DPs, the parameter contains the C-number if the call has already been routed.

Extension: serviceInteractionIndicatorsTwo
With this parameter, the SCF can control the interworking between some network supplementary services and IN services. . Forward ConferenceTreatmentIndicator: The value of the related forward network signalling parameter, if available, is carried to the SCF. For further information, see ETS 300 356-1 . . Backward ConferenceTreatmentIndicator: The value of the related backward network signalling parameter, if available, is carried to the SCF. For further information, see ETS 300 356-1. . CallDiversionTreatmentIndicator: The value of the related forward network signalling parameter, if available, is carried to the SCF. For further information, see ETS 300 3561. . CallOfferingTreatmentIndicator: The value of the related forward network signalling parameter, if available, is carried to the SCF. For further information, see ETS 300 356-1.

Extension: midCallInformation

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

85 (196)

DX MSC/SSP/IP - SCP Interface Specification

This parameter is available in DPs 8 and 16 (threshold warning or user midcall), and contains the MidCall code (D5'H for threshold warning and D6'H for user midcall), and the possibly received USSD-string with a related coding scheme. The operator can define, with MML commands, which supplementary service codes cause the encountering of the MidCall DP.
.

Extension: ext-BasicServiceCode
With this parameter, the operator can offer CAMEL-like functionality in the Home PLMN INAP. For further information, see Feature 994: CAMEL, Phase 2, Feature Description.

Extension: presentationNumber
The parameter contains the received Presentation Number parameter, if supported in the originating side in network signalling.

Extension: machineIndicator
The parameter contains the received Machine Indicator parameter, if supported in the originating side in network signalling.

Extension: measuredCellList
The parameter provides the measured cell list. It can be used to determine the location of the calling subscriber. The parameter contains 1 to 7 cell IDs (LAC+CI), that is, a serving cell ID and 1 to 6 neighbour cell IDs.

Extension: chargeNumber
The parameter contains the number to be charged. For further information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: originatingLineInformation
It indicates the Origination Line Information. For further information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: carrierSelectionInformation
The parameter contains the Carrier Selection Information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: transitNetworkSelection
The parameter contains the Transit Network Selection. For further information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

86 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Extension: NumberPortabilityInfo
The parameter contains Number Portability -related information: npRoutingNumber calledDialledNumber contains the called party number if the destinationRoutingAddress parameter includes the Routing Number. numberPortabilityQueryIndicator For further information, see Feature 1055: SS7 Stack Selection for IN Protocols in SSP, Feature Description.

Extension: timingAdvanceValue
The parameter is available in the OBCSM if received from the Ainterface. For further information, see Feature 1026: Use of Timing Advance Value for Location Based Services, Feature Description.

Extension: localisedServiceArea
The parameter is available if SoLSA is supported.

Extension: EventTypeCobi
The parameter indicates whether the call is a COBI call involved with the ISDN CCBS. Other IN functionalities than number translations are not supported in COBI calls. For further information, see Feature 234: Completion of Calls to Busy Subscriber Phase 2, Feature Description.

Operation: PlayAnnouncement (PA) Direction: Usage: SCF -> SRF The SCF requests the SRF to send information to the user terminal. . Associated operations: ConnectToResource
. . .

SpecializedResourceReport (linked operation) Cancel DisconnectForwardConnection

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

87 (196)

DX MSC/SSP/IP - SCP Interface Specification

Comments:

Support in DPs:

The SCF sends this operation as an intermediate response operation after sending the ConnectToResource operation. The SSP supports the operation in the same DPs as with the ConnectToResource operation.

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. If the SCF requests information about the completion of the announcement, the linked operation SpecializedResourceReport is sent to the SCF when the announcement has been played.

Parameters:
S NS supported not supported

Table 31. Parameter

Support for PlayAnnouncement operation parameter Nokia Siemens Networks' support


S S S S

Note number

informationToSend disconnectFromIPForbidden requestAnnouncementComplete extensions languageID

The informationToSend.inbandInfo.messageID.text and the informationToSend.displayInformation are not supported.

About the use of the parameters:

88 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

informationToSend . inbandInfo: . numberOfRepetitions The default is 1. If the SCF does not send this default value, the SRF plays the announcement once. . duration If the duration is given, the announcement is stopped after the time has passed, even if the repetition count has not been reached. . interval . messageID . The elementaryMessageID contains 3 digits and forms the announcement identifier. The SRF adds the fourth digit, the announcement case, and sets it to the value 'IN Announcement'. The SRF also adds the fifth digit: language identification. If the SCF does not send the extension languageId, the SRF uses the default value defined by the operator. . The elementaryMessageIDs can contain up to 5 announcement IDs. . The SRF is not capable of converting the SCFprovided text to speech. The sub-parameter text is not supported. . For a variableMessage, an announcement has been recorded in the MSC, containing the fixed announcement parts and the variable announcements between them. The SCF gives the elementaryId of the proper announcement and the required variableParts data to be played during the variable announcement. The SCF must know the structure of the announcement containing variable parts, and must provide the proper type of information for each variable announcement part. The SRF is capable of handling all the variable part types defined by the variablePart parameter. . tone Like the announcement identifier, the toneID consists of 3 digits, and defines the tone to be played in the MSC. . displayInformation

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

89 (196)

DX MSC/SSP/IP - SCP Interface Specification

The SRF is not capable of displaying the information provided by the SCF on the display of a mobile phone or ISDN terminal. The parameter is not accepted. Instead, an error is returned to the SCF.
.

disconnectFromIPForbidden . If the SCF sets this parameter to the value 'TRUE', the SCF disconnects the SRF by using the DisconnectForwardConnection operation, after the SRF has reported that the user interaction is completed, and the SCF does not continue the user interaction any more. The SCF requests the report, by setting the requestAnnouncementComplete = TRUE, to know when the SRF can be released. . If the SCF sets this parameter to FALSE, the SRF is released automatically when the user interaction is completed. The SCF also requests the report to know when it can send the next operation to the SSF after the user interaction. If the SCF tries to send the SSF-SRF operation to the SSF before the SRF is fully released, the SSF does not accept the operation, but returns an error. requestAnnouncementComplete . If this parameter is missing or set to TRUE, the announcement complete notification is sent to the SCF. . If the value is FALSE, the SCF does not know when the announcement is completed.

Extensions: The criticality of every extension is IGNORE by default.


.

Extension: languageID
With this parameter, the SCF can order the announcement to be played by using 1- 4 languages in sequence. The announcement is played using the defined languages in sequence, following the order in the languageID parameter. The announcement identifier is the same for every announcement. But the SRF places the digit of the first language ID as the fifth digit of the announcement index for the first announcement to be played, then places the digit of the second language ID as the fifth digit for the second announcement index, and so on up to the fourth announcement. If, for example, the numberOfRepetitions is 2, the announcement is played twice in each language.

Operation: PromptAndCollectUserInformation (P&C)

90 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Direction: Usage:

SCF -> SRF The SCP requests the SRF to send information to, and collect user information from the user terminal. The SRF returns the collected information with the RESULT of the operation. . Associated operations: ConnectToResource DisconnectForwardConnection Cancel The SCF sends this operation as an intermediate response operation after sending the ConnectToResource operation. The SSP supports the operation in the same DPs as with the ConnectToResource operation.
. .

Comments:

Support in DPs:

About the use of this operation:


For the coding of the extensions, see ASN.1 definitions for extensions in Section Interface description: ASN definitions.

Parameters:
S NS supported not supported

Table 32. Parameter

Support for PromptAndCollectUserInformation operation parameters Nokia Siemens Networks' support


S S S S 2

Note number

collectedInfo disconnectFromIPForbidden informationToSend extensions languageID

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

91 (196)

DX MSC/SSP/IP - SCP Interface Specification

The collectedInfo.collectedDigits.voiceInformation and the collectedInfo.collectedDigits.voiceBack are not supported. The informationToSend.inbandInfo.messageID.text and the informationToSend.displayInformation are not supported.

About the use of the parameters:


.

collectedInfo . minimumNbOfDigits . maximumNbOfDigits The maximum number of collected digits the SSF can provide is 32. . endOfReplyDigit The SSF does not send the digit(s) defined by the endOfReplyDigit to the SCF. . cancelDigit . startDigit The SSF does not send the digit(s) defined by the startDigit to the SCF. . firstDigitTimeOut The maximum amount of waiting time for the first digit after the announcement part has been completed. The default is 30 seconds. . InterDigitTimeOut The default is 30 seconds. . errorTreatment . interruptableAnnInd . voiceInformation Not supported by the SSP. . VoiceBack Not supported by the SSP. disconnectFromIPForbidden
The function is the same as with the PlayAnnouncement operation.

informationToSend
The function is the same as with the PlayAnnouncement operation.

Extensions:

92 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

The criticality of every extension is IGNORE by default.


.

Extension: languageID
The function is the same as with the PlayAnnouncement operation.

Result:
The SRF returns the digits collected from the user to the SCF when the criteria for stopping to collect them are reached. The digits sent to the SCF, revealing what the subscriber has dialled, are as follows:

Table 33.

Digits, sent to the SCF, indicating what the subscriber has called digit sent to SCF
0 1 2 3 4 5 6 7 8 9 B C A F E D

digit dialled by subscriber


0 1 2 3 4 5 6 7 8 9 * # A B C D

Note that A, B, C, and D are not generally supported by mobile phones. Operation: ReleaseCall (RC)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

93 (196)

DX MSC/SSP/IP - SCP Interface Specification

Direction: Usage:

SCF -> SSF The SCF requests the SSF to release the call for all parties involved in the call. Note that this operation has a special function. When the SCF has set a limit for the call, and the SSF has been informed by the ACR operation that the limit has been reached, the SCF is allowed either to give a new limit or send a ReleaseCall operation regardless of the relationship type (controlling or monitoring).

Associated operations: None. Comments: The SCF sends this operation as a final response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 34. DP1


yes

SSP support for the ReleaseCall operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
yes

About the use of this operation:


The call is released immediately when a ReleaseCall is received, unless an announcement is provided by the SCF. The SSF sends the pending reports (the ApplyChargingReport) after receiving the ReleaseCall from the SCF, if the SCF has sent an RC in the TC-CONTINUE. Because there is no error component for this operation (class 4 operation), the SSF aborts the dialogue in an error case.

Parameters:

94 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

S NS

supported not supported

Table 35. Parameter

Support for the ReleaseCall operation parameter Nokia Siemens Networks' support
S

Note number

cause

About the use of the parameters:


.

cause
The cause value is mapped from the signalling to the DX internal form, according to the Mapping of External Data, Operating Instructions, INAP section. In the call set-up phase the CCF makes the End-Of-Selection (EOS) analysis for the cause received from the SCF. The actions to be taken depend on the analysis. For example, an announcement can be given to the calling subscriber before the release. In the speech phase a function analysis is made for the cause.

Operation: RequestNotificationChargingEvent (RNC) Direction: Usage: SCF -> SSF The SCF requests the SSF to report on the charging events coming from the network. The supported charging event types are the (Finnish) national ISUP messages MPM and CHG. Associated operations: EventNotificationCharging Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

95 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 36.

SSP support for the RequestNotificationChargingEvent operation in Detection Points DP4


yes

DP1
yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
no

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
no

DP17
yes

DP18
yes

spont
yes

About the use of this operation:


The operation is meaningful only if the network supports charging messages between the network elements. In the TBCSM the operation makes sense only in the G-TBCSM, where it is applicable only with the Continue operation. If the SCF sends a Connect message to the G-TBCSM, the SSF does not have any roaming charging going on, and the SSF does not send ENC reports to the SCF.

Parameters:
S NS supported not supported

Table 37.

Support for the RequestNotificationChargingEvent operation parameters Nokia Siemens Networks' support
S S NS 1

Parameter

Note number

eventTypeCharging monitorMode legID

The value 'interrupted' is not supported in the monitorMode parameter.

This operation does not contain any extension parameters.

96 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

About the use of the parameters:


.

eventTypeCharging
The SCF defines whether a report on charge pulses or charge messages is requested. The SCF can request the charge pulses or charge messages separately. If the SCF wants both of them, it must request them separately with different eventTypeCharging values.

monitorMode
Only the values 'notifyAndContinue' and 'transparent' are possible, that is, the SCF cannot control the network charging. It can only monitor it.

legID
The legID parameter is not used, but the SCF separates the calling subscriber, the forwarding subscriber, or the roaming subscriber charging cases based on the BCSM if the charging event is requested.

Operation: RequestReportBCSMEvent (RRB) Direction: Usage: SCF -> SSF The SCF requests the SSF to monitor a call-related event. If the SSF detects such an Event DP (EDP) during the call processing, it sends a response back to the SCF (EventReportBCSM). Associated operations: EventReportBCSM Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 38.

SSP support for the RequestReportBCSMEvent operation in Detection Points DP4


yes

DP1
yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

97 (196)

DX MSC/SSP/IP - SCP Interface Specification

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
no

About the use of this operation:


The SCF can arm only the OBCSM DPs as EDPs when it sends the RequestReportBCSMEvent to the OBCSM. The SCF can arm only the TBCSM DPs as EDPs when it sends the RequestReportBCSMEvent to the TBCSM. If the same DP is armed as an EDP several times, the DP is armed with the data of the last received RequestReportBCSMEvent operation. If the SSF finds an error in the operation, for example, the SCF tries to arm an illegal DP, it returns the error to the SCF. If several DPs are included in the operation, none of them is armed because of the error in one DP. In an error situation, the SSF returns to the SCF error codes as follows:
.

UnexpectedDataValue: The collectedInfoSpecificInfo for DP2 is out of range, the timer value for DP6/DP15 is out of range, the DP value is illegal, or no DP is provided at all.

Parameters:
S NS supported not supported

Table 39. Parameter

Support for the RequestReportBCSMEvent operation parameters Nokia Siemens Networks' support
S NS

Note number

bcsmEvents extensions

1 2

98 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

BCSMEvent.eventTypeBCSM DP values 1 and 12 are not sensible. The BCSMEvent. legID is not supported. No extensions have been defined for this operation.

About the use of the parameters:


.

bcsmEvents . eventTypeBCSM An error is returned to the SCF if there is an attempt to arm an illegal EDP. These are DP1 and DP12. . monitorMode . The interrupted message makes the relationship a controlling one, and prevents another SSF-SCF relationship to that BCSM. . If all DPs are notifyAndContinue, the relationship is a monitoring one, and other parallel SSF-SCF relationships are possible. . transparent disarms the DP. . legID This parameter is not read by the SSF. . dPSpecificCriteria: . The numberOfDigits criterion is used only in DP2, in other DPs it is neglected. . The applicationTimer indicates the alerting time in seconds, after which the No_Answer DP is encountered. The criterion is used only in DP6 and DP14. In other DPs it is neglected. The maximum value used for the applicationTimer is the normal no_answer timeout in the MSC. If the SCP gives the application timer to DP6, there is a re-answer timer both in the OBCSM and the TBCSM. If the time specified for the timer in the OBCSM is shorter than it is in the TBCSM, the expiration of the timer occurs first in the OBCSM.

Operation: ResetTimer (RT) Direction: Usage: SCF -> SSF The SCF requests the SSF to refresh the operation Tssf timer. Associated operations: None.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

99 (196)

DX MSC/SSP/IP - SCP Interface Specification

Comments: Support in DPs:

The SCF sends this operation as an intermediate response operation. The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 40. DP1


yes

SSP support for the ResetTimer operation in Detection Points DP4


yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
yes

DP10
yes

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
yes

DP18
yes

spont
no

About the use of this operation:


In an error situation, the SSF returns to the SCF error codes as follows:
.

UnexpectedComponentSequence: The SCF has sent more than one ResetTimer operation after InitialDP operation.

Parameters:
S NS supported not supported

Table 41. Parameter

Support for the ResetTimer operation parameters Nokia Siemens Networks' support
NS S NS

Note number

timerID timervalue extensions

1 2 3

100 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

1 2

The default value 'timerID = Tssf' is used. The maximum time that the SSF waits for the Final response operation from the SCF has been defined in the SSF. This value replaces the initial value of Tssf defined in MSC/SSP. No extensions have been defined for this operation.

About the use of the parameters:


.

timerID
The SSF always uses the default value 'Tssf' regardless of this parameter.

timervalue
The value is given in seconds. For the SCF timer reset, the following rules apply: . After receiving the InitialDP, only one ResetTimer operation is allowed; after that the SCF must send the response. In other cases several successive ResetTimer operations are allowed. . In the SRF-SCF relationship, the SCF can send the ResetTimer an unlimited number of times.

Operation: SendChargingInformation (SCI) Direction: Usage: SCF -> SSF The SCF requests the SSF to use certain charging criteria for the calling/forwarding or called party. Associated operations: None. Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table. 'Spont' means that the operation is allowed as a spontaneous operation outside any DP.

Table 42.

SSP support for the SendChargingInformation operation in Detection Points DP4


yes

DP1
yes

DP2
yes

DP3
yes

DP5
yes

DP6
yes

DP7
yes

DP8
yes

DP9
no

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

101 (196)

DX MSC/SSP/IP - SCP Interface Specification

DP10
no

DP12
yes

DP13
yes

DP14
yes

DP15
yes

DP16
yes

DP17
no

DP18
no

spont
no

About the use of this operation:


For the coding of the network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions. The operation is not accepted from the SCF if the charging is running. In that case the 'Task Refused' error component is returned. An exception is the case when the SCF has given a tariff for the user interaction. After the user interaction, when the charging has been stopped and the end of user interaction has been reported to the SCF, the SCF can override the previous tariff it has sent and give a new tariff for the actual call. If the SCF sends many SCI operations concerning the same function (zone/e-parameters is one and change percentage/pulses is another), the last one sent is valid. In an error situation the SSF returns error codes to the SCF as follows:
.

missingParameter: The SCF has provided neither zone nor eparameters, neither percentage change nor pulse addition in the SendChargingInformation operation. TaskRefused, generic: The charging is running when the SendChargingInformation operation is received.

If the charging zone provided by the SCF is unknown for the SSF, the SSF is not capable of noticing at once that the value is faulty. In this case, no error is returned. Instead, an alarm is generated later on in the MSC/SSP, when there is an attempt to use a faulty value for charging. If the e-parameters provided by the SCF are invalid, the SSF is not capable of returning an error to the SCF. The call is released later on when there is an attempt to use the parameters.

Parameters:
S NS supported not supported

102 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

Table 43. Parameter

Support for the SendChargingInformation operation parameters Nokia Siemens Networks' support
S NS NS 1

Note number

sCIBillingChargingCharacteristics legID extensions

No extensions have been defined for this operation.

About the use of the parameters:


.

sCIBillingChargingCharacteristics
The coding is network-specific. The DX 200 MSC/SSP supports the following data: . sCIChType: This parameter indicates the way the SCF uses to change the charging. . The ISUP message is not supported by the SSF. . Charging Level . Charging change percentage . Charging change pulses . e-parameters . withdrawPrecedingSCI: The SCF cancels the charging control that it has received previously from the SCI operation, for example, for user interaction only. The withdrawal is possible only in the same DP where the charging order was given. . sCIChValue . The mpm is not supported by the SSF. . The chg is not supported by the SSF. . charging zone The MSC/SSP uses the zone ordered by the SCF instead of the zone from the charging analysis. To be able to use this parameter, the SCF Service Logic Program must know the zones that exist in the controlling MSC/SSP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

103 (196)

DX MSC/SSP/IP - SCP Interface Specification

If a new charging zone is given, it replaces the previous charging zone or e-parameters given by the SCF without any notice to the SCF. If the charging zone provided by the SCF is unknown to the CCF, an alarm is generated in the MSC/SSP and a TC-ABORT message is sent to the SCF. changePercentage . direction Value 0 means 'increase', 1 means 'decrease'. . percentage With this parameter, the SCF can change the charging, determined by the MSC/SSP, by defining whether a reduction or premium rate is concerned, and the value for the percentage change. If the reduction is greater than 100%, the SSF uses the value 100%. (It means no charge.) The reduction percentage value can be over 100% in the protocol, but the function is the same for the 100-255% reduction. If a new percentage change is given, it replaces the previous pulse or percentage change given by the SCF without any notice to the SCF. During the call active phase in the Mid_Call DP, the percentage change affects the actual tariff. changePulses . direction Value 0 means 'increase', 1 means 'decrease'. The direction can only be 'increment', which is also the default value. The pulse reduction is not supported. . pulses With this parameter, the SCF can change the number of the charging units and the charging determined by the MSC/SSP, by defining whether a reduction or premium rate is concerned. If a new pulse change is given, it replaces the previous pulse or percentage change given by the SCF without any notice to the SCF. During a call active phase in the Mid_Call DP, the pulse change affects the actual tariff. The maximum amount of pulses for one call is 6500, including the SCF-given pulses and the network-generated pulses. eParameters

104 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

With this parameter, the SCF can change the charging determined by the MSC/SSP, by defining the eparameters that are used. The charging zone in the CDR is the value defined for that purpose in the MSC/SSP. If new e-parameters are given, they replace the previous charging zone e-parameters given by the SCF without any notice to the SCF. The SSF does not read or use the e-parameter.
.

legID
The parameter is not supported by the SSF. The charging control concerns the calling/forwarding party.

Operation: SpecializedResourceReport (SRR) Direction: Usage: SRF -> SCF The SRF returns the SpecializedResourceReport message to the SCF as a response after the announcement has been completed and the report indication has been set in the PA operation. Associated operations: PlayAnnouncement. The SRR is a linked operation to the PA. Support in DPs: The SSP supports the operation in the same DPs as with the operation PlayAnnouncement. Parameters: None.

4.4

MSC/SSP Core INAP configuration data


The MSC/SSP contains definitions that have influence on the IN Service activation or the SSF-SCF relationship. The data contains: PRFILE parameters: SSN_FOR_INAP_CS1 (026:013) The parameter defines the subsystem number (SSN) for INAP CS-1 signalling. With this parameter it is possible to configure different SSN for SCCP level Calling Party Address and SCCP level Called Party Address. The lowest two bytes define the SSN of the SCCP level Calling Party

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

105 (196)

DX MSC/SSP/IP - SCP Interface Specification

Address. The highest two bytes define the SSN of the SCCP level Called Party Address. If the highest two bytes are 0x00 then the lowest two bytes apply to both the SSN of the SCCP level Called Party Address and Calling Party Address.
.

DEFAULT_CHRG_ZONE (001:0044) This parameter is used when the SCF provides new e-parameters with the SendChargingInformation operation, but does not provide the zone to be used. This value is stored in the CDR as the zone value. Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.

INTERMEDIATE_CHARGING (001:0075) This parameter defines whether the intermediate charging is performed in various cases. If the intermediate CDR is generated, an intermediateApplyChargingReport is also sent to the SCF. If the CDR is not generated, no ACR is sent to the SCF either.

REC_PULSE_BUFFERING (001:0076)001:076 rec_pulse_buffering This parameter indicates when the MPM message has to be reported to the SCF by the ENC operation if the SCF has requested the report by the RNC operation. The possible values are the following: . Value 0: Sent immediately after the reception of pulses. . Other value: Sent after receiving the number of pulses indicated by the value and at the end of the call.

DEFAULT_CHRG_ZONE_B (001:0077) If the SCF provides new e-parameters with the SendChargingInformation operation for subscriber B charging in the TBCSM, but does not provide the zone to be used, this default value is stored in the CDR as the zone value. Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.

DEF_CHRG_ZONE_B_ROAM (001:0078)

106 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

If the SCF provides new e-parameters with the SendChargingInformation operation for subscriber B charging in the G-BCSM, but does not provide the zone to be used, this default value is stored in the ROAM CDR as the zone value. Note that to avoid confusion, this value should not be used as a normal zone value in the MSC.
.

SSF_FUNCTION_ON (002:0289) If this parameter is set to FALSE, no InitialDP operation is sent to any SCF. In this case, the calls are normal calls without an IN service. However, the ongoing IN calls are handled as IN calls, that is, ERB operations are sent.

SSF_DP_I_PREANALYZED (002:0419) This parameter defines whether DP2 is encountered before or after the pre-analysis. The default value TRUE means that DP2 is encountered after the pre-analysis. If the values are set to FALSE, DP2 is encountered before the preanalysis. Exception: If the SCF has sent the CollectInformation (CI) operation in DP1 and armed DP2 as EDP-R, the EDP2 encountering does not depend on the parameter at all, it is always met before the preanalysis.

INAP_AC_IN_USE (002:0446) If this parameter is set to FALSE, the Application Context is not used when a dialogue is invoked towards the SCF. The default is TRUE.

SCCP_SEGMENTATION (002:0447) If this parameter is set to the value TRUE, the SCCP level segmentation is used with the INAP. The default is FALSE.

CS1_LAST_OP_IN_TC_END (002:0599) If this parameter value is TRUE (default), the last operation (the ERB-N or the ACR) is sent in the TC_END message. If the value is FALSE, the last operation is sent in the TC_CONTINUE message.

IMPLICIT_DISARMING_CS1 (007:0106)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

107 (196)

DX MSC/SSP/IP - SCP Interface Specification

The parameter indicates whether or not the implicit disarming of events in the Core Intelligent Network Application Protocol Capability Set 1 (CoreINAP CS-1) is possible (as a default, implicit disarming is not used), see Feature 739: IN: CS-1 Core INAP, Feature Description, version 3.
.

SSF_MPC_ALLOWED (007:0108) The parameter generally states whether or not the multiple point of control principle in an Intelligent Network is available. The default value is 'FALSE', which means that as long as any controlling IN service is active, no new controlling IN service can be started.

SSF_MSDP_ALLOWED (007:0110) The parameter generally states whether multiple controlling IN services can be served in a single DP. The default value is FALSE, which means that only one controlling IN service (the EDP-R or the TDP-R) is allowed to be served in a single DP.

DEDICATED_IN_EVENT_CODE (007:0128) This parameter indicates whether or not the dedicated IN Event Codes are used for Connect operations. With the parameter value TRUE, the INAP Connect operation uses Event Code 1043. With value FALSE, the default Event Code 1028 is used.

CAMEL_ACTIVE (041:0002) The parameter controls whether the CAMEL functionality is ON (active) or OFF (inactive) in the network element (MSC/VLR, HLR). The parameter also indicates the CAMEL phase, either 1, 2, 3, or 4.

Fixed values for various limits: The maximum number of service activations (InitialDP operations) in one BCSM is 10. When the limit is reached, no new IN service is triggered, even if an armed trigger is encountered. Trigger Data: The trigger record contains the information for one triggering to the SCF. It includes the following data, which has an influence on the IN service activation or execution:

108 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

SKEY: ST:

PRT:

DP:

BCSM:

FOP:

AP: ND:

STRING:

The ServiceKey that is sent to the SCF in the InitialDP operation with the ServiceKey parameter. The Status of the Trigger. If the trigger is deactivated, that specific triggering does not take place and that the IN service is not initiated. It is possible that even in the same DP there is another active trigger that causes the initiation of an IN service. The Priority of the trigger. Defining several triggers to the same DP should be avoided because the service interaction is usually not able to foresee them in the SSF. If several triggers are defined, priority decides which service is started. If a service is triggered, the other triggers no longer cause triggering in the same DP visit. But they can cause triggering if the same DP is encountered again later on in the same call. DP defines the DP in which an IN Service must be triggered. Triggering in the proper DP is essential for many IN services. The type of the BCSM. This parameter indicates from which model the triggering takes place. For DPs 1...10, 'OBCSM' is the default and the only allowed value. For DPs 12...18, the default is 'TBCSM' and, in this case, the triggering takes place in the TBCSM in the Visited MSC/SSP. The other choice is 'GBCSM': the triggering then takes place in the TBCSM in the Gateway MSC/SSP. The value 'ANY' means that the triggering takes place both in the GBCSM and the TBCSM. If the SCF-SSF communication terminates in an error, the SCF is not aware of how the call continues. In this case, the way the call continues is determined by the SSF with the FailureOperation (FOP) information included in the trigger. AP specifies the used Application Protocol. The default value is INAP. Number of Digits: a trigger condition. It defines the minimum number of digits that has to be collected before the triggering to the SCF takes place. Digit String: a trigger condition. This triggering condition contains the Type of Number and 1 to 10 digits that are compared to the called party number. The triggering can take place if the trigger condition matches the called party number.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

109 (196)

DX MSC/SSP/IP - SCP Interface Specification

NOT_STRING:

Not Digit String: a trigger condition. This triggering condition contains the Type of Number and 1 to 10 digits, which are compared to the called party number. The triggering can take place if the trigger condition does not match the called party number.

CALLING_PARTY: CallinG Party: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if the TON or both of the trigger conditions match the calling party number. If the TON is the only criterion, the calling party number can be anything. NOT_CALLING_PARTY: Not CallinG Party: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if neither the TON nor any of the trigger conditions matches the calling party number. If the TON is the only criterion, the calling party number can be anything. VLR_ADDRESS: VLR address: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the VLR address. The triggering can take place if the TON or both of the trigger conditions match the VLR address. If the TON is the only criterion, the VLR number can be anything. The VLR address is always an international number. The VLR_ADDRESS trigger condition is valid only in the Gateway terminating BCSM. NOT_VLR_ADDRESS: Not VLR address: a trigger condition. This triggering condition contains the Type of Number and 0 to 10 digits, which will be compared to the calling party number. The triggering can take place if neither the TON nor any of the trigger conditions matches the VLR address. If the TON is the only criterion, the VLR number can be anything. The VLR address is always an international number. The NOT_VLR_ADDRESS trigger condition is valid only in the Gateway terminating BCSM. C1...C5: Cause value: a trigger condition. The triggering can take place if any of the defined cause values matches the cause of the clear code found in the call.

110 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

TIME:

OPER:

Time Out value: a trigger condition. It defines the time after which the triggering can take place. It is intended to be used in the 'No_Answer' DP. Criteria Operation. It indicates the logical operation that is used between the trigger criteria defined for a trigger. The possible values are 'AND' and 'OR'.

The following table summarises the possible uses of the Trigger Criteria listed above:
ND
TDP1 TDP2 TDP3 TDP4 TDP5 TDP6 TDP7 TDP8 TDP9 TDP10 Yes Yes Yes

STRING
yes yes yes yes yes yes yes yes yes yes

NOT STRING
yes yes yes yes yes yes yes yes yes yes

C1...C5

TIME

CGP
yes yes yes

NCGP
yes yes yes yes yes yes yes yes yes yes

VLR NVLR

yes yes yes yes

yes yes yes yes yes

yes yes

yes yes

Table 44. ND
TDP12 TDP13 TDP14 TDP15 TDP16 TDP17 TDP18

The possible uses of the Trigger Criteria NOT STRING


yes yes yes yes yes yes yes yes yes yes yes yes

STRING
yes yes yes yes yes yes yes

C1...C5

TIME

CGP
yes yes yes yes yes yes yes

NCGP
yes yes yes yes yes yes yes

VLR
yes yes yes yes yes yes yes

NVLR
yes yes yes yes yes yes yes

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

111 (196)

DX MSC/SSP/IP - SCP Interface Specification

AL:

SCP Address Location. This parameter indicates how the SCP address is determined. The possible values are 'T' = the GT address from the Trigger Data, 'A' = use the calling party address (or redirecting party address when available), and 'B' = use the called party address of the call.

Note that if in DP1 the Nature of Address of the GT address (derived from the B-number) is 'unknown', it is automatically converted to the 'subscriber' for the SCCP GT analysis. GTI: TT: GT: The Global Title Indicator parameter is used to select the SCCP analysis root. The Translation Type parameter is used to select the SCCP analysis root. If the AL parameter has the value 'T', this parameter contains the SCP address. With other AL parameter values, this parameter has no meaning. The address of the SCP where the InitialDP is sent is always in the Global Title format. The Numbering Plan parameter is used to select the SCCP analysis root. This parameter can only be used if the AL value is 'T'. The Nature of Address parameter is used to select the SCCP analysis root. This parameter can only be used if the AL value is 'T'. Use Application Context. This parameter indicates whether the Application Context is included in the TC INVOKE message when the IDP operation is sent to the SCP. By default, the AC is sent. The use of the AC can be denied by the INAP_AC_IN_USE (002:0446) PRFILE parameter, see MSC/SSP Core INAP configuration data. Short Timer. This time value is used as the initial value for the Tssf when the SSF-SCF relationship is started. Medium Timer. This time value is used as an initial value for the Tssf when the SRF-SCF relationship is started. Operation in a Multiple Point of Control environment. This parameter determines if the service can function in a multiple point of control environment.

NP:

NAI:

AC:

STMR:

MTMR:

OMPC:

112 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-related IN functions

STOC:

OMCS:

SEOC:

TD:

Starting of Other Controlling services. This parameter determines if the service restricts the starting of new controlling services in the same BCSM. Operation of Multiple Controlling Service requests in the same DP. This parameter determines if the service can be started if another controlling service has been served in the same DP before it. Serving of Other Controlling service requests in the same DP. This parameter determines if the service restricts the serving of other controlling services in the same detection point after the service itself has been served. Trigger Deactivation. This parameter determines if the lifetime of the trigger can be restricted with the FIM mechanisms.

MSC software release information to SCP The MSC software release information is packed to the TC Begin towards the SCP. This functionality allows the SCP to detect the dialogue initiator capabilities, for example, during the software upgrade phase. The TC Begin DialoguePortition dialogueRequest user information field carries the MSC software release information coded as follows: SwRelease ::= IA5String (SIZE(2...10)) m14 SwRelease ::= '4D3134'H

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

113 (196)

DX MSC/SSP/IP - SCP Interface Specification

114 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

5
5.1
5.1.1

Interface description: Call-unrelated IN functions


Specifications and terminology
Related specifications
The SSF-SCF Interface descriptions are based on the ETS 300 374-1: Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 1: Protocol specification, September 1994. All the restrictions and inconsistencies presented in this document, if not stated otherwise, refer to that specification. The call-unrelated functions use the same Core INAP as the call-related cases. This implementation is Nokia Siemens Networks-specific. More information about the use of the INAP operations in each feature can be found in the respective feature documentation. For more information, see Feature 742: IN: Mobility Management, Feature Description, Feature 911: IN: Supplementary Service Management, Feature Description, and Feature 910: IN: Short Message Service, Feature Description. The following Application Contexts of the ETSI CS-1 Core INAP are supported:
.

Core-INAP-CS-SSP-to-SCP-AC, dialogue initiated by the SSP with InitialDP. Core-INAP-CS1-SCP-to-SSP-traffic-management-AC, dialogue initiated by the SCP with CallGap.

5.1.2

Terminology
The remark for an operation contains the following terms:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

115 (196)

DX MSC/SSP/IP - SCP Interface Specification

Intermediate response: After receiving an InitialDP operation, the SCF sends back one or more operations to the SSF. All other operations but the last one are intermediate responses, which do not allow the location registration to proceed. Final response: The last response operation from the SCF to the SSF is the final response, which allows the location registration to proceed according to the state model and the SCF response. After the final response, the SSF does not accept intermediate responses in that DP any more. Spontaneous operation: The SCF can send a spontaneous operation any time during the dialogue with the SSF. The parameter table contains the indication of the support of the parameters and possibly a reference to an explaining note.

5.2
5.2.1

IN mobility management
IN mobility management procedures
DPs have been inserted into the location registration procedures. Only the request-type trigger DPs (TDP-R) are supported. When a TDP is met, the SSF contacts the SCF, and suspends the processing of the location update. DPs are included in the following transactions:
.

inter-VLR location update (the subscriber changes the VLR area) intra-VLR location update (the subscriber changes the location area, but remains in the same VLR area) IMSI attach periodic location registration

DPs can be located with the help of a state model. Three separate mobility management state models have been defined for the location registration procedure: two in the VLR and one in the HLR. For more information, see Feature 742: IN: Mobility Management, Feature Description.

116 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

5.2.2

Mobility management state model in the VLR


The VLR functionality in Mobility Management state models has the following states:

Table 45.

The states of the VLR functionality in Mobility Management State Models


The subscriber data of the subscriber is not available in the VLR. The location registration attempt triggers a location update towards the HLR. The subscriber data is available in the VLR. The subscriber can actively use the network, for example, by initiating or receiving calls. The subscriber data is available in the VLR. The registration attempt is denied from the subscriber. The subscriber cannot actively use the network, for example, by initiating or receiving calls before a successful location registration.

Non-Registered

Registered, Attached Registered, Barred

The Mobility Management State Model in the VLR consists of two independent models:
.

Inter-VLR location registration Mobility Management state model Intra-VLR location registration Mobility Management state model

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

117 (196)

DX MSC/SSP/IP - SCP Interface Specification

Inter-VLR location registration state model

NON-REGISTERED

Inter-VLR Location Update & Authentication

MM-DP1 Subscriber Data Transfer

MM-DP2 Location Registration Completion

REGISTERED, ATTACHED

REGISTERED, BARRED

MM-DP1: PLMN-Specific-LocUp-Detection-Point MM-DP2: Inter-VLR-LocUp-Detection-Point

Figure 6.

Mobility Management State Model in the VLR for inter-VLR location registration

MM-DP1 PLMN-specific-LocUp-DP
This DP is intended for roaming subscribers. The MM-DP1 is PLMNspecific, that is, it can be set for all or no subscribers of a foreign network. It can also be armed for home subscribers, but it is not recommended because of possible overload problems. For home subscribers, the MM-DP4 in the HLR/SSP offers the same functionality as the MM-DP1 for roaming subscribers. Location registration is initiated by the MS. The subscriber is roaming to another VLR area and carries out the inter-VLR location registration. The authentication is carried out, but the location registration to the HLR is not started yet. The SSF starts the transaction towards the SCF. The result of the request is one of the following:

118 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

1. 2.

The location registration is accepted by the SCF. The location registration is rejected by the SCF. The VLR passes the reject cause to the MS and acts according to the reject cause (registered, barred/non-registered).

MM-DP2 Inter-VLR-LocUp-DP
The MM-DP2 is subscriber-specific. The subscriber data indicates whether the DP is armed or not. The subscriber data is transferred to the VLR, and the HLR accepts the registration. The success of the registration attempt is not yet indicated to the Mobile Station. Optionally, an IMEI checking is carried out. The SSF starts the transaction towards the SCF. The result of the request is one of the following: 1. The location registration is accepted by the SCF. 2. The SCF sends the charging information (FCI) to the SSF and accepts the location registration. 3. The location registration is rejected by the SCF. The VLR passes the reject cause to the MS and acts according to the reject cause (registered, barred/non-registered).

Intra-VLR location registration state model

REGISTERED ATTACHED

NON-REGISTERED

REGISTERED, BARRED

Intra VLR Location Update & Authentication

MM-DP3 Location Registration Completion

MM-DP3: Intra-VLR-LocUp-Detection-Point

Figure 7.

Mobility Management State Model in the VLR for intra-VLR location registration

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

119 (196)

DX MSC/SSP/IP - SCP Interface Specification

MM-DP3 Intra-VLR-LocUp-DP
The MM-DP3 is subscriber-specific. That is, the subscriber data indicates whether the DP is armed or not. The intra-VLR location registration is initiated by the MS. If the subscriber was not registered in the VLR (for example, after a VLR cleaning or a reset), the subscriber data is retrieved from the HLR. The authentication is completed. The MS has not yet indicated the success of the registration attempt. As an option, an IMEI checking is carried out. The SSF starts the transaction towards the SCF. The result of the request is one of the following: 1. The location registration is accepted by the SCF. 2. The SCF sends the charging information (FCI) to the SSF and accepts the location registration. 3. The location registration is rejected by the SCF. The VLR passes the reject cause to the MS and acts according to the reject cause (registered, barred/non-registered).

5.2.3

Mobility management state model in the HLR

IDLE

Inter-VLR LocUp & Subscriber Data Check

MM-DP4 Subscriber Data Transfer

MM-DP4: HLR-LocUp-Detection-Point

Figure 8.

Mobility Management state model in the HLR

MM-DP4 HLR-LocUp-DP

120 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

The MM-DP4 is subscriber specific. The Inter-VLR location registration is received from the new VLR. The IMSI is known by the HLR. The HLR checks whether the subscriber is allowed to roam in the area in question or not. It is also checked that the old VLR address in the database and the new VLR address received in the location registration attempt are not the same, as they could be after a VLR cleaning or a reset. The subscriber data transfer to the new VLR has not been started yet. The SSF starts the transaction towards the SCF. The result of the request is one of the following: 1. The location registration is accepted by the SCF. The HLR stores the new VLR address to the subscriber data. The subscriber data transfer to the new VLR and the cancel location procedure towards the old VLR are started. 2. The location registration is rejected by the SCF. The reject cause received from the SCF is passed to the VLR. The VLR address is removed from the subscriber data.

5.2.4

SCP load control


The IN Mobility Management supports the use of INAP CallGap operations by means of the SCP load control.

5.2.5

Support of Core INAP operations in IN mobility management


The SCF-SSF operations defined by the Core INAP specification are presented in Table Support for SSF - SCF Core INAP operations in IN Mobility Management. For more information, see also ETS 300 374-1. The indication whether the implementation of the DX 200 MSC/SSP supports the operation in the Mobility Management DP in the HLR or in the VLR is marked with: S NS supported not supported

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

121 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 46.

Support for SSF - SCF Core INAP operations in IN Mobility Management Note

Core INAP Operation

Nokia Siemens Nokia Siemens Nokia Siemens Networks' Networks' Networks' support in the support in the support in the Intra-VLR HLR location Inter-VLR location registration state location registration state registration state model model model
S S S S S S S S S S S S NS S S

CallGap Continue FurnishChargingInformati on InitialDP ReleaseCall

Extensions have been specified for the operation.

The SSF is not capable of sending an unsupported operation to the SCF. If a not supported operation is received from the SCF, the SSF neglects the operation and aborts the conversation. If an operation outside the Core INAP application context is received, the operation is rejected.

5.2.6

Support of Core INAP parameters in IN mobility management


This section presents support for the parameters of Core INAP operations, including restrictions and inconsistencies with ETS 300 374-1. Operation: CallGap (CG) Direction: Usage: SCF SSF The SCF may request the SSF to reduce the rate at which specific service requests are sent to the SCF. Associated operations: None. Comments: The SCF sends this operation as a standalone spontaneous operation. Support in DPs: The operation does not depend on any DP.

About the use of this operation:

122 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

With this operation, the SSF uses the pre-arranged end method. No response is sent to the SCF, and the SSF-SCF relationship is locally ended.

Parameters:

Table 47. Parameter

Support for the CallGap operation parameters Nokia Siemens Networks' support
S S S S NS 3 4

Note

gapCriteria gapIndicators controlType gapTreatment extensions

1 2

1 2

3 4

Only the gapOnService is supported. The duration is indicated in seconds. Values -1 (=infinite duration) and -2 (network-specific duration) are not supported. The gapInterval is indicated in milliseconds. The resolution is 10 ms. Only the releaseCause is supported. No extensions have been defined for this operation.

About the use of the parameters:


.

gapCriteria
The gapOnService compares the ServiceKey defined in the trigger data and the ServiceKey given by the SCF in the CallGap operation.

gapIndicators

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

123 (196)

DX MSC/SSP/IP - SCP Interface Specification

Duration: If the SCF sends the value -1 or -2, the operation is discarded. But as the operation contains no result and no response operation exists, the SSF cannot indicate the case to the SCF. The SCF may check the existence of the call gapping by reading the cGEncountered parameter in the InitialDP operation. gapInterval: The resolution 10 ms means that the value received from the SCF in milliseconds is divided by ten to form the interval. The SCF must give a value greater than 9 because values 0-9 give interval=0 and the gapping is not activated.

controlType . sCPOverload . manuallyInitiated: ManuallyInitiated has higher priority, so it replaces the previous gapping with the same criteria. A CallGap with sCPOverload is discarded if there is an active gapping with the same criteria and with controlType=manuallyInitiated. gapTreatment . releaseCause: The cause code provided by the SCF has no effect in the MSC/SSP. If the SCP contact attempt is gapped, an IN-specific internal cause is used for statistics. For the cause value, see the Mapping of External Data, Operating Instructions, INAP section.

Operation: Continue (CUE) Direction: Usage: SCF SSF The SCF requests the SSF to continue the processing from the DP where it was suspended because of the SCF inquiry. Associated operations: None. Comments: The SCF sends this operation as a final response operation. Support in DPs: The SSP supports the operation in the DPs as indicated in the following table.

Table 48.

SSP support for the Continue operation in the Detection Points MM-DP2
yes

MM-DP1
yes

MM-DP3
yes

MM-DP4
yes

124 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

About the use of this operation:


With this operation, the SCP allows the location updating procedure to continue normally.

Parameters: None.
Operation: FurnishChargingInformation (FCI) Direction: Usage: SCF SSF The SCF gives the SSF charging-related information, which the SSF includes in the Call Detail Records (CDRs). The SCF sends this operation as an intermediate response. The SSP supports the operation in the DPs as indicated in the following table:

Comments: Support in DPs:

Table 49.

SSP support for FurnishChargingInformation operation in the Detection Points MM-DP2


yes

MM-DP1
no

MM-DP3
yes

MM-DP4
no

About the use of this operation:


For the coding of network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions. One FurnishChargingInformation operation or several successive operations, depending on the controlInformation parameter, create an IN CDR in the MSC. The generated IN CDRs are stored in the related basic CDR, for example, in the LOCA CDR. In an error situation, the SSF returns to the SCF error codes as follows:
.

UnexpectedComponentSequence: The operation is received when waiting for a new limit from the SCF (after the previous limit has expired). UnexpectedDataValue: The ControlInfo is out of range. TaskRefused: The SCF requested a CDR generation that is not possible.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

125 (196)

DX MSC/SSP/IP - SCP Interface Specification

Parameters:

Table 50. Parameter

Support for the FurnishChargingInformation operation parameter Nokia Siemens Networks' support
S

Note

fCIBillingChargingCharacteristics

About the use of the parameters:


.

fCIBillingChargingCharacteristics
The coding is network-specific. The IN Mobility Management SSF in the VLR supports the following data: . controlInformation: Using this parameter, the SCF can request the SSF to process the IN-CDR as follows: add a new IN service information element or add data into an existing element. The SCF can use the following values: . 00'H: Start generating a new IN CDR and store the previous one. . 02'H: If there is no IN CDR open, start generating a new CDR, leave it open, and store the previous IN CDR. If there is already an open IN CDR, append the data into the IN CDR and leave it open. The maximum number of FCI operations for one IN CDR is 5. . 01'H: If there is no IN CDR open, start generating a new IN CDR and close it. Store the previous IN CDR. If there is already an open IN CDR, append the data into the IN CDR and close it. If the SCF uses other values than specified, the SSF returns the error 'UnexpectedDataValue'. . serviceInformationLength This parameter indicates the amount of octets that the serviceInformation contains. The value must be in the 0...310 (decimal) range. The SSF does not read the length from this parameter, but calculates it from the length of the received FCI operation. . serviceInformation With this parameter, the SCF can give extra instructions to the billing system.

126 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

It contains charging data for the billing system provided by the SCF. For the SSF, it is transparent data which has no influence on the charging functionality in the SSP. The coding of serviceInformation must be agreed between the SCF Service Logic Program and the Billing Center. The SSF copies this octet string into the IN CDR for the billing system. Operation: InitialDP (IDP) Direction: Usage: SSF SCF The SSF requests the SCF for service when it detects an active trigger in a TDP. Associated operations: None. Comments: The location registration procedure is stopped until the final response from the SCF is received. Support in DPs: The SSP supports the operation in the DPs as indicated in the table below.

Table 51.

SSP support for the InitialDP operation in the Detection Points MM-DP2
yes

MM-DP1
yes

MM-DP3
yes

MM-DP4
yes

About the use of this operation:


For the coding of the extension, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. The InitialDP is sent to the SCF when:
.

The SSF functionality is active in the SSP. An armed TDP is encountered. The INAP protocol handler is able to deliver the operation through the TC.

Note that when the SSF leaves the TDP, it is disarmed regardless of whether the triggering has taken place or not.

Parameters:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

127 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 52. Parameter

Support for the InitialDP operation parameters Nokia Siemens Networks' support
S S S S 1

Note

serviceKey calledPartyNumber CGEncounered extensions iMSI iMEI gSMSupplementaryServiceList mSRoamingStatus oDB-info msClassmarks gSMLocationOnformation mM-EventType transactionType vLRAddress hLRAddress

The subscriber's MSISDN number from the database - a maximum length of 15 digits.

About the use of the parameters:


.

serviceKey
This parameter contains the value of the SKey in the subscriber data.

calledPartyNumber
This parameter contains the MSISDN of the subscriber making the location registration attempt. It identifies the service requested from the SCP together with the SKey.

cGEncountered

128 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

This parameter is sent if there is a call-gapping active for the ServiceKey, but the triggering is not gapped. With this information, the SCF can check if the CallGap operation has been successfully processed in the SSF.

Extensions:
The criticality of every extension is IGNORE.
.

Extension: iMSI
The SSF passes the IMSI of the mobile subscriber trying to make a location update. It is acquired from the VLR or the HLR database, or from the MS itself.

Extension: iMEI
The SSF passes the IMEI of the subscriber making the location registration attempt, if available. It is received from the MS.

Extension: gSMSupplementaryServiceList
With this extension, the SSF gives the SCF information about the active GSM Supplementary Services of the Mobile Subscriber. With the information, the SCF Service Logic Program can control the interactions between the IN and the GSM Supplementary Services. The data related to the primary basic service is used in the HLR. In the VLR, the data related to the teleservice T11 is used if available.

Extension: mSRoamingStatus
It indicates whether the subscriber is roaming in the home network or home country, or not.

Extension: oDBInfo
With this extension, the SSF gives the SCF information about the GSM Operator Determined Barring, that is, whether the operator determined barring supplementary service is active or not.

Extension: msClassmarks
With this extension, the SSF sends to the SCF the Mobile Station Classmark 1, if available. Classmark 1 (other classmarks are used for other purposes) is an optional parameter. It is sent to the SCF if received from the MS.

Extension: gSMLocationInformation

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

129 (196)

DX MSC/SSP/IP - SCP Interface Specification

With this extension, the SSF sends the old and new location information (CGIs) of the MS to the SCF. The location information of the subscriber making the location updating attempt can be found in the cell global identities of the new and old cell of the subscriber (parameter contents: location (new cell) = Location Area Code + Cell Identity, oldLocation (old cell) = Mobile Country Code + Mobile Network Code + Location Area Code). The information is received from the MS.
.

Extension: mM-EventType
This parameter identifies the DP at which the triggering was done and the IDP message that was sent. The following values are reserved: . plmnSpecificlocup 1 . interVLRLocup 2 . intraVLRLocup 3 . hLRLocup 4

Extension: transactionType
It indicates whether the transaction is a normal location registration, a periodic location registration, or an IMSI attach. The possible values are (integer 0...255): . Normal location registration 1 (MM-DP1, MM-DP2, MM-DP3) . IMSI attach 2 (MM-DP3) . Periodic location registration (MM-DP3)

Extension: vLRAddress
The ISDN address string of the new VLR of the subscriber. The numbering plan is E.164. In the HLR, this is a new VLR address.

Extension: hLRAddress
The ISDN address string of the HLR of the subscriber. The numbering plan is E.164.

Operation: ReleaseCall (RC) Direction: Usage: SCF SSF The SCF requests the SSF to reject the location updating attempt. A reject cause is sent to the SSF, which is then forwarded to the MS. Associated operations: None.

130 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

Comments: Support in DPs:

The SCF sends this operation as a final response operation. The SSP supports the operation in the DPs as indicated in the following table.

Table 53.

SSP support for the ReleaseCall operation in the Detection Points MM-DP2
yes

MM-DP1
yes

MM-DP3
yes

MM-DP4
yes

About the use of this operation:


This operation is used to reject the location registration attempt. The cause value is forwarded to the MS.

Parameters:

Table 54. Parameter

Support for the ReleaseCall operation parameter Nokia Siemens Networks' support
S

Note

cause

About the use of the parameters:


.

cause
The value includes the mobility management causes. Value 7C is reserved for call-unrelated functionalities, and the additional cause value in the diagnostics field of the parameter indicates the Mobility Management reason. The additional IN Mobility Management cause values are the following:

Table 55.

Additional IN Mobility Management cause values


0x1; 0x8; 0x9;

Unknown Subscriber Roaming Not Allowed (PLMN Not Allowed) Illegal MS

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

131 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 55.

Additional IN Mobility Management cause values (cont.)


0x22; 0x29 0xf0;

System Failure LA Not Allowed National Roaming Not Allowed in this LA

5.3
5.3.1

IN supplementary service management


IN supplementary service management procedures
One DP has been inserted into the supplementary service management procedures. One request-type trigger DP (TDP-R) is supported. When the TDP is met, the SSF contacts the SCF, and suspends the processing of the supplementary service management request. The DPs can be located with the help of a state model. The state model for the supplementary service management procedure is defined in the HLR.

O_Null & Receive_SS_Request

SS-DP1

SS-Management

Complete_SS_Request

Figure 9.

SS-DP1: SS management

5.3.2

Support of Core INAP operations in IN supplementary service management


The SCF-SSF operations defined by the Core INAP specification are presented in Table Mobility Management state model in the VLR for the inter-VLR location registration. For further information, see ETS 300 374-1 . The indication whether the implementation of the SSP supports the operation in the Supplementary Service DP in the HLR is marked with:

132 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

S NS

supported not supported

Table 56.

Support for SSF - SCF Core INAP operations in the Supplementary Service State Model Nokia Siemens Networks' support in Supplementary Service Management state model
S S S S 1

Core INAP Operation

Note

Connect Continue InitialDP ReleaseCall

Extensions have been specified for the operation.

The SSF is not capable of sending an unsupported operation to the SCF. If a not supported operation is received from the SCF, the SSF ignores the operation and aborts the conversation. If an operation outside the Core INAP application context is received, the operation is rejected.

5.3.3

Support of Core INAP parameters in IN supplementary service management


This section describes support for parameters of Core INAP operations, including the restrictions and inconsistencies relating to ETS 300 374-1. Operation: Connect (CON) Direction: SCF SSF Usage: The SCF changes the forwarded-to-number. Associated operations: None. Comments: The SCF sends this operation as a final response operation.

About the use of this operation:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

133 (196)

DX MSC/SSP/IP - SCP Interface Specification

With this operation, the SCP changes the forwarded-to-number which the subscriber tries to register.

Parameters:

Table 57. Parameter

Support for the Connect operation parameter Nokia Siemens Networks' support
S

Note

destinationRoutingAddress

About the use of the parameters:


.

destinationRoutingAddress
It indicates the changed forwarded-to-number, which is stored in the HLR database.

Operation: Continue (CUE) Direction: Usage: SCF SSF The SCF requests the SSF to continue the processing from the DP where it was suspended because of the SCF inquiry. Associated operations: None. Comments: The SCF sends this operation as a final response operation.

About the use of this operation:


With this operation, the SCP allows the supplementary service management procedure to continue normally. Parameters: None.

Operation: InitialDP (IDP) Direction: Usage: SSF SCF The SSF requests service from the SCF when it detects an active trigger in a TDP.

134 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

Associated operations: None. Comments: The supplementary service management procedure is stopped until the final response from the SCF is received.

About the use of this operation:


For the coding of the extension, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. The InitialDP is sent to the SCF, when:
.

The SSF functionality is active in the HLR/SSF. An armed TDP is encountered. The INAP protocol handler is able to deliver the operation through the TC.

Note
When the SSF leaves the TDP, it is disarmed regardless of whether the triggering took place or not.

Parameters:

Table 58. Parameter

Support for InitialDP operation parameters Nokia Siemens Networks' support


S S S

Note

serviceKey callingPartyNumber extensions iMSI sS-Code ext-BasicServiveCode mAPOperationCode forwardedToNumber mM-EventType

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

135 (196)

DX MSC/SSP/IP - SCP Interface Specification

About the use of the parameters:


.

serviceKey
This parameter contains the value of the SKey in the subscriber data.

callingPartyNumber
It contains the Primary MSISDN of the subscriber making the supplementary service management request from the HLR database. It identifies the service requested from the SCP together with the SKey.

Extensions:
The criticality of every extension is IGNORE.
.

Extension: iMSI
The IMSI of the subscriber making the supplementary service management attempt is received from the MS.

Extension: sS-Code
It specifies the supplementary service related to the SS management request. It is received from the MS.

Extension: ext-BasicServiceCode
It specifies the basic service related to the supplementary service. It is received from the MS.

Extension: mAPOperationCode
It specifies the request type, that is, the SS operation. It is received from the MS.

Extension: forwardedToNumber
It specifies the forwarded-to-number the subscriber tries to register. It is received from the MS.

Extension: mM-EventType
It identifies the DP at which the triggering was done. The following value has been reserved: . value 7 indicated in the SS-DP1

Operation: ReleaseCall (RC)

136 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

Direction: Usage:

SCF SSF The SCF requests the SSF to reject the locationupdating attempt. A reject cause is sent to the SSF, which is then forwarded to the MS. Associated operations: None. Comments: The SCF sends this operation as a final response operation.

About the use of this operation:


This operation is used to reject the supplementary service management transaction.

Parameters:

Table 59. Parameter

Support for the ReleaseCall operation parameter Nokia Siemens Networks' support
S

Note

cause

About the use of the parameters:


.

cause
Value 7C is reserved for the call-unrelated functionalities. The additional cause value in the diagnostics field of the parameter is not used.

5.4
5.4.1

IN Short Message Service


IN Short Message Service procedures
There are two Short Message Service State Models defined in the VMSC: the Mobile-originating and the Mobile-terminating State Model. The Mobile-originating State Model includes three DPs, a TDP for triggering, and EDPs for successful and failure delivery cases. The Mobileterminating State Model includes four DPs, two TDPs for triggering, SMS-

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

137 (196)

DX MSC/SSP/IP - SCP Interface Specification

DP2 for triggering in short message DELIVER cases, SMS-DP3 for triggering in status REPORT cases, and EDPs for successful and failure delivery cases. When a TDP is met, the SSF contacts the SCF, and suspends the processing of the short message.

O_Null & Authorize_Receive_SMS

MO-SMS

SMS-DP1 Forward_SMS

SMS_Failure SMS-DP5

SMS_Successful

SMS-DP7

Figure 10.

Mobile-Originating Short Message Service State Model

T_Null & Authorize_Receive_SMS

MT-SMS

SMSDP2

SMSDP3

SMS_Failure SMS-DP13

Page & Authorize & Send_SMS

SMS_Successful

SMS-DP15

Figure 11.

Mobile-Terminating Short Message Service State Model

138 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

5.4.2

Support of Core INAP operations in IN Short Message Service


The SCF-SSF operations defined by the Core INAP specification are presented in the table below. For further information, see ETS 300 374-1 . The indication whether the operation is supported in the SMS-BCSMs in the VMSC is marked with: S NS supported not supported

Table 60.

Support for SSF - SCF Core INAP operations in the Short Message Service State Models Nokia Siemens Networks' support in the MT-SMS state model
S S S S S S S S 1 1

Core INAP operation

Nokia Siemens Networks' support in the MO-SMS state model


S S S S S S S S

Note

CallGap Connect Continue FurnishChargingInformati on InitialDP ReleaseCall RequestReportBCSMEve nt EventReportBCSM

Extensions have been specified for the operation.

The SSF is not capable of sending an unsupported operation to the SCF. If a not supported operation is received from the SCF, the SSF ignores the operation, and aborts the conversation. If an operation outside the Core INAP application context is received, the operation is rejected.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

139 (196)

DX MSC/SSP/IP - SCP Interface Specification

5.4.3

Support of Core INAP parameters in IN Short Message Service


This information describes support for parameters of Core INAP operations, including the restrictions and inconsistencies with ETS 300 374-1. Operation: CallGap (CG) Direction: Usage: SCF SSF The SCF can request the SSF to reduce the rate at which specific service requests are sent to the SCF. Associated operations: None. Comments: The SCF sends this operation as a stand-alone, spontaneous operation. Support in DPs: The operation does not depend on any DP.

About the use of this operation:


In this operation, the SSF uses the pre-arranged end method. No response is sent to the SCF, and the SSF-SCF relationship is locally ended.

Parameters:

Table 61. Parameter

Support for the CallGap operation parameters Nokia Siemens Networks' support
S S S NS NS 3 4

Note

gapCriteria gapIndicators controlType gapTreatment extensions

1 2

1 2

Only the gapOnService is supported. The duration is indicated in seconds. Values -1 (=infinite duration) and -2 (network-specific duration) are not supported. The gapInterval is indicated in milliseconds. The resolution is 10 ms.

140 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

3 4

Only the releaseCause is supported. No extensions have been defined for this operation.

About the use of the parameters:


.

gapCriteria
The gapOnService compares the ServiceKey defined in the subscriber data and the ServiceKey given by the SCF in the CallGap operation.

gapIndicators . Duration: If the SCF sends the value -1 or -2, the operation is discarded. But as the operation contains no result and no response operation exists, the SSF cannot indicate the case to the SCF. The SCF can check the existence of the call gapping by reading the cGEncountered parameter in the InitialDP operation. . gapInterval: The resolution 10 ms means that the value received from the SCF in milliseconds is divided by ten to form the interval. The SCF must give a value greater than 9, because the values 0-9 give interval=0, and the gapping is not activated. controlType . sCPOverload . manuallyInitiated has higher priority, so it replaces the previous gapping with the same criteria. A CallGap with sCPOverload is discarded if there is an active gapping with the same criteria and with controlType=manuallyInitiated. gapTreatment releaseCause:
The cause code provided by the SCF has no effect in the MSC/SSP. If the SCF contact attempt is gapped, an IN-specific internal cause is used for statistics. For the cause value, see the Mapping of External Data, Operating Instructions, INAP section.

Operation: Connect (CON) Direction: Usage: SCF SSF The SCF changes the destination of the short message
.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

141 (196)

DX MSC/SSP/IP - SCP Interface Specification

Associated operations: None. Comments: The SCF sends this operation as a final response operation. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

Table 62. SMS DP1 SMS DP2


yes yes

SSF support for the Connect Operation in Detection Points SMS DP5
no

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

About the use of this operation:


With this operation, the SCF may change the destination address, both the SMSC address and subscriber B's address, to the address where the short message was originally sent. Also, the header information of the short message can be changed.

Parameters:

Table 63. Parameter

Support for the Connect operation parameters Nokia Siemens Networks' support
S S

Note

destinationRoutingAddress extensions serviceCentreAddress sm-RP-UIHeader

The parameter is coded according to ITU-T Q.763 Signalling System No. 7 - ISDN User Part Formats and Codes, December 1999, because the parameter is Mandatory in the protocol.

About the use of the parameters:


.

destinationRoutingAddress

142 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

This parameter is not used in the SSF because the routing address is included in the sm-RP-UIHeader.

Extensions:
The criticality of every extension is IGNORE.
.

Extension: serviceCentreAddress
Changed SMSC address. It indicates the SMSC address where the MO short message is sent.

Extension: sm-RP-UIHeader
Header of the following SM TL layer PDUs: . SMS DELIVER, conveying a short message from the SMSC to the MS. . SMS SUBMIT, conveying a command from the MS to the SMSC. . SMS COMMAND, conveying a command from the MS to the SMSC. . SMS REPORT, conveying a report from the SMSC to the MS.

Operation: Continue (CUE) Direction: Usage: SCF SSF With this operation, the SCF allows the short message service procedure to continue as normal. Associated operations: None. Comments: The SCF sends this operation as a final response operation. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

Table 64. SMS DP1 SMS DP2


yes yes

SSF support for the Continue operation in Detection Points SMS DP5
no

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

Parameters:
None.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

143 (196)

DX MSC/SSP/IP - SCP Interface Specification

Operation: FurnishChargingInformation (FCI) Direction: Usage: Comments: Support in DPs: SCF SSF The SCF gives the SSF charging-related information, which the SSF includes in the CDRs. The SCF sends this operation as an intermediate response. The SSF supports the operation in the DPs as indicated in the following table.

Table 65.

SSF support for the FurnishChargingInformation operation in Detection Points SMS DP5
no

SMS DP1 SMS DP2


yes yes

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

About the use of this operation:


For the coding of the network-specific parameters, see ASN.1 definitions for operation data types in Section Interface description: ASN definitions.

Parameters:

Table 66. Parameter

Support for the FurnishChargingInformation operation parameter Nokia Siemens Networks' support
S

Note

FCIBillingChargingCharacteristics

About the use of the parameters:


.

fCIBillingChargingCharacteristics
The coding is network-specific. The DX 200 MSC/SSP supports the following data: . controlInformation Using this parameter, the SCF can request the SSF to add a new IN service information element to the IN-CDR.

144 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

serviceInformationLength It indicates the number of octets that the serviceInformation contains. The value must be in the range 0...310 (decimal). The SSF does not read the length from this parameter, but calculates it from the length of the received FCI operation. serviceInformation It contains charging data for the billing system provided by the SCF. For the SSF it is transparent data, which has no influence on the charging functionality in the SSP. With this parameter, the SCF can give extra instructions for the billing system. The coding of the serviceInformation must be agreed between the SCF Service Logic Program and the Billing Center. The SSF copies this octet string into the IN CDR for the billing system.

Operation: InitialDP (IDP) Direction: Usage: SSF SCF The SSF requests the SCF for service when it detects an active trigger in a TDP. Associated operations: None. Comments: The short message service procedure is stopped until the final response from the SCF is received. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

Table 67. SMS DP1 SMS DP2


yes yes

SSF support for the InitialDP operation in Detection Points SMS DP5
no

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

About the use of this operation:


For the coding of the extension, see ASN.1 definitions for extensions in Section Interface description: ASN definitions. The InitialDP is sent to the SCF when:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

145 (196)

DX MSC/SSP/IP - SCP Interface Specification

The SSF functionality is active in the SSP. An armed TDP is encountered. The INAP protocol handler is able to deliver the operation through the TC.

Parameters:

Table 68. Parameter

Support for the InitialDP operation parameters Nokia Siemens Networks' support
S S S S S

Note

serviceKey callingPartyNumber calledPartyNumber cGEncountered extensions gsmSupplementaryServiceList iMSI iMEI msRoamingStatus mM-EventType gSMLocationInformation serviceCentreAddress sM-RP-UIHeader

About the use of the parameters:


.

serviceKey
This parameter contains the value of the ServiceKey in the subscriber data.

callingPartyNumber
It contains the primary MSISDN of the subscriber sending the short message. It identifies the service requested from the SCP together with the ServiceKey. It exists in MO short messages only.

146 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

calledPartyNumber
It contains the MSISDN of the subscriber receiving the short message. It identifies the service requested from the SCF together with the ServiceKey. It exists in MT short messages only.

cGEncountered
This parameter is sent if there is a call-gapping active for the ServiceKey, but the triggering is not gapped. With this information, the SCF can check if the CallGap operation has been successfully processed in the SSF.

Extensions: The criticality of every extension is IGNORE.


.

Extension: gSMSupplementaryServiceList
Supplementary data from the active supplementary list.

Extension: IMSI
The MO-SMS and MT-SMS cases are presented as follows: . sending the subscriber IMSI in an MO-SMS . receiving the subscriber IMSI in an MT-SMS

Extension: iMEI: . sending the subscriber IMEI in an MO-SMS . receiving the subscriber IMEI in an MT-SMS Extension: mSRoamingStatus
It indicates whether the subscriber is roaming in the home network or country. . Sending subscriber status in MO-SMS . Receiving subscriber status in MT-SMS

Extension: mM-EventType
It indicates the SMS-DP, that is, whether the transaction is initiated from an MO-SMS or an MT-SMS. . Value 5 indicates the SMS-DP1 (MO-SMS). . Value 6 indicates the SMS-DP2 (MT-SMS). . Value 8 indicates the SMS-DP3 (MT-SMS).

Extension: gSMLocationInformation
The calling party location area code (LAC) and the cell identity (CI) in an MO-SMS. The information is received from the MS.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

147 (196)

DX MSC/SSP/IP - SCP Interface Specification

Extension: serviceCentreAddress
SMSC address. It indicates the SMSC address where the MO short message is sent.

Extension: sm-RP-UIHeader
The deader of the following SM TL layer PDUs: . SMS DELIVER, conveying a short message from the SMSC to the MS . SMS SUBMIT, conveying a short message from the MS to the SMSC . SMS COMMAND, conveying a command from the MS to the SMSC . SMS REPORT, conveying a report from the SMSC to the MS

Operation: ReleaseCall (RC) Direction: Usage: SCF SSF The SCF requests the SSF to reject the sending of a short message. Associated operations: None. Comments: The SCF sends this operation as a final response operation. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

Table 69. SMS DP1 SMS DP2


yes yes

SSF support for the ReleaseCall operation in Detection Points SMS DP5
no

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

About the use of this operation:


This operation is used to reject the sending of a short message. The cause value is forwarded to the MS in case of an MO short message and to the SMSC in case of an MT short message.

Parameters:

148 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

Table 70. Parameter

Support for the ReleaseCall operation parameter Nokia Siemens Networks' support
S

Note

cause

About the use of the parameters:


.

cause
The value is always 'H'7C', which is reserved for call-unrelated functionalities. The additional cause value in the diagnostics field of the parameter is used instead. For the values of the MAP error codes, see GSM 09.02, v5.x.y, Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification, (Release 96). . System Failure . Unexpected Data Value . Facility Not Supported . SM Delivery Failure . Data Missing . Unidentified Subscriber . Illegal Subscriber . Illegal Equipment . Subscriber Busy For MT SM . Absent Subscriber SM

Operation: RequestReportBCSMEvent (RRB) Direction: Usage: SCF -> SSF The SCF requests the SSF to monitor the event. If the SSF detects an Event Detection Point (EDP) during the SMS processing, it sends a response back to the SCF (EventReportBCSM). Associated operations: EventReportBCSM Comments: The SCF sends this operation as an intermediate response operation. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

149 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 71.

SSF support for the RequestReportBCSMEvent operation in Detection Points SMS DP5
no

SMS DP1 SMS DP2


yes yes

SMS DP3
yes

SMS DP7
no

SMS DP13
no

SMS DP15
no

Spont
no

About the use of this operation:


The SCF arms the EDPs with this operation. In an MO-SMS case, the following DPs can be armed by the SCF: DP5 (SMS_Failure) and DP7 (SMS_Successful). In an MT-SMS case: DP13 (SMS_Failure) and DP15 (SMS_Successful). In an MT-SMS Connect case, the RequestReportBCSM operation is allowed from the SCF, but if followed by the Connect operation, the requested EDPs are disarmed, and there will be no EventReportBCSM operation.

Parameters:

Table 72. Parameter

Support for the RequestReportBCSMEvent operation parameters Nokia Siemens Networks' support
NS

Note

bcsmEvents

No extensions are used for this operation.

About the use of the parameters:


.

bcsmEvents: eventTypeBCSM: The armed DP is indicated to the SSF. The SSF has to monitor the event, and when it occurs, send an EventReportBCSM. . Value 5 indicates the SMS-DP5 (MO-SMS). . Value 7 indicates the SMS-DP7 (MO-SMS). . Value 13 indicates the SMS-DP13 (MT-SMS). . Value 15 indicates the SMS-DP15 (MT-SMS). . monitorMode:
.

150 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: Call-unrelated IN functions

. .

interrupted: Not supported. notifyAndContinue: The relationship is monitoring, and another parallel SSF-SCF relationship is possible. . transparent: Not supported. legID: This parameter is not read by the SSF. dPSpecificCriteria: This parameter is not read by the SSF.
. .

Operation: EventReportBCSM (ERB) Direction: Usage: SSF -> SCF The SSF informs the SCF of the encountered event that was previously requested by the SCF with operation RequestReportBCSMEvent. Associated operations: RequestReportBCSMEvent Comments: The SSF sends this operation only after an armed EDP has been encountered. The DP is always a notification-type EDP. In that case no response is expected from the SCF. Support in DPs: The SSF supports the operation in the DPs as indicated in the following table.

Table 73.

SSF support for the EventReportBCSM operation in Detection Points SMS DP5
yes

SMS DP1 SMS DP2


no no

SMS DP3
no

SMS DP7
yes

SMS DP13
yes

SMS DP15
yes

Spont
no

About the use of this operation:


The operation is used to indicate the outcome of the SM operation to the SCF.

Parameters:

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

151 (196)

DX MSC/SSP/IP - SCP Interface Specification

Table 74. Parameter

Support for the C (ERB) operation parameters Nokia Siemens Networks' support
S NS NS NS NS 1 1 1 2

Note

EventTypeBCSM EventSpecificInformationBCSM LegID MiscCallInfo Extensions

1 2

The parameter is not needed in case of an SMS. The extensions are not needed in case of an SMS.

About the use of the parameters:


.

eventTypeBCSM:
The SSF always includes this parameter. In an MO-SMS case, the DP5 (SMS_Failure) and the DP7 (SMS_Successful) DPs are used, and in an MT-SMS case, the DP13 (SMS_Failure) and the DP15 (SMS_Successful) DPs are used. . Value 5 indicates the SMS-DP5 (MO-SMS). . Value 7 indicates the SMS-DP7 (MO-SMS). . Value 13 indicates the SMS-DP13 (MT-SMS). . Value 15 indicates the SMS-DP15 (MT-SMS).

152 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

6
6.1

Interface description: ASN definitions


ASN.1 definitions for extensions

-- @ (#)MID: ITACEXMX.ASN -- Core-INAP-CS1-ExtensionTypes {???} CS1ExtensionTypes DEFINITIONS IMPLICIT TAGS ::= BEGIN IMPORTS EXT FROM EXTENSionModule Cause, ChargingZone, Digits, LegID, LocationNumber, ServiceKey, CallingPartyNumber, EventTypeBCSM, CalledPartyNumber FROM CS1DataTypes; -----Core-INAP-CS1-DataTypes { ccitt (0) identified-organization (4) etsi (0) intelligentNetworksDomain (1) in-network (1) modules (0) cs1-datatypes (2) version1 (0) };

-- *** TYPE DEFINITIONS IN CS1 EXTENSION TYPES FOLLOWS ********************** ------------------------------------------------------------------------------ LegIDExtension ::= EXTENSION -- EXTENSION SYNTAX Party -- CRITICALITY ignore legIDExtension EXT ::= { &ExtensionSyntax &criticality &id } Party ::= CHOICE {

Party, ignore, 11

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

153 (196)

DX MSC/SSP/IP - SCP Interface Specification

legID bothParty } --$ENTRY ----------

LegID, NULL

LegIDExtension is used with the ConnectToResource- and EstablishTemporaryConnection operations to define the party/parties to which/who the user interaction is related. If the LegIDExtension is not included, the user interaction is performed with the calling user. LegIDExtension is used with the ReleaseCall operation to define the party that has to be released. The formal definition is not yet clear, because the ReleaseCall operation does not include an extensions-field. If the value of the Party is bothParty, the PromptAndCollectUserInformation operation is not possible.

--------------------------------------------------------------------------------- LanguageIDExtension ::= EXTENSION -- EXTENSION SYNTAX LanguageID -- CRITICALITY ignore languageIDExtension EXT ::= &ExtensionSyntax &criticality &id } { LanguageID, ignore, 12

LanguageID ::= OCTET STRING (SIZE (1..2)) --$ENTRY -- LanguageIDExtension is used with the Connect-, the InitialDP-, the - PlayAnnouncement- and the PromptAndCollectUserInformation operations. -- With the Connect operation it is used to inform the SSP about the language-- parameter that has to be sent to the terminating line. -- With the InitialDP operation it is used to inform the service logic of the -- language-parameter received from the originating line or from the subscriber -- data. -- With the PlayAnnouncement- and PromptAndCollectUserInformation operations it -- is used to inform the IP about the up to four languages in which the - announcement and its various partscan be played. -- Coding of the LanguageID with the Connect-, and InitialDP- operations: the - Length is one octet: -- bits 4 3 2 and 1 define the language indicator (coded as the language indicator - of the Network specific facility, that is, of the ISUP; THK 9203; 3.23A). -- bits 8 7 6 and 5 are not used, set to '0' -- Coding of the LanguageID with the PromptAndCollectUserInformation- and -- PlayAnnouncement- operations: the Length is two octets: -- octet 1 bits 4 3 2 1 define the language 1 indicator -- octet 1 bits 8 7 6 5 define the language 2 indicator -- octet 2 bits 4 3 2 1 define the language 3 indicator -- octet 2 bits 8 7 6 5 define the language 4 indicator -- The Language indicator is coded as the language indicator of the Network- specific facility of the ISUP; THK 9203; 3.23A. The Languages are used in - the numbering order starting from language 1. - The value '0' means end of the list. --------------------------------------------------------------------------------

154 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-- ReleaseTypeExtension ::= EXTENSION -- EXTENSION SYNTAX ReleaseType -- CRITICALITY ignore releaseTypeExtension EXT ::= &ExtensionSyntax &criticality &id } { ReleaseType, ignore, 14

ReleaseType ::= ENUMERATED { caller (0), firstParty (1) } --$ENTRY -- ReleaseTypeExtension is used with Connect operation to inform the SSP about how -- the call has to be released. The values of the ReleaseType can be caller-- or first-party. -- If the ReleaseTypeExtension is not included, the call has to be released -- according to the traffic case or used signalling systems. --------------------------------------------------------------------------------- InterceptAnswerExtension ::= EXTENSION -- EXTENSION SYNTAX InterceptAnswer -- CRITICALITY ignore interceptAnswerExtension EXT ::= { &ExtensionSyntax InterceptAnswer, &criticality ignore, &id 15 } InterceptAnswer ::= BOOLEAN --$ENTRY -- InterceptAnswerExtension is used with the ConnectToResource- and -- EstablishTemporaryConnection operations to indicate to the SSP that the -- Answer signal received from the integrated or external IP have to be -- intercepted. -- If the extension is not included or the value is FALSE, the SSP sends the -- Answer signal to the originating line. --------------------------------------------------------------------------------- INtoINServiceInteractionsExtension ::= EXTENSION -- EXTENSION SYNTAX INtoINServiceInteractions -- CRITICALITY ignore iNtoINServiceInteractionsExtension EXT ::= { &ExtensionSyntax INtoINServiceInteractions, &criticality ignore, &id 18 } INtoINServiceInteractions ::= SEQUENCE SIZE (1..5) --$ENTRY-- OF SEQUENCE { service ServiceKey, activity BOOLEAN OPTIONAL } -- The INtoINServiceIndicationExtension is used to control the co-operation

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

155 (196)

DX MSC/SSP/IP - SCP Interface Specification

-------

of the IN-services in the same SSP. It indicates the list of services that have been invoked within the call. It is up to the service logic to decide whether some interaction exists and how to deal with that (for example to prevent new invocation). This parameter is transferred from the SCF to the SSF in the Connect, ConnectToResource and EstablishTemporaryConnection operations. It is returned in the case of a retriggering to the SCF in the InitialDP operation.

-- *** MOBILE SPECIFIC EXTENSIONS ********************************************** gsmSupplementaryServiceList EXT ::= { -- Connect, InitialDP &ExtensionSyntax GsmSupplementaryServiceList, &criticality ignore, &id 21 } odbInfo EXT ::= { &ExtensionSyntax &criticality &id } cugInfo EXT ::= { &ExtensionSyntax &criticality &id } calledLocation EXT ::= { &ExtensionSyntax &criticality &id } noAnswerCause EXT ::= { &ExtensionSyntax &criticality &id } imsi EXT ::= { &ExtensionSyntax &criticality &id } imei EXT ::= { &ExtensionSyntax &criticality &id } msrn EXT ::= { &ExtensionSyntax &criticality &id -- Connect, InitialDP ODBInfo, ignore, 22

-- Connect, InitialDP CUG-CheckInfo, ignore, 23

-- EventReportBCSM CalledLocation, ignore, 24

-- EventReportBCSM Cause, ignore, 25

-- InitialDP IMSI, ignore, 26

-- InitialDP IMEI, ignore, 27

-- InitialDP MSRN, ignore, 28

156 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

} msRoamingStatus EXT ::= { &ExtensionSyntax &criticality &id } pni EXT ::= { &ExtensionSyntax &criticality &id } absSubscriber EXT ::= { &ExtensionSyntax &criticality &id } msClassmarks EXT ::= { &ExtensionSyntax &criticality &id } -- InitialDP MSRoamingStatus, ignore, 29

-- InitialDP PNI, ignore, 30

-- InitialDP AbsSubscriber, ignore, 31

-- InitialDP MsClassmarks, ignore, 32

-- The Mobile Station Classmark 2 is sent to the SCF, if available. -- Concerns both the calling and the called mobiles. gsmLocationInformation EXT ::= &ExtensionSyntax &criticality &id } -------{ -- InitialDP GsmLocationInformation, ignore, 33

This extension is used to pass the GSM location of the called Mobile Station to the SCF in the same way as the standard parameter "locationNumber" passes the location information of the calling Mobile Station. Both of them can be included in the same IDP operation if both the calling and the called party location info is available for the MSC/SSP. -- InitialDP UsedSignalling, ignore, 34

usedSignalling EXT ::= { &ExtensionSyntax &criticality &id }

-- With this parameter the SSF informs the SCF from which incoming signalling -- type the call setup was received (for example ISUP, TUP, R2) in originating -- calls and the outgoing signalling type, if available, in the TBCSM. chargingBasis EXT ::= { &ExtensionSyntax &criticality -- InitialDP + ERB ChargingBasis, ignore,

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

157 (196)

DX MSC/SSP/IP - SCP Interface Specification

&id } -----

35

With this parameter the SSF gives the SCF information about the charging as much as it is available in the trigger DP. The information contains the charging zone, and it can be sent only if it is available in the call phase in which the triggering takes place.

extraForwardCallIndicator EXT ::= { -- InitialDP + Connect &ExtensionSyntax ExtraForwardCallIndicator, &criticality ignore, &id 36 } -- With this parameter the SSF tells the SCF that the called party address has -- already been translated by the network if such information is received -- from the incoming signalling. gatewaySSFIndication EXT ::= &ExtensionSyntax &criticality &id } -------{ -- InitialDP GatewaySSFIndication, ignore, 37

As the official version of ETSI Core INAP does not support the possibility of indicating when DP11 is encountered, a new parameter is included in the InitialDP operation advising that the triggering is initiated from the Gateway BCSM. With this indication the SCF is able to decide whether the triggering has occurred in DP11 or in DP12. However, the information is included also in other TDPs than DP12 when triggered from the Gateway BCSM. { -- InitialDP + ERB ForwardedToNumber, ignore, 38

forwardedToNumber EXT ::= &ExtensionSyntax &criticality &id }

-- The SSF tells the SCF the number to which the call is to be forwarded -- if the SCF lets the call continue without re-routing it. chargeableUserInteraction EXT ::= { -- CTR + ETC &ExtensionSyntax ChargeableUserInteraction, &criticality ignore, &id 39 } -- With this new parameter the SCF orders the charging to be started -- in the MSC/SSP. Previously this indication was bound to -- the "interceptAnswer" parameter that had double usage. mmEventType EXT ::= { &ExtensionSyntax &criticality &id } -- InitialDP MmEventType, ignore, 40

158 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

transactionType EXT ::= { &ExtensionSyntax &criticality &id } vlrNumber EXT ::= { &ExtensionSyntax &criticality &id } hlrNumber EXT ::= { &ExtensionSyntax &criticality &id }

-- InitialDP TransactionType, ignore, 41

-- InitialDP VlrNumber, ignore, 42

-- InitialDP HlrNumber, ignore, 43

gsmSupplementaryServiceControl EXT ::= { -- Connect &ExtensionSyntax GsmSupplementaryServiceControl, &criticality ignore, &id 44 } serviceCentreAddress EXT &ExtensionSyntax &criticality &id } sm-RP-UIHeader EXT ::= &ExtensionSyntax &criticality &id } ss-Code EXT ::= { &ExtensionSyntax &criticality &id } ext-BasicServiceCode EXT &ExtensionSyntax &criticality &id } mapOperationCode EXT ::= &ExtensionSyntax &criticality &id } midCallInformation EXT ::= ::= ::= { -- InitialDP, Connect ServiceCentreAddress, ignore, 46

-- InitialDP, Connect SM-RP-UIHeader, ignore, 47

-- InitialDP SS-Code, ignore, 48

{ -- InitialDP Ext-BasicServiceCode, ignore, 49

-- InitialDP MapOperationCode, ignore, 50

-- IDP, ERB

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

159 (196)

DX MSC/SSP/IP - SCP Interface Specification

&ExtensionSyntax &criticality &id } serviceInteractionIndicatorsTwo &ExtensionSyntax &criticality &id }

MidCallInformation, ignore, 51

EXT ::= { -- IDP, CON, CTR, ETC ServiceInteractionIndicatorsTwo, ignore, 52

suppressionOfAnnouncement EXT ::= { -- IDP, CON &ExtensionSyntax SuppressionOfAnnouncement, &criticality ignore, &id 53 } genericNumbers EXT ::= { &ExtensionSyntax &criticality &id } machineIndicator EXT ::= &ExtensionSyntax &criticality &id } timingAdvanceValue EXT ::= &ExtensionSyntax &criticality &id } measuredCellList EXT ::= { &ExtensionSyntax &criticality &id } -- IDP, CON GenericNumbers, ignore, 54

-- IDP, CON MachineIndicator, ignore, 55

-- IDP TimingAdvanceValue, ignore, 56

-- IDP MeasuredCellList, ignore, 57

na-Info EXT ::= { --IDP, CON, ETC &ExtensionSyntax NA-Info, &criticality ignore, &id 58 } numberPortabilityInfo EXT ::= { &ExtensionSyntax NumberPortabilityInfo, &criticality ignore, &id 59 } eventTypeCobi EXT::= { &ExtensionSyntax &criticality --IDP EventTypeCobi, ignore,

160 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

&id } localisedServiceArea EXT::= { &ExtensionSyntax &criticality &id } inTriggerKey EXT::= { &ExtensionSyntax &criticality &id } tmsi EXT ::= { &ExtensionSyntax &criticality &id }

60

--IDP LocalisedServiceArea, ignore, 61

--Connect InTriggerKey, ignore, 62

--IDP TMSI, ignore, 64

-- *** MOBILE SPECIFIC EXTENSION SYNTAX DEFINITIONS **************************** AbsSubscriber ::= OCTET STRING (SIZE (1)) --$ENTRY -- Values are coded as follows: -- 0 = No specific information -- 1 = Imsi detached -- 2 = No page responce -------------------------------------------------------------------------------CalledLocation ::= OCTET STRING (SIZE (1)) --$ENTRY -- Operator determined value -------------------------------------------------------------------------------CUG-CheckInfo ::= SEQUENCE { -- To be removed here after cug-Interlock CUG-Interlock, -- this definition has been cug-OutgoingAccess NULL OPTIONAL -- imported from MAP ! } --$ENTRY CUG-Interlock ::= OCTET STRING (SIZE (4)) -- Internal structure defined in Rec CCITT Q.763 -- GSM/MAP spec. 09.02 version 4.8.0. -------------------------------------------------------------------------------GsmSupplementaryServiceList ::= OCTET STRING (SIZE (3)) --$ENTRY -- Packed bit-structure containing the following information: -- (bit A = least significant) -- bit=0: ss not active for the subscriber in that specific call -- bit=1: ss active for the subscriber in that specific call -- octet 1, bit A: BAOC -bit B: BOIC -bit C: BOIC-exHC

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

161 (196)

DX MSC/SSP/IP - SCP Interface Specification

-bit D: BAIC -bit E: BIC-Roam -bit F: ODB -bit G: AoCI -bit H: AoCC -- octet 2, bit A: CFU -bit B: CFB -bit C: CFNRy -bit D: CFNRc -bit E: CLIP -bit F: CLIR -bit G: COLP (not used) -bit H: COLR (not used) -- octet 3, bit A: CW -bit B: HOLD -bit C: MPTY -bit D: CUG -bit E: CD -bit F: spare -bit G: spare -bit H: spare -------------------------------------------------------------------------------GsmSupplementaryServiceControl ::= SEQUENCE { controlList [0] GsmSupplementaryServiceList, serviceList [1] GsmSupplementaryServiceList } --$ENTRY -------------------------------------------------------------------------------IMEI ::= OCTET STRING (SIZE (8)) -- To be removed here after --$ENTRY --$N=8 -- this definition has been -- imported from MAP ! -- BCD-coded International mobile equipment identity -------------------------------------------------------------------------------IMSI ::= OCTET STRING (SIZE (3..8)) --$ENTRY--- To be removed here after -- this definition has been -- imported from MAP ! -- BCD-coded International mobile subscriber identity -------------------------------------------------------------------------------TMSI ::= OCTET STRING (SIZE (4)) --$ENTRY--- To be removed here after -- this definition has been -- imported from MAP ! -- BCD-coded Temporary mobile subscriber identity -------------------------------------------------------------------------------InTriggerKey ::= INTEGER (1..65535) -------------------------------------------------------------------------------MSRN ::= OCTET STRING (SIZE (1..9)) --$ENTRY--- To be removed here after -- this definition has been -- imported from MAP ! -- BCD-coded Mobile subscriber roaming number

162 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-------------------------------------------------------------------------------MSRoamingStatus ::= INTEGER (0..255) --$ENTRY -------------------------------------------------------------------------------ODBInfo ::= SEQUENCE { odb-Data ODB-Data OPTIONAL, odb-HlrData ODB-HlrData OPTIONAL } --$ENTRY -------------------------------------------------------------------------------ODB-Data ::= SEQUENCE { -- To be removed here after odb-GeneralData ODB-GeneralData, -- this definition has been odb-HPLMN-Data ODB-HPLMN-Data OPTIONAL -- imported from MAP ! } -------------------------------------------------------------------------------ODB-GeneralData ::= BIT STRING { allOG-CallsBarred (0), internationalOGCallsBarred (1), internationalOGCallsNotToHPLMN-CountryBarred (2), interzonalOGCallsBarred (6), interzonalOGCallsNotToHPLMN-CountryBarred (7), interzonalOGCallsAndInterzonalOGCallsNotToHPLMN-CountryBarred (8), premiumRateInformationOGCallsBarred (3), premiumRateEntertainementOGCallsBarred (4), ss-AccessBarred (5), allECT-Barred (9), chargeableECT-Barred (10), internationalECT-Barred (11), interzonalECT-Barred (12), doublyChargeableECT-Barred (13), multipleECT-Barred (14)} (SIZE (6..32)) -- exception handling: reception of unknown bit assignments in the -- ODB-GeneralData type shall be treated like unsupported - ODB-GeneralData in version 2 SIZE (6) in version 3 SIZE (15..32), - check in en/decode-function -------------------------------------------------------------------------------ODB-HPLMN-Data ::= BIT STRING { -- To be removed here after plmn-SpecificBarringType1 (0), -- this definition has been plmn-SpecificBarringType2 (1), -- imported from MAP ! plmn-SpecificBarringType3 (2), plmn-SpecificBarringType4 (3) } (SIZE (4)) --$N=8 -- Written directly from GSM/MAP spec. 09.02 version 4.8.0. -------------------------------------------------------------------------------ODB-HlrData ::= OCTET STRING (SIZE (1)) --$N=8 -------------------------------------------------------------------------------PNI ::= INTEGER (0..255) --$ENTRY -- Private number index for the Private Numbering Plan service (PNP)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

163 (196)

DX MSC/SSP/IP - SCP Interface Specification

-------------------------------------------------------------------------------MsClassmarks ::= SEQUENCE SIZE (1..2) --$ENTRY-- OF MsClassmark -------------------------------------------------------------------------------MsClassmark ::= OCTET STRING (SIZE (2..14)) -- This parameter includes Classmark 1..3 definitions and does not -- pay attention to classmark type. The application specifies the type of -- the used classmark. -- See GSM 04.08 for more information. -------------------------------------------------------------------------------GsmLocationInformation ::= CHOICE { locationNumber [0] LocationNumber, globalCellIds [1] GlobalCellIds } --$ENTRY -------------------------------------------------------------------------------GlobalCellIds ::= SEQUENCE { location [0] GlobalCellId OPTIONAL, -- Current or new ms-location oldLocation [1] GlobalCellId OPTIONAL } --$ENTRY -------------------------------------------------------------------------------GlobalCellId ::= OCTET STRING (SIZE (5..7)) -- Refers to Cell Global Identification defined in GSM 03.03. -- Octets are coded according to GSM 04.08. -- The internal structure is defined as follows: -Mobile Country Code: 3 digits according to CCITT Rec E.212 -1 digit filler (1111) -Mobile Network Code: 2 digits according to CCITT Rec E.212 -Location Area Code: 2 octets according to TS GSM 04.08 -Cell Identity: 2 octets (CI) according to TS GSM 04.08 -------------------------------------------------------------------------------UsedSignalling ::= SEQUENCE { inSignalling [0] SignallingType OPTIONAL, outSignalling [1] SignallingType OPTIONAL } --$ENTRY -------------------------------------------------------------------------------SignallingType ::= SEQUENCE { mainSignalling [0] MainSignallingType, version [1] SignallingVersionType OPTIONAL } -------------------------------------------------------------------------------MainSignallingType ::= ENUMERATED { bssap (1), -- A-interface tup (2), -- CCS#7 signallings nup (3), isup (4), dpnss (5), -- PBX signallings dss1 (6), r2 (7), -- Channel associated signalling pad (8) -- Data access

164 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

} -------------------------------------------------------------------------------SignallingVersionType ::= OCTET STRING (SIZE (1)) -- Shows a version of the current signalling e.g. isup = 1 and isup2 = 2 -------------------------------------------------------------------------------ChargingBasis ::= ChargingZone --$ENTRY -------------------------------------------------------------------------------ExtraForwardCallIndicator ::= OCTET STRING (SIZE (1)) --$ENTRY -- National Forward Call Indicator includes Calling Line Identity Barring -- Indicator (CBI) and Network Translated Address Indicator (NTA). --- bit A: CBI, value 0 no information and value 1 CLI blocking available -- bit B: NTA, value 0 no information and value 1 NTA has occured -- bit C: spare -- bit D: spare -- bit E: spare -- bit F: spare -- bit G: spare -- bit H: spare --- If no extension is used, the default values are CBI=1 and NTA=0. -------------------------------------------------------------------------------GatewaySSFIndication ::= NULL --$ENTRY -------------------------------------------------------------------------------ForwardedToNumber ::= ISDN-AddressString --$ENTRY -- The following definitions are imported from GSM 09.02 -------------------------------------------------------------------------------AddressString ::= OCTET STRING (SIZE (1..maxAddressLength)) -- This type is used to represent a number for addressing -- purposes. It is composed of -- a) one octet for the nature of address and numbering plan -indicator. -- b) digits of an address encoded as TBCD-String. -- a) The first octet includes a one bit extension indicator, a -3 bits nature of address indicator and a 4 bits numbering -plan indicator, encoded as follows: -- bit 8: 1 (no extension) -- bits 765: nature of address indicator -- 000 unknown -- 001 international number -- 010 national significant number -- 011 network-specific number -- 100 subscriber number -- 101 reserved -- 110 abbreviated number -- 111 reserved for extension -- bits 4321: numbering plan indicator -- 0000 unknown -- 0001 ISDN/Telephone Numbering Plan (Rec CCITT E.164)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

165 (196)

DX MSC/SSP/IP - SCP Interface Specification

----------

0010 0011 0100 0101 0110 0111 1000 1001 1111

spare data numbering plan (CCITT Rec X.121) telex numbering plan (CCITT Rec F.69) spare land mobile numbering plan (CCITT Rec E.212) spare national numbering plan private numbering plan reserved for extension

-- all other values are reserved. -- b) -The following octets represent digits of an address encoded as a TBCD-STRING. INTEGER ::= 20

maxAddressLength

ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength)) -- This type is used to represent ISDN numbers. maxISDN-AddressLength INTEGER ::= 9

-------------------------------------------------------------------------------ChargeableUserInteraction ::= BOOLEAN --$ENTRY -------------------------------------------------------------------------------MmEventType ::= INTEGER (1..127) --$ENTRY -- The following values are reserved for the -- different TDPs: -plmnSpecificLocup 1 -interVLrLocup 2 -intraVLRLocup 3 -hLRLocup 4 -moSMS 5 -mtSMS 6 -ss 7 -report 8

-------------------------------------------------------------------------------TransactionType ::= INTEGER (1..127) --$ENTRY -- The following values are reserved for the -- different transaction types: -normal location registration 1 -IMSI attach 2 -------------------------------------------------------------------------------VlrNumber ::= ISDN-AddressString --$ENTRY -------------------------------------------------------------------------------HlrNumber ::= ISDN-AddressString --$ENTRY -------------------------------------------------------------------------------PresentationNumber ::= CallingPartyNumber --$ENTRY --------------------------------------------------------------------------------

166 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

ServiceCentreAddress ::=

ISDN-AddressString --$ENTRY

-------------------------------------------------------------------------------SM-RP-UIHeader ::= CHOICE { smsDeliver [0] OCTET STRING (SIZE (12..22)), smsSubmit [1] OCTET STRING (SIZE (7..23)), smsCommand [2] OCTET STRING (SIZE (6..17)), smsReport [3] OCTET STRING (SIZE (19..32)) } --$ENTRY -------------------------------------------------------------------------------SS-Code ::= OCTET STRING (SIZE (1)) --$ENTRY --$N=8 -- This type is used to represent the code identifying a single -- supplementary service, a group of supplementary services, or -- all supplementary services. The services and abbreviations -- used are defined in GSM 02.04. The internal structure is -- defined as follows: --- bits 87654321: group (bits 8765), and specific service -- (bits 4321) -------------------------------------------------------------------------------Ext-BasicServiceCode ::= CHOICE { ext-BearerService [2] Ext-BearerServiceCode --$CCONV= --, ext-Teleservice [3] Ext-TeleserviceCode --$CCONV= } --$ENTRY Ext-BearerServiceCode ::= OCTET STRING (SIZE (1..5)) --$ENTRY --$TCONV= --$TSUFF= -- This type is used to represent the code identifying a single -- bearer service, a group of bearer services, or all bearer -- services. The services are defined in TS GSM 02.02. -- The internal structure is defined as follows: --- OCTET 1: -- plmn-specific bearer services: -- bits 87654321: defined by the HPLMN operator --- rest of bearer services: -- bit 8: 0 (unused) -- bits 7654321: group (bits 7654), and rate, if applicable -- (bits 321) -- OCTETS 2-5: reserved for future use. If received the -- Ext-TeleserviceCode shall be -- treated according to the exception handling defined for the -- operation that uses this type. -- Ext-BearerServiceCode includes all values defined for -- BearerServiceCode. Ext-TeleserviceCode ::= OCTET STRING (SIZE (1..5))

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

167 (196)

DX MSC/SSP/IP - SCP Interface Specification

--$ENTRY --$TCONV= --$TSUFF= -- This type is used to represent the code identifying a single -- teleservice, a group of teleservices, or all teleservices. The -- services are defined in TS GSM 02.03. -- The internal structure is defined as follows: ----OCTET 1: bits 87654321: group (bits 8765) and specific service (bits 4321) OCTETS 2-5: reserved for future use. If received the -- Ext-TeleserviceCode shall be -- treated according to the exception handling defined for the -- operation that uses this type. -- Ext-TeleserviceCode includes all values defined for TeleserviceCode.

-------------------------------------------------------------------------------MapOperationCode ::= OCTET STRING (SIZE (1)) --$ENTRY -- This type is used to represent the MAP operation code -------------------------------------------------------------------------------MidCallInformation ::= SEQUENCE { midCallCode [0] OCTET STRING (SIZE (1)), codingScheme [1] OCTET STRING (SIZE (1)) OPTIONAL, uSSDString [2] OCTET STRING (SIZE (1..161)) OPTIONAL} --$ENTRY -------------------------------------------------------------------------------ServiceInteractionIndicatorsTwo ::= SEQUENCE { forwardServiceInteractionInd [0] ForwardServiceInteractionInd OPTIONAL, -- applicable to operations IDP, CON. backwardServiceInteractionInd [1] BackwardServiceInteractionInd OPTIONAL, -- applicable to operations IDP, CON, CTR, ETC. bothwayThroughConnectionInd [2] BothwayThroughConnectionInd OPTIONAL, -- applicable to operations CTR, ETC. suspendTimer [3] SuspendTimer OPTIONAL, -- applicable to operations CON. connectedNumberTreatmentInd [4] ConnectedNumberTreatmentInd OPTIONAL, -- applicable to operations CON, CTR, ETC. suppressCallDiversionNotification [5] BOOLEAN OPTIONAL, -- applicable to CON -- indicates whether the Call diversion -- notification indicator shall be suppressed (TRUE) or -- notification shall be allowed, that is, no IN -- impact (FALSE). -- network default is no IN impact. suppressCallTransferNotification [6] BOOLEAN OPTIONAL, -- applicable to CON -- indicates wheter the Call transfer -- notification indicator shall be suppressed (TRUE) or -- notification shall be allowed, that is, no IN -- impact (FALSE). -- network default is no IN impact. allowCdINNoPresentationInd [7] BOOLEAN OPTIONAL,

168 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-- applicable to CON -- indicates whether the Number Presentation not allowed -- indicator of the ISUP -- "called IN number" shall be set to presentation allowed -- (TRUE) or presentation not allowed (FALSE) -- network default is not allowed userDialogueDurationInd [8] BOOLEAN DEFAULT TRUE -- applicable when interaction with the user is required, -- if the interaction -- TRUE means the user interaction may last longer than 90 seconds. -- Otherwise the indicator should be set to FALSE. -- used for delaying ISUP T9 timer. } --$ENTRY -- Indicators which are exchanged between SSP and SCP to resolve -- interactions between IN based services -- and network based services, respectively between different -- IN based services. ForwardServiceInteractionInd ::= SEQUENCE { conferenceTreatmentIndicator [1] OCTET STRING (SIZE (1)) OPTIONAL, -- acceptConferenceRequest (xxxx xx01)B -- rejectConferenceRequest (xxxx xx10)B -- network default is accept conference request callDiversionTreatmentIndicator [2] OCTET STRING (SIZE (1)) OPTIONAL, -- callDiversionAllowed (xxxx xx01)B -- callDiversionNotAllowed (xxxx xx10)B -- network default is Call Diversion allowed callOfferingTreatmentIndicator [3] OCTET STRING (SIZE (1)) OPTIONAL -- callOfferingNotAllowed (xxxx xx01)B -- callOfferingAllowed (xxxx xx10)B -- network default is Call Offering not allowed } --$ENTRY BackwardServiceInteractionInd ::= SEQUENCE { conferenceTreatmentIndicator [1] OCTET STRING (SIZE (1)) OPTIONAL, -- acceptConferenceRequest (xxxx xx01)B -- rejectConferenceRequest (xxxx xx10)B -- network default is accept conference request, callCompletionTreatmentIndicator [2] OCTET STRING (SIZE (1)) OPTIONAL -- acceptCallCompletionServiceRequest (xxxx xx01)B -- rejectCallCompletionServiceRequest (xxxx xx10)B -- network default is reject call completion service request } --$ENTRY BothwayThroughConnectionInd ::= ENUMERATED { bothwayPathRequired (0), bothwayPathNotRequired (1) } --$ENTRY -- network default is bothway path required: SPS3 WP4 17-21.11.97 SuspendTimer ::= INTEGER (-1..120) --$ENTRY --value in seconds -- The value -1 indicates the network-specific suspend timer (T6) -- must be used (CS2 PE drafts 01/98) -- network default is 0: SPS3 WP4 17-21.11.97

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

169 (196)

DX MSC/SSP/IP - SCP Interface Specification

ConnectedNumberTreatmentInd ::= ENUMERATED { noINImpact (0), presentationRestricted (1), presentCalledINNumber (2), presentCalledINNumberRestricted (3) } --$ENTRY -- network default is present called IN number: SPS3 WP4 17-21.11.97 -------------------------------------------------------------------------------SuppressionOfAnnouncement ::= NULL --$ENTRY -- CAMEL-parameter as INAP-extension -------------------------------------------------------------------------------GenericNumbers ::= Digits --$ENTRY -- CAMEL-parameter as INAP-extension (Q.763) -------------------------------------------------------------------------------MachineIndicator ::= OCTET STRING (SIZE (5)) --$ENTRY -------------------------------------------------------------------------------TimingAdvanceValue ::= OCTET STRING (SIZE (1)) --$ENTRY -------------------------------------------------------------------------------MeasuredCellList ::= OCTET STRING (SIZE (4..28)) --$ENTRY -List of 1 to 7 measured cells (LAC+CI) -Location Area Code: 2 octets (LAC) according to TS GSM 04.08 -Cell Identity: 2 octets (CI) according to TS GSM 04.08 -------------------------------------------------------------------------------NA-Info ::= SEQUENCE { naCarrierInformation [0] NACarrierInformation OPTIONAL, naOliInfo [1] NAOliInfo OPTIONAL, naChargeNumber [2] NAChargeNumber OPTIONAL } --$ENTRY -------------------------------------------------------------------------------NACarrierInformation ::= SEQUENCE { naCarrierId [0] NAEA-CIC OPTIONAL, naCICSelectionType [1] NACarrierSelectionInfo OPTIONAL } --$ENTRY -------------------------------------------------------------------------------NAEA-CIC ::= OCTET STRING (SIZE (3)) --$ENTRY -- The internal structure is defined by the Carrier Identification -- parameter in ANSI T1.113.3. Carrier codes between 000 and 999 -- are encoded in 3 digits using 000 to 999 or in 4 digits using -- 0000 to 0999. Carrier codes between 1000 and 9999 are encoded -- using 4 digits -------------------------------------------------------------------------------NACarrierSelectionInfo ::= OCTET STRING (SIZE (1)) --$ENTRY -- NA carrier selection information octet carries the same values as ANSI -- provides -- ISUP T1.113: '00'H -not indicated or not explicitly provided -- '01'H -subscribed not dialled

170 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-- '02'H -subscribed and dialled -- '03'H -subscribed with dialling undetermined -- '04'H -dialed CIC not subscribed -------------------------------------------------------------------------------NAOliInfo ::= OCTET STRING (SIZE (1)) --$ENTRY -- NA Oli information takes the same value as defined in ANSI ISUP T1.113 -- e.g. '3D'H - Decimal value 61 - Cellular Service (Type 1) -- '3E'H -Decimal value 62 - Cellular Service (Type 2) -- '3F'H -Decimal value 63 - Cellular Service (roaming) -------------------------------------------------------------------------------NAChargeNumber ::= OCTET STRING (SIZE (2..7)) --$ENTRY -- This parameter uniquely identifies the chargeable number for a call -- sent into a North American long distance carrier. It transports the -- ChargeNumber Parameter Field as defined in ANSI ISUP T1.113. This -- provides -- - 1 octet for the nature of address indicator field, plus -- - 1 octet for a numbering plan field, plus -- - up to 5 octets for the address signal (up to 10 digits) -- The Charge Number in ANSI T1.113 normally contains a 10 digit national -- number within the North American Numbering Plan (NANP); longer (e.g. -- international) charge numbers are not supported in T1.113 -------------------------------------------------------------------------------NumberPortabilityInfo ::= SEQUENCE { npRoutingNumber [0] CalledPartyNumber OPTIONAL, calledDialledNumber [1] CalledPartyNumber OPTIONAL, npQueryIndicator [2] NPQueryIndicator OPTIONAL } --$ENTRY -------------------------------------------------------------------------------NPQueryIndicator ::= ENUMERATED { notDone (0), done (1), doneNotPorted (2), donePorted (3), doneNotKnown (4), donePortedOut (5), donePortedForeign (6) } --$ENTRY -------------------------------------------------------------------------------EventTypeCobi ::= EventTypeBCSM --$ENTRY -------------------------------------------------------------------------------LocalisedServiceArea ::= OCTET STRING (SIZE (3)) --$ENTRY --------------------------------------------------------------------------------- *** EXTENSION CODE ASSIGNEMENTS IN CS1 PROTOCOL FOLLOWS ********************* -- LegIDExtension ::= localValue 11 -- LanguageIDExtension ::= localValue 12 -- releaseTypeExtension ::= localValue 14 -- interceptAnswerExtension ::= localValue 15 -- iNtoINServiceInteractionsExtension ::= localValue 18 -- gsmSupplementaryServiceList ::= localValue 21

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

171 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- odbInfo -- cugInfo -- calledLocation -- noAnswerCause -- imsi -- imei -- msrn -- msRoamingStatus -- pni -- absSubscriber -- msClassmarks -- gsmLocationInformation -- usedSignalling -- chargingBasis -- nationalForwardCallIndicator -- gatewaySSFIndication -- forwardedToNumber -- chargeableUserInteraction -- mmEventType -- transactionType -- vlrNumber -- hlrNumber -- gsmSupplementaryServiceControl -- presentationNumber -- serviceCentreAddress -- sm-RP-UIHeader -- ss-Code -- ext-BasicServiceCode -- mapOperationCode -- midCallInformation -- serviceInteractionIndicatorsTwo -- suppressionOfAnnouncement -- genericNumbers -- machineIndicator -- timingAdvanceValue -- measuredCellList -- naInfo -- numberPortabilityInfo -- eventTypeCobi -- localisedSeviceArea -- inTriggerKey END

::= localValue 22 ::= localValue 23 ::= localValue 24 ::= localValue 25 ::= localValue 26 ::= localValue 27 ::= localValue 28 ::= localValue 29 ::= localValue 30 ::= localValue 31 ::= localValue 32 ::= localValue 33 ::= localValue 34 ::= localValue 35 ::= localValue 36 ::= localValue 37 ::= localValue 38 ::= localValue 39 ::= localValue 40 ::= localValue 41 ::= localValue 42 ::= localValue 43 ::= localValue 44 ::= localValue 45 ::= localValue 46 ::= localValue 47 ::= localValue 48 ::= localValue 49 ::= localValue 50 ::= localValue 51 ::= localValue 52 ::= localValue 53 ::= localValue 54 ::= localValue 55 ::= localValue 56 ::= localValue 57 ::= localValue 58 ::= localValue 59 ::= localValue 60 ::= localValue 61 ::= localValue 62

6.2

ASN.1 definitions for operation data types

-- @ (#)MID: ITACDAMX.ASN -- Core-INAP-CS1-DataTypes CS1DataTypes { ccitt (0) identified-organization (4) etsi (0) intelligentNetworksDomain (1) in-network (1) modules (0)

172 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

cs1-datatypes (2) version1 (0) } -- This module contains the type definitions for the IN CS1 data types. -- The following parameters map onto the bearer protocol (that is, Q.931/2 and - ISUP) parameters: CalledPartyNumber, Prefix (derived from dialed digits), -- DestinationRoutingAddress, DialedDigits, AccessTransport, -- CallingPartyCategory, ForwardCallIndicators, LocationNumber, -- AssistingSSPIPRoutingAddress, AlertingPattern (Q.931 only), ReleaseCause -- (and other Cause parameters), AdditionalCallingPartyNumber. -- The following SSF parameters do not map onto the bearer protocol (that is, - Q.931/2 and ISUP) parameters and therefore are assumed to be local to the - switching system: RouteList, LegID, SSPIPCapabilities, IPAvailable, - CGEncountered, CorrelationID, Timers, MiscCallInfo, and ServiceKey. -- Where possible, administrators should define the maximum size within their - network of parameters specified in this Recommendation that are of an - indeterminate length. DEFINITIONS IMPLICIT TAGS ::= BEGIN -- NOTE ! InvokeIdType has been defined in this file ! --- IMPORTS -InvokeIdType FROM TCAPMessages { -ccitt recommendation q 773 modules (2) -messages (1) version2 (2) -}; -- **** TYPE DEFINITIONS FOR IN CS1 DATA TYPES FOLLOWS ************************* -- CoreINAP SCF - SSF operation argument definitions ----The ordering of parameters in the argument sequences has been arbitrary. Further study may be required to order arguments in a manner which will facilitate efficient encoding and decoding. NOTE ! Charging-related operations are defined later in this file.

-- Operations: CallGapArg ::= SEQUENCE gapCriteria gapIndicators controlType gapTreatment extensions -... } --$ENTRY { [0] [1] [2] [3] [4]

GapCriteria, GapIndicators, ControlType GapTreatment ExtensionArray

OPTIONAL, OPTIONAL, OPTIONAL

-- OPTIONAL denotes network operator optional. If gapTreatment is not present, - the SSF will use a default treatment depending on network operator - implementation. CancelArg ::= CHOICE { invokeID allRequests

[0] InvokeID, [1] NULL

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

173 (196)

DX MSC/SSP/IP - SCP Interface Specification

} --$ENTRY -- The InvokeID has the same value as the one that was used for the operation -- to be cancelled. CollectInformationArg ::= SEQUENCE { extensions [4] ExtensionArray -... } --$ENTRY ConnectArg ::= SEQUENCE { destinationRoutingAddress alertingPattern correlationID cutAndPaste originalCalledPartyID routeList scfID extensions serviceInteractionIndicators callingPartyNumber callingPartysCategory redirectingPartyID redirectionInformation } --$ENTRY

OPTIONAL

[0] DestinationRoutingAddress, [1] AlertingPattern [2] CorrelationID [3] CutAndPaste [6] OriginalCalledPartyID [7] RouteList [8] ScfID [10] ExtensionArray [26] ServiceInteractionIndicators [27] CallingPartyNumber [28] CallingPartysCategory [29] RedirectingPartyID [30] RedirectionInformation

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

-- For the alerting pattern, OPTIONAL denotes that this parameter only applies if - the SSF is the terminating local exchange for the subscriber. ConnectToResourceArg ::= SEQUENCE { resourceAddress CHOICE { ipRoutingAddress none }, extensions serviceInteractionIndicators -... } --$ENTRY

[0] IPRoutingAddress, [3] NULL [4] ExtensionArray [30] ServiceInteractionIndicators OPTIONAL, OPTIONAL

EstablishTemporaryConnectionArg ::= SEQUENCE { assistingSSPIPRoutingAddress [0] AssistingSSPIPRoutingAddress, correlationID [1] CorrelationID OPTIONAL, scfID [3] ScfID OPTIONAL, extensions [4] ExtensionArray OPTIONAL, serviceInteractionIndicators [30] ServiceInteractionIndicators -... } --$ENTRY EventReportBCSMArg ::= SEQUENCE { eventTypeBCSM eventSpecificInformationBCSM legID miscCallInfo extensions ...

OPTIONAL

[0] [2] [3] [4]

EventTypeBCSM, EventSpecificInformationBCSM LegID MiscCallInfo { messageType request }, [5] ExtensionArray

OPTIONAL, OPTIONAL, DEFAULT OPTIONAL

--

174 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

} --$ENTRY InitialDPArg ::= SEQUENCE { serviceKey calledPartyNumber callingPartyNumber callingPartysCategory cGEncountered iPSSPCapabilities iPAvailable locationNumber originalCalledPartyID extensions highLayerCompatibility serviceInteractionIndicators additionalCallingPartyNumber forwardCallIndicators bearerCapability eventTypeBCSM redirectingPartyID redirectionInformation } --$ENTRY ----------

[0] ServiceKey, [2] CalledPartyNumber [3] CallingPartyNumber [5] CallingPartysCategory [7] CGEncountered [8] IPSSPCapabilities [9] IPAvailable [10] LocationNumber [12] OriginalCalledPartyID [15] ExtensionArray [23] HighLayerCompatibility [24] ServiceInteractionIndicators [25] AdditionalCallingPartyNumber [26] ForwardCallIndicators [27] BearerCapability [28] EventTypeBCSM [29] RedirectingPartyID [30] RedirectionInformation

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

OPTIONAL for iPSSPCapabilities, iPAvailable, cGEncountered denotes network operator specific use. OPTIONAL for callingPartyNumber, and callingParty'sCategory refers to section 3 for the trigger detection point processing rules to specify when these parameters are included in the message. The structural parameters shall be recognised by the SCF upon reception of the InitialDP. These parameters shall be ignored by the SCF and not lead to any error procedures. These parameters shall not be sent by an SSF following this standard.

PlayAnnouncementArg ::= SEQUENCE { informationToSend disconnectFromIPForbidden requestAnnouncementComplete extensions -... } --$ENTRY

[0] [1] [2] [3]

InformationToSend, BOOLEAN DEFAULT TRUE, BOOLEAN DEFAULT TRUE, ExtensionArray OPTIONAL

PromptAndCollectUserInformationArg::= SEQUENCE { collectedInfo [0] CollectedInfo, disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, informationToSend [2] InformationToSend OPTIONAL, extensions [3] ExtensionArray OPTIONAL -... } --$ENTRY ReceivedInformationArg ::= CHOICE { digitsResponse [0] Digits } --$ENTRY ReleaseCallArg ::= Cause --$ENTRY

-- The default value of decimal 31 (normal unspecified) should be coded

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

175 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- appropriately. RequestReportBCSMEventArg ::= SEQUENCE { bcsmEvents [0] SEQUENCE SIZE (1..numOfBCSMEvents) OF BCSMEvent, extensions [2] ExtensionArray OPTIONAL -... } --$ENTRY -- Indicates the BCSM related events for notification. ResetTimerArg ::= SEQUENCE { timerID [0] TimerID DEFAULT tssf, timervalue [1] TimerValue, extensions [2] ExtensionArray OPTIONAL -... } --$ENTRY SpecializedResourceReportArg ::= NULL --$ENTRY

-- **** CHARGING RELATED DEFINITIONS ******************************************* -- Operations: ApplyChargingArg ::= SEQUENCE { aChBillingChargingCharacteristics sendCalculationToSCFIndication partyToCharge extensions -... } --$ENTRY ---

[0] [1] [2] [3]

AChBillingChargingCharacteristics, BOOLEAN DEFAULT FALSE, LegID OPTIONAL, ExtensionArray OPTIONAL

The sendCalculationToSCFIndication parameter indicates that ApplyChargingReport operations are expected from the SSF. This parameter shall always be set to TRUE. The PartyToCharge parameter indicates the party in the call to which the ApplyCharging operation should be applied. If it is not present, then it is applied to the A-party.

ApplyChargingReportArg ::= CallResult --$ENTRY EventNotificationChargingArg ::= SEQUENCE { eventTypeCharging [0] EventTypeCharging, eventSpecificInformationCharging [1] EventSpecificInformationCharging - OPTIONAL, legID [2] LegID OPTIONAL, extensions [3] ExtensionArray OPTIONAL, monitorMode [30] MonitorMode - DEFAULT notifyAndContinue -... } --$ENTRY -- OPTIONAL denotes network operator-specific use. FurnishChargingInformationArg ::= FCIBillingChargingCharacteristics --$ENTRY

RequestNotificationChargingEventArg ::= SEQUENCE SIZE (1..numOfChargingEvents) --

176 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

$ENTRY OF ChargingEvent SendChargingInformationArg ::= SEQUENCE { sCIBillingChargingCharacteristics legID extensions -... } --$ENTRY

[0] SCIBillingChargingCharacteristics, [1] LegID, [2] ExtensionArray OPTIONAL

--------------------------------------------------------------------------------- Operation data types: AChBillingChargingCharacteristics ::= OCTET STRING - (SIZE (minAChBillingChargingLength ..maxAChBillingChargingLength )) ----------The AChBillingChargingCharacteristics parameter specifies the charging related information to be provided by the SSF and the conditions on which this information has to be reported back to the SCF with the ApplyChargingReport operation. Examples of charging-related information to be provided by the SSF may be: bulk counter values, costs, tariff change and time of change, time stamps, durations, et cetera. Examples of conditions on which the charging related information are to be reported may be: threshold value reached, timer expiration, tariff change, end of connection configuration, et cetera.

-- *** NCS implementation *** -- *** NOTE ! -- *** Following commented description defines ONLY the STRUCTURE of DATA -- *** in the operation. They are NOT ASN.1 coded presentation ! -- AChBillingChargingCharacteristics ::= SEQUENCE { -callTreatment CallTreatment, -threshold Threshold, -warningTime INTEGER (0..255) OPTIONAL -} -------------------------------------------------------------------------------CallResult ::= OCTET STRING (SIZE (minCallResultLength .. maxCallResultLength )) -This parameter provides the SCF with the charging-related information previously requested using the ApplyCharging operation. This shall include the partyToCharge parameter as received in the related ApplyCharging operation to correlate the result to the request. The remaining content is network operator-specific. Examples of charging-related information to be provided by the SSF may be: bulk counter values, costs, tariff change and time of change, time stamps, durations, et cetera. Examples of conditions on which the charging-related information is to be reported may be: threshold value reached, timer expiration, tariff change, end of connection configuration, et cetera. *** *** ***

-- *** NCS implementation *** -- *** NOTE ! ***

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

177 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- *** Following commented descriptions defines ONLY the STRUCTURE of DATA -- *** in the operation. They are NOT ASN.1 coded presentation ! -- CallResult ::= SEQUENCE { -callTreatment -reportInfo ----endOfCallIndicator -}

*** ***

CallTreatment, CHOICE { hotBillingRecord threshold }, BOOLEAN

HotBillingRecord, Threshold

-- CallTreatment ::= ENUMERATED { -hotBillingRecord (0), -pulseThresholdValue (1), -currencyThresholdValue (2), -timeThresholdValue (3) -} -- HotBillingRecord ::= SEQUENCE { -callingPartyNumber OCTET STRING (SIZE (12)), - BCDF coded number -calledPartyNumber OCTET STRING (SIZE (12)), - BCDF coded number -startTimeOfCall OCTET STRING (SIZE (8)), - DX200 coded time -endTimeOfCall OCTET STRING (SIZE (8)), - DX200 coded time -chargingPulses ChargingPulses, -redirectingPartyID OCTET STRING (SIZE (12)), - BCDF coded -redirectionInformation OCTET STRING (SIZE (1)), - Only first octet -callTime Integer4, - Call duration in tenth seconds -chargingZone ChargingZone -} --- NOTE ! Isup parameter lengths are fixed sized here whereas isup paremeters are -normally of variable length! Coding is still done according to ISUP spec. Q.763. -- Threshold ::= CHOICE { -pulseLimit PulseLimit, -chargeMessage ChargeMessage, -time INTEGER (0..65535) -} -- PulseLimit ::= SEQUENCE { -pulses chargingPulses, -tariffType DXtariffType -} -- DXTariffType ::= OCTET STRING (SIZE (1))

- Remaining time of call in seco

--------------------------------------------------------------------------------- ChargeMessage ::= SEQUENCE { -messageType OCTET STRING (SIZE (1)), -pointCode OCTET STRING (SIZE (2)), -tariffType OCTET STRING (SIZE (1)), -currency OCTET STRING (SIZE (4)), -endOfOptParameters OCTET STRING (SIZE (1)) -}

178 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-------------------------------------------------------------------------------ChargingEvent ::= SEQUENCE { eventTypeCharging [0] EventTypeCharging, monitorMode [1] MonitorMode, legID [2] LegID OPTIONAL } -- This parameter indicates the charging event type -- monitor mode and LegID. and corresponding

--------------------------------------------------------------------------------- ChargingPulses ::= INTEGER (0..65535) -------------------------------------------------------------------------------ChargingZone ::= INTEGER (0..65535) -------------------------------------------------------------------------------EventSpecificInformationCharging ::= OCTET STRING - ( SIZE ( minEventSpecificInformationChargingLength .. maxEventSpecificInformationChargingLength )) -------defined by the network operator. Indicates the charging-related information specific to the event. An example data type definition for this parameter is given below: EventSpecificInformationCharging ::= CHOICE { chargePulses [0] Integer4, chargeMessages [1] OCTET STRING (SIZE (min..max )) }

-------------------------------------------------------------------------------EventTypeCharging ::= OCTET STRING (SIZE (minEventTypeChargingLength .. maxEventTypeChargingLength )) -------This parameter indicates the charging event type. Its content is network operator-specific. An example data type definition for this parameter is given below: EventTypeCharging ::= ENUMERATED { chargePulses (0), chargeMessages (1) }

-------------------------------------------------------------------------------FCIBillingChargingCharacteristics ::= OCTET STRING - (SIZE (minFCIBillingChargingLength .. maxFCIBillingChargingLength )) ---------This parameter indicates the billing and/or charging characteristics. Its content is network operator-specific. An example datatype definition for this parameter is given below: FCIBillingChargingCharacteristics ::= CHOICE { completeChargingRecord [0] OCTET STRING (SIZE (min...max)), correlationID [1] CorrelationID, scenario2Dot3 [2] SEQUENCE { chargeParty [0] LegID OPTIONAL, chargeLevel [1] OCTET STRING (SIZE (min..max))

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

179 (196)

DX MSC/SSP/IP - SCP Interface Specification

-OPTIONAL, -chargeItems [2] SET OF Attribute OPTIONAL -} -} -- Depending on the applied charging scenario the following information elements - can be included -- (refer to Annex B): -complete charging record (scenario 2.2) -charge party (scenario 2.3) -charge level (scenario 2.3) -charge items (scenario 2.3) -correlationID (scenario 2.4) -- *** NCS implementation *** -- *** NOTE ! *** -- *** The following commented description defines ONLY the STRUCTURE of DATA *** -- *** in the operation. They are NOT ASN.1 coded presentation! *** -- FCIBillingChargingCharacteristics ::= SEQUENCE { -controlInformation OCTET STRING (SIZE (1)), -serviceInformationLength OCTET STRING (SIZE (2)), -serviceInformation OCTET STRING (SIZE (1..310)) OPTIONAL -} -------------------------------------------------------------------------------SCIBillingChargingCharacteristics ::= OCTET STRING (SIZE (minSCIBillingChargingLength .. maxSCIBillingChargingLength )) ------------This parameter indicates the billing and/or charging characteristics. Its content is network operator-specific. An example datatype definition for this parameter is given below: SCIBillingChargingCharacteristics ::= CHOICE { chargeLevel [0] OCTET STRING (SIZE (min..max), chargePulses [1] Integer4, chargeMessages [2] OCTET STRING (SIZE (min..max) } Depending on the applied charging scenario the following information elements can be included (refer to Annex B): charge level (scenario 3.2) chargePulses (scenario 3.2) chargeMessages (scenario 3.2)

-- *** NCS implementation *** -- *** NOTE ! *** -- *** The following commented descriptions define ONLY the STRUCTURE of DATA *** -- *** in the operation. They are NOT ASN.1 coded presentation! *** -- SCIBillingChargingCharacteristics ::= SEQUENCE { -sciChType SCIChType, -sciChValue SCIChValue -} -- SCIChType ::= ENUMERATED {

180 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

--------

isupMessage (0), chargingLevel (1), chargingChangePercentage (2), chargingChangePulses (3), e-Parameters (4), withdrawPrecedingSCI (5) }

-- SCIChValue ::= CHOICE { -mpm -chg -chargingZone -changePercentage -changePulses -e-parameters -}

IsupMPM, IsupCHG, ChargingZone, ChangePercentage, ChangePulses, E-parameters

-- ChangePercentage ::= SEQUENCE { -direction OCTET STRING (SIZE (1)), -percentage INTEGER (0..255) -} -- ChangePulses ::= SEQUENCE { -direction OCTET STRING (SIZE (1)), -pulses ChargingPulses -} -- E-parameters ::= SEQUENCE { -e1 INTEGER (0..65535), -e2 INTEGER (0..65535), -e3 INTEGER (0..65535), -e4 INTEGER (0..65535), -e5 INTEGER (0..65535), -e6 INTEGER (0..65535), -e7 INTEGER (0..65535) -} -- **** DEFINITION OF ISUP (CHARGING) MESSAGES ********************************* -- IsupCHG ::= OCTET STRING (SIZE (4..19)) -- IsupMPM ::= OCTET STRING (SIZE (3)) - SFS 5779 - SFS 5779

-- **** THE DEFINITION OF COMMON DATA TYPES FOLLOWS **************************** -------------------------------------------------------------------------------AdditionalCallingPartyNumber ::= Digits -------------------------------------------------------------------------------AlertingPattern ::= OCTET STRING (SIZE (3)) -- Indicates a specific pattern that is used to alert a subscriber (for example, -- distinctive ringing, tones, etc.). Only applies if the SSF is the terminating -- local exchange for the subscriber. Refer to the Q.931 Signal parameter for -- encoding. -------------------------------------------------------------------------------ApplicationTimer ::= INTEGER (0..2047)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

181 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- Used by the SCF to set a timer in the SSF. The timer is in seconds. -------------------------------------------------------------------------------AssistingSSPIPRoutingAddress ::= Digits -- Indicates the destination address of the SRF for the assisting procedure. -------------------------------------------------------------------------------BCSMEvent ::= SEQUENCE { eventTypeBCSM [0] EventTypeBCSM, monitorMode [1] MonitorMode, legID [2] LegID OPTIONAL, dPSpecificCriteria [30] DPSpecificCriteria OPTIONAL } -- Indicates the BCSM Event information for monitoring. -------------------------------------------------------------------------------BearerCapability ::= CHOICE { bearerCap [0] OCTET STRING (SIZE (2..maxBearerCapabilityLength)) } -- Indicates the type of the bearer capability connection to the user. For - bearerCap, the value as described in -- DSS1 (Q.931)/ISUP (Q.763, User Service Information) shall be used.

-------------------------------------------------------------------------------CalledPartyNumber ::= OCTET STRING (SIZE (minCalledPartyNumberLength .. maxCalledPartyNumberLength )) -- Indicates the Called Party Number. Refer to Q.763 for encoding. -------------------------------------------------------------------------------CallingPartyNumber ::= OCTET STRING (SIZE (minCallingPartyNumberLength .. maxCallingPartyNumberLength )) -- Indicates the Calling Party Number. Refer to Q.763 for encoding. -------------------------------------------------------------------------------CallingPartysCategory ::= OCTET STRING (SIZE (1)) -- Indicates the type of the calling party (for example, operator, payphone, -- ordinary subscriber). Refer to Q.763 for encoding. -------------------------------------------------------------------------------Cause ::= OCTET STRING (SIZE (minCauseLength .. maxCauseLength)) --$ENTRY -- Indicates the cause for interface-related information. Refer to the Q.763 -- Cause parameter for encoding. For the use of Cause and Location values -- refer to Q.850. -------------------------------------------------------------------------------CGEncountered ::= ENUMERATED { manualCGencountered (1), scpOverload (2) } -- Indicates the type of the automatic code gapping encountered, if any. --------------------------------------------------------------------------------

182 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

CollectedDigits ::= SEQUENCE { minimumNbOfDigits maximumNbOfDigits endOfReplyDigit cancelDigit startDigit firstDigitTimeOut interDigitTimeOut errortreatment interruptableAnnInd voiceInformation voiceBack } ------

[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

INTEGER (1..127) INTEGER (1..127), OCTET STRING (SIZE OCTET STRING (SIZE OCTET STRING (SIZE INTEGER (1..127) INTEGER (1..127) ErrorTreatment BOOLEAN DEFAULT BOOLEAN DEFAULT BOOLEAN DEFAULT

DEFAULT 1, (1..2)) OPTIONAL, (1..2)) OPTIONAL, (1..2)) OPTIONAL, OPTIONAL, OPTIONAL, DEFAULT stdErrorAndInfo, TRUE, FALSE, FALSE

The use of voiceBack is network operator-specific. The endOfReplyDigit, cancelDigit, and startDigit parameters have been designated as OCTET STRING, and are to be encoded as BCD, one digit only, contained in the four least significant bits of the OCTET. The interpretation is service-dependent.

-------------------------------------------------------------------------------CollectedInfo ::= CHOICE { collectedDigits [0] CollectedDigits } -------------------------------------------------------------------------------ControlType ::= ENUMERATED { sCPOverloaded (0), manuallyInitiated (1) --***, comma commented out -- other values FFS } -------------------------------------------------------------------------------CorrelationID ::= Digits -- Used by the SCF for correlation with a previous operation. Refer to section 3 -- for a description of the procedures associated with this parameter. -------------------------------------------------------------------------------CounterAndValue ::= SEQUENCE { counterID [0] CounterID, counterValue [1] Integer4 } -------------------------------------------------------------------------------CountersValue ::= SEQUENCE SIZE (0..numOfCounters) OF CounterAndValue -------------------------------------------------------------------------------CounterID ::= INTEGER (0..numOfCounters-1) -- Indicates the counters to be increased. -- The counterIDs can be addressed by using the last digits of the dialled number. -------------------------------------------------------------------------------CriticalityType ::= ENUMERATED { ignore (0), abort (1) } -------------------------------------------------------------------------------CutAndPaste ::= INTEGER (0..22)

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

183 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- Indicates the number of digits to be deleted. - Section 6.4.2.16 for additional information.

Refer to Q.1214,

-------------------------------------------------------------------------------DateAndTime ::= OCTET STRING (SIZE (6)) -- Indicates, amongst others, the start time for activated service filtering. - Coded as YYMMDDHHMMSS with each digit being a coded BCD. The first octet - contains YY and the remaining items are sequenced following it. -- For example, 1993 September 30th, 12:15:01 would be encoded as: -- Bits HGFE DCBA -- leading octet 3 9 -9 0 -0 3 -2 1 -5 1 -1 0 -------------------------------------------------------------------------------DestinationRoutingAddress ::= SEQUENCE SIZE (1) OF CalledPartyNumber -- Indicates the Called Party Number. -------------------------------------------------------------------------------Digits ::= OCTET STRING (SIZE (minDigitsLength .. maxDigitsLength )) -- Indicates the address signalling digits. Refer to the Q.763 Generic Number -- and Generic Digits parameters for encoding. The coding of the subfields -- 'NumberQualifier' in Generic Number and 'Type Of Digits' in Generic Digits -- are irrelevant to the INAP. The ASN.1 tags are sufficient to identify -- the parameter. The ISUP format does not allow the exclusion of these subfields, -- therefore the value is network operator-specific. -- The following parameters should use Generic Number: -AdditionalCallingPartyNumber for InitialDP, -AssistingSSPIPRoutingAddress for EstablishTemporaryConnection, -calledAddressValue for all occurances, -callingAddressValue for all occurances -- The following parameters should use Generic Digits: -all other CorrelationID occurrences, -number VariablePart, -digitsResponse ReceivedInformationArg -------------------------------------------------------------------------------DisplayInformation ::= IA5String (SIZE (minDisplayInformationLength .. maxDisplayInformationLength )) -- Indicates the display information. -------------------------------------------------------------------------------DPSpecificCriteria ::= CHOICE { numberOfDigits [0] NumberOfDigits, applicationTimer [1] ApplicationTimer } ------The SCF may specify the number of digits to be collected by the SSF for the Collected Info event. When all the digits are collected, the SSF reports the event to the SCF. The SCF may set a timer in the SSF for the No Answer event. If the user doesn't answer the call within the allotted time, the SSF reports the event to the SCF.

184 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-------------------------------------------------------------------------------Duration ::= INTEGER (-2..86400) -- Values are seconds. Negative values denote a special value. Refer to the -- procedure description of the relevant operations for further information. -------------------------------------------------------------------------------ErrorTreatment ::= ENUMERATED { stdErrorAndInfo (0), help (1), repeatPrompt (2)} -- stdErrorAndInfo means returning the "ImproperCallerResponse" error -- in the event of an error condition during the collection of user info. -------------------------------------------------------------------------------EventSpecificInformationBCSM ::= CHOICE { collectedInfoSpecificInfo [0] CollectedInfoSpecificInfo, analyzedInfoSpecificInfo [1] AnalyzedInfoSpecificInfo, routeSelectFailureSpecificInfo [2] RouteSelectFailureSpecificInfo, oCalledPartyBusySpecificInfo [3] OCalledPartyBusySpecificInfo, oNoAnswerSpecificInfo [4] ONoAnswerSpecificInfo, oAnswerSpecificInfo [5] OAnswerSpecificInfo, oMidCallSpecificInfo [6] OMidCallSpecificInfo, oDisconnectSpecificInfo [7] ODisconnectSpecificInfo, tCalledPartyBusySpecificInfo [8] TCalledPartyBusySpecificInfo, tNoAnswerSpecificInfo [9] TNoAnswerSpecificInfo, tAnswerSpecificInfo [10] TAnswerSpecificInfo, tMidCallSpecificInfo [11] TMidCallSpecificInfo, tDisconnectSpecificInfo [12] TDisconnectSpecificInfo } CollectedInfoSpecificInfo ::= SEQUENCE { calledPartyNumber [0] CalledPartyNumber } AnalyzedInfoSpecificInfo ::= SEQUENCE { calledPartyNumber [0] CalledPartyNumber } RouteSelectFailureSpecificInfo ::= SEQUENCE { failureCause [0] Cause OPTIONAL } OCalledPartyBusySpecificInfo ::= busyCause [0] Cause } ONoAnswerSpecificInfo OAnswerSpecificInfo OMidCallSpecificInfo SEQUENCE { OPTIONAL

::= SEQUENCE {} ::= SEQUENCE {} ::= SEQUENCE {}

ODisconnectSpecificInfo ::= SEQUENCE { releaseCause [0] Cause

OPTIONAL

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

185 (196)

DX MSC/SSP/IP - SCP Interface Specification

} TCalledPartyBusySpecificInfo ::= SEQUENCE { busyCause [0] Cause OPTIONAL } TNoAnswerSpecificInfo TAnswerSpecificInfo TMidCallSpecificInfo ::= SEQUENCE {} ::= SEQUENCE {} ::= SEQUENCE {}

TDisconnectSpecificInfo ::= SEQUENCE { releaseCause [0] Cause }

OPTIONAL

-- Indicates the call related information specific to the event. -------------------------------------------------------------------------------EventTypeBCSM ::= ENUMERATED { origAttemptAuthorized (1), collectInfo (2), analyzedInformation (3), routeSelectFailure (4), oCalledPartyBusy (5), oNoAnswer (6), oAnswer (7), oMidCall (8), oDisconnect (9), oAbandon (10), termAttemptAuthorized (12), tCalledPartyBusy (13), tNoAnswer (14), tAnswer (15), tMidCall (16), tDisconnect (17), tAbandon (18) } ----Indicates the BCSM detection point event. Refer to Q.1214 _ 4.2.2.2 for additional information on the events. The values origAttemptAuthorized and termAttemptAuthorized can only be used for TDPs.

-------------------------------------------------------------------------------ExtensionArray ::= SEQUENCE SIZE (1..numOfExtensions) OF ExtensionField -------------------------------------------------------------------------------ExtensionField ::= SEQUENCE { exType INTEGER (1..255), -- shall identify the value of an - EXTENSION type criticality ENUMERATED { ignore (0), abort (1) } DEFAULT ignore, value [1] ANY DEFINED BY exType

186 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

} -- This parameter indicates an extension of an argument data type. Its contents -- are network operator-specific. -------------------------------------------------------------------------------ExtensionIdentifier ::= INTEGER (1..255) -------------------------------------------------------------------------------ForwardCallIndicators ::= OCTET STRING (SIZE (2)) -- Indicates the Forward Call Indicators. Refer to Q.763 for encoding. -------------------------------------------------------------------------------GapCriteria ::= CHOICE { calledAddressValue [0] Digits, gapOnService [2] GapOnService, calledAddressAndService [29] SEQUENCE { calledAddressValue [0] Digits, serviceKey [1] ServiceKey }, callingAddressAndService callingAddressValue serviceKey locationNumber } } ----[30] SEQUENCE { [0] Digits, [1] ServiceKey, [2] LocationNumber

OPTIONAL

Both calledAddressValue and callingAddressValue can be incomplete numbers, in the sense that a limited amount of digits can be given. For the handling of numbers starting with the same digit string, refer to the detailed procedure of the CallGap operation in section 3.3

-------------------------------------------------------------------------------GapOnService ::= SEQUENCE { serviceKey [0] ServiceKey } -------------------------------------------------------------------------------GapIndicators ::= SEQUENCE { duration [0] Duration, gapInterval [1] Interval } -Indicates the gapping characteristics. No gapping when gapInterval equals 0, and gap all calls when gapInterval equals-1. For further information regarding the meaning of specific values of duration and gapinterval, refer to the detailed procedure of the CallGap operation in section 3.3.

-------------------------------------------------------------------------------GapTreatment ::= CHOICE { informationToSend [0] InformationToSend, releaseCause [1] Cause, both [2] SEQUENCE { informationToSend [0] InformationToSend, releaseCause [1] Cause

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

187 (196)

DX MSC/SSP/IP - SCP Interface Specification

} } -- The default value for Cause is the same as in ISUP. -------------------------------------------------------------------------------HighLayerCompatibility ::= OCTET STRING (SIZE (highLayerCompatibilityLength)) -- Indicates the teleservice. For encoding, DSS1 (Q.931) is used. -------------------------------------------------------------------------------InbandInfo ::= SEQUENCE { messageID [0] MessageID, numberOfRepetitions [1] INTEGER (1..127) OPTIONAL, duration [2] INTEGER (0..32767) OPTIONAL, interval [3] INTEGER (0..32767) OPTIONAL } --The interval is the time in seconds between each pair of the repeated announcements. The duration is the total amount of time in seconds, including repetitions and intervals. The end of announcement is either the end of duration or numberOfRepetitions, whichever comes first. duration with value 0 indicates infinite duration.

-------------------------------------------------------------------------------InformationToSend ::= CHOICE { inbandinfo [0] InbandInfo, tone [1] Tone, displayInformation [2] DisplayInformation } -------------------------------------------------------------------------------Integer4 ::= INTEGER (0..2147483647) -------------------------------------------------------------------------------Interval ::= INTEGER (-1..60000) -- Units are milliseconds. A -1 value denotes infinite. -------------------------------------------------------------------------------InvokeID ::= INTEGER (-128..127) -- = InvokeIDType -- Operation invoke identifier. -------------------------------------------------------------------------------IPAvailable ::= OCTET STRING (SIZE (minIPAvailableLength .. maxIPAvailableLength )) -- defined by network operator. It indicates that the resource is available. -------------------------------------------------------------------------------IPRoutingAddress ::= CalledPartyNumber -- Indicates the routing address for the IP. -------------------------------------------------------------------------------IPSSPCapabilities ::= OCTET STRING (SIZE (minIPSSPCapabilitiesLength .. maxIPSSPCapabilitiesLength )) -- defined by network operator. It indicates the SRF resources available at - the SSP.

188 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-------------------------------------------------------------------------------LegID ::= CHOICE { sendingSideID [0] LegType, -- used in operations sent from SCF to SSF receivingSideID [1] LegType -- used in operations sent from SSF to SCF } -- Indicates a reference to a specific party in a call. OPTIONAL denotes network - operator specific use with a unilateral ID assignment. -- OPTIONAL for LegID also denotes the following: -- when only one party takes part in the call, this parameter is not needed - (as no ambiguity exists). - when more than one party takes part in the call, one of the following - alternatives applies: -1. LegID is present and indicates which party is concerned. -2. LegID is not present and a default value is assumed (for example, -calling party in the case of the ApplyCharging operation). -------------------------------------------------------------------------------LegType ::= OCTET STRING (SIZE (1)) leg1 LegType ::= '01'H leg2 LegType ::= '02'H -------------------------------------------------------------------------------LocationNumber ::= OCTET STRING (SIZE (minLocationNumberLength .. maxLocationNumberLength )) -- Indicates the Location Number for the calling party. Refer to Q.763 (White book) - for encoding. -------------------------------------------------------------------------------MaximumNumberOfCounters ::= INTEGER (1.. numOfCounters) -------------------------------------------------------------------------------MessageID ::= CHOICE { elementaryMessageID [0] Integer4, text [1] SEQUENCE { messageContent [0] IA5String (SIZE (minMessageContentLength .. maxMessageContentLength )), attributes [1] OCTET STRING (SIZE (minAttributesLength .. maxAttributesLength )) OPTIONAL }, elementaryMessageIDs [29] SEQUENCE SIZE (1..numOfMessageIDs) OF Integer4, variableMessage [30] SEQUENCE { elementaryMessageID [0] Integer4, variableParts [1] SEQUENCE SIZE (1..5) OF VariablePart } } -- OPTIONAL denotes network operator-specific use. -------------------------------------------------------------------------------MiscCallInfo ::= SEQUENCE { messageType [0] ENUMERATED { request (0) --$VNAME=req--,

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

189 (196)

DX MSC/SSP/IP - SCP Interface Specification

notification (1) --$VNAME=notif } --$CNAME=mesType } -- Indicates detection-point-related information. -------------------------------------------------------------------------------MonitorMode ::= ENUMERATED { interrupted (0), notifyAndContinue (1), transparent (2) } -----Indicates the event is relayed and/or processed by the SSP. If this parameter is used in the context of charging events, the following definitions apply for the handling of the charging events: Interrupted means that the SSF notifies the SCF of the charging event using EventNotificationCharging, and does not process the event but discards it. NotifyAndContinue means that the SSF notifies the SCF of the charging event using EventNotificationCharging, and continues processing the event or signal without waiting for the SCF instructions. Transparent means that the SSF does not notify the SCF of the event. This value is used to end the monitoring of a previously requested charging event. Previously requested charging events are monitored until ended by a transparent monitor mode, or until the end of the connection configuration.

-------------------------------------------------------------------------------NumberOfDigits ::= INTEGER (1..255) -- Indicates the number of digits to be collected -------------------------------------------------------------------------------OriginalCalledPartyID ::= OCTET STRING (SIZE (minOriginalCalledPartyIDLength .. maxOriginalCalledPartyIDLength )) -- Refer to the Q.763 Original Called Number for encoding. -------------------------------------------------------------------------------RedirectingPartyID ::= OCTET STRING (SIZE (minRedirectingPartyIDLength .. maxRedirectingPartyIDLength )) -- Indicates redirecting number. Refer to the Q.763 Redirecting number -- for encoding. -------------------------------------------------------------------------------RedirectionInformation ::= OCTET STRING (SIZE (2)) -- Indicates redirection information. Refer to the Q.763 Redirection -- Information for encoding. -------------------------------------------------------------------------------RequestedInformationList ::= SEQUENCE SIZE (1..numOfInfoItems) OF RequestedInformation -------------------------------------------------------------------------------RequestedInformationTypeList ::= SEQUENCE SIZE (1..numOfInfoItems) OF RequestedInformationType -------------------------------------------------------------------------------RequestedInformation ::= SEQUENCE {

190 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

requestedInformationType requestedInformationValue }

[0] RequestedInformationType, [1] RequestedInformationValue

-------------------------------------------------------------------------------RequestedInformationType ::= ENUMERATED { callAttemptElapsedTime (0), callStopTime (1), callConnectedElapsedTime (2), calledAddress (3), releaseCause (30) } -------------------------------------------------------------------------------RequestedInformationValue ::= CHOICE { callAttemptElapsedTimeValue [0] INTEGER (0..255), callStopTimeValue [1] DateAndTime, callConnectedElapsedTimeValue [2] Integer4, calledAddressValue [3] Digits, releaseCauseValue [30] Cause } -- The callAttemptElapsedTimeValue -- is specified in seconds. The unit for the callConnectedElapsedTimeValue is 100 - milliseconds. -------------------------------------------------------------------------------RouteList ::= SEQUENCE SIZE (1..3) OF OCTET STRING (SIZE (minRouteListLength .. maxRouteListLength )) -- Indicates the routing category information. -- The routing category information is transmitted in the leading octet of the - first RouteList SEQUENCE element; the other RouteList Sequence elements are - ignored. -------------------------------------------------------------------------------ScfID ::= OCTET STRING (SIZE (minScfIDLength .. maxScfIDLength )) -- defined by network operator. Indicates the SCF identifier. -------------------------------------------------------------------------------ServiceInteractionIndicators ::= OCTET STRING (SIZE - (minServiceInteractionIndicatorsLength..maxServiceInteractionIndicatorsLength)) -- Indicators which are exchanged between the SSP and the SCP to resolve - interactions between IN-based services and network-based services, - respectively. The contents are network-specific and identified as a subject for - further study with respect to the INAP. -------------------------------------------------------------------------------ServiceKey ::= Integer4 -- Information that allows the SCF to choose the appropriate service logic. -------------------------------------------------------------------------------SFBillingChargingCharacteristics ::= OCTET STRING (SIZE - (minSFBillingChargingLength .. maxSFBillingChargingLength )) -- This parameter indicates the billing and/or charging characteristics for - filtered calls.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

191 (196)

DX MSC/SSP/IP - SCP Interface Specification

-- Its content is network operator-specific. -------------------------------------------------------------------------------TimerID ::= ENUMERATED { tssf (0) } -- Indicates the timer to be reset. -------------------------------------------------------------------------------TimerValue ::= Integer4 -- Indicates the timer value (in seconds). -------------------------------------------------------------------------------Tone ::= SEQUENCE { toneID [0] Integer4, duration [1] Integer4 OPTIONAL } -- The duration specifies the length of the tone in seconds; the value 0 indicates - infinite duration. -------------------------------------------------------------------------------UnavailableNetworkResource ::= ENUMERATED { unavailableResources (0), componentFailure (1), basicCallProcessingException (2), resourceStatusFailure (3), endUserFailure (4) } -- Indicates the network resource that failed. -------------------------------------------------------------------------------VariablePart ::= CHOICE { integer [0] Integer4, number [1] Digits, -- Generic digits time [2] OCTET STRING (SIZE (2)), -- HH:MM, BCD coded date [3] OCTET STRING (SIZE (3)), -- YYMMDD, BCD coded price [4] OCTET STRING (SIZE (4)) -- DDDDDD.DD, BCD coded } --------------Indicates the variable part of the message. BCD coded variable parts are encoded as described in the examples below. For example, time = 12:15 would be encoded as: Bits HGFE DCBA leading octet 2 1 5 1 date = 1993 September 30th would be encoded as: Bits HGFE DCBA leading octet 3 9 9 0 0 3 price = ECU 249.50 would be encoded as: Bits HGFE DCBA leading octet 0 0

192 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Interface description: ASN definitions

-----

0 2 9 0

0 0 4 5

-- **** DEFINITION OF RANGE CONSTANTS ****************************************** -- Unused constants are commented out highLayerCompatibilityLength INTEGER minAChBillingChargingLength INTEGER maxAChBillingChargingLength INTEGER minAttributesLength INTEGER maxAttributesLength INTEGER maxBearerCapabilityLength INTEGER minCalledPartyNumberLength INTEGER maxCalledPartyNumberLength INTEGER minCallingPartyNumberLength INTEGER maxCallingPartyNumberLength INTEGER minCallResultLength INTEGER maxCallResultLength INTEGER minCauseLength INTEGER maxCauseLength INTEGER minDigitsLength INTEGER maxDigitsLength INTEGER minDisplayInformationLength INTEGER maxDisplayInformationLength INTEGER minEventSpecificInformationChargingLength maxEventSpecificInformationChargingLength minEventTypeChargingLength INTEGER maxEventTypeChargingLength INTEGER minFCIBillingChargingLength INTEGER maxFCIBillingChargingLength INTEGER minIPAvailableLength INTEGER maxIPAvailableLength INTEGER minIPSSPCapabilitiesLength INTEGER maxIPSSPCapabilitiesLength INTEGER minLocationNumberLength INTEGER maxLocationNumberLength INTEGER minMessageContentLength INTEGER maxMessageContentLength INTEGER minOriginalCalledPartyIDLength INTEGER maxOriginalCalledPartyIDLength INTEGER minRedirectingPartyIDLength INTEGER maxRedirectingPartyIDLength INTEGER minRouteListLength INTEGER maxRouteListLength INTEGER minScfIDLength INTEGER maxScfIDLength INTEGER minSCIBillingChargingLength INTEGER maxSCIBillingChargingLength INTEGER minServiceInteractionIndicatorsLength INTEGER maxServiceInteractionIndicatorsLength INTEGER minSFBillingChargingLength INTEGER maxSFBillingChargingLength INTEGER numOfBCSMEvents INTEGER numOfChargingEvents INTEGER

::= 2 ::= 1 ::= 11 ::= 1 ::= 1 ::= 11 ::= 3 ::= 18 ::= 2 ::= 18 ::= 4 ::= 63 ::= 2 ::= 12 ::= 2 ::= 33 ::= 1 ::= 80 INTEGER ::= 3 INTEGER ::= 19 ::= 1 ::= 1 ::= 2 ::= 313 ::= 1 ::= 1 ::= 2 ::= 10 ::= 3 ::= 18 ::= 1 ::= 82 ::= 2 ::= 18 ::= 2 ::= 18 ::= 2 ::= 2 ::= 2 ::= 10 ::= 1 ::= 20 ::= 1 ::= 10 ::= 4 ::= 20 ::= 10 ::= 4

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

193 (196)

DX MSC/SSP/IP - SCP Interface Specification

numOfCounters numOfCounters-1 numOfExtensions numOfInfoItems numOfMessageIDs END

INTEGER INTEGER INTEGER INTEGER INTEGER

::= ::= ::= ::= ::=

100 99 10 5 5

194 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en

Support protocol description

Support protocol description


The Core INAP protocol handler in the DX 200 MSC/SSP uses the White Book TC. The following rules apply for the SSF:
.

The SSF anticipates an error/reject message from the SCF in the TC-END primitive. If the SCF sends an error/reject message in the TC-CONTINUE primitive, the SSF terminates the SSF-SCF relationship by sending the TC-U-ABORT primitive. If the SSF detects an error, for example, in a parameter of a Core INAP operation, and sends the TC-U-ERROR primitive to the SCF, the SSF discards all the operations that the SCF has sent so far, and starts to handle the operation that was received after the error had been reported to the SCF.

If the INAP protocol handler in the SSP receives an operation that is not supported by the SSP, it sends the TC-U-REJECT in the TC-END to the SCP. If the not supported operation is received in the TC message, which also contains the supported operations, it is handled in the normal way. On the use of the SCCP The subsystem number used by Core INAP is 0C hex (12 decimal). For configuration options of this parameter see MSC/SSP Core INAP configuration data section. The SCCP service class is '1'. This means that the successive TC messages sent from the SSP are received in sequence in the SCP. The SCCP return option is 'in use'. This means that the signalling network returns to the SSP the messages that cannot be routed to the destination SCP.

DN00212979 Issue 6-0 en

# Nokia Siemens Networks

195 (196)

DX MSC/SSP/IP - SCP Interface Specification

SCCP Global Title Transition (GTT) load sharing between the 16 GTT results is available. It requires the use of different GTs during dialogue initiation and continuation, for example, the dialogues are initiated with the Service GT and continued with the SCP-node GTs.

196 (196)

# Nokia Siemens Networks

DN00212979 Issue 6-0 en