IEEE HomeSearch IEEE ShopWeb Account Contact IEEE IEEE
MembershipPublicationsServicesStandardsConferencesCareers/Jobs
IEEE-SA IEEE-SA Member Area Search our standards database for Abstract, Sponsor, Status, Contact,Ordering and Historical information. IEEE-SA Standards Association
Products & ServicesIEEE-SA MembershipStandards DevelopmentNews & InformationnavFillerHOMEHOME Icon

IEEE Std 1394.3™-2003 IEEE Standard for a High Performance Serial Bus Peer-to-Peer Data Transport Protocol (PPDT) -Description

Abstract: This standard defines a peer-to-peer data transport (PPDT) protocol between Serial Bus devices that implement Serial Bus Protocol 2 (SBP-2). The facilities specified include device and service discovery, self-configurable (plug and play) binding, and connection management.

Keywords: computers, CSR architecture, connect, peer-to-peer, SBP-2, transport protocol

Content +

  • 1. Overview
    • 1.1 Scope
    • 1.2 Purpose
  • 2. References
  • 3. Definitions, abbreviations, and notation
    • 3.1 Definitions
      • 3.1.1 Conformance definitions
      • 3.1.2 Technical definitions
    • 3.2 Abbreviations
    • 3.3 Notation
      • 3.3.1 Numeric values
      • 3.3.2 Bit, byte and quadlet ordering
  • 4. Model (informative)
    • 4.1 Protocol stack and service model
    • 4.2 Independent data paths for each service
    • 4.3 Connection management
    • 4.4 Data transfer between initiator and target
    • 4.5 Control requests and responses
    • 4.6 Unsolicited status
    • 4.7 Reverse login and logout
  • 5. Data structures
    • 5.1 Transport flow ORBs
    • 5.2 Status block
    • 5.3 Control information
    • 5.4 Queue information
    • 5.5 Reverse login request and response
  • 6. Control operations
    • 6.1 Login, reverse login and queue zero
    • 6.2 Autonomous response information
    • 6.3 Connection management
      • 6.3.1 Connection establishment
      • 6.3.2 Queue shutdown
    • 6.4 Queue status information
    • 6.5 Logout and reverse logout
  • 7. Transport flow operations
    • 7.1 Data transfer to a target
    • 7.2 Data transfer to an initiator
    • 7.3 Completion status
    • 7.4 Execution context for active ORBs
    • 7.5 Error recovery
  • 8. Configuration ROM
    • 8.1 Root directory
    • 8.2 Instance directories
    • 8.3 Feature directories
    • 8.4 Keyword leaves
    • 8.5 Initiator unit directory
    • 8.6 Target unit directories
    • 8.7 Private unit directory
    • 8.8 Device ID
  • Annex A Minimum Serial Bus node capabilities
    • A.1 Initiator capabilities
    • A.2 Target capabilities
  • Annex B Compliance with INCITS 325-1998 (SBP-2)
    • B.1 Divergence from SBP-2
    • B.2 Implementation requirements for SBP-2 initiators and targets
  • Annex C Control request and response parameters
  • Annex D Control and status registers
  • Annex E Service ID registration
  • Annex F Configuration ROM
    • F.1 Bus information block and root directory
    • F.2 Feature directory
    • F.3 Target unit directory
    • F.4 Scanner with a single unit architecture
    • F.5 Printer with multiple unit architectures
    • F.6 Multifunction device with uniform unit architectures
    • F.7 Initiator unit directory
  • Annex G Bibliography

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

available for Standards Online Bus Architecture Collection subscribers only

spacer

Copyright ©2004 IEEE-SA
Contact IEEE-SA
(m.v.rodriguez@ieee.org)
URL: http://standards.ieee.org/reading/ieee/std_public/description/busarch/1394.3-2003_desc.html

spacer