Package jain.protocol.ss7.tcap.dialogue

This package contains the Event classes representing the JAIN TCAP Dialogue Handling primitives and their specific parameters, if a paramater is not included in any specific primitive, it is common to all the specified dialogues and therefore coded within that dialogues parent class.

See:
Description

Class Summary

BeginIndEvent	An event representing a TCAP Begin indication dialogue primitive.
BeginReqEvent	An event representing a TCAP Begin request dialogue primitive.
ContinueIndEvent	An event representing a TCAP Continue indication dialogue primitive.
ContinueReqEvent	An event representing a TCAP Continue request dialogue primitive.
DialogueConstants	This class contains the common Constants used throughout the package jain.protocol.ss7.tcap.dialogue
DialoguePortion	This class represents the optional Dialogue Portion of a dialogue handling primitive.
EndIndEvent	An event representing a TCAP End indication dialogue primitive.
EndReqEvent	An event representing a TCAP End request dialogue primitive.
NoticeIndEvent	An event representing a TCAP Notice indication dialogue primitive.
ProviderAbortIndEvent	An event representing a TCAP ProviderAbort indication dialogue primitive.
UnidirectionalIndEvent	An event representing a TCAP Unidirectional indication dialogue primitive.
UnidirectionalReqEvent	An event representing a TCAP Unidirectional Request dialogue primitive.
UserAbortIndEvent	An event representing a TCAP UserAbort indication dialogue primitive.
UserAbortReqEvent	An event representing a TCAP UserAbort request dialogue primitive.

Package jain.protocol.ss7.tcap.dialogue Description

This package contains the Event classes representing the JAIN TCAP Dialogue Handling primitives and their specific parameters, if a paramater is not included in any specific primitive, it is common to all the specified dialogues and therefore coded within that dialogues parent class. The parent classes can be either DialogueIndEvent or DialogueReqEvent depending on whether the dialogue is an indication or request primitive where:

• Indication Dialogue handling primitives - are primitives that can only be sent from a JainTcapProvider. to a JainTcapListener
• Request Dialogue handling primitives - are primitives that can only be sent from a JainTcapListener to a JainTcapProvider.

A generic set of Dialogue handling primitives has been created that abstracts the functionality of the Dialogue handling primitives for the supported variants. The mapping between these generic primitives and the variant specific primitives they represent is illustrated in Table 1:

Request Primitives	Indication Primitives	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
UnidirectionalReqEvent	UnidirectionalIndEvent	TC_UNI		TC_UNI
BeginReqEvent	BeginIndEvent	TC_BEGIN		TC_QWP TC_QWOP
ContinueReqEvent	ContinueIndEvent	TC_CONTINUE		TC_CWP TC_CWOP
EndReqEvent	EndIndEvent	TC_END		TC_RESPONSE
	ProviderAbortIndEvent	TC_P_ABORT		TC_P_ABORT
UserAbortReqEvent	UserAbortIndEvent	TC_U_ABORT		TC_U_ABORT
	NoticeIndEvent	TC_NOTICE

Table 1 Mapping of Dialogue handling primitives
NOTE:

• The ANSI protocol varient includes granting permission to the remote Nodes, in order to release (terminate) a dialogue between two TC_User applications. To allow for this concept, the BeginReqEvent, BeginIndEvent, ContinueReqEvent and ContinueIndEvent primitives each include a flag 'allowedPermission', which indicates if permission has been granted to that specific primitive.

Mapping of JAIN Mandatory and Optional parameters of Component primitives

The following tables identify the mapping between the ITU and ANSI TCAP Component primitives and parameters. The standards supported in JAIN TCAP v1.0 include:

• ITU-T (03/93) Q series (Q.771-775) � SS7 Functional description of Transaction Capabilities.

• ITU-T (06/97) Q series (Q.771-775) � SS7 Functional description of Transaction Capabilities.

• ANSI (1992) T1.114.1 - T1.114.5 � SS7 Transaction Capabilities Application Part.

• ANSI (1996) T1.114.1 - T1.114.5 � SS7 Transaction Capabilities Application Part.

Mandatory and Optional Parameters

Each of the supported standards defines mandatory and optional parameters for each primitive. As JAIN TCAP supports all the mandatory and optional parameters of each primitive of the supported variants within the one specification, it is necessary to redefine the mandatory and optional parameters of the standards. This new definition of mandatory and optional parameters will be referred to as JAIN TCAP mandatory and optional and will accommodate the mandatory and optional parameter differences within the standards supported.

JAIN TCAP MANDATORY: A JAIN TCAP mandatory parameter is a parameter within a primitive that is mandatory for all the supported variants. In the tables below if any parameter is mandatory (M) for all the variants then it will be mandatory for that JAIN TCAP primitive.

