Table of Contents
1Scope
2References
2.1Normativereferences
2.1.1IdenticalRecommendations/InternationalStandards
2.1.2Othernormativereferences
2.2Informativereferences
3Definitions
4Abbreviations
5TheprotocolframeworkofIPoverSDHusingLAPS
6Physicallayeranditsprimitives
7Servicefacilitiesandprotocolspecificationsofdatalink
7.1UITSanditsspecification
AnnexA-TheLAPSspecification
A.1General
A.2Framestructureforpeer-to-peercommunication
A.2.1General
A.2.2Flagsequence
A.2.3Addressfield
A.2.4ControlandSAPIfield
A.2.5Informationfield
A.2.6Transparency
A.2.7FrameCheckSequence(FCS)field
A.2.8Formatconvention
A.2.9Invalidframes
A.3Elementsofproceduresandformatsoffieldsfor
datalinklayer
A.3.1General
A.3.2AddressfieldanddatalinkSAPI
A.3.3Serviceaccesspointidentifier(SAPI)
A.4Definitionofthepeer-to-peerproceduresofthe
datalinklayer
A.4.1Transmissionofunacknowledgedinformation
A.4.2Receiptofunacknowledgedinformation
A.4.3ProcedureontheConnectionmanagemententity
AnnexB-PrimitivesbetweenLayer3orotherupper
protocolsandlinklayer,Layer1andlinklayer
B.1General
B.2Layer3orotherupperprotocolentity-Datalink
layerprimitives
B.3Layer1-Datalinklayerprimitives
B.3.1PH-DATA
B.4Theconnectionmanagemententity-Datalinklayer
primitive
B.4.1MDL-ERROR
B.5Parameterdefinition
B.6Primitiverelationshipdescription
AnnexC-Theself-synchronousscrambling/descrambling
(x[43]+1)functiondescription
C.1Theself-synchronous(x[43]+1)scrambler/descrambler
AppendixI-ThemaindifferencesbetweenLAPSandPPP/HDLC Abstract
Provides a simple HDLC specification named LAPS to adapt IP directly to SDH. The Service Access Point Identifier (SAPI) is introduced to encapsulate IPv4, IPv6, PPP and other upper layer protocols.