SIST ETS 300 214 E1:2003
(Main)Network Aspects (NA); Metropolitan Area Network (MAN); Physical layer convergence procedure for 34,386 Mbit/s
Network Aspects (NA); Metropolitan Area Network (MAN); Physical layer convergence procedure for 34,386 Mbit/s
DE/NA-053027
Omrežni vidiki (NA) – Velemestno omrežje (MAN) – Konvergenčni postopek na fizični plasti za hitrost 34,368 Mbit/s
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Network Aspects (NA); Metropolitan Area Network (MAN); Physical layer convergence procedure for 34,386 Mbit/s35.110OmreževanjeNetworkingICS:Ta slovenski standard je istoveten z:ETS 300 214 Edition 1SIST ETS 300 214 E1:2003en01-december-2003SIST ETS 300 214 E1:2003SLOVENSKI
STANDARD
SIST ETS 300 214 E1:2003
EUROPEANETS 300 214TELECOMMUNICATIONDecember 1992STANDARDSource: ETSI TC-NAReference: DE/NA-053027ICS:33.040Key words:Network, access, MANNetwork Aspects (NA);Metropolitan Area Network (MAN)Physical layer convergence procedure for34,368 Mbit/sETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1992. All rights reserved.SIST ETS 300 214 E1:2003
Page 2ETS 300 214: December 1992Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 214 E1:2003
Page 3ETS 300 214: December 1992ContentsForeword.51Scope.72Normative references.73Definitions.74Symbols and abbreviations.75Physical Layer Convergence Procedure (PLCP) for(E31) based systems.85.1Introduction.85.1.1E3 relationship to the PLCP.85.2The PLCP frame format.95.3PLCP field definitions.95.3.1Framing octets (A1, A2).95.3.2Path overhead identifier (P0.P8).95.3.3PLCP path overhead octets.105.3.3.1PLCP path user channel (F1).105.3.3.2Bit interleaved parity - 8 (B1).105.3.3.3PLCP path status (G1).105.3.3.4DQDB layer management information octets (M1, M2).115.3.3.5Stuffing (octet C1).115.3.3.6Growth octets (Z1.Z3).125.3.4Trailer octets.125.4PLCP behaviour during faults.125.5PLCP behaviour during DQDB layer out of service.125.6PLCP framing.135.6.1Link status signal operations table.155.6.2Physical layer frame timing operations table.16History.17SIST ETS 300 214 E1:2003
Page 4ETS 300 214: December 1992Blank pageSIST ETS 300 214 E1:2003
Page 5ETS 300 214: December 1992ForewordThis European Telecommunication Standard (ETS) has been prepared by the Network Aspects (NA)Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS details the physical layer convergence procedure for an European Metropolitan Area Network(MAN) based on the Distributed Queue Dual Bus (DQDB) access method as defined in IEEE Standard802.6 [6] operating at a transmission rate of 34,368 Mbit/s in accordance with CCITT RecommendationG.751 [1].SIST ETS 300 214 E1:2003
Page 6ETS 300 214: December 1992Blank pageSIST ETS 300 214 E1:2003
Page 7ETS 300 214: December 19921ScopeThis European Telecommunication Standard (ETS) defines the physical layer convergence procedure at34,368 Mbit/s for use in the context of a subnetwork of a Metropolitan Area Network (MAN). Additional slotmappings for use in the transit network and use of methods defined in this ETS for other purposes areoutside the scope of this ETS.Methods of testing will be the subject of separate arrangements.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listed below.For dated references, subsequent amendments to, or revisions of any of these publications apply to thisETS only when incorporated in it by amendment or revision. For undated references the latest edition ofthe publication referred to applies.[1]CCITT Recommendation G.751 (1988): "Digital multiplexing equipmentsoperating at the third order bit rate of 34 368 kbit/s and the fourth order bit rateof 139 264 kbit/s and using positive justification".[2]CCITT Recommendation G.703 (1991): "Physical/electrical characteristics ofhierarchical digital interfaces".[3]CCITT Recommendation G.707 (1991): "Synchronous digital hierarchy bitrates".[4]CCITT Recommendation G.708 (1991): "Network node interface for thesynchronous digital hierarchy".[5]CCITT Recommendation G.709 (1991): "Synchronous multiplexing structure".[6]IEEE Standard 802.6 (1990): "Distributed Queue Dual Bus (DQDB) Subnetworkof a Metropolitan Area Network (MAN)".3DefinitionsFor the purposes of this ETS, the definitions as defined in IEEE Standard 802.6 [6] shall apply.4Symbols and abbreviationsFor the purposes of this ETS, the symbols and abbreviations as defined in IEEE Standard 802.6 [6] shallapply.SIST ETS 300 214 E1:2003
Page 8ETS 300 214: December 19925Physical Layer Convergence Procedure (PLCP) for(E31) based systems5.1IntroductionThis ETS provides a convergence procedure in which the Distributed Queue Dual Bus (DQDB) layer ismapped into a standard transmission system according to CCITT Recommendations G.751 [1] andG.703 [2] operating at 34,368 Mbit/s as used in public networks. Beyond the provisions of CCITTRecommendations G.751 [1] and G.703 [2], a 125 µs framing period shall be provided to supportn x 64 kbit/s channels based on octets.5.1.1E3 relationship to the PLCPThe rate, format, electrical characteristics and other attributes of the E3 signal shall be as defined inCCITT Recommendations G.751 [1] and G.703 [2]. The first 2 octets of each CCITT RecommendationG.751 [1] frame shall not be used for the PLCP. They are left for E3 synchronisation (i.e. frame alignment)and overhead bits compatible with existing equipment.NOTE 1:Only 12 bits of the first two octets are used for the synchronisation pattern, alarmindication to the remote end (A) and national use (N). The remaining 4 bits shall be setto (1100). Thus the two octets will be (1111010000 A N 1100). The "sliding" of the twooctets through the 125 µs frame shall be done via full octets.Thus the net bit rate available to the PLCP is 34,010 Mbit/s. The nominal frame rate is 22,375 kHz.NOTE 2:The PLCP shall provide sufficient buffering or other provisions to accommodate the"jump" resulting from the passing of the 2 unavailable octets.The 125 µs frame is not in any way aligned with the 44,6927 µs (22,375 kHz) frame of the transmissionsystem. The E3 payload slots are only octet aligned to the E3 overhead octets.
1)The designation E3 is used for a 34,368 Mbit/s transmission system according to CCITT Recommendation G.751 [1]. It is the3rd level of the plesiochronous digital hierarchy.SIST ETS 300 214 E1:2003
Page 9ETS 300 214: December 19925.2The PLCP frame formatA frame duration of 125 µs is chosen to easily accommodate n x 64 kbit/s channels based on octets.4 octets shall be added to each DQDB slot of 53 octets to provide framing and overhead functions so thateach row contains 57 octets. 9 of these rows are placed into one 125 µs frame. 18 to 20 octets (nominal)shall be left as a trailer depending on whether 2 or 3 E3 overhead double octets occurred during the 125µs frame. The complete frame structure is shown in figure 1. Each row of bits in the PLCP frame formatillustrated in figure 1 shall be transmitted in order, from left to right, top to bottom.111153 octetsA1A2P8Z3First DQDB SlotA1A2P7Z2DQDB SlotA1A2P6Z1DQDB SlotA1A2P5F1DQDB SlotA1A2P4B1DQDB SlotA1A2P3G1DQDB SlotA1A2P2M2DQDB SlotA1A2P1M1DQDB Slot18 to 20 octetsA1A2P0C1Last DQDB SlotTrailer125 msA1,A2:framing octets.P0.P8:path overhead identifier octet.C1:cycle stuff counter.M1,M2:DQDB layer management information octets.G1:PLCP path status.B1:Bit Interleaved Parity-8 (BIP-8).F1:PLCP path user channel.Z1.Z3:growth octets.Figure 1: PLCP frame format5.3PLCP field definitions(Refer to figure 1). The values of fields are described as bit patterns. The leftmost bit of each octet is themost significant.5.3.1Framing octets (A1, A2)The first two columns (A1, A2) may be used to provide slot delineation. The encoding of the A1 and A2octets is:A1A21111011000101000These codes are the same patterns as used in the Synchronous Digital Hierarchy (SDH) (CCITTRecommendations G.707 [3], G.708 [4] and G.709 [5]. Alternatively, slot delineation based on the HeaderCheck Sequence (HCS) of the DQDB header may be used.5.3.2Path overhead identifier (P0.P8)The third column identifies the PLCP overhead octets contained in the fourth column of figure 1. Theleftmost 6 bits of these octets provide numbering of the 9 rows. The 7th bit is reserved and the rightmostbit, Least Significant Bit (LSB), is a parity bit. The reserved bit shall be set to (0). The parity bit providesodd parity over this field.Table 1 defines the codes P0.P8, which shall be generated by the PLCP at each node. All other codesshall be invalid. A code shall also be considered invalid if the parity bit contained in the LSB is not correct.The response to invalid codes is described in subclause 5.6.SIST ETS 300 214 E1:2003
Page 10ETS 300 214: December 1992Table 1: Path overhead identifier codesP800100000P700011100P600011001P500010101P400010000P300001101P200001000P100000100P0000000015.3.3PLCP path overhead octetsThe PLCP path is defined between two adjacent peer PLCP entities. The F1, B1, G1 and C1 PLCP pathoverhead octets are related to PLCP operation and shall be terminated/generated at each PLCP on thesubnetwork. The M1 and M2 octets are provided for the transport of DQDB layer management informationoctets and shall not be processed by the PLCP sublayer.5.3.3.1PLCP path user channel (F1)The F1 octet is the user channel, which is allocated for user communication purposes between adjacentPLCPs. The use of this octet in DQDB subnetworks is for further study. The default code for this octetshall be (00000000).5.3.3.2Bit interleaved parity - 8 (B1)One octet is allocated for PLCP path error monitoring. This function shall be a Bit Interleaved Parity - 8(BIP-8) code using even parity. The PLCP path BIP-8 is calculated over the 9 x 54 octet structure(columns 4 to 57, 1 PLCP path overhead octet and 53 DQDB slot octets per row) of the previous PLCPframe and inserted into the B1 octet of the current PLCP frame.A BIP-8 is an 8 bit code in which the first bit represents even parity calculated over the first bit of eachoctet in the 9 x 54 octet structure, the second bit represents even parity over the second bit of each octetin the 9 x 54 octet structure, etc. Therefore the BIP-8 code provides for 8 separate even parity codescovering the corresponding bit of each octet in the 9 x 54 octet structure.5.3.3.3PLCP path status (G1)The G1 octet is allocated to convey the received PLCP status and performance back to the transmittingPLCP. This octet permits the status of the full duplex PLCP path to be monitored at either PLCP entity.The G1 octet shall consist of:-4 bits for the Far End Block Error (FEBE) code;-1 bit for the Alarm Signal (AS);-3 bits for a Link Status Signal (LSS).This is illustrated in figure 2.FEBE (4)AS (1)LSS (3)Figure 2: PLCP path status (G1)The first four bits of the G1 octet are the FEBE code which may be used to convey the count ofinterleaved-bit blocks that have been detected to be in error by the BIP-8 code in the preceding frame. Ifimplemented, this count shall have nine legal codes, namely zero (0000) to eight (1000) errors. If notimplemented, the code shall be (1111). The remaining six possible codes (1001 through 1110) wouldhave been the result of an error condition and shall be interpreted as zero errors.SIST ETS 300 214 E1:2003
Page 11ETS 300 214: December 1992The fifth bit may be used for the AS. The AS alerts the transmitting PLCP that a received failure indicationhas been decl
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.