IEEE Std 802.9-1994
`
`IEEE Standards for Local and
`Metropolitan Area Networks:
`Integrated Services (IS) LAN Interface
`at the Medium Access Control (:MAC)
`and Physical (PHY) Layers
`
`Sponsor
`Technical Committee on Computer Communications
`of the
`IEEE Computer Society
`
`Approved September 22,1994
`
`IEEE Standards Board
`
`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 80:!.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), medium access
`control (MAC) sublayer, metropolitan area network (MAN), physical (PHY) layer, physical medium
`dependent, physical signalling, private switching network, protocol data unit (PDU), Seirvice access point,
`time division multiplexer (TDM)
`
`The Institute of Electrical and Electronics Engineers, Inc.
`345 East 47th Street, New York, NY 1001 7-2394, USA
`
`Copyright 0 1994 by the Institute of Electrical and Electronics Engineers, Inc.
`All rights reserved. Published 1994. Printed in the United States of America.
`
`ISBN 1-55937-456-X
`
`No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwi:se, without the prior
`written permission of the publisher.
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 1
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`IEEE Standards documents are developed within the Technical Committees of the
`IEEE Societies and the Standards Coordinating 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 E E E that have expressed an interest in partici-
`pating in the development 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, mar-
`ket, 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 subjected to
`review at least every five years for revision or reaffmnation. 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 presenl 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 docu-
`ments 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 appro-
`priate responses. Since IEEE Standards represent a consensus of all concerned inter-
`ests, 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 technical com-
`mittees are not able to provide an instant response to interpretation requests except in
`those cases where the matter has previously received formal consideration.
`
`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-1331
`USA
`
`approval by the Institute of Electrical and Electronics Engineers does not mean that
`using such technology for the purpose of conforming to such standards is authorized
`by the patent owner. It is the obligation of the user of such technology to obtain all
`necessary permissions.
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 2
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`In t rod uct ion
`
`[This introduction is not a part of IEEE Std 802.9-1994, IEEE Standards for Local and Metropolitan Area Networks: Integrated
`Services (IS) LAN Interface at the Medium Access Control (MAC) and Physical (PHY) Layers.]
`
`This standard is part of a family of standards for local and metropolitan area networks. The relationship of
`the members of the family to each other is shown below. (The numbers in the figure refer to IEEE standard
`numbers.)
`
`I
`
`802.2 LOGICAL LINK
`
`802.1 BRIDGING
`
`I
`
`DATA
`LINK
`
`-1
`
`802.3
`MEDIUM
`ACCESS
`
`802.4
`MEDIUM
`ACCESS
`
`802.5
`MEDIUM
`ACCESS
`
`802.3
`PHYSICAL
`
`802.4
`PHYSICAL
`
`802.5
`PHYSlCAl
`
`-U-
`* Formerly IEEE Std 802.1A.
`
`I 802.12 I PHYSICAL
`
`PHYSICAL
`
`LAYER
`
`ers as defined 1bY the International
`This family of standards deals with the
`Organization for Standardization (ISO) Open Systems Interconnection Basic Reference Model
`(IS0 7498 : 1984). The access standards define several types
`edium access technolQ$es and associated
`physical media, each appropriate for particular applications
`ystem objectives. Other types are under
`investigation. The IEEE 802.9 ISLAN Interface Standard sp
`s both isochronous and packet mode ser-
`vices, and provides access to ISDN and other backbone networks for service provisioning.
`
`The standards defining these technologies are as follows:
`
`IEEE Std 802a:
`
`ISOAEC DIS 15802-2
`[IEEE Std 802.1B and 802.lkl:
`
`ISOAEC 10038
`[ANSIAEEE Std 802.1Dl:
`
`Overview and Architecture. This standard ]provides an over-
`view to the family of IEEE 802 Standards. This document
`forms part of the 802.1 scope of work.
`
`LANMAN Management. Defines an Open Systems
`Interconnection (OSI) management-compaiible architecture,
`and services and protocol elements for use in a LANMAN
`environment for performing remote management.
`
`MAC Bridging. Specifies an architecture and protocol for the
`interconnection of IEEE 802 LANs below the MAC service
`boundary.
`
`aThe 802 Architecture and Overview Specification, originally known as IEEE Std 802.1A, has been renumbeivd as IEEE Std 802. This
`has been done to accommodate recognition of the base standard in a family of standards. References to IE:EE Std 802.1A should be
`considered as references to IEEE Std 802.
`
`iii
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 3
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`ISOAEC 15802-4
`[ANSVIEEE Std 802.1El:
`
`System Load Protocol. Specifies a set of services and protocol
`for those aspects of management concerned with the loading of
`systems on IEEE 802 LANs.
`
`ISODEC 8802-2 [ANSUIEEE Std 802.21: Logical Link Control
`
`* ISOAEC 8802-3 [ANSI/IEEE Std 802.31: CSMA/CD Access Method and Physical Layer Specifications
`
`ISO/IEC 8802-4 [ANSVIEEE Std 802.41: Token Bus Access Method and Physical Layer Specifications
`
`ISOAEC 8802-5 [ANSUIEEE Std 802.51: Token Ring Access Method and Physical Layer Specifications
`
`ISODEC 8802-6 [ANSUIEEE Std 802.61: Distributed Queue Dual Bus Access Method and Physical
`Layer Specifications
`
`IEEE Std 802.9:
`
`IEEE Std 802.10:
`
`Integrated Services (IS) LAN Interface at the Medium Access
`Control (MAC) and Physical (PHY) Layers
`
`Interoperable LAN/MAN Security, Currently approved:
`Secure Data Exchange (SDE)
`
`In addition to the family of standards, the following is a recommended practice for a common technology:
`
`IEEE Std 802.7:
`
`IEEE Recommended Practice for Broadband Local Area
`Networks
`
`The following additional working groups have authorized standards projects under development:
`
`IEEE 802.11 :
`
`IEEE 802.12:
`
`IEEE 802.14:
`
`Wireless LAN Medium Access Control (MAC) and Physical
`Layer Specifications
`
`Demand Priority Access MethodPhysical Layer Specifications
`
`Standard Protocol for Cable-TV Based Broadband
`Communication Network
`
`Conformance 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.
`
`iv
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 4
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`IEEE Std 802.9-1 994
`
`The ongoing work of the IEEE 802 committee has resulted in standards for data commiunications 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 ofhers, 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
`maintain. In the vast majority of installations, there is spare capacity, and in these casts, 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.
`
`With respect to the provision of integrated s
`een ongoing work in other standards bodies,
`notably, the International Telecommunication Union-Telecommunication Standardization 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 Computer Manufacturers Association (ECMA)] to extend such services tci customer premises
`networks.
`
`This standard defines a unified access method that offers global integrated services to the desktop for a
`variety of publicly and privately administered backbone networks (e.g., ANSI FDDL IEEE 802.xb, and
`ISDN). This standard will enable 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.
`
`bIEEE 802.x refers to the entire family of IEEE 802 standards.
`
`V
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 5
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`Participants
`
`When the IEEE Project 802.9 Working Group approved IEEE Std 802.9-1994, it had the following
`membership:
`
`Dhadesugoor R. Vaman, Chair
`Wayne A. Zakowski, Editor
`
`Ronald Kemper Sr., Vice Chair
`George Westwick, Secretary
`
`Sven Olof Akerlund
`Dan Ater
`Kwame Boakyet
`John BoalS
`Richard Brand
`Dale Buchholz
`Allan Cobb*
`John Conville
`Felix Diaz
`Earl Emerson
`Staffan Fredricsson
`* Past Chair
`t Past Editor
`$ Past Secretary
`
`lngrid Fromm
`Stephen Hall
`Tohru Kazawa
`Kansuke Kurayanagi
`William Lee
`Kiyoshi Maruyama
`Takmori Miyamoto
`John Moughton
`Tony Parker
`Keith Patterson*
`Sanjay Popli
`
`Floyd Ross
`Everett Rigsbee
`Chandos Rypinskit
`Hiroshi Shimizu
`Toshiro Suzuki
`Kenta Takumi
`Norman Tester
`Ian Thomas
`Kazuo Unemoto
`Surya Varanasi
`Kojiro Watanabe
`
`The following persons were on the balloting committee:
`
`William B. A d a m
`Albert Bernhard
`Robert M. Amy
`Yong Myung Baeg
`Asa 0. Bishop
`Michael J. Caldwell
`George Carson
`Basilio Chen
`Robert Crowder
`Robert A. Donnan
`Sourav Kumar Dutta
`Judith A. Edwards
`Philip H. Enslow
`Changxin Fan
`John W. Fendrich
`Harvey A. Freeman
`Ingrid Fromm
`Robert Gagliano
`D. G. Gan
`Isaac Ghansah
`Julio Gonzalez-Sanz
`G. L. Hollander
`Paul L. Hutton
`Richard J. Iliff
`Raj Jain
`Anura P. Janasumana
`
`Gary C. Kessler
`Youngbum Kim
`Demosthenes Kostas
`Randolph S. Little
`Ming T. Liu
`Donald C. Loughry
`Nam C. Low
`Gottfried W. R. Luderer
`Peter Martini
`Richard McBride
`William C. McDonald
`A. E. Methiwalla
`Ann Miller
`David S. Millman
`Zohn E. Montague
`Kinji Mori
`David J. Morris
`D.O'Mahony
`Charles Oestereicher
`Thomas E. Phillips
`Art J. Pina
`Yang Qianli
`Fernando Ramos
`John P. Riganati
`Ekiouard Y. Rocher
`
`Robert Rosenthal
`Floyd E. Ross
`Rainer A. Rueppel
`Christoph Ruland
`Norman Schneidewind
`Adarshpal S. Sethi
`Donald A. Sheppard
`Leo Sintonen
`Saragur M. Srinidhi
`Joseph Stevenson
`Clay Stocklin
`Fred J. Strauss
`E. D. Sykas
`Ahmed N. Tantawy
`Geoffrey 0. Thompson
`Robert Tripi
`Mark-Rene Uchida
`Dhadesugoor R. Vaman
`Raymond Van Houtte
`h n j Vikram
`James T. Vorhies
`Garry M. Vornbrock
`Alan J. Weissberger
`Raymond Wenig
`A. Jameson West
`Oren Yuen
`
`vi
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 6
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`When the IEEE Standards Board approved this standard o n September 22, 1994, it had the following
`membership:
`
`Wallace S. Read, Chair
`
`Donald C. Loughry, Vice Chair
`Andrew G. Salem, Secretary
`
`Gilles A. Baril
`Bruce B. Barrow
`Jos6 A. Berrios de la Paz
`Clyde R. Camp
`James Costantino
`Stephen L. Diamond
`Donald C. Fleckenstein
`Jay Forster*
`Ramiro Garcia
`
`*Member Emeritus
`
`Donald N. Heirman
`Richard J. Holleman
`Jim Isaak
`Ben C. Johnson
`Sonny Kasturi
`Lorraine C. Kevra
`E. G. “Al” Kiener
`Ivor N. Knight
`
`Joseph L. Koepfinger*
`D. N. “Jim” Logothetis
`L. Bruce McClung
`Marco W. Migliaro
`Mary Lou Padgett
`Arthur K. Reilly
`Ronald H. Reimer
`Gary S . Robinson
`Leoinard L. Tripp
`
`Also included are the following nonvoting IEEE Standards Board liaisons:
`
`Satish K. Aggarwal
`James Beall
`Richard B. Engelman
`Robert E. Hcbner
`David E. Soffrin
`
`Valerie E. Zelenty
`E Stundurds Projecl Editor
`
`,
`
`AppletalkB is a registered trademark of Apple Computer, Inc.
`NetbiosB and IBMB are registered trademarks of International Business Machines, Inc.
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`vii
`
`Juniper Ex 1032 - 7
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`Contents
`
`CHAPTER
`Overview ..............................................................................................................................................
`
`1 .
`
`PAGE
`
`1
`
`1.1 Scope and purpose ....................................................................................................................... 1
`1.2 Notation ........................................................................................................................................ 2
`1.3 Service model ............................................................................................................................... 6
`1.4 Document organization ..............................................................................................................
`11
`
`2 .
`
`3 .
`
`4 .
`
`5 .
`
`References .......................................................................................................................................... 13
`
`Definitions ..........................................................................................................................................
`
`19
`
`Abbreviations ..................................................................................................................................... 23
`
`Architecture ........................................................................................................................................
`
`29
`
`Overview and basic concepts .....................................................................................................
`29
`5.1
`5.2 Application areas ....................................................................................................................... 32
`Layers and layer service boundaries .......................................................................................... 33
`5.3
`
`6 .
`
`Frame structure .................................................................................................................................. 41
`
`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 .....................................
`42
`................... 42
`6.5 TDM frame structure .............
`....................................................................
`54
`6.6 Packet frame structure
`
`41
`
`..........................
`
`7 .
`
`Service specification ..........................................................................................................................
`
`59
`
`7.1 Packet services .............................................................
`7.2 Convergence of services ............................................................................................................
`7.3 Management services ....................
`....................................................................................
`
`8 .
`
`Detailed specification of the medium access control (MAC) sublayer .............................................
`
`70
`82
`
`97
`
`Overview of the MAC sublayer ................................................................................................. 97
`8.1
`The ISLAN MAC protocol engine model .................................................................................
`97
`8.2
`8.3 P channel access control ..........................................................................................................
`102
`Timing relationship of TDM frames exchanged between the ISTE and the AU .....................
`131
`8.4
`
`9 .
`
`Detailed specification of the Physical (PHY) Layer ........................................................................
`
`133
`
`.................................................
`9.1 Overview
`9.2 HMUX sublayer ......................................
`9.3 PS sublayer ..............................................
`9.4 PMD sublayer for 4.096 Mb/s application ...............................................................................
`178
`9.5 PMD sublayer for higher rate (20.48 Mb/s) application ..........................................................
`190
`9.6 Connector ................................................................................................................................. 207
`9.7 Powering considerations .
`....................
`......
`
`133
`
`.......................
`
`...
`VI11
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 8
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`CHAPTER
`
`PAGE
`
`9.8 Medium cable characteristics-4.096 Mb/s PMD .................................................................... 210
`9.9 Medium cable characteristics-20.48 Mb/s PMD ....................................................................
`213
`ISLAN layer management ............................................................................................................... 215
`
`10 .
`
`10.1 Introduction ........................................................................................................................... 215
`10.2 Characteristics of the ISLAN interface relevant to management ..........................................
`215
`OS1 network management framework ................................................................................... 216
`10.3
`10.4 Relationship of IEEE 802.9 subnetwork management entities .............................................
`220
`10.5 ISDN network management information exchange ..............................................................
`222
`10.6 Management transport channels within the IEEE 802.9 interface ........................................
`223
`10.7 The structure of OS1 management information .....................................................................
`224
`10.8 OS1 management functional areas in the ISLAN environment .............................................
`230
`Inheritance hierarchy for ISLAN management .....................................................................
`231
`10.9
`10.10 The containment hierarchy for ISLAN management ............................................................
`235
`10.11 The OS1 registration hierarchy for 1q.T 4Y lver T - ~ s Y - P ~ +
`236
`10.12 The definition of the ISLAN systei . \I( 1
`238
`10.13 Definition of the ISLAN layer MO classes ...........................................................................
`239
`10.14 Management of the ISDN userhetwork interface in the ISLAN ..........................................
`251
`10.15 MIB tables ............................................................................................................................. 262
`11 . Signalling and ISDN I ~ ~ i \ ~ l i ~ ~ c ~ l l c ~ 1 t
`scopc ........................................................................................
`11.1 Introduction .............................................................................................................................. 271
`11.2 General overview of the service ..............................................................................................
`272
`11.3 Requirements for signalling support ........................................................................................
`273
`11.4 CCITT 4.93 1 architecture overview .......................................................................................
`275
`11.5 P channel call control procedures ............................................................................................
`283
`11.6 Interface between CCITT Q.93 I and the HMC .......................................................................
`286
`.............................................................
`11.7 Addressing .............................................................
`287
`.............................................................
`1 1.8 Configuration topologies .......................................
`287
`11.9 ISDN management functions ..................................................................................
`
`271
`
`291
`
`293
`
`295
`
`ANNEX
`Annex A (normative) Protocol implementation conformance statement (PICS) proforma ......................
`(normative) Managed object conformance statement (MOCS) ..................................................
`Annex B
`Annex C (normative) GDMO and ASN.l specification of management information ...............................
`Annex D (normative) Recommendations for signalling procedures .........................................................
`357
`(informative) Architecture of the access unit (AU) and guidelines for implementation ........... 377
`
`Annex E
`
`Annex F
`
`Annex G
`
`Annex H
`
`Annex I
`
`(informative) Sequence and description language (SDL) description of the information flow
`across layers ...............................................................................................................................
`(informative) Multimedia security control provision in IEEE 802.9 ISLAN ............................
`(informative) Address interworking across an IEEE 802.9 network .........................................
`(informative) Support of cell relay bearer service .....................................................................
`
`383
`
`399
`
`401
`
`421
`
`ix
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 9
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 10
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`IEEE Standards for Local and Metropolitan Area
`Networks: 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 standard is to
`
`- Develop an ISLAN interface at the medium access control (MAC) sublayer and the Physical (PHY)
`Layer compatible with IEEE 802.x' and ISDN standards and architectures
`- Develop an ISLAN interface that operates independently from the backbone network
`- Focus upon unshielded twisted-pair wiring as the prim
`- Enable implementation of IS terminal equipment (ISTE) that accesses IEEE 1802 LAN and ISDN
`services through a common interface
`
`The body of this 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.
`
`1
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 11
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`IEEE
`Std 802.9-1 994
`
`INTEGRATED SERVICES (IS) LOCAL AREA NETWORK (LAN) INTERFACE
`
`Specifies the PHY Layer functions over unshielded telephone twisted-pair (UTTP) cable
`-
`Specifies the characteristics of the UlTP 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 Isms 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 . 9 3 ~ 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 1-1 illustrates this notion of service hierarchy and shows the relationship of
`the two corresponding N Layer users.
`
`2
`
`Authorized licensed use limited to: Ian Crayford. Downloaded on June 16,2017 at 18:25:45 UTC from IEEE Xplore. Restrictions apply.
`
`Juniper Ex 1032 - 12
`Juniper v Chrimar
`IPR2016-01397
`
`

`

`AT THE MEDIUM ACCESS CONTROL (MAC) AND PHYSICAL (PHY) LAYERS
`
`IEEE
`Std 802.9-1994
`
`1
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`N LAYER 4
`
`N LAYER SERVICE PROVIDER
`
`Figure 1-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 1-1.
`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.
`
`a)
`
`b)
`
`c)
`
`d)
`
`Request primitive. This primitive is passed from the N+l Layer service user to the N Layer (or
`sublayer) to request that a service be initiated.
`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
`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
`user to convey the results of one or more associated previous service requests
`
`Figure 1-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 mor