Access through metro aggregation
Application decision brief
Telecom & ISP Optical Networks
Telecom optics are route-specific. Access speed, aggregation density, wavelength plan, fibre scarcity, link budget and field replacement policy must be frozen before quoting.
Budgeted route, not label-only
Channel and mux-loss control
An ISP bill of materials should separate customer access, aggregation, core, metro transport and protection paths. Each layer has a different failure impact, spare policy and acceptable optical margin.
Long-reach selection requires the real route: fibre attenuation, connector and splice count, patch panels, mux insertion loss and receiver limits. A nominal 40 km or 80 km label is not a route approval.
For wavelength expansion, the passive CWDM/DWDM plan and transceiver channel identity must be released as one controlled system.
01 / Architecture
Translate the network requirement into an optical path
Map service layer, route budget and restoration requirement before selecting reach or wavelength.
| Network requirement | Recommended design path | Confirm before approval |
|---|---|---|
| Access uplink | 1G/10G LX/LR or BiDi where fibre count and host support justify it. | Host, pair direction, connector and route loss. |
| Aggregation | 25G LR/ER or 100G LR4 selected by capacity and route. | Traffic growth, FEC, margin and spare policy. |
| Metro long reach | 10G ER/ZR or 25G ER after engineered link budget. | Attenuation, splices, receiver power and dispersion. |
| Wavelength expansion | CWDM/DWDM mux plus channel-matched optics. | Channel grid, mux loss, monitoring and protection path. |
02 / Real catalogue anchors
Product examples for a controlled starting point
These live product pages anchor common access, aggregation, metro and wavelength paths.
Verified live product page10G SFP+ 1310nm LR 10km LC TransceiverAccess and metro-edge linksVerified live product page10G SFP+ 1550nm ER 40km LC TransceiverEngineered long-reach metro pathVerified live product page25G SFP28 ER 40km LC TransceiverHigher-capacity aggregation reachVerified live product page100G QSFP28 LR4 10km LC TransceiverCore and aggregation uplinkVerified live product page40-Channel DWDM Mux/Demux ModuleDense wavelength expansion
Catalogue examples define a starting configuration, not automatic proof for a different host, revision, reach or fibre plant.
03 / Deployment patterns
Where this application architecture is used
Treat each network layer as a separate acceptance and spare domain.
ISP access rings
1G/10G uplinks with field-replaceable spares and route records.
Aggregation refresh
25G/100G capacity uplift with named host and FEC validation.
Metro transport
Engineered ER/ZR routes with optical-margin monitoring.
Fibre-constrained expansion
CWDM/DWDM channels released with mux and channel identity.
04 / Validation
Sample, compatibility and release workflow
Telecom approval connects the host result to the measured route and restoration plan.
- 1
Freeze the service map
Record access, aggregation, core and protection roles.
- 2
Measure the route
Capture loss, splices, connectors, muxes and reserve margin.
- 3
Validate host and channel
Test recognition, DOM, FEC and correct wavelength identity.
- 4
Prove restoration
Confirm spare coding, replacement steps and protection switching.
- 5
Release the lot
Tie optical checks, labels and quantities to each route line.
05 / Commercial control
MOQ, lead time and pricing factors
Field impact, wavelength identity and route engineering shape telecom cost more than headline speed.
| Commercial item | What changes the outcome | Buyer action |
|---|---|---|
| MOQ | Many wavelengths and coding profiles fragment quantity. | Group demand by exact channel and host. |
| Lead time | Long-reach optics and WDM parts may have different availability. | State critical routes and approved alternates. |
| Price | Reach, wavelength, receiver class and monitoring affect cost. | Request route-specific line pricing. |
| Field spares | Restoration time depends on correctly coded, labelled stock. | Define spare ratio and storage location. |
06 / Evidence
Downloadable buyer evidence pack
Use the redacted templates to define what must be recorded for the exact quoted configuration.
07 / Risk control
Failure modes to remove before shipment
Distance-label procurement
A nominal reach without a measured budget can overload or starve the receiver.
Wrong WDM channel
Correct form factor with wrong wavelength can interrupt the service plan.
Uncontrolled spare
A spare with different coding or label may not restore the named host.
Mux loss omitted
Passive-component loss can remove the entire engineering margin.
08 / Buyer questions
Application-specific questions
Is 40 km reach enough for a 35 km route?
Not automatically. Calculate fibre, splice, connector and mux loss plus reserve margin and receiver limits.
Can BiDi reduce fibre use?
Yes, when the host supports the pair and TX/RX wavelength direction is controlled at both ends.
Should every WDM channel use the same spare policy?
No. Criticality, installed base and channel availability may require different spare quantities.
What should a telecom RFQ include?
Route map, measured loss, host/software, wavelength, rate, connector, protection role, quantity, spare plan and delivery target.
Controlled next step
Send the route and wavelength plan, not only the distance label.
MingApex will structure the access, aggregation, metro or WDM BOM around measured loss, named hosts, restoration priority and order-specific evidence.