O-DU to O-RU Fiber Link Design

Definition: An O-DU to O-RU fiber link is the physical optical path used by an approved open-fronthaul design. O-RAN and eCPRI define interface and transport scope; they do not select one cable or connector. Endpoint, optics, transport, route, and acceptance documents determine whether the link uses direct fiber, protected MPO aggregation, a hardened demarcation, or another approved topology.

For procurement, collect the governing open-fronthaul profile, O-DU and O-RU model and port documents, paired transceiver data, transport topology, synchronization plan, and route drawing. Compare those records before selecting direct fiber, protected MPO aggregation, a hardened demarcation, or an approved WDM or packet path. Hold the cable BOM if the records conflict, any budget is open, an exposed boundary lacks evidence, or the fiber map is incomplete. A familiar connector, rate, wavelength, reach, or outdoor label cannot resolve a missing design decision.

Early project checkpoint: If the endpoint, optics, topology or route records disagree, consolidate the conflict log before requesting a cable part number. This keeps an RFQ from converting an open system decision into an unapproved supplier assumption.

Define the O-DU/O-RU boundary before choosing cable

The O-DU/O-RU boundary defines a network function and interface relationship. It does not define a ready-made cable assembly. Project documents, not the protocol name, establish the cabling requirements.

3GPP TS 38.401 provides NG-RAN architecture context for central and distributed functions. Within the O-RAN program, Working Group 4 develops open-fronthaul specifications and test specifications for the O-DU/O-RU interface. The eCPRI specification set describes a packet-based fronthaul transport interface and related requirements.

How do you define the physical link in six evidence steps?

Treat O-RAN open fronthaul cabling and eCPRI fiber link as names for a project-defined implementation, not catalog cable types. The protocol label alone cannot identify the radio connector, approved transceiver, fiber count, route construction, or acceptable channel loss. Build the specification from this source order:

operator and system architecture with the approved functional split;
applicable O-RAN/eCPRI profile and revision;
O-DU, O-RU, and transport-equipment documentation;
transceiver or integrated-optics documentation;
route, environment, and passive-path records;
the cabling drawing and acceptance plan.

When a lower-level drawing conflicts with an upstream source, pause the design and return the discrepancy to its owner. Physical mating alone does not establish host approval, optical interoperability, or system compliance.

The FTTA solution overview covers broader radio-site fiber infrastructure.

Map the fronthaul constraint cascade

Trace each physical decision to the source that authorizes it. Selecting cable before these inputs are stable creates rework.

Constraint layer	Controlled question	Output passed downstream	What cannot be inferred
System architecture	Which split/profile, topology, resilience and timing objectives are approved?	Interface scope, availability model and system targets	Connector, wavelength or cable construction
Endpoint equipment	Which O-DU/O-RU models, software revisions and ports are in scope?	Supported/approved port and optics options	A family-wide interface from one nearby model
Optical interface	Which paired modules or integrated optics are approved?	Rate, wavelength, reach class, connector/polish and optical limits	A universal value from "eCPRI" or "5G"
Transport topology	Is the path direct, switched, protected, packetized or wavelength-multiplexed?	Delay contributors, synchronization topology and active/passive boundaries	Fiber distance from a delay class alone
Passive path	Which cords, adapters, panels, trunks, fan-outs, splices and WDM elements are in route order?	Fiber map, connection count and channel-loss calculation	End-to-end loss from cable length alone
Environment and acceptance	Where are the exposed zones, and what must be inspected, measured and recorded?	Construction and evidence needs, plus the acceptance plan	Whole-route suitability from one "outdoor" or IP label

Procurement may flag a gap, and the cable supplier may reject an incomplete specification. Architecture, radio, optics, and transport decisions stay with their assigned owners.

Choose the physical link placement

MPO in 5G fronthaul is a placement choice. For a direct fiber versus MPO aggregation decision, compare the physical boundary and evidence burden, not only the fiber count. MPO may belong between protected distribution points even when neither active endpoint uses it. Do not place MPO at an O-RU simply because the route carries multiple fibers.

