nucom_bhs_adsl2_tech_reqs_rev7

7/28/2019 NuCom_BHS_ADSL2_Tech_Reqs_rev7

1/134

1

2

2

M


2/134


3/134


4/134


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 clarificationare 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

ain blocks are:


6/134

BRAS: Broadband Remote Access Server

CCBS: Completion of Calls to Busy Subscribers

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 ProtectionIP: 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.


7/134

LED: Light Emitting Diode

MAC: Media Access Control

MBPS: Megabits Per Second

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.


8/134

TKIP: Temporal Key Integrity Protocol

TR: Technical Requirement.

TXOP: Transmit Opportunity

UDP: User Datagram Protocol.

UNE: Una Norma Espaola

USB: Universal Serial Bus

VC: Virtual ConnectionVoIP: 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


9/134


10/134

Cod

TR-GENRQQ

TR-GENRQQ-MECDE

TR-GENRQQ-MECDE-001

TR-GENRQQ-MECDE-002

TR-GENRQQ-MECDE-003

TR-GENRQQ-MECDE-004

TR-GENRQQ-MECDE-005

TR-GENRQQ-MECDE-006

TR-GENRQQ-MECDE-007

TR-GENRQQ-MECDE-008

TR-GENRQQ-POWSU

TR-GENRQQ-POWSU-001

TR-GENRQQ-POWSU-002

TR-GENRQQ-POWSU-003

TR-GENRQQ-POWSU-004

TR-GENRQQ-POWSU-005

TR-GENRQQ-POWSU-006


11/134

TR-GENRQQ-POWSU-007

TR-GENRQQ-POWSU-008TR-GENRQQ-POWSU-009

TR-GENRQQ-POWSU-010

TR-GENRQQ-POWSU-011

TR-GENRQQ-POWSU-012

TR-GENRQQ-OPSTA


12/134

TR-GENRQQ-OPSTA-001

TR-GENRQQ-OPSTA-002

TR-GENRQQ-OPSTA-003

TR-GENRQQ-OPSTA-004

TR-GENRQQ-OPSTA-003

TR-GENRQQ-ELCHA

TR-GENRQQ-ELCHA-001

TR-GENRQQ-ELCHA-002

TR-GENRQQ-ELCHA-003

TR-GENRQQ-ELCHA-004

TR-GENRQQ-ELCHA-005

TR-GENRQQ-ELCHA-006

TR-GENRQQ-ELCHA-007

TR-GENRQQ-ELCHA-008

TR-GENRQQ-ELCHA-009

TR-GENRQQ-ELCHA-010

TR-GENRQQ-ELCHA-011


13/134

TR-GENRQQ-ELCHA-012

TR-GENRQQ-ELCHA-013

TR-GENRQQ-ELCHA-014

TR-GENRQQ-ELCHA-015

TR-GENRQQ-ELCHA-016

TR-GENRQQ-CLICO

TR-GENRQQ-CLICO-001

TR-GENRQQ-CLICO-002

TR-GENRQQ-CLICO-003

TR-GENRQQ-CLICO-004

TR-GENRQQ-CLICO-005

TR-GENRQQ-SECPR

TR-GENRQQ-SECPR-001

TR-GENRQQ-SECPR-002

TR-GENRQQ-SECPR-003

TR-GENRQQ-SECPR-004

TR-GENRQQ-ELECO

TR-GENRQQ-ELECO-001

TR-GENRQQ-ELECO-002

TR-GENRQQ-ELECO-003

TR-GENRQQ-ELECO-004

TR-GENRQQ-ELECO-005

TR-GENRQQ-ELECO-006

TR-GENRQQ-OVERR

TR-GENRQQ-OVERR-001

TR-GENRQQ-OVERR-002

TR-GENRQQ-OVERR-003

TR-GENRQQ-OVERR-004

TR-GENRQQ-OVERR-005


14/134

TR-GENRQQ-OVERR-006

TR-GENRQQ-CONNE

TR-GENRQQ-CONNE-001

TR-GENRQQ-CONNE-002

TR-GENRQQ-CONNE-003

TR-GENRQQ-ENVRQ

TR-GENRQQ-ENVRQ-001

TR-GENRQQ-FREEF

TR-GENRQQ-FREEF-001

TR-GENRQQ-PPCAS

TR-GENRQQ-PPCAS-001

TR-GENRQQ-PPCAS-002

TR-GENRQQ-PPCAS-003

TR-GENRQQ-PPCAS-004

TR-GENRQQ-PPCAS-005

TR-GENRQQ-PPCAS-006

TR-GENRQQ-PPCAS-007

TR-GENRQQ-PPCAS-008

TR-GENRQQ-PPCAS-009

TR-GENRQQ-PPCAS-010

TR-GENRQ-POSTT

TR-GENRQ-POSTT-001

TR-GENRQQ-OTHER


15/134

TR-GENRQQ-OTHER-001

TR-GENRQQ-OTHER-002


16/134

Description Ctg.

General Requirements

Mechanical Design

The 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 TelefonicaM

Power supply size shall not block or obstruct the use of the adjacent plugs M

The device housing shall be white M

The plastic of the device will be ABS+PC M

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

M

The device shall have an ON/OFF labelled power button M

The device shall have a reset button to restore default configuration. The button must be located at the back of the unit M

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)

M

Power Supply

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%)

M

Device power input type: DC M

The device power adaptor can be external or internal M

The device power adapter shall be an automatic power switch M

The device power cord minimum length shall be 2 meters M

Power supply must be according to each conutry M

Argentina M


17/134

Brazil M

Chile M

Colombia M

Peru M

UK M

Spain M

Power supply shall be labelled with device model and name M

In case of power interruption the device shall reboot automatically M

The device can not be powered via RJ11 interface I

Power supply shall be according to EU RD 278/2009 M

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 hembra compatible

connector:

- External diameter: 5,50,05mm

- Internal Diameter: 2,10,1mm

- Length: 9,00,1mm

M

The Power supply must be in conformity with Telefonica specification for Universal Power supply as defined on the document

ERQ.c1.0001 3rd edition / Jul 2011 (document in Spanish)M

Indication of Operating Status


18/134

In the frontal side of the equipment it has to be included the following LEDS

