Browse Prior Art Database

Use of AIX Processes to Support TCPIP Layers

IP.com Disclosure Number: IPCOM000123311D
Original Publication Date: 1998-Sep-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 100K

Publishing Venue

IBM

Related People

De Leeuw, A: AUTHOR [+2]

Abstract

AIN (Advanced Intelligent Network) allows the rapid development of telephony applications in response to customer requirements. This is achieved by moving the application's runtime environment from the multiple switches of different manufacturers to a device that can attach to all these switches. Hence the application need only be developed once and not on a per switch basis.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Use of AIX Processes to Support TCPIP Layers

   AIN (Advanced Intelligent Network) allows the rapid
development of telephony applications in response to customer
requirements.  This is achieved by moving the application's runtime
environment from the multiple switches of different manufacturers to
a device that can attach to all these switches.  Hence the
application need only be developed once and not on a per switch
basis.

   A key component of AIN is the connection between a Service
Control Point (SCP), which controls how an incoming telephone call
is dealt with, and an Intelligent Peripheral (IP), which performs
such task as the playing of prompts and speech recognition.  In the
USA this connection is achieved using the 1129+ protocol.  This
protocol allows the IP to query an SCP and ask what operation, such
as playing a voice prompt, it should perform on a particular call.

   Implementing the 1129+ TCP/IP on an AIX system poses many
problems.  The major ones are:
  - acceptable performance of data transfer on established
    transactions.
  - rapid acceptance and validation of new connections.
  - optimum use of AIX processes.
  - validity of AIX connection File Descriptors within different
    processes.
  - uncomplicated interface to rest of 1129+.

   The simplest solution would be to use a single AIX process
to perform all four major tasks.  This would mean that the validity
of AIX File Descriptors for connections would not be a problem and
there would be no need to find ways of sharing information between
processes.  However it is obvious that there would be major
performance problems with the following major tasks being done
serially:
  - accept/validate connection
  - receive data on established transactions
  - send data on established transactions
  - establish new transactions

   The solution described here involves three processes, one
to accept new connections, one to read data from connections and
another to write data to connections.  Each time a new connection is
received, new read and write processes are started with the new
correct list of connection file descriptors.  These are held in
check until the existing read and write processes complete their
current reads or writes and terminate.  Once the old read and write
processes terminate the new processes take over.  In this way,
similar to running a relay where the new runner is already moving
before he receives the baton from the previous runner as little time
is possible is wasted while the new processes start.  This method has
the following benefits:
  - there is minimal context switching o...