Placement pattern	When it may be considered	Required evidence	Exclude or hold when
Direct endpoint-to-endpoint fiber	Few links, simple route, no useful intermediate aggregation	Both endpoint ports, paired optics, complete route and environmental transition	Any endpoint interface or exposed transition is unresolved
Protected MPO aggregation	Several approved fiber paths share a controlled indoor or protected route or cross-connect	Trunk and fan-out drawings, complete fiber map, polarity, pinning, connection count and inspection access	The MPO system would duplicate an exposed device interface or its lane map is missing
Hardened outdoor demarcation	The design has a defined exposed equipment or transition boundary	Device-side interface, tested mated-system evidence, cable construction and installation conditions	"IP67/IP68" or "outdoor" appears without the part pairing and tested state
WDM or packet-transport path	Fiber constraints or the approved architecture justify passive or active transport elements	Channel plan, passive losses, active-node delay, synchronization, protection and operations ownership	The design treats WDM or switching as a cable-only substitution

Separate fiber category from cable construction

ITU-T G.652 and ITU-T G.657 define characteristics of single-mode optical fiber and cable, including category-specific attributes. They do not approve an unnamed cable assembly for a route. A G.652.D, G.657.A1 or G.657.A2 designation cannot replace the finished cable datasheet, route conditions or installation specification. Do not treat an optical-fiber category as the cable assembly's minimum bend radius, tensile rating, crush rating, jacket material or environmental qualification.

When the path crosses indoor, outdoor, aerial, duct, direct-burial or mechanically exposed sections, record every transition. The route specification determines whether a loose-tube, tight-buffered, armored, ADSS, duct, drop, direct-burial or other construction is relevant. It also controls the evidence needed for PE or LSZH jackets, UV exposure, flame behavior, water blocking, rodent protection, minimum bend radius, tensile load and crush resistance. None follows from "O-RAN," "5G" or the fiber category. IEC 60794-1-1:2023 establishes generic cable requirements, but the contract must invoke the applicable cable-family and test requirements for the selected product and route.

For an aerial self-supporting segment, do not select ADSS from a family name alone. The route owner must define the span, wind and any applicable ice or loading condition, sag and clearance criteria, support hardware, and installation method before the exact finished-cable data is evaluated. For an indoor/outdoor transition, LSZH or flame behavior and PE outdoor durability address different hazards; one label does not prove the other.

Use the table to choose the evidence path, not a product. The MPO cable types guide covers connector and assembly families.

Close delay, synchronization and optical loss separately

A fronthaul link budget checklist needs three separate approvals. Route distance affects each one, but it cannot stand in for transport delay, synchronization, or optical loss.

1. Transport delay

The eCPRI transport requirements define multiple one-way frame-delay classes, including 25, 100, 200 and 500 microseconds for different functional decompositions. Fiber propagation and switching can both contribute to transport delay. The governing architecture sets the class and allocation; the class does not create a universal fiber reach.

List every active and passive contributor required by the system authority, how its value was established, and who accepts the result.

2. Synchronization

The O-DU/O-RU system may use PTP, SyncE or another approved method. Its topology, clock roles, performance limits, monitoring and failure behavior belong to the synchronization design. A fiber cable carries the signal; it does not prove that the timing system complies with the project requirements.

Keep synchronization approval separate from the transport-delay worksheet. A link can meet one requirement and still fail the other.

3. Optical loss

The paired optics establish the available optical budget at their documented operating conditions. Every passive component consumes part of it:

Total channel loss = fiber attenuation + mated-pair losses + splice losses + passive-device losses + engineering margin

Count the actual path in route order. Adding a cassette, fan-out, adapter or passive WDM element changes the calculation. Use the project-specified maximum attenuation at the operating wavelength and stated conditions, not an uncited typical value. Take each mated-pair, splice and passive-device allowance from its applicable source, and keep the engineering margin visible. The result passes only when the calculated path and specified acceptance value fit the approved optical interface.

The MPO trunk cable design guide covers generic trunk sizing and passive-channel calculations. For a fronthaul release, compare that result with the delay and synchronization records.

Budget handoff rule

Assign an owner and source to each budget. Cross-check all three against the same architecture revision and physical-path drawing. If any result remains provisional, keep the cable BOM provisional.

Use a design-authority matrix

Adding another cable field rarely resolves an incomplete fronthaul specification. Send the unknown back to the team authorized to decide it.

The same ownership rule applies to transceiver compatibility. A passive-cabling supplier can compare a proposed interface with the supplied documents. The equipment and optics owner approves the host and optical pairing.

