Skip to main content

NDIS 5.0 and ATM Support in Windows

Updated: March 10, 2004


Microsoft launched the industry's first logo and compatibility testing program for Asynchronous Transfer Mode (ATM) LAN Emulation solutions for Microsoft Windows 95 and Microsoft Windows NT 4.0, and also released Network Driver Interface Specification (NDIS) extensions for native ATM support. (See the Network/ATM Test Kit on NDIS 5.0 and supporting ATM components are available in the Windows DDK.) Support is included in the current Windows operating systems: Microsoft Windows XP, Microsoft Windows Server 2003, Microsoft Windows 2000, Windows NT 4.0, Microsoft Windows Millennium Edition, and Microsoft Windows 98. The NDIS 5.0 extensions will enable direct access to any connection-oriented media, such as ATM with full Quality of Service (QoS) support for media that can support QoS.

Note:

  • ATM LAN Emulation is being considered for removal in future Microsoft operating systems.

  • All references on this page to NDIS 5.0 also apply to NDIS 5.1.

On This Page

Introduction to ATM Introduction to ATM
Deploying ATM with Microsoft Windows Deploying ATM with Microsoft Windows
ATM and NDIS 5.0 DDK ATM and NDIS 5.0 DDK
ATM Deliverables ATM Deliverables
Call to action for ATM and NDIS 5.0: Call to action for ATM and NDIS 5.0:


Introduction to ATM

ATM technology has been deployed rapidly throughout the telecommunications industry. ATM enables a spectrum of new applications, including greatly enhanced multimedia, video conferencing, and movie-on-demand type video streaming, as well as telephony and other real-time voice services.

ATM has been developed to ensure smooth integration with numerous existing network technologies at several levels, including Frame Relay, Ethernet, and TCP/IP. ATM accommodates the simultaneous transmission of data, voice, and video, allowing for the unification of the separate voice and data networks, while also easily coexisting in mixed network environments. This is good news for network administrators, because it means that networks can be incrementally upgraded to ATM.

ATM represents a significant advance in network communications. There is nothing faster on the horizon or better geared to support QoS-based applications, and it has been designed from the outset to have the flexibility and scalability that will enable it to match future advances in telecommunications and computer technology.

An ATM Call Manager and a LAN emulation module allow ATM adapters to function in an Ethernet environment, with the ATM adapter appearing to overlying applications and protocols as if it were Ethernet. The LAN emulation module and Call Manager work together to accept Ethernet headers and addresses, and translate them for ATM, allowing legacy LAN applications and protocols to work transparently in an ATM network.

Deploying ATM with Microsoft Windows

Microsoft's support of LAN emulation makes Windows the communications platform of choice. The logo testing and qualification programs for Windows provide a standard measure of compatibility and performance for ATM adapter vendors. The logo testing program means that customers will be able buy ATM adapter products that have earned the "Designed for Microsoft Windows" logo with confidence that the ATM adapters will perform reliably with a broad set of applications. ATM adapter vendors can make use of the logo testing process also, to ensure a higher degree of customer satisfaction with their products.

Microsoft has released the NDIS 5.0 extensions for native ATM support and now offers native ATM drivers. Native ATM support at the operating system level enables a new class of guaranteed QoS-based applications. Native support means that the Call Manager and LAN emulation module are provided in Windows. Therefore, developers do not need to develop or license their own call managers and LAN emulation modules. This should allow ATM hardware to be more easily and more quickly developed and will lower the costs to develop and deploy ATM-based solutions.

ATM and NDIS 5.0 DDK

