1、Recognized as anAmerican National Standard (ANSI)The Institute of Electrical and Electronics Engineers, Inc.345 East 47th Street, New York, NY 10017-2394, USACopyright 1997 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 1997. Printed in the United States
2、 of America.IEEE is a registered trademark in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.iiiIntroductionThis introduction is not part of IEEE Std 1284.1-1997, IE
3、EE Standard for Information TechnologyTransport IndependentPrinter/System Interface (TIP/SI.)Local area networks are increasingly becoming the most popular means of interconnecting devices within acorporation. With costs per connection coming down, this trend shows no sign of abating. As networks gr
4、ow larger,more computers and printers will be interconnected. Any weaknesses in network printing will only be magnified asmore devices are made to communicate.The absence of feedback from existing printers causes many problems in todays network environment. For example,a user could be submitting a j
5、ob to a remote printer. If that printer is low on toner, most printers today do not have thecapability to inform users about this condition. Additionally, if the job is large, the user risks having to wait until thejob is finished before finding out that the output is incorrect. The resulting waste
6、of paper, toner, and time could besignificant when calculated over a period of time on a large network.Standardized feedback information from a printer would solve this problem. By the use of this standard, when a printerrecognizes a condition that would prevent it from accurately printing a job, it
7、 can send a standardized message to a hostcomputer that is monitoring network printing. Upon receipt of this message, the host could then send a message to theuser who submitted the job, informing him or her of the error condition. The user could then redirect a job to a moreappropriate printer or u
8、ndertake action to correct the defect at the target printer. When projected over a period of timeand a large number of network users, the resulting monetary savings could be substantial.The example shown above is just one of many error conditions that could occur when printing either on a standalone
9、computer or over a network. By using this standard format for exchanging information between the printer and host,software vendors, network suppliers, and printer manufacturers will now be able to greatly improve the efficiency ofnetwork printing.At the time this standard was completed, the key cont
10、ributors to the IEEE 1284.1 Working Group were as follows:Forrest D. Wright, ChairJay Martin, SecretaryMichael Timperman, EditorChirag BakshiMichael BringmannAndy DavidsonNeal FischerBob GarciaRod GerhartTom HastingTim HathawayBob HerriotKen HilliardBarry HillsTerry JonesTheodore KearleyCharles Kimb
11、erRick LandauHarry LewisRick LomickaErnie MandeseStan McConnellRon NortonRoman OrzolSteve PriceSuzy PricePaul ReillyDave RoachAvi SchlankRon SmithGail SongerLarry SteinMike StilzKoji TashiroRandy TurnerWilliam WagnerCraig WhittleKeith WinterLloyd YoungSteve ZillesThe following persons were on the ba
12、lloting committee:Dharma P. AgrawalKeith D. AnthonyCharles BrillGeorge HoranskyThomas M. KuriharaDonald C. LoughryRaymond LutzEdward McCreightDarrell B. McIndoeJames D. MooneyRoman OrzolRoy ReedLarry C. SollmanLarry SteinRobert G. StewartMichael TimpermanClarence M. Weaver, Jr.Gregory WinstonForrest
13、 D. WrightOren YuenivThe final conditions for approval of this standard were met on 29 July 1997. This standard was conditionally approvedby the IEEE Standards Board on 26 June 1997, with the following membership:Donald C. Loughry, ChairRichard J. Holleman, Vice ChairAndrew G. Salem, SecretaryClyde
14、R. CampStephen L. DiamondHarold E. EpsteinDonald C. FleckensteinJay Forster*Thomas F. GarrityDonald N. HeirmanJim IsaakBen C. JohnsonLowell JohnsonRobert KennellyE. G. “Al” KienerJoseph L. Koepfinger*Stephen R. LambertLawrence V. McCallL. Bruce McClungMarco W. MigliaroLouis-Franois PauGerald H. Pete
15、rsonJohn W. PopeJose R. RamosRonald H. ReimerIngo RschJohn S. RyanChee Kiow TanHoward L. Wolfman*Member EmeritusAlso included are the following nonvoting IEEE Standards Board liaisons:Satish K. AggarwalAlan H. CooksonKristin M. DittmannIEEE Standards Project EditorTrademarksThe trademarks in the fol
16、lowing list are referred to on one or more pages of this standard. This list is provided as amatter of convenience and accommodation. By providing the list, IEEE takes no position on the legal status of anytrademarks listed nor of any trademarks omitted from the list. While the information in the li
17、st is believed to be correct,it is based on information supplied by those who claim to own the trademarks. Consequently, IEEE disclaims liabilityfor any inaccuracies in the list.Adobe and Postscript are trademarks of Adobe Systems Incorporated.Hewlett-Packard is a registered trademark of Hewlett-Pac
18、kard Company.IBM and Presentation Manager are registered trademarks of IBM Corporation.Internetwork Packet Exchange, IPX, NCP, and NetWare Core Protocol are trademarks of Novell, Inc.Microsoft and Windows are registered trademarks of Microsoft.Novell and NetWare are registered trademarks of Novell,
19、Inc. in the United States and/or other countries.TrueType is a registered trademark of Apple Computer, Inc.vCLAUSE PAGE1. Overview.11.1 Scope 11.2 Purpose. 11.3 Objectives. 12. Definitions, abbreviations, and acronyms.22.1 Definitions 22.2 Abbreviations and acronyms 53. Software model .63.1 IEEE 128
20、4.1 printer model 63.2 Printer job data flow. 73.3 Printer sessions and jobs 94. The command/reply structure .114.1 General topics 114.2 The structure 125. Command set.155.1 Overview 155.2 Request Device Characteristics (RDC) 155.3 Request Interpreter Characteristics (RIC) 355.4 Job Control (JC). 44
21、5.5 Request Device Status (RDS) 585.6 Printer Configuration Control (PCC). 795.7 Request Logical Unit Characteristics (RLUC) 855.8 Printer Variable Commands (PVC) . 875.9 Remote Operator Panel (ROP). 906. Alerts.1006.1 Device Status Alert (DSA). 1006.2 Interpreter Message Alerts (IMA) 1026.3 Job Con
22、trol Alerts (JCA) . 1046.4 Common Printer MIB Alert (CPMA) 1076.5 Operator Panel Alert (OPA). 108viCLAUSE PAGEAnnex A (normative) Conformance .109Annex B (informative) Requirements for a Standard Information Mover Protocol with Link Encapsulation (SIMPLE) .110Annex C (informative) Internetwork Packe
23、t (IP) transport mapping example.113Annex D (informative) NovellNetWaretransport mapping example.119Annex E (informative) De-multiplexing alerts .122Annex F (informative) Host ownership of an IEEE 1284.1 printer123Annex G (informative) Bibliography124Copyright 1997 IEEE All Rights Reserved 1IEEE Sta
24、ndard for Information TechnologyTransport Independent Printer/System Interface (TIP/SI)1. Overview1.1 ScopeA standard protocol for the control of printers that is independent of the underlying data stream or page descriptionlanguage (PDL) used to create the printed page is defined in this standard.
25、This protocol is usable by all classes ofprinters. The scope of this standard is limited to management and control of printers and does not include managementor control of a printing system or subsystems.1.2 PurposeThere is currently no defined, independent standard for controlling printers. Each ve
26、ndor builds some control into theunderlying PDL or data stream. Without an independent, openly defined protocol, applications and operating systemscannot automatically determine the type of printer being addressed. This protocol will provide a minimumimplementation subset that will allow automatic i
27、dentification and configuration of printers and vendor extensibility toprovide for growth and product differentiation.1.3 ObjectivesThis standard defines a protocol for communications between a host and printer. Its intent is to provide a standardmethodology for software developers, computer vendors
28、, and printer manufacturers that facilitates the orderlyexchange of information between printers and host computers. A minimum set of functions that permit meaningfuldata exchange is defined. Thus, this standard establishes a foundation upon which compatible applications, computers,and printers can
29、be developed, without compromising an individual organizations desire for design innovation. Thefollowing objectives accompany this standard:a) To simplify the printer driver development process by defining a standard set of command/responsetransactions between the host computer and printer.b) To ac
30、celerate the development of communicating printers by providing a robust protocol that can beimplemented in phases ranging from basic to extended functionality.c) To ease customers printing problems (especially over networks) by accelerating the availability ofcommunicating printers and compatible h
31、ost software.2 Copyright 1997 IEEE All Rights ReservedIEEE Std 1284.1-1997 IEEE STANDARD FOR INFORMATION TECHNOLOGY-d) To assist software developers in minimizing time to market by establishing a base set of functions that ensurea minimum level of communications between the host and printer.e) To fa
32、cilitate the creation of powerful network print management software by defining transactions that workacross a wide range of printers.f) To enable the creation of standard control/communications firmware that can be included in many peripheraldevices.g) To create a standard methodology for host and
33、printer communications that is independent of the transportmechanism used between devices.h) To enhance the management of printers in networks by providing a mechanism for printers to readily providetheir status and configuration to the host application.i) To permit design innovation by providing fl
34、exibility within the specification for printer manufacturers toinclude extensions to the original set of guidelines.j) To ensure cross-platform host-to-printer communications by creating an operating system-independent set ofguidelines.The resultant protocol is PDL-independent with the capability of
35、 a printer to support multiple PDLs, all activeat the same time, if desired.2. Definitions, abbreviations, and acronyms2.1 DefinitionsThis clause provides certain terms and definitions used in this specification that may not be generally familiar or thatmay be used with a very specific meaning. Thes
36、e definitions are not intended to be absolute but rather to give the senseof the terms as used in the context of this standard.2.1.1 American National Standard Code for Information Interchange (ASCII): In this standard, a text string ofsome arbitrary length. The text string may contain nonprintable
37、characters. The length must be stated in another field.The encoding is typically ISO 8859-1, but is specified by the Printer Language field in a “Request DeviceCharacteristicsRequest Summary” response. See also: IEEE Std 100-1996.2.1.2 ASCIIz: In this standard, an ASCII string concatenated with a NU
38、LL character.2.1.3 big endian: A term used to imply that bytes in a word and words in a double word are transmitted mostsignificant byte or word first in a serial stream of bytes.2.1.4 bit: A single binary integer. A set bit represents to a binary “1.” A cleared bit represents a binary “0.”2.1.5 bit
39、-encoded byte: A byte with a definition for each bit.2.1.6 bit-encoded word: A word with a definition for each bit.2.1.7 byte: An entity composed of 8 bits, used to define a unit element of memory or transmitted data. It is capable ofdescribing integers in the decimal range 128 to 127.2.1.8 command:
40、 A message from the host directed to the printer that may or may not include print data.2.1.9 connection: A parallel interface state that is outside the scope of this standard and is not defined herein. Thisstate is indicative of the state of the physical or logical connection between a host and the
41、 printer. Only in this state candata be transferred between a host and the printer.2.1.10 console language: The human language in which information is to be displayed on local or remote consoles.2.1.11 deprecated: Supported by predecessors to this standard but no longer used.2.1.12 desktop managemen
42、t interface (DMI): A facility, normally host resident, for handling and translating definedinterfaces for component information, event information, stored management information format (MIF) structures andmanagement information. In this context, a component is an integral device or product, such as
43、a printer; and event isan asynchronous alert or trap. The management information is used by an application such as a user managementCopyright 1997 IEEE All Rights Reserved 3TRANSPORT INDEPENDENT PRINTER/SYSTEM INTERFACE (TIP/SI) IEEE Std 1284.1-1997program, or may be converted for use by a network m
44、anagement facility. The desktop management interface iscontrolled by the Desktop Management Task Force.2.1.13 Desktop Management Task Force (DMTF): An association of software developers, host computer, andperipheral device manufacturers that promulgate a platform-independent interface standard for t
45、he management ofdesktop computers and the peripheral devices attached to such computers. In addition to defining the interfacesbetween components, the host-based service layer and management applications, the association supports thedevelopment of consistent management information format (MIF) struc
46、tures that define the significant manageableand status attributes of various components incorporated into desktop computers.2.1.14 document: An encoded, electronically transmittable image, set of images, or image-related information, whichis handled by the printer interface control unit.2.1.15 doubl
47、e word: A field composed of two words. In a message, the most significant word is transmitted/receivedfirst. It is capable of describing integers in the decimal range 2 147 483 648 to 2 147 483 647.2.1.16 duplex: For purposes of this standard, a type of printing that involves the process of creating
48、 images orimpressions on both sides of the printing media.2.1.17 facsimile: A process by which textual or pictorial images are communicated, typically but not exclusively, overtelephone lines. The images may be coded in raster or compressed raster format (such as CCITT group 3) or in a pagedescripti
49、on language such as Adobe PostScript. Facsimile typically operates down to the physical link level andincludes protocols providing control and addressing mechanisms specific to the media being used. This isdistinguished from the process of communicating similarly encoded images over local or wide area networks.However, both may be considered implementations of remote printing.2.1.18 feed direction: On most printers, the direction that the medium is moved through the marking engine. For aprinter in which the medium is not moved, the feed direction may be considered as al
