Browse Prior Art Database

Data Encoding Algorithm for a Multi-Media Network

IP.com Disclosure Number: IPCOM000118886D
Original Publication Date: 1997-Aug-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Worley, BJ: AUTHOR

Abstract

Various networks are being established to transport and transcode voice and other forms of data, such as fax. The data is transcoded from the sending system format to the destination system format during its journey through the network. When and how this transcoding is performed is critical to the use of network resources and the complexity of network nodes.

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

Data Encoding Algorithm for a Multi-Media Network

      Various networks are being established to transport and
transcode voice and other forms of data, such as fax.  The data is
transcoded from the sending system format to the destination system
format during its journey through the network.  When and how this
transcoding is performed is critical to the use of network resources
and the complexity of network nodes.

The approach described here defines the optimal point in the network
for transcoding.

The network configuration is taken to consist of the following:
  o  Originating System
     The system that is sending messages or non-delivery reports to
      the network.
  o  Receiving Network Node
     The part of the network to which the originating system
      attaches.
  o  Destination Network Node
     The part of the network to which the destination system
      attaches.
  o  Destination System
     The system that is the destination of messages or
      non-delivery reports sent to the network.

      The majority of systems that will connect to the multi-media
network will use a protocol such as X.400 which supports delivery and
non-delivery notification.  Because of this, the multi-media network
will have to be based upon a protocol which supports these features.
The approach described here proposes that it is best to leave any
data within  a message that enters the system in its native format
until it reaches  its destination network node, while converting any
data within a non-delivery report at the receiving network node.

      In order to perform message data transcoding at the destination
network node when an originating system sends a message to the
receiving network node, the system's data format type is tagged to
the message's  originating address.  This then travels with the
message through the network.  In an X.400 network, a domain-defined
attribute could be used  as with The Messaging Alliance Integrated
Message Transport.

      If the message now experiences problems within the network and
a non-delivery report is generated, the...