ISO/IEC 8802-9:1996

Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 9: Integrated Services (IS) LAN Interface at the Medium Access Control (MAC) and Physical (PHY) Layers

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 9: Interface LAN pour services intégrés (IS) aux couches de contrôle d'accès au support (MAC) et physique (PHY)

General Information

• Status: Withdrawn
• Publication Date: 18-Dec-1996
• Withdrawal Date: 18-Dec-1996
• ICS: 35.110 - Networking
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 05-Apr-2001
• Completion Date: 30-Oct-2025

Relations

• Consolidated By: ISO 11833-1:2007 - Plastics - Unplasticized poly(vinyl chloride) sheets - Types, dimensions and characteristics - Part 1: Sheets of thickness not less than 1 mm
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD
ANSI/IEEE
Std 802.9
First edition
1996-l 2-15
Information technology -
Telecommunications and. information
exchange between systems - Local and
metropolitan area networks - Specific
requirements -
Part 9:
Integrated Services (IS) LAN Interface at the
Medium Access Control (MAC) and Physical
(PHY) Layers
Technologies de /‘information - T6l&ommunica tions et khange
d ‘informa tion en tre s ys t&mes - R&eaux locaux et m&ropolitains -
Exigences spkcifiques -
Partie 9: Interface LAN pour services in t&g&s (IS) aux couches de con trdle
d ’acc& au support (MAC) et physique (PHY)
Reference number
ISO/I EC 8802-g: 1996(E)
ANSI/IEEE
Std 802.9-I 996 edition
Abstract: A unified access method that offers integrated services (IS) to the desktop for a variety
of publicly and privately administered backbone networks (e.g., ANSI FDDI, IEEE 802.x, and ISDN)
is defined. In addition, the interface at the MAC sublayer and the PHY Layer is specified.
Keywords: access unit (AU), data link layer, hybrid multiplexer (HMUX), integrated services digital
network (ISDN), integrated services terminal equipment (ISTE), layer management entity, local
area network (LAN), logical link control, managed object, management information base (MIB), me-
dium access control (MAC) sublayer, metropolitan area network (MAN), physical (PHY) layer, phys-
ical medium dependent, physical signalling, private switching network, protocol data unit (PDU),
service access point, time division multiplexer (TDM)
The Institute of Electrical and Electronics Engineers, inc.
345 East 47th Street, New York, NY 10017-2394, USA
Copyright 0 1996 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 1996. This printing is by the International Organization for Standardization with special per-
mission of the Institute of Electrical and Electronics Engineers, Inc. Printed in Geneva, Switzerland.
ISBN 1-55937-837-9
No part of this publication may be reproduced in any form, in an electronic retrieval system or o thetwise, without the prior
written permission of the publisher.
31 December 1996
International Standard ISWIEC 8802-g: 1996(E)
ANSI/IEEE Std 802.9, 1996 Edition
Information technology-
Telecommunications and information exchange
between systems-
Local and metropolitan area networks-
Specific requirements-
Part 9: Int
grated Services (IS) LAN
Interface at t
edium Access
nd Physical (PHY)
Control (
Layers
Sponsor
LAN MAN Standards Committee
of the
IEEE Computer Society
Adopted as an International Standard by the
International Organization for Standardization
and by the
International Electrotechnical Commission
- American National Standard
Published by
The Institute of Electrical and Electronics Engineers, Inc.

IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Com-
mission) form the specialized system for worldwide standardization. National bodies that are members of
IS0 or IEC participate in the development of International Standards through technical committees estab-
lished by the respective organization to deal with particular fields of technical activity. ISO and IEC techni-
cal committees collaborate in fields of mutual interest. Other international organizations, 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 bsd-
ies for voting. Publication as an International Standard requires approval by at least 75% of the national bod-
ies casting a vote.
In 1995, ANSI/IEEE Std $02.9-1994 was adopted by ISCVIEC JTC 1, as draft International Standard ISO/
IEC DIS 8802-9. A further revision was subsequently approved by ISCYIEC JTC 1 in the form of this new
edition, which is published as International Standard ISO/IEC 8802-9: 1996.
For the purpose of assigning organizationally unique identifiers, the Institute of Electrical and Electronics
Engineers, Inc., USA, has been designated by the ISO Council as the Registration Authority. Communica-
tions on this subject should be addressed to
Registration Authority for ISOREC 8802-9
c/o The Institute of Electrical and Electronics Engineers, Inc.
445 Hoes Lane, PO. Box 1331
Biscataway, NJ 08855133 1
USA
During the original preparation of this International Standard, information was gathered on patents upon
which application of this standard might depend. The basic relevant patents were identified as belonging to
Racal-Datacom Limited. However, IS0 and HE@ cannot give authoritative or comprehensive information
about evidence, validity or scope of patent and like rights. The patent-holder has stated that licenses will be
granted under reasonable terms and conditions and communications on this subject should be addressed to
Racal-Datacom Ltd
Landata House
Hook, Hampshire
IJK
International Organization for Standardization/International Electrotechnical Commission
Case postale 56 l CH-1211 Genkve 20 l Switzerland