M

The frontal Led indicating the Ethernet functionality should be a single led for the four LAN pors I

In the Back side of the device it may have indibidual Led for each of the Ethernet ports M

A 2 Hz blinking Green-Red round of Broadband led should inform the firmware updating and flash memory writing M

Additionaly to LED indicators the supplier may provide user software to monitor device activity O

Electrical characteristics

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

M

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.

M

The equipment will meet the established requirements in TS 202 913 V1.2.2 Recommendation in the applicable aspect. M

DSL 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.1M

DSL channel longitudinal balance must be higher than 40dB at [20 - 1.100]kHz when charging the DSL interface with 600ohm M

DSL channel nominal impedance of 100ohm at DSL band in the PSTN interface M

DSL channel return loss at 30Hz - 1.100kHz equal or higher to 10dB M

Noise level inserted by the device to the DSL channel of the PSTN line shall be lower than -65dBmp M

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

M

Errors 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.M

The analog ports shall perform according to ETSI ES 201 970 v1.1.1 M

LED Colour Mode Status

Power Red/Green

Off Router powered off

Blinking 2Hz Red Failure on Power On Self Test

Solid Green Router powered on correctly

Wifi Green

On Wi-Fi connection is available

Off Wi-Fi connection is not available

Blinking green Negotiation or traffic on line

3G Red/Green

Blinking green Negotiation

Solid green Up

Quick blinking green Tx/Rx traffic on line

Solid red Authentication failed

Off Traffic through broadband interface

Broadband Red/Green

Blinking green PPP/DHCP negotiation

Solid green PPP/DHCP up

Quick blinking green Tx/Rx traffic on line

Solid red Authentication failed

Ethernet GreenOn Ethernet connection is available

Off Ethernet connection is not available

DSL Green

Off Router powered off

Blinking 2Hz No line detected

Blinking 4Hz Line training

Solid Line up

WPS Red/Green

Solid Green WPS Active

Blinking 2Hz Green WPS Negotiation OpenSolid Red (20 seconds) Problems on WPS registration

Off WPS Functionality Disable


19/134

Inband noise (psophometrically weighted) for narrowband audio (300Hz 3.4kHz) shall be less than 75.0 dBVp M

Inband noise (psophometrically weighted) for wideband audio (50Hz - 7kHz) will be less than 75.0 dBVp O

Out-of-band noise (psophometrically weighted) for the human audible spectrum (30Hz - 20kHz) shall be less than 67.0 dBVp M

Noise at mains frequency (50Hz) should not exceed 0.25 mV (psophometric weighed), this being the value at the l ine 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)

M

ALASS and other enhanced services as in 14.3 of ES 201 970 shall be supported M

Climatic Conditions

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)

M

The device shall be ready to be installed in non temperature or humidity controlled indoor environments at 0-50C and 5-95%

relative humidity conditionsM

Storage temperature [-25, 70]C M

Device electrical values shall be accomplished in the range [-10,60]C, humidity class F and after 2 hours (DIN 40046). M

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 part laboratory (as

defined on ASTM-B117 Salt spray test.)M

Security and Protection

The device shall comply with the 73/23/CEE directive and the amendments to the 93/68/CEE directive M

The 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 dischargesM

Minimum resistance shall be 100Mohm when 100Vcc applied between cover and line contacts, cover and power wires and

contacts and power wiresM

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

M

Electromagnetic Compatibility

The device shall comply with the 89/336/CEE directive and the amendments to the 93/68/CEE directive (reviewed if newer

directives)M

The device shall comply ETSI 300 127, EM 55022-Classe A M

No EM interferences between device and PSTN M

The 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,M

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

M

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

M

Overvoltage and Overcurrent Resistibility

The device shall comply with the requirements of ITU-T Recommendation K.21 M

Power 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 500VccM

The device shall have output overcurrent and overvoltage protection M

The device shall have a protection fuse M

The device shall have minimum resistance 1Mohm M


20/134

On a case of Overvoltage and/or overcurrent, the device shouldn't lose the configurations and shall preserve the Firmware

Version unaffectedM

Connectors

It shall be ensured good contact between the plug and socket plug elements (male and female conectors) and that the

degradation 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 testing

will 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.

M

The device shall have a RJ11 female connector for the WAN interface and use its internal pair (3rd and 4th wires) M

The device shall have 4xRJ45 female connectors for the LAN interface according the specification ANSI EIA TIA-568B (to be

used with UTP cat5 cables)M

Environmental Requirements

The 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

HR

Freefall

The device shall be EM 60068-2-32 regulation compliant M

Production Process Control and Samples

The supplier shall provide the samples and means to perform quality tests M

Device sample for approval test shall be identified by producer name, model name, version, serial number, SW version,

chipset model and manufacturer and FW versionM

Telefonica inspectors can oversee device materials and production processes and