Design authority	Must provide or approve	Controlled output	BOM hold condition
RAN/system architect	Functional split/profile, endpoint relationship, availability objective and system-level timing requirements	Approved architecture baseline	Split/profile or system targets are undefined or revisions conflict
Equipment/optics owner	O-DU/O-RU models, ports, software constraints and paired optical interfaces	Endpoint/optics approval record	One side is inferred from a product family, connector color or rate label
Transport/synchronization owner	Direct/switched/WDM topology, delay allocation, synchronization design, protection and operations boundaries	Transport and synchronization approvals	Active/passive nodes or timing responsibilities are missing
Passive-infrastructure designer	Route drawing, transitions, component order, fiber map, connection count and environmental and mechanical requirements	Controlled passive-path drawing and loss calculation	A component, transition, exposure or channel map is absent
Procurement, supplier and quality reviewers	Manufacturability, offered part and drawing, applicable evidence, acceptance method, document revision and deviations	Quote, drawing and evidence package for approval	A supplier substitution changes an upstream input or lacks product-specific evidence

An ISO, IEC, ITU-T or TIA reference can identify a method or technical scope. It does not transfer design authority and does not prove that an unnamed product complies.

BWNFiber's public pre-terminated fiber cable intake asks for route, fiber, end, length, breakout, construction and pulling-protection inputs before a production drawing. For an O-DU/O-RU review, add the upstream endpoint, optics, topology, budget and acceptance evidence described here. Whether an exact assembly can be offered remains subject to current product and engineering review.

For detailed lane mapping, use the MPO polarity checklist rather than recreating its worksheet here.

Apply five hold points before BOM release

Use a hold point whenever a missing decision could change the cable assembly. Record the affected field, its owner, and the evidence required to release the BOM.

Hold 1: Architecture baseline is not controlled

Pause the BOM when the functional split, interface profile, topology or timing objective is missing or appears in conflicting revisions. Release it only after the RAN and system owner identifies the governing record.

Hold 2: Endpoint and optical documents do not agree

Pause the BOM when O-DU/O-RU ports, transceiver pairing, connector and polish, wavelength, rate or host restrictions cannot be traced to the governing documents. A physically compatible shell does not close this hold.

Hold 3: One of the three budgets is open

Pause the BOM when transport delay, synchronization or optical loss is provisional, or when the three approvals use different path or architecture revisions.

Hold 4: The exposed boundary is undefined

Pause the BOM when a connector, enclosure, transition or cable enters an outdoor or mechanically exposed zone without evidence for its state and installation conditions. Fiber category alone does not establish cable suitability.

Hold 5: The offered drawing cannot be reconciled

Pause the BOM when the supplier drawing, fiber map, labels, component order, evidence references or acceptance records cannot be reconciled with the approved path. Record every deviation and return it to the owning authority.

Illustrative document-review scenario

Consider an RFQ that names an O-RU family, an equipment list that names a transceiver family, and a route drawing that shows an outdoor transition but no mating interface. A supplier should not close those gaps by choosing a familiar jumper. Record the endpoint, optics and route discrepancies, assign each one to its design owner, and keep the BOM on hold until the controlled documents converge. This is an illustrative review scenario, not a BWNFiber customer-deployment claim.

Common shortcuts that create fronthaul rework

Copying a port or optic from another model in the same equipment family.
Selecting MPO before locating the protected distribution boundary.
Using route length as a proxy for delay, synchronization and optical feasibility.
Leaving a switch, fan-out, cassette, adapter, splice or WDM element off the path drawing.
Extending an ingress-protection claim beyond the named connector or enclosure and its tested state.
Accepting a supplier alternative that changes fiber mapping, polish or construction without design approval.
Requesting generic "standard test reports" without tying each record to an interface, criterion and acceptance plan.

Compare supplier responses before commercial release

Compare every supplier against the same controlled evidence pack. A lower price is not comparable when the proposed build, assumptions, tests or exclusions differ.

Review line	What a controlled response includes	Hold signal
Requirement traceability	Each offered characteristic maps to the submitted requirement and its source revision	The response relies on a catalog family name or rewrites the requirement without a source
Proposed assembly	Drawing, end views, route order, fiber map, labels and bill of materials identify the exact build	A part number is quoted without a reconcilable drawing or map
Product evidence	Current product-specific data supports every claimed physical, mechanical, environmental or optical characteristic	A generic standard, family page or unrelated test report is used as product proof
Deviations and assumptions	Every substitution, open field and commercial assumption is stated for design-owner review	A changed polish, mapping, construction, test method or interface is presented as equivalent without approval
Acceptance plan	Required inspection and measurement records identify method, conditions, limits and record format	The response promises a generic pass report with no link to the project criterion
Commercial basis	Quantity, length mix, approval revision, delivery destination and requested date use the same technical baseline	Price, MOQ or schedule is presented without the exact configuration and stated dependencies

