IEEE Std 802.1CM-2018 pdf free download – IEEE Standard for Local and metropolitan area networks- Time-Sensitive Networking for Fronthaul.
3. Definitions
For the purposes of this document, the fllowing tems and definitions apply. The IEEE Suandarnds Dictionary Online should be consulted for terms not defined im this clause 8 This standard maks use of the fllowing terms defined in IEEE Std 802:
bridge
end station
Ethermet
forwanding
frame
Local Area Network (LAN)
This standard maks use of the fllowing terms defined in IEEE Sud 802. IQ:
bridged network
latency
port
prionity. laged frame
traffic class
untagped frame
Virtual Local Area Network (VLAN)
VLAN Bridge
VLAN tagged fume
The fllwing terms are specific to this standand:
Category: An idenfier of time synchronization requirements.”
NOTE- -See 6.4.1.
Cass: A oleivee term for fronthaul itereaces that pplies a particular functional decomposition of a cellular base station and a particular treatment of fonthaul information flows.
NOTE- -See 6.2 and 63.
fronthaul: The coneetivity between the functional blocks (eg, bascband processing and nadio frequeney blocks) of a cellular base station.
periodic: Repeating continwously, with a constant time (the period) between cach oceurenee.
Synchronous Ethernet: A method to distibute frequency synchronizatio over the Ethemet phy sical layer according to IEEE Sid 802.3 and ITUT Recommendations G8261, G8262. G8264.0 time window: A time interval (among back-to-back time intevals of the same duration), within which packets of a speeified flow can be sent.
5. Conformance A claim of conformance to this standard is a claim that the bechavior of a implementation of a bridge (5.3, 5.4) or of an end station (55, 5.6) meets the mandatory requirements of this standard and may supprt options ientifid in this standard.
5.1 Requirements terminology For consistency with existing IEEE and IEEE 802. 1T standurds, requirements placed upon conformant implementations of this standard are exressed using the fllowing terminology:
a) Shall is used for mandatory requirements;
b) May is used to describe implementation or administrative choices (‘”may” means “is permited to.,” and hence,“may” and“may not” mean prcisely the same thingk
c) Should is used for recommended choices (the behaviors described by “should” and“should not” are both pemissible but not cqually desirable choices).
The Profle Conformance Statement (PCS) profomas (see Annex A) rflt the occurences of the words “shall,”“may,” and “should” within the standard. The standard avoids nelless repetition and apparent duplication of its fomal requirements by using i i n0t, are, and are nor for definitions and the logical consequences of confommant behavior. Behavior that is permitted but is neither always required nor deety cotolldl by an implementer or adnministrator, or whose onformance requirement is detailed elsewhere, is described by cou. Behavior that never occurs in a conformant implenentaion or systemn of confomant implementations i described by canmot. The word allo is used as a replacement for the phrase“*support the ability for.” and the word apubility means“can be configured to.”
5.2 Profile Conformance Statement (PCS) The supplier of an implemenation that is claimed to conform to this standard shall prov ide the infomation neessary to identify both the supplier and the implementation, and shall complste a copy of the PCS proforma provided in Amex A.
5.3 Bridge requirements This subclause defines the conformance requiremnents fo bridge implermentations claiming conformance to this standard. Each bridge implementation supports one or more profiles defined in this standard. Each profle includes tbe comon bridge requirements (53.1). A bridge inmplementation that confoms to tbe provisions of this standard shall support Profile A requircements (5.3.2) IEEE Std 802.1CM pdf download.