perform recalls if the product does not satisfy any requirement (recalls can be

carried 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.

M

The 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 yearsM

The device shall ensure a Mean Time Between (Hardware) Failure of:

- O2CR: 100 days

- O2DE and ColTel: at least 1 year

M

Faulty (total or partial) device rate = maximum 1 per 100 devices per year M

The device manufacturer shall provide a TR069 Score Card M

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.

M

The device supplier shall perform Interoperability Tests (IOT) with the supplier of Auto-Configuration Server that the OB hasselected 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.

M

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 the device

manufacturer

M

Power On Self Test

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.

M

Others


21/134

Non device status dependant phone service M

The supplier must be certified or commit to a deadline for certification in local regulator of each country M


22/134

Details and comments

(Spanish)Details and comments (English)

Fully

Compliant

(FC)

Partially

Compliant

(PC)

NonCompliant

(NC)

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

Es externo external only FC

FC

Actualmente es de 1.5m, pero

podra ser de 2mCurrently is 1.5m, but could be 2m FC

FC

FC


23/134

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


24/134

FC

En el modelo actual, 4 LEDs

Ethernet en el frontalCurrently, 4 LEDs for the Ethernet ports FC

Los LEDs ETH estn en el

frontalCurrently, the LEDs are on the front panel FC

FC

Soportado a travs del Web

GUIIt is provided in the Web GUI FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


25/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


26/134

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


27/134

FC

FC


28/134

Cod

TR-PHLRQ

TR-PHLRQ-WANTC

TR-PHLRQ-WANTC-001

TR-PHLRQ-WANTC-002

TR-PHLRQ-WANTC-003

TR-PHLRQ-WANTC-004

TR-PHLRQ-WANTC-005

TR-PHLRQ-WANTC-006

TR-PHLRQ-WANTC-007

TR-PHLRQ-WANTC-008

TR-PHLRQ-WANTC-009

TR-PHLRQ-WANTC-010

TR-PHLRQ-WANTC-011

TR-PHLRQ-WANTC-012

TR-PHLRQ-WANTC-013

TR-PHLRQ-WANTC-014

TR-PHLRQ-WANTC-015

TR-PHLRQ-WANTC-016

TR-PHLRQ-WANTC-017

TR-PHLRQ-WANTC-018

TR-PHLRQ-WANTC-019

TR-PHLRQ-WANTC-020

TR-PHLRQ-WANTC-021

TR-PHLRQ-WANTC-022

TR-PHLRQ-WANTC-023

TR-PHLRQ-WANTC-024

TR-PHLRQ-WANTC-025

TR-PHLRQ-WANTC-026

TR-PHLRQ-WANTC-027

TR-PHLRQ-WANTC-028

TR-PHLRQ-WANTC-029

TR-PHLRQ-WANTC-030

TR-PHLRQ-WANTC-031


29/134

TR-PHLRQ-WANTC-032

TR-PHLRQ-WANTC-033

TR-PHLRQ-WANTC-034

TR-PHLRQ-WANTC-035

TR-PHLRQ-WANTC-036

TR-PHLRQ-WANTC-037

TR-PHLRQ-WANTC-038

TR-PHLRQ-WANTC-039

TR-PHLRQ-WANTC-040

TR-PHLRQ-WANTC-041

TR-PHLRQ-WANTC-042

TR-PHLRQ-WANTC-043

TR-PHLRQ-WANTC-044

TR-PHLRQ-WANTC-045

TR-PHLRQ-WANTC-046

TR-PHLRQ-WANTC-047

TR-PHLRQ-WANTC-048

TR-PHLRQ-WANTC-049

TR-PHLRQ-WANTC-050

TR-PHLRQ-WANTC-051

TR-PHLRQ-WANTC-052

TR-PHLRQ-WANTC-053

TR-PHLRQ-WANTC-054

TR-PHLRQ-WANTC-055

TR-PHLRQ-WANTC-056

TR-PHLRQ-WANTC-057

TR-PHLRQ-WANTC-058

TR-PHLRQ-WANTC-059

TR-PHLRQ-WANTC-060

TR-PHLRQ-WANTC-061

TR-PHLRQ-WANTC-062

TR-PHLRQ-WANTC-063

TR-PHLRQ-WANTC-064

TR-PHLRQ-WANTC-065

TR-PHLRQ-WANTC-066

TR-PHLRQ-WANTC-067


30/134

TR-PHLRQ-WANTC-068

TR-PHLRQ-WANTC-069

TR-PHLRQ-WANTC-070

TR-PHLRQ-WANTC-071

TR-PHLRQ-WANTC-072

TR-PHLRQ-WANTC-073

TR-PHLRQ-WANTC-074

TR-PHLRQ-WANTC-075

TR-PHLRQ-WANTC-076

TR-PHLRQ-WANTC-077

TR-PHLRQ-WANTC-078

TR-PHLRQ-LANET

TR-PHLRQ-LANET-001

TR-PHLRQ-LANET-002

TR-PHLRQ-LANET-003

TR-PHLRQ-LANET-004

TR-PHLRQ-LANET-005

TR-PHLRQ-WILAN

TR-PHLRQ-WILAN-001

TR-PHLRQ-WILAN-002

TR-PHLRQ-WILAN-003

TR-PHLRQ-WILAN-004

TR-PHLRQ-WILAN-005TR-PHLRQ-WILAN-006

TR-PHLRQ-WILAN-007

TR-PHLRQ-WILAN-008

TR-PHLRQ-WILAN-009

TR-PHLRQ-WILAN-010

TR-PHLRQ-WILAN-011

TR-PHLRQ-WILAN-012

TR-PHLRQ-WILAN-013

TR-PHLRQ-WILAN-014


31/134

TR-PHLRQ-WILAN-015

TR-PHLRQ-WILAN-016

TR-PHLRQ-WILAN-017

TR-PHLRQ-WILAN-018

TR-PHLRQ-WILAN-019

TR-PHLRQ-WILAN-020

TR-PHLRQ-WILAN-021

TR-PHLRQ-WILAN-022

TR-PHLRQ-WILAN-023

TR-PHLRQ-WILAN-024

TR-PHLRQ-WILAN-025

TR-PHLRQ-WILAN-026

TR-PHLRQ-WILAN-027

TR-PHLRQ-WILAN-028

TR-PHLRQ-WILAN-029

TR-PHLRQ-WILAN-030

TR-PHLRQ-WILAN-031

TR-PHLRQ-WILAN-032

TR-PHLRQ-WILAN-033


TR-PHLRQ-WILAN-036

TR-PHLRQ-WILAN-037

TR-PHLRQ-WILAN-038

TR-PHLRQ-WILAN-039

TR-PHLRQ-WILAN-040

TR-PHLRQ-WILAN-041

TR-PHLRQ-WILAN-042

TR-PHLRQ-WILAN-043

TR-PHLRQ-WILAN-044


TR-PHLRQ-WILAN-047

TR-PHLRQ-WILAN-048

TR-PHLRQ-WILAN-049

TR-PHLRQ-WILAN-050

TR-PHLRQ-WILAN-051

TR-PHLRQ-WILAN-052

TR-PHLRQ-WILAN-053

TR-PHLRQ-WILAN-054

TR-PHLRQ-WILAN-055

TR-PHLRQ-WILAN-056


32/134

TR-PHLRQ-WILAN-057

TR-PHLRQ-WILAN-058

TR-PHLRQ-WILAN-059

TR-PHLRQ-WILAN-060

TR-PHLRQ-WILAN-061

TR-PHLRQ-WILAN-062

TR-PHLRQ-WILAN-063

TR-PHLRQ-WILAN-064

TR-PHLRQ-WILAN-065

TR-PHLRQ-WILAN-066

TR-PHLRQ-WILAN-067

TR-PHLRQ-WILAN-068

TR-PHLRQ-WILAN-069

TR-PHLRQ-WILAN-070

TR-PHLRQ-WILAN-071

TR-PHLRQ-WILAN-072

TR-PHLRQ-WILAN-073

TR-PHLRQ-WILAN-074

TR-PHLRQ-WILAN-075

TR-PHLRQ-WILAN-076

TR-PHLRQ-WILAN-077

TR-PHLRQ-WILAN-078

TR-PHLRQ-WILAN-079

TR-PHLRQ-WILAN-080


33/134

Description Ctg.

Physical Layer Requirements

Wan Access Technology

The device shall interoperate with any supplier DSLAM M

The 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)].M

The device shall have an ADSL over ISDN interface with 2B1Q modulation M

The device shall comply the standard ANSI T1.413: ADSL M

The device shall comply the standard G992.1 (G.DMT): ADSL transceivers using DMT modulation M

The device shall comply the standard G992.2 (G.Lite): ADSL Lite M

The device shall comply the standard G992.3: ADSL2 M

The device shall comply the standard G.992.3 Annex L: Extended Range ADSL2 M

The device shall comply the standard G.992.3 Annex M: Increased Upload Speed ADSL2 M

The device shall comply the standard G992.5: ADSL2+ M

The device shall comply the standard G.992.5 Annex L: Extended Range ADSL2+ M

The device shall comply the standard G.992.5 Annex M: Increased Upload Speed ADSL2+ M

The 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.M

Transmitters 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).M

The device shall support ATM data transport over DSL as in T1.413-5.2, G.992.1-6.2, G.992.2-5 MThe 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).

M

The 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.M

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 M

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.3

and G.992.5 (depending on the standards supported by the operator)M

The 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)M

The 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.O

The 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)M

The 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)M

The 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.M

The Management Plane Procedure feature will be mandatory supported, according to whats described in G.992.5 section 9.4 M

The device shall support Power Management functionalities as in G.992.3, section 9.5 M

The Power Management feature will be completely supported according to whats described in G.992.3 section 9.5, 8.17 and10.3. This is, the three states described in the regulation (L0, L2 and L3) must be supported.

M

The device shall support Programmed reduce framing overhead as in G.992.3 M

The device shall operate ensuring 10e-7 BER or better with a security noise margin M

The device shall support Fast and Interleaved transmission modes M

The device shall support Interleaved transmission mode providing protection against impulsive (INP) noise as in G.992.3,

including Annex K.2.7M


34/134

The 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 wellM

The device shall transport ATM data over ADSL2 using frame format defined in G.992.3-7.6 with programmed reduction of

overhead.M

The device shall transport ATM data over ADSL2+ using frame format defined in G.992.5-7.6 M

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

M

The 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)M

The device shall use CRC checksums to detect errors M

The 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)M

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. M

FEC Reed-Solomon coding support (with 3 words per symbol when G.992.5 is in use) M

The 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.M

The device shall support one-bit constellation encoding M

The 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.9M

The 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) M

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 M

The 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.5M

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 M

The device shall perform Frequency Bands Separation using FDM M

Besides FDM the device can use Echo Cancellation to perform Frenquency Bands Separation but only if FDM interoperability

is guaranteedO

The device shall use DMT modulation with 4,3125 kHz between subcarriers M

The device shall control subcarriers transmission spectrum M

The 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 bufferM

The pilot carrier (276kHz) cannot be modulated or transport user data when using T1.413, G.992.1 or G.992.2 but it does whenusing G.992.3

M

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 M

The 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)M

The 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)M

The device transmitted power spectral density and aggregate power level shall comply ANSI T1.413-1998, section 7.15. M

Device 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.M

Device Initialization Sequence as in G.992.3-8.13, G.992.3, G.992.5 and transactions as in G.994.1-10 M

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

M

The device should support RETRAIN and RESYNC states as in G992.3 Annex D M

The device should support RETRAIN and RESYNC states as in T1.413 Annex A O

EOC (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).M

The 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.M

The device should support In-service performance monitoring and surveillance as in T1.413-8.2 and G.992.1-9.3 M

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

O

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 M


35/134

Values reserved for signalling, OAM functions and resources management shall not be used for data transmission M

The 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.M

The 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.1M

The 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 ISPM

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 ISPM

The device shall include OLR feature Dynamic Rate Adaptation (DRA) as in T1.413 Annex K and G.992.1 Annex G, appendix

IIHR

Operation bit rate can be fixed or adaptative M

The 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-LTsM

Operation bit rate depends on line characteristics so ATM data bit rate will be adapted in 32kbps steps. M

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 ANSI T1413

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 whenusing 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.

M

If the device needs a minimum link length larger than 0km the supplier shall report that value. M

LAN Ethernet

The 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: 1992M

The device shall have Fast Ethernet 802.3u 100baseTX interface (compatible with 10baseT, 100baseTX, 100baseT4 and

optionally with 1000baseTX) with bit rate autonegotiationM

The device Ethernet 802.3 interface shall detect and operate in half/full duplex modes MThe device Ethernet 802.3 interface shall support Auto-MDI/MDI-X feature to detect the connection polarity (10baseT,

100baseTX or optionally 1000base-TX).M

The residential gateway shall offer four Ethernet ports and be able to operate as a switch at Ethernet level. M

WLAN

The wireless interface can be enabled/disabled via software from the user interface and via hardware facility (button). M

The device WLAN Interface shall operate in Access Point / Infrastructure Mode M

The 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.M

The device WLAN Interface shall ensure interoperability with IEEE 802.11b and IEEE 802.11g clients simultaneously with IEEE

802.11n clients.M

The device WLAN Interface shall be able to operate at 2.4GHz frequency. MThe device WLAN Interface shall be able to apply IEEE 802.11n standard features at 2.4GHz frequency band. M

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

M

The device WLAN Interface shall be able to operate using 20MHz channels in 2.4GHz band according to IEEE 802.11n M

The device WLAN Interface may be able to operate using 40MHz bandwidth channels in 2.4GHz band according to IEEE

802.11nO

The device WLAN Interface may have DFS (Dynamic Frequency Selection) feature in 2.4GHz frequency band M

The 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 antennaM

Power spectral density level shall comply with VO-R/12/08.2005-34 in operation bands (2.4GHz). M

The device WLAN Interface transmitter power output may be configured via web-based user interface (supplier should specify

the range) O

The supplier shall specify receiver sensitivity at BER 10-6 in dBm for each frequency band and every single supported rate I


36/134

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).M

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..

HR

The 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.M

The device WLAN Interface shall offer Multiple Input Multiple Output features (MIMO) to take advantage of IEEE 802.11n

improvementsM

The supplier shall specify what has been implemented in terms of MIMO (multiple input and multiple output) according to IEEE

802.11n standardI

The supplier shall specify implemented MIMO chipset I

The 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.M

The supplier shall specify the multiplexing algorithm used in SDM (Spatial Division Multiplexing). I

The 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.O

The supplier shall specify if the device may apply diversity coding techniques (space-time coding) to enhance signal diversity. O

The device WLAN Interface can be configured to be used without encryption M

The device WLAN Interface shall support WEP security M

The device WLAN Interface can be configured to use 64bit key WEP encryption M

The device WLAN Interface can be configured to use 128bit key WEP encryption M

The device WLAN Interface using WEP security can use Open authentication M

The device WLAN Interface using WEP security can use Shared Key authentication. This authentication method is less secure

than Open authentication.M

The WEP key of the WLAN Interface shall be entered in hexadecimal format M

The WEP key of the WLAN Interface may be entered in ASCII format M

The device shall support extended ASCII characters M

The device WLAN Interface shall support WPA security MThe device WLAN Interface shall support WPS security M

WPA user authentication can be performed via PSK (PreShared Key). Personal WPA mode. M

WPA user authentication can be performed via IEEE 802.1x protocol through EAP framework. Enterprise WPA mode. M

WPA 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 RFC4017M

The WPA security shall include RC4-based TKIP (Temporal Key Integrity Protocol) for encryption and rekeying M

The AES re-keying interval may be configured M

The TKIP re-keying interval may be configured O

WPA security shall include MIC (Message Integrity Code) to avoid CRR (Cyclic Redundance Code) modifications by attackers M

WPA security shall include Reply Attack Protection mechanisms M

WPA key of the WLAN Interface shall be entered in hexadecimal format M

WPA key of the WLAN Interface shall be entered in phrase format MWPA key of the WLAN Interface must be random and it will be the same always M

The device WLAN Interface shall support IEEE 802.11i WPA2 security M

WPA2 security shall ensure interoperability with WPA clients M

WPA2 user authentication can be performed via PSK (PreShared Key). Personal WPA2 mode. M

WPA2 user authentication can be performed via IEEE 802.1x protocol through EAP framework. Enterprise WPA2 mode. M

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

M

The WPA2 security shall include AES-based CCMP (Counter Mode with Cipher Block Chaining Message Authentication Code

Protocol) for encryption and rekeyingM

WPA2 security shall include MIC (Message Integrity Code) to avoid CRR (Cyclic Redundance Code) modifications by attackers M

WPA2 security shall include Reply Attack Protection mechanisms M

WPA2 key of the WLAN Interface shall be entered in hexadecimal format M

WPA2 key of the WLAN Interface shall be entered in phrase format M


37/134

The WLAN Interface can be secured using MAC filter to control the access of certain MAC addresses to the wireless network M

The MAC filter shall be able to operate in whitelist mode (only the registered MAC addresses are allowed to access to the

wireless network)M

The MAC filter shall be able to operate in blacklist mode (only the registered MAC addresses are not allowed to access to the

wireless network)O

The device shall support MAC addresses self-learning of wireless clients M

The supplier shall specify maximum number of MAC addresses registered in the access table I

The SSIDs of the WLAN Interface must be WLAN_XXXX by defect, The SSIDs of the WLAN Interface must be WLAN_XXXX

by defect, with "XXXX" the last bytes of MAC Ethernet (all characters of "WLAN_XXXX" must be on upper case)M

The SSIDs of the WLAN Interface can be changed by the user. M

The device WLAN Interface can be configured to not broadcast the SSIDs (SSID hiding feature) M

The device WLAN Interface shall support Multiple SSID feature with a minumum of 4 SSIDs M

When using Multiple SSID, different settings can be asigned to each SSID: encryption, hiding, enabled/disabled, mac

filteringM

The device WLAN Interface shall support IEEE 802.11e QoS features M

The device WLAN Interface shall comply Wifi MultiMedia (WMM) interoperability certification. M

The device WLAN Interface shall support Enhanced DCF Channel Access (EDCA) medium access control method + Transmit

Opportunity (TXOP)M

The device WLAN Interface HCF Controlled Channel Access (HCCA) medium access control method is optional O

The device WLAN Interface shall support Automatic Power Save Delivery (APSD) or other similar mechanism M

The device WLAN Interface may support Block Acknowledgments (BA) to reduce overhead when longer TXOPs are specified O

The device WLAN Interface may be able to send frames with No Acknowledgement (NoAck) service class to avoid

retransmission of highly time-critical data.O

WPS feature as user-friendly method to establish the WiFi configuration shall be provided in PBC (Push Button Configuration)

mode.M

Each 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 configurationM

The device shal l support Adaptive RF (automatic adjustment of signal power and WiFi channel / bandwidth) M

The device shall support Airtime Fairness functionality M

The antennas shall have a signal power of 3dBi M

The 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 otherM

The supplier shall provide the plans that is been implemented to avoid the vulnerability of the WPS functionality to Brute ForceAttack attempts. To have a defined plan to avoid this vulnerability is mandatory.

M


38/134

Details and comments (Spanish) Details and comments (English)

Fully

Compliant

(FC)

Partially

Compliant

(PC)

NonCompliant

(NC)

FC

Puerto DSL RJ11 en el modelo

actual. Para el dispositivo O2DE se

ajustara convenientemente en la

placa adecuada para su tipo de

tecnologa de acceso

DSL port is RJ11 Jack in current model. For the O2DE

