1、 IEEE Standard for Local and metropolitan area networks Time-Sensitive Networking for Fronthaul Sponsored by the LAN/MAN Standards Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Society IEEE Std 802.1CM-2018 IEEE Std 802.1CM-2018IEEE Standard for Local and metropolitan area n
2、etworksTime-Sensitive Networking for FronthaulSponsorLAN/MAN Standards Committeeof theIEEE Computer SocietyApproved 7 May 2018IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2018 by The Institute of Electrical and
3、 Electronics Engineers, Inc.All rights reserved. Published 8 June 2018. Printed in the United States of America.IEEE and 802 are registered trademarks in the U.S. Patent fitnessfor a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness ofmaterial. In
4、addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort.IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that thereare no other ways to produce, test,
5、 measure, purchase, market, or provide other goods and services related tothe scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved andissued is subject to change brought about through developments in the state of the art and commentsreceived from users
6、of the standard.In publishing and making its standards available, IEEE is not suggesting or rendering professional or otherservices for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by anyother person or entity to another. Any person utilizing any IEEE Stand
7、ards document, should rely upon hisor her own independent judgment in the exercise of reasonable care in any given circumstances or, asappropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEEstandard.IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT,
8、INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO:PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDIN
9、G NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPONANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE ANDREGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.4Copyright 2018 IEEE. All rights reserved.Translations The IEEE consensus development proc
10、ess involves the review of documents in English only. In the eventthat an IEEE standard is translated, only the English version published by IEEE should be considered theapproved IEEE standard.Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Stan
11、dards BoardOperations Manual shall not be considered or inferred to be the official position of IEEE or any of itscommittees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectures,symposia, seminars, or educational courses, an individual presenting informatio
12、n on IEEE standards shallmake it clear that his or her views should be considered the personal views of that individual rather than theformal position of IEEE.Comments on standardsComments for revision of IEEE Standards documents are welcome from any interested party, regardless ofmembership affilia
13、tion with IEEE. However, IEEE does not provide consulting information or advicepertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of aproposed change of text, together with appropriate supporting comments. Since IEEE standards represent aconsensus of c
14、oncerned interests, it is important that any responses to comments and questions also receivethe concurrence of a balance of interests. For this reason, IEEE and the members of its societies andStandards Coordinating Committees are not able to provide an instant response to comments or questionsexce
15、pt in those cases where the matter has previously been addressed. For the same reason, IEEE does notrespond to interpretation requests. Any person who would like to participate in revisions to an IEEEstandard is welcome to join the relevant IEEE working group.Comments on standards should be submitte
16、d to the following address:Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USALaws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with theprovisions of any IEEE Standards document does not imply compliance to any
17、 applicable regulatoryrequirements. Implementers of the standard are responsible for observing or referring to the applicableregulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is notin compliance with applicable laws, and these documents may not b
18、e construed as doing so.CopyrightsIEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws.They are made available by IEEE and are adopted for a wide variety of both public and private uses. Theseinclude both use, by reference, in laws and regulations, an
19、d use in private self-regulation, standardization,and the promotion of engineering practices and methods. By making these documents available for use andadoption by public authorities and private users, IEEE does not waive any rights in copyright to thedocuments.5Copyright 2018 IEEE. All rights rese
20、rved.Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license tophotocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please conta
21、ct Copyright Clearance Center,Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission tophotocopy portions of any individual standard for educational classroom use can also be obtained throughthe Copyright Clearance Center.Updating of IEEE Standards documents Users o
22、f IEEE Standards documents should be aware that these documents may be superseded at any timeby the issuance of new editions or may be amended from time to time through the issuance of amendments,corrigenda, or errata. A current IEEE document at any point in time consists of the current edition of t
23、hedocument together with any amendments, corrigenda, or errata then in effect. Every IEEE standard is subjected to review at least every ten years. When a document is more than ten yearsold and has not undergone a revision process, it is reasonable to conclude that its contents, although still ofsom
24、e value, do not wholly reflect the present state of the art. Users are cautioned to check to determine thatthey have the latest edition of any IEEE standard.In order to determine whether a given document is the current edition and whether it has been amendedthrough the issuance of amendments, corrig
25、enda, or errata, visit the IEEE-SA Website at http:/ieeexplore.ieee.org/ or contact IEEE at the address listed previously. For more information about the IEEESA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org.Errata Errata, if any, for all IEEE standards
26、 can be accessed on the IEEE-SA Website at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errataperiodically.PatentsAttention is called to the possibility that implementation of this standard may require use of subject mattercovered
27、 by patent rights. By publication of this standard, no position is taken by the IEEE with respect to theexistence or validity of any patent rights in connection therewith. If a patent holder or patent applicant hasfiled a statement of assurance via an Accepted Letter of Assurance, then the statement
28、 is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicatewhether the Submitter is willing or unwilling to grant licenses under patent rights without compensation orunder reasonable rates, with reasonable terms and conditions that
29、are demonstrably free of any unfairdiscrimination to applicants desiring to obtain such licenses.Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is notresponsible for identifying Essential Patent Claims for which a license may be required, for conduc
30、tinginquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms orconditions provided in connection with submission of a Letter of Assurance, if any, or in any licensingagreements are reasonable or non-discriminatory. Users of this standard are expressly
31、advised thatdetermination of the validity of any patent rights, and the risk of infringement of such rights, is entirely theirown responsibility. Further information may be obtained from the IEEE Standards Association.6Copyright 2018 IEEE. All rights reserved.ParticipantsAt the time of approval of t
32、his standard, the IEEE 802.1 Working Group had the following membership:Glenn Parsons, ChairJohn Messenger, Vice ChairJnos Farkas, Chair, Time-Sensitive Networking Task Group, EditorThe following members of the individual balloting committee voted on this standard. Balloters may havevoted for approv
33、al, disapproval, or abstention. Ralf AssmannShenghua BaoGordon BechtelJens BierschenkSteinar BjrnstadChristian BoigerPaul BottorffRadhakrishna CanchiDavid ChenFeng ChenWeiying ChengPaul CongdonRodney CummingsHesham ElBakouryNorman FinnMickal FontaineGeoffrey GarnerEric W. GrayCraig GuntherMarina Gut
34、irrezStephen HaddockMark HantelMarc HolnessLokesh KabraMichael KarlStephan KehrerHajime KotoYizhou LiChristophe ManginScott MansfieldJames McIntoshRobert MoskowitzTero MustalaTomoki OhsawaDonald R. PannellWalter PienciakMichael PottsWei QiuKaren RandallMaximilian RiegelJessy V. RouyerSoheil SamiiAts
35、ushi SatoFrank ScheweMichael SeamanJohannes SpechtPatricia ThalerPaul UnbehagenHao WangTongtong WangXinyuan WangKarl WeberBrian WeisJordon WoodsTakahiro YamauraXiang YuNader ZeinThomas AlexanderButch AntonStefan AustGordon BechtelHarry BimsSteinar BjrnstadChristian BoigerDemetrio Bucaneg, Jr.William
36、 ByrdJuan CarreonKeith ChowTodor CooklevRodney CummingsLars EllegaardMarc EmmelmannYonggang FangJnos FarkasNorman FinnAvraham FreedmanMatthias FritscheYukihiro FujimotoDevon GayleEric W. GrayRandall GrovesStephen HaddockMarco HernandezWerner HoelzlNoriyuki IkeuchiAtsushi ItoRaj JainSangKwon JeongPio
37、tr KarockiStuart KerryYongbum KimMark LaubachHan Hyub LeeHyeong Ho LeeJohn LemonMichael LynchElvis MaculubaRichard MaidenRoger MarksJohn MessengerMichael MontemurroNick S. A. NikjooSatoshi ObaraRobert OHaraGlenn ParsonsBansi PatelClinton PowellAlon RegevMaximilian RiegelRobert RobinsonJessy V. Rouye
38、rPeter SaundersonMichael SeamanThomas StaraiWalter StrupplerBo SunRichard TseMark-Rene UchidaDmitri VarsanofievKari VierimaaGeorge VlantisKhurram WaheedLisa WardHung-Yu WeiAndreas WolfOren YuenNader ZeinZhen Zhou7Copyright 2018 IEEE. All rights reserved.When the IEEE-SA Standards Board approved this
39、 standard on 7 May 2018, it had the followingmembership:Jean-Philippe Faure, ChairGary Hoffman, Vice ChairJohn D. Kulick, Past ChairKonstantinos Karachalios, Secretary*Member EmeritusChuck AdamsMasayuki AriyoshiTed BurseStephen DukesDoug EdwardsJ. Travis GriffithMichael JanezicThomas KoshyJoseph L.
40、Koepfinger*Kevin LuDaleep MohlaDamir NovoselRonald C. PetersenAnnette D. ReillyRobby RobsonDorothy StanleyAdrian StephensMehmet UlemaPhil WennblomHoward WolfmanYu Yuan8Copyright 2018 IEEE. All rights reserved.IntroductionThis standard defines profiles that select features, options, configurations, d
41、efaults, protocols and proceduresof bridges, stations, and LANs that are necessary to build networks that are capable of transporting fronthaulstreams, which are time-sensitive.This introduction is not part of IEEE Std 802.1CM-2018, IEEE Standard for Local and metropolitan area networksTime-Sensitiv
42、e Networking for Fronthaul.9Copyright 2018 IEEE. All rights reserved.Contents1. Overview . 101.1 Scope 101.2 Purpose. 101.3 Introduction 102. Normative references 123. Definitions 134. Acronyms and abbreviations 145. Conformance . 165.1 Requirements terminology. 165.2 Profile Conformance Statement (
43、PCS) 165.3 Bridge requirements. 165.4 Bridge options 175.5 End station requirements . 185.6 End station options. 186. Fronthaul . 206.1 Evolved Universal Terrestrial Radio Access background . 216.2 Class 1 requirements 216.3 Class 2 requirements 236.4 Synchronization requirements . 267. Bridge and s
44、ynchronization functions 317.1 Latency components 317.2 Bridge delay calculation 317.3 Frame preemption 337.4 Network synchronization. 337.5 Flow control. 377.6 Energy Efficient Ethernet 378. Fronthaul profiles 398.1 Profile A. 408.2 Profile B. 429. Synchronization solutions . 449.1 Solution for Cat
45、egory A+ 449.2 Solutions for Category A . 449.3 Solutions for Category B . 449.4 Solutions for Category C . 44Annex A (normative) PCS proformaTime-Sensitive Networking for Fronthaul Profiles. 45Annex B (informative) Delay calculation examples 55Annex C (informative) Bibliography. 59IEEE Std 802.1CM-
46、2018IEEE Standard for Local and metropolitan area networksTime-Sensitive Networking for Fronthaul10Copyright 2018 IEEE. All rights reserved. IEEE Standard for Local and metropolitan area networksTime-Sensitive Networking for Fronthaul1. Overview1.1 ScopeThis standard defines profiles that select fea
47、tures, options, configurations, defaults, protocols and proceduresof bridges, stations, and LANs that are necessary to build networks that are capable of transporting fronthaulstreams, which are time-sensitive.NOTEStream and flow are used as synonyms in this document.11.2 PurposeThe purpose of this
48、standard is to specify defaults and profiles that enable the transport of time-sensitivefronthaul streams in Ethernet bridged networks.1.3 IntroductionFronthaul provides connectivity between functional blocks of a cellular base station (BS). The fronthaulflows between these functional blocks have st
49、ringent quality of service requirements. The successful supportof fronthaul flows in a bridged network requires the selection of specific features and options that arespecified in a number of different standards, some developed by IEEE Project 802, and others (inparticular, those that relate to functionality in OSI layer 3 and above; ISO/IEC 7498:1994 B11) developedby other standards organizations.2This standard selects features and options that support OSI layers 1 and 2 in bridges and end stations fromthe following specifications: Virtual Local Area
