Download - Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
1/134
1
2
3
M
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
2/134
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
3/134
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
4/134
4
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
5/134
. Development requirements
Four categories of requirements are established:
Mandatory (M): the device must support the characteristic in order to achieve Telefnica Group approval.
Highly Recommended (HR): it is highly desirable the device supports this characteristic. This degree ofcompliance can evolve to Mandatory in subsequent versions of the document. Supporting this characteristic
will be valued in the device commercial promotion.
Optional (O): it is left up to the manufacturer whether the device supports this characteristic or not.
Informative (I): manufacturer can enter a free text to provide information about the requirement/question.
. Functional classification
General
WAN Interfaces
LAN Interfaces
Core Functionality
Services
Management
Documentation
. Glossary
In the Scope of this document, the following definitions are applicable (only terms needing some clarification
are included):
3GPP: Third Generation Partnership Program
10 Base-T: Ethernet Local Area Network
AAL:ATM Adaptation Layer.
AC:Alternating Current.
ACCOMP: Address and Control field COMPression
ACS:Auto-Configuration Server.
ADSL: Asymmetric Digital Subscriber Line.
ADSLmn: Asymmetric Digital Subscriber Line multinorm.
AES: Advanced Encryption Standard
ALG: Application Level Gateway
AMR: Adaptive Multi-Rate
ANSI: American National Standards Institute
ATM: Asynchronous Transfer Mode.
ATU-C:ADSL Transceiver Unit, Central office end
ATU-R:ADSL Transceiver Unit, Remote terminal end.
BER: Bit Error Rate
BPS: Bits Per Second
BRAS: Broadband Remote Access Server
CCBS: Completion of Calls to Busy Subscribers
ain blocks are:
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
6/134
CCNR: Call Completion on No Reply
CDV: Cell Delay Variation
CHAP: Challenge Handshake Protocol.
CLIP: Calling Line Identification Presentation
CLIR: Calling Line Identification Restriction
CPE: Customer Premises Equipment
CRC: Cyclic redundancy check
dBrnc: dB over noise reference (-90dBm) according to C curve
DCF: Distributed Coordination Function
DHCP: Dynamic Host Configuration Protocol.
DMT: Discrete Multitone
DNS: Domain Name Service
DRA: Dynamic Rate Adaptation
DRR: Dynamic Rate Repartitioning
DSL: Digital Subscriber Line.
DSLAM: Digital Subscriber Line Access Multiplexer.
DSL Modem: Converts ATM cells to Ethernet packets and vice versa in the use of DSL
DSSS: Direct Sequence Spreading Spectrum
EAP: Extensible Authentication Protocol.
EDCA: Enhanced Distributed Channel Access
EIRP: Equivalent isotropically radiated power
EM: Eletro Magnetic
EOC: Embedded Operations Channel.
ETSI: European Telecommunications Standards Institute
FDM: Frequency Division Multiplexing
FEC: Forward Error Correction
FTP: File Transfer Protocol.
GFC: Generic Flow Control
GUI: Graphical User Interface.
HCF: Hybrid Coordination Function
HCCF: Hybrid Coordinator Function Controlled Channel Access
HTML: Hyper Text Mark Language.
HTTP: Hyper Text Transfer Language.
ICMP: Internet Control Message Protocol.
IEC: International Electrotechnical Commission.
IETF: Internet Engineering Task Force
INP: Impulsive Noise Protection
IP: Internet Protocol
IRC: Internet Relay Chat.
ISDN: Integrated Services Digital Network
ISO: International Organization for Standardization
ISP: Internet Service Provider.
ITU: International Telecommunication Union
KBPS: Kilobits per Second.
LAN: Local Area Network.
LED: Light Emitting Diode
MAC: Media Access Control
MBPS: Megabits Per Second
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
7/134
MDI: Medium Dependent Interface
MIC: Message Integrity Check
MIMO: Multiple Input and Multiple Output
NAPT: Network Address & Port Translation.
NAT: Network Address Translation.
NIC: Network Interface Card.
NTR: Network Timing Reference.
OAM: Operation, Administration and Management
OLR: OnLine Reconfiguration
OSI: Open System Interconnection.
PAP: Password Authentication Protocol.
PC: Personal Computer.
PAP: Password Authentication Protocol.
POST: Power On Self Test
POTS: Plain Old Telephone Service.
PPP: Point to Point Protocol.
PPPoA: PPP over ATM.
PPPoE: PPP over Ethernet.PSD: Power Spectral Density
PSK: Pre-Shared Key
PSTN: Public Switched Telephone Network
PT: Port Translation.
PVC: Permanent VC.
PvC: Polyvinyl Chloride.
PVP: Permanent Virtual Path.
QoS: Quality of Service
RFC: Request for Comments.
RFQ: Request for Quotation.
RPC: Remote Procedure Call.
RT: Real-time.
RTCP: RTP Control Protocol.
RTP: Real-Time Transport Protocol
RTSP: Real Time Streaming Protocol.
SIM: Subscriber Identity Module.
SDP: Session Description Protocol
SNR: Signal to Noise Ration
SOAP: Simple Object Access Protocol.
SoC: Statement of Compliance.
SRA: Seamless Rate Adaptation
SSID: Service Set Identifier
SVC: Switched VC.TBB Client: Telefonica Broad Band Client
TCM: Trellis Code Modulation.
TCP: Transmission Control Protocol.
TKIP: Temporal Key Integrity Protocol
TR: Technical Requirement.
TXOP: Transmit Opportunity
UDP: User Datagram Protocol.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
8/134
UNE: Una Norma Espaola
USB: Universal Serial Bus
VC: Virtual Connection
VoIP: Voice over IP
VP: Virtual Path.
WAN: Wide Area Network.
WECA: Wireless Ethernet Compatibility Alliance
WEP: Wired Equivalent Privacy
WiFi: Wireless Fidelity
WLAN: Wireless Local Area Network
WMM: WiFi MultiMedia
WPA: WiFi Protected Access.
WPS: Wi-Fi Protected Setup
. Operation Business Reference
In the Scope of this document, the following definitions are applicable for defining the Country of the
Telefonica Opetarion Business (OBs)
ColTel: Colombia
O2CR: Czech Republic
O2DE: Germany
TASA:Argentina
TCh: Chile
TdP: Peru
TE: Spain (Espaa)
Telesp: Brazil
TLATAM: Latin America (Argentina, Brazil, Chile, Colombia, Peru)
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
9/134
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
10/134
Cod Description
TR-GENRQQ General Requirements
TR-GENRQQ-MECDE Mechanical Design
TR-GENRQQ-MECDE-001The device shall be designed to allow vertical (wall mount) and horizontal mounting (desktop design). The casing must be
according to what will be decided by Telefonica
TR-GENRQQ-MECDE-002 Power supply size shall not block or obstruct the use of the adjacent plugs
TR-GENRQQ-MECDE-003 The device housing shall be white
TR-GENRQQ-MECDE-004 The plastic of the device will be ABS+PC
TR-GENRQQ-MECDE-005
The device should use sockets colour scheme as in TR-068:
Yellow (114c pantone) Ethernet ports
Black power connector
Gray (matte cool gray 3U) phone ports
TR-GENRQQ-MECDE-006 The device shall have an ON/OFF labelled power button
TR-GENRQQ-MECDE-007 The device shall have a reset button to restore default configuration. The button must be located at the back of the unit
TR-GENRQQ-MECDE-008
The device shall have a WPS button to activate the simplified configuration WPS method. This same button can be used
for turn on/off the WLAN functionality (the on/off WLAN functionality should be present only on the OBs that indicate the
request for this functionality)
TR-GENRQQ-POWSU Power Supply
TR-GENRQQ-POWSU-001
The device shall be designed for a local power supply AC mains: TE: 220-230V / 50Hz;
O2CR: 220-230V (+/-10%) / 50Hz (+/- 4%);
TLATAM(br): 90-240V (+/- 15%) / 60Hz (+/- 5%);
TLATAM(pe): 90-240V (+/- 10%) / 60Hz (+/- 5%);
TLATAM(ar;cl): 90-240V (+/- 10%) / 50Hz (+/- 5%)
O2 UK: 100-240V (+/- 10%) / 50Hz (+/- 5%)
TR-GENRQQ-POWSU-002 Device power input type: DC
TR-GENRQQ-POWSU-003 The device power adaptor can be external or internal
TR-GENRQQ-POWSU-004 The device power adapter shall be an automatic power switch
TR-GENRQQ-POWSU-005 The device power cord minimum length shall be 2 meters
TR-GENRQQ-POWSU-006 Power supply must be according to each conutry
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
11/134
Argentina
Brazil
Chile
Colombia
Peru
UK
Spain
TR-GENRQQ-POWSU-007 Power supply shall be labelled with device model and name
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
12/134
TR-GENRQQ-POWSU-008 In case of power interruption the device shall reboot automatically
TR-GENRQQ-POWSU-009 The device can not be powered via RJ11 interfaceTR-GENRQQ-POWSU-010 Power supply shall be according to EU RD 278/2009
TR-GENRQQ-POWSU-011
The device shall accomplish the European Union Code of Conduct on Energy Consumption of Broadband Equipment
Version 4 from 10 February 2011(Tier 2013-2014), supporting a maximum of 12V DC and 1,5A and a have a female
compatible connector:
- External diameter: 5,50,05mm
- Internal Diameter: 2,10,1mm
- Length: 9,00,1mm
TR-GENRQQ-POWSU-012 The Power supply must be in conformity with Telefonica specification for Universal Power supply as defined on thedocument ERQ.c1.0001 3rd edition / Jul 2011 (document in Spanish)
TR-GENRQQ-OPSTA Indication of Operating Status
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
13/134
TR-GENRQQ-OPSTA-001
In the frontal side of the equipment it has to be included the following LEDS
TR-GENRQQ-OPSTA-002 The frontal Led indicating the Ethernet functionality should be a single led for the four LAN pors
TR-GENRQQ-OPSTA-003 In the Back side of the device it may have indibidual Led for each of the Ethernet ports
TR-GENRQQ-OPSTA-004 A 2 Hz blinking Green-Red round of Broadband led should inform the firmware updating and flash memory writing
TR-GENRQQ-OPSTA-003 Additionaly to LED indicators the supplier may provide user software to monitor device activity
TR-GENRQQ-ELCHA Electrical characteristics
TR-GENRQQ-ELCHA-001
The device shall comply ETSI TS 102 913 V1.1.1 technical specification:
4.2 (insulation resistance between terminals)
4.3 (DSL channel input impedance)
4.4 (transitory response to call signal)
4.5 (DC response to call signal)
4.6 (voice channel longitudinal balance)
4.7 (insulation resistance between line terminals and ground)
4.8 (voice channel input impedance) sections
TR-GENRQQ-ELCHA-002
Noise level inserted by DSL channel into voice channel must comply:
- 18dBrnC maximum when voice channel is not being used
- less than 15 noise impulses with a maximum of 47dBrncO in 15 minutes during initiation and operation stages
- less than 15 noise impulses with a maximum of 65dBrncO (at 1.004Hz, -13dBm0) in 15 minutes during initiation and
operation stages.
TR-GENRQQ-ELCHA-003 The equipment will meet the established requirements in TS 202 913 V1.2.2 Recommendation in the applicable aspect.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
14/134
TR-GENRQQ-ELCHA-004DSL channel longitudinal balance: the device shall comply with the requirements of section 12.3.1 of ANSI T1.413-1998 and
section A.4.3 of ITU-T G.992.1
TR-GENRQQ-ELCHA-005DSL channel longitudinal balance must be higher than 40dB at [20 - 1.100]kHz when charging the DSL interface with
600ohm
TR-GENRQQ-ELCHA-006 DSL channel nominal impedance of 100ohm at DSL band in the PSTN interface
TR-GENRQQ-ELCHA-007 DSL channel return loss at 30Hz - 1.100kHz equal or higher to 10dB
TR-GENRQQ-ELCHA-008 Noise level inserted by the device to the DSL channel of the PSTN line shall be lower than -65dBmp
TR-GENRQQ-ELCHA-009
Error rate caused by cross-talk interference shall be better than 10e-7 for a minimum noise margin of 6dB (measured as
defined in paragraph 5.41: Measuring cross-talk noise margin of ETSI TS 388 V 1.3.1) taking into account the improvement
due to the error correction mechanism
TR-GENRQQ-ELCHA-010Errors due to impulsive noise at DSLAM interface shall be less than 0.14% error seconds (up to 15 impulses during 15min
and with 1sec between impulses) as defined in ANSI T1.413, section 11.2.2 and ITU-T G.996.1, section 8.
TR-GENRQQ-ELCHA-011 The analog ports shall perform according to ETSI ES 201 970 v1.1.1
TR-GENRQQ-ELCHA-012 Inband noise (psophometrically weighted) for narrowband audio (300Hz 3.4kHz) shall be less than 75.0 dBVp
TR-GENRQQ-ELCHA-013 Inband noise (psophometrically weighted) for wideband audio (50Hz - 7kHz) will be less than 75.0 dBVp
TR-GENRQQ-ELCHA-014Out-of-band noise (psophometrically weighted) for the human audible spectrum (30Hz - 20kHz) shall be less than 67.0
dBVp
TR-GENRQQ-ELCHA-015
Noise at mains frequency (50Hz) should not exceed 0.25 mV (psophometric weighed), this being the value at the line
terminals of the subscriber's set (when receiving). The subscriber's set assumed is only powered by the analogue line. (i.e.
half of the value in G.120 paragraph 6.1)
TR-GENRQQ-ELCHA-016 ALASS and other enhanced services as in 14.3 of ES 201 970 shall be supported
TR-GENRQQ-CLICO Climatic Conditions
TR-GENRQQ-CLICO-001
The device shall comply ETSI 300 019-1-1 to ETSI 300 019-1-8 standards:
- class 1.2 device for storage in non temperature-controlled environments
- class 2.3 for public transportation
- class 3.1 for operation in temperature-controlled environments (5-45C, 5-85% relative humidity, 880-1060mbar and a
solar radation of 700w/m2)
TR-GENRQQ-CLICO-002The device shall be ready to be installed in non temperature or humidity controlled indoor environments at 0-50C and 5-
95% relative humidity conditions
TR-GENRQQ-CLICO-003 Storage temperature [-25, 70]C
TR-GENRQQ-CLICO-004 Device electrical values shall be accomplished in the range [-10,60]C, humidity class F and after 2 hours (DIN 40046).
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
15/134
TR-GENRQQ-CLICO-005
The device shall correctly work in salted environments (coast areas) as defined on the UNE 20 502-2-3 (Eletrical
equipments and components), and shall be provide a certification of this functionality from result of tests on a third partlaboratory (as defined on ASTM-B117 Salt spray test.)
TR-GENRQQ-SECPR Security and Protect ion
TR-GENRQQ-SECPR-001 The device shall comply with the 73/23/CEE directive and the amendments to the 93/68/CEE directive
TR-GENRQQ-SECPR-002The device shall tolerate security level 3 ESD as in IEC 801, part 2, sections 7 and 8. It's not allowed any alteration over its
components due to contact or air discharges
TR-GENRQQ-SECPR-003Minimum resistance shall be 100Mohm when 100Vcc applied between cover and line contacts, cover and power wires and
contacts and power wires
TR-GENRQQ-SECPR-004
Test device manufacturer must supply beforehand the corresponding user safety certification and associated reports issued
by an accredited laboratory (EU directive 2006/95/CE compliance). Other norms applicable (technical normative):
- UNE EN 60950-1:2006+A11:2009
- EN 50371:2002
- EU Directive 99/05/CE
TR-GENRQQ-ELECO Electromagnetic Compatibility
TR-GENRQQ-ELECO-001The device shall comply with the 89/336/CEE directive and the amendments to the 93/68/CEE directive (reviewed if newer
directives)
TR-GENRQQ-ELECO-002 The device shall comply ETSI 300 127, EM 55022-Classe A
TR-GENRQQ-ELECO-003 No EM interferences between device and PSTN
TR-GENRQQ-ELECO-004The device and its power supply shall continue working in spite of: ESD (ElectroStatic
Discharges), EM radiations, RF transmitters presence and transitories/pulses or other variations in the power signal,
TR-GENRQQ-ELECO-005
WiFi interface shall comply with EN 300 328: Electromagnetic compatibility and Radio spectrum Matters (ERM) in
Wideband Transmission systems when data transmission equipment operate in the 2,4 GHz ISM band and uses spread
spectrum modulation techniques
- Part 1: Technical characteristics and test conditions- Part 2: Harmonized EN covering essential requirements under article 3.2 of the R&TTE Directive
TR-GENRQQ-ELECO-006
WiFi interface shall comply with EN 301 489: Electromagnetic compatibility and Radio spectrum Matters (ERM).
ElectroMagnetic Compatibility (EMC) standard for radio equipment and services.
- Part 1: Common technical requirements
- Part 17: Specific conditions for 2,4 GHz wideband transmission systems
TR-GENRQQ-OVERR Overvoltage and Overcurrent Resistibility
TR-GENRQQ-OVERR-001 The device shall comply with the requirements of ITU-T Recommendation K.21
TR-GENRQQ-OVERR-002Power supply shall resist (1000Vrms, 50/60Hz, 200mA current drain) for 30sec between phases and between each phase
and ground. After this test the isolated resistance of the power supply must be at least 200Mohm measured with 500Vcc
TR-GENRQQ-OVERR-003 The device shall have output overcurrent and overvoltage protection
TR-GENRQQ-OVERR-004 The device shall have a protection fuse
TR-GENRQQ-OVERR-005 The device shall have minimum resistance 1Mohm
TR-GENRQQ-OVERR-006On a case of Overvoltage and/or overcurrent, the device shouldn't lose the configurations and shall preserve the Firmware
Version unaffected
TR-GENRQQ-CONNE Connectors
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
16/134
TR-GENRQQ-CONNE-001
It shall be ensured good contact between the plug and socket plug elements (male and female conectors) and that thedegradation that occurs over time is not significant for the continuity of contact.
To ensure this behavior the gold coating thickness shall be of at least 1.27 m. (micrometers). in this case no further testingwill be needed.
If the thickness of gold coating is between 0.4 m and 1.27 m, willl be performed additional tests to verify the quality of theconnectors.
Under no circumstances accept lower coating thicknesses of 0.4 um of gold.
In the case of filter elements, microfilters, dividers etc ... the gold coating is always equal to or greater than 1.27 um.
TR-GENRQQ-CONNE-002 The device shall have a RJ11 female connector for the WAN interface and use its internal pair (3rd and 4th wires)
TR-GENRQQ-CONNE-003The device shall have 4xRJ45 female connectors for the LAN interface according the specification ANSI EIA TIA-568B (to
be used with UTP cat5 cables)
TR-GENRQQ-ENVRQ Environmental Requirements
TR-GENRQQ-ENVRQ-001The device shall have low environmental impact. So it shall be produced using materials: tagged for recycling, without CFC,without cadmium, solvent-free (water-based lacquers) with reusable packaging or failing foams without CFCs, biostables
and fuel, disposable in landfills or incinerators
TR-GENRQQ-FREEF Freefall
TR-GENRQQ-FREEF-001 The device shall be EM 60068-2-32 regulation compliant
TR-GENRQQ-PPCAS Production Process Control and Samples
TR-GENRQQ-PPCAS-001 The supplier shall provide the samples and means to perform quality tests
TR-GENRQQ-PPCAS-002Device sample for approval test shall be identified by producer name, model name, version, serial number, SW version,
chipset model and manufacturer and FW version
TR-GENRQQ-PPCAS-003
Telefonica inspectors can oversee device materials and production processes and
perform recalls if the product does not satisfy any requirement (recalls can becarried out also when the product has already been delivered). Production critical points shall be notified to Telefonica in
order to take actions if necessary and any SW/HW modifications shall be notified.
TR-GENRQQ-PPCAS-004The device shall have a life cycle (the supplier shall be able to ship devices during 24 months from the tender beginning) of:
- O2CR and TLATAM: 2 years
TR-GENRQQ-PPCAS-005
The device shall ensure a Mean Time Between (Hardware) Failure of:
- O2CR: 100 days
- O2DE and ColTel: at least 1 year
TR-GENRQQ-PPCAS-006 Faulty (total or partial) device rate = maximum 1 per 100 devices per year
TR-GENRQQ-PPCAS-007 The device manufacturer shall provide a TR069 Score Card
TR-GENRQQ-PPCAS-008
Certificate Requirements. The device manufacturer shall provide a TR069 Certification on RFATS date for each firmware
version of the device.
All mandatory TR-069 methods must be passed.The device must achieve 100% compliance for all profiles from the TR-098
datamodel requested in this document.
TR-GENRQQ-PPCAS-009
The device supplier shall perform Interoperability Tests (IOT) with the supplier of Auto-Configuration Server that the OB has
selected before shipment of the devices. The OB shall inform the device supplier in advance but the supplier may also
provide a list of the ACS systems on which IOT have been performed.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
17/134
TR-GENRQQ-PPCAS-010
The device manufacturer shall provide IEEE 802.11n WECA Certification (according to the last avaliable version) by WIFI
Alliance accredited test laboratory. A list of 3rd party Wifi devices and tested firmware version has to be provided by thedevice manufacturer
TR-GENRQ-POSTT Power On Self Test
TR-GENRQ-POSTT-001
During the boot process, the CPE will make a POST (Power On Self Test) about the following components at least: main
chipset, ADSL Chipset, chipset wifi, memory and switch ethernet.
If during this process, some bugs are detected and the CPE isn't going to be able to boot or isn't going to work properly, the
power led will light red, as says the technical specification TR-068, paragraph I-30 (Base Requirements for an ADSL
Modem with Routing).
If during this process,the FW isn't in the CPE or there is a FW error and the CPE isn't going to be able to boot, the power
led will blink red.
TR-GENRQQ-OTHER Others
TR-GENRQQ-OTHER-001 Non device status dependant phone serviceTR-GENRQQ-OTHER-002 The supplier must be cert ified or commit to a deadline for certification in local regulator of each country
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
18/134
Details and comments (English)
Fully Compliant (FC)
Partially Compliant (PC)
Non Compliant (NC)
Many designs can be presented to Telefonica
and discussed together to make the suitable
choice.
FC
FC
FC
ABS+HB is proposed. For ABS+PC, this will
be subject to a new quotationPC
FC
FC
FC
It can be implemented via 1 unique button or 2
specific buttonsFC
FC
FC
External power supply FC
AC input range:100 to 240 Vac automatic
switchFC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
19/134
FC
FC
FC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
20/134
FC
FCFC
FC
The output current in this power supply is
0,8A. When operating with our board at 12V,
9.6W is more than enough to properly power
the device.
Other parameters (noise level, maximum
overvoltage, cable caliber and inner connectordiameter) vary according to the developped
output power.
Longer and more agressive climatic cycles
have been passed.
For an optimum durability, a temperature
range between o and 45 is recommended
PC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
21/134
The delivered product has no 3G Led. The
Internet LED does not blink when traffic: only
steady green when 3G is up and off if 3G and
ADSL down. The behaviour of the other LEDs
is compliant with the requirements.
PC
FC
The LED can be found in the front panel rather
than in the back panel PC
FC
NC
The device comply with ETSI TS 202 913 FC
Tests to be performed. PC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
22/134
FC
FC
FC
FC
Tests to be performed. PC
FC
FC
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
TelefonicaIgnored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
Telefonica
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
Telefonica
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
Telefonica
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
Telefonica
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent byTelefonica
FC
FC
The Device meets storage conditions: ETS
300 019-1-1 Classe 1.1
Temperature: - 25C / + 55CTransport conditions: ETS 300 019-1-2 Classe
2.3
Temperature : - 40C / + 70C
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
23/134
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
Tests to be performed. PC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
24/134
thickness in the 0.8-1.5m range PC
FC
FC
ROHS/WEEE compatible FC
FC
FC
FC
Ignored. See "QA BHS Technical FinalCLARIFICATION SESSION.xls" sent by
Telefonica
Ignored. See "QA BHS Technical Final
CLARIFICATION SESSION.xls" sent by
Telefonica
FC
FC
FC
IOT tests can be performed with the ACS
selected by OB under the supervision of
Telefonica.The proposed product is Alcatel Motiv certified
FC
IOT tests can be performed with the ACS
selected by OB under the supervision of
Telefonica.
The proposed product is Alcatel Motiv certified
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
25/134
FC
FC
FCPlease refer to Annex sheet
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
26/134
Cod Description
TR-PHLRQ Physical Layer Requirements
TR-PHLRQ-WANTC Wan Access Technology
TR-PHLRQ-WANTC-001 The device shall interoperate with any supplier DSLAM
TR-PHLRQ-WANTC-002The device shall support a physical interface to connect, transmit and receive data from/to a DSL port that is compliant to
the recommendation [T-Com TR112 (U-R2)].
TR-PHLRQ-WANTC-003 The device shall have an ADSL over ISDN interface with 2B1Q modulation
TR-PHLRQ-WANTC-004 The device shall comply the standard ANSI T1.413: ADSL
TR-PHLRQ-WANTC-005 The device shall comply the standard G992.1 (G.DMT): ADSL transceivers using DMT modulation
TR-PHLRQ-WANTC-006 The device shall comply the standard G992.2 (G.Lite): ADSL Lite
TR-PHLRQ-WANTC-007 The device shall comply the standard G992.3: ADSL2
TR-PHLRQ-WANTC-008 The device shall comply the standard G.992.3 Annex L: Extended Range ADSL2
TR-PHLRQ-WANTC-009 The device shall comply the standard G.992.3 Annex M: Increased Upload Speed ADSL2
TR-PHLRQ-WANTC-010 The device shall comply the standard G992.5: ADSL2+
TR-PHLRQ-WANTC-011 The device shall comply the standard G.992.5 Annex L: Extended Range ADSL2+
TR-PHLRQ-WANTC-012 The device shall comply the standard G.992.5 Annex M: Increased Upload Speed ADSL2+
TR-PHLRQ-WANTC-013The DSL standard (ADSL/ADSL2/ADSL2+) to be used shall automatically negotiated between device and DSLAM.Higher
speed DSL standard has priority and it is also allowed to statically enable/disable the use of each DSL standard.
TR-PHLRQ-WANTC-014Transmitters reference model as in T1.413-4, G.992.1-5, G.992.2-4, G.992.3-5 and G.992.5-5 (depending on the standards
supported by the operator).
TR-PHLRQ-WANTC-015 The device shall support ATM data transport over DSL as in T1.413-5.2, G.992.1-6.2, G.992.2-5
TR-PHLRQ-WANTC-016
The device shall support ATM Transport Protocol Specific functionalities over DSL (ATM TPS-TC sublayer) as in ANSI
T1.413-7.2, G.992.1-8.2, G.992.2-7.1, G.992.3-6 and Annex K.2 (all parameters in K.2.7.i and K.2.10 can be configured)
and G.992.5-6 and Annex K (depending on the standards supported by the operator).
TR-PHLRQ-WANTC-017The transport model will mandatory be ATM according to the reference model of ANSI T1.413 section 4.2.2. of the
regulation. If STM mode is supported, it will be considered a value added, according to ANSI T1.413 section 4.2.1.
TR-PHLRQ-WANTC-018 If STM mode is supported, it will be considered as a value added to support all whats specified in ANSI T1.413 section 5.1
TR-PHLRQ-WANTC-019 The device shall operate in Simple Latency Mode (upload or download independent) as in T1.413-5.2, G.992.1-6.2, G.992.3and G.992.5 (depending on the standards supported by the operator)
TR-PHLRQ-WANTC-020The device should be able to operate in Dual Latency Mode (upload or download independent) as in T1.413-5.2, G.992.1-
6.2, and G.992.3 (depending on the standards supported by the operator)
TR-PHLRQ-WANTC-021The device shall support PTM Transport Protocol Specific Transmission Convergence functions over ADSL2 as in ITU
G.992.3, Section 6 and Annex K.3. All parameters in K.3.7.i and K.3.10 can be configured.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
27/134
TR-PHLRQ-WANTC-022The device shall support Physical Media Dependent function as in G.992.3-8 and G.992.5-8 (control parameters as in
G.992.3-8.5)
TR-PHLRQ-WANTC-023The device shall support Physical Media Specific Transmission Convergence function as in G.992.3-7 and G.992.5-7
(transport capabilities as in G.992.3-7.1 and control parameters as in G.992.3-7.5)
TR-PHLRQ-WANTC-024The device shall support Management Plane Procedures as in G.992.3, section 9 with the primitives described in G.992.3-
8.12.1, G.992.3-8.12.2 and G.997.1. The L0, L1 and L3 states are mandatory as well.
TR-PHLRQ-WANTC-025The Management Plane Procedure feature will be mandatory supported, according to whats described in G.992.5 section9.4
TR-PHLRQ-WANTC-026 The device shall support Power Management functionalities as in G.992.3, section 9.5
TR-PHLRQ-WANTC-027The Power Management feature will be completely supported according to whats described in G.992.3 section 9.5, 8.17and 10.3. This is, the three states described in the regulation (L0, L2 and L3) must be supported.
TR-PHLRQ-WANTC-028 The device shall support Programmed reduce framing overhead as in G.992.3TR-PHLRQ-WANTC-029 The device shall operate ensuring 10e-7 BER or better with a security noise margin
TR-PHLRQ-WANTC-030 The device shall support Fast and Interleaved transmission modes
TR-PHLRQ-WANTC-031 The device shall support Interleaved transmission mode providing protection against impulsive (INP) noise as in G.992.3,including Annex K.2.7
TR-PHLRQ-WANTC-032The device shall transport ATM data over DSL using frames with the format defined in T1.413-6.4, T1.413-7.4, G.992.1-7.4
and G.992.1-8.4. The Formats 0, 1, 2, 3 and for are mandatory as well
TR-PHLRQ-WANTC-033The device shall transport ATM data over ADSL2 using frame format defined in G.992.3-7.6 with programmed reduction of
overhead.
TR-PHLRQ-WANTC-034 The device shall transport ATM data over ADSL2+ using frame format defined in G.992.5-7.6
TR-PHLRQ-WANTC-035
The device shall accept NTR (Network Timing Reference) as in T1.413-6.3, T1.413-7.3, G.992.1-7.3, G.992.1-8.3, G.992.2-
7.2 and G.992.3-7.8 (depending on the DSL standard in use).The NTR sent by the DSLAM is reconstructed in the device as
in T1.413-5.2
TR-PHLRQ-WANTC-036The device shall use Scrambling for error protection as in T1.413-6.5, T1.413-7.5, G.992.1-7.5, G.992.1-8.5 and G.992.3-
7.7.1.3 (depending on the DSL standards supported)
TR-PHLRQ-WANTC-037 The device shall use CRC checksums to detect errors
TR-PHLRQ-WANTC-038The device shall support Forward Error Correction (FEC) as in T1.413-7.6, G.992.1-7.6, G.992.1-8.6, G.992.2, G.992.3,
G.992.5 (depending on the DSL standards supported)
TR-PHLRQ-WANTC-039 FEC R, S and D parameters of T1.413 Table 10, G.992.1 Table 7.7 and G.992.2 Table 5 parameteres must be supported.
TR-PHLRQ-WANTC-040 FEC Reed-Solomon coding support (with 3 words per symbol when G.992.5 is in use)
TR-PHLRQ-WANTC-041The device shall use Trellis Coding Modulation (TCM) as in G.992.1-7.8, G.992.1-8.8, T1.413-7.8 but being able to
interoperate with DSLAM with no Trellis Coding Modulation.
TR-PHLRQ-WANTC-042 The device shall support one-bit constellation encoding
TR-PHLRQ-WANTC-043The device shall use Constellation Encoding (no Trellis) with a maximum number of bits per carrier between 8 and 15 as in
T1.413-7.9, G.992.1-7.9 and G.992.1-8.9
TR-PHLRQ-WANTC-044The device shall perform Gain Scaling as in T1.413-6.10, T1.413-7.10, G.992.1-7.19 and G.992.1-8.10 (depending on the
DSL supported standards)
TR-PHLRQ-WANTC-045 The device shall use modulation as in T1.413-6.11, T1.413-7.11, G.992.1-7.11, G.992.1-8.11 and G.992.1 Annex A
TR-PHLRQ-WANTC-046The device shall use 1.1MHz bandwidth and 256 subcarriers for T1.413/G.992.1/G.992.3 and 2.2MHz and 512 subcarriers
for G.992.5TR-PHLRQ-WANTC-047 The device shall use subcarriers as in T1.413-6.7, T1.413-7.7, G.992.1-7.7, G.992.1-8.7 and G.992.1 Annex A
TR-PHLRQ-WANTC-048 The device shall perform Frequency Bands Separation using FDM
TR-PHLRQ-WANTC-049Besides FDM the device can use Echo Cancellation to perform Frenquency Bands Separation but only if FDM
interoperability is guaranteed
TR-PHLRQ-WANTC-050 The device shall use DMT modulation with 4,3125 kHz between subcarriers
TR-PHLRQ-WANTC-051 The device shall control subcarriers transmission spectrum
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
28/134
TR-PHLRQ-WANTC-052The device shall respect the frame structure "reduced overhead with merged fast and sync bytes" according to G.992.1 item
7.4.3.2 using interleaved buffer
TR-PHLRQ-WANTC-053The pilot carrier (276kHz) cannot be modulated or transport user data when using T1.413, G.992.1 or G.992.2 but it does
when using G.992.3
TR-PHLRQ-WANTC-054 The device shall use Cyclic Prefix as in T1.413-6.12, T1.413-7.12, G.992.1-7.2, G.992.1-8.2 and G.992.1
TR-PHLRQ-WANTC-055The device transmitter dynamic range shall comply T1.413-6.13, T1.413-7.13, G.992.1-7.13 and G.992.1-8.13 (depending
on the DSL supported standards)
TR-PHLRQ-WANTC-056The device transmitter spectral response shall comply T1.413-6.14, T1.413-7.14, G.992.1-7.14, G.992.1-8.14 and G.992.1
(depending on the DSL supported standards)
TR-PHLRQ-WANTC-057 The device transmitted power spectral density and aggregate power level shall comply ANSI T1.413-1998, section 7.15.
TR-PHLRQ-WANTC-058Device Initialization Sequence as in T1.413-9, G.992.1-10 and annexes. The R-QUIET2 parameter duration shall be
between 128 and 4000 and a maximum interleaving depth at least of 64.
TR-PHLRQ-WANTC-059 Device Initialization Sequence as in G.992.3-8.13, G.992.3, G.992.5 and transactions as in G.994.1-10
TR-PHLRQ-WANTC-060
Device Initialization Sequence details (all the sequence is controlled by the ISP):
- determination pilot tone location- fast start up as in G.992.3-8.14
- length control of the different satus in the boot process
- determination of the carriers used to transmit messages in the boot process
- disabling Tones voluntarily
TR-PHLRQ-WANTC-061 The device should support RETRAIN and RESYNC states as in G992.3 Annex D
TR-PHLRQ-WANTC-062 The device should support RETRAIN and RESYNC states as in T1.413 Annex A
TR-PHLRQ-WANTC-063EOC (Embedded Operation Channel) availability as in T1.413-8.1 and G.992.1-9.1 and requirements as in G.992.1-9.2
(depending on DSL supported standards).
TR-PHLRQ-WANTC-064The device must support Dying Gasp (device Loss Of Power announcement) using free EOC (Embedded Operation
Channel) and EOC message as defined in T1.413-8.1.5.4, G.992.1-9.2.5.4 and G.992.2-8.3.3.
TR-PHLRQ-WANTC-065 The device should support In-service performance monitoring and surveillance as in T1.413-8.2 and G.992.1-9.3
TR-PHLRQ-WANTC-066
The Device Should Support failure count parameters as in T1.413-8.2.4.3, line far-end failures detection as in T1.413-
8.2.5.2, atm far-end failures as in T1.413-8.2.7.2 and near-end performance monitoring functions as in T1.413-9.3
TR-PHLRQ-WANTC-067 Device Loop Diagnostics Mode supported as in G.992.3-8.12.4 and G.992.3-8.15. Autotest as in G.992.3-9.4.1.2
TR-PHLRQ-WANTC-068 Values reserved for signalling, OAM functions and resources management shall not be used for data transmission
TR-PHLRQ-WANTC-069The device shall be able to perform OLR (OnLine Reconfigurations) to ensure good operation when line or environment
conditions change as in T1.413-10 and G.992.1-11.
TR-PHLRQ-WANTC-070The device shall include OLR feature Bit Swapping to perform seamless re-allocation of bits between sub-carriers without
interrupting the data flow as in G.992.3-10.2.1
TR-PHLRQ-WANTC-071The device shall include OLR feature Dynamic Rate Repartitioning (DRR) to reallocate bandwidth between the fast and
interleave channels as in G.992.3-10.2.1 and G.992.5. This feature can be enabled/disabled by the ISP
TR-PHLRQ-WANTC-072
The device shall include OLR feature Seamless Rate Adaptation (SRA) to avoid dropping the connection changing the bit
rate to accommodate temporary line conditions in G.992.3-10.2.1 and G.992.5. This feature can be enabled/disabled by the
ISP
TR-PHLRQ-WANTC-073The device shall include OLR feature Dynamic Rate Adaptation (DRA) as in T1.413 Annex K and G.992.1 Annex G,
appendix II
TR-PHLRQ-WANTC-074 Operation bit rate can be fixed or adaptative
TR-PHLRQ-WANTC-075The device shall be able to set up both asymmetrical and symmetrical bit rate connections. Those bit rates must be
supported depending on the settings in the ADSL-LTs
TR-PHLRQ-WANTC-076 Operation bit rate depends on line characteristics so ATM data bit rate will be adapted in 32kbps steps.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
29/134
TR-PHLRQ-WANTC-077
The vendor must provide information about minimum and maximum upstream and downstream ATM bit rates:
- TE requires a minimum upstream bit rate of 800kbps and a minimum downstream bit rate of 8Mbps using ADSL ANSIT1413 and 1M/24M using ADSL2+ G992.5 Annex A.
- TLATAM requires a minimum upstream bit rate of 700kbps and a minimum downstream bit rate of 8000 kbps when using
ADSL (T1.413 or G.DMT), a minimum upstream bit rate of 600kbps and a minimum downstream bit rate of 1500 kbps when
using ADSL Lite (G.Lite), a minimum upstream bit rate of 900kbps and a minimum downstream bit rate of 12000 kbps when
using ADSL2 (G.992.3)and a minimum upstream bit rate of 900kbps and a minimum downstream bit rate of 22000 kbps
when using ADSL2+ (G.992.5)
- O2CR requires an upstream bit rate between 32 to 25000 kbps and a downstream bit rate between 32 and 8000 kbps.
TR-PHLRQ-WANTC-078 If the device needs a minimum link length larger than 0km the supplier shall report that value.
TR-PHLRQ-LANET LAN Ethernet
TR-PHLRQ-LANET-001The 8-pin interface mechanics shall comply with the requirements of section 3 of the IEEE 802.3 specification and will be
consistent with the figures of 1-5 ISO/IEC 8877: 1992
TR-PHLRQ-LANET-002The device shall have Fast Ethernet 802.3u 100baseTX interface (compatible with 10baseT, 100baseTX, 100baseT4 and
optionally with 1000baseTX) with bit rate autonegotiation
TR-PHLRQ-LANET-003 The device Ethernet 802.3 interface shall detect and operate in half/full duplex modes
TR-PHLRQ-LANET-004The device Ethernet 802.3 interface shall support Auto-MDI/MDI-X feature to detect the connection polarity (10baseT,
100baseTX or optionally 1000base-TX).
TR-PHLRQ-LANET-005 The residential gateway shall offer four Ethernet ports and be able to operate as a switch at Ethernet level.
TR-PHLRQ-WILAN WLAN
TR-PHLRQ-WILAN-001 The wireless interface can be enabled/disabled via software from the user interface and via hardware facility (button).
TR-PHLRQ-WILAN-002 The device WLAN Interface shall operate in Access Point / Infrastructure Mode
TR-PHLRQ-WILAN-003The router should support the wireless standard 802.11n 2.4GHz(2x2) in the last available version certified by the WIFi
Alliance. Troughput of WLAN to LAN shall be 100Mbps at last.
TR-PHLRQ-WILAN-004The device WLAN Interface shall ensure interoperability with IEEE 802.11b and IEEE 802.11g clients simultaneously with
IEEE 802.11n clients.
TR-PHLRQ-WILAN-005 The device WLAN Interface shall be able to operate at 2.4GHz frequency.
TR-PHLRQ-WILAN-006 The device WLAN Interface shall be able to apply IEEE 802.11n standard features at 2.4GHz frequency band.
TR-PHLRQ-WILAN-007
The device WLAN Interface shall operate over frequency channels in 2.4GHz band: from 1 (2412MHz) to 13 (2472MHz)
with 5MHz channel spacing. Defined for Europe in 802.11-2007, Wireless LAN Medium Access Control (MAC) and Physical
Layer (PHY) Specifications, Clause 15, Table 15-7
TR-PHLRQ-WILAN-008 The device WLAN Interface shall be able to operate using 20MHz channels in 2.4GHz band according to IEEE 802.11n
TR-PHLRQ-WILAN-009The device WLAN Interface may be able to operate using 40MHz bandwidth channels in 2.4GHz band according to IEEE
802.11n
TR-PHLRQ-WILAN-010 The device WLAN Interface may have DFS (Dynamic Frequency Selection) feature in 2.4GHz frequency band
TR-PHLRQ-WILAN-011The device WLAN Interface maximum transmitted power (EIRP) when using channels from 1 to 13 in 2.4GHz band must
not exceed 100mw in any combination of transmitter power output and supplied antennaTR-PHLRQ-WILAN-012 Power spectral density level shall comply with VO-R/12/08.2005-34 in operation bands (2.4GHz).
TR-PHLRQ-WILAN-013The device WLAN Interface transmitter power output may be configured via web-based user interface (supplier should
specify the range)
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
30/134
TR-PHLRQ-WILAN-014 The supplier shall specify receiver sensitivity at BER 10-6 in dBm for each frequency band and every single supported rate
TR-PHLRQ-WILAN-015
The device shall have at least 2 external antennas. The supplier shall also specify technical parameters of supplied
antennas (gain in dBi, radiation pattern envelope, frequency band). The antennas shall not be detachable (fixed mounted on
the BHS).
TR-PHLRQ-WILAN-016
It can be offered internal antennas to replace the external antennas requested on the requirement TR-PHLRQ-WILAN-015,
as long as the internal antennas presents no loss in coverage, confirmed by local tests with participation and approval of the
local OB..
TR-PHLRQ-WILAN-017The supplier shall specify the number of antennas included to the device. IEEE 802.11n requires a minimum of 2 antennas
to take advantage of MIMO features.
TR-PHLRQ-WILAN-018 The device WLAN Interface shall offer Multiple Input Multiple Output features (MIMO) to take advantage of IEEE 802.11nimprovements
TR-PHLRQ-WILAN-019The supplier shall specify what has been implemented in terms of MIMO (multiple input and multiple output) according to
IEEE 802.11n standard
TR-PHLRQ-WILAN-020 The supplier shall specify implemented MIMO chipset
TR-PHLRQ-WILAN-021The device WLAN Interface must be able to perform MIMO spatial multiplexing. At least two spatial streams shall be able to
be received/transmitted but IEEE 802.11n standard allows a maximum of four spatial streams.
TR-PHLRQ-WILAN-022 The supplier shall specify the multiplexing algorithm used in SDM (Spatial Div ision Multiplexing).
TR-PHLRQ-WILAN-023The supplier shall specify implemented kind of beamforming (single layer beamforming or multilayer beamforming with
precoding) to take advantage of antenna diversity. This feature is optional in IEEE 802.11n standard.
TR-PHLRQ-WILAN-024The supplier shall specify if the device may apply diversity coding techniques (space-time coding) to enhance signal
diversity.
TR-PHLRQ-WILAN-025 The device WLAN Interface can be configured to be used without encryptionTR-PHLRQ-WILAN-026 The device WLAN Interface shall support WEP security
TR-PHLRQ-WILAN-027 The device WLAN Interface can be configured to use 64bit key WEP encryption
TR-PHLRQ-WILAN-028 The device WLAN Interface can be configured to use 128bit key WEP encryption
TR-PHLRQ-WILAN-029 The device WLAN Interface using WEP security can use Open authentication
TR-PHLRQ-WILAN-030The device WLAN Interface using WEP security can use Shared Key authentication. This authentication method is less
secure than Open authentication.
TR-PHLRQ-WILAN-031 The WEP key of the WLAN Interface shall be entered in hexadecimal format
TR-PHLRQ-WILAN-032 The WEP key of the WLAN Interface may be entered in ASCII format
TR-PHLRQ-WILAN-033 The device shall support extended ASCII characters
TR-PHLRQ-WILAN-034 The device WLAN Interface shall support WPA security
TR-PHLRQ-WILAN-035 The device WLAN Interface shall support WPS security
TR-PHLRQ-WILAN-036 WPA user authentication can be performed via PSK (PreShared Key). Personal WPA mode.
TR-PHLRQ-WILAN-037 WPA user authentication can be performed via IEEE 802.1x protocol through EAP framework. Enterprise WPA mode.
TR-PHLRQ-WILAN-038WPA user authentication via EAP framework shall support the following methods: EAP-TLS, EAP-TTLS/MSCHAPv2,
PEAPv0/EAP-MSCHAPv2, PEAPv1/EAP-GTC and EAP-SIM as in IETF RFC4017
TR-PHLRQ-WILAN-039 The WPA security shall include RC4-based TKIP (Temporal Key Integrity Protocol) for encryption and rekeying
TR-PHLRQ-WILAN-040 The AES re-keying interval may be configured
TR-PHLRQ-WILAN-041 The TKIP re-keying interval may be configured
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
31/134
TR-PHLRQ-WILAN-042WPA security shall include MIC (Message Integrity Code) to avoid CRR (Cyclic Redundance Code) modifications by
attackers
TR-PHLRQ-WILAN-043 WPA security shall include Reply Attack Protection mechanisms
TR-PHLRQ-WILAN-044 WPA key of the WLAN Interface shall be entered in hexadecimal format
TR-PHLRQ-WILAN-045 WPA key of the WLAN Interface shall be entered in phrase format
TR-PHLRQ-WILAN-046 WPA key of the WLAN Interface must be random and it will be the same always
TR-PHLRQ-WILAN-047 The device WLAN Interface shall support IEEE 802.11i WPA2 security
TR-PHLRQ-WILAN-048 WPA2 security shall ensure interoperability with WPA clients
TR-PHLRQ-WILAN-049 WPA2 user authentication can be performed via PSK (PreShared Key). Personal WPA2 mode.
TR-PHLRQ-WILAN-050 WPA2 user authentication can be performed via IEEE 802.1x protocol through EAP framework. Enterprise WPA2 mode.
TR-PHLRQ-WILAN-051
WPA2 user authentication via EAP framework shall support the following methods: EAP-TLS, EAP-TTLS/MSCHAPv2,
PEAPv0/EAP-MSCHAPv2, PEAPv1/EAP-GTC and EAP-SIM as in IETF RFC4017. EAP peer and authenticator
authorization must be supported
TR-PHLRQ-WILAN-052The WPA2 security shall include AES-based CCMP (Counter Mode with Cipher Block Chaining Message Authentication
Code Protocol) for encryption and rekeying
TR-PHLRQ-WILAN-053WPA2 security shall include MIC (Message Integrity Code) to avoid CRR (Cyclic Redundance Code) modifications by
attackers
TR-PHLRQ-WILAN-054 WPA2 security shall include Reply Attack Protection mechanisms
TR-PHLRQ-WILAN-055 WPA2 key of the WLAN Interface shall be entered in hexadecimal format
TR-PHLRQ-WILAN-056 WPA2 key of the WLAN Interface shall be entered in phrase format
TR-PHLRQ-WILAN-057The WLAN Interface can be secured using MAC filter to control the access of certain MAC addresses to the wireless
network
TR-PHLRQ-WILAN-058The MAC filter shall be able to operate in whitelist mode (only the registered MAC addresses are allowed to access to the
wireless network)
TR-PHLRQ-WILAN-059The MAC filter shall be able to operate in blacklist mode (only the registered MAC addresses are not allowed to access to
the wireless network)
TR-PHLRQ-WILAN-060 The device shall support MAC addresses self-learning of wireless clients
TR-PHLRQ-WILAN-061 The supplier shall specify maximum number of MAC addresses registered in the access table
TR-PHLRQ-WILAN-062The SSIDs of the WLAN Interface must be WLAN_XXXX by defect, The SSIDs of the WLAN Interface must beWLAN_XXXX by defect, with "XXXX" the last bytes of MAC Ethernet (all characters of "WLAN_XXXX" must be on upper
case)
TR-PHLRQ-WILAN-063 The SSIDs of the WLAN Interface can be changed by the user.
TR-PHLRQ-WILAN-064 The device WLAN Interface can be configured to not broadcast the SSIDs (SSID hiding feature)
TR-PHLRQ-WILAN-065 The device WLAN Interface shall support Multiple SSID feature with a minumum of 4 SSIDs
TR-PHLRQ-WILAN-066When using Multiple SSID, different settings can be asigned to each SSID: encryption, hiding, enabled/disabled, mac
filtering
TR-PHLRQ-WILAN-067 The device WLAN Interface shall support IEEE 802.11e QoS features
TR-PHLRQ-WILAN-068 The device WLAN Interface shall comply Wifi MultiMedia (WMM) interoperability certification.
TR-PHLRQ-WILAN-069 The device WLAN Interface shall support Enhanced DCF Channel Access (EDCA) medium access control method +Transmit Opportunity (TXOP)
TR-PHLRQ-WILAN-070 The device WLAN Interface HCF Controlled Channel Access (HCCA) medium access control method is optional
TR-PHLRQ-WILAN-071 The device WLAN Interface shall support Automatic Power Save Delivery (APSD) or other similar mechanism
TR-PHLRQ-WILAN-072The device WLAN Interface may support Block Acknowledgments (BA) to reduce overhead when longer TXOPs are
specified
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
32/134
TR-PHLRQ-WILAN-073The device WLAN Interface may be able to send frames with No Acknowledgement (NoAck) service class to avoid
retransmission of highly time-critical data.
TR-PHLRQ-WILAN-074 WPS feature as user-friendly method to establish the WiFi configuration shall be provided in PBC (Push Button
Configuration) mode.
TR-PHLRQ-WILAN-075Each unit shall have a unique phrase format WPA key and a customized SSID (to allow the user to recognize its own WiFi
network) in its default configuration
TR-PHLRQ-WILAN-076 The device shall support Adaptive RF (automatic adjustment of signal power and WiFi channel / bandwidth)
TR-PHLRQ-WILAN-077 The device shall support Airtime Fairness functionality
TR-PHLRQ-WILAN-078 The antennas shall have a signal power of 3dBi
TR-PHLRQ-WILAN-079The Mac Address from the Ethernet interfaces and the Mac Address from the WLAN interface shall not be sequential from
one to another (LAN to WLAN) and shall have no correlation between each other
TR-PHLRQ-WILAN-080 The supplier shall provide the plans that is been implemented to avoid the vulnerability of the WPS functionality to BruteForce Attack attempts. To have a defined plan to avoid this vulnerability is mandatory.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
33/134
Details and comments (English)
Fully Compliant (FC)
Partially Compliant (PC)
Non Compliant (NC)
The product is designed to interoperate with
the DSL technologies DSLAMs
Broadcom solutions are the most widely
deployed in the industry. Interoperability has
been achieved with more than 40 different
DSLAMs manufacturers and more than 100
different line cards and firmware versions.
Tests to be performed.
FC
FC
Different Hardware FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
PC
NC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
34/134
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
35/134
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
To be developped upon request. No hardware
limitationsPC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
36/134
25000 kbps Upstream bitrate is not supported.
We suspect a Typo there.FC
Not required FC
FC
FC
FC
The device is compatible with 10baseT and
100baseTX onlyFC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
Possibility to choose the channel via the web
user interfaceNC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
37/134
According to the Wi-fi IEEE802.11n standard
requiremens, the sensitivity test results aredescribed in this document. Please refer to
sheet "TR-PHLRQ-WILAN-014"
FC
Precise spec to be provided later and agreed
with TEF.
we can use two internal antennas, and the
performance is same as external anternnas.
NC
we can use two internal antennas, and the
performance is same as external anternnas.FC
2x2 FC
FC
FC
FC
2x2 FC
As described in 802.11n standard FC
FC
FC
FCFC
FC
FC
FC
FC
FC
FC
NC
FC
FC
FC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
38/134
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
32 FC
FC
FC
FC
The device supports Multiple SSID feature with
a maximum of 2 SSIDs. To reach 4 SSIDs a
development is necessary. This request must
be discussed together with Telefonica.
PC
FC
FC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
39/134
FC
FC
This information is available on a label sticked
to the device with the corresponding
information.
FC
FC
Precise spec needed.
Sagemcom already implemented WiFi QoS on
deployed products with 2 SSIDs.
PC
FC
FC
Already deployed with a Tier1 operator FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
40/134
Cod Description
TR-LINRQ Link layer Requirements
TR-LINRQ-GENRQQ General Requirements
TR-LINRQ-GENRQQ-001The supplier shall specify ARP table maximum size and expiration time of the entries. The number of entries must be higher
than 256 addresses
TR-LINRQ-GENRQQ-002The device should have LAN 802.1p packet priorization (QoS on MAC). The supplier shall provide its roadmap to include
this functionality
TR-LINRQ-GENRQQ-003The device shall use ATM layer to transport data over DSL layer as in IT-BA-003 Ed 2, section 6, ITU-T I.361, I.321 and
I.150
TR-LINRQ-GENRQQ-004The device shall support ATM layer Physical Medium sublayer (PMD) functions and primitives between PMD and ATM
layers as in ITU-T I.321TR-LINRQ-GENRQQ-005 The device shall support ATM layer: Convergence sublayer (CS) as in ITU-T I.321
TR-LINRQ-GENRQQ-006The device shall support ATM layer: Transmission Convergence (TC) sublayer primitives (to/from ATM-PMD and
management plane) as in ITU-T I.413
TR-LINRQ-GENRQQ-007The device ATM layer, Convergence sublayer shall use HEC field to perform cell alignment, single bit error correction and
error detection and correction as in ITU-T I.321, I.432.1 and I.361-2.3.5
TR-LINRQ-GENRQQ-008
The device shall support ATM layer Convergence sublayer. Cell Rate Decoupling (CRD) feature using idle cells to adapt cell
flow to the transmission system capacity as defined in ITU-T I.321 and I.432.1. If not possible then ATM Forum proceedings
for CRD can be used.
TR-LINRQ-GENRQQ-009 The device shall support ATM layer: Convergence sublayer. Cell data randomizing as in ITU-T I.432.1
TR-LINRQ-GENRQQ-010 ATM cell format as in ITU-T I.361. UNI 2.2 and UNI 3.1 must be Supported
TR-LINRQ-GENRQQ-011 Default Cell Loss Priority = 0 (upstream cells) for PPPoE over ATM.
TR-LINRQ-GENRQQ-012 General Flow Control (GFC) bits are not required in the cell header.
TR-LINRQ-GENRQQ-013Filling out of PTI (Payload Type Identifier) field shall be accomplished according to I.361 paragraph 2.3.3 and 2.3.4 in the
incoming and outgoing directions
TR-LINRQ-GENRQQ-014 The device shall support ATM Virtual Channels in both permanent and semipermanent mode
TR-LINRQ-GENRQQ-015The device shall support ATM layer. Transmission of user data is always considered as bidirectional, and therefore cells
with the same VPI and VCI only belong to one bidirectional data connection (VC)
TR-LINRQ-GENRQQ-016ATM Virtual Channels Identifiers. VPI Range for 0 to 255 and VCI from 0 to 65535. No limitations in VPI/VCI range (0/0 not
valid, but 0/x or x/0 shall be valid)
TR-LINRQ-GENRQQ-017ATM Virtual Channels: VPI/VCI values reserved for signalling, OAM, resource management, etc shall no be used for datatransmission or any kind of proprietary communication channel
TR-LINRQ-GENRQQ-018The device shall support al teast 8 PVCs and each one of them may have different configuration (QoS, RIP, NAT, Firewall,
PPPoE sessions...)
TR-LINRQ-GENRQQ-019 ATM requirements. It shall be possible to attach a PVC to each Ethernet, WLAN or USB interface
TR-LINRQ-GENRQQ-020 ATM requirements. It shall be possible to attach the same one PVC on more than one interface (Ethernet, WLAN and USBinterface)
TR-LINRQ-GENRQQ-021 ATM requirements. Minimum 2 PPPoE sessions can be initialized per PVC
TR-LINRQ-GENRQQ-022 ATM requirements. Static routes can be assigned to different PVCs without the need of a destination IP address.
TR-LINRQ-GENRQQ-023 ATM requirements. Multicast/Unicast can be enabled over 1 PVC to provide video service
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
41/134
TR-LINRQ-GENRQQ-024 ATM requirements. The video PVC shall be able to transport 3 multicast/unicast traffic flows
TR-LINRQ-GENRQQ-025 ATM requirements. The device shall support ATM AAL5 (ITU.363.5)TR-LINRQ-GENRQQ-026 ATM requirements. The maximum allowed BER is 10e-7 when using ATM AAL5 (ITU.363.5)
TR-LINRQ-GENRQQ-027
The device shall support the Multi-protocol Encapsulation over ATM AAL5 according to the specification RFC1483 and RFC
2684, including LLC, LLC SNAP (MTU of AAL5 payload shall be at least 1528 byte -at least 1536 for ATM cell payload - to
transport 1518 byte of Ethernet frames without fragmentation through PPPoE or not) and VCMux
TR-LINRQ-GENRQQ-028The device shall support ATM QoS: service classes as in ITU-T I.371 and ATM Forum Traffic Management 4.1, including
UBR, CBR and VBR
TR-LINRQ-GENRQQ-029 Support of ATM QoS service Class ABR
TR-LINRQ-GENRQQ-030 ATM QoS serv ice classes can be configured for each connection from the remote management system
TR-LINRQ-GENRQQ-031ATM asymmetric/symmetric data bit rate is achieved depending on the ATM service class used (QoS parameters: SCR,
PCR)
TR-LINRQ-GENRQQ-032 The device shall support ATM QoS Connection Admission Control (CAC) feature.
TR-LINRQ-GENRQQ-033
The device shall support ITU-T I.610 Operation And Maintenance (OAM) functions in F4 and F5 End to End and Segment
flows:
OAM F4 and F5 cells support
VC-AIS / VC-RDI
Continuity check
Loopback
Forward and backward performance monitoring
Activation / deactivation
System management
TR-LINRQ-GENRQQ-034
If the device support processing of OAM cells (ITU-T I.610, I.751 and I.732) the supplier shall describe in detail the
implemented algorithms. If OAM feature is not supported then data transmission shall not be affected when the the device
receives OAM cells.
TR-LINRQ-GENRQQ-035For operation and maintenance purposes the supplier of the ADSL modem and the type of the modem shall be uniquelyidentified by information stored in the ATU-R registers ATU-R supplier ID (Register #0), ATU-R version number minusone (Register #1), ATU-R serial number (Register #2) as specified in the ITU-T recommendation [G.992.1].
TR-LINRQ-GENRQQ-036
After power up the ADSL modem of the DSL Port may perform a self test and report the self test result via the ATU-R
register Self test result (Register #3). If the self test succeeded and the ADSL modem is able to transfer data, the self testresult should be 0x00. If the self test fails, the result should be a value other than 0x00.
TR-LINRQ-GENRQQ-037 Link layer for Internet service: The device shall support PPP line layer protocol in accordance with RFC791
TR-LINRQ-GENRQQ-038 Link layer for Internet service: The device shall support PPP control protocol for IP (IPCP) in accordance with RFC1332
TR-LINRQ-GENRQQ-039 Link layer for Internet service: The device shall not negotiate other network protocol over PPP (IPX, X25)
TR-LINRQ-GENRQQ-040 Link layer for Internet service. PPP. PAP authentication for the PPP protocol (IETF RFC1334)
TR-LINRQ-GENRQQ-041 Link layer for Internet service. PPP. CHAP authentication for the PPP protocol (IETF RFC1994)
TR-LINRQ-GENRQQ-042 Link layer for Internet service. PPP. The supplier shall describe if the device supports forced PPP authentication: if it isconfigured to authenticate using only CHAP, it shall inform the BRAS to use CHAP if it tries to use PAP
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
42/134
TR-LINRQ-GENRQQ-043
Link layer for Internet service. PPP. The supplier shall describe if the modem supports configuration of automatic retry
parameters in case of unsuccessful setup of PPP protocol. Modem must automatically retry setup of PPP protocol. The
delay between to consecutive retries of PPP setup should be configurable on modem in range 5 to 90 seconds with step of
1 second. Default value of PPP setup rate must be set from 60 to 90 seconds
TR-LINRQ-GENRQQ-044
Link layer for Internet service. The supplier shall describe the modem behaviour if the modem sends PPPoE PADI to BRAS
and the BRAS does not answer with PADO. The supplier shall describe the amount of consecutive PADI and the time
interval within the consecutive PADI are sent. Max. 60 seconds between consecutive PPPoE PADI is required.
TR-LINRQ-GENRQQ-045The device must send PPPoE PADT to BRAS at first when is restarted through internal tools (e.q. restart of the device or
reboot after upgrade of the device).
TR-LINRQ-GENRQQ-046 The PPPoE PADI may be only sent to ADSL port. PPPoE PADI must not be sent to any LAN port when is not allowed
TR-LINRQ-GENRQQ-047
Link layer for Internet service. The modem shall support PPP keep-alive option. PPP keep-alive parameters should be
configurable on modem. Default value of PPP keep-alive must be set to send keep-alive (PPP echo-request) every 30
seconds to BRAS and brings PPP session down if 5 consecutive keep-alive procedures fail (The modem does not receive 5
PPP echo-replay). The modem must answer to PPP echo-request from the BRAS sending PPP echo-replay.
TR-LINRQ-GENRQQ-048
The device shall use the Point-to-Point Protocol over Ethernet (PPPoE) adaptation layer to establish Point-to-Point Protocol
(PPP) sessions according to the specifications [RFC 1144], [RFC 1332], [RFC 1334], [RFC 1570], [RFC 1661], [RFC 1994],
[RFC 2865], [RFC 2869] with additions.
TR-LINRQ-GENRQQ-049The device shall establish one PPP session within 1 second for all data traffic and the Auto-Configuration Service using oneunique MAC address if the PPP session has not been established previously and the Auto-Configuration Client or the IP
Routing functionality requests the data connection
TR-LINRQ-GENRQQ-050
The device shall support the following retry mechanism in the case of an unsuccessful PPP Data session establishment.
No. No of retries Timeouts(secs) Description
1 4 3 The initial retry must follow up relatively quickly in order to guarantee a fast setup
time.
2 5 60 When the initial retry has failed 4 times this indicates something is wrong and
therefore to avoid unnecessary traffic it is suggested to have a retry after 60 secs until the limit of 5 is reached.
3 infinite 900 The device does a retry every 900 secs
TR-LINRQ-GENRQQ-051Link layer for Internet service. The supplier shall describe allowed range and default value of maximum routable unit (MRU).
Default value 1492 is expected
TR-LINRQ-GENRQQ-052 Link layer for Internet service. The supplier shall describe allowed range and default value of maximum segment size(MSS). Default value 1452 is expected
TR-LINRQ-GENRQQ-053
Link layer for Internet service. Adjusting of TCP maximum segment size: when IP packets with TCP payloads are traversing
between media with different MTUs (for example Ethernet 1500 and PPPoE 1492) the minimum value shall be kept (local
MSS, remote MSS and the MSS configured in the device)
TR-LINRQ-GENRQQ-054Spanning tree protocol support in the link layer for TV service. This protocol bridging shall be done with no changes inside
STP frames.
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
43/134
TR-LINRQ-GENRQQ-055 Link layer for TV service. MAC table: limitations and acquiring and releasing rules
TR-LINRQ-GENRQQ-056 Link layer for TV service. FCS checking: rule to check frame integrityTR-LINRQ-GENRQQ-057 Link layer for TV service. The modem shall support flooding broadcast
TR-LINRQ-GENRQQ-058 Link layer for TV service. The modem shall support bridging all DHCP frames
TR-LINRQ-GENRQQ-059 Link layer for TV service. The modem shall support flooding of multicast frames
TR-LINRQ-GENRQQ-060 Link layer for TV service. The modem shall support flooding of unknown unicast frames
TR-LINRQ-GENRQQ-061
The device shall support a functionality to use prioritisation of outgoing packets between the following interfaces:
- DSL Port Interface
- LAN Port Interface
TR-LINRQ-GENRQQ-062 The device shall support diffserv
TR-LINRQ-GENRQQ-063 The device shall support the configuration of link type and connection type as per appendix B of TR098 on these VCs.
TR-LINRQ-GENRQQ-064
The device shall support a separate layer2bridging instance for the IPTV passthrough.
Above mentioned VCs and some of the Ethernet ports can be assigned to this bridging instance through TR069 methods.Appendix A5 of TR098 shall be used.
TR-LINRQ-GENRQQ-065The device shall support a separate layer3forwarding instance for the IPTV passthrough.
Above mentioned VCs and some of the Ethernet ports can be assigned to this routing instance through TR069 methods
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
44/134
Details and comments (English)
Fully Compliant (FC)
Partially Compliant (PC)
Non Compliant (NC)
FC
FC
FC
FC
FCFC
FC
FC
FC
FC
FC
FC
FC
FC
FC
VCI:32-65535 PC
FC
Maximum of 8 PVC are supported FC
The device offers the possibility to attach a
PVC to each Ethernet interface. No USB slave
available
PC
PC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
45/134
FC
FC
FC
FC
FC
ABR not supported but nrt-VBR can be used. It
has almost the same behavior as ABRPC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FCThe device supports to choose between PAP
and CHAPFC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
46/134
In case of unsuccessful setup of PPP, the
router tries to reconnect each 60 seconds (this
value is the default one and can be changed
upon request. It's not available using the web
interface). Beside this, when the user tries to
connect to internet, the router use an
interception page that gives to the end user the
possibility to state a new configuration
parameters. The interception page contains a
message saying that there may be an error in
the PPP parameters.
PC
To be implemented FC
FC
FC
FC
FC
FC
This mechanism may be implemented. PC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
47/134
FCBad FCS frames are discarded FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
48/134
Cod Description
TR-NETRQ Network Layer Requirements
TR-NETRQ-IPCON IP Configurations
TR-NETRQ-IPCON-001 The device shall support RFC791 IP protocol (v4)
TR-NETRQ-IPCON-002
The device shall support RFC2460 IP protocol v6 with at least the following requirements:
- support RFC 4291, IP Version 6 Addressing Architecture
- support RFC 5952 A Recommendation for IPv6 Address Text Representation
- support RFC 4862 IPv6 Stateless Address Autoconfiguration
TR-NETRQ-IPCON-003
The device shall support DHCPv6 (DHCP snoop -for subscriber identification) with at least the following requirements:
- support RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
- support Lightweight DHCPv6 Relay Agent draft-ietf-dhc-dhcpv6-ldra-02- support RFC 3633 IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
TR-NETRQ-IPCON-004
The device shall support DUAL STACK IPv6/IPv4 with at least the following requirements:
- support Dual-stack lite broadband deployments post IPv4 exhaustion draft-durand-softwire-dual-stack-lite-01
- support RFC 4213 Basic Transition Mechanisms for IPv6 Hosts and Routers
- support RFC 4241 A Model of IPv6/IPv4 Dual Stack Internet Access Service
TR-NETRQ-IPCON-005
The device shall support TUNNELING (PPPoE and IPoE) for IPv6 with at least the following requirements:
- support RFC 2473 Generic Packet Tunneling in IPv6 Specification
- support RFC 5072, IP Version 6 over PPP
TR-NETRQ-IPCON-006
The provider shall inform regarding DUAL STACK LITE the following information:
- how long it takes to implement the software in the CPE after the standard it will be defined. (Specify the amount of time -
weeks- after T0)
- it would be possible to upgrade remotely the change of software. (Detail if it necessary any change in the hardware)
- if it is possible in your equipment (detail the model that applies) support both mode Dual Stack and Dual Stack Lite.
- if your offer include the possibility to deliver CPE with Dual Stack and then evolve to Dual Stack Lite (please detail this
issue and if it is part of the same buying process.
TR-NETRQ-IPCON-007
The provider shall inform regarding INTEROPERABILITY the following information:
- For DS-Lite the provider will inform what AFTRs vendor (Address Family Transition Router) interoperate with your
solution. Specify model and release and if it were possible the configuration tested.
TR-NETRQ-IPCON-008
The provider shall inform regarding MULTICAST IPv6 AND GROUP MANAGEMENT the following information:
- the mechanism used for MLD ICMPv6 (Multicast Listener Discovery) Reference RFC 4605 Internet Group Management
Protocol (IGMP) Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying")
- MLD snooping
- Unicast Transmission of IPv6 Multicast Messages on Link-layer draft-gundavelli-v6ops-l2-unicast-04
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
49/134
TR-NETRQ-IPCON-009
The provider shall inform regarding QoS SUPPORT the following information:
- IPv6 Flow Classification,
- IPv6 Flow Policy
- Queue management
- Marking Traffic Class
TR-NETRQ-IPCON-010
The provider shall inform the planning to address the following issues:
- The A+P Approach to the IPv4 Address Shortage draft-ymbk-aplusp-05
- Routing RIPng for IPv6 RFC 2080
- Allowing together with the BRAS the functionality Change of Authorization RFC 5176 Dynamic Authorization Extensionsto Remote Authentication Dial In User Service (RADIUS)
- IPv4 Connectivity Access in the Context of IPv4 Address Exhaustion: Port Range based IP Architecture
- PPPoE v6 Dialer
- Support of monitoring: MIB v6, V6 Interface stat, etc.
- The recommendation from the Broadband Forum TR-187 IPv6 for PPP Broadband Access
TR-NETRQ-IPCON-011 The device can be configured in IP mode: RFC1483/2684 routed. IPoA (RFC1577)
TR-NETRQ-IPCON-012 The device can be configured in IP mode: RFC1483/2684 routed. IPoE/MER (MAC Encapsulated Routing).
TR-NETRQ-IPCON-013 The device can be configured in IP mode: RFC1483/2684 bridged. EthoA.
TR-NETRQ-IPCON-014The device can be configured in IP mode: RFC1483/2684 bridged. EthoA bridging using IEEE802.1d MAC bridging
supporting a minimum of 272 MAC addresses
TR-NETRQ-IPCON-015The device can be configured in IP mode: RFC1483/2684 bridged. EthoA bridging using IEEE802.1d MAC bridging is
transparent to PPPoE (RFC2516), VLAN (IEEE802.1Q) and IPSEC protocols
TR-NETRQ-IPCON-016
The device can be configured in IP mode: RFC2364 routed PPPoA (RFC2364) with PAP (RFC1334) or CHAP (RFC1994)
authentication. Session establishment can be done: manually, on demand or always on (in case session is closed it will be
restablished as soon as it becomes possible).
TR-NETRQ-IPCON-017 IP configuration modes PPPoA: Session Terminated on Inactivity Timeout
TR-NETRQ-IPCON-018
The device can be configured in IP mode: RFC1483/2684 routed. PPPoE (RFC2516) with PAP (RFC1334) or CHAP
(RFC1994) authentication. Session establishment can be done: manually, on demand or always on (in case session is
closed it will be restablished as soon as it becomes possible).
TR-NETRQ-IPCON-019 IP configuration modes PPPoE: Session Terminated on Inactivity Timeout
TR-NETRQ-IPCON-020 Secondary IP addresses can be configured in all the device interfaces
TR-NETRQ-IPCON-021 IP subnets can be defined and attached to the LAN interfaces
TR-NETRQ-IPCON-022
VLSM (variable length subnet mask): The modem shall handle the variable subnet mask in accordance with IETF RFC
1878. The modem shall acquire IP address through PPP IPCP within the same network class as is configured at LAN side
of the modem. For example, when LAN side of the modem is configured with 194.228.208.0/29 network the modem shall be
able to acquire 194.228.208.8 address at WAN through PPP IPCP.
TR-NETRQ-ROUTI Routing
TR-NETRQ-ROUTI-001
The device shall support a functionality to support routing/forwarding of network packets that have been received on the
following interfaces to any of the following interfaces: WAN interface (PPP interface if configured), LAN interface and WLAN
interface
TR-NETRQ-ROUTI-002 The IP Routing functionality of the device shall use IP Routing Table.TR-NETRQ-ROUTI-003 The device shall support static routing
TR-NETRQ-ROUTI-004 The supplier shall describe if the device supports establishing of static routing entries through management interface
TR-NETRQ-ROUTI-005 The device shall support dynamic routing
TR-NETRQ-ROUTI-006 Dynamic routing via RIPv1 and RIPv2 protocol in both LAN and WAN Interfaces
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
50/134
TR-NETRQ-ROUTI-007 The device should have ARP proxy functionality
TR-NETRQ-ROUTI-008 The device shall support ARP cache as defined in RFC 826
TR-NETRQ-ROUTI-009The routing functionality of the device shall support the Address Resolution Protocol (ARP) according the specification RFC
826.
TR-NETRQ-ROUTI-010The device shall have NAT/PAT functionality as in RFC1631/RFC3022 (NAT/PAT basics), RFC2663 (terminology and
considerations) and RFC3027(protocol complications with the IP NAT) in routed mode that can be enabled or disabled
TR-NETRQ-ROUTI-011The device shall be able to run in NAT mode to translate IP addresses in accordance with IETF RFC 3022. NAT shall
preserve TOS field of IP header when IP packet is going through translation process in both directions
TR-NETRQ-ROUTI-012The device shall be able to run in NAT mode to translate IP addresses in accordance with IETF RFC 3022. The supplier
shall specify amount of maximum simultaneously established session
TR-NETRQ-ROUTI-013
The Network and Port Address Translation of the device shall be based on ports defined in the Transmission Control
Protocol (TCP) according the specification [RFC 793] and in the User Datagram Protocol (UDP) according the specification
[RFC 768].
TR-NETRQ-ROUTI-014The PAT functionality shall be able to carry out TCP/UDP mappings of external addresses and ports to different internal
addresses and ports
TR-NETRQ-ROUTI-015 PAT minimum table size of 80 entries. Vendor shall specify maximum number of entries.
TR-NETRQ-ROUTI-016 The PAT funcionatily shall support DMZ
TR-NETRQ-ROUTI-017 NAT shall be transparent for IPSec (NAT traversal): VPN pass-through
TR-NETRQ-ROUTI-018
NAT shall be transparent for protocols that support NAT/PAT and shall use ALG (Application Level Gateway) for those do
not support NAT/PAT: ICMP, HTTP, RTSP, FTP, TELNET, DNS queries, POP3, SMTP, IRC, Real Audio, Online gaming,
Netmeeting, Instant Messaging (ICQ, MSN...), Softphone, Video Messenger, UPNP, Microsoft MMS...)
TR-NETRQ-ROUTI-019The modem shall support acquiring WAN default route during PPP negotiation. Default route shall be install as soon as the
PPP session is established. Default route shall be withdrawn as soon as the PPP session is disconnected
TR-NETRQ-ROUTI-020
Both in bridged or routed modes time to transfer packets among interfaces must comply:
- 5ms between LAN and WLAN
- 15ms between PPP/WAN and LAN or WLAN
TR-NETRQ-ROUTI-021Both in bridged or routed modes throughtput between interfaces must comply:- 16Mbps between PPP/WAN and LAN
- 16Mbps between PPP/WAN and WLAN
TR-NETRQ-ROUTI-022 The device shall support IP fragmentation
TR-NETRQ-ROUTI-023The routing functionality of the device shall support the Internet Control Message Protocol (ICMP) according the
specification RFC 826.
TR-NETRQ-ROUTI-024 The number of sessions supported by UDP should not be lower than 512 no matter how long the packet is
TR-NETRQ-ROUTI-025 The device shall support IETF RFC 0894 Standards for the Transmission of IP Datagrams over Ethernet Networks
TR-NETRQ-ROUTI-026 The device shall support IETF RFC 0922 Broadcasting Internet Datagrams in the Presence of Subnets
TR-NETRQ-ROUTI-027 The device shall support IETF RFC 0950 Internet Standard Subnetting Procedure
TR-NETRQ-ROUTI-028 The device shall support IETF RFC 1009 Requirements for Internet Gateways (Link Layer issues only)
TR-NETRQ-ROUTI-029 The device shall support IETF RFC 1042 Standard for the Transmission of IP Datagrams over IEEE 802 Networks
TR-NETRQ-ROUTI-030 The device shall support IETF RFC 1112 Host Extensions for IP MulticastingTR-NETRQ-ROUTI-031 The device shall support IETF RFC 1122 Requirements for Internet Hosts Communication Layers
TR-NETRQ-ROUTI-032 The device shall support IETF RFC 1123 Requirements for Internet Hosts Application and Support
TR-NETRQ-ROUTI-033 The device shall support IETF RFC 1256 ICMP Router Discovery Messages (Router Specification only)
TR-NETRQ-ROUTI-034 The device shall support IETF RFC 1519 Classless InterDomain Routing (CIDR)
TR-NETRQ-ROUTI-035 The device shall support IETF RFC 1812 Requirements for IP Version 4 Routers
TR-NETRQ-ROUTI-036 The device shall support IETF RFC 1918 Address Allocation for Private Internets
-
7/30/2019 Bhs Adsl2 Tech Reqs Rev7 Sagemcom Final
51/134
TR-NETRQ-ROUTI-037 The device shall support IETF RFC 3600 Internet Official Protocol Standards
TR-NETRQ-SECUR Security
TR-NETRQ-SECUR-001Firewall filtering: default rules to filter NetBIOS traffic (137, 138 and 138 both tcp and udp ports) that can be changed from
the local and management software
TR-NETRQ-SECUR-002
The device shall have firewall functionality in routed mode with a minimum of 20 filter rules andthroughtput of 46B IP
packets.
Firewall shall filter by origin/destination IP, mask and origin/destination TCP/UDP ports and can also filter ICMP packets,
service types and protocols.
TR-NETRQ-SECUR-003 Firewall shall support port scanning protection
TR-NETRQ-SECUR-004
Firewall shall support Denial of Service (DOS) protection for itself and all routed LAN Port Interface and Wireless LAN Air
Interface including protection from Ping of Death, SYN Flood LAND and variant attacks in routing mode (not in bridged
mode).
TR-NETRQ-SECUR-005 The device shall not reply to ICMP echo requests by default but it can be allowed
TR-NETRQ-SECUR-006 The supplier will describe other IP firewall functionalities
TR-NETRQ-SECUR-007 Firewall may be provided as external application installed in the user equipment
TR-NETRQ-SECUR-008The device shall support Access Control List: limited range of IP addresses (Management Center) can remotely manage the
device (telnet, ftp, tftp...)
TR-NETRQ-SECUR-009
The device shall support a functionality for Stateful Packet Inspection (SPI) firewall of network packets that have been
received on the PPP Data session based at maximum speed of 16Mbit/s. The firewall shall use stateful packet inspection to
determine if an inbound connection is allowed through the firewall to the private LAN. A legitimate incoming packet shall be
matched with the outbound request for that packet and allowed in
TR-NETRQ-SECUR-010
The device shall reject packets from the WAN with MAC addresses of devices on the local LAN or invalid IP addresses
(including but not limited to broadcast addresses, private IP addresses or IP Addresses matching those assigned by the
DHCP Server to the LAN Port and Wireless LAN Air Interface and their attached clients).
TR-NETRQ-SECUR-019
The device shall drop or deny access requests from WAN side connections to LAN side devices and the DSL device itself
except in direct response to outgoing traffic or as explicitly permitted through configuration of the DSL device (e.g., for port
forwarding or management)
TR-NETRQ-SECUR-020
The device may support a separate firewall log to maintain records of all transactions that violate firewall rules with
timestamps. This log shall hold al least the last 100 entries or 10KB text and will be only cleared when rebooted
TR-NETRQ-OTHER Others
TR-NETRQ-OTHER-001 Multicasting support to provide video service
TR-NETRQ-OTHER-002 The device must comply "IGMP proxy functionality for 2xSTB IPTV connection Functionality Description v.2" document
TR-NETRQ-OTHER-003 Multicasting support to provide video service. The WAN interface shall have an static IP address.
TR-NETRQ-OTHER-004
The device shall support IGMP protocol for multicasting. Configurable parameters are: robuts control, query interval, group
query interval, query response interval, group query response interval, last member query interval, last member query count
and group query count.
TR-NETRQ-OTHER-005 The supplier shall provide its roadmap to include Layer 2 Multicast (similar to IGMP snooping) support into the device.
TR-NETRQ-OTHER-006 The device shall support IGMP protocol for multicasting. Multicast packet interchange can be allowed in the interface
TR-NETRQ-OTHER-007 The device shall support IGMP prot