model, it would be adjustedFC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

El modo STM no estara soportado STM mode is not supported PC

El modo STM no estara soportado STM mode is not supported NC

FC

FC

El modo PTM no estara soportado PTM mode is not supported NC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


39/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

FC

FC

FC

FC

FC

FC


40/134

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

No soporta 1000Base-TX not support for 1000base-TX FC

FC

FC

FC

FC

FC

FCFC

FC

FC

FC

FC

FC

FC

FC

FC


41/134

FC

Las muestras actuales disponen

de antenas externas, pero el

hardware tambin es totalmente

compatible con antenas internas,

aunque sera necesario modificarel molde BHS actual

Currently, it is external antenna, but the hardware can be

compatible with internal antenna, just modifying the

current BHS housing

FC

2T2R 2T2R FC

FC

2T2R, 2.4G 802.11n ,WiFi alliance

compatiable2T2R, 2.4G 802.11n ,WiFi alliance compatiable FC

BCM43217 BCM43217 FC

FC

OFDM OFDM FC

Previsto para Q4/2012 Plan for Q4/2012 PC

Previsto para Q4/2012 Plan for Q4/2012 PC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FCFC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FCFC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


42/134

FC

FC

FC

FC

256 256 FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


43/134

Cod

TR-LINRQ

TR-LINRQ-GENRQQ

TR-LINRQ-GENRQQ-001

TR-LINRQ-GENRQQ-002

TR-LINRQ-GENRQQ-003

TR-LINRQ-GENRQQ-004

TR-LINRQ-GENRQQ-005

TR-LINRQ-GENRQQ-006

TR-LINRQ-GENRQQ-007

TR-LINRQ-GENRQQ-008

TR-LINRQ-GENRQQ-009

TR-LINRQ-GENRQQ-010

TR-LINRQ-GENRQQ-011

TR-LINRQ-GENRQQ-012

TR-LINRQ-GENRQQ-013

TR-LINRQ-GENRQQ-014

TR-LINRQ-GENRQQ-015

TR-LINRQ-GENRQQ-016

TR-LINRQ-GENRQQ-017

TR-LINRQ-GENRQQ-018

TR-LINRQ-GENRQQ-019

TR-LINRQ-GENRQQ-020

TR-LINRQ-GENRQQ-021

TR-LINRQ-GENRQQ-022

TR-LINRQ-GENRQQ-023

TR-LINRQ-GENRQQ-024

TR-LINRQ-GENRQQ-025

TR-LINRQ-GENRQQ-026

TR-LINRQ-GENRQQ-027

TR-LINRQ-GENRQQ-028

TR-LINRQ-GENRQQ-029

TR-LINRQ-GENRQQ-030

TR-LINRQ-GENRQQ-031

TR-LINRQ-GENRQQ-032


44/134

TR-LINRQ-GENRQQ-033

TR-LINRQ-GENRQQ-034

TR-LINRQ-GENRQQ-035

TR-LINRQ-GENRQQ-036

TR-LINRQ-GENRQQ-037

TR-LINRQ-GENRQQ-038

TR-LINRQ-GENRQQ-039

TR-LINRQ-GENRQQ-040

TR-LINRQ-GENRQQ-041

TR-LINRQ-GENRQQ-042

TR-LINRQ-GENRQQ-043

TR-LINRQ-GENRQQ-044

TR-LINRQ-GENRQQ-045

TR-LINRQ-GENRQQ-046

TR-LINRQ-GENRQQ-047

TR-LINRQ-GENRQQ-048

TR-LINRQ-GENRQQ-049

TR-LINRQ-GENRQQ-050


45/134

TR-LINRQ-GENRQQ-051

TR-LINRQ-GENRQQ-052

TR-LINRQ-GENRQQ-053

TR-LINRQ-GENRQQ-054

TR-LINRQ-GENRQQ-055

TR-LINRQ-GENRQQ-056

TR-LINRQ-GENRQQ-057

TR-LINRQ-GENRQQ-058

TR-LINRQ-GENRQQ-059

TR-LINRQ-GENRQQ-060

TR-LINRQ-GENRQQ-061

TR-LINRQ-GENRQQ-062

TR-LINRQ-GENRQQ-063

TR-LINRQ-GENRQQ-064

TR-LINRQ-GENRQQ-065


46/134

Description Ctg.

Link layer Requirements

General Requirements

The supplier shall specify ARP table maximum size and expiration time of the entries. The number of entries must be higherthan 256 addresses

M

The device should have LAN 802.1p packet priorization (QoS on MAC). The supplier shall provide its roadmap to include this

functionalityHR

The 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.150M

The device shall support ATM layer Physical Medium sublayer (PMD) functions and primitives between PMD and ATM layers

as in ITU-T I.321M

The device shall support ATM layer: Convergence sublayer (CS) as in ITU-T I.321 M

The device shall support ATM layer: Transmission Convergence (TC) sublayer primitives (to/from ATM-PMD and

management plane) as in ITU-T I.413M

The 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.5M

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 proceedingsfor CRD can be used.

M

The device shall support ATM layer: Convergence sublayer. Cell data randomizing as in ITU-T I.432.1 M

ATM cell format as in ITU-T I.361. UNI 2.2 and UNI 3.1 must be Supported M

Default Cell Loss Priority = 0 (upstream cells) for PPPoE over ATM. M

General Flow Control (GFC) bits are not required in the cell header. M

Filling 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 directionsM

The device shall support ATM Virtual Channels in both permanent and semipermanent mode M

The 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)M

ATM 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)M

ATM 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

M

The device shall support al teast 8 PVCs and each one of them may have different configuration (QoS, RIP, NAT, Firewall,

PPPoE sessions...)M

ATM requirements. It shall be possible to attach a PVC to each Ethernet, WLAN or USB interface M

ATM requirements. It shall be possible to attach the same one PVC on more than one interface (Ethernet, WLAN and USB

interface)M

ATM requirements. Minimum 2 PPPoE sessions can be initialized per PVC M

ATM requirements. Static routes can be assigned to different PVCs without the need of a destination IP address. M

ATM requirements. Multicast/Unicast can be enabled over 1 PVC to provide video service M

ATM requirements. The video PVC shall be able to transport 3 multicast/unicast traffic flows M

