|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
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.tcap.dialogue |
DialoguePortion | This class represents the optional Dialogue Portion of an ANSI 96 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. |
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:
Request Primitives | Indication Primitives | ITU æ93 | ITU æ97 | ANSI æ92 | ANSI æ96 |
UnidirectionalReqEvent | UnidirectionalIndEvent |
|
|
||
BeginReqEvent | BeginIndEvent |
|
TC_QWOP |
||
ContinueReqEvent | ContinueIndEvent |
|
TC_CWOP |
||
EndReqEvent | EndIndEvent |
|
|
||
ProviderAbortIndEvent |
|
|
|||
UserAbortReqEvent | UserAbortIndEvent |
|
|
||
NoticeIndEvent |
|
Table 1 Mapping of Dialogue handling primitives
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:
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.
[4] A UNI Indication event is the only Dialogue Indication Event that does not use a Dialogue Id within the supported variants. However for the JAIN TCAP API specification the Dialogue Id will be included to associate Component Events with this Dialogue Event, hence simplifing the implementation of a JAIN TCAP application.
Unidirectional Request |
TC_UNI |
TC_UNI |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
Quality Of Service |
O |
O |
|
|
Dialogue Id |
M [3] |
M [3] |
O |
O |
Originating Address |
M |
M |
M |
M |
Destination Address |
M |
M |
M |
M |
DialoguePortion |
O [1] |
O [1] |
O |
Unidirectional Indication |
TC_UNI |
TC_UNI |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
M |
M |
M |
M |
Begin Req |
TC_BEGIN |
TC_QWP |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
BeginInd |
TC_BEGIN |
TC_QWP |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
Continue Request |
TC_CONTINUE |
TC_CWP |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
Continue Ind |
TC_CONTINUE |
TC_CWP |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
EndReq |
TC_END |
TC_RESPONSE |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
Quality Of Service |
O |
O |
||
Dialogue Id |
M |
M |
M [2] |
M [2] |
Termination |
M |
M |
||
DialoguePortion |
O [1] |
O [1] |
O |
EndInd |
TC_END |
TC_RESPONSE |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
UserAbort Request |
TC_U_ABORT |
TC_U_ABORT |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
UserAbort Ind |
TC_U_ABORT |
TC_U_ABORT |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
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 |
ProviderAbort Ind |
TC_P_ABORT |
TC_P_ABORT |
||
ITU ‘93 |
ITU ‘97 |
ANSI ‘92 |
ANSI ‘96 |
|
Quality Of Service |
O |
O |
||
Dialogue Id |
M |
M |
M [2] |
M [2] |
P Abort Cause |
M |
M |
M |
M |
DialoguePortion |
O |
O |
O |
Notice Ind |
TC_NOTICE |
|
ITU ‘93 |
ITU ‘97 |
|
Dialogue Id |
M |
M |
Report Cause |
M |
M |
Originating Address |
O |
|
Destination Address |
O |
Dialogue Portion |
|
Protocol Version |
O |
Application Context Name |
O |
Security Context Information |
O |
Confidentiality Information |
O |
User Information |
O |
Timer Reset Ind |
|
Invoke Id |
M |
Dialogue Id |
M |
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |