ISO/IEC 11518-1:1995

Information technology — High-Performance Parallel Interface — Part 1: Mechanical, electrical and signalling protocol specification (HIPPI-PH)

Provides the mechanical, electrical and signalling protocol specifications for an efficient simplex high-performance point-to-point interface between pieces of data-processing equipment. Facilitates the development and use of computer systems by providing a common interface at the physical and data framing layers. Provides an efficient interconnection between computers, high-performance display systems, and high-performance, intelligent block-transfer peripherals.

Technologies de l'information — Interface parallèle à haute performance — Partie 1: Spécification du protocole mécanique, électrique et de signalisation (HIPPI-PH)

General Information

• Status: Published
• Publication Date: 07-Jun-1995
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Drafting Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Current Stage: 9093 - International Standard confirmed
• Start Date: 13-Jul-2018
• Completion Date: 14-Feb-2026

ISO/IEC 11518-1:1995 - Overview

ISO/IEC 11518-1:1995 defines the mechanical, electrical and signalling protocol for the High-Performance Parallel Interface (HIPPI-PH) physical layer. It specifies a high-speed, simplex point-to-point interface optimized for large block transfers at peak data rates of 800 Mbit/s and 1600 Mbit/s, using twisted‑pair cabling up to 25 m. The standard provides the common physical and data‑framing layer needed to interconnect computers, high-performance displays, and intelligent block‑transfer peripherals.

Key topics and technical requirements

• Physical layer specification: connector pin assignments, cable and grounding requirements, differential and interconnect signal characteristics, and maximum connector footprint.
• Electrical and timing: CLOCK, DATA BUS and PARITY BUS timing, source/destination clock behavior, propagation delay and skew considerations.
• Signalling protocol & framing: physical framing hierarchy, data rate options, error detection (byte parity, LLRC) and burst/packet formats.
• Service interface: defined service primitives for connection management (initiate/complete), flow control, packet and data transfer, control and status primitives.
• State transitions & control logic: state diagrams, source/destination pseudo-code and READY/WAIT flow control mechanisms.
• Operational details & examples: waveform examples for connect/start/end sequences, burst handling, and annexes with implementation suggestions, error checking and component options.
• Design guidance: annexes cover cable selection, connector availability, byte ordering, sample LLRC circuits and propagation delay calculations.

Practical applications & who uses it

ISO/IEC 11518-1 is for organizations needing reliable, low‑latency, high‑bandwidth physical interconnects:

• System architects and hardware engineers designing high-performance servers, graphics subsystems, or intelligent block‑transfer peripherals.
• Embedded and interface designers implementing point‑to‑point data links where predictable latency and burst transfer efficiency matter.
• Data center engineers and integrators retrofitting or interfacing legacy HIPPI systems.
• Test labs and compliance teams validating mechanical, electrical and signalling conformance against HIPPI‑PH specifications.

HIPPI‑PH supports large file transfers, real‑time and variable‑size packet transfers, and is designed for circuit‑switched environments where rapid burst transfers and look‑ahead flow control maximize throughput.

Related standards

ISO/IEC 11518 is a multipart standard. Related parts include:

• Part 2: Framing Protocol (HIPPI‑FP)
• Part 3: Encapsulation of ISO 8802-3 (HIPPI‑LE)
• Part 4–6: Command mapping, Memory Interface, Physical Switch Control

