Browse Prior Art Database

Addition of CCITT Cause and Diagnostic codes to X.25 Network Provider Interface

IP.com Disclosure Number: IPCOM000033442D
Original Publication Date: 2004-Dec-10
Included in the Prior Art Database: 2004-Dec-10
Document File: 3 page(s) / 44K

Publishing Venue

IBM

Abstract

Disclosed is an Enhancement to the to X.25 Network Provider Interface to Report CCITT (Comite Consultatif International Telegraphique et Telephonique) Cause and Diagnostic codes for Disconnects and Resets

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 3

Addition of CCITT Cause and Diagnostic codes to X .25 Network Provider Interface

When using the *RS/6000 AIXlink X.25 Network Provider Interface (NPI), the NPI reset and disconnect definition from the **UNIX International Open Systems Interconnection (OSI) Work Group's "Network Provider Interface Specification" only provides a minumum amount of information concerning the cause of a connection problem and does not report the location or reason of a connection problem to the user's NPI application. The RESET_reason field in the N_reset_req_t and N_reset_ind_t structures, and the DISCON_reason in the N_discon_req_t, and N_discon_ind_t structures do not give enough information to NPI users and applications to determine the actual cause of the reset or disconnect. In order to give NPI applications more information concerning the cause of a reset or disconnect and to allow those applications to be able to determine more accurately how to respond to a connection problem, a change to the NPI device driver code reset and diagnostics structures to pass the CCITT X.25 clear and reset causes and diagnostic codes to the application is needed. With this improvement, these causes and diagnostic codes can be checked by the NPI application to help determine the type of connection problem. These causes and diagnostic codes are already available at the packet layer; but the current "Network Provider Interface Specification" does not provide a way to report those causes and diagnostic codes to NPI applications.

This invention solves the problem where NPI applications are unable to determine the actual of cause of a connection problem because the OSI Work Group's "Network Provider Interface Specification" does not define a way to report the X.25 clear and reset causes and diagnostic codes to the NPI application.

This invention enhances the following NPI structures by adding the cause and diagnostic field to each structure:

* NC Reset Request */

typedef struct {

att_ulong PRIM_type; /* always N_RESET_REQ*/

att_ulong RESET_reason; /* the reason for reset */

uchar cause; /* Cause value of the reset */

uchar diagnostic; /* Diagnostic reason of the reset */ } N_reset_req_t;

/* * NC Reset Indication */

typedef struct {

1

Page 2 of 3

att_ulong PRIM_type; /* always N_RESET_IND*/

att_ulong RESET_orig; /* the reset originator */

att_ulong RESET_reason; /* the reason for reset */

uchar cause; /* Cause value of the reset */

uchar diagnostic; /* Diagnostic reason of the reset */ } N_reset_ind_t;

/* * NC Disconnection Request */

typedef struct {

att_ulong PRIM_type; /* always N_DISCON_REQ*/

att_ulong DISCON_reason; /* reason for disconnection*/

att_ulong RES_length; /* responding address length */

att_ulong RES_offset; /* the offset of the responding address from the

beginning of the M_...