Browse Prior Art Database

Socket Access on Native NETBIOS Protocol

IP.com Disclosure Number: IPCOM000106216D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 94K

Publishing Venue

IBM

Related People

Edel, TR: AUTHOR [+4]

Abstract

This disclosure describes a method for accessing the native NETBIOS protocol using the SOCKETS Application Programming Interface (API) thereby utilizing the rich knowledge base associated with the sockets to be used over the NetBIOS protocol. Presently, communication with the native NetBIOS protocol is carried out using the NetBIOS API. In the native NetBIOS API, the flow control problem is dealt with by the applications and is clearly a transport specific API. The use of socket API alleviates these problems, facilitates transport independence, and transport level flow control.

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

Socket Access on Native NETBIOS Protocol

      This disclosure describes a method for accessing the native
NETBIOS protocol using the SOCKETS Application Programming Interface
(API) thereby utilizing the rich knowledge base associated with the
sockets to be used over the NetBIOS protocol.  Presently,
communication with the native NetBIOS protocol is carried out using
the NetBIOS API.  In the native NetBIOS API, the flow control problem
is dealt with by the applications and is clearly a transport specific
API.  The use of socket API alleviates these problems, facilitates
transport independence, and transport level flow control.

      Sockets creates a transport endpoint for a given address family
such as AF_INET to access the Internet protocols, eg: TCP, UDP, and
AF_UNIX to access the Unix internal protocols.  We define a new
address family viz  AF_NetBIOS with which a socket user can create a
transport endpoint that utilizes the NetBIOS protocol via the socket
API.  The socket abstraction layer will select the appropriate
protocol based on the address family of the endpoint, for either
connection-oriented or connectionless communication.

      The transport level flow control is effected by setting aside
an upper limit for the send and receive paths for the endpoint.  This
information is maintained in the control block for the endpoint and
the sender is not allowed to send more than the "send window"
specified by the upper limit.  When the data is received by the
intended recipient, the sender's "window" is opened, thus enabling
the sender to continue sending, if any.  The user of the native
NetBIOS API has no such control and a native user can flood the
network with any amount of data.  This could cause network congestion
and undesirable resource consumption at the endpoint.

      The socket API serves as a transport independent API and is
independent of various communication platforms.  As a result, an
application written using socket API for AF_NetBIOS is easily
portable to function on other protocol domains such as AF_INET.
Also, there is a clear-cut distinction of user addresses from the
resource names which are often used interchangeably while using the
native NetBIOS API.

      Socket API access on the native NetBIOS protocol is facilitated
by writing a thin device driver called the Protocol Manager that
communicates with the so...