Foreword to International Standard ISOAEC 8802-g: 1996
This International Standard is part of a family of International Standards for Local and Metropolitan Area
Networks. The relationship between this International Standard and the other members of the family is
shown below. (The numbers in the figure refer to IS0 Standard numbers.)
8802-2 Logical Link Control
10038 Media Access Control (MAC) Bridges
Data
Link
Layer
8802-5
8802-4 8802-6 8802-7 8802-9
8802-3
Medium
Medium Medium Medium Medium
Medium
Access
Access Access Access
Access Access
---------
----w----. .--------- ,--------. .---------
---- -----.
8802-5
8802-4 8802-6 8802-7
8802-3 8802-9 Physical
Physical
Physical Physical Physical Physical
Physical Layer
This family of International Standards deals with the Physical and Data Link layers as defined by the ISO/
IEC Open Systems Interconnection Basic Reference Model (ISO/IEC 7498-l : 1994). The access standards
define several types of medium access technologies and associated physical media, each appropriate for par-
ticular applications or system objectives. Other types are under investigation.
The International Standards defining the access technologies are as follows:
ISO/IEC 8802-3 [ANSI/IEEE Std 802.31, a bus utilizing CSMAKD as the access method.
a>
b) ISO/IEC 8802-4 [ANSI/IEEE Std 802.41, a bus utilizing token passing as the access method.
ISO/IEC 8802-5 [ANSI/IEEE Std 802.51, a ring utilizing token passing as the access method.
C>
d) ISO/IEC 8802-6 [ANSI/IEEE Std 802.61, a dual bus utilizing distributed queuing as the access
method.
IS0 8802-7, a ring utilizing slotted ring as the access method.
e>
f) ISO/IEC 8802-9 [ANSI/IEEE Std 802.91, a unified access method offering global integrated services
to the desktop by accessing a variety of networks.
ISO/IEC TR 8802-l provides an overview of the LAN/MAN standards, along with details of their document
numbering.
ISO/IEC 8802-2 [ANSI/IEEE Std 802.21, Logical Link ControZ, is used in conjunction with the medium
access standards to provide the data link layer service to network layer protocols.
ISOLIEC 10038 [ANSI/IEEE Std 802.lD], Media Access Control (MAC) bridges, specifies an architecture
and protocol for the interconnection of IEEE 802 LANs below the level of the logical link control protocol.
ISO/IEC 15802-2 [ANSI/IEEE Std 802.lB], LAN/MAN Management, defines an Open Systems
Interconnection (OSI) management-compatible architecture, and services and protocol elements for use in a
LAN/MAN environment for performing remote management.
ISO/IEC 15802-4 [ANSI/IEEE Std 802. lE], System Load ProtocoZ, specifies a set of services and protocol
for those aspects of management concerned with the loading of systems in ISO/IEC LAN/MAN environ-
ments.
The main body of the International Standard serves for both the ISO/IEC 8802-9: 1996 and ANSI/IEEE Std
802.9, 1996 Edition standards. IS0 and IEEE each have a unique foreword.
. . .
ANSI/IEEE Std 802.9,1996 Edition
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordi-
nating Committees of the IEEE Standards Board. Members of the committees serve voluntarily and
without compensation. They are not necessarily members of the Institute. The standards developed
within IEEE represent a consensus of the broad expertise on the subject within the Institute as well
as those activities outside of IEEE that have expressed an interest in participating in the develop-
ment of the standard.
Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply
that there are no other ways to produce, test, measure, purchase, market, or provide other goods and
services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the
time a standard is approved and issued is subject to change brought about through developments in
the state of the art and comments received from users of the standard. Every IEEE Standard is sub-
jected to review at least every five years for revision or reaffirmation. When a document is more
than five years old and has not been reaffirmed, it is reasonable to conclude that its contents,
although still of some value, do not wholly reflect the present state of the art. Users are cautioned to
check to determine that they have the latest edition of any IEEE Standard.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of
membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a
proposed change of text, together with appropriate supporting comments.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as
they relate to specific applications. When the need for interpretations is brought to the attention of
IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards rep-
resent a consensus of all concerned interests, it is important to ensure that any interpretation has
also received the concurrence of a balance of interests. For this reason IEEE and the members of its
societies and Standards Coordinating Committees are not able to provide an instant response to
interpretation requests except in those cases where the matter has previously received formal con-
sideration.
Comments on standards and requests for interpretations should be addressed to:
Secretary, IEEE Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855- 133 1, USA
use of sub-
h respect to
responsible
conducting
The patent holder has, however, filed a statement of assurance that it will grant a license under these
rights without compensation or under reasonable rates and nondiscriminatory, reasonable terms and
conditions to all applicants desiring to obtain such a license. The IEEE makes no representation as to
the reasonableness of rates and/or terms and conditions of the license agreement offered by the patent
holder. Contact information may be obtained from the IEEE Standards Department.
Authorization to photocopy portions of any individual standard for internal or personal use is granted by the
Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright
Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Cus-
tomer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; [phone]. Permission to photocopy
portions of any individual s tandard for educational classroom
use can also be obtained through the Copyright
Clearance Center
iv
Foreword to ANSI/IEEE Std 802.9,1996 Edition
This standard is part of a family of standards for local and metropolitan area networks. The relationship
between the standard and other members of the family is shown below. (The numbers in the figure refer to
IEEE standard numbers.)
802.2 LOGICAL LINK CONTROL
DATA
802.1 BRIDGING
LINK
LAYER
802.3 802.4 802.5 802.6
802.9 802.11 802.12
MEDIUM MEDIUM MEDIUM MEDIUM MEDIUM MEDIUM MEDIUM
ACCESS
ACCESS ACCESS ACCESS ACCESS ACCESS ACCESS
,
802.3 802.4 802.5 802.6 802.9 802.11
802.12 PHYSICAL
PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL
LAYER
.
* Formerly IEEE Std 802.1A.
This family of standards deals with the Physical and Data Link layers as defined by the International Organi-
zation for Standardization/International Electrotechnical Commission (ISO/IEC) Open Systems Intercon-
nection Basic Reference Model (ISO/IEC 7498-l: 1994). The access standards define several types of
medium access technologies and associated physical media, each appropriate for particular applications or
system objectives. Other types are under investigation.
The standards defining the access technologies are as follows:
Overview and Architecture. This standard provides an overview to the
0 IEEE Std 802
family of IEEE 802 Standards. This document forms part of the 802.1
scope of work.
LAN/MAN Management. Defines an Open Systems Interconnection (OSI)
l ANSI/IEEE Std 802.1B
management-compatible architecture, and services and protocol elements
and 802.lk
for use in a LAN/MAN environment for performing remote management.
[ISO/IEC 15802-21
MAC Bridging. Specifies an architecture and protocol for the interconnec-
0 ANSI/IEEE Std 802.1D
tion of IEEE 802 LANs below the MAC service boundary.
[ISO/IEC 10038]
System Load Protocol. Specifies a set of services and protocol for those
0 ANSI/IEEE Std 802.1E
[ISO/IEC 15802-41 aspects of management concerned with the loading of systems on IEEE
802 LANs.
Logical Link Control
0 ANSI/IEEE Std 802.2
[ISO/IEC 8802-21
CSMAKD Access Method and Physical Layer Specifications
l ANSI/IEEE Std 802.3
[ISO/IEC 8802-31
l ANSI/IEEE Std 802.4 Token Passing Bus Access Method and Physical Layer Specifications
[ISO/IEC 8802-4]
0 ANSI/IEEE Std 802.5 Token Ring Access Method and Physical Layer Specifications
[ISO/IEC 8802-51
Q ANSI/IEEE Std 802.6 Distributed Queue Dual Bus Access Method and Physical Layer
[ISO/IEC 8802-61 Specifications
Integrated Services (IS) LAN Inter$uce at the Medium Access Control
e ANSI/IEEE Std 802.9
[ISO/IEC 8802-91 (MAC) and Physical (PHY) Layers
8 ANSI/IEEE Std 802.10 Interoperuble LAN/MAN Security
e ANSI/IEEE Std 802.12 Demand Priority Access Method, PhysicaL Layer and Repeater
Specifications
In addition to the family of standards, the following is a recommended practice for a common Physical
Layer technology:
EEE Recommended Practice for Broadband Local Area Networks
0 IEEE Std 802.7
The following additional working groups have authorized standards projects under development:
e IEEE 802.11 Wireless LAN Medium Access Control (MAC) Subluyer and Physical
Layer Specifications
0 IEEE 802.14 Stundurd Protocol for Cable-TV Bused Broadband Communication
Network
The reader of this standard is urged to become familiar with the complete family of standards.
onfoamance test methodology
An additional standards series, identified by the number 1802, has been established to identify the
conformance test methodology documents for the 802 family of standards. Thus the conformance test
documents for 802.3 are numbered 1802.3, the conformance test documents for 802.5 will be 1802.5, and so
on. Similarly, IS0 will use 18802 to number conformance test standards for 8802 standards.
lUUSIBIlXE Std 802.9, 1 Edition
The ongoing work of the IEEE 802 committee has resulted in standards for data communications in a local
area network (LAN) environment. As office workstations have proliferated, however, the demand for LANs
has substantially increased. This has led to the inevitable diversification in market requirements.
Since the typical office worker requires access to both data and voice services, among others, at the desktop,
there has been a growing trend toward integrated services (IS), namely voice, data, and video. Due to the
increasing need for facsimile, image transfer, and video services, these services are included in the general
category of the integration of voice and data services. Such integration offers potential economies to the
business customer in terms of reduced components (one port per station instead of two or more), and in
simpler management and maintenance (one network instead of two or more).
The provision of voice service is generally effected using unshielded twisted-pair wire. Not only is
this
medium widespread in typical office environments, but it is also inexpensive and easy to install
and
Vi
c
maintain. In the vast majority of installations, there is spare capacity, and in these cases, the use of such a
medium is essentially free since the need for rewiring is significantly reduced. Moreover, with existing
technology, it is possible to provide medium- to high-performance data service over the unshielded twisted-
pair wire. This places special emphasis on the use of the unshielded twisted-pair wire to provide IS services.
This standard extends the scope and capability of existing twisted-pair wiring and thus reduces the incentive
for overlay wiring systems.
W ith respect to the provision of integrated services, there has been ongoing work in other standards bodies,
notably, the International Telecommunication Union-Telecommunication S tandardization Sector (ITU-T)
on the provision of such services through integrated services digital networks (ISDNs). While the principal
focus has been the provision of such services using public networks, efforts are under way [notably, in the
European Compu ter Manu facturers Association (ECMA)] to extend such services to customer premises
networks.
This standard defines a unified access me thod that offers global integrated services to the desktop by access-
ing a variety of publicly and privately administered backbone networks (e.g., ANS I FDDI, IEEE 802.x ’, and
ISDN). This standard will enable integrated services termial adapters (ISTEs) to be attached to IEEE 802.9
LANs and will allow them to communicate with other IS stations as well as data-only stations, voice-only
stations, and premises-based networks offering ISDN services. In addition, it specifies the use of unshielded
telephone twisted pair as the primary medium of distribution.
The use of terminal adaptor (TA) devices will permit the direct coupling of native mode terminal devices
such as data-only modules, voice modules, and ISDN basic rate terminals to the IEEE 802.9 interface. This
standard has been designed to accommodate the adaptation of ISDN basic rate station devices and IEEE
802.x station devices to the IEEE 802.9 interface. In summary, this standard represents the integration of
IEEE 802 services and ISDN services.
This standard contains state-of-the-art ma terial. The area covered by this standard is undergoing evolution.
Revisions are anticipated to this standard within the next few years to clarify existing ma terial, to correct
possible errors, and to incorporate new related ma terial. Information on the current revision state of this and
other IEEE 802 standards may be obtained from
Secretary, IEEE S tandards Board
445 Hoes Lane
P .O . Box 1331
Piscataway, NJ 0885- 133 1 USA
‘IEEE 802.x refers to the entire family of IEEE 802 standards.
vii
Participants
When the IEEE Project 802.9 Working Group approved IEEE Std 802.9-1994, it had the following
.
membership:
Dhadesngoor ’R. Vaman, Chair Ronald Kemper Sr., Vice Chair
Wayne A. Zakowski, Editor George Westwick, Secretary
Sven Olof Akerlund Ingrid Fromm Floyd Ross
Dan Ater Stephen Hall Everett Rigsbee
Kwame Boakyet Tohru Kazawa Chandos Rypinskit
John Boa@ Kansuke Kurayanagi Hiroshi Shimizu
Richard Brand William Lee Toshiro Suzuki
Dale Buchholz Kiyoshi Maruyama Kenta Takumi
Allan Cobb* Takanori Miyamoto Norman Tester
John Conville John Moughton Ian Thomas
Felix Diaz Tony Parker Kazuo Unemoto
Earl Emerson Keith Patterson* Surya Varanasi
Staffan Fredricsson Sanjay Popli Kojiro Watanabe
* Past Chair >
7 Past Editor
$ Past Secretary
The following persons were on the balloting committee:
Gary C. Kessler Robert Rosenthal
William B. Adams
Albert Bernhard Youngbum Kim Floyd E. Ross
Demosthenes Kostas Rainer A. Rueppel
Robert M. Amy
Randolph S. Little Christoph Ruland
Yong Myung Baeg
Asa 0. Bishop Ming T. Liu Norman Schneidewind
Donald C. Loughry Adarshpal S. Sethi
Michael J. Caldwell
Nam C. Low Donald A. Sheppard
George Carson
Gottfried W. R. Luderer Leo Sintonen
Basilio Chen
Peter Martini
Robert Crowder Saragur M. Srinidhi
Robert A. Donnan Richard McBride Joseph Stevenson
William C. McDonald
Sourav Kumar Dutta Clay S tocklin
Judith A. Edwards A. E. Methiwalla Fred J. Strauss
Philip H. Enslow Ann Miller E. D. Sykas
Changxin Fan David S. Millman Ahmed N. Tantawy
John W. Fendrich John E. Montague Geoffrey 0. Thompson
Harvey A. Freeman Kinji Mori Robert Tripi
Ingrid Fromm David J. Morris Mark-Rene Uchida
Robert Gagliano D. O ’Mahony Dhadesugoor R. Vaman
D. G. Gan Charles Oestereicher Raymond Van Houtte
Isaac Ghansah Thomas E. Phillips Punj Vikram
Julio Gonzalez-Sanz Art J. Pina James T. Vorhies
G. L. Hollander Yang Qianli Carry M. Vornbrock
Paul L. Hutton Fernando Ramos Alan J. Weissberger
Richard J. Iliff John P. Riganati Raymond Wenig
Raj Jain Edouard Y. Rocher A. Jameson West
Anura P. Janasumana Oren Yuen
. . .
VI11
When the IEEE Standards Board approved this standard on 22 September 1994, it had the following
membership:
Donald C. Loughry, Vice Chair
Wallace S. Read, Chair
Andrew G. Salem, Secretary
Donald N. Heirman Joseph L. Koepfinger*
Gilles A. Baril
D. N. “Jim” Logothetis
Richard J. Holleman
Bruce B. Barrow
Jim Isaak L. Bruce McClung
Jose A. Berrios de la Paz
Ben C. Johnson Marco W. Migliaro
Clyde R. Camp
Mary Lou Padgett
Sonny Kasturi
James Costantino
Lorraine C. Kevra Arthur K. Reilly
Stephen L. Diamond
E. G. “Al” Kiener Ronald H. Reimer
Donald C. Fleckenstein
Gary S. Robinson
Ivor N. Knight
Jay Fors ter*
Leonard L. Tripp
Ramiro Garcia
*Member Emeritus
Also included are the following nonvoting IEEE Standards Board liaisons:
Satish K. Aggarwal
James Beall
Richard B. Engelman
Robert E. Hebner
David E. Soffrin
Valerie E. Zelenty
IEEE Standards Project Editor
This standard was approved by the American National Standards Institute on 15 March 1995.
Note that editorial changes were made to the IEEE standard to accommodate concerns raised during
the ISO/IEC JTC 1 balloting process. These are indicated in the text by a change bar (such as shown
at the left of this paragraph).
iX
Contents
PAGE
CHAPTER
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope and purpose
n
L
1.2 Notation . . . . . . . . . . . . . . . . .0.~.
1.3 Service model .
..............................................................................................................
1.4 Document organization
2. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.“.
3. Definitions . . . . . . . . .~.
. . . . . . . . . . . .0.
4. Abbreviations
. . . . . . . . . . . . . . . . . . . .“.~.
5. Architecture
.....................................................................................................
5.1 Overview and basic concepts
.......................................................................................................................
5.2 Application areas
..........................................................................................
5.3 Layers and layer service boundaries
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~.
6 . Frame structure
....................................................................................................................................
6.1 Overview
...............................................................................................................
6.2 Numbering convention
...........................................................................................................
6.3 Order of bit transmission
.....................................
6.4 Order of octet transmission for fields which span more than one octet
.................................................................................................................
6.5 TDM frame structure
................................................................................................................
6.6 Packet frame structure
7. Service specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Packet services .
............................................................................................................
7.2 Convergence of services
.................................................................................................................
7.3 Management services
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8. Detailed specification of the medium access control (MAC) sublayer
8.1 Overview of the MAC sublayer .
.................................................................................
8.2 The ISLAN MAC protocol engine model
8.3 P channel access control .
..................... 13 1
8.4 Timing relationship of TDM frames exchanged between the ISTE and the AU
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9. Detailed specification of the Physical (PHY) Layer
..................................................................................................................................
9.1 Overview
.......................................................................................................................
9.2 HMUX sublayer
...............................................................................................................................
9.3 PS sublayer
...............................................................................
9.4 PMD sublayer for 4.096 Mb/s application
..........................................................
9.5 PMD sublayer for higher rate (20.48 Mb/s) application
9.6 Connector .
9.7 Powering considerations .

PAGE
CHAPTER
................................................................... 210
9.8 Medium cable characteristics-4096 Mb/s PMD
................................................................... 213
9.9 Medium cable characteristics-20.48 Mb/s PMD
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
10. ISLAN layer management
........................................................................................................................... 215
10.1 Introduction
.......................................... 215
10.2 Characteristics of the ISLAN interface relevant to management
................................................................................... 216
10.3 OS1 network management framework
............................................. 220
10.4 Relationship of IEEE 802.9 subnetwork management entities
.............................................................. 222
10.5 ISDN network management information exchange
........................................ 223
10.6 Management transport channels within the IEEE 802.9 interface
..................................................................... 224
10.7 The structure of OS1 management information
.............................................
10.8 OS1 management functional areas in the ISLAN environment
.....................................................................
10.9 Inheritance hierarchy for ISLAN management
............................................................
10.10 The containment hierarchy for ISLAN management
.............................................
10.11 The OS1 registration hierarchy for ISLAN layer management
...........................................................................
10.12 The definition of the ISLAN systems MOs
........................................................................... 239
10.13 Definition of the ISLAN layer MO classes
..........................................
10.14 Management of the ISDN user/network interface in the ISLAN
10.15 MIB tables .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11. Signalling and ISDN management scope
11.1 Introduction .
..............................................................................................
11.2 General overview of the service
........................................................................................
11.3 Requirements for signalling support
.......................................................................................
11.4 CCITT Q.93 1 architecture overview
............................................................................................
11.5 P channel call control procedures
.......................................................................
11.6 Interface between CCITT Q.931 and the HMC
11.7 Addressing .
11.8 Configuration topologies .
11.9 ISDN management functions .
ANNEX
Annex A (normative) Protocol implementation conformance statement (PICS) proforma . . . . . . . . . . . . . . . . . . . . . .29 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Annex B (normative) Managed object conformance statement (MOCS)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annex C (normative) GDMO and ASN. 1 specification of management information
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annex D (normative) Recommendations for signalling procedures
Annex E (informative) Architecture of the access unit (AU) and guidelines for implementation . . . . . . . . . . . 377
Annex F (informative) Sequence and description language (SDL) description of the information flow
across layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Annex G (informative) Multimedia security control provision in IEEE 802.9 ISLAN
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annex H (informative) Address interworking across an IEEE 802.9 network
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Annex I (informative) Support of cell relay bearer service
xi
This page intentionally left blank

Information technology-
Telecommunications and information exchange between systems-
Local and metropolitan area networks-Specific requirements-
Part 9: Integrated Services (IS) LAN Interface
at the Medium Access Control (MAC) and
Physical (PHY) Layers
1. Overview
1.1 Scope and purpose
The scope of this International Standard is to
- Develop an ISLAN interface at the medium access control (MAC) sublayer and the Physical (PHY)
Layer compatible with IEEE 802.x1 and ISDN standards and architectures
- Develop an ISLAN interface that operates independently from the backbone network
- Focus upon unshielded twisted-pair wiring as the primary distribution medium
- Enable implementation of IS terminal equipment (ISTE) that accesses IEEE 802 LAN and ISDN
services through a common interface
The body of this International Standard
- Defines the service provided by the MAC sublayer to the IEEE 802 Logical Link Control (LLC)
sublayer and management, and describes the services provided by the PHY Layer to the MAC
sublayer and management in terms of service primitives and associated parameters
- Describes the services provided by the Physical Layer (PHY MUX) to support a basic rate interface
.
(BRI) ISDN in terms of service primitives and associated parameters
--
Describes the services provided by the PHY MUX to the isochronous channels
- Specifies the MAC functions that allow ISTEs access to one another and to LANs providing IEEE
802 services and/or ISDN services
- Specifies the frame format for the MAC frame
-
Defines the MAC protocol
- Specifies the channel structure and frame format of the time division multiplexed (TDM) frame
‘IEEE 802.x refers to the entire family of IEEE 802 standards.

ISO/IEC 8802-g: 1996(E)
LOCAL AND METROPOLITAN AREA NETWORKS:
ANSI/IEEE Std 802.9, 1996 Edition
- Specifies the PHY Layer functions over unshielded telephone twisted-pair (UTTP) cable
- Specifies the characteristics of the UTTP attachment of the station to the access unit (AU) including
the specification of the medium interface connector
- Specifies the definition of MAC and PHY managed objects (MOs)
- Describes recommended ISDN signalling and management methods to coordinate the multiple
channels operated between ISTEs and the AU
The normative annexes provide
- The Protocol Implementation Conformance Statement (PICS) proforma
- The Managed Object Conformance Statement (MOCS)
- The Guidelines for the Definition of Managed Objects (GDMO) specifications
- Supplemental recommendations on the use of CCITT Q.93x signalling procedures
The informative annexes provide
- Reference models of common configurations as guidelines for implementation
- A sequence and description language (SDL) description of the information flow across protocol
layers
- Description of an optional remote secure control (RSC) procedure to invoke secure communication
device (SCD) operations
- Recommendations for a common, consistent synthesis of ISDN and IEEE 802 that conforms with the
addressing of ISTE devices and services
- Description of a mechanism to support the transport of a broadband ISDN conformant “cell” bearer
service
1.2 Notation
1.2.1 Service specification method and notation
This subclause describes the method of specification of the services required of the MAC sublayer by the
LLC sublayer as well as of the PHY Layer by the MAC sublayer of the P channel, the Data Link Layer of
the D channel, and the services provided on the B and C channels.
In general, the services of a layer (or sublayer) are the capabilities that it offers to a user in the next higher
layer (or sublayer). In order to provide its services, a layer builds its functions on the services that it requires
from the next lower layer. Figure l-l illustrates this notion of service hierarchy and shows the relationship of
the two corresponding N Layer users.

ISO/IEC 8802-g: 1996(E)
INTEGRATED SERVICES (IS) AT THE MAC AND PHY LAYERS ANSI/IEEE Std 802.9, 1996 Edition
I
N LAYER ;
c
SERVICE
I
ACCESS ’
N LAYER
N LAYER SERVICE PROVIDER
Figure l-1 -Layer service model
This information flow is modeled by discrete, instantaneous events that characterize the provision of a
service. Each event consists of passing a service primitive from one layer to the other through an N Layer
service access point (SAP) associated with an N+l Layer service user. These SAPS are shown in figure l-l.
Service primitives convey the information required to provide a particular service. These service primitives
are an abstraction in that they specify only the service provided rather than the means by which the service is
provided. This definition of layer service is independent of any particular interface implementation, and is
not subject to conformance testing requirements.
In order to comply with the service message flow signals described in the CCITT Recommendations on
ISDN, it is necessary to consider all four primitive flow types.
Request primitive. This primitive is passed from the N+l Layer service user to the N Layer (or
a>
sublayer) to request that a service be initiated.
b)
Indication primitive. This primitive is passed from the N Layer (or sublayer) to the N+l Layer
service user to indicate an internal N Layer event that is significant to the N+l Layer service user.
This may be logically related to a remote service request, or may be caused by an event internal to
the N Layer.
Response primitive. This primitive is passed from the N+l Layer service user to the N Layer (or
C>
sublayer) to complete a procedure previously invoked by an indication primitive.
Confirm primitive. This primitive is passed from the N Layer (or sublayer) to the N+l Layer service
d)
user to convey the results of one or more associated previous service requests.
Figure l-2 shows the service primitives and N+l Layer peer protocol entities associated with the two
corresponding N+l Layer service users. Services are specified by describing the service primitives and
parameters that characterize each service. A service may have one or more related primitives that constitute
the activity that is related to the particular service. Each service primitive may have zero or more parameters
that convey the information required to provide the service.
ISO/I EC 8802-g: 1996(E)
LOCAL AND METROPOLITAN AREA NETWORKS:
ANSI/IEEE Std 802.9, 1996 Edition
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
- INDICATION
REQUEST -
4- RESPONSE
CONFIRM -
Figure 1-2-Service primitives
Figure l-3 illustrates the end-to-end relationship of the service primitives and the N Layer peer protocol
entities across a communication network.
NETWORK SIDE B
NETWORK SIDE A
w--e-------
--w---s
~I--- --a-------
1 1
\ l 1
NI 1 N LAYER
h I
. . ,AYER
1 1
L I
1 SERVICE
“‘RVICE 1
USER
jSER
1 N+l LAYER i
s----s
L.----IL-------
INDICATION
REQUEST
CONFIRM RESPONSE
SIDE B
SIDE A
N LAYER SERVICE
N LAYER SERVICE
PROVIDER
PROVIDER
Figure 1-3-End-to-end relationship of service primitives
1.2.2 Timing relationship between service primitives
Figure l-4 a) illustrates the flow from the service user to the service provider for a request. Figure l-4 b)
illustrates the notification to the service user of an event that has occurred in the service provider. Figure l-4
c) illustrates the event wherein two separate service users are simultaneously making a service request at
each end of the peer communication. Figure l-4 d) illustrates the event wherein both ends of a communica-
tion link have the service provider sending up an indication of an event occurrence. Figure l-4 e) illustrates
the common situation wherein a “request” from a service user at one side of a network is sent in the form of
a message action across the network to the peer side. The service provider at the other end of the network
will report the incoming protocol packet as an “indication.” Figure l-4 f) depicts a communication flow in
which all four types of primitives are used as part of a communication between two ends of the network.
ISO/I EC 8802-g: 1996(E)
ANSI/IEEE Std 802.9, 1996 Edition
INTEGRATED SERVICES (IS) AT THE MAC AND PHY LAYERS
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
REQUEST -
a) Request from user to provider
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
A INDICATION
b) Indication from provider to user
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER ’
a- REQUEST
REQUEST -
c) Independent simultaneous request at the two ends
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
4 INDICATION
INDICATION -
d) Independent simultaneous indications at the two ends
Figure l-4-Timing relationship between service primitives

ISO/IEC 8802-g: 1996(E)
LOCAL AND METROPOLITAN AREA NETWORKS:
ANSI/IEEE Std 802.9, 1996 Edition
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
-.
REQUEST h
‘1.
\
‘1.
‘1.
\
‘\.
\
-w INDICATION
x
e) Request leading to an indication at the peer entity
N LAYER
N+l LAYER
N+l LAYER
SERVICE
SERVICE
SERVICE
PROVIDER
USER
USER
. - -- z -. -
REQUEST -,
INDICATJ
IL 1, RESPONSE
----
-1-1
& “‘------
CONFIRM ’-
f) Cycle of interactions between peer entities
Figure I-4-Timing relationship between service primitives
1.3 Service model
In the general N Layer service model, the N+l Layer service user communicates with the N Layer
...