Copyright - 1999 Sun Microsystems, Inc. All rights reserved.
901 San Antonio Road, Palo Alto, California 94043, U.S.A.
This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
TRADEMARKS
Sun, the Sun logo, Sun Microsystems, Java, Java Compatible, JavaBeans, Solaris,Write Once, Run Anywhere, JDK, Java Development Kit, and JavaStation are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and certain other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. All other product names mentioned herein are the trademarks of their respective owners.
THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
The purpose of this document is to2.1 Support SoftwareThe JAIN TCAP RI will emulate the functions of an SS7 stack (but will not be an SS7 stack) in order to verify the requirements within this specification. The intention of the JAIN TCAP RI is not to implement an SS7 stack or to replace vendor SS7 stacks. The purpose of the JAIN TCAP RI is to provide a means to verify that JAIN TCAP applications are compatible with the JAIN TCAP specification. The RI can be used in order to help develop a JTAIN TCAP application. The JAIN TCAP RI (here after referred to as RI) handles 'normal' TCAP message sequencing, however, it performs some limited checking.
- Outline the requirements for setting up the Reference Implementation (RI) which JAIN TCAP applications can run against.
- List the scope, limitations and restrictions of the JAIN TCAP RI.
Several classes developed with JDK1.2 and the JAIN TCAP API specification will be used while running the RI. This implementation will satisfy the following requirement as listed in the JAIN TCAP Requirement Specification.REQ-RR-01-01: In order to execute the JAIN TCAP Compatibility Test Suite, or a JAIN TCAP application, the following shall be required:
1. The Reference Implementation is utilised by implementing a JAIN TCAP API specification.
2. Java Virtual Machine
After the initial setup, the JAIN TCAP Application should be capable of sending Red events to the RI and receiving Ind Events with corresponding parameters set from RI, see Section 4.0.
Messages are sent from an Application through the RI, to the addressed to a Destination node. Any messages sent from the Application will be expected to be routed through the RI to the Destination node. The destination node may be the same Application or another Application with the same Signaling Point Code but different Sub System Number (SSN). The RI can handle a multiple listener to provider relationship [see Figure 4.1].
In order to send events the Application running against the RI will construct Request Events i.e. Dialogues and some (if any) associated Components.
These Events are passed to the RI's Provider (here after referred to as RI_Provider) by invoking : sendComponentReqEvent(componentRequest)The events are passed as parameter arguments within the method calls.
sendDialogueReqEvent(dialogueRequest).
The RI_Provider accepts these events. If a component is received it will added to the ComponentRequest Table. It is stored relative to that component's DialogueId. If other components with the same DialogueId have previously been received it is stored referenced by this index, otherwise it is added as a new entry in the table. A received Dialogue triggers the sending of associated components (i.e. those with the same Dialogue ID as the received Dialogue). [see Figure 4.2].
Any associated Components are passed to the Convertor. This converts the Requests to Indication events. The Component Indications are passed to the Component Indication table and stored in a similar fashion to the Component Request table.
The Dialogue is converted to an Dialogue Indication event and passed to the Application by invoking the Application's processDialogueReqEvent(dialogueInd).
The associated components are then passed to the Application by invoking the Application's processDialogueReqEvent(componentInd).
The RI does not have all the functionality of a TCAP stack. It handles normal TCAP message sequencing and some abnormal conditions.It can handle the following Request primitives
It will return the appropriate Indication type with corresponding parameters set.
- Unidirectional Request Event
- Begin Request Event
- Continue Request Event
- End Request Event
- UserAbort Request Event
- Invoke Request Event
- Result Request Event
- Error Request Event
- Reject Request Event
- User Cancel Request Event
Examples message sequences
![]()
Figure 5.1 Message exchange for an unstructured Unidirectional dialogue.
![]()
Figure 5.2 Message exchange for an structured Begin dialogue.
![]()
Figure 5.3 Message exchange for an Abort dialogue.
- This release of RI does not have the functionality to handle a multiple provider
- This release of RI will return only Mandatory and any Optional parameters for the protocol variant it is running on, e.g. ITU, ANSI.
Abbreviations
ANSI | American National Standards Institute |
API | Application Programming Interface |
CTS | Capability Test Suite |
ITU | International Telecommunications Union |
JAIN | Java APIs for Integrated Network Framework |
JDK | Java Development Toolkit |
TCAP | Transaction Capabilities Application Part |
RI | Reference Implementation |
Document ID: RI-JAINTCAP-001 Version: 1.0a Location: Mercury::/project/jain/Dev/TCAP_CTS_RI/RI_Web/RI.html Originator KP Yong Approval Date: Status: Draft Approver:
Copyright - 1999 Sun Microsystems
01 September 99