Team Members & Roles:

TPC (Third Party Call) Gateway System Middleware

     TPC is one of the promising services that enable the internet web server to control 
     he call for voice service  between two pre-registered subscribers. It can make advanced
     stock trading, internet shopping and many other services  to be possible. These kinds of services
     require the internetworking technology between internet and telecommunication network.
     TPC gateway is the call control system that allows the third party call from web severs to
     setup the call between caller and callee. It has several network protocols for the functionality.
     TPC gateway is for that purpose. Hence, the system should satisfy reliability, real-time, and high performance.
     In this project, we focus on the three requirements and other things such as network protocol, 
     caller, and callee that will play their roles in simulated TPC service.
  

Configuration:

• Middleware: CORBA (Java ORB)
• Operating system: Linux(UNIX) Server
• Language: Java

System Architecture:

Inital Baseline Requirement

Baseline Application Features:

• The call request from the web server should be set up between a caller and a callee.
• The result of call setup should be notified to the web sever.
• The 3 consecutive call setup should be executed with regular interval in case of callee is busy.

Fault-Tolerance Requirements (FT)

• The call request should be preserved on the system failure.
• Function should still run even if one gateway system is crashed.
• The failed system should be recovered form crash.

Real-Time Requirements (RT)

• The call setup should be completed average in 1 sec.
• Process recovery from crash should be in 5 sec.
• Node(Network, Hardware, CORBA, etc) recovery from crash should be in 1min.

High Performance Requirement (HP)

• Number of the concurrent call request for the web-server should be more than 20.
• 100 call setup should be completed in 30 sec.
• 30 call setup in worst case and 100 call setup in normal case should be guaranteed.

Baseline Application

1. Method (Interface)

• bool createCall(callerNum,calleeNum)
• bool ordReleaseCall()
• bool setupCall(destNum), bool askReleaseCall(destNum)
• bool sendVoice(message)

2. Attribute (Structure)

• The number of ongoing transaction
• The number of successful call setup
• The call duration per a caller or a Callee

3. Exception (error messages)

• When TPC Gateway Server is unavailable
• When wrong number is received from a call generator
• When a user is busy (a Caller or a Callee)

4. Status Definition

• Caller, Callee state : IDLE, BUSY
• Middleware Status : NORMAL, ERROR

5. Data Storing

• Volatile : Call Duration( ID|Setup Time| EndTime)
• Static : Subscriber lookup(ID|IOR)

Behavior of each interface

Fault-Tolerant Baseline Application

Failure Scenarios/Failover/Fault Detetion

Fault Tolerance Test Doc(Scenarios/Interactions)-Mar/16/2005

Fault Baseline Java Sourrc File-Mar/16/2005

Current Status

Downloads

Real-Time Fault-Tolerant Baseline Application

Current Status

Downloads

High-Performance Real-Time Fault-Tolerant Baseline Application

Performance Test

Downloads