Quick answer: A PON mobile backhaul splitter can belong in an approved PON-based or purpose-designed passive point-to-multipoint transport system. Do not insert one into a point-to-point fronthaul or Ethernet link simply because both ends use fiber. Approve the transport architecture first; then select and qualify its passive component.
Procurement summary: Start with the approved PON mobile-backhaul architecture, not a splitter ratio. If the architecture is open, close the six gates for service/interface, capacity/QoS, delay/timing, optical path, resilience/operations and controlled evidence. If it is approved, attach the current system revision, shortest and longest path records, port map, optical limits, host/interface requirements and acceptance plan to the component inquiry. The operator or system integrator owns system approval; the passive-component supplier reviews only the submitted configuration. BWNFiber uses that boundary to identify confirmed, open and out-of-scope fields without implying that a component quote certifies the mobile transport system.
Four release rules
- A passive power splitter belongs only in an approved PON or passive point-to-multipoint architecture.
- Split count affects optical branching and path loss; it does not assign a fixed bandwidth share to each site.
- Component, installed-plant and active-service acceptance records answer different questions and are not interchangeable.
- Compare supplier bids only after the design revision, candidate model, evidence scope, exceptions and substitution rules are aligned.
On this page
- 5G transport fit
- Device classification
- Six approval gates
- Change control
- Optical-path and acceptance evidence
- Supplier submittal and commercial release
- Destination annex
- Frequently asked questions
Can a Passive Optical Splitter Be Used in 5G Transport?
Classify the transport segment and the architecture carrying it before reviewing the passive component.
| Transport context | When a passive power splitter may belong | When to stop the component review |
|---|---|---|
| Fronthaul between radio and distributed functions | A purpose-designed PON or passive point-to-multipoint transport solution explicitly supports the selected functional split, interface and operator requirements | The approved design is point-to-point, or the active equipment and transport specification do not support PON/P2MP for that interface |
| Midhaul between distributed and central functions | The approved packet-service design is delivered over a supported PON/P2MP system with the required service treatment | The proposal is only “add a splitter to save fiber” and has no supported OLT/ONU, capacity, timing or recovery design |
| Backhaul from a cell site toward aggregation or core | A PON-based mobile-backhaul architecture has been approved and the cell-site endpoint is represented by a supported ONU or equivalent termination | The supplier is being asked to infer the network architecture from a splitter ratio or connector list |
| Monitoring path | A defined tap architecture has enough optical margin and the monitoring receiver, direction and wavelengths are specified | A tap is being used as though it were a traffic switch, packet replicator or protection controller |
The Broadband Forum's TR-331 Issue 2 provides an architecture and requirement framework for PON-based mobile backhaul. Its focus includes LTE and LTE-Advanced, so a current 5G project still needs the applicable RAN, transport and operator requirements. ITU-T G.9807.1 includes mobile backhaul among the applications for XGS-PON. Neither document turns a generic splitter into a system approval.
For fronthaul, the selected functional split and transport profile control the answer. O-RAN WG4 develops open-fronthaul, cooperative-transport and test specifications. ITU-T G.9804.1 includes higher-speed PON requirement areas for wireless transport and fronthaul. ETSI GS F5G 013 describes a high-speed passive point-to-multipoint aggregation use case for mobile xHaul and states that best-effort treatment is insufficient. These sources support architecture-specific review; they do not support adding a generic splitter to an existing point-to-point link.
If the project instead needs tower-side fiber assemblies, hardened connectors or cable construction, use the FTTA solution page. That is a different buyer task from approving a passive branch in the transport path.
Name the Optical Device Before Discussing 5G Fit
“Splitter” is often used loosely in meeting notes and supplier quotations. That shorthand can place the wrong device class in the BOM.
| Device class | Optical function | It does not do | Approval evidence |
|---|---|---|---|
| Passive power splitter | Divides optical power among predetermined ports without wavelength selection | Schedule traffic, identify a protocol or select a protection path | Port map, operating band, maximum path losses, uniformity/PDL where applicable, reflectance or return-loss convention, directivity, package and interfaces |
| WDM MUX/DEMUX or AWG/AWGR | Routes or combines named wavelength paths | Behave like a wavelength-non-selective equal power divider | Passbands, insertion loss, isolation, ripple, direction, port-wavelength map and temperature conditions |
| Tap coupler | Sends most power along a main path and a defined fraction to a tap path | Create an error-free packet copy or prove the monitoring receiver will work | Main/tap port assignment, coupling tolerance, both path losses, direction, wavelength range and receiver margin |
| Optical switch | Selects a path under active control | Remain a purely passive branching device | Switching logic, states, failover control, insertion loss, timing and system acceptance |
ITU-T G.671 separates wavelength-non-selective branching components, tap couplers, wavelength MUX/DEMUX devices and optical switches. Use the detailed coupler-versus-splitter equivalence guide when two supplier records use different names.
Two stop rules prevent most category errors:
- Do not insert a generic passive splitter into an approved point-to-point Ethernet or open-fronthaul circuit. That changes the optical path and does not create a supported point-to-multipoint service.
- Do not use a passive splitter or tap as the mechanism that selects a primary or backup route. Path selection belongs to the active system or an optical switch; any passive branch must still be budgeted as part of the path.
A Splitter Does Not Divide Bandwidth into Fixed Per-Site Shares
A passive power splitter divides optical power. It does not assign a fixed fraction of the PON line rate to each output.
XGS-PON operates at a nominal line rate of 10 Gbit/s in each direction, but that number is not a guaranteed rate for every ONU connected through the splitter. Traffic is handled by the active OLT/ONU system and its transmission-convergence, scheduling, service and quality-of-service mechanisms. See the current ITU-T G.9807.1 record.
If the project team first needs the OLT, ODN and ONU relationship, use the PON network primer and return here for the mobile-specific approval gates.
The calculation “line rate divided by split count equals each site's bandwidth” is therefore not a valid service commitment. A capacity model needs, at minimum:
- the mobile service profile and interface presented at each endpoint;
- downstream and upstream offered load, including peak and failure conditions;
- OLT and ONU capabilities and supported profiles;
- dynamic bandwidth allocation and QoS behavior;
- protocol overhead and any encapsulation or transport treatment;
- the number of simultaneously active endpoints, not just physical splitter ports;
- capacity reserved for timing, operations, residential or business services;
- protection and maintenance states that may concentrate traffic on fewer resources.
The split count still matters, but for two different reasons: it contributes to optical path loss and determines how many physical branches can be served. It is not, by itself, a bandwidth policy.
Use Six Gates Before Approving PON-Based Mobile Backhaul
Treat the following as a hold-point matrix. The passive-component RFQ should not begin until the system owner closes the first five gates and defines the evidence required at the sixth.
| Gate | Decision question | Minimum record | Hold condition |
|---|---|---|---|
| Service and interface | What exact transport service and endpoint interface must the PON carry? | RAN/transport segment, functional split where relevant, endpoint models, interface and governing operator requirement | “5G fiber” is the only system description |
| Capacity, QoS and DBA | Can the active PON system meet the load and service treatment under normal and failure states? | Traffic model, service profiles, DBA/QoS configuration assumptions and headroom rule | Capacity is derived only from line rate divided by split count |
| Delay, jitter and timing | Does the end-to-end design meet the applicable delay and synchronization budget? | Allocation by network segment, timing source, delivery method, boundary clocks or other functions, and acceptance method | A splitter datasheet is offered as timing evidence |
| Optical path | Do the shortest and longest paths pass at all required wavelengths and directions? | Path diagram, equipment optical limits, model-specific passive losses, connector/splice plan and engineering margin | Only a theoretical split value or typical category value is available |
| Resilience and operations | How are failures detected, isolated, switched and restored? | Protection architecture, alarm/OAM plan, ownership, maintenance access and recovery test | A passive branch is assumed to perform switching or fault isolation by itself |
| Controlled evidence | Which revision and test result authorizes release? | Approved design revision, model record, acceptance plan, deviation process and signatories | Marketing labels replace controlled documents |
Gate 1: Freeze the service and interface
Record whether the work package is backhaul, midhaul or fronthaul, and identify both active endpoints. If the design relies on PON, name the PON generation and the supported equipment profiles. If it relies on wavelength routing, state the wavelength plan and device class instead of writing “WDM splitter.”
Gate 2: Model capacity and service treatment
Use the operator's traffic assumptions and the active equipment's documented behavior. Check busy conditions and a credible failure state. If fixed and mobile services share the port, include both in the same model and define how one service is prevented from consuming the other's protected capacity.
Gate 3: Close delay and synchronization
Mobile transport can require frequency and time/phase delivery in addition to packet forwarding. TR-331 treats synchronization as a specific system requirement and discusses mechanisms including Synchronous Ethernet and Precision Time Protocol. The applicable method and error allocation depend on the mobile system; they cannot be copied from a generic 5G infographic.
Gate 4: Calculate every relevant optical path
Build at least the shortest credible path and the longest credible path. Repeat the check for relevant directions and wavelengths. Include every splitter stage, connector pair, splice, fiber section, coexistence or WDM device and other passive loss on that path. Use maximum limits from the controlled model record where the approval needs a worst-case result.
Use the current GPON splitter selection guide for the generic ratio, topology and ODN-budget workflow. Bring the completed budget back to this mobile review as a controlled project input.
Gate 5: Define resilience and operations
Write down who owns the OLT, ONU, outside plant, timing source and mobile service. Define alarms, test access, failure isolation, path switching and restoration. Shared infrastructure may save fiber while adding an operational boundary; the design is incomplete if nobody owns that boundary.
Gate 6: Bind evidence to the approved revision
The final system design, splitter model, drawing, port map, test plan and supplier deviation process should reference the same project revision. If the operator changes the functional split, endpoint, PON profile, service mix or protection design, reopen the affected gates before releasing the component order.
Reopen the Approval When a Controlled Input Changes
A passed review is valid only for its recorded inputs. Use this impact matrix instead of treating an earlier approval as a permanent property of the splitter.
| Changed input | Reopen these gates | Update before release |
|---|---|---|
| Transport segment, functional split or endpoint interface | Service/interface; capacity/QoS; delay/timing; resilience/operations | System design, endpoint references, traffic and timing acceptance basis |
| OLT, ONU, software release or service profile | Capacity/QoS; delay/timing; resilience/operations; controlled evidence | Supported-profile record, configuration assumptions, failure-state model and service test plan |
| Split ratio, splitter stage or port map | Optical path; resilience/operations; controlled evidence | Shortest/longest path budget, drawing, labels, model record and test scope |
| Wavelength plan or coexistence/WDM device | Service/interface; optical path; controlled evidence | Bands, directions, passbands or isolation where applicable, and every affected path |
| Route, connector plan, cable specification, enclosure or environment | Optical path; resilience/operations; controlled evidence | Route drawing, passive-loss allowances, physical interface, installation method and environmental evidence |
| Protection design, maintenance access or responsibility boundary | Capacity/QoS; delay/timing; resilience/operations; controlled evidence | Failure-state load, timing behavior, alarms, switching, restoration test and named owners |
| Candidate model, package or proposed substitution | Optical path; controlled evidence | Exact model limits, dimensioned drawing, traceability, sample/lot evidence and approved deviation |
The project owner decides whether a change is material. The supplier should identify affected component records, not silently carry an earlier match into a revised architecture.
Can Mobile Backhaul Share a PON with Fixed Services?
Yes, in a defined system architecture. TR-331 Issue 2 includes use cases in which mobile backhaul shares a PON port with residential and/or business services. That is evidence that convergence is a legitimate architecture, not evidence that every existing FTTH tree is ready for a mobile workload.
The splitter does not recognize which photons belong to mobile, business or residential traffic. The active system and operating model must provide the separation. Before approving shared infrastructure, record:
- which services share the OLT port and which endpoints terminate them;
- how capacity, priority and congestion behavior are controlled;
- how synchronization is delivered and accepted;
- which security and management domains apply;
- whether maintenance on the common ODN can affect multiple service classes;
- which protection and restoration targets apply to the mobile service;
- how a change to the residential take rate or service profile triggers capacity review.
A project may also choose a dedicated PON port or line card for mobile services while reusing ducts, cabinets or parts of the outside plant. “Converged” therefore needs a diagram, not a slogan.
Build the Mobile-Backhaul Optical Path Record
Once the system architecture passes, convert it into path-level component inputs. Do not begin with “1×32, SC/APC” and ask a supplier to infer the rest.
For each controlled path, record:
- service and active endpoint references;
- PON generation and optical class or the exact approved system limits;
- shortest and longest route variants;
- every passive stage crossed by that route;
- required wavelengths and directions;
- maximum splitter insertion loss for the candidate model and port path;
- connector, splice, fiber and coexistence-device allowances;
- minimum-loss or receiver-overload check where applicable;
- engineering and restoration margin policy;
- result, owner, evidence and revision date.
The record should show an unresolved field as open. It should not hide the gap inside a “standard loss” assumption. The current splitter product hub can help locate a product family after the optical and physical requirements are known; a family page is not the final model record.
Record the installed fiber specification and route construction as project inputs. The word “PON” does not select a fiber type, cable structure, jacket, bend radius, tensile or crush limit, or environmental protection. Those choices belong to the route design and its controlled cable specification.
Before release, reconcile the drawing revision, splitter port identifiers and field test reference points. An optical-budget worksheet is not installable evidence if technicians cannot match its paths and measurement endpoints to the drawing and labels.
Approved topology, open passive-component fields? Send the topology and shortest/longest path worksheet for a configuration review. The useful output is an identified candidate configuration, the current records available for it and a list of fields that remain open—not an assumption that the mobile system is approved. Submit the controlled path inputs to BWNFiber.
Separate Component, Installed-Plant and Active-Service Acceptance
Three evidence layers answer three different questions.
| Evidence layer | What it can establish | What it cannot establish alone |
|---|---|---|
| Component/model evidence | The identified splitter or passive device was built and measured against agreed optical and physical requirements | The installed route or live mobile service passes |
| Installed-plant evidence | The completed single-mode path meets the project's attenuation, optical-return-loss, continuity, polarity and identification requirements | The active system meets capacity, timing, packet-delay, recovery or service-SLA requirements |
| Active-service evidence | The configured end-to-end transport meets the operator's traffic, delay, timing, OAM, resilience and recovery criteria | Every unmeasured passive component or future configuration will behave the same |
IEC 61280-4-2:2024 applies to attenuation and optical-return-loss measurements of installed single-mode cabling; its principles can also be applied to plants containing splitters and passive wavelength-selective devices. The project still needs to define reference points, wavelengths, methods and acceptance limits. Active mobile-service acceptance belongs to the operator or system integrator's plan, not to that cabling measurement alone.
The installed-plant plan may call for an optical loss test set, OTDR or both. Record the selected method and reference points; “OTDR tested” without a method, limit and path identifier is not an acceptance result.
Request records for the named candidate—not the product category: Ask for the current model datasheet, dimensioned drawing and available test-record format tied to the proposed configuration and revision. If fit, labeling or acceptance risk remains, agree whether a configuration-matched sample is needed and how it will be evaluated. Request technical materials or discuss a sample. Document and sample availability remain model- and order-specific.
Hold Point Example: Multi-Site ONU Branch
When an EPC submittal places several cell-site ONUs behind one splitter, hold component pricing until the OLT/ONU profile, traffic and timing design, path-loss worksheet and recovery plan share an approved revision. Suppliers can then compare like-for-like splitter configurations, packages and evidence. This is a review example, not a claim about a BWNFiber deployment or performance result.
Turn the Approved Architecture into a Splitter Submittal
A mobile-backhaul splitter RFQ should use a short, work-package-specific handoff. Attach the approved system documents instead of copying their requirements into marketing prose.
| Handoff field | What the buyer supplies | What the splitter supplier returns |
|---|---|---|
| System reference | Approved PON generation, active endpoint references and system design revision | Confirmation of the input used for component matching; no system-performance approval |
| Topology and path | Splitter stage, effective path, port map and shortest/longest route identifiers | Candidate configuration and drawing tied to the stated topology |
| Optical limits | Required bands/wavelengths, directions, maximum path losses and other component parameters | Current model limits and test-record format at the agreed reference planes |
| Physical interface | Package, host enclosure, fiber/pigtail, connector, polish, labels and access constraints | Dimensioned build, interface schedule and unresolved fit questions |
| Environment | Host-location and installation requirements supplied by the project owner | Applicable product evidence or an explicit unsupported/alternative disposition |
| Acceptance and control | Sample or lot plan, records, traceability, deviation and substitution rules | Evidence list, sample proposal where useful, quotation exclusions and change-control response |
| Logistics and receipt | Destination, packing, handling, storage, site labeling and incoming-inspection requirements | Packing and marking proposal, quantity mapping and a process for damage, shortage or substitution discrepancies |
Do not assume one global submittal fits every region. Operator specifications, project language, labeling, material or flame requirements, environmental conditions and acceptance documents can differ. List the governing project requirements; the supplier should return either matching evidence or a clearly stated exception.
Compare Supplier Responses on Evidence, Not Adjectives
Use the same approved input pack for every bidder. A technically usable response should make comparison easier, not ask the buyer to accept an undefined claim such as “telecom grade” or “5G compatible.”
| Comparison point | Acceptable supplier response | Hold or reject signal |
|---|---|---|
| Input and revision | Names the topology, path limits and revision used | Quotes a ratio and connector without identifying the submitted design |
| Device class | Identifies a power splitter, tap, WDM device or switch by function | Uses the word “splitter” for unlike devices without a port/function map |
| Optical evidence | Returns exact-model limits and test reference planes for the affected paths | Supplies only typical category values or theoretical split loss |
| Physical and environmental fit | Returns a dimensioned build, interfaces and evidence or exceptions against the stated host conditions | Says “outdoor” or “carrier grade” without the applicable model record |
| Test and traceability | Defines sample/lot scope, records, identifiers and failed-result disposition | Provides an undated generic report that cannot be tied to the offered model or lot |
| Deviations and substitutions | Lists every exception and requires approval before change | Reserves an undefined right to substitute an “equivalent” component |
| System-claim discipline | Limits approval to the passive component and records open system questions | Claims the component alone guarantees capacity, timing, latency or protection |
| Delivery and receipt | Confirms packing, labeling, quantity mapping and discrepancy handling | Leaves site identification, shortages or damaged-item disposition unresolved |
Price comparison starts after these fields are aligned. A lower quotation based on a different revision, evidence scope or substitution rule is not a like-for-like bid.
After the architecture and path inputs are approved, use the fiber optic splitter product and configuration page for connector, packaging, labeling, quantity and quotation fields beyond this mobile work package.
Move from Technical Match to Commercial Release
A technically acceptable response is not yet an order. Keep the candidate configuration, documents, sample decision and quotation on one controlled baseline.
| Release stage | Buyer confirms or sends | Supplier returns | Proceed only when |
|---|---|---|---|
| Candidate configuration | Approved system revision, topology, path limits, physical interfaces and open exceptions | Named candidate configuration, revision and unresolved fields | No open field could change the device class, optical path, fit or acceptance basis |
| Documents and sample decision | Required datasheet, drawing, test-record format and the specific risk a sample would evaluate | Available current documents and, where justified, a configuration-matched sample proposal | Document scope matches the candidate; sample method, acceptance and disposition are agreed before it is treated as evidence |
| Comparable quotation | Same configuration revision, quantity, destination, required date, packing/labeling, evidence scope and commercial terms for every bidder | Dated price, lead-time basis, quotation validity, exclusions, deviations and substitution rule | The quotation can be compared without silently changing the technical or evidence scope |
| Order or project discussion | Approved configuration, accepted quotation, sample disposition where applicable and named change authority | Order acknowledgement or project response tied to the controlled revision and approved exceptions | Engineering, quality and procurement owners have closed their required holds under the buyer's process |
Lead time is not comparable until its starting event and dependencies are clear. Record whether the schedule begins after purchase-order acceptance, drawing approval, sample approval or another agreed milestone. If the request includes OEM/ODM labeling, custom packaging, bulk scheduling, split shipments, special reports or export documentation, treat each as a controlled option. Availability, price and schedule must be confirmed in the dated model- and order-specific response.
Ready for a document, sample or quotation discussion? Send the candidate configuration and revision, quantity, destination, required date, requested records and open deviations. BWNFiber's inquiry route accepts project details and requests for technical materials or quotation support; it does not establish document availability, sample terms, price or lead time until the exact request is reviewed. Send the commercial-release inputs.
Add a Destination Annex to the Mobile-Backhaul Submittal
For a cross-border order, add a destination annex to the same mobile work-package revision. Its purpose is not to create a regional product specification. It shows which local inputs can reopen the system, path, host-interface or commercial record.
| Destination-annex control | Mobile-backhaul reason | Regional prompts to verify—not assumptions | Release evidence |
|---|---|---|---|
| Approval authority and governing documents | The operator or integrator, not the splitter supplier, approves the mobile service and active-system outcome | For North American, European or Latin American work, name the country, operator/purchaser or utility specification and any applicable authority requirement; use the same rule for every destination | Document title, edition, clause, owner and approved system revision |
| Splitter-to-host boundary | Environmental suitability may depend on the complete indoor rack, outdoor closure or street-cabinet assembly, not a bare splitter label | For Middle Eastern, Southeast Asian or African sites, provide actual enclosure temperature, dust, UV, coastal, humidity, rain, flood, storage and access conditions only where relevant to that site | Candidate drawing, named host, applicable model evidence and explicit exceptions |
| Optical path and active profile | A destination or operator change can alter endpoint profiles, wavelength plans, path lengths, margins or restoration rules | Confirm the PON profile, endpoint references, shortest/longest paths and acceptance basis for the local operator; do not carry a budget from another market or network | Revised system reference, path worksheet, port map and acceptance plan |
| Language, labels and document register | Field identification and handover records must remain traceable to the approved paths and candidate revision | Request the actual language, unit, marking, declaration and import-document set; European, Latin American and Middle Eastern projects can differ within the same region | Supplier document index showing available, pending, unsupported and alternative items |
| Packing, storage and site access | Damage, lost labels or split deliveries can break path-to-component traceability before installation | Record remote-site access, port or inland handling, storage duration, spares and shipment grouping for the actual destination, including Southeast Asian, Latin American or African projects where applicable | Packing/marking proposal, quantity-to-path mapping, delivery basis and discrepancy process |
| Commercial schedule and options | A quoted lead time is meaningless if its starting event or custom scope changes | State quantity, destination, required date, schedule starting event, split shipments, OEM/ODM labels, special records and export packing for any market | Dated quotation with dependencies, exclusions, deviations and substitution rule |
The buyer should identify the applicable standard, edition, contract clause or operator specification. The supplier should map evidence to the named requirement or return an explicit exception. A region name, CE/CPR label, “tropical” claim or generic international certificate cannot replace that record.
If the unresolved requirement is cable construction, tensile/crush evidence or route approval rather than the passive splitter, move that question to the controlled cable specification; the armored-cable mechanical evidence guide explains that separate evidence task. This page keeps only the fields that can change the mobile system-to-splitter handoff.
Where BWNFiber Support Starts and Stops
BWNFiber's role in this workflow is narrow by design: review the passive splitter portion of a project against a submitted topology, path-loss requirement, package, fiber, interface and document request. The response should separate what is confirmed against the identified configuration, what remains open and what is unavailable or outside the component scope.
The working rule is simple: scope first, evidence second, system approval stays with the operator or integrator. Customization, OEM/ODM labeling, bulk scheduling, test-report scope, export documentation and delivery dates are not assumed capabilities in this guide. When the project requires them, list them in the inquiry and accept them only through a dated, configuration-specific response.
The operator, RAN vendor or system integrator remains responsible for approving the mobile architecture, active equipment, functional split, capacity model, delay and timing budget, security, resilience and live-service acceptance. A passive-component quotation must not be treated as approval of those system outcomes.
Start a controlled PON mobile backhaul splitter review: Send the approved PON generation, topology, shortest/longest path worksheet, splitter stage and port map, required optical limits, host environment, interfaces, quantity, destination and acceptance records. State whether the next decision requires model documents, a sample discussion or a dated quotation. BWNFiber can review the passive configuration and return confirmed, open and out-of-scope fields before commercial release. Submit the project inputs.
Frequently Asked Questions
Is a passive optical splitter used in every 5G fiber network?
No. It belongs only where the approved transport architecture uses passive power branching, such as a supported PON or passive P2MP design. Point-to-point, WDM and actively switched designs use different components and approval evidence.
Can XGS-PON be used for mobile backhaul?
XGS-PON is defined for mobile backhaul among other applications, but applicability is conditional. Confirm the active equipment, service profile, capacity, QoS, timing, optical path, resilience and operator acceptance plan before selecting the splitter.
Can PON carry 5G fronthaul?
Some purpose-designed standards and transport architectures address PON or passive P2MP for wireless fronthaul. That does not make a generic PON or splitter suitable for every functional split. Use the current RAN and transport specification for the selected endpoints.
Does a 1×32 splitter give each site one thirty-second of the line rate?
No. The ratio describes optical branching. The active PON system schedules traffic and applies service policies. Model capacity from endpoint demand, service profiles, overhead, DBA/QoS behavior and failure states.
Can mobile and residential services share one PON port?
They can in a defined converged architecture. Approve capacity isolation, synchronization, security, maintenance impact, protection and responsibility boundaries. The passive splitter does not provide those controls.
Is an AWG the same as a passive power splitter?
No. An AWG/AWGR routes wavelengths according to its port-wavelength behavior, while a conventional power splitter is wavelength-non-selective. Specify the device by function and obtain the relevant passband, isolation and path-loss evidence.
Can a tap coupler replace the distribution splitter?
Only if the approved design calls for that asymmetric power allocation and every path passes. A monitoring tap and an equal-distribution PON splitter solve different tasks; matching connector types does not make them equivalent.
Does a passive splitter provide protection switching?
No. It can be part of a protected architecture or provide a monitored branch, but active equipment or an optical switch performs path selection. Budget and test every passive path used by the protection design.
What should be tested before release?
Separate component/model inspection, installed-plant optical measurements and active-service acceptance. Define the reference points, wavelengths, methods, limits, sample scope, failed-result action and record owner for each layer.
What timing information is needed before a splitter is quoted?
Identify the timing source, delivery method, active nodes, end-to-end error allocation, failure-state requirement and acceptance method. A splitter ratio or loss value cannot establish synchronization performance.
Who approves a PON mobile-backhaul splitter design?
The operator or system integrator approves the transport architecture and active-service outcome. The passive-component supplier reviews the submitted splitter configuration and its available model evidence; a quotation does not transfer system responsibility.
What information should be sent for a mobile-backhaul splitter quote?
Send the approved system reference, topology, splitter stage and port map, path-loss limits, wavelengths and directions, package, host, fiber, connectors, environment, test records, quantity, destination and change-control rules.
Technical References
- Broadband Forum TR-331 Issue 2: Architecture and Technical Requirements for PON-Based Mobile Backhaul Networks
- ITU-T G.9807.1: 10-Gigabit-capable symmetric passive optical network
- ITU-T G.9804.1: Higher speed passive optical networks — Requirements
- ITU-T G.671: Transmission characteristics of optical components and subsystems
- IEC 61280-4-2:2024: Installed single-mode attenuation and optical-return-loss measurements
- ETSI GS F5G 013 V1.1.1: F5G Technology Landscape Release 2
- O-RAN WG4: Open Fronthaul Interface
Technical notice: This guide is a component-selection and evidence-planning aid for reference only, not a guarantee of project performance. It does not certify a mobile network, active PON system or splitter model. Use current operator requirements, standards, equipment documents and controlled product records for the exact project.