ATM requirements. The device shall support ATM AAL5 (ITU.363.5) M

ATM requirements. The maximum allowed BER is 10e-7 when using ATM AAL5 (ITU.363.5) M

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

M

The device shall support ATM QoS: service classes as in ITU-T I.371 and ATM Forum Traffic Management 4.1, including

UBR, CBR and VBRM

Support of ATM QoS service Class ABR O

ATM QoS service classes can be configured for each connection from the remote management system M

ATM asymmetric/symmetric data bit rate is achieved depending on the ATM service class used (QoS parameters: SCR, PCR) M

The device shall support ATM QoS Connection Admission Control (CAC) feature. M


47/134

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

M

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.

M

For operation and maintenance purposes the supplier of the ADSL modem and the type of the modem shall be uniquely

identified by information stored in the ATU-R registers ATU-R supplier ID (Register #0), ATU-R version number minus one(Register #1), ATU-R serial number (Register #2) as specified in the ITU-T recommendation [G.992.1].

M

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 test resultshould be 0x00. If the self test fails, the result should be a value other than 0x00.

O

Link layer for Internet service: The device shal l support PPP l ine layer protocol in accordance with RFC791 M

Link layer for Internet service: The device shall support PPP control protocol for IP (IPCP) in accordance with RFC1332 M

Link layer for Internet service: The device shall not negotiate other network protocol over PPP (IPX, X25) M

Link layer for Internet service. PPP. PAP authentication for the PPP protocol (IETF RFC1334) M

Link layer for Internet service. PPP. CHAP authentication for the PPP protocol (IETF RFC1994) M

Link layer for Internet service. PPP. The supplier shall describe if the device supports forced PPP authentication: if it is

configured to authenticate using only CHAP, it shall inform the BRAS to use CHAP if it tries to use PAPI

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

I

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.

I

The 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).M

The PPPoE PADI may be only sent to ADSL port. PPPoE PADI must not be sent to any LAN port when is not allowed M

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.

M

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.

M

The 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

M

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

M


48/134

Link layer for Internet service. The supplier shall describe allowed range and default value of maximum routable unit (MRU).

Default value 1492 is expectedI

Link layer for Internet service. The supplier shall describe allowed range and default value of maximum segment size (MSS).

Default value 1452 is expectedI

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)

M

Spanning tree protocol support in the link layer for TV service. This protocol bridging shall be done with no changes inside

STP frames.

I

Link layer for TV service. MAC table: limitations and acquiring and releasing rules I

Link layer for TV service. FCS checking: rule to check frame integrity I

Link layer for TV service. The modem shall support flooding broadcast M

Link layer for TV service. The modem shall support bridging all DHCP frames M

Link layer for TV service. The modem shall support flooding of multicast frames M

Link layer for TV service. The modem shall support flooding of unknown unicast frames M

The device shall support a functionality to use prioritisation of outgoing packets between the following interfaces:

- DSL Port Interface

- LAN Port Interface

M

The device shall support diffserv M

The device shall support the configuration of link type and connection type as per appendix B of TR098 on these VCs. M

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.

M

The 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 methodsM


49/134

Details and comments

(Spanish)Details and comments (English)

Fully Compliant (FC)

Partially Compliant (PC)

Non Compliant (NC)

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

FC

FC


50/134

FC

FC

FC

Sera implementable en

base a una especificacin

ms detallada

Implemented based on a detailed

specPC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


51/134

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC


52/134

Cod

TR-NETRQ

TR-NETRQ-IPCON

TR-NETRQ-IPCON-001

TR-NETRQ-IPCON-002

TR-NETRQ-IPCON-003

TR-NETRQ-IPCON-004

TR-NETRQ-IPCON-005

TR-NETRQ-IPCON-006

TR-NETRQ-IPCON-007

TR-NETRQ-IPCON-008

TR-NETRQ-IPCON-009

TR-NETRQ-IPCON-010

TR-NETRQ-IPCON-011

TR-NETRQ-IPCON-012

TR-NETRQ-IPCON-013


53/134

TR-NETRQ-IPCON-014

TR-NETRQ-IPCON-015

TR-NETRQ-IPCON-016

TR-NETRQ-IPCON-017

TR-NETRQ-IPCON-018

TR-NETRQ-IPCON-019

TR-NETRQ-IPCON-020

TR-NETRQ-IPCON-021

TR-NETRQ-IPCON-022

TR-NETRQ-ROUTI

TR-NETRQ-ROUTI-001

TR-NETRQ-ROUTI-002

TR-NETRQ-ROUTI-003

TR-NETRQ-ROUTI-004

TR-NETRQ-ROUTI-005

TR-NETRQ-ROUTI-006

TR-NETRQ-ROUTI-007

TR-NETRQ-ROUTI-008

TR-NETRQ-ROUTI-009

TR-NETRQ-ROUTI-010

TR-NETRQ-ROUTI-011

TR-NETRQ-ROUTI-012

TR-NETRQ-ROUTI-013

TR-NETRQ-ROUTI-014

TR-NETRQ-ROUTI-015

TR-NETRQ-ROUTI-016

TR-NETRQ-ROUTI-017

TR-NETRQ-ROUTI-018

TR-NETRQ-ROUTI-019

TR-NETRQ-ROUTI-020

TR-NETRQ-ROUTI-021


54/134

TR-NETRQ-ROUTI-022

TR-NETRQ-ROUTI-023

TR-NETRQ-ROUTI-024

TR-NETRQ-ROUTI-025

TR-NETRQ-ROUTI-026

TR-NETRQ-ROUTI-027

TR-NETRQ-ROUTI-028TR-NETRQ-ROUTI-029

TR-NETRQ-ROUTI-030

TR-NETRQ-ROUTI-031

TR-NETRQ-ROUTI-032

TR-NETRQ-ROUTI-033

TR-NETRQ-ROUTI-034

TR-NETRQ-ROUTI-035

TR-NETRQ-ROUTI-036

TR-NETRQ-ROUTI-037

TR-NETRQ-SECUR

TR-NETRQ-SECUR-001

TR-NETRQ-SECUR-002

TR-NETRQ-SECUR-003

TR-NETRQ-SECUR-004