What changes price and schedule?

Quantity and length mix, connector or fan-out complexity, route construction, labels and packaging, required inspection or test records, drawing-approval cycles, delivery destination and requested date can all change a quotation. Treat these as quote inputs, not article-level promises. Ask each supplier to state exclusions, validity, proposed substitutes and dependencies. Keep price, MOQ and schedule conditional until the exact item and commercial record are approved.

When is a sample useful?

Request a sample after the assembly drawing and acceptance plan are revision controlled. A production-representative sample may be used to examine agreed workmanship, mapping, labels, mechanical fit in the approved setup and specified optical measurements. It does not by itself prove host approval, software behavior, O-DU/O-RU interoperability or production-lot conformity. Record the sample identity, drawing revision, results and deviation disposition.

How do you control a bulk order after sample approval?

A sample approval is one release record, not a substitute for lot control. Freeze the drawing revision, fiber map, quantity and length matrix, labels, acceptance and sampling plan, required records, packing method, and approved deviations in the purchase order. Require written change notification and disposition for every proposed substitution or revision. At receipt, reconcile labels, quantities, records, and sampled units with that controlled baseline before accepting the batch.

How does a project move from evidence to order?

Submit the controlled architecture, endpoint, optics, transport, route and acceptance evidence pack.
Log gaps, conflicts, assumptions and the design authority responsible for each one.
Review the proposed assembly drawing, fiber map, product evidence and deviation matrix.
Complete any project-required sample or first-article review against the approved revision.
Compare quotations only when their technical scope, quantity, records, destination and schedule basis match.
Release the purchase order and project BOM against the approved drawing revision and required acceptance records.

This sequence is a control path, not evidence that BWNFiber can supply every configuration. Exact product availability and commercial terms require a current project review and quotation.

Add international procurement controls

A country or region is a screening field, not a cable specification. For an international O-DU/O-RU fiber link, record the destination country, contract and operator authority, authority having jurisdiction where applicable, installed location, route conditions and required submittals. A standard, regulation, mark or certificate becomes a requirement only when its current scope covers the exact product and intended use or the contract explicitly invokes it.

Which regional questions should the buyer close?

Use the following prompts to expose missing decisions. They are not universal legal requirements or assumptions about every site in a region.

Market scope	Standards and document questions	Route and environment questions	Commercial handoff questions
North America	Which operator, owner, AHJ, premises-cabling, electrical/building-code or listing requirements are contractually applicable? Does ANSI/TIA-568.3-E apply to any premises segment?	Where does the link cross building, outdoor, aerial, duct, buried or exposed boundaries, and which exact fire, mechanical and environmental evidence is required?	Which units, labels, receiving records, ship-to location and importer responsibilities must appear in the approved documents?
Europe	Which EU, national and contract rules apply to the exact cable and intended use? If construction-product rules are in scope, which declaration, classification and marking records are required?	Which indoor/outdoor transition, reaction-to-fire, smoke/halogen, UV, water, temperature or mechanical requirement is actually specified?	Which document language, importer/economic-operator details, delivery term and conformity records are required?
Middle East	Which national, operator, project, building or civil requirements control the submittal?	What are the site design temperature, solar/UV, dust/sand, moisture, ingress and corrosion conditions at each exposed boundary?	How many technical-submittal and inspection approvals precede production and shipment, and where is final delivery?
Southeast Asia	Which national, operator, building and fire requirements apply to each route segment?	What are the measured or specified humidity, rainfall/flood, salt/corrosion, water-entry and mechanical conditions for the actual site?	Are document language, moisture-protected packaging, port/island transfer or local receiving inspections specified?
Latin America	Which country, operator, building, electrical and fire requirements are invoked?	Do the route drawings identify UV, altitude, storm, salt/corrosion and aerial/duct/buried transitions where relevant?	Are Spanish or Portuguese records, labels, customs responsibilities and inland delivery constraints required by the contract?
Africa	Which country, operator, tender and import requirements govern the offered item?	What site-specific heat, UV, dust, rain, route-access, security and repair conditions affect construction, packaging or spares planning?	Which pre-shipment inspection, document approval, port/inland delivery and receiving steps are part of the requested schedule?

ANSI/TIA-568.3-E is an optical fiber cabling component standard for premises applications; it should not be extended automatically to every outdoor fronthaul segment. For European work, the European Commission's Construction Products Regulation guidance and CE-marking guidance both require a product-scope determination. A CE mark is not a universal certificate for every cable, and this article does not claim that any BWNFiber item is within scope or compliant.

What should an international RFQ add?

Field group	Buyer-controlled input	Required supplier response or open item
Jurisdiction and contract	Destination country, project owner, operator/AHJ, contract language, invoked standards and revisions	Requirement matrix that identifies applicable, not-applicable and unresolved items
Route and environment	Segment drawing, installed location, transitions, exposure and installation method	Exact proposed construction plus product-specific evidence for each claimed attribute
Product identity	Approved interfaces, drawing revision, fiber map, length mix and quantities	Offered item, controlled drawing, BOM and deviations tied to the same revision
Labels and controlled customization	Project names, label content/language, color or packaging marks, private-label/OEM responsibility and approval path	Marking proof, drawing changes, responsibility split and approval hold; no assumed OEM/ODM capability
Inspection and records	Witness points, sample/first-article requirement, methods, limits, sampling and record format	Inspection/test plan and exact records that can be supplied, with unsupported requests marked open
Packing	Unit length, reel/coil/drum limits, pulling-end protection, moisture/mechanical protection, lifting and receiving constraints	Packing drawing or method, dimensions/weights when known and any handling deviations
Shipment and import	Named delivery place, transport mode, importer/customs responsibilities, required origin/classification documents	Commercial assumptions, document owner and unresolved import/export questions
Schedule	Required-on-site date and approval milestones	Phase-based schedule assumptions; no unconditional lead-time commitment

If solid-wood pallets, crates, drums or dunnage are proposed, determine whether the destination requires treatment and marking under ISPM 15. The parties should state the exact Incoterms rule and named place using the current ICC Incoterms 2020 framework, and assign customs-classification responsibility instead of copying an unverified HS code from another shipment. The World Customs Organization maintains the Harmonized System framework; the applicable classification still requires the exact item and importing-country review.

How should the international schedule be built?

Separate the schedule into input clarification, drawing/submittal approval, any required sample or first-article review, production and inspection, export booking, and customs plus final delivery. Record the owner, entry condition and target date for each phase. A single factory lead-time number does not include every approval or logistics dependency and should not be used as an unconditional project completion date.

International inquiry checkpoint: Send the destination, named delivery place, required-on-site date, approval milestones, route conditions, packaging constraints and required document list with the technical evidence pack. Ask the supplier to return unsupported items and schedule dependencies before commercial release.

Hold the quotation or order when jurisdiction, exact product scope, route exposure, required records, packaging or delivery responsibility remains unresolved. Do not convert a regional assumption into a certification, compliance or delivery claim.

O-DU/O-RU fiber link FAQ

Does O-RAN require an MPO connector between O-DU and O-RU?

No. O-RAN defines the open-fronthaul interface scope. The equipment and physical-path design determine the connector. MPO is one optional aggregation interface.

Does eCPRI define the optical transceiver?

eCPRI does not prescribe one optical module for every deployment. Use the approved equipment and transceiver documents for rate, wavelength, reach class, connector and optical limits.

Where can MPO fit in an O-DU to O-RU fiber link?

It may fit between protected distribution points or in a controlled cross-connect when several approved fiber paths share the route. The endpoints and full fiber map must still be documented.

When should MPO be excluded from a fronthaul link?

Exclude it when it adds no useful aggregation, an endpoint expects another interface, the placement is exposed without evidence, or the fiber map and polarity cannot be approved.

Is a physically mateable connector proof of compatibility?

No. Physical mating does not prove host approval, wavelength pairing, optical power, lane mapping, protocol operation or environmental qualification.

How does fronthaul delay relate to fiber distance?

Fiber propagation contributes to delay, and switches or other transport elements may add more. Use the approved delay class and allocation instead of converting a generic distance into a pass result.

Who owns synchronization approval for an O-DU/O-RU link?

The project must name the RAN and transport synchronization authority. A cable supplier can provide physical-path information but cannot approve clock roles, topology or performance limits.

Can an Ethernet switch or WDM system sit between O-DU and O-RU?

Only when the approved architecture supports the topology and its delay, synchronization, protection, management and optical implications are included in the design.

When does an outdoor radio link need a hardened connector?

The exposed boundary and device interface decide this. The phrase "outdoor radio" alone does not justify a hardened connector or IP code.

Which document wins when the RFQ and equipment manual conflict?

Pause the BOM. Record the discrepancy, document revisions and affected fields, then send the issue to the designated design authority.

What should stop a fronthaul cable BOM from being released?

An uncontrolled architecture, unresolved endpoint/optic, open delay/sync/loss budget, undefined exposed boundary or unreconciled supplier drawing should each trigger a hold.

What belongs in an O-DU/O-RU link evidence pack?

Include the architecture and profile revision, endpoints and ports, paired optics, transport and synchronization approvals, route and passive-path drawing, three budget records, environmental boundaries, proposed cabling drawing, deviations and acceptance-document requirements.

Continue with the page that owns the next task:

For broad radio-site fiber context, read the FTTA solution overview.
For a listed FTTA or CPRI assembly, start with the current BWNFiber product catalog. Verify the item, page status, product revision and evidence before specifying it.
For connector and assembly terminology, use the MPO cable types guide.
For trunk sizing and passive loss work, use the MPO trunk cable design guide.
For lane and polarity mapping, use the MPO polarity checklist.
For measurement, pulling and receipt acceptance, use the pre-terminated MPO deployment guide.
After route conditions are approved, use the fiber optic cable overview for the relevant construction family; do not infer a finished cable from the fiber category.
After the upstream evidence pack is approved, use the pre-terminated fiber cable intake linked above to submit the finished assembly requirements.

Submit an O-DU/O-RU link evidence pack

Before asking BWNFiber or another physical-layer supplier to recommend an assembly, send one evidence pack containing:

the project country or region, contract authority and contract-invoked standards or codes;
the architecture/split/profile and applicable revisions;
O-DU/O-RU and transport-equipment models, ports and approved optics;
transport-delay and synchronization approvals;
route drawing, passive-component order and optical-loss calculation;
exposed boundaries and environmental/mechanical requirements;
required drawing, deviation, inspection/test and acceptance records.

Organize these fields in a revision-controlled O-DU/O-RU evidence-pack and RFQ worksheet. The worksheet is an intake aid, not a product datasheet or compatibility approval.

What should the supplier return?

A usable response should contain:

a proposed assembly drawing and fiber map;
a requirement and deviation matrix keyed to the submitted fields;
a source reference for each claimed characteristic;
a list of unresolved questions and the resulting BOM hold status.

Define acceptance evidence before quotation

Acceptance must match the contract and the actual path. For an installed single-mode passive cable plant, IEC 61280-4-2:2024 covers attenuation and optical return loss measurements. The project still has to state the method, wavelength, reference method, limits, required direction or directions, instrument identification and calibration status, and record format. OTDR can characterize the path and locate events; it does not replace an end-to-end attenuation measurement required by the acceptance plan.

IEC 61300-3-35:2022 covers visual inspection of fiber-optic connector and fiber-stub transceiver end faces. The standard states that visual inspection does not replace optical qualification such as attenuation and return-loss measurement. Record whether a requirement concerns installed-plant attenuation, component insertion loss, connector return loss or path optical return loss; these are related but not interchangeable terms. Request each result only where the interface, product specification or contract requires it.

Ask the supplier to mark missing inputs and proposed deviations before quoting a configuration. If BWNFiber reviews the pack, any proposed assembly still requires the current product datasheet, drawing, equipment approval and project acceptance records.

Compatibility, compliance, availability, MOQ, price and schedule depend on the selected item and must be confirmed in the project or quotation documents. This article makes no commitment for any of them.

Technical notice: This guide is for planning reference only. It does not approve an equipment pair or cable assembly. Final selection depends on current equipment and optics documents, product data, the approved drawing, contract terms and project acceptance records.

Official sources

Specifications and product documents are revision controlled. Confirm the editions invoked by the contract and equipment manufacturer before design release.

O-DU to O-RU Fiber Link Design: Where MPO Fits in 5G Fronthaul