Browse Prior Art Database

Layered Software Architecture

IP.com Disclosure Number: IPCOM000029412D
Original Publication Date: 2004-Jul-25
Included in the Prior Art Database: 2004-Jul-25
Document File: 2 page(s) / 27K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

ISUP (ISDN User Part) is a protocol of signaling procedures for the set-up and tear-down of ISDN (Integrated Services Digital Network) and non-ISDN connections; it is widely used in switching systems worldwide. ISUP contains a set of signaling messages, each of which is composed of a set of parameters. ITU (International Telecommunication Union) defines the ISUP standard for international calls, and each country defines its own version with particular requirements of messages, parameter formats, parameter values, and signaling procedures. Current implementations of ISUP may involve a specific implementation for each message, and separate software modules and builds for different countries. This requires many members of staff to code and support the protocol. The idea described in this text is to address the problem of designing and implementing a single piece of ISUP software in such a way to support a new country variant quickly and easily, and to meet real-time requirements.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

S

Layered Software Architecture

Idea: Lin Huang, US-Boca Raton; Dimitri Verzhinski, US-Boca Raton

ISUP (ISDN User Part) is a protocol of signaling procedures for the set-up and tear-down of ISDN (Integrated Services Digital Network) and non-ISDN connections; it is widely used in switching systems worldwide. ISUP contains a set of signaling messages, each of which is composed of a set of parameters. ITU (International Telecommunication Union) defines the ISUP standard for international calls, and each country defines its own version with particular requirements of messages, parameter formats, parameter values, and signaling procedures.

Current implementations of ISUP may involve a specific implementation for each message, and separate software modules and builds for different countries. This requires many members of staff to code and support the protocol. The idea described in this text is to address the problem of designing and implementing a single piece of ISUP software in such a way to support a new country variant quickly and easily, and to meet real-time requirements.

An ISUP software which currently supports ANSI (American National Standard Institute), Japan, China, and ETSI (European Telecommunications Standards Institute) ISUP variants, has been designed and implemented now. This approach allows to add new variants and add/modify messages easily, and to build one load for all variants. The focus is on the differences between the new variant and the ITU common, and the differences only are implemented.

1. Layered Software Architecture

ISUP software is organized in a layered structure (cf. Fig. 1). Code common to all variants is placed in ISUP common base. ANSI specific code and ITU common code are built upon the common base. ETSI, Japan, China, and any other ITU variants are built upon ITU common. When a new country variant (except ANSI) is to be supported, it is just needed to focus on the differences between the new variant and the ITU common, and implement the differences only. This makes it easy and quick to add one or more new variants. Common code is reused as much as possible.

2. Generic Message Encoding/Decoding Engine

An ISUP message may contain fixed mandatory, variable mandatory, and optional parameters. Those parameter...