hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2de3df3c06bacb40b2a5b2ba42d09851 | 103 863 | 9.4.3 Limit | The blocking level for any of the above specified frequencies shall be greater than 55 dB. |
2de3df3c06bacb40b2a5b2ba42d09851 | 103 863 | 9.5 Spurious emissions | |
2de3df3c06bacb40b2a5b2ba42d09851 | 103 863 | 9.5.1 Definition | Receiver spurious emissions are emissions at any frequency. |
2de3df3c06bacb40b2a5b2ba42d09851 | 103 863 | 9.5.2 Method of measurement | The measurement set up shall be as in Figure 12. The measurement antenna shall be connected to a spectrum analyser and Max Hold (peak detector) shall be selected. The value of the emissions shall be measured. The measurement shall be made over the frequency range from 30 MHz to 26 GHz. The reference bandwidths shall be... |
2de3df3c06bacb40b2a5b2ba42d09851 | 103 863 | 9.5.3 Limits | The spurious emissions of the receiver shall not exceed the limits specified in Table 2. Table 2: Receiver spurious emission limits and measurement bandwidth Frequency range Emission Limits RBW 30 MHz ≤ f ≤ 1 GHz -57 dBm 100 kHz 1 GHz < f ≤ 26 GHz -47 dBm 1 MHz ETSI ETSI TS 103 863 V1.1.1 (2023-01) 23 History Document ... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 1 Scope | The present defines a "digital product passport" for ICT products to be represented in digital format, including an overview of the opportunities and benefits to include information relevant to sustainability, mainly environmental related, focusing on circularity and transparency. The present document does not intend t... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 2 References | |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 3 Definition of terms, symbols and abbreviations | |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 3.1 Terms | For the purposes of the present document, the following terms apply: accountability: equivalent to answerability, liability, and the expectation of account-giving, with the obligation to inform about (past or future) actions and decisions, to justify them NOTE: Adapted from [i.18] and [i.19]. authenticity: ability of p... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 3.2 Symbols | Void. |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADR International carriage of Dangerous goods by Road CRT Cathode Ray Tube DGS Delivery and Global Solutions DPP Digital Product Passport ECHA European Chemicals Agency NOTE: ECHA: Candidate list: https://echa.europa.eu/candidate-list-table, A... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 4 Conventions | Generally, ETSI ES 203 199 [i.27] and Recommendation ITU-T L.1410 [i.28] use the term "ICT goods" instead of "ICT products", however considering the present document is about the Digital Product Passport, both terms are used interchangeably. Hence the term "product" should be considered synonymous to the term "goods" i... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 5 Description and scope of the digital product passport | For ICT products, access to digital information about a product, a DPP, enables or facilitates the activities of product operators, such as manufacturers, buyers, owners, repairers, refurbishes, recyclers, market surveillance authorities, environmental and sustainability auditors, customs, etc. DPP may provide access t... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6 Circular digital products | |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.0 General | The scope of products in the present document is digital technology products (ICT products/goods and their components, e-equipment, and e-waste), focusing on circular and sustainable products. This clause describes stages, challenges, digitalisation considerations in different stages and for different actors of the cir... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.1 Objectives for a circular economy | Three are recognized as the main objectives for the circular economy for electronics as reported in [i.52]: 1) New products use more recycled and recyclable content. 2) Products and their components are used for longer. 3) After the end of the use stage products are collected and recycled to a high standard. These obje... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.2 Lifecycle stages | Circular digital products undergo several lifecycle stages see Recommendation ITU-T L.1410 [i.28] or the technically aligned ETSI ES 203 199 [i.27] and face challenges that the digitalisation of the life cycle information supported by a DPP can help with. The life cycle stages of ICT products are grouped as goods raw m... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.3 Challenges in the electronics life cycles | Despite the push towards a circular economy, with an impetus to systemic improvement and awareness-raising, on-ground implementation challenges hold back a more efficient and circular electronics life cycles. These are, according to [i.36]: • Insufficient and unreliable data on e-waste flows, such as for the definition... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.4 Digitalising the information about ICT product' life cycles | Applying digital technologies, specifically a DPP, can support the transition to a circular electronics industry, helping address the challenges just introduced, helping optimize existing solutions with digitalisation and enabling new transformative ways. That implies satisfying the needs of all stakeholders. Each acto... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.5 Desirable properties of product information | In the context of access to environmental information, following what the Aarhus convention [i.5], the Escazu agreement [i.6] or EU directive 2003/4/EC [i.76] recognize, the quality properties described below render environmental and sustainability-related information useful and reliable at the product level and in agg... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.6 Definition of the product | 6.6.0 General What is the product in the context of electronics and ICT products has to do with the required level of detail in terms of breadth, precision or granularity of identification. A DPP shall refer to the following not exhaustive list of product type: • Individual ICT goods: such as a serialized or customized... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.6.1 Classes of products (verticals) | Some characteristics are specific to ICT product classes (verticals) with specific environmental requirements for function or form (components). Some examples of product categories: • Electric and autonomous vehicles have large batteries and many critical ICT elements (products), with specific environmental and persona... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.6.2 Customization and change | While new or remanufactured consumer or industrial ICT products are produced in large quantities with identical features, therefore represented by a DPP in common, customized (modified) products as a result of reconfiguration, repair, refurbishment, incorporating new, modified or second-hand pieces tend to acquire uniq... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 6.6.3 Relevant details to sustainability | Considering a circular lifespan of products that results in the need for reporting information related to or resulting from processes, ranging from raw material acquisition, manufacturing, usage, servitization, transfer, maintenance, repair, refurbishing, remanufacturing, disassembly, recycling, and recovery (more info... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 7 Guidance for implementation | 7.0 General The present global and broad (generic) document contains an overview from an environmental perspective (sustainability) about the digitalisation of product-related information integrated and harmonized under a digital product passport representation. DPPs are expected to incorporate data in response to dema... |
03af2b77ec1b98774cc886858862dd72 | 103 881 | 7.1 DPP architecture considerations | The product-level scope of DPP has considerable implications for the DPP architecture and implementation. Alternatives are compared in Table 1. Table 1: Impact of the product-level scope of DPP architecture Product-level scope of DPP Comparison item brand Product model (collective) Product batch (collective) individual... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 1 Scope | The contents of the present document are subject to continuing work within O-RAN and may change following formal O-RAN approval. Should the O-RAN Alliance modify the contents of the present document, it will be re-released by O- RAN with an identifying change of release date and an increase in version number as follows... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 2 References | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference t... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3 Definition of terms, symbols and abbreviations | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. C-Plane: Control Plane: refers specifically to real-time control between O-DU and O-RU, an... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: None. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. eNB e NodeB (applies to LTE) FHM Fronthaul Multiplexer gNB g Node... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.4 Document Conventions | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.4.1 Terminologies | For the purposes of the present document, the following terminologies apply. ignored Within this specification, it is sometimes stated that certain information elements are to be “ignored” by the receiver (generally for “reserved” fields but in some cases other fields too). In this case, the fields shall be ignored for... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 3.4.2 Fields and Bitmasks in Messages | For the purposes of the present document, the following conventions apply for the format of messages and data structures within messages. In accordance with RFC 1166 [10], the left most bit of an octet is the most significant bit (msb) and the right most bit is the least significant bit (lsb). The msb is labelled as 0 ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4 Architecture & Requirements | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1 Architectural aspects | The architecture of eNB or gNB with O-DU and O-RUs is shown in Figure 4-1. LLS-C and LLS-U provide C-plane and U-plane over LLS interface, respectively. In this architecture, O-DU and O-RU can be defined as follows. Lower Layer Split Central Unit (O-DU): a logical node that includes the eNB/gNB functions as listed in c... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.1 Functional Split | When considering the functional split defining a fronthaul interface there are two competing interests: a) There is a benefit in keeping an O-RU as simple as possible because size, weight, and power draw are primary deciding considerations and the more complex an O-RU, the larger, heavier and more power-hungry the O-RU... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.2 Selected Split 7-2x (DL) | DL functional split for various physical layer channels is illustrated in Figure 4-3 (LTE Category A O-RUs), Figure 4-4 (LTE Category B O-RUs), Figure 4-5 (NR Category A O-RUs), and Figure 4-6 (NR Category B O-RUs). When O-RU Category A is supported by O-DU it is mandatory to support a total number of precoded streams ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.2.1 Description | In the DL, OFDM phase compensation (clause 5.4 of [4]), iFFT, CP addition, and digital beamforming functions reside in the O-RU as well as precoding for Category B O-RUs. The rest of the PHY functions including resource element mapping, precoding, layer mapping, modulation, scrambling, rate matching and coding reside i... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.2.2 Benefits and Justification | • Interface simplicity: Transfer of user plane data is based on Resource Elements / Physical Resource Blocks, which simplifies the data mapping and limits the required associated control messages • Transport Bandwidth Scalability: Lower split options (e.g., splits 7-1 and 8) scale based on number of antennas. In contra... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.3 Selected Split 7-2x (UL) | UL functional split for various physical layer channels and transmission modes are illustrated in Figure 4-7. Likewise, digital beamforming in this context, is the function of antenna port selection or antenna port combining. Digital Beamforming Equalization, iDFT Channel Estimation Detection Demodulation FFT and CP re... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.3.1 Description | In the UL, OFDM phase compensation (for all channels except PRACH when Section Type “3” message is used) according to clause 5.4 of [4], FFT, CP removal and digital beamforming functions reside in the O-RU. The rest of the PHY functions including resource element de-mapping, equalization, de-modulation, de-scrambling, ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.1.3.2 Benefits and Justification | The benefits defined for Option 7-2x for DL are also applicable for Uplink (See clause 4.1.2.2). |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.2 Data Flows | An overall reference of required inputs for some major functional blocks, their granularity and input originating source is compiled in Table 4-1 and Table 4-2 for DL and UL respectively. Table 4-1 : Required information for each functional block (DL) Function Required Information Signaling Granularity Information sour... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3 Latency Requirements | Intra-PHY lower layer fronthaul split has characteristic of a stringent bandwidth and tight latency requirement. This implies use of a special “Fronthaul Service Profile” to be supported by the transport network, and which may differ depending on the operating environment, topology and target use cases. The general con... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.1 Timing Parameter Relationships | To ensure proper reception of data at the receiver over the packet interface, there are several relationships between the parameters defined above which shall be met. First it is important to understand the nature of the transmission itself. In either direction (downlink/ uplink) it takes some amount of time for the se... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.1.1 O-DU Transmission Window | The U-Plane O-DU transmission window (T1amax – T1amin) is defined by the relationships above based on the O-RU reception window and max transport variation. It does not define the exact timing of transmission from the O-DU. Rather, it defines the boundaries that the U-Plane O-DU transmission shall operate within. The w... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.2 U-Plane/ C-Plane Timing | The basic delay parameters above describe the general delay model and characteristics of the O-RAN interface. However, the ORAN interface is divided into C-Plane and U-Plane parts. The C-Plane shall be available in order to process the corresponding U-Plane packets. To support coordination of C-Plane and U-Plane timing... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.3 Computed Latency Methods | As previously noted, the goal of delay management for O-RAN interfaces is to ensure that the transmission/ reception windows as the O-DU are properly aligned to support the O-RU and transport network characteristics. The computed methods require the O-DU to compute the required transmit and receive windows based on O-R... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.3.1 Fronthaul Timing Domain | When using a computed delay approach, the domain over which the O-DU delay parameters apply shall be considered. A timing domain is defined as the set of O-DU and O-RU ports to which the computed O-DU delay parameters apply. The O-DU timing domain may encompass a single O-DU port, or may encompass multiple O-DU ports, ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.3.2 Defined Transport Method | With the Defined Transport method, the O-DU transmit and receive windows are determined based on pre-defined transport network characteristics, and the delay characteristics of the O-RUs within the timing domain. For this approach to work, the O-RU delay characteristics as defined in Table 4-14 for each O-RU in the tim... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.3.3 Measured Transport Method | With the Measured Transport method, the O-DU transmit and receive windows are determined based on the delay characteristics of the O-RUs as defined in clause 4.3.3.2, and measured transport delays between all O-DU ports and O- RU ports in the timing domain. The O-DU shall measure the transport delay(s) for all O-RU/O-D... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.4 Latency Categories for O-DU with dynamic timing advance | As an aide to selection of equipment for use in specific transport network use cases, O-RAN O-DU and O-RU are categorized based on delay capabilities. Equipment is categorized with a Category [AAAA-ZZ] and Sub-category [.00- .1000]. The category can be used to determine the maximum T12max/ T34max which the equipment ca... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.5 Latency Categories for O-DU with fixed timing advance | The same category concepts apply for O-DU which support fixed transmit/ receive windows. The earliest transmit window and latest receive window timing defines the maximum range that the O-DU can support. T1a_max_upO-DU for the O-DU is equal to the T1a_max_up of the earliest fixed transmit window. Similarly, Ta4_maxO-DU... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.3.6 Non-Delay Managed U-Plane Traffic | While most U-Plane data shall meet the delay constraints described above, there are certain types of U-Plane traffic for which the reception windows may not be applicable. Not applying the transmission/ reception window constraints to such data allows the transmission of the data over the fronthaul interface to be spre... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.5.1 Normal Transmission | O-RU and O-DU send C- and U-Plane messages at unspecified time within appropriate transmission window (see clause 4.3.2 for general description of transmission windows). This default O-RU transmission behavior in uplink may be altered by configuration over M-plane or with Section Extension 18 in C-plane message as desc... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.5.2.1 Overlapping transmission windows | In many cases transmission windows will be overlapping between different user data flows (different eAxCs or different section IDs etc.) When this is the case the same “rule” as described above in clause 4.5.2 is still valid. I.e. within the specific sub-window that data packet should be sent at a random time. If sever... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.5.3 Ordered Transmission | O-RU may be configured (over M-plane) to order transmission of UL U-plane messages within transmission window (ordered-transmission-supported in M-Plane). If O-RU is configured to order transmission of a set of eAxC then O- RU reports how eAxC are grouped into ordering groups (G) and relative order of eAxCs within each... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.5.4 Scheduled Transmission | O-RU may be configured (over M-plane or with Section Extension 18 in C-plane message) to shift (delay) and/or resize UL U-plane messages transmission window. O-RU may be commanded to shift the transmission window by given offset (delay) expressed as number of symbols. Depending on the O-RU capability the eAxC specific ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.6 O-RU External Antenna Delay Handling | Up to and including v06.00 of this specification it is not possible to adjust timing to compensate transmission delays between antenna ports of the O-RU and the external antenna. Figure 2-9 assumes that the antenna delay is negligible compared to the O-RU’s internal delay or is known by the O-RU. Figure 2-9 defines the... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.6.1 Minimal O-DU Impact Method (Defined Transport Method) | When using Defined Transport Method as described in clause 4.3.3.2 and non-negligible external delays between the O- RU and antenna are present this method will have a minimal impact on the O-DU implementation. The presence of the external delays is assumed to be unknown to the part of the O-DU implementation that hand... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 4.6.1.1 Minimal O-DU Impact Method - Example | This clause shows an example of the timing relations for downlink and uplink when using the method described in clause 4.1.1. Table 4-18 contains values for all relevant parameters used in this example. Table 4-18: Parameters for example Parameter Latency (Tda = Tau = 0) [µs] Latency (Tda = Tau = 25) [µs] Physical T12/... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5 Transport & Protocol Architecture | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1 Transport Encapsulation Types | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.1 Ethernet Encapsulation | Ethernet can be used as transport mechanism for both U-plane and C-plane. In this case, messages are transmitted over standard Ethernet frames (See Figure 5-1). The supported frame format is Ethernet II/DIX frame with type interpretation of the type length field. The Length-interpretation and multiplexing data with LLC... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.2 IP/UDP Encapsulation | IP/UDP can be used as transport mechanism for both U-plane and C-plane. In this case, IP version 4 shall be supported according to RFC791 (Internet Protocol), and/or IPv6 as per RFC2460 (both IPv4 and IPv6 are optional, see Table 8-2). The encapsulation mechanism is identified by “IPv4” or “IPv6” Ethertype (See Figure ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3 Transport Headers | O-RAN allows for multiple different transport headers within the Ethernet payload to further describe how the application data is to be handled in the C-Plane and U-Plane. In each case the transport header is 8 bytes in length and provides basic data routing capabilities, including description of the data flow type, se... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1 eCPRI Transport Header | The definition of the eCPRI transport header is shown in Table 5-1 below. Table 5-1 : eCPRI Transport Header Field Definitions Section Type : any 0 (msb) 1 2 3 4 5 6 7 (lsb) # of bytes ecpriVersion ecpriReserved ecpriConcat enation 1 Octet 1 ecpriMessage 1 Octet 2 ecpriPayload 2 Octet 3 ecpriRtcid / ecpriPcid 2 Octet 5... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.1 ecpriVersion (eCPRI protocol revision) | Description: This parameter indicates the eCPRI protocol version. NOTE: This parameter is part of the eCPRI common header. Value range: {0001b=eCPRI version 1.0, 1.1, 1.2 and 2.0, where the interpretation of the eCPRI message shall follow the eCPRI specification versions up to 2.0; 0000b and 0010b-1111b=Reserved for fu... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.2 ecpriReserved (eCPRI reserved) | Description: This parameter is reserved for eCPRI future use. NOTE: This parameter is part of the eCPRI common header. Value range: {001b-111b=Reserved}. Type: unsigned integer Field length: 3 bits. Default Value: 000b (reserved fields should always be set to all zeros). |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.3 ecpriConcatenation (eCPRI concatenation indicator) | Description: This parameter indicates when eCPRI concatenation is in use (allowing multiple eCPRI messages in a single Ethernet payload). NOTE: This parameter is part of the eCPRI common header. Value range: {0b=No concatenation, 1b=Concatenation}. Type: binary bit. Field length: 1 bits. Default Value: 0b (no concatena... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.4 ecpriMessage (eCPRI message type) | Description: This parameter indicates the type of service conveyed by the message type. NOTE: This parameter is part of the eCPRI common header. NOTE: In this version of the specification, only values “0000 0000b” and “0000 0010b” and “0000 0101b” are used. Value range: 0000 0000b = IQ data message; 0000 0010b = Real-t... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.5 ecpriPayload (eCPRI payload size) | Description: This parameter is the size in bytes of the payload part of the corresponding eCPRI message. It does not include any padding bytes following the eCPRI message. The maximum supported payload size is 216-1, but the actual ETSI ETSI TS 103 859 V7.0.2 (2022-09) 55 size may be further limited by the maximum payl... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.1.7 ecpriSeqid (message identifier) | Description: This parameter provides unique message identification and ordering on two different levels. The first octet of this parameter is the Sequence ID, which is used to identify ordering of messages within an eAxC message stream. The Sequence ID field increments and wraps independently for each U-Plane eAxC DL, ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.2 1914.3 Transport Header | As an alternative to eCPRI as a transport header, IEEE 1914.3 may be used. The definition of the 1914.3 transport header is shown in Table 5-4 below. Table 5-4 : 1914.3 Transport Header Field Definitions Section Type : any 0 (msb) 1 2 3 4 5 6 7 (lsb) # of bytes RoEsubType 1 Octet 1 RoEflowId 1 Octet 2 RoElength 2 Octet... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.2.1 RoEsubType (sub type / message type) | Description: This field indicates the payload type within the IEEE 1914.3 Standard for Radio over Ethernet Encapsulations and Mappings (RoE) subType range. RoE allows RoE subTypes in the range 128 to 191 to be mapped to external organizations and companies using a subtype mapping table (below). This table has two field... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.2.2 RoEflowID (flow identifier) | Description: The RoEflowID is a mechanism which can identify specific flows between end-points. RoEflowID, 0xFF is reserved for RoE control packets. O-RAN has no current use for this field. Value range: 0 – 0xFE. Type: unsigned integer. Field length: 8 bits. Description: This field is currently unused. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.2.3 RoElength (length) | Description: This field is the size in bytes of the payload part of the message. The payload length field value is the total number of octets following the O-RAN common header. It does not include the Ethernet FCS or following bytes. Value range: 0 – 0xFFFF. Type: unsigned integer. Field length: 16 bits. |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.1.3.2.4 RoEorderInfo (order information) | Description: This field is split into seven sub-fields. Table 5-6 : RoE RoEorderInfo MappingField Field Length Note DU_Port_ID 16 bits Used to differentiate processing units at O-DU (e.g., different baseband cards). It is expected the O-DU will assign these bits, and the O-RU will attach the same value to the UL U-Plan... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.2 Protocol Architecture | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.2.1 C-plane | Figure 5-7 depicts the protocol stack for C-Plane. Data can be optionally transmitted over IP Layer 3 if supported by the transmitting and receiving nodes. Figure 5-7 : C-plane protocol structure |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.2.2 U-plane | Figure 5-8 depicts the protocol stack for U-Plane. Data can be optionally transmitted over IP Layer 3 if supported by the transmitting and receiving nodes. Figure 5-8 : U-plane protocol structure |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.2.3 S-plane | Frequency and time synchronization of O-DUs and O-RUs via Ethernet use Synchronous Ethernet and IEEE 1588 Precision Time Protocol (PTP). Transport of PTP directly over L2 Ethernet (ITU-T G.8275.1 full timing on-path support) is assumed in this version of the specification, whilst transport of PTP over UDP/IP (ITU-T G.8... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.3 Quality of Service | The LLS interface needs to support the ability to distinguish between data flows with different QoS requirements. Configurable priority levels (via the M-Plane) for traffic prioritization of flows shall be supported on each node on the network path. Default values for the respective O-RAN planes are indicated. Priority... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.4 Data Flow Identification | Differentiation between a combined U/C-Plane data flow for a single eAxC_ID and Management Plane data flow traffic can be achieved using the following options: • Data flow separation based on TCP/UDP (applicable when layer 3 transport is used for the C/U-plane) • Data flow separation based on VLAN (applicable when laye... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.5 Fragmentation | Fragmentation is applied in case data (U-Plane or C-Plane data) with Ethernet transport overheads to be transferred exceed maximum transmission unit (MTU) of the network. This specification allows two methods for fragmentation, application layer fragmentation and transport layer fragmentation: |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.5.1 Application layer fragmentation | • Application creates C-plane or U-Plane messages, which when including overheads can fit to MTU requirements set by network • Sequence ID: Sequence ID increases for every message, E=1, Subsequence ID=0 An example of application fragmentation is provided in Figure 5-10, wherein a long data section is split between mult... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.5.2 Radio Transport layer (eCPRI or IEEE-1914.3) fragmentation | o Application creates U-Plane messages, which when including overhead may exceed MTU requirements set by network o Radio transport layer splits message which may contain more than one section into pieces such that the fragments with overheads fit to MTU requirements set by network. o Sequence ID: Sequence ID remains sa... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 5.5.3 Fragmentation Guideline | Application layer fragmentation should be applied so that maximum size standard IEEE 802.3 Ethernet frames can be used. (Jumbo frames, if used, increase the maximum MTU size). • In case of L2 only solution, application layer maximum transmission unit size is standard IEEE 802.3 Ethernet frame payload size (1500 bytes) ... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 6 Security | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 6.1 General | Security requirements are depicted in Table 6-1. Table 6-1 : Security requirements for User-Plane, Control-Plane, and Synchronization-Plane Plane Integrity (protection from modifications) Confidentiality (encryption protection) Availability (protection from packet insertion) Remarks U-Plane No requirement No requiremen... |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7 C-plane Protocol | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.1 General | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.2 Function | |
bedca00b77bd2bcaa5a1804601b66e93 | 103 859 | 7.2.1 C-Plane Transport | Either eCPRI or IEEE 1914.3 is used as an encapsulation mechanism for the control-plane messages. Due to the nature of these messages (very strict delay constraints), it is assumed that message acknowledgements are not possible. Likewise, it is assumed that a different data flow is used other than the U-Plane channel. ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.