1 General
1.1 Introduction
Ericsson Signaling SS7 is compliant with:
- Ericsson INAP CS1+. The Ericsson INAP CS1+ is described in Reference [1], Reference [2] and Reference [3] according to the tables in this document.
1.2 Concept
The terms that will be used are:
| C | Module complies with the specified paragraph in the standard | |
| N | Module does not comply with the specified paragraph in the standard | |
| P | Module complies partly with the specified paragraph in the standard | |
| - | There is nothing to implement in the referred paragraph (used in column “ C” ) | |
1.3 History
|
Rev |
Date |
Author |
Comments |
|---|---|---|---|
|
A |
2012-04-20 |
XALENAL |
First version |
2 Compliance Lists
2.1 Ericsson INAP CS1+
2.1.1 Ericsson INAP CS1+, Abstract Syntax, 2/15517-CRT 249 09 Uen, Rev B
|
References |
C |
N |
P |
Comments |
|---|---|---|---|---|
|
GENERAL INFORMATION |
- |
|
|
|
|
INTRODUCTION |
- |
|
|
|
|
REVISION INFORMATION |
- |
|
|
|
|
REFERENCES |
- |
|
|
|
|
CONCEPTS |
- |
|
|
|
|
Remote Operations (ROS) |
X |
|
|
|
|
Abstract Syntax Notation |
- |
|
|
|
|
Basic Encoding Rules |
X |
|
|
|
|
Operation Acronyms |
- |
|
|
|
|
FUNCTION |
- |
|
|
|
|
GENERAL INFORMATION |
X |
|
|
|
|
ABSTRACT SYNTAX OF ERICSSON INAP CS1+ |
- |
|
|
|
|
Operations |
|
|
X |
|
|
Operation Timers |
X |
|
|
|
|
Errors |
|
|
X |
|
|
Argument Data Types |
|
|
X |
|
|
Common Data Types |
|
|
X |
|
|
Codes |
X |
|
|
|
|
Application Contexts |
|
|
X |
|
|
EXPANDED ASN.1 SOURCE OF ERICSSON INAP CS1+ |
|
|
X |
|
|
OPERATIONAL CONDITIONS |
- |
|
|
|
|
EXTERNAL CONDITIONS |
- |
|
|
|
|
APPLICATION PARAMETERS |
- |
|
|
|
|
COMMANDS |
- |
|
|
|
|
PRINTOUTS |
- |
|
|
|
|
SUBSCRIBER PROCEDURES |
- |
|
|
|
|
SUBSCRIBER CATEGORIES |
- |
|
|
|
|
CHARGING |
- |
|
|
|
|
CAPABILITIES |
- |
|
|
|
2.1.2 Ericsson INAP CS1+, Operation and Parameter Descriptions, Detailed Operation Procedures, 3/15517-CRT 249 09 Uen, Rev B
|
References |
C |
N |
P |
Comments |
|---|---|---|---|---|
|
GENERAL INFORMATION |
- |
|
|
|
|
INTRODUCTION |
- |
|
|
|
|
REVISION INFORMATION |
- |
|
|
|
|
REFERENCES |
- |
|
|
|
|
CONCEPTS |
- |
|
|
|
|
FUNCTION |
- |
|
|
|
|
GENERAL RULES FOR OPERATION EXECUTION |
|
|
X |
|
|
- 2.39 |
|
|
X |
|
|
OPERATIONAL CONDITIONS |
- |
|
|
|
|
EXTERNAL CONDITIONS |
- |
|
|
|
|
APPLICATION PARAMETERS |
- |
|
|
|
|
COMMANDS |
- |
|
|
|
|
PRINTOUTS |
- |
|
|
|
|
SUBSCRIBER PROCEDURES |
- |
|
|
|
|
SUBSCRIBER CATEGORIES |
- |
|
|
|
|
CHARGING |
- |
|
|
|
|
CAPABILITIES |
- |
|
|
|
2.1.3 Ericsson INAP CS1+, Services Assumed from TCAP, 4/15517-CRT 249 09 Uen, Rev A
|
References |
C |
N |
P |
Comments |
|---|---|---|---|---|
|
GENERAL INFORMATION |
- |
|
|
|
|
INTRODUCTION |
- |
|
|
|
|
REVISION INFORMATION |
- |
|
|
|
|
REFERENCES |
- |
|
|
|
|
CONCEPTS |
- |
|
|
|
|
FUNCTION |
- |
|
|
|
|
GENERAL INFORMATION |
- |
|
|
|
|
NORMAL PROCEDURES |
X |
|
|
|
|
- |
|
|
| |
|
SSF-FSM Related Messages, Initiating SSP |
|
|
X |
|
|
SSF-FSM Related Messages, Assist/Hand-Off SSP |
|
|
X |
|
|
SSME-FSM Related Messages |
|
|
X |
|
|
- |
|
|
| |
|
SCF-FSM Related Messages |
|
|
X |
|
|
SCME-FSM Related Messages |
X |
|
|
|
|
|
|
X |
| |
|
X |
|
|
| |
|
|
|
X |
||
|
SCF to SDF Messages |
X |
|
|
|
|
SDF to SCF Messages |
X |
|
|
|
|
ABNORMAL PROCEDURES |
X |
|
|
|
|
SCF to SSF/SRF/SDF Messages |
|
|
X |
|
|
SSF/SRF/SDF to SCF Messages |
|
|
X |
|
|
DIALOGUE ESTABLISHMENT |
X |
|
|
|
|
Sending of a TC-BEGIN-Req Primitive |
X |
|
|
|
|
Receipt of a TC-BEGIN-Ind Primitive |
X |
|
|
|
|
Receipt of the first TC-CONTINUE-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-END-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-U-ABORT-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-P-ABORT-Ind Primitive |
X |
|
|
|
|
DIALOGUE CONTINUATION |
X |
|
|
|
|
Sending Entity |
X |
|
|
|
|
Receiving Entity |
X |
|
|
|
|
DIALOGUE TERMINATION |
X |
|
|
|
|
Sending a TC-END-Request |
X |
|
|
|
|
Receipt of a TC-END-Ind Primitive |
X |
|
|
|
|
USER ABORT |
X |
|
|
|
|
Sending a TC-U-ABORT-Req Primitive |
X |
|
|
|
|
Receipt of a TC-U-ABORT-Ind Primitive |
X |
|
|
|
|
PROVIDER ABORT |
X |
|
|
|
|
Receipt of a TC-P-ABORT-Ind Primitive |
X |
|
|
|
|
PROCEDURES FOR INAP OPERATIONS |
- |
|
|
|
|
Operation Invocation |
X |
|
|
|
|
Operation Invocation Receipt |
X |
|
|
|
|
Operation Response |
X |
|
|
|
|
Receipt of a Response |
- |
|
|
|
|
Receipt of a TC-RESULT-NL-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-RESULT-L-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-U-ERROR-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-U-REJECT-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-R-REJECT-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-L-REJECT-Ind Primitive |
X |
|
|
|
|
Receipt of a TC-L-CANCEL-Ind Primitive |
X |
|
|
|
|
Other Events |
- |
|
|
|
|
Receipt of a TC-NOTICE-Ind Primitive |
X |
|
|
|
|
MAPPING ONTO TC SERVICES |
- |
|
|
|
|
Dialogue Control |
X |
|
|
|
|
Destination Address |
X |
|
|
|
|
Originating Address |
X |
|
|
|
|
Dialogue ID |
X |
|
|
|
|
Application Context Name |
|
|
X |
|
|
User Information |
X |
|
|
|
|
Component Present |
X |
|
|
|
|
Termination |
X |
|
|
|
|
Quality of Service |
X |
|
|
|
|
Operation Procedures |
- |
|
|
|
|
Invoke ID |
X |
|
|
|
|
Linked ID |
X |
|
|
|
|
Dialogue ID |
X |
|
|
|
|
Class |
X |
|
|
|
|
Operation |
X |
|
|
|
|
Error |
X |
|
|
|
|
Parameters |
X |
|
|
|
|
Time Out |
X |
|
|
|
|
Last Component |
X |
|
|
|
|
Problem Code |
X |
|
|
|
|
OPERATIONAL CONDITIONS |
- |
|
|
|
|
EXTERNAL CONDITIONS |
- |
|
|
|
|
APPLICATION PARAMETERS |
- |
|
|
|
|
COMMANDS |
- |
|
|
|
|
PRINTOUTS |
- |
|
|
|
|
SUBSCRIBER PROCEDURES |
- |
|
|
|
|
SUBSCRIBER CATEGORIES |
- |
|
|
|
|
CHARGING |
- |
|
|
|
|
CAPABILITIES |
- |
|
|
|
3 Notes and Comments
| Note 1 | SSF functionality is partially implemented. | |
Application Context supported for SSF : INAP-CS1plus-SSP-to-SCP-AC Rev 0 and Rev 1.
Operation supported (This operations can be used without AC for Blue TCAP):
- InitialDP
- ApplyCharging
- ApplyChargingReport
- CallGap
- CallInformationRequest
- CallInformationReport
- CollectInformation
- Connect
- ConnectToResource
- Continue
- DisconnectForwardConnection
- EstablishTemporaryConnection
- EventNotificationCharging
- EventReportBCSM
- FurnishChargingInformation
- ReleaseCall
- RequestNotificationChargingEvent
- RequestReportBCSMEvent
- ResetTimer
- SendChargingInformation
- HandOver
- HoldCallPartyConnection
- Reconnect
- ReleaseCallPartyConnection
- SignallingInformation
| Note 2 | This chapter describes the same functionality as ch. 2.2. See statements for ch.2.2 and its subclauses. | |
| Note 3 | The INAP module relies on the application to do its part. The INAP module handles message coding, message decoding and validation. The INAP module mainatains state information related to the dialogue only. | |
| Note 4 | The INAP module does not have the same FSMs as are described in Ericsson INAP CS1+, Operation and Parameter Descriptions, Detailed Operation Procedures, 3/15517-CRT 249 09 Uen, rev B. The INAP module mainatains state information related to the dialogue only. | |
| Note 5 | The INAP module does not maintain information about “ views” . | |
| Note 6 | This rule is supported but not enforced by INAP. | |
| Note 7 | The statement for this chapter does not concern functionality described in chapters that this chapter refers to. See statement(s) for the referred chapter(s) for the functionality described there. | |
| Note 8 | TC-NOTICE-Ind is supported but the Return Option is set by the INAP user. | |
| Note 9 | The Dialogue ID parameter sent out in the network is chosen by TC. The Dialogue ID used in the user interface for incoming dialogues is also chosen by TC. The Dialogue ID used in the user interface for outgoing dialogues is chosen by the INAP user. | |
| Note 10 | Network specific application context names are not supported. | |
| Note 11 | “ In sequence delivery” not requested and/or “ Message Return Option” requested may also be used. | |
| Note 12 | INAP always notifies the INAP user. | |
| Note 13 | Supports also Application Contexts revisionA set to 1. | |

Contents