The NDIS extensions provide kernel-mode NDIS 5.0 "client" drivers with direct access to connection-oriented media such as ATM. The NDIS 5.0 API accommodates three objects:

  • An NDIS 5.0 miniport driver that exposes the connection-oriented media adapter.

    NDIS 5.0 provides an interface whereby a miniport driver can be developed and added to the architecture. The miniport driver is informed (and allocates resources) when virtual circuits are established and terminated—and is also informed of the QoS requirements of the virtual circuit if the media supports QoS. The miniport is then given packets of data to transmit on a specified virtual circuit.

  • A Call Manager that implements the virtual circuit (or call) signaling protocol over the media.

    NDIS 5.0 provides an interface whereby a Call Manager can be developed and added to the architecture to accommodate signaling on associated media. All connection-oriented media require a signaling protocol (Q.931 on ISDN, Q.2931 on ATM, and the AT command set on most serial modems), which is implemented by the Call Manager component.

  • A Client of the Call Manager (the NDIS 5.0 "client") that sits above NDIS 5.0, using the NDIS 5.0 API to request that an appropriate Call Manager create a virtual circuit using specified addressing and applicable QoS information and then transmit data on that virtual circuit.

    NDIS 5.0 provides an interface whereby an NDIS 5.0 Client can be developed and plugged in to the architecture. This Client binds to a miniport for the media it intends to use, and also binds to a Call Manager that is known to implement signaling for the media the Client intends to use. The Client then uses the NDIS 5.0 API to create virtual connections (VCs) and transfer data over those VCs.

The new architecture for Windows extends native ATM support to Windows Sockets 2.0 (WinSock) and DirectShow-based applications by providing system-level components that map the applicable WinSock and DirectShow APIs to NDIS 5.0, extending direct ATM access to user-mode applications. WinSock and DirectShow are Win32 APIs that enable development of transport-independent network applications.

Microsoft plans to extend NDIS to support ATM natively in the operating system. On the left side of Figure 1 is the previous version of NDIS. Third-party ATM solution vendors provide their own LAN emulation clients (LEC), User Network Interface (UNI) Call Manager, and hardware interface software. (UNI is the signaling protocol standardized by the ATM Forum.)

Figure 1

On the right in Figure 1 is NDIS today, showing the new Windows architecture view of native ATM support in which Microsoft provides the LEC, UNI Call Manager, and IP over ATM support (IETF RFC 1577, 2022, and extensions) natively in the operating system. The Windows TCP/IP protocol stack runs over the LEC, or the IP over ATM module which provides added efficiency in running TCP/IP over an ATM network. The Win32 WinSock 2.0 and DirectShow support for ATM will enable more QoS-based applications to run over ATM.

ATM Deliverables

ATM network adapter manufacturers can immediately begin development and testing of NDIS 5.0 ATM miniport drivers using the Windows DDK. The DDK includes additional design guide information for writing NDIS 5.0 Call Managers and Clients.

Native ATM support from Microsoft consists of two products:

NDIS 5.0 in the Windows DDK (for ATM adapter vendors), which enables development, testing, and logo awards for ATM media adapters. This product consists of the following:

  • NDIS library with NDIS 5.0 extension.

  • Sample source (and associated working binary) for an NDIS 5.0 miniport driver for a line of ATM media adapters (Adaptec PCI OC3 and 25M ATM adapters).

  • Enhanced NDIS Test Tool that supports testing of NDIS 5.0 miniport drivers for ATM.

  • An ATM Call Manager that conforms to the ATM Forum UNI specification for signaling over ATM.

Windows ATM Services, which consists of the following:

  • NDIS library with NDIS 5.0 extension.

  • ATM Call Manager that conforms to the ATM Forum UNI specification for signaling over ATM. This Call Manager supports permanent virtual circuits (PVCs) as well as switched virtual circuits (SVCs).

  • Several NDIS 5.0 ATM miniport drivers, tested by WHQL.

  • ATM LAN Emulation Client module (an NDIS 5.0 client that exposes NDIS 4.0 Ethernet or Token Ring at its upper edge) that conforms to the ATM Forum LANE 1.0 specification for enabling existing applications and protocols to run on ATM as if they were running on one or multiple Ethernet or Token Ring segments.

  • IP Over ATM module for the Microsoft TCP/IP stack that conforms to the IEEE 1577 and 2022 specifications, which enable the TCP/IP stack to operate directly over ATM.

  • Win32 services that extends the NDIS 5.0 native call and data plane access up to User-mode WinSock and ActiveMovie-based applications that want direct access to ATM.

Call to action for ATM and NDIS 5.0:

Rate: