ETSI GS F5G 040 V1.1.1 (2026-09)

• Abstract:

  DGS/F5G-0040

• Status: Not Published
• Technical Committee: F5G - Fifth Generation Fixed Network
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 11-Oct-2026
• Completion Date: 16-Sep-2026

GROUP SPECIFICATION
Fifth Generation Fixed Network (F5G);
Technical Requirements for FTTR Network Deployment
Disclaimer
The present document has been produced and approved by the Fifth Generation Fixed Network (F5G) ETSI Industry
Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS F5G 040 V1.1.1 (2026-09)

Reference
DGS/F5G-0040
Keywords
deployment, F5G, F5G Advanced, FTTR, QoE,
quality
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.

© ETSI 2026.
All rights reserved.
ETSI
3 ETSI GS F5G 040 V1.1.1 (2026-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Overview of FTTR Network Deployment Quality . . 8
4.1 FTTR Network Deployment Architecture . 8
4.2 Architecture of the Evaluation Indicator System . 9
5 Network Coverage Requirements . 10
5.1 Coverage Ratio Requirements . 10
5.2 Signal Coverage Strength Requirements . 11
6 Network Connection Requirements . 11
6.1 Network Access Requirements . 11
6.2 Networking Mode Requirements . 11
6.3 MFU/SFU Combination Requirements . 12
6.3.1 Optical Power Budget Requirements . 12
6.3.2 WLAN Protocol Requirements . 12
6.3.3 Roaming Protocol Requirements . 12
6.4 Network Configuration Requirements. 13
6.4.1 WAN Configuration Requirements . 13
6.4.2 VLAN Configuration Requirements . 14
6.4.3 WLAN Configuration Requirements . 15
6.4.3.1 Channel Allocation Requirements . 15
6.4.3.2 Roaming Configuration Requirements . 16
6.4.4 DHCP Configuration Requirements . 16
7 Network Performance Requirements . 17
7.1 Network Connectivity Requirements . 17
7.1.1 Physical Layer Connectivity Requirements . 17
7.1.2 Service Connectivity Requirements . 18
7.1.3 Management Channel Connectivity Requirements . 18
7.2 Network Rate Requirements. 18
7.2.1 PON Access Rate Requirements . 18 ®
7.2.2 Wi-Fi Rate Requirements . 18
7.2.2.1 Single Terminal Rate in Core Area . 18
7.2.2.2 Single Terminal Rate in Edge Area . 19
7.2.2.3 Multi-terminal Concurrent Rate . 19
7.3 Network Stability Requirements . 19
7.3.1 Network Latency Requirements . 19
7.3.1.1 In-Premises Network Latency Requirements . 19
7.3.1.2 End-to-End Network Latency Requirements . 19
7.3.2 Network Jitter Requirements . 19
7.3.2.1 In-Premises Network Jitter Requirements . 19
7.3.2.2 End-to-End Network Jitter Requirements . 19
7.3.3 Network Packet Loss Rate Requirements . 20
7.3.3.1 In-Premises Network packet loss rate Requirements . 20
ETSI
4 ETSI GS F5G 040 V1.1.1 (2026-09)
7.3.3.2 End-to-End Network packet loss rate Requirements . 20 ®
7.3.4 Wi-Fi Coverage Continuity Requirements . 20
7.4 Network Interference Requirements . 20
7.4.1 AP Interference Requirements . 20 ®
7.4.2 Wi-Fi Interference Requirements. 20
7.4.3 Electromagnetic Interference Requirements . 20
7.5 Roaming Requirements . 21
8 Service Experience Requirements . 21
9 Network Operations and Maintenance Requirements . 21
9.1 FTTR Management System Requirements . 21
9.1.1 Network Information Visualization Requirements . 21
9.1.2 Network Parameter Configuration Requirements . 22
9.1.3 Network Fault Diagnosis Requirements . 22
9.2 Installation and Maintenance APP Requirements . 24
9.3 User App Requirements . 25
9.4 FTTR Protection Requirements . 26
9.4.1 Dual-MFU Protection . 26
9.4.2 Single MFU Port-level Protection . 28
Annex A (informative): Reference for Wireless Signal Attenuation by Distance . 29
Annex B (informative): Reference for Wireless Signal Attenuation by Obstacles . 30
History . 31

ETSI
5 ETSI GS F5G 040 V1.1.1 (2026-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables (European Standard (EN), Technical Specification (TS),
Group Specification (GS) or ETSI Standard (ES)) may have been declared to ETSI. The declarations pertaining to these
essential IPRs, if any, are publicly available for ETSI members and non-members, and can be found in
ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association. ®
BLUETOOTH is a trademark registered and owned by Bluetooth SIG, Inc.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Fifth Generation Fixed
Network (F5G).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Fiber to the Room (FTTR) technology provides home users with a stable and high-speed network experience by directly ®
laying optical fibers to every room in a building or home, and by efficiently coordinating optical and Wi-Fi
technologies. However, during the large-scale deployment of FTTR, the complexity and the difficulty in
troubleshooting network faults often make it challenging to achieve the expected quality standards for FTTR network
deployment. As a result, users do not fully enjoy the convenience brought by high-quality FTTR networks in real-world
scenarios. They often face issues such as incomplete network coverage, substandard network speeds, severe network
interference, high latency, and insufficient operations and maintenance capabilities, which significantly affect user
experience. To significantly improve user experience and build truly high-quality FTTR networks, it is particularly
necessary to establish standards for the deployment quality of FTTR networks.

ETSI
6 ETSI GS F5G 040 V1.1.1 (2026-09)
1 Scope
The present document specifies the deployment requirements for building high-quality FTTR networks, covering
various aspects including FTTR network coverage requirements, network connection requirements, network
performance requirements, service experience requirements and network operations and maintenance requirements.
2 References
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 are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] Recommendation ITU-T G.9940: "High speed fibre-based in-premises transceivers - system
architecture".
[2] ETSI TS 103 933 (V1.1.1): "Access, Terminals, Transmission and Multiplexing (ATTM); Fibre
deployment for fibre-based in-premises networking".
[3] Recommendation ITU-T G.9941: "High speed fibre-based in-premises transceivers - physical
layer specification".
[4] IEEE Std 802.11™-2024: "IEEE Standard for Information Technology--Telecommunications and
Information Exchange between Systems Local and Metropolitan Area Networks--Specific
Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
NOTE: This standard incorporates previous amendments including IEEE Std 802.11ac™-2013, IEEE
Std 802.11ax™-2021, IEEE Std 802.11k™-2008, IEEE Std 802.11v™-2011, and IEEE
Std 802.11r™-2008. The consolidated standard IEEE 802.11™-2024 is the preferred reference.
® ®
[5] Wi-Fi Alliance: "Wi-Fi EasyMesh Specification".
[6] IEEE Std 802.1Q™-2022: "IEEE Standard for Local and Metropolitan Area Networks--Bridges
and Bridged Networks".
[7] Recommendation ITU-T G.9949: "Wireless local area network management control interface
(WMCI) for in-premises networks".
[8] BBF TR-069: "CPE WAN Management Protocol".
[9] IETF RFC 2681: "A Round-trip Delay Metric for IPPM". G. Almes, S. Kalidindi, M. Zekauskas.
September 1999.
[10] IETF RFC 3393: "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)".
C. Demichelis, P. Chimento. November 2002.
ETSI
7 ETSI GS F5G 040 V1.1.1 (2026-09)
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 included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
Not applicable.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
installation and maintenance APP: application used by professional installation and maintenance personnel for FTTR
network deployment, commissioning, testing and acceptance
primary splitting point: first splitter in the FTTR ODN network located the MFU that splits the optical signal from
upper-level network (PON/OLT) to secondary splitter or directly connecting to a limited number (2 - 8 SFUs) of remote
terminals.
secondary splitting point: subsequent splitter following after the Primary Splitting Point
NOTE: The secondary splitting point distributes the optical signal to terminals or rooms within a smaller scope.
service serve: remote server providing the service the user is accessing
NOTE: Examples of services include web browsing, gaming, video streaming, cloud applications.
user APP: application used by FTTR subscribers for self-service management of their home network ®
NOTE: Typical functions include network status viewing, basic Wi-Fi configuration, one-click fault diagnosis.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
th ®
5G 5 Generation, 5GHz Wi-Fi band
ACK Acknowledgment
AP Access Point
APP Application
ATTM Access, Terminals, Transmission and Multiplexing
BSS Basic Service Set
CPU Central Processing Unit
DFS Dynamic Frequency Selection
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
DSCP Differentiated Services Code Point
E2E End-to-End
ETSI
8 ETSI GS F5G 040 V1.1.1 (2026-09)
FQDN Fully Qualified Domain Name
FTTH Fibre-To-The-Home
FTTR Fibre-To-The-Room
GE Gigabit Ethernet
GO-GC Group Owner - Group Client
GPON Gigabit-capable Passive Optical Network
HD High Definition
ID Identifier
IEEE Institute of Electrical and Electronics Engineers
IFDN In-premises Fibre Distribution Network
IoT Internet of Things
IP Internet Protocol
IPDV IP Packet Delay Variation
IPTV Internal Protocol TeleVision
LAN Local Area Network
MAC Media Access Control
MFU Main FTTR Unit
O&M Operations and Maintenance
ODN Optical Distribution Network
OLT Optical Line Termination
P2MP Point to Multipoint
PAD Personal Access Device
PC Personal Computer
PCP Priority Code Point
PON Passive Optical Network
QoS Quality of Service
RSSI Received Signal Strength Indication
RTT Round-Trip Time
SFU Sub FTTR Unit
SME Small and Medium Enterprise
SN Serial Number
SNR Signal-to-Noise Ration
SSID Service Set IDentification
STA Station
STB Set Top Box
TR Technical Report
VLAN Virtual Local Area Network
VoIP Voice over Internet Protocol
VR Virtual Reality
WAN Wide Area Network
WLAN Wireless Local Area Network
WMCI WLAN Management Control Interface
4 Overview of FTTR Network Deployment Quality
4.1 FTTR Network Deployment Architecture
Based on the G.fin reference model defined in Recommendation ITU-T G.9940 [1], and adapted according to the actual
deployment scenario. The FTTR network deployment architecture is achieved through the MFU, SFU, the indoor fibre
distribution network, the FTTR management system, the Installation and Maintenance APP, and the User APP. The
specific architecture is shown in Figure 1.
NOTE: APP denotes applications installed on off-the-shelve mobile terminals or computers.
ETSI
9 ETSI GS F5G 040 V1.1.1 (2026-09)
FTTR extends fiber optics into every room within the home connected on Fibre-To-The-Home (FTTH), achieving full
fiber coverage of the internal home network. The MFU connects upstream to the PON port of the central office OLT
equipment and connects downstream to multiple SFU via optical splitters or optical-electrical composite cables. The
SFU extend to the user's required deployment areas based on the internal structure, providing wired and wireless ®
coverage for each area, achieving whole-home network coverage. User terminals access the network via Wi-Fi or
Ethernet to meet internet access needs.
The FTTR management system supports one-stop network management services for the FTTR network, enabling
visibility, manageability, and maintainability by collecting information such as MFU/SFU operational status, user
network configuration information, and network operational status. It supports FTTR network operational status
viewing, network quality monitoring, and network fault diagnosis capabilities.
The Installation and Maintenance APP supports FTTR service information display, network configuration parameter
distribution, network deployment quality acceptance, and network fault diagnosis capabilities, assisting installation and
maintenance personnel in efficient, standardized deployment, testing, and acceptance.
The User APP supports user network status viewing, network function configuration, and network fault diagnosis
functions, enabling FTTR users to perform self-service management and maintenance.

Figure 1: FTTR Network Deployment Architecture
4.2 Architecture of the Evaluation Indicator System
The FTTR networks deployment quality evaluation indicator system consists of five indicator classes: network
coverage, network connection, network performance, service experience, and network operations and maintenance. The
specific architecture is shown in Figure 2.
a) Network Coverage: The network coverage indicators focus on the core dimensions of coverage completeness ®
(such as the proportion of effective coverage throughout the house) and signal quality (such as the Wi-Fi
reception level in each area), aiming for a coverage goal of "no blind spots and strong signals". Ultimately, this
ensures that FTTR users enjoy a seamless connection experience of "full-house gigabit" without any
interruptions.
b) Network Connection: Network connection indicators include network access methods, networking modes,
FTTR devices coordination, and network configuration, ensuring the FTTR network has stable basic access
capabilities, efficient topology coordination mechanisms, and standardized parameter configuration levels,
supporting whole-home quality coverage and reliable service carrying.
ETSI
10 ETSI GS F5G 040 V1.1.1 (2026-09)
c) Network Performance: Network performance indicators include network accessibility performance, network
rate (the data transfer speed achieved over the network), network latency, network interference, network
stability, and seamless roaming, aiming to ensure the FTTR network achieves high-speed, high-reliability
connection, low-latency response, low-interference operations, and seamless roaming capabilities in all
scenarios.
d) Service Experience: Service experience indicators focus on the specific requirements of different types of
service for network bandwidth, latency, stability, and roaming, precisely measuring the user's actual perceived
service quality. The aim is to translate FTTR's "technical compliance" into the user's "experience compliance",
eliminating the cognitive gap where "deployment indicators are qualified but the user feels it is 'not good to
use'", ensuring users practically enjoy the real service value of "whole-home gigabit".
e) Network Operations and Maintenance: Network operations and maintenance indicators include the
functional requirements that the FTTR management system, Installation and Maintenance APP, User APP and
the FTTR system shall meet, ensuring the FTTR network achieves efficient deployment processes, stable
operational status, and timely fault repair, ultimately supporting high-quality operations and maintenance
throughout the network's entire lifecycle, guaranteeing users FTTR network experience.

Figure 2: Architecture of the Evaluation Indicator System
5 Network Coverage Requirements
5.1 Coverage Ratio Requirements
To ensure users obtain stable network connections at any location, including areas with elevation differences within
multi-story buildings, the building's network coverage shall meet the following requirements:
a) Single-story buildings: The effective coverage area of network signals shall reach 95 % or above of the
building's floor area.
b) Multi-story/complex-structure buildings (e.g. duplex residences, commercial buildings, underground garages,
etc.):
- Each single floor's area coverage rate shall reach 95 % or above (measured as a 2D area on each floor).
ETSI
11 ETSI GS F5G 040 V1.1.1 (2026-09)
- The overall volume coverage rate of the vertical space shall reach 95 % or above (measured as a 3d
volume coverage accounting for stairways, elevators and transitions between floors where the signal may
be challenged by multiple structural barriers).
NOTE: A network signal strength of ≥ -70 dBm is the benchmark value for determining qualified coverage.
5.2 Signal Coverage Strength Requirements
Based on the user's actual network usage needs, primary application scenarios, and usage habits, the FTTR network
coverage area is divided into core coverage areas and edge coverage areas. The signal coverage strength in different
areas shall follow the requirements:
a) Core Coverage Areas: In the main activity areas, where users frequently use the network, such as the living
room, master bedroom, and study area, the core coverage scenario signal strength shall be ≥ -65 dBm.
b) Edge Coverage Areas: In areas where users occasionally use the network or have relatively low usage
demands (e.g. less than 30 minutes per day of fewer than 3 times per week), such as balconies, bathrooms, and
corridors, the edge scenario signal strength shall be ≥ -70 dBm.
When designing the FTTR network deployment plan, the wireless signal attenuation of distance and obstructions are
referred to in Annex A and Annex B.
6 Network Connection Requirements
6.1 Network Access Requirements
The home's internal network shall be built as a full optical network system with the MFU as the core. The upstream port
of the MFU shall communicate with the public communication network's OLT through the entrance facility. The OLT
shall have at least 10G PON network ports to connect the MFU to ensure sufficient bandwidth and high-speed data
transmission capabilities. The user indoor network access method is shown in Figure 3.
10 GPON
10 GPON
MFU
OLT Optical Splitter
Figure 3: User Indoor Network Access Method
6.2 Networking Mode Requirements
According to the splitting architecture requirements of Recommendation ITU-T G.9940 [1] and topology of FTTR
system requirements of ETSI TS 103 933 [2], FTTR networks shall adopt the Point-to-Multi-Point (P2MP) networking
methods. The MFU connects to multiple SFU through one passive splitter (or cascaded extension splitters), with all
SFU sharing the backbone fiber bandwidth. Deploying this solution requires meeting strict optical power budget
requirements and reasonably planning the split ratio and splitter location. Its architecture is divided into two types:
a) Single Splitter Architecture: One splitter is centrally placed, with a simple structure that is easy to maintain. It
is suitable for scenarios with concentrated area and a moderate number of Access Points (SFUs) (typically 4 -
8 SFUs within a single floor layout), as shown in Figure 4.
b) Multiple Splitter Cascaded Architecture: Coverage is extended through optical splitter cascading, which
flexibly adapt to complex layouts like duplexes and multi-story homes, but requires higher planning for link
loss, as shown in Figure 5.
ETSI
12 ETSI GS F5G 040 V1.1.1 (2026-09)
SFU
1：n Optical cable / Optical-electrical hybrid cable
MFU
Optical splitter
SFU
Figure 4: Single Splitter Architecture
SFU
SFU
1：n
Optical cable / Optical-electrical hybrid cable
1：n Optical cable / Optical-electrical hybrid cable
MFU
SFU
SFU
Optical splitter
Optical splitter
Figure 5: Cascaded Architecture of Multiple Optical Splitters
6.3 MFU/SFU Combination Requirements
6.3.1 Optical Power Budget Requirements
In accordance with the optical interface parameter requirements specified in Recommendation ITU-T G.9941 [3], the
MFU and SFUs in an FTTR network shall be selected with matching IFDN classes (e.g. Ra or Rb). This ensures that the
received optical power at each SFU stays within the specified sensitivity and overload limits.
To guarantee stable and reliable optical links during deployment, the total loss of the entire optical path shall be
accurately estimated based on fiber distance, the number of connectors, and the insertion loss of the splitter in P2MP
topologies.
In exceptional cases, like scenarios with FTTR device upgrades, mixed use, or deployment in complex layouts
(e.g. multi-level splitting), if the classes are not perfectly matched, engineering methods such as adding fixed optical
attenuators, changing the split ratio, or adjusting splitter configurations shall be used for adaptation and calibration to
avoid operational risks and ensure long-term network stability and reliability. These cases are operationally complex
and therefore are not recommended.
6.3.2 WLAN Protocol Requirements
The deployment environment might involve mixed networking of FTTR devices. This might be the case when the
devices are either from different brands, they are from the same brand but different generations, or when the user's ®
existing network contains routers or other network access terminals. To ensure Wi-Fi signal compatibility and
maximize overall network performance, all networking devices within an FTTR network deployment that transmit ®
wireless signals shall support the same Wi-Fi protocol generation [4] or be downward compatible. This means that the
protocol generation chosen for the FTTR network shall be the generation supported by all devices in the network.
6.3.3 Roaming Protocol Requirements
To ensure users obtain a continuous, stable, high-quality wireless network experience during movement, optimize
overall wireless network resource utilization, and enhance overall system capacity, in FTTR mixed networking
environments, all access point (Aps) shall meet the following roaming protocol requirements:
a) Basic Protocol Level: All APs accessing the FTTR network, including MFU, SFU and pre-existing routers on
the user side, shall support and enable the following IEEE 802.11™ [4] protocol enhancements:
- Radio Resource Measurement of Wireless LANs;
ETSI
13 ETSI GS F5G 040 V1.1.1 (2026-09)
- Wireless Network Management;
- Fast BSS Transition.
b) Networking Coordination Level: On the premise of meeting basic protocol requirements, all APs connected to
the FTTR network shall support the same Mesh networking protocol to achieve centralized management and
real-time information synchronization between the MFU and SFUs.
® ®
EXAMPLE 1: Mesh networking protocols could be the Wi-Fi EasyMesh™ [5] defined by the Wi-Fi Alliance,
or a proprietary Mesh protocol.
c) Packet Loss Level: To ensure service continuity during roaming handovers, the FTTR network shall support
zero-packet-loss roaming.
EXAMPLE 2: Example implementation options include:
- Dual-Link Roaming Mechanism: Utilizing dual-band or dual physical interfaces, this
approach establishes connections via two links in advance. During the handover phase, the
standby link maintains continuous data transmission.
- Single Physical Interface Roaming Mechanism: This approach establishes a Group Owner -
Group Client (GO-GC) communication link between the original AP and the STA. It
leverages this link to sustain data forwarding during the interval between the disconnection of
the primary link and the establishment of the new link, thereby preventing service
interruption.
- Roaming Protocol Enhancement: Optimizing signalling interactions and state synchronization
mechanisms to implement a "make-before-break" handover procedure, ensuring lossless
transition.
- Centralized Control and Real-Time Data Synchronization: A centralized controller
coordinates the STA context and data forwarding among multiple APs, enabling collaborative
roaming.
During FTTR network deployment, the protocol support status of all APs shall be audited and confirmed. During APs
selection, verification shall be conducted to confirm support for IEEE 802.11™ [4] protocol, Mesh protocol
compatibility, and the roaming packet loss mitigation protocol, prioritizing the deployment of a homogeneous system
network to minimize interoperability risks and ensure optimal performance.
For existing APs that do not meet the coordination requirements, it is recommended to isolate them by setting up
independent networks or adjusting them to bridge/client modes to prevent negative impacts on overall roaming
performance and network efficiency.
6.4 Network Configuration Requirements
6.4.1 WAN Configuration Requirements
In FTTR network deployment, the configuration of WAN connections serves as the foundation for ensuring normal
service provisioning, stable operation, and efficient management.
The configuration shall adhere to the principles of service isolation, differentiated policies, and security &
controllability. In accordance with the service templates or technical specifications provided by the operator, the
corresponding WAN connection parameters shall be configured on the FTTR MFU.
Each connection shall implement logical isolation and carry differentiated forwarding policies and security policies.
The following types and requirements of WAN connection configuration are as follows:
a) FTTR Management WAN:
Used for secure communication between the MFU and the operator's FTTR management system, it enables
remote automatic deployment, status monitoring, performance management, fault diagnosis and software
upgrade of the device.
ETSI
14 ETSI GS F5G 040 V1.1.1 (2026-09)
The FTTR management system server address (IP address or FQDN), authentication information and secure
transmission protocols shall be configured. The FTTR devices shall support queries and commands from the
specified management domain, while direct access from the Internet side shall be strictly prohibited.
b) Internet Access WAN:
Serves as the core access channel for broadband services, carrying all ordinary Internet data traffic of users.
Mandatory configuration:
- The corresponding encapsulation mode and authentication parameters shall be configured according to
the contracted bandwidth and service model.
Optional configuration:
- Multi-WAN Load Balancing: if multiple WAN connections are available - load balancing may be
enabled to distribute traffic across connections.
- Link Backup: if redundant WAN connections are available, link backup may be configured to provide
failover capability.
- Policy Routing: if traffic needs to be directed based on specific policies, policy routing functions may be
configured.
- Traffic Shaping and Connection Limits: traffic shaping, connection limits and default security policies
may be configured as needed to manage network resources.
c) Video Service WAN:
Used to carry the operator's IPTV video traffic. Multicast protocol parameters and high-priority QoS policies
shall be configured to ensure effective distribution of video streams within the home network and efficient
multicast forwarding in the FTTR system.
d) Voice Service WAN:
Used to carry VoIP traffic. A dedicated VoIP access connection shall be established, with the corresponding
voice VLAN, server address and authentication information configured. The highest-priority Differentiated
Services Code Point (DSCP) marking shall be enabled, and top-priority queue scheduling and forwarding
assurance shall be guaranteed across the entire network to minimize delay and jitter.
6.4.2 VLAN Configuration Requirements
During FTTR network deployment, VLAN division and priority configuration shall be implemented according to service
type, user type, physical ports and other factors. By isolating traffic of different services, network security shall be
enhanced and network management efficiency shall be optimized. Specific requirements are as follows:
a) Division by service: Independent service VLANs shall be assigned to different upstream services to implement
Layer 2 logical isolation of traffic. ®
b) On-demand intranet isolation: Different user VLANs shall be divided on the user side (LAN/Wi-Fi ) as
required.
EXAMPLE: For example, smart home devices and guest terminals are isolated from the main home network to
improve security. ®
c) Binding to ports and SSIDs: Each VLAN shall be bound to the corresponding physical port, Wi-Fi SSID or
specific SFU, ensuring that service traffic is accurately directed to target terminals.
d) QoS priority marking: In the 802.1Q [6] tag of a VLAN, the Priority Code Point (PCP) value shall be
configured according to service sensitivity, providing a foundation for end-to-end quality of service assurance.
e) Planning and synchronization: VLAN IDs shall be uniformly planned before deployment to avoid conflicts.
During configuration, VLAN information shall be synchronized across the entire network between the MFU
and SFU devices to ensure service continuity.
ETSI
15 ETSI GS F5G 040 V1.1.1 (2026-09)
6.4.3 WLAN Configuration Requirements
6.4.3.1 Channel Allocation Requirements
In an FTTR network, reasonable channel allocation and transmit power control shall be adopted to maximize system
capacity and user experience, so as to achieve minimized interference, load balancing and dynamic optimization of the
FTTR network. The specific requirements are as follows:
Requirements for Band-Specific Differentiated Configuration
• 2,4 GHz Band: Owing to the scarcity of available non-overlapping channels (usually only channels 1, 6 and
® ®
11) and high vulnerability to interference from non-Wi-Fi devices such as Bluetooth and microwave ovens,
the 2,4 GHz band features a crowded channel environment.
To realize effective interference avoidance and stable roaming, all SFUs shall operate on the same channel
...