JAIN TCAP OPTIONAL: A JAIN TCAP optional parameter is a parameter within a primitive that is either optional or not supported by any of the supported variants. In the tables below if a parameter is regarded as mandatory for a specific variant and optional or not supported by the other variant it will be regarded as a JAIN TCAP optional.

Table Key:
M = mandatory
O = optional
Blank = not-supported

[1] Dialogue Portion contains the remaining optional ITU parameters: Application Context Name, User Information.

[2] The Dialogue ID maps onto the (Originating and Destination) Transaction IDs exchanged in the messages between a pair of nodes, therefore from a JAIN perspective, a dialogue ID is exchanged between provider and listener for both variants, and an ANSI implementation of the JAIN TCAP provider will handle the mapping to the Originating and Destination Transaction Ids.

[3] The Dialogue ID in a UNI Request has local significance only and may have the zero as its value.

[4] A UNI Indication event in the JAIN TCAP API specification is the only Dialogue Indication Event that does not use a Dialogue Id within all the supported variants.

[5] Specific to the ANSI TCAP standards only.

Unidirectional Request	TC_UNI		TC_UNI
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M [3]	M [3]	M [3]	M [3]
Originating Address	M	M	M	M
Destination Address	M	M	M	M
DialoguePortion	O [1]	O [1]		O

Table 2 : Mapping of the Unidirectional Request Dialogue Parameters

Unidirectional Indication	TC_UNI		TC_UNI
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Originating Address	M	M	M	M
Destination Address	M	M	M	M
DialoguePortion	O [1]	O [1]		O
Components Present	M	M	M	M
Dialogue Id	[4]	[4]	[4]	[4]

Table 3 : Mapping of the Unidirectional Indication Dialogue Parameters

Begin Req	TC_BEGIN		TC_QWP TC_QWOP
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Originating Address	M	M	M	M
Destination Address	M	M	M	M
DialoguePortion	O [1]	O [1]		O

Table 4 : Mapping of the Begin Request Dialogue Parameters

BeginInd	TC_BEGIN		TC_QWP TC_QWOP
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Originating Address	M	M	M	M
Destination Address	M	M	M	M
Components Present	M	M	M	M
DialoguePortion	O [1]	O [1]		O

Table 5 : Mapping of the Begin Indication Dialogue Parameters

Continue Request	TC_CONTINUE		TC_CWP TC_CWOP
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Originating Address	O	O	O	O
DialoguePortion	O [1]	O [1]		O

Table 6 : Mapping of the Continue Request Dialogue Parameters

Continue Ind	TC_CONTINUE		TC_CWP TC_CWOP
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
DialoguePortion	O [1]	O [1]		O
Components Present	M	M	M	M

Table 7 : Mapping of the Continue Indication Dialogue Parameters

EndReq	TC_END		TC_RESPONSE
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Termination	M	M
DialoguePortion	O [1]	O [1]		O

Table 8 : Mapping of the End Request Dialogue Parameters

EndInd	TC_END		TC_RESPONSE
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Components Present	M	M	M	M
DialoguePortion	O [1]	O [1]		O

Table 9 : Mapping of the End Indication Dialogue Parameters

UserAbort Request	TC_U_ABORT		TC_U_ABORT
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Abort Reason	O	O
User Abort Information			M	M
DialoguePortion	O	O		O

Table 10 : Mapping of the User Abort Request Dialogue Parameters

UserAbort Ind	TC_U_ABORT		TC_U_ABORT
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
Abort Reason	O	O
User Abort Information			M	M
DialoguePortion	O	O		O

Table 11 : Mapping of the User Abort Indication Dialogue Parameters

ProviderAbort Ind	TC_P_ABORT		TC_P_ABORT
	ITU 1993	ITU 1997	ANSI 1992	ANSI 1996
Quality Of Service	O	O
Dialogue Id	M	M	M [2]	M [2]
P Abort Cause	M	M	M	M
DialoguePortion	O	O		O

Table 12 : Mapping of the Provider Abort Indication Dialogue Parameters

Notice Ind	TC_NOTICE
	ITU 1993	ITU 1997
Dialogue Id	M	M
Report Cause	M	M
Originating Address		O
Destination Address		O

Table 13 : Mapping of the Notice Indication Dialogue Parameters

Dialogue Portion
Protocol Version	O
Application Context Name	O
Security Context Information	O[5]
Confidentiality Information	O[5]
User Information	O[5]

Table 14 : Mapping of the Dialogue Portion Dialogue Parameters

Timer Reset Ind
Invoke Id	M
Dialogue Id	M

Table 15 : Mapping of the Timer Reset Indication Dialogue Parameters