ISOfIEC 8802-3 : 1993
`ISOIlEC 8802-3 : 1993
`ANSllIEE]<~ Std R02.3 . 1991 EditIon
`ANS IIlEEE S td R02 .3. 199::l Edi tIon
`
`U )(,AL AND lI l ETROPOLITAN AREA NETWORKS:
`LO/ 'ALAND tll ETROPOLITAN AREA NETWORK.S:
`
`OSI
`OSI
`REFERENCE
`REFERENCE
`MODEL
`MODEL
`LAYERS
`LAYERS
`
`APPLICATION
`APPLICATION
`
`PRESENTATION
`PRESENTATION
`
`SESSION
`SESSION
`
`TRANSPORT
`TRANSPORT
`
`NETWORK
`NETWORK
`
`DATA LINK
`DATA LINK
`
`PHYSICAL
`PHYSICAL
`
`LAN
`LAN
`CSMNCI)
`CSMNCD
`
`LAYERS LAYERS
`
`
`
`HIGHER LAYERS HIGHER LAYERS
`
`
`LLC LLC
`LOGICAL LINK CONTROL
`LOGICAL LINK CONTROL
`
`DTE
`
`DTE
`DTE
`(AUI not
`(AUI not
`exposed)
`exposed)
`
`-4------ AUI
`
`MOl
`
`I-
`
`I
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`
`I
`/
`
`I
`I
`
`I
`/
`
`It
`
`AUI
`AUI
`MAU
`MAU
`MDI
`MOl
`PMA
`PMA
`
`ATTACHMENT UNIT INTERFACE
`ATTACHMENT UNIT INTERFACE
`MEDIUM ATTACHMENT UNIT
`MEDIUM ATTACHMENT UNIT
`MEDIUM DEPENDENT INTERFACE
`MEDIUM DEPENDENT INTERFACE
`PHYSICAL MEDIUM ATTACHMENT
`PHYSI CAL MEDIUM ATTACHMENT
`
`Fig 1-1
`Fig 1-1
`LAN Standard Relationship to the ISO Open Systems Interconnection
`LAN Standard Relationship to the ISO Open Systems Interconnection
`(OSI) Reference Model
`(OSI) Reference Model
`
`The architectural model is based on a set of interfaces that may be different from those emphasized in
`The architectural model is based on a set of interfaces that may be different from those emphasized in
`implementations. One critical aspect of the design, however, shall be addressed largely in terms of the
`implementations. One critical aspect of the design, however, shall be addressed largely in terms of the
`implementation interfaces: compatibility.
`implementation interfaces: compatibility.
`
`1.1.2.2 Two important compatibility interfaces are defined within what is architecturally the Physical
`1.1.2.2 Two important compatibility interfaces are defined within what is architecturally the Physical
`Layer.
`Layer.
`
`
`0) Medium-Dependent Interface (MDI), To communicate in a compatible manner, all stations shall (1) Medium-Dependent Interface (MDI) . To communicate in a compatible manner, all stations shall
`adhere rigidly to the exact specification of physical media signals defined in Section 8 (and beyond)
`adhere rigidly to the exact specification of physical media signals defin ed in Section 8 (and beyond)
`in this standard, and to the procedures that define correct behavior of a station. The medium-inde(cid:173)
`in this standard, and to the procedures that define correct behavior of a station. The medium-inde(cid:173)
`pendent aspects of the LLC sublayer and the MAC sublayer should not be taken as detracting from
`pendent aspects of the LLC sub layer and the MAC sublayer should not be taken as detracting from
`this point; communication by way ofthe ISO 8802-3 [IEEE 802.3] Local Area Network requires com(cid:173)
`this point; communication by way ofthe ISO 8802-3 [IEEE 802.3] Local Area Network requires com(cid:173)
`plete compatibility at the Physical Medium interface (that is, the coaxial cable interface).
`plete compatibility at the Physical Medium interface (that is, the coaxial cable interface).
`(2) Attachment Unit Interface (AUI), It is anticipated that most DTEs will be located some distance
`(2) Attachment Unit Interface (AUI), It is anticipated that most DTEs will be located some distance
`from their connection to the coaxial cable. A small amount of circuitry will exist in the Medium
`from their connection to the coaxial cable. A small amount of circuitry will exist in the Medium
`Attachment Unit (MAU) directly adjacent to the coaxial cable, while the majority of the hardware
`Attachment Unit (MAU) directly adjacent to the coaxial cable, while the majority of the hardware
`and all of the software will be placed within the DTE. The AUI is defined as a second compatibility
`and all of the software will be placed within the DTE. The AUI is defin ed as a second compatibility
`interface. While conformance with this interface is not strictly necessary to ensure communication,
`interface. While conformance with this interface is not strictly necessa ry to ensure communication,
`it is highly recommended, since it allows maximum flexibility in intermixing MAUs and DTEs. The
`it is highly r ecommended , since it allows maximum flexibility in intermixing MAUs and DTEs . The
`AUI may be optional or not specified for some implementations of this standard that are expected to
`AUI may be optional or not specified for some implementations of this standard that are expected to
`be connected directly to the medium and so do not use a separate MAU or its interconnecting AUI
`be connected directly to the medium and so do not use a separate MAU or its interconnecting AUI
`cable. The PLS and PMA are then part of a single unit, and no explicit AUI specification is required .
`cable. The PLS and PMA are then part of a single unit, and no explicit AUI specification is required .
`
`1.1.3 Layer Interfaces. In the architectural model used here, the layers interact by way of well defined
`1.1.3 Layer Interfaces. In the architectural model used here, the layers interact by way of well defined
`interfaces, providing services as specified in Sections 2 and 6. In general, the interface requirements are as
`interfaces, providing services as specified in Sections 2 and 6. In general, the interface requirements are as
`follows.
`follows.
`
`32
`32
`
`AMX
`Exhibit 1026-00035
`
`

`
`
`
`--
`
`ISG'IEC 88OIl-3: l~S
`ISQIIEC 1180IHI: lilfl!
`
`ANSJIIEFX SId !lO2.3, UI\I~ Editiom ANSln£El: SId !lO2.3, 19~3 Editioa
`
`(ll The interface between the MAC suhlayer aod the LLC sublayer includes facilitie. for trarumtitting
`(ll The interface between the MAC I!Ublayer and the LLC sublllYer includes focilitie. for trllllJllI\itting
`
`and receiving fram .... and pnwides per-operation statu. information for use by lrigher.layer error and recoiving frames, and p"""ides per-operation statull intonnation for use by lrigher.layer error
`
`recovery procedures. recovery procedures.
`(2) The interface between the MAC .ublayer and the Physical Layer includos .ignals for framing (car(cid:173)
`(2) The interface between the MAC lublaY"l" omd tho PhyEicai LRY"r includ ..... ignals for framing (cal'(cid:173)
`
`rier 8ell8e, traJ1llmit initiation) lind wntention resolution (colli.ion detect), facilities for p"osing a rier !Iell8e, trlll1l!mit initiation) lind oontention resolution (colli.ion detect), fac:ilitlea for PIlosing II
`pair ofsenal bit stream. (tranamit, receive) between the two layer!!, and II wait function for timing.
`pair of serial bit streams (transmit, receive) between the two layers, and a wait function for timing.
`
`'These interface. are described more preci&eiy in '.3. Additional interface" are necesaaryto allow higher
`'These interface! are des<:ribed more preci&eiy in 4.3. Additional interfaces are necessary to allow higher
`level network management facilities to interact with th""" layers to perform operation, maintenance, and
`level network management facilities to interact with these Iayera to perform operation, maintenance, and
`plannjng functiona. Network management function. will be di..CU8Sed in Section:l.
`planning functions. Network ID!lIlogement function" will be di,o,CWlsOO. in Section 5.
`
`1.1." Application Area6. 'll>e applieatiollll envirmunent for the Local Area Network;~ intended to be 1.1." Application Areaa. 'I1>e applieatiollil environment for the Local Are" Network;8 intended to be
`commercial and light indUHtrial. Use ofCSMAlCD LAN. in home or heavy indw;triai environments, while
`commercial and light ind\lJltrial. Use ofCSMAlCD LAN. in home or heavy industrial environments, while
`
`not precluded, is not CO!l.'Iidered within the scope of thi& stirndard. not precluded, is not roru:idered within the scope of thi& .tlllldard.
`
`
`
`1.2 Notation 1.2 Notation
`
`
`1.2.1 State Di"¥l"Am Conv .... tion&. The operation or.. protocol can hede/lcribed by subd'viding the pro(cid:173)1.2.1 State Diagram Conventions. The operation oca protocol can bedescribed by subdividing tho: pro(cid:173)
`
`tocol into a number of interrelated functioDII. The operation of th" functions can be d"""rlbed by ..tate dia· tocolinw a number of interrelated functiona. The operation ofllie function.'l can be d"""ribed by state dia·
`
`graltl.'!. Each diagram represents the domain of a function and consists of a group or connected, mutually grams. Each diagram ...,presents the domain of ... function and coMiata of a group of connected, mutually
`
`exclwrive .tates. Only one lltate ofa function '" active at any given time (see Fig 1·2). exclusive .tates. Only one..tate ofa function ... llCtive at any given time (see Fig 1·2).
`
`TERMS TO ENTER
`TEAMS TO ENTER
`STATE
`STATE
`
`STATE NAME
`STATE NAME
`
`<MESSAGE SENT~
`<MESSAGE SENT~
`
`< .. ~ [CONDITION)
`< .. ~ (CON~T1ON)
`
`[ACTIONS T .&.KEN]
`(ACTIONS TAKEN]
`
`TERMS TO EXIT
`TEAMS TO EXIT
`STATE
`STATE
`
`
`Fig 1·2 Fig 1·2
`
`State Diagram Notation Example State Dlagrun Notation Example
`
`Each .tate that the function can assume is representOO by a rectangle. These an: divided into two paI"t$
`Each .tate that the function can assume is represented by a rectAngle. Theae an: divided into two parU
`
`by a horiwnta!line. In the upper part the state is identified by a name in capitallettet'l'l. The lower part by a horiwntalline. In the upper part the atate i.o identified by a name in capitallette!"8. The lower part
`contain.'! the name of any ON sign,.] that i.o generated by the function. Action! are described by .hort
`contairu! the nam" of any ON mana! that i.o generated by the function. Action. Me deacribed by ahort
`phrMell and enclD8ed in bracket..
`phrMell and endOlled in braclr.eta.
`All permiSiiible transitions between the state8 of a function are represented graphically by arroWS All permissible transitions bt:tween the .tates of a function aro represented graphically by arroWll
`
`hetw""n them. A tranllition that ,s global in nature (for example, an exit condition from all atate8 to the
`betW"'-'1l them. A tranoition that i. global in nature (ror example, an exit condition from o.ll state>! to the
`
`IDLE or RESET state) i.o indicated by an open arrow. Label. on tran.itioll8 Me qulililier. that mUllt be ful· IDLE or RESET state) i.o indicated by an open arrow. Label. on transition.o are qualifierl that mUl!t be ful·
`
`filled before the uan.ition will be taken. The label UeT demgnate!! an unconditional tranllition. Qualifiers filled before the tran.ition will be taken. 'The label UCT demgnateo an unconditional tranllition. Qualifiers
`
`d .... cribed by mort PMa",," "'" encl .... ed in parenti>ellell. de8cribed by mort phrases....., encl""ed in parenihelleO.
`
`State transition. and 8ending and receiving ofm",,""11"" occur instantaneously. When 8 state i.o entered State tran..itiona and .ending and rec:civing ofmOO81lgeB occur inotantanoously. When. 3tate i.o entered
`and the oondition to leave that .tate i8 not immediately fulfilled, the !tate execute.. continuously, sending
`and the condition to leave that atate i. not immediately fulfilled, th ... tate ""erute" continuously, ""nding
`
`the meosagcs and executing the "ctiona contained in the .tate in a continuous man.ner. the m""sagcs and executing the acti.orus contained in the .tate in a continuous manner.
`
`AMX
`Exhibit 1026-00036
`
`

`
`
`
`- - - - - - - - - - - - - - - - - - - - - -- - - --- - - - - - -
`
`I8O'II:C S802-3 : 19\13
`TSO'II:C 811(12-3 : 1993
`ANSlIIEEE SId 802.3, 1993 IMiIlon
`ANSlIIEEE SId 1102.3, 1993 IMJIlon
`
`LOCALAlID METROPOLl'l'A!1/ ARF.A NETWOR/Ol:
`
`Some devicetl described in thie standard (e.g., repeaters) arc allowed to have two or more ports. State
`Some device8 de&uibed in this standard (e.g., repeaters) arc .. Hawed to have two or more porlII. StAte
`diagrams capable of describing the operation of dcviOl!ll with an unspecified numher uf paN, roquired qual(cid:173)
`diagrlll1Ul capable of deacribing tho op ...... tion of dcviOl!ll with an u.nHpecified number uf pori>!, roquired. qual(cid:173)
`ifier notation that allows testing ror ronditions at multiple porb. The notation u..oo ill a tenn that includ!l6
`mer notation that allow~ testing for ronditions at multiple pm1>I. The notation uoed is a term that includes
`a del!cription in pllrenthfl'l811 ofwhich porta muot meet the term for the qualifier to be sat.is1ied (e.g., ANY
`a d .... criptiou in paronth_ ofwhich porta muot meet the term for the qualifier to be pt.isJied (e.g., ANY
`and ALL). It is also ne<:ea8lU')'to provide for term-&llsWunent Itatementll that ..... ign a name to a plrl that
`and ALL). It is also necellsaryto provide fur term-aa"igrunent statement.. that "".ign a name to II port that
`6atiafiea a qualifier. The following COl\Vantion is used to deIIcribe a tenn_lllIILignwent statement that i8 aSIlO(cid:173)
`satiafi"" a qualifier. The following convention ill used to deIIcribe a term-WIIlignment atatement that is aSSO(cid:173)
`ciated with a transitiou:
`ciated with a transition:
`
`(1) The character"'" (colon) is" delimiter u!!ed to denote that ... term a&lignrnent statement follow •.
`(1) The character"" (colon) is a delimiter u ... d to denote that a term asoignmeut atAtement follow8.
`(2) The character"<;:? (lett 1IrT<IW) denotes WlBignm .... t .. fthe valu .. following the arrow to the term pre·
`(2) The character"=- (left arrow) denote.. R8Bignmant of tile value following the arrow to the term. pre(cid:173)
`ceding the arrow.
`ceding the arrow.
`The state diagrama contain the II.nthoritative statement of the funmo"" they depict; when appareut ""n(cid:173)
`The state diagram" contain the authoritative statement oftha functiOIU! they depict; when apparent 000-
`ftict~ between descriptive text and state diagram. ari&o, the "tate diagram. are to take precedence. Thio
`Bjets between descriptive tert and.tate diagrams ari8e, the state diagrams AnI to take precedence. Thi.o
`does not override, however, any explicit deacnption in the ten that has no parallel in the state diagr8IIIII.
`does not override, however, any eIplicit de.cnptioo in the text that haa no parallel in the state diagr8Illil.
`The model. presented by atate diagrams an. intended 011 the primary specifications of the functions to be
`The model~ pre""nted by ~tota diagrams are intended as the primary specifications of the functions to be
`provided, It is important to distinguish, Imwever, between a model and a real implementation. The models
`provided. It i~ important to disti~ish, however, between a model RIU! a real implementation. The models
`are optimu,ed for simplicity and clarity of presenbition, while any realiatic implemeutation may place
`are optimized for simplicity RIU! clarity of PrellllIltation, while any realiatic implementation may place
`buavier emphasis on efficiency and suitahility to II. partirullU' implementation technology. It i. the fune(cid:173)
`heavier emphasi~ on efficiency lUId Buitability to a partirular implementation technology. It i8 the func(cid:173)
`tional behavior of any unit that must match the standard, not it. intemalstrueture. The internal details of
`tional behavior of any unit that must match the standard, not itll internalatructun. The internal details of
`the model are ulleful only to the eItent that they ~pecify the erlornal behavior clearly and preciaely.
`the model are useful only to the eJ:tent that they specify the external behavior clearly and precil!ely.
`
`
`1.2.2 Service Specification Method and Notation. The ""rvice of a layer or 6ublayer is the set of 1..2..2 Service Specification Method and Notation. The llervk:e of a layer or B\lblayer is the set of
`capabilities that it offe ... to a noer in the next higher (sub)i.ayer. Abotrad BOrn""" are specified here by
`Cll.pabiliti~ that it offers to a Uller in the nm:t higher (sub)Layer. Abstract BCrvi""" are specified here by
`deacribing the service primitives IUld paramet..1lI that characteriOle each ...mce. This definition or ""mce
`describing the servi"" primitives Ilnd parameters that characterio:& each service. This definition or service
`ill indeJlOndent of any particular implementation(see Fig 1-3).
`is independent of any partkular implementation(see F1g 1-3).
`
`LAYER N
`lAYER N
`
`6E~USER ~U6ER
`
`
`
`, ,
`
`FlEClI.EST
`
`LAYER N
`~~,
`
`
`
`, ,
`
`
`Fig 1-3 Fig 1-3
`Servie" Primitive Notation
`Servic,", Primitive Notation
`
`Specifie implementlltiona may II.iHO include provisiona for interface interactions that have no direct end(cid:173)
`Specific implementations may also include proviaioNi for interface interactions that have no direct end(cid:173)
`to-end effects. Eumples ohuch local interactions include interface flow control, status requests and indi(cid:173)
`to..,nd effects. Examples of such local interactions include interface flow control, status requ....t8 and ind.i(cid:173)
`Clltions, error notifications, and layer management, Specific implementation dct.ai.ls are omitted from this
`cation., error notifications, lUId layer management. Specific implementation details Il1"e omitted from this
`!!emce specification both l;oeoaWM! they will differ from implementation to implementation lUId beC8lU1e
`1Iervi"" .pccification both I.>ecauae they will differ from implementation to implementation and becalUle
`thtIy do not impact the peer-to-pee.- pl"Otocoll.
`they do not impact the peeT-to-peer protooola.
`
`
`
`1.2.2.1 Classification of Serrio,", Primitives. Primitivea are of two generic types: 1.2..2,1 Classiflclltlon of Servie" Primitive~. Primitiv .... are of two generic types:
`
`(1) REQUEST. The request primitive iii p""oed from lsyer N to layer N-J to reqU!!llt that a service be
`(1) REQUEST. The request primitive is plllllWld from layer N to layer N-I to request that a service be
`initiated.
`initiated.
`
`AMX
`Exhibit 1026-00037
`
`

`
`
`
`--
`
`ISQ'I]!C S8(r.l.~ , l!lliS
`ISQ'IEC 680'.01·3 , l!l!lS
`ANSIIlEEl': Sid SOU , l!l!lS Edition
`ANSIIlEtl!: Sid 8()U, l!l!lS Edi .....
`
`
`
`(2 ) (2)
`
`INDICATION. The indication primitive i8 pa...oo ftmn layer N-! to lllYer N to indicate an internal
`INDICATION. The indication primitive i8 paased from layer N-! to lIlY"'" N to indicate an internal
`lllYl!I" N-l event that i" significant to lay .... N. Thi. event may be logically related to a remote servioe
`layer N-l event that is significant to lay.,.. N. 'Ibis event may be logically related to a remote service
`request, or m .. y be cau.ed by an event internal to layer N_l.
`request, or m .. y be cau. ed by an event internal to layer N_I.
`
`The service primitives are an abstraction of the functional specification and the user-h.yer interaction.
`The "erviee primitives are an abstraction of the functional specification and the uoer-iayer interaction.
`The abstract definition doe. not contain 10<:8l detail of the \ll!eu'providcr interaction. For instance, it doe.
`The abstract definition doe. not contain 10<:8l detail ofthc user{providcr interaction. For instance, it does
`not indicate the local me<:han;gm that allows a moer to indicate that it is awaiting an incoming ClIlI. Each
`not indicate the local mechanism that allows a uaer to indicate that it is awaiting an incoming <:lilt Each
`primitive hR" "oet of.ero or more parameter., repuoonting data element. that ohall be passed to qUalifY
`primitive has a oet of zero or more parameter., repre""nting data elementll that ohall be passed to qUalifY
`the functiOIUl invoked by the primitive. Parameter. indlm.te infonnation available in a userlprovid .. r inter(cid:173)
`the functlOIll! invoked by the primitive. Parameter. indicate information available in a userlprovider inter(cid:173)
`action; in any particular interface, some parRmctCl'!! may he explicitly stated (even though not explicitly
`action; in any particular interface, """"c paramctcl'!! may he explicitly stated (even though not explicitly
`
`defined in the primitive) or implicitly a-.riated with the oervice ac""". point. Similarly, in any p!l1'ticular defined in the primitive) or implicitly a-.riated with the oervice acce!I" point. Similarly, in any p!ll'ticular
`protoroi8pecific8tion, function. corresponding to s service primitive msy be eIpliciUy defined or implicitly
`protoroi8pecification, function. corresponding to a service primitive may be eIpliciUy defined or implicitly
`
`svailable. available.
`
`
`1.2.3 Physical Layer and Media Notation. Uoers oftbi" standard need to reference which partirulsr 1.2.3 Phyllicai Layer IlDd Media Notation. Uoe", ofthi" standard need to reference which particular
`implementation i. being used or identified. Therefore, a means ofidentifying each implementation is given implementation i. being used or identified. Therefore, a mean. ofidentifying each implementation is given
`
`by a simple, ihroo-field, type notation that is explicitly stated at the heginninll of each relevant .ed:ion. In
`by a simple, three--field, type notation that is eIplicitly stated at the beginning of each relevant .ed:ion. In
`
`general, the Physical Layer type is sp"cified by th""" fields: general, the Phyaical Layer type is specified by th~ fields:
`
`
`
`<data r ate in MhI.> <medium type> <maximum segment length (x 100 m)> <data rate in Mbls> <medium type> <maximum segment length (x 100 m)>
`
`For example, the standard contains a 10 Mbls baseband ~eci:fication identified "" "TYPE 10EAS&;,"
`For example, the standard contains a 10 Mhls baseband ~eci:!ication identified as "TYPE lOBASE~,"
`meaning a 10 Mh's baseband medium whose maximum segment length u. ~oo m. Each sU<:cel!sive Physical
`meaning a 10 Mh'. baseband medium whose maximum segment length i.'! 500 m. Each .utcellsive Physical
`Layer .pecification willstatc its own unique TYPE identifier aloog similar line.!.
`Layer . pecification willstatc its own unique TYPE identifier all)l1.g ~imilar !inc.!.
`
`1.2.4 Physic..! Layer Message Notation. Messages generated within the Physical Layer, either
`1.2.4 Physic..! Layer Message Notation. Messages generated within the Physical Layer, either
`within or between PIS and the MAU (that u., PMAcircuitry), are designated by an italic type to designate
`within or between PIS and the MAU (that i.'!, PMAcirroitry), are designated by an italic type to d .... ignate
`
`either fonn of phyaical Or logical me.sage u.ed to execute tM physical layer signaling process (for example, either fonn of phyaical Or logical me""stle u"ed to execute the physical layer signaling proc"". (for example,
`
`inpuCidle or mauJJlXlilable). inpuCidle 01" mau-'J!Xjilabl~).
`
`
`
`1.3 Reference" 1.3 References
`
`
`[l] CISPR Publication 22 (19B~), Limits and Methods of Measurement of Radio Interference Charactcris(cid:173)[I] CISPR Publication 22 (1985), limit!; and Meth0d.5 of Measurement of Radio Interference Characteris(cid:173)
`
`ti"" ofInformation Technology Equipment.2 tic.! ofInformation Technology Equipment. 2
`
`
`
`[2J [2)
`
`
`
`IEC Publication 96-1, Radio-freque1l<-"y cables, Part 1: General requirement. and measuring methods.3 IEC Publication 96-1, Radio-frequelll-"y cables. Part 1: General requirement. and measuring methods.3
`
`IEC Publication 96-lA, 1st Supplement to Radio-frequ=~"y cables, Part 1: Appendix S",,\ion 5.4, Ter(cid:173)
`IEC Publication 96-lA, 13t Supplement to Radio-freq\JCll~"y cables, Pari 1: Appendix Section 5.4, Ter(cid:173)
`
`[3J [3)
`minated tri!iIiol test method for tramfer impedance up to 100 MH •.
`minated tri!lIiai test method for tramfer impedance up to 100 MH •.
`
`lEC Publication 169-8 and -16, Radio-frequency connectol"3, Part 8: Radio-frequency coaxial connoo(cid:173)
`IEC Publication 169-8 aruI-16, Radio-frequency connector.>, Part 8: Radio-freqnency coaxial conn",,"
`
`[4J [4)
`ton; with inner diameter of ""ter conduttor 6.5 mm (0.256 in) with bayonet loc"k.-Characieristic imped(cid:173)
`ton; with inner diameter of ooter conductor 6.5 mm (0.256 in) with bayonet loe"k.-Characteristic imped(cid:173)
`ance W ohm. (Type BNe); Part 16: Radio-frequency corns} connector"!! with inner diameter of outer
`ance Ml ohms (Type BNe); Part 16: Radio-frequency coaris} connector!! with inner diameter of outer
`""nduetor 7 mm (0.276 in) with..".ew coupling-Charactermtic impedance W ohm. (75 ohma) (Type N).
`conduetor 7 mm (0.276 in) with screw coupling-Characteristic impedance Ml ohm. (7~ ohms) (Type N).
`
`[5]
`[51
`
`IEC Publication 380, Safety ofeledrically energi.ed office machines.
`IEC Publication 380, Safety of electrically ene~gized office machines.
`
`
`
`[61 [6]
`
`
`
`IEC Publication 01.35, Safety of data processing equipment. IEC Publication 01.36, Safety ofdataproceSSIing equipment.
`
`'cISPR doou"",nto a~ a~.ilable from the lnterlnt;oo,;,l Elooi:,oto<hn"",l Com_ lion, 3 ,LIe d. V..,.lnbO. c.... P_le 131, CH
`'cISPR OOou"",nto a~ a~.ilable from thelnterlnti<JrLo.l Elod;,otooh.o.""] Co"""i<sion, 3 " .. d. Vu.""bO. C .... P_le la1, CH
`1211, 0.,....., 20, Switzerl.ndISIri_ . CISPRd"""m ..... a~.leo ... ilable;n \he Un;W>d St. t.. ""'" the s..lo. Dep&rt.me.n~ Aaorloon
`all, Gel>l>w> 20, Switu>rl.ndISui_. CISPRd"""m ..... a~.1eo .. oil.bIe;u Ihe UnH;"" Stoteo from the &10. Dep6rt.me.n~ AmcrloOD.
`Noto"-"'ll St.ndonlo lnotilulo, 11 W.,.t 42nd Stroe~ 13th Floc<. N.",Y",k. NY 1110116. USA.
`N otiM>ll Stondardo I",.;<ow , 11 W.,.t 42nd Str""~ 13th 1'100<. N. ",Yo<lt. NY 10036. USA.
`' r!;c publk~tion. aN availoblo !rum IEC SA.,. .o.,P",;;..,nI;, c.... Po.tale 131, 3 ""'" "" V.rembO, CE_12U, Gcnlov. 20. s..i .... '·
`'rl';C publk>.tion. aN available {rum IEC &Ie. n.,P"~"",nI;, CoM _ale 131, 3"..., d< Vol"UlbO, CE_12U, acnlov. 20. g.",l .... r·
`~. IEC pool'oooron. ore aloo onilable in the U.oitod SUIoo It"", !boo _ ~nI, Am ... ican N.Iion.1 St.nd.ud. lnoti(cid:173)
`~w.-. lEC pOOI;"'tio ... ore aJoo ovoilable '" the U.oitod Stat.. It"", tho &100 Uopart&ttonl, Am ... ;..." Nalion.l St.nd.rnl. looti(cid:173)
`"'to, 11 W .. I 4~J>d Streo~ 13th Floor. N . .. YO£k. NY 10036. USA.
`"'to, 11 W .. I 4~oo Streo~ 13th !I"Ioor. N ... York. NY 10006. USA.
`
`AMX
`Exhibit 1026-00038
`
`

`
`ISOIIEC 8802-3 : 1993
`ISOIIEC 8802-3 : 1993
`ANSIIIEEE Std 802.3. 1993 Edition
`ANSIIIEEE Std 802.3. 1993 Edition
`
`LOCAL ANn MF.'T'ROPnT.T'T'AN ARF.A. NF.'T'WORKS:
`LOr,AL ANn MF.'T'ROPnT .T'T'A N A RF.A. NF.'T'WORKS:
`
`IEC Publication 807-2, Rectangular connectors for frequencies below
`[7]
`IEC Publication 807-2, Rectangular connectors for frequencies below
`[7]
`3 MHz, Part 2: Detail specification for a range of connectors with round contacts-Fixed solder contact
`3 MHz, Part 2: Detail specification for a range of connectors with round contacts-Fixed solder contact
`types.
`types.
`
`IEC Publication 950, Safety of Information Technology Equipment, Including Electrical Business
`[8]
`IEC Publication 950, Safety of Information Technology Equipment, Including Electrical Business
`[8]
`Equipment.
`Equipment.
`
`[9]
`[9]
`
`
`
`ISO 2382-9 : 1984, Data processing-Vocabulary-Part 09: Data communication. 4 ISO 2382-9 : 1984, Data processing-Vocabulary-Part 09: Data communication. 4
`
`ISO 7498 : 1984, Information processing systems-open systems interconnection-Basic reference
`[10]
`ISO 7498 : 1984, Information processing systems-open systems interconnection-Basic reference
`[10]
`model.
`model.
`
`[11] IEC Publication 60, High-voltage test techniques.
`[11] IEC Publication 60, High-voltage test techniques.
`
`[12] IEC Publication 68, Environmental testing.
`[12] IEC Publication 68, Environmental testing.
`
`[13] IEC Publication 793-1, Optical fibres, Part 1: Generic specification.
`[13] IEC Publication 793-1, Optical fibres, Part 1: Generic specification.
`
`[14] IEC Publication 793-2, Optical fibres, Part 2: Product specifications. 5
`[14] IEC Publication 793-2, Optical fibres, Part 2: Product specifications. 5
`
`[15] IEC Publication 794-1, Optical fibre cables, Part 1: Generic specification.
`[15] IEC Publication 794-1, Optical fibre cables, Part 1: Generic specification.
`
`[16] IEC Publication 794-2, Optical fibres cables, Part 2: Product specifications.
`[16] IEC Publication 794-2, Optical fibres cables, Part 2: Product specifications.
`
`[17] IEC Publication 825, Radiation safety of laser products, equipment classification, requirements, and
`[17) IEC Publication 825, Radiation safety of laser products, equipment classification, requirements, and
`user's guide.
`user's guide.
`
`[18] IEC Publication 874-1, Connectors for optical fibres and cables, Part 1: Generic specification.
`[18] IEC Publication 874-1, Connectors for optical fibres and cables, Part 1: Generic specification.
`
`[19] IEC Publication 874-2, Connectors for optical fibres and cables, Part 2: Sectional specification for fibre
`[19) IEC Publication 874-2, Connectors for optical fibres and cables, Part 2: Sectional specification for fibre
`optic connector type F -SMA.
`optic connector type F -SMA.
`
`[20] ISOIIEC 7498-4: 1989, Information processing systems-Open Systems Interconnection-Basic Ref(cid:173)
`[20) !SOIlEC 7498-4: 1989, Information processing systems-Open Systems Interconnection-Basic Ref(cid:173)
`erence Model-Part 4: Management Framework.
`erence Model-Part 4: Management Framework.
`
`[21] ISO 8877 : 1987, Information processing systems-Interface connector and contact assignments for
`[21] ISO 8877 : 1987, Information processing systems-Interface connector and contact assignments for
`ISDN basic access interface located at reference points Sand T.
`ISDN basic access interface located at reference points Sand T.
`
`Local and national standards such as those supported by ANSI, EIA, IEEE; MIL, NFPA, and UL are not
`Local and national standards such as those supported by ANSI, EIA, IEEE, MIL, NFPA, and UL are not
`a formal part of the ISOIIEC 8802-3 standard. Reference to such local or national standards may be useful
`a formal part of the ISOIlEC 8802-3 standard. Reference to such local or national standards may be useful
`resource material and are identified by a bracketed number beginning with the letter A and located in
`resource material and are identified by a bracketed number beginning with the letter A and located in
`AnnexA.
`AnnexA.
`
`1.4 Definitions. The definitions used in this standard are consistent with ISO 2382-9:1984 [9). A more
`1.4 Definitions. The definitions used in this standard are consistent with ISO 2382-9:1984 [9]. A more
`specific Part 25, pertaining to LAN systems, is in development.
`specific Part 25, pertaining to LAN systems, is in development.
`
`41S0 publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varembe, CH-1211, Geneve 20, Switzer(cid:173)
`41S0 publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varembe, CH-1211, Geneve 20, Switzer(cid:173)
`land/Suisse. ISO publications are also available in the United States from the Sales Department, American National Standards Insti(cid:173)
`land/Suisse. ISO publications are also available in the United States from the Sales Department, American National Standards Insti(cid:173)
`
`tute, 11 West 42nd Street, 13th Floor, New York, NY 10036, USA. tute, 11 West 42nd Street, 13th Floor, New York, NY 10036, USA.
`
`5 Subsection 9.9 is to be read with the understanding that the following changes to IEC Publication 793-2 [14J have been requested: 5 Subsection 9.9 is to be read with the understanding that the following changes to IEC Publication 793-2 [14J have been requested:
`(1) Correction of the numerical aperture tolerance in Table III to ± 0.015.
`(1) Correction of the numerical aperture tolerance in Table III to ± 0.015.
`(2) Addition of another bandwidth category, of 2! 150 MHz referred to 1 km, for the type Alb fiber in Table III.
`(2) Addition of another bandwidth category, of~ 150 MHz referred to 1 km, for the type Alb fiber in Table III.
`
`36
`36
`
`AMX
`Exhibit 1026-00039
`
`

`
`
`
`• •
`
`
`
`CSMMD CSMMD
`
`TSOIIl':C 1180:6-3 : 19!1.l
`TSOIIEe Si!02-3 : llll/a
`A..'>SlIIEEE Std B02.3, 1993 Edition
`A..'iSlIIEEE Std !!O2.3, 1993 Edition
`
`
`
`2. I\-IAC Service Specification 2.l\IAC Service Specification
`
`2.1 Scope IlIld Field of AppliclI.tion. Thi" flection specifie. the .ervi""" provided by the Media Acoe.s
`2.1 Scope IlIld Field of AppliCll.tion. This ""dion specifie. the oern""" provided by the Media Acoe ••
`COIItrol (MAC) Hublayer to the Logioal Link Control (LLe) Hublayer forthe ISO (IEEE] LocalArea Network Control (MAC) Hublayer to the Logioal Link Control (LLe) . ublayer forthe ISO (IEEE] LocalArea Network
`
`
`mandard (. ee Fig 2-1). The servioes are described in an abstract way and do not imply any particul!l1" mandard (see Fig 2-1). The service" are de!lCribed in lin abstract way and do not imply any particular
`implementation, or any e:<posed interface. There is not necessarily a one-t<>-one cOiITe!!pondence between
`implementation, or any e:<