IEEE Std 1284.4-2000 IEEE Standard for Data Delivery and Logical Channels for IEEE 1284 Interfaces -Description

Abstract: A device to carry on multiple, concurrent exchanges of data and/or control information with another device across a single point-to-point link allowed by the packet protocol is described in this standard. The protocol is not a device control language. The protocol provides basic transport-level flow control and multiplexing services. The multiplexed information exchanges are independent, and blocking of one has no effect on any other. The protocol shall operate over interfaces such as described in 1284-2000.

Keywords: channelized protocol, IEEE 1284, logical channels, multiple logical channels (MLC), transport protocol

Content

• 1. Overview
• • 1.1 Scope
  • 1.2 Purpose
• 2. Definitions
• • 2.1 General terminology
  • 2.2 IEEE 1284.4-specific terminology
• 3. Features and compliance
• • 3.1 Overview
  • 3.2 Features
  • 3.3 Compliance criteria
  • 3.4 Multiple logical channels (MLC) compatibility criteria
• 4. Theory of operation of the IEEE 1284.4 protocol
• • 4.1 Overview
  • 4.2 General packet structure
  • 4.3 Communication procedures
  • • 4.3.1 IEEE 1284.4 conversation management
    • 4.3.2 Channels
    • 4.3.3 Special data packets
    • 4.3.4 Errors
  • 4.4 Service discovery
  • • 4.4.1 Overview
    • 4.4.2 Service names
    • 4.4.3 Service discovery protocols
  • 4.5 Data transfer and flow control
  • • 4.5.1 Introduction
    • 4.5.2 Packet size negotiation
    • 4.5.3 Credit
    • 4.5.4 IEEE 1284.4 data flow control
    • 4.5.5 IEEE 1284.4 transaction channel flow control
    • 4.5.6 Multiple outstanding transactions
    • 4.5.7 Deadlock avoidance and blockage prevention
• 5. IEEE 1284.4 transactions
• • 5.1 Overview
  • 5.2 Transaction summary
  • 5.3 Conversation control transactions
  • • 5.3.1 Init
    • 5.3.2 Exit
    • 5.3.3 Error
  • 5.4 Connection control transactions
  • • 5.4.1 GetSocketID
    • 5.4.2 GetServiceName
    • 5.4.3 OpenChannel
    • 5.4.4 Credit
    • 5.4.5 CreditRequest
    • 5.4.6 CloseChannel
• 6. Data link service requirements
• • 6.1 Overview
  • 6.2 Required services
  • • 6.2.1 Register/unregister
    • 6.2.2 Packet Data Transfer
    • 6.2.3 Asynchronous operation
• Annex A Bibliography
• Annex B Service names registry
• • B.1 Introduction
  • B.2 Service-names list
  • B.3 Registry process
  • • B.3.1 Service name registry request template
    • B.3.2 Example
• Annex C IEEE 1284.4 architecture
• Annex D Example IEEE 1284.4 application programming interface (API)
• • D.1 API overview
  • D.2 API Services
  • • D.2.1 Socket
    • D.2.2 Bind
    • D.2.3 Listen
    • D.2.4 Accept
    • D.2.5 Connect
    • D.2.6 Send
    • D.2.7 Receive
    • D.2.8 Shutdown
    • D.2.9 CloseSocket
    • D.2.10 SetSockOpt
    • D.2.11 GetSockOpt
  • D.3 API Usage
  • • D.3.1 Servers
    • D.3.2 Clients
  • D.4 Mapping API services to IEEE 1284.4 transactions
  • • D.4.1 Socket ( )
    • D.4.2 Bind ( )
    • D.4.3 Listen ( )
    • D.4.4 Accept ( )
    • D.4.5 Connect ( )
    • D.4.6 Send ( )
    • D.4.7 Receive ( )
    • D.4.8 Shutdown ( )
    • D.4.9 CloseSocket ( )
    • D.4.10 SetSockOpt ( )
    • D.4.11 GetSockOpt ( )
• Annex E Implementation issues
• • E.1 Example of simple device
  • E.2 Data transfer efficiency
  • E.3 Flow control algorithms
  • E.4 Allocating buffers to avoid channel interaction
  • E.5 Initialization negotiation
  • E.6 Random back-off strategy for Init
  • E.7 Enumerating services

links: [Standard Status] - [Purchase] - [PDF^*] - [Bus Architecture Collection - Description]

available for Standards Online Bus Architecture Collection subscribers only