TR-NETRQ-SECUR-005

TR-NETRQ-SECUR-006

TR-NETRQ-SECUR-007

TR-NETRQ-SECUR-008

TR-NETRQ-SECUR-009

TR-NETRQ-SECUR-010

TR-NETRQ-SECUR-019

TR-NETRQ-SECUR-020

TR-NETRQ-OTHER

TR-NETRQ-OTHER-001

TR-NETRQ-OTHER-002

TR-NETRQ-OTHER-003

TR-NETRQ-OTHER-004

TR-NETRQ-OTHER-005


55/134

TR-NETRQ-OTHER-006

TR-NETRQ-OTHER-007

TR-NETRQ-OTHER-008

TR-NETRQ-OTHER-009

TR-NETRQ-OTHER-010

TR-NETRQ-OTHER-011

TR-NETRQ-OTHER-012

TR-NETRQ-OTHER-013

TR-NETRQ-OTHER-014

TR-NETRQ-OTHER-015

TR-NETRQ-OTHER-016

TR-NETRQ-OTHER-017

TR-NETRQ-OTHER-018

TR-NETRQ-OTHER-019

TR-NETRQ-OTHER-020

TR-NETRQ-OTHER-021

TR-NETRQ-OTHER-022

TR-NETRQ-OTHER-023

TR-NETRQ-OTHER-024

TR-NETRQ-OTHER-025

TR-NETRQ-OTHER-026

TR-NETRQ-OTHER-027

TR-NETRQ-OTHER-028

TR-NETRQ-OTHER-029

TR-NETRQ-OTHER-030


56/134

TR-NETRQ-OTHER-031

TR-NETRQ-OTHER-032

TR-NETRQ-OTHER-033

TR-NETRQ-OTHER-034

TR-NETRQ-OTHER-035

TR-NETRQ-OTHER-036

TR-NETRQ-OTHER-037


57/134

Description Ctg.

Network Layer Requirements

IP Configurations

The device shall support RFC791 IP protocol (v4) MThe 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

M

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

M

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

M

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

M

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.

I

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 yoursolution. Specify model and release and if it were possible the configuration tested.

I

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

I

The provider shall inform regarding QoS SUPPORT the following information:

- IPv6 Flow Classification,

- IPv6 Flow Policy

- Queue management

- Marking Traffic Class

I

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

I

The device can be configured in IP mode: RFC1483/2684 routed. IPoA (RFC1577) M

The device can be configured in IP mode: RFC1483/2684 routed. IPoE/MER (MAC Encapsulated Routing). M

The device can be configured in IP mode: RFC1483/2684 bridged. EthoA. M


58/134

The device can be configured in IP mode: RFC1483/2684 bridged. EthoA bridging using IEEE802.1d MAC bridging supporting

a minimum of 272 MAC addressesM

The 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 protocolsM

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).

M

IP configuration modes PPPoA: Session Terminated on Inactivity Timeout M

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).

M

IP configuration modes PPPoE: Session Terminated on Inactivity Timeout M

Secondary IP addresses can be configured in all the device interfaces M

IP subnets can be defined and attached to the LAN interfaces M

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.

M

Routing

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 WLANinterface

M

The IP Routing functionality of the device shall use IP Routing Table. M

The device shall support static routing M

The supplier shall describe if the device supports establishing of static routing entries through management interface I

The device shall support dynamic routing M

Dynamic routing via RIPv1 and RIPv2 protocol in both LAN and WAN Interfaces M

The device should have ARP proxy functionality HR

The device shall support ARP cache as defined in RFC 826 M

The routing functionality of the device shall support the Address Resolution Protocol (ARP) according the specification RFC

826.M

The 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 disabledM

The 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 directionsM

The 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 sessionI

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].M

The PAT functionality shall be able to carry out TCP/UDP mappings of external addresses and ports to different internal

addresses and portsM

PAT minimum table size of 80 entries. Vendor shall specify maximum number of entries. M

The PAT funcionatily shall support DMZ M

NAT shall be transparent for IPSec (NAT traversal): VPN pass-through M

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...)

M

The 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 disconnectedM

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

O

Both in bridged or routed modes throughtput between interfaces must comply:

- 16Mbps between PPP/WAN and LAN

- 16Mbps between PPP/WAN and WLAN

M


59/134

The device shall support IP fragmentation M

The routing functionality of the device shall support the Internet Control Message Protocol (ICMP) according the specification

RFC 826.M

The number of sessions supported by UDP should not be lower than 512 no matter how long the packet is M

The device shall support IETF RFC 0894 Standards for the Transmission of IP Datagrams over Ethernet Networks M

The device shall support IETF RFC 0922 Broadcasting Internet Datagrams in the Presence of Subnets M

The device shall support IETF RFC 0950 Internet Standard Subnetting Procedure M

The device shall support IETF RFC 1009 Requirements for Internet Gateways (Link Layer issues only) MThe device shall support IETF RFC 1042 Standard for the Transmission of IP Datagrams over IEEE 802 Networks M

The device shall support IETF RFC 1112 Host Extensions for IP Multicasting M

The device shall support IETF RFC 1122 Requirements for Internet Hosts Communication Layers M

The device shall support IETF RFC 1123 Requirements for Internet Hosts Application and Support M

The device shall support IETF RFC 1256 ICMP Router Discovery Messages (Router Specification only) M

The device shall support IETF RFC 1519 Classless InterDomain Routing (CIDR) M

The device shall support IETF RFC 1812 Requirements for IP Version 4 Routers M

The device shall support IETF RFC 1918 Address Allocation for Private Internets M

The device shall support IETF RFC 3600 Internet Official Protocol Standards M

Security

Firewall 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

M

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.

M

Firewall shall support port scanning protection M

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).M

The device shall not reply to ICMP echo requests by default but it can be allowed M

The supplier will describe other IP firewall functionalities I

Firewall may be provided as external application installed in the user equipment O

The device shall support Access Control List: limited range of IP addresses (Management Center) can remotely manage the

device (telnet, ftp, tftp...)

M

The device shall support a functionality for Stateful Packet Inspection (SPI) fi rewall 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

M

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 Interfac

nucom_bhs_adsl2_tech_reqs_rev7

Documents