Keywords: ISO/IEC 11518-1, HIPPI-PH, High-Performance Parallel Interface, physical layer, point-to-point interface, 800 Mbit/s, 1600 Mbit/s, burst transfer, LLRC, error detection, connector, cable specifications.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 11518-1
First edition
1995-06-01
Information technology -
High-Performance Parallel Interface -
Part 1:
Mechanical, electrical and signalling protocol
specification (H I PPI-PH)
Technologies de I’information - Interface paralkle 2 haute
Performance -
Partie 7: Sp&ification du protocole mkanique, blectrique et de
signakation (HIPP/-PH)
lSO/IEC 11518=1:1995(E)
Page
Contents
V
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*.*.
Introduction . . . . . . . . . . . . . . . . . . . . . . .
1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
2 Definitions, editorial conventions, and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . 1
.............................................................................
3 HIPP1 structure
.2
characteristics.
3.1 Configuration .
....................................................
3.2 Logical framing hierarchy
.........................................................................
4 Service interface.
..............................................................
4.1 Service primitives
.................................................... .3
4.2 Sequences of primitives
.3
summary.
4.3 Service primitives .
.3
.....................................................
4.4 Operational sequences
................................... .4
4.5 Initiate connection Service primitives
........................... .4
4.6 Complete the connection Service primitives
............................................ .5
4.7 Flow control Service primitives
..................................................
4.8 Packet Service primitives.
primitives .
4.9 Data transfer Service
...................................................
4.10 Hangup Service primitives
.8
primitives.
4.1 1 Control Service .
....................................................
4.1 2 Status Service primitives
........................................................ IO
5 Interface format and Signals.
................................................ IO
5.1 Physical framing hierarchy
5.2 Data rate Options. .
.............................................................
5.3 Usage of Signals
..............................................................
5.4 Error detection.
.........................................................................
6 State transitions
..................................................................... 14
6.1 State exit.
...................................................................... 14
6.2 Interlocks
............................................. 14
6.3 Source READY pseudo-code
.......................................
6.4 Destination READY pseudo-code
........................................................
6.5 Source pseudo-code
.................................................. 18
6.6 Destination pseudo-code
7 Timing. .
....................................................... 21
7.1 Source CLOCK Signal
................................................. 22
7.2 Destination CLOCK Signal
..................................... 22
7.3 DATA BUS and PARITY BUS timing
.................................................... 22
Signals.
7.4 Source control
information. .
7.5 1-Field
7.6 LLRC .
................................................
7.7 Destination control Signals
gaps. .
7.8 Source wait
....................................................... 22
7.9 Destination wait gaps
............................................................... 23
8 Physical characteristics
....................................... 23
8.1 Differential circuit characteristics
............................... 24
8.2 INTERCONNECT Signal characteristics
...............................................................
8.3 Ground Signals
............................................................
8.4 Reserved Signals
........................................................
8.5 Cable specifications
..............................................................
8.6 Cable grounding
..................................................
8.7 Connector specifications
............................................... 25
8.8 Connector pin assignments
0 ISO/IEC 1995
All rights reserved. Unless otherwise specified, no patt of this publication may be reproduced or utilized in any form or
by an means, electronie or mechanical, including photocopying and microfilm, without Permission in writing from the
publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
ii
ISOAEC 11518=1:1995(E)
.........................................................
Annex A Waveform examples
...................................................................
A.l Introduction
..............................................
A.2 Connection and Start packet
.......................................................
A.3 End burst, Start burst
.................... 31
A.4 End burst, end packet, Start packet, Start burst
..................................... 31
A.5 End burst, end packet, disconnect
...................................................... 32
A.6 Illegal end termination
.......................................... 32
A.7 Rejected connection sequence
........................................... 33
A.8 Aborted connection sequence
.............................................. 34
B Implementation suggestions
Annex
B.l Data rate Option control .
....................................................
B .2 Source READY counter
.............................................................
B.3 1-Field sampling.
................................................................... 34
B. 4 Short bursts
................................................... 35
Switching and the 1-Field
B .5
................................................................
B .6 Byte ordering.
................................................................
Annex C Error checking
Byte parity .
c.1
............................................................................
C .2 LLRC
..........................................................
C .3 Burst length check
.........................................................
C .4 Sample LLRC circuit
................................
Annex D Propagation delay calculation example
D.l CLOCK .
.................................................................. 38
D .2 Loading data
....................................................................
D .3 Cable skew
D. 4 Setup time .
.......................................................................
D.5 Hold time
...................................................................
D .6 Tuning delay
..........................................................
Annex E Component Options
.....................................
E.l Cable availability and colour coding
.................................................................
E.2 Cable lengths
................................................
E.3 Connector alignment guide
.............................................
E.4 Maximum connector footprint
.......................................................
E.5 Connector availability
....................................................... 40
E.6 Connector jackscrew torque
............................................ 40
E. 7 Line driver and receiver availability
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alphabetical index
. . .
Ill
0 ISOAEC
ISOAEC 11518=1:1995(E)
Tables
Table 1 Data rate Options .
....................................... 26
Table 2 Connector pin assignments
................................................... 35
Table B.l Byte assignments
...................................... 41
Table E.1 Connector wire assignments
Figures
vi
Figure 1 Control hierarchy .
Logical framing hierarchy .
Figure 2
...... 2
HIPPI-PH Service interface .
Figure 3
Initiate the connection Service primitives . .4
Figure 4
Complete the connection Service primitives . .4
Figure 5
Flow control Service primitives . 5
Figure 6
Packet Service primitives . 6
Figure 7
primitives . 7
Figure 8 Data transfer Service
Hangup Service primitives . .7
Figure 9
Control Service primitives . 8
Figure 10
........................................... 9
Figure 11 Status Service primitives
....................................... IO
Figure 12 Physical framing hierarchy
Interface Signal summary . IO
Figure 13
......................................................... 12
Figure 14 Data packing
..................................... 14
Figure 15 Source READY flow diagram
............................... 14
Figure 16 Destination READY flow diagram
................................................ 16
Figure 17 Source flow diagram
.......................................... 19
Figure 18 Destination flow diagram
........................... 21
Figure 19 Source driven Signals at the Source
..................... 21
Figure 20 Source driven Signals at the Destination
................................................. 23
Figure 21 Differential circuit.
I NTERCONN ECT circuit . 24
Figure 22
............................................ 27
Figure 23 Cable connector - tabs
.............................. 28
Figure 24 Bulkhead connector - receptacle
.................................. 29
Figure A.1 Typical HIPPI-PH waveforms.
.............................. 30
Figure A.2 Connect, Start packet, Start burst
.............................................. 30
Figure A.3 End burst, Start burst
........... 31
Figure A.4 End burst, end packet, Start packet, Start burst
............................ 31
Figure A.5 End burst, end packet, disconnect
Figure A.6 Illegal end termination .
................................. 32
Figure A.7 Rejected connection sequence
Figure A.8 Aborted connection sequence . 33
Figure B.1 Physical layer switching . 35
Figure B.2 Switching with intermediate nodes .
Ordered byte stream mapping . 35
Figure 8.3
Figure B.4 Bit significance within byte 0 . 35
......................................... 37
Figure C.l Parity and LLRC example
Representative LLRC circuit . 37
Figure C.2
Propagation delay example block diagram . 39
Figure D.1
Figure E.l Connector alignment guide . 42
Maximum connector footprint . 42
Fiqure E.2
iv
0 ISOAEC
ISOAEC 115184:1995(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized System for
worldwide standardization. National bodies that are members of ISO or
IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with particular fields of technical activity. ISO and IEC technical com-
mittees collaborate in fields of mutual interest. Other international organ-
izations, governmental and non-governmental, in liaison with ISO and IEC,
also take part in the work.
In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for vot-
ing. Publication as an International Standard requires approval by at least
75 % of the national bodies casting a vote.
International Standard lSO/IEC 11518-1 was prepared by Joint Technical
Committee lSO/IEC JTC 1, Information technology, Subcommittee SC 25,
In terconnection of informa tion technology equipmen t.
lSO/lEC 11518 consists of the following Parts, under the general title In-
forma Gon technology - High-Performance Parallel Interface:
- Part 7: Mechanical, electrical and signalling protocol specifica tion
(HIPP/-PH)
- Part 2: Framing Protocol (HIPP/-FP)
- Part 3: Encapsulation of ISO 8802-3 - L ogical /in k con trol pro tocol
data units (HIPP/-LE)
- Part 4: Mapping of HIPP/ to /PI device generic command sets
(Hl PP/-/ PI)
- Part 5: Memory Interface (HIPP/-MI)
- Part 6: Physical Switch Control (HIPP/-SC)
Annexes A to E of this part of ISO/IEC 11518 are for information only.

ISOAEC 11518=1:1995(E) 0 ISO/IEC
Introduction
This part of ISO/IEC 11518 defines the physical layer of an efficient simplex high-
Performance Point-to-Point interface operating at Speeds of 800 or 1 600 Mbit/s. The
-PH abbreviation Stands for “physical layer”.
Characteristics of this HIPP1 physical layer interface include
-
Point-to-Point connections use one or two topper twisted-pair cables for distances
of up to 25 m.
-
the HIPPI-PH is a simplex interface, capable of transferring data in one direction
only. Two HIPPI-PHs may be used to implement a full-duplex interface.
-
data transfers are performed and flow controlled in increments of bursts, each burst
normally containing 256 words.
-
signalling and control sequences are kept simple, and a look-ahead flow control is
used, to allow average transfer rates for large file transfers to approach the peak
transfer rate, even over distances longer than specified for the HIPPI-PH cables.
-
the HIPPI-PH provides support for low-latency, real-time, and variable size packet
transfers.
-
the HIPPI-PH is designed to facilitate use in a circuit-switched environment. In sup-
port of this feature, a limited information field is available for subdevice addressing or
other nonspecified control functions during the connection Phase of Operation. One
round-trip cable delay is required to establish or terminate a connection.
-
the HIPPI-PH is also designed to transmit multiple packets after a connection has
been established. No round-trip cable delays are required between packets.
Figure 1 Shows the interrelationship of the different clauses of this part of ISO/IEC
11518. The upper-layer protocols and Station management protocols are not covered in
this patt of ISOAEC 11518.
-1-11111-111111111
I I
I Upper-layer and sta tion I
I I
management protocols
I
I
Service interface
(Clause 4)
I
v--
State transitions
(Clause 6)
Electrical Signals
(Clauses 5,7,8)
Figure 1 - Control hierarchy
vi
ISO/lEC 11518~1:1995 (E)
INTERNATIONAL STANDARD 0 ISOAEC
Information technology -
High-Performance Parallel Interface -
Part 1:
Mechanical, electrical, and signalling protocol specification
(HIPPI-PH)
1 Scope
2.1.5 IengthAongitudinal redundancy check-
A Single word that is sent on the DATA
word (LLRC):
BUS from Source to Destination after each burst.
This part of ISO/IEC 11518 provides the mechanical,
2.1.6 optional: Features that are not required by this
electrical and signalling protocol specifications for an
part of ISO/IEC 11518. However, if any optional feature
efficient simplex high-performance Point-to-Point interface
defined by this part of ISO/IEC 11518 is implemented, it
between pieces of data-processing equipment.
shall be implemented according to this part of ISO/IEC
11518.
The interface described in this patt of ISO/IEC 11518 tan
be operated at peak data rates of 800 or 1 600 Mbit/s, over
2.1.7 packet: A data set sent from Source to Desti-
distances of up to 25 m by means of topper cabling. A
nation. A packet is composed of one or more bursts. The
distance-independent signalling protocol allows the average
HIPPI-PH specification does not limit the maximum packet
data rates to approach the peak data rates, even over
size, but a maximum size may be imposed by a given HIPPI-
distances longer than specified for the HIPPI-PH.
PH implementation, or by an upper-layer protocol.
The purpose of this part of ISO/IEC 11518 is to facilitate the
2.1.8 Service interface (SI): The means by which
development and use of Computer Systems by providing a
the HIPPI-PH provides Services to upper-layer protocols.
common interface at the physical and data framing layers.
2.1.9 Source: The equipment that transmits the data.
lt provides an efficient interconnection between Computers,
high-performance display Systems, and high-performance,
2.1 ,IO state: The current condition of the HIPPI-PH,
The interface is
intelligent block-transfer peripherals.
excluding transitions, as indicated by the control Signals.
optimized for large block transfers.
2.1 .ll Station management (SMT): The super-
visory entity that monitors and controls the HIPPI-PH.
2.1 .12 upper-layer protocol (ULP): The protocols
2 Definitions, editorial conventions, and
above the Service interface. These could be done in
abbreviations
hardware or Software, or they could be distributed between
the two.
2.1 Definitions
2.1 .13 wait: Wait is every CLOCK period when there is
no valid information on the DATA BUS. Some wait times are
For the purposes of this part of ISO/IEC 11518, the follow-
required by the HIPPI-PH signalling protocol; others may be
ing definitions apply.
the result of flow control or upper-layer protocol operations.
2.1 .l burst: A group of words, sent during contiguous
2.1 .14 word: A unit of information, consisting of 32 or
CLOCK periods. A burst may be sent by the Source for
64 bits, matthing the DATA BUS width, and transferred
each READY indication received from the Destination.
from the Source to the Destination during a CLOCK period.
Bursts contain 1 to 256 words. Bursts that contain less
than 256 words are called short bursts. A packet contains
no more than one short burst. A short burst will be either the
2.2 Editorial conventions
first or last burst of a packet.
Condition of the HIPPI-PH when
2.1.2 connection: In this patt of ISO/IEC 11518, certain terms that are proper
data transfers from Source to Destination are possible. names of Signals or similar terms are printed in upper case
to avoid possible confusion with other uses of the same
2.1.3 Destination: The equipment that receives the
words (e.g., REQUEST, CONNECT, BURST). Any lower
data.
case uses of these words have the normal technical English
meaning.
2.1.4 I-Field: A 32-bit information field sent as part of
the sequence of operations establishing a connection from
A number of conditions, sequences Parameters, events,
a Source to a Destination.
states, or similar terms are printed with the first letter of
NOTE - The contents of the I-Field are defined by an upper-layer
each word in upper case and the rest lower case (e.g.,
protocol and are not defined in this part of ISO/IEC 11518.
Source, Destination). Any lower case uses of these words
have the normal technical English meaning.
0 ISOAEC
ISOAEC 11518=1:1995(E)
2.3 Abbreviations 4 Service interface
CCI Connection Control Information
This clause specifies the Services provided by HIPPI-PH.
ECL Emitter Coupled Logic
The intent is to allow ULPs to operate correctly with this
HIPPI-PH H igh-Performance Parallel I nterface -
HIPPI-PH. How many of the Services described herein are
Mechanical, electrical, and signalling protocol
Chosen for a given implementation is up to that implernentor;
specification - P hysical (Layer)
however, a set of HIPPI-PH Services must be supplied
LLRC LenghlLongitudinal Redundancy Check
sufficient to satisfy the ULP(s) being used. The Services as
PHSM Physical (layer) Station Management
defined herein do not imply any particular implementation, or
any interface.
SI Service Interface
SMT Station Management
Figure 3 Shows the relationship of the HIPPI-PH interfaces.
ULP Upper-Layer Protocol
Upper-layer
protocols
3 HIPP1 structure
WV
Data transfer
3.1 Configuration characteristics
Service interface
The HIPPI-PH has been designed in a modular fashion to
support different peak bandwidth requirements.
Station
3.1 .l 800 Mbit/s
6 HIPPI-PH
management 5
An HIPPI-PH with a DATA BUS width of 32-bit words
(SW
Management
provides 800 Mbit/s data transfer rates.
Service interface
(PHSM-.)
3.1.2 1 600 Mbit/s
An HIPPI-PH with a DATA BUS width of 64-bit words
Figure 3 - HIPPI-PH Service interface
provides 1 600 Mbit/s data transfer rates.
4.1 Service primitives
3.2 Logical framing hierarchy
The primitives, in the context of the state transitions in
Figure 2 Shows the basic organization of the information on
clause 5, are declared required or optional. Additionally,
the HIPPI-PH.
Parameters are either required, conditional, or optional. All
of the primitives and Parameters are considered as required
Once a connection is established a packet (or multiple
except where explicitly stated otherwise.
packets) tan be sent from the Source to the Destination.
Esch packet shall contain one or more bursts. Bursts shall
HIPPI-PH Service primitives are of four types.
contain 1 to 256 words. Bursts that contain less than 256
words are called short bursts. A packet shall contain no
- ßequest primitives are issued by a Service user to
more than one short burst. A short burst shall be either the
initiate a Service provided by the HIPPI-PH. In this patt of
first or last burst of a multi-burst packet.
ISO/IEC 11518, a second Request primitive of the same
name shall not be issued until the Confirm for the first
request is received.
-
Confirm primitives are issued by the HIPPI-PH to
1 E::t$t,d ( ::i-iiii?l!i IF E 1:
acknowledge a Request.
HH@
dd
dd
-
-1-m Indicate primitives are issued by the HIPPI-PH to notify
the Service user of a local event. This primitive is similar
Packet
Packet
I
in nature to an unsolicited interrupt. Note that the local
event may have been caused by a Service Request. In
dH-
#
this part of ISO/IEC 11518, a second Indicate primitive of
the same name shall not be issued until the Response for
Burst Burst
c x
the first Indicate is received.
HH
--1
-
ßesponse primitives are issued by a Service user to
256 words of 32 or 64 bits each acknowledge an Indicate.
Figure 2 - Logical framing hierarchy
ISOAEC 11518=1:1995(E)
0 ISOAEC
4.2 Sequences of primitives 4.4 Operational sequences
Primitives issued by the ULP shall be serviced by the
The Order of execution of Service primitives is not arbitrary.
HIPPI-PH in the sequences defined in the state transitions
Logical and time sequence relationships exist for all
of clause 6. An implementation may present the HIPPI-PH
described Service primitives. Time sequence diagrams are
with multiple requests for Services, but the HIPPI-PH shall
used to illustrate a valid sequence. Other valid sequences
Service the requests one at a time.
may exist. The sequence of events between peer users
across the user/provider interface is illustrated. In the time
The following sequence of Service primitives is an example
sequence diagrams the HIPPI-PH users are depicted on
of normal Operation of the HIPPI-PH.
either side of the vertical bars while the HIPPI-PH acts as
the Service provider.
4.4.1 Enable the interface
The interface may be enabled using whatever
4.3 Service primitives summary
implementation dependent enabling method, if any, is
specified.
Initiate a Connection
PH-RING.Request (CCI)
4.4.2 Initiate a connection
PH RING.Confirm
PHIRING.lndicate (CCI)
PH RING primitives shall be used to initiate a connection
PH RING.Response
-
from the Source to the Destination. The Connection Control
Information (CCI) may be used for non-specified control
Complete the Connection
functions.
PH-ANSWER.Request (AcceptIReject)
PH ANSWER.Confirm
4.4.3 Complete the connection
PHIANSWER.lndicate (AcceptIReject)
PH ANSWER.Response PH ANSWER primitives shall be used to establish or reject
-
theconnection.
Flow Control
4.4.4 Enable Destination reception
PH FLOW.Request
PH-FLOW.Confirm
When it is ready, the Destination ULP may use the
PHIFLOW. Indicate (Enabled)
PH FLOW.Request primitive to indicate that it is willing to
PH FLOW.Response
-
accept bursts from the HIPPI-PH.
Packet Control
4.4.5 Start a packet
PH PACKET.Request (Begin/End)
PHIPACKET.Confirm (Accept/Reject)
PH PACKET (Begin) primitives shall be used to indicate the
PH-PACKET.Indicate (Begin/End,Status)
staz of a packet.
PH PACKET.Response
-
4.4.6 Send burst
Burst Transfer
PH-TRANSFER.Request (Length,Burst)
PH TRANSFER primitives shall be used to transfer one
PH-TRANSFER.Confirm (AcceptIReject)
hurst of a packet.
PH-TRANSFERJndicate (Status,Length,Burst)
4.4.7 Send more bursts
PH TRANSFER.Response
-
More bursts may be sent for this packet by returning to
Terminate the Connection
4.4.6.
PH HANGUP.Request
PH-HANGUP.Confirm
4.4.8 Terminate the packet
PH-HANGUP.lndicate
PH-HANGUP.Response
-
PH PACKET (End) primitives shall be used to indicate the
endof a packet.
Control Interface
PHSM-CONTROL. Request (Parameter-List)
4.4.9 Send more packets
PHSM CONTROL.Confirm (Status,Status-List)
-
More packets may be sent by returning to 4.4.5.
Interface Status
PHSM STATUS.Request
4.4.10 Terminate the connection
PHSMISTATUS.Confirm (Status)
The Source or Destination may terminate the connection by
PHSM STATUS.lndicate
using the PH-HANGUP primitives. Note that dedicated
PHSM-STATUS.Response
-
Point-to-Point HIPPI-PHs may never need to terminate the
connection once it is established, or only terminate the
connection as an error recovery process. See the
cautionary note in 5.3.6.
0 ISOAEC
ISOAEC 11518=1:1995(E)
PH RING.Indicate
Initiate another connection 4.5.3 _
4.4.11
This primitive indicates to the Destination ULP an attempt
Return to 4.4.2 to initiate another connection.
by a Source ULP to establish a connection.
PH-RING.lndicate ( CCI )
Semantics -
4.5 Initiate connection Service primitives
The CCI Parameter is a 32-bit field that may be used for
Figure 4 is a diagram of these primitives. They shall be used
non-specified control operations for connection estab-
to request that a connection be established between the
This CCI may be different from the CCI
lishment.
Source and Destination.
supplied by the PH-RlNG.Request primitive due to the
action of intermediate devices, such as switches,
between the Source and Destination.
Des tina tion
Source
HIPP/-PH
ULP ULP
Issued - The HIPPI-PH shall issue this primitive to the
Destination ULP when it has received a connection
PH RING
request.
PH RING
* .Indicate Effect - The Destination ULP should accept or reject the
connection request.
PH RING
.C&nfirm
PH RING
. Response
4.5.4 PH RING.Response
-
This primitive acknowledges the PH RING.Indicate from the
-
Figure 4 - Initiate the connection
HIPPI-PH.
Service primitives
PH RING.Response
Semantics -
-
PH RING.Request
4.5.1 - The Destination ULP issues this primitive to
Issued -
acknowledge receipt of the PH-RING.Indicate.
Issued by the Source ULP to request establishment of a
connection from the Source to the Destination. In the case
Effect - The HIPPI-PH is enabled to issue another
where a previous connection attempt did not complete with
PH RING.Indicate.
-
a PH-ANSWER.Indicate, and was aborted with a Source
ULP issued PH HANGUP.Request, the Source must wait a
time Tl beforeinitiating another connection. Tl shall be a
round-trip propagation delay plus appropriate action time.
No assumptions are made as to where or how the timer is
lt may be done in the ULP or the HIPPI-PH.
implemented.
4.6 Complete the connection Service
The timer may be implemented with hardware, Software, or a
primitives
mixture of the two. The default value of Tl shall be approxi-
mately 2 ms.
Figure 5 is a diagram of these primitives. To respond to a
connection request, the PH-ANSWER primitives shall be
Semantics - PH-RING.Request ( CCI )
used.
The CCI Parameter is a 32-bit field that may be used for
non-specified control operations for the connection
Source Destina tion
establishment.
HIPP/-PH
ULP
ULP
Issued - The Source ULP issues this primitive to the
PH ANSWER
-
HIPPI-PH when a connection to a Destination ULP is
w . Request
PH ANSWER
d
required.
-fl--
4-
.Indicate e
Effect - The HIPPI-PH shall initiate a connection.
PH ANSWER
-
PH ANSWER
-
Confirm
. Response
PH RING.Confirm
4.5.2
-
This primitive acknowledges the PH RlNG.Request from
-
Figure 5 - Complete the connection
the Source ULP.
Service primitives
Semantics - PH RING.Confirm
-
The HIPPI-PH shall issue this primitive to the
Issued -
RING.Request.
Source ULP to acknowledge a PH -
Effect - Unspecified
0 ISOAEC ISOAEC 11518=1:1995(E)
4.6.1 PH ANSWER.Request
- 4.7 Flow control Service primitives
(optional)
This primitive is issued by the Destination ULP in response
to the PH RING primitives to instruct the HIPPI-PH to reject
Figure 6 is a diagram of these primitives. These primitives
or establish a connection.
are optional, and may be used to pass flow control infor-
mation between the HIPPI-PH and the Source and
Semantics - PH-ANSWER.Request (Accept/Reject)
Destination ULPs.
The Accept/Reject Parameter instructs the HIPPI-PH to
The Flow Control Service primitives are used by the Destina-
complete the connection or to reject it.
tion ULP to inform the HIPPI-PH that it is willing to accept a
burst in the form of the PH TRANSFER.Indicate.
-
Issued - The Destination ULP should issue this primitive
to the HIPPI-PH in response to a PH RING.Indicate.
-
Source Destination
Effect - The HIPPI-PH shall complete the connection if
HIPP/-PH
ULP
ULP
the Accept Parameter is used. If the Reject Parameter is
used, the HIPPI-PH may either do nothing (in which case
the Source ULP shall not receive a PH ANSWER
.Indicate), or perform a short connection seiuence (in
which case the Source ULP shall receive a PH ANSWER
-
.Indicate with the Reject Parameter).
PH FLOW
-
.Confirm
r
4.6.2 PH ANSWER.Confirm
-
Figure 6 - Flow control Service primitives
This primitive acknowledges the PH ANSWER.Request
-
from the Destination ULP.
4.7.1 PH FLOW.Request
-
Semantics - PH ANSWER.Confirm
-
This primitive is issued by the Destination ULP to tell the
Issued - The HIPPI-PH shall issue this primitive to the
HIPPI-PH that it is ready to accept a burst from the HIPPI-
Destination ULP to acknowledge a PH ANSWER
-
PH.
.Request.
Semantics - PH FLOW.Request
-
Effect - Unspecified
Issued - The Destination ULP issues this primitive to the
4.6.3 PH ANSWER.Indicate HIPPI-PH when it is ready to receive bursts.
-
This primitive indicates to the Source ULP that the connec-
Effect - The HIPPI-PH shall be enabled to send another
tion has been accepted or rejected.
burst to the Destination ULP. Esch PH FLOW.Request
enables an additional PH-TRANSFER.lndicate.
Semantics - PH-ANSWER.Indicate (Accept/Reject)
If the Accept Parameter is used, the connection has
4.7.2 PH FLOW.Confirm
-
been accepted and is available for data transfer. If the
Reject Parameter is used, the connection has been
This primitive acknowledges the PH
FLOW.Request from
-
rejected and the interface is available for another
the Destination ULP.
PH RING.Request.
-
Semantics - PH FLOW.Confirm
-
Issued - The HIPPI-PH shall issue this primitive to the
Source ULP when it has determined the Status of the
- The HIPPI-PH shall issue this primitive to the
Issued
connection request.
Destination ULP to acknowledge a PH FLOW.Request.
-
Effect - The connection sequence is complete.
Effect - Unspecified
4.6.4 PH ANSWER.Response
-
4.7.3 PH FLOW.Indicate
-
This primitive acknowledges the PH ANSWER.Indicate
-
from the HIPPI-PH.
This primitive notifies the Source ULP that it tan send a
lt shall indicate to the Source ULP the current
burst.
Semantics - PH ANSWER.Response
-
number of available bursts that the HIPPI-PH is willing to
accept.
lssued - The Source ULP issues this primitive to
acknowledge receipt of the PH-ANSWER.lndicate.
Semantics - PH-FLOW. Indicate (Enabled)
Effect - The HIPPI-PH is enabled to issue another
PH ANSWER.Indicate.
-
0 ISOAEC
ISOAEC 11518=1:1995(E)
4.8.2 PH PACKET.Confirm
The Enabled Parameter shall be the current number of -
bursts that the HIPPI-PH is willing to accept. The range
This primitive acknowledges the PH PACKET.Request from
is implementation dependent. -
the Source ULP.
Issued - The HIPPI-PH shall attempt to issue this
primitive to the Source ULP every time it receives an
Semantics - PH-PACKET.Confirm (Accept/Reject)
indication that another burst tan be transmitted.
The Parameter denotes whether or not the primitive was
Effect - Unspecified
accepted by the HIPPI-PH. The PH-PACKET.Request
primitive may have been issued by the ULP along with
other primitives, e.g., RING.Request. If the connection
4.7.4 PH FLOW.Response
-
sequence fails, then the packet delimiter would not be
inserted and this PH-PACKETConfirm primitive would
This primitive acknowledges the PH FLOW.Indicate from
-
indicate Reject.
the HIPPI-PH.
The HIPPI-PH shall issue this primitive to the
Semantics - PH FLOW.Response Issued -
-
Source ULP to acknowledge a PH PACKET.Request.
-
lssued - The Source ULP issues this primitive to
acknowledge receipt of the PH-FLOW.Indicate.
Effect - Unspecified
Effect - The HIPPI-PH is enabled to issue another
PH FLOW.lndicate.
-
4.8.3 PH PACKET.lndicate
-
This primitive indicates to the Destination ULP that a packet
delimiter has been received from the Source ULP.
4.8 Packet Service primitives
Semantics - PH PACKET.lndicate (Begin/End, Status)
-
Figure 7 is a diagram of these primitives. They shall be
used to delimit one or more bursts into entities called
The Begin/End Parameter indicates either the beginning
packets.
or the end of the packet.
The Status Parameter may include, but is not limited to,
Source Des tina tion
an error when a burst with an illegal size and correct
HIPP/-PH
ULP ULP
LLRC was received as patt of this packet.
Issued - The HIPPI-PH shall issue this primitive to the
PH PACKET
-
Destination ULP when it receives a packet boundary
. Request -
indication.
PH PACKET
* . idicate
Effect - Unspecified
PH PACKET
.Conf irm
PH PACKET
-
. Response
PH PACKET.Response
4.8.4
-
Figure 7 - Packet Service primitives
This primitive acknowledges the PH PACKET.Indicate from
-
the HIPPI-PH.
4.8.1 PH PACKET.Request
-
Semantics - PH PACKET. Response
-
This primitive is issued by the Source ULP to delimit one or
Issued - The Destination ULP issues this primitive to
more bursts into a packet entity.
acknowledge receipt of the PH-PACKET.lndicate.
Semantics - PH PACKET. Request (Begin/End)
-
Effect - The HIPPI-PH is enabled to issue another
PH PACKET.Indicate.
-
the beginning
The Parameter or the end of
the packet.
Issued - The Source ULP issues this primitive to the
HIPPI-PH to delimit one or more bursts into a packet.
Effect - Upon receipt of a Begin Parameter, the HIPPI-PH
shall mark the statt of a packet. Upon receipt of an End
Parameter, the HIPPI-PH shall mark the end of a packet.
0 ISOAEC ISO/IEC 11518=1:1995(E)
Issued - The HIPPI-PH shall issue this primitive to the
4.9 Data transfer Service primitives
Destination ULP when a burst has been received.
Figure 8 is a diagram of these primitives. They shall be used
to transfer a burst from the Source ULP to the Destination Effect - Unspecified
ULP.
Source Des tina tion
4.9.4 PH TRANSFER.Response
-
ULP HIPP/-PH ULP
This primitive acknowledges the PH TRANSFER.Indicate
-
from the HIPPI-PH.
PH TRANSFER
iequest w
PH TRANSFER.Response
Semantics -
-
PH TRANSFER
PH TRANSFER
- The Destination ULP issues this primitive to
Issued
- Tndicate
2onfirm
acknowledge receipt of the PH-TRANSFER.lndicate.
PH TRANSFER
-
The HIPPI-PH is enabled to issue another
Effect -
. Response
PH TRANSFER.Indicate.
-
Data transfer Service primitives
Figure 8 -
4.9.1 PH TRANSFER.Request
-
4.10 Hangup Service primitives
This primitive is issued by the Source ULP to request the
transfer of a burst.
Figure 9 is a diagram of these primitives. They shall be used
to terminate a connection between the Source and Destina-
Semantics - PH-TRANSFER.Request (Length,Burst)
tion. Note that a Hangup tan be initiated from either the
Source or Destination and will usually affect both the local
ed in any units , but
The length Parameter may be specif
and opposite ends of the interface.
an integral number of words shall be transferred.
Issued - The Source ULP issues this primitive to the
Source or
HIPPI-PH to request the transfer of a burst to the
destina tion Other end
Destination ULP.
ULP HIPP/-PH ULP
The HIPPI-PH shall accept the burst for
Effect -
transmission.
PH HANGUP
. Request
PH TRANSFER.Confirm
4.9.2
-
PH HANGUP
PH HANGUP -
-
y.Indicate
TRANSFER.Request
This primitive acknowledges the PH -
.Confirm
from the Source ULP.
PH HANGUP -
?‘H HANGUP
-
PH-TRANSFER.Confirm (Accept/Reject)
Semantics -
.Indicate
. Response
The Parameter denotes whether or not the primitive was
PH HANGUP-
-
accepted by the HIPPI-PH.
. Response
Issued - The HIPPI-PH shall issue this primitive to the
Source ULP to acknowledge a PH TRANSFER.Request.
-
Figure 9 - Hangup Service primitives
Effect - Unspecified
4.10.1 PH HANGUP.Request
-
4.9.3 PH TRANSFER.lndicate
-
This primitive is issued by either the Source ULP or
This primitive indicates to the Destination ULP that a burst
Destination ULP to request that the connection be
has been received from the Source ULP.
terminated.
PH-TRANSFER.lndicate (Status,Length,
Semantics -
Semantics - PH HANGUP.Request
-
Burst)
Issued - The Source ULP or Destination ULP issues this
The Status Parameter reports any parity or LLRC errors
primitive to the HIPPI-PH to terminate a connection.
detected during the data transfer if error checking is
supported. Illegal length bursts, with correct LLRC,
Effect - The HIPPI-PH shall terminate the connection.
shall be indicated in the PH-PACKET.Indicate primitive
if error checking is supported.

0 ISO/IEC
ISOAEC 11518-1:1995(E)
4.10.2 PH HANGUP.Confirm 4.11 Control Service primitives
-
This primitive acknowledges the PH HANGUP.Request to Figure 10 Shows the SMT Control Service primitives. They
-
the issuing ULP. shall be used to set Parameters and control the interface.
Note that a Control primitive tan be initiated from either the
Semantics - PH HANGUP.Confirm Source or Destination.
-
Issued - The HIPPI-PH shall issue this primitive to the
ULP to acknowledge a PH HANGUP.Request. Source or
-
destina tion
Other end
Effect - Unspecified
SMT HIPP/-PH
SMT
4.10.3 PH HANGUP.Indicate
-
PHSM CONTROL
kequest
This primitive indicates to the ULP that the connection has
If a connection exists, the ULP that
been terminated.
issued the PH HANGUP.Request shall receive a
PHSM CONTROL
PH HANGUP.Confirm when the hangup sequence Starts
-
2onfirm
and a PH-HANGUP.Indicate when the sequence com-
pletes. The other end ULP shall receive only a
PH HANGUP.Indicate.
-
- Control Service primitives
Figure 10
Semantics - PH HANGUP.lndicate
-
PHSM CONTROL.Request
4.11 .l
-
Issued - The HIPPI-PH shall issue this primitive to the
ULP when the connection has been terminated.
This primitive is issued by either the Source SMT or
Destination SMT to set Parameters within the interface,
Effect - The ULP may no longer use the connection for
Start diagnostics, or otherwise control the interface. One
data transfers, and all pending .Requests are cancelled.
function is specified and others are left to specific
implernentations.
4.10.4 PH HANGUP.Response
-
Semantics - PHSM-CONTROL.Request (Parameter List)
-
This primitive acknowledges the PH HANGUP.lndicate from
-
the HIPPI-PH. The Parameter List specifies what is to be set, started,
etc. The Parameter list includes but is not limited to:
Semantics - PH _ HANGUP.Response Reset
Issued - The ULP issues this primitive to acknowledge Issued - The Source or Destination SMT issues this
receipt of the PH-HANGUP.Indicate. primitive to perform some control function over the
interface as a whole.
The HIPPI-PH is enabled to issue another
Effect -
PH HANGUP.Indicate. Effect - The HIPPI-PH shall perform the function speci-
-
fied. The Reset Parameter shall take the HIPPI-PH to the
Disabled state and cancel all pending .Requests.
4.11.2 PHSM CONTROL.Confirm
-
This primitive acknowledges the PHSM-CONTROL. Re-
quest to the issuing SMT.
Semantics - PHSM CONTROL.Confirm (Status,
Status- List) -
Status reports the success or failure of the
PHSM CONTROL.Request Operation. There should be
one Status value in Status-List for each event initiated
with the PHSM-CONTROL.Request.
Issued - The HIPPI-PH shall issue this primitive to the
SMT when all of the operations specified in the
PHSM CONTROL.Request have been accepted or
complsed.
Effect - Unspecified
ISOAEC 11518=1:1995(E)
0 ISOAEC
PHSM STATUS.Indicate
4.12.3
4.12 Status Service primitives -
This primitive informs the SMT entity that a major event has
Figure 11 Shows the SMT Status Service primitives. They
occurred that affects the Operation of the HIPPI-PH.
shall be used to obtain local Status information from the
HIPPI-PH. Note that a Status primitive tan be initiated from
Semantics - PHSM STATUS.Indicate
either the Source or Destination and shall only affect the -
local end of the interface.
Issued - The HIPPI-PH shall issue this primitive to the
SMT whenever a major event is detected. Major events
include but are not limited to a Change in the
Source or
INTERCONNECT Signal.
destina tion Other end
HIPP/- PH
SMT
SMT
NOTE - If a PHSM-CONTROL.Request was accepted success-
fully but not completed, then an PHSM-STATUS.Indicate could
PHSM STATUS be used to indicate completion.
. Reqiest v
Upon receipt of this primitive, the local SMT
Effect -
PHSM STA
...