BelAir Ericsson Wi-Fi RFQ Technical Responses Final

BelAir Networks Confidential 1 of 48 13 November, 2011

BelAir Networks Technical Responses

To

Ericsson TECHNICAL SPECFICIATION

FOR WI-FI MODULE RFP

Document Date: 13 November, 2011 Document Version: Final, v1.0 Security Status: Confidential Contact: Kevin Cordell

Vice President WW Channels Phone: +1.443.398.6693 Email: [email protected]

David Park

VP System Architecture Phone: +1.613.852.1967

Email: [email protected]

© Copyright 2002-2011 BelAir Networks Inc. The information contained in this document is Confidential and Proprietary to BelAir Networks.

Errors and Omissions Excepted. Specifications may be subject to change.


Table of Contents Table of Contents .......................................................................................................................... 2 Table of Figures ............................................................................................................................ 3 Summary ....................................................................................................................................... 5 1 General requirements (Section 1.0) ...................................................................................... 6

1.1 Regulatory requirements (Section 1.1) .......................................................................... 6 1.2 Interoperability (Wi-Fi alliance certification program) (Section 1.2) ............................... 8 1.3 Quality (Section 1.3) ...................................................................................................... 9

2 Mechanical requirements (Section 2.0) ............................................................................... 11 2.1 Mechanical design (Section 2.1) ................................................................................. 11 2.2 Environment (Section 2.2) ........................................................................................... 13 2.3 Antennas (Section 2.3) ................................................................................................ 14 2.4 Cable / Connectors (Section 2.4) ................................................................................ 16 2.5 Test Point (Section 2.5) ............................................................................................... 16

3 Electrical requirements (Section 3.0) .................................................................................. 18 3.1 Power consumption (Section 3.1) ............................................................................... 18 3.2 Power supply (Section 3.2) ......................................................................................... 19 3.3 Control interface (Section 3.3) ..................................................................................... 20 3.4 Communication interface (Section 3.4) ....................................................................... 20

4 Radio requirements (Section 4.0) ....................................................................................... 21 4.1 Transmitter output power (Section 4.1) ....................................................................... 22 4.2 Transmitter spurious emission (Section 4.2) ............................................................... 23 4.3 Receiver blocking (Section 4.3) ................................................................................... 26

5 Transmission requirements (Section 5.0) ........................................................................... 31 5.1 Authentication (5.1) ..................................................................................................... 31 5.2 Topology and link discovery (Section 5.2) ................................................................... 32 5.3 Tunnels, Security and Encryption (Section 5.3) .......................................................... 32 5.4 QoS (Section 5.4) ........................................................................................................ 33 5.5 Transport Configuration (Section 5.5) ......................................................................... 34 5.6 Access Gateway Address from Small-RBS (Section 5.6) ........................................... 35 5.7 GPS positioning (Section 5.7) ..................................................................................... 35 5.8 Status messages (Section 5.8) ................................................................................... 39 5.9 Wi-Fi as backhaul (Section 5.9) .................................................................................. 39

6 MMI requirements (Section 6.0) .......................................................................................... 40 6.1 Button and LED-indicators (Section 6.1) ..................................................................... 40 6.2 Messages to cellular (Section 6.2) .............................................................................. 40

7 Security (Section 7.0) .......................................................................................................... 41 8 Test and verification (Section 8.0) ....................................................................................... 43

8.1 Wi-Fi-module production test (Section 8.1) ................................................................. 43 8.2 Wi-Fi-module type approval (Section 8.2) ................................................................... 44 8.3 Small-RBS verification (Section 8.3) ........................................................................... 44 8.4 Small-RBS type approval (Section 8.4) ....................................................................... 46 8.5 Small-RBS production test (Section 8.5) ..................................................................... 46

9 Summary ............................................................................................................................. 47


Table of Figures Figure 1: Wi-Fi Certificate for the BelAir20E/EO ........................................................................... 9 Figure 2: Wi-Fi Certificate for the BelAir100NE/SNE .................................................................... 9 Figure 3: 10cm x 20cm Wi-Fi Module – Conceptual Layout ....................................................... 11 Figure 4: Wi-Fi Module Total Thickness ..................................................................................... 12 Figure 5: BelAir DRUe Card Thermal Interfaces ......................................................................... 12 Figure 6: BelAir100SNE Chassis Thermal Interfaces ................................................................. 13 Figure 7: Wi-Fi Module 3x3 MIMO Antenna ................................................................................ 14 Figure 8: 5 GHz Antenna Elevation Radiation Pattern ................................................................ 15 Figure 9: 5GHz Antenna Azimuth Radiation Pattern .................................................................. 15 Figure 10: 2.4GHz Antenna Azimuth Radiation Pattern ............................................................. 16 Figure 10: RF filtering architecture for co-location ...................................................................... 21 Figure 12: RF filtering specifications ........................................................................................... 22 Figure 11: NMS map screenshot ................................................................................................ 36 Figure 12: Detailed NMS screenshots ........................................................................................ 36 Figure 13: BelView Business Intelligence Module ...................................................................... 38 Figure 14: BelView Synthetic Client ............................................................................................ 38 Figure 15: BelView Heat Maps ................................................................................................... 38 Figure 16: Wi-Fi-Module Production Test Setup ......................................................................... 43 Figure 17: Receive Sensitivity Test Setup .................................................................................. 45 Figure 18: Small-RBS Wi-Fi Throughput Test Setup .................................................................. 45 Figure 19: Proposed Test Setup for Production Testing of Integrated Wi-Fi Module.................. 46


The BelAir Networks Product Family

Protected by U.S. Patents: 7,660,559; 7,545,782; 7,171,223;7,164,667; 7,154,356; 7,030,712; D501,195; 7,433,343; 7,162,234; 7,433,361. Patents pending in the U.S. and other countries. BelAir Networks, the BelAir logo, BelAir200, BelAir100, BelAir20, BelView and BelView NMS are trademarks of BelAir Networks Inc.


Summary This document includes responses to requirements outlined in the Ericsson Technical Specification for Wi-Fi-Module RFQ, Document No. 2/1056-FCP 121 8519 Uen, Rev A, 2011-10-28.

Each section represents the section from the Ericsson requirements document and the section heading numeration is identical to the Ericsson’s original document. Original Ericsson requirement text is in italic. BelAir responses begin with “ANSWER:” followed by compliancy status. Additional solution description as applicable is also included.

BelAir has presented a compliant response to Ericsson’s requirements.


1 General requirements (Section 1.0) The Wi-Fi-module should fulfill following standards:

IEEE 802.11-2007 IEEE 802.11n-2009

The target is a product that fulfills following: IEEE 802.11g IEEE 802.11n, 3x3 MIMO, 3 spatial streams, 40 MHz channel bandwidth Support 2.4GHz and 5GHz simultaneously

ANSWER: Fully Compliant The BelAir family of products is fully 802.11 standards compliant. In addition, all BelAir radios fully support both 2.4 GHz and 5 GHz dual band / dual radio concurrent operation with the capability to activate individual bands or both simultaneously. Our latest generation of products, the BelAir20E/EO and Belair100NE/SNE are fully compliant to the 802.11-2007 and 802.11n-2009 with backwards compatibility to 802.11a/b/g/n. The BelAir100NE/SNE product line includes the industry’s first integration of the IEEE 802.11n and 3x3 MIMO with Beam Forming technology. BelAir will leverage and re-utilize existing technology to develop the Wi-Fi-module, therefore ensuring the module is developed to full standards to IEEE 802.11-2007 and the latest IEEE 802.11n-2009 standard compliancy. As with other BelAir radios, the BelAir will include in the Wi-Fi module the 2.4 GHz and 5.8 GHz dual band / Dual Radio concurrent operation technology with the capability to activate either one band only or both simultaneously. The BelAir Wi-Fi Module will also fully support the IEEE 802.11n 3x3 MIMO with Beam Forming technology, utilizing BelAir’s innovative antenna technology described in Section 2.3.

1.1 Regulatory requirements (Section 1.1) The module shall in general, be regulatory approved for global market access. Main markets required regulatory approvals are specified below. For all other markets that not accept any of the below approvals, where special requirements exists, shall also be prepared to meet necessary requirements. ANSWER: Fully Compliant BelAir products are sold throughout the world and hence conform to regulatory requirements from many different countries. BelAir has a well-established development process that ensures regulatory requirements are met or exceeded, and efficient certification verification process that minimizes/optimizes the time to obtain regulatory approvals. In cases where the BelAir product lacks certification for a certain marketplace, BelAir will work with Ericsson and obtain the necessary approvals. In this proposal, BelAir has proposed several variants that meet or exceed the requirements for global markets. This includes a radio that can meet the full FCC specifications meeting all


emission specifications at 4W EIRP in 2.4GHz. BelAir has also provided pricing for alternate models that meet a 1W EIRP and 100mW EU specified EIRP.

1.1.1 European market (Section 1.1.1) The module shall fulfill relevant parts of 1999/5/EC R&TTE directive, according to Table 1.

ANSWER: Fully Compliant BelAir has well established development and certification processes to ensure full compliance to many regulatory requirements, including the European market. BelAir products are sold and deployed worldwide. This proposal meets the EU requirements.

Radio EN 300 328 (2.4 GHz frequency band

Fully Compliant

EN 301 893 (5 GHz frequency band)

Fully Compliant

EMC EN 301 489-1 Fully Compliant EN 301 489-17 Fully Compliant

Safety EN/IEC 60950-1 Fully Compliant RF Health/SAR ICNIRP guidelines Fully Compliant to EN

50385, which calls for EN 50385, that uses ICNIRP guidelines

1.1.2 North American market (Section 1.1.2) The module shall fulfill requirements in Table 2.


ANSWER: Fully Compliant BelAir has well established development and certification processes to ensure full compliance to many regulatory requirements, including the North American market. BelAir products are sold and deployed worldwide. This proposal meets the North American requirements as a full 4W EIRP.

Radio FCC CFR 47 part 15.247 subpart C Fully Compliant IC RSS210 Fully Compliant

EMC FCC CFR 47 part 15 subpart B Fully Compliant Safety ANSI/UL60950-1 Fully Compliant RF Health/SAR FCC OET Bulletin 65 supplement C Fully Compliant

1.1.3 Japan market (Section 1.1.3) The module shall fulfill requirements in Table 3.

ANSWER: Fully Compliant BelAir has well established development and certification processes to ensure full compliance to many regulatory requirements, including the Japanese market. BelAir products are sold and deployed worldwide. This proposal meets the Japan requirements.

Radio Japanese Radio Law, Telec / STD-66 Fully Compliant Safety ANSI/UL60950-1 Fully Compliant

1.2 Interoperability (Wi-Fi alliance certification program) (Section 1.2) The module shall be Wi-Fi certified for the relevant IEEE 802.11 standards (see above). ANSWER: Fully Compliant All BelAir products are Wi-Fi Alliance Certified. BelAir has an established development process for designing per Wi-Fi standards and obtaining Wi-Fi Alliance Certification. The Wi-Fi module will be designed per Wi-Fi standards and have Wi-Fi Alliance Certification prior to production. The following are the Wi-Fi Alliance certificates for the BelAir20E/EO and the BelAir100N/SNE, which are the originators of the design for the Wi-Fi module.


Figure 1: Wi-Fi Certificate for the BelAir20E/EO

Figure 2: Wi-Fi Certificate for the BelAir100NE/SNE

1.3 Quality (Section 1.3) The technical lifetime of the module shall be at least 5 years. The return rate shall be < 0.5%.


The above should be interpreted as a really low return rate the first 5 years. After this time, the product is exchanged. We are considering not repairing faulty units, just replacing them. This means that we will only send back faulty units for root-cause analysis in order to improve product quality. ANSWER: Fully Compliant BelAir’s Hardware return rate is typically well under 0.5% for our cards and we have over 9 years of experience of shipping carrier grade outdoor Wi-Fi cards to base this on. For example, BelAir’s last 12-month return rate for our 802.11n full FCC specification MIMO 4W EIRP outdoor card is 0.09%. This is a strong indicator of the high quality built into our designs and product lines as these products are deployed in harsh environments worldwide and subject to extremes of temperature, humidity and vibration. Through continuous process improvements, BelAir’s goal is to improve the reliability of our products with each new release, while retaining their market competitiveness.


2 Mechanical requirements (Section 2.0)

2.1 Mechanical design (Section 2.1) The maximum size of the module is 100x200 mm. ANSWER: Fully Compliant The BelAir Wi-Fi module will be 100mm x 200mm with a maximum thickness of 20 mm, antenna inclusive. Figure 3 shows the planned block layout model of the Wi-Fi module which is based on actual size of the relevant blocks from our current card portfolio. BelAir’s proposal is for a full FCC specification card with cellular co-location filters in this size.

Figure 3: 10cm x 20cm Wi-Fi Module – Conceptual Layout

The target for the thickness is 21 mm.

ANSWER: Fully Compliant

The bottom side of the PCB will house only components of 2.5 mm height or less. Coupled with innovative layout analysis and cutting edge antenna technology, BelAir is able to keep the total height of the module to less than 21 mm.


Figure 4: Wi-Fi Module Total Thickness

The heat will be dissipated by using a gap pad via the bottom of the Wi-Fi___33-module. ANSWER: Fully Compliant All BelAir products include passive cooling management techniques that greatly reduce the system’s complexity (no fans or HVAC systems are required). BelAir has extensive experience with these techniques and is on our 4th generation of products using this technology. Figure 5 clearly demonstrates the thermal management engineering considerations present within the BelAir radio design (BelAir100SNE example). The indicated surface areas interface to machined flat surfaces on the chassis (see Figure 6), which allows thermal conduction to the convection-based cooling fins located on the exterior of the chassis. Similar thermal management techniques will be applied to the Wi-Fi Module to enable this passive cooling management approach that is implemented in all BelAir products. If required, BelAir can provide thermal information at the interface point(s).

Figure 5: BelAir DRUe Card Thermal Interfaces

Thermal Contact for Radios

Thermal Contact for Power


Figure 6: BelAir100SNE Chassis Thermal Interfaces

2.2 Environment (Section 2.2) The module shall fulfill following environment conditions according to Table 4.

ANSWER: Fully Compliant BelAir units are designed to operate in harsh environments. They undergo severe environmental testing to ensure compliance to strict environmental standards. BelAir products have been deployed in all climate types, from desert conditions in Saudi Arabia to extreme cold conditions in Alaska’s North Slopes.

All BelAir AP's are designed with components rated at +85°C (185F) External temperature operating range: -40°C (-40F) to +65°C (+149F) Maximum humidity: 95% (non-condensing) Complete BelAir products are rated to IP66/IP67

As per the previous section, BelAir implementation of passive conductive/convective thermal management techniques allows the units to operate over a broad range of temperatures.

Thermal Interfaces


2.3 Antennas (Section 2.3) The Wi-Fi-module shall have a build in sector antenna. A preliminary specification for the radiation of the antenna is specified below in Table 5.

ANSWER: Fully Compliant BelAir proposes a fully integrated 3x3 MIMO, beamforming, compliant internal antenna, with 10cm x 20cm dimensions. The antenna would overlay on top of the Wi-Fi Module card, and be part of the Wi-Fi Module assembly. BelAir also provides a range of Omni-directional beamforming antennas should Ericsson wish to include these in a product offer.

Figure 7: Wi-Fi Module 3*3 MIMO Antenna

5 GHz Antenna The 5 GHz Antenna will have a 70o azimuth beamwidth. The elevation pattern is shown below, and will provide street level and first/second floor building coverage. The elevation beamwidth will be 35o, with an electrical down-tilt of 8o to meet IR2007.


Figure 8: 5 GHz Antenna Elevation Radiation Pattern

Figure 9: 5GHz Antenna Azimuth Radiation Pattern

2.4GHz Antenna 2.4 GHz Antenna azimuth pattern will be similar to that shown below, but will employ a higher dielectric material to achieve wider elevation of 70 degrees. Vertical elevation will be >35 degrees using a stacked two element design.


Figure 10: 2.4GHz Antenna Azimuth Radiation Pattern

2.4 Cable / Connectors (Section 2.4) The module is connected to the main board of the basestation using a ribbon cable. ANSWER: Fully Compliant BelAir will design the Wi-Fi Module with a ribbon cable. BelAir is very familiar with ribbon cable technology and is commonly used throughout our product line. The length of the cable is maximum 150 mm. ANSWER: Fully Compliant The length of the ribbon cable will not exceed 150 mm. Connector type is TBD. ANSWER: Fully Compliant BelAir is well versed in multiple connector technologies for interconnecting cards in outdoor products and can accommodate any types. BelAir will share our experience and expertise on the subject matter with Ericsson and select the appropriate connector to ensure performance is not compromised. Connectors to external antennas are not used. ANSWER: Fully Compliant The Wi-Fi Module will not include a connector for external antennas. However, it is also possible to make a variation that will support external antennas.

2.5 Test Point (Section 2.5) For signal integrity testing, test points are required for all interface signals between the Wi-Fi-module and the Small-RBS board. Preferred test point size is 0.8mm. All test points shall be


accessible from one side of the Wi-Fi-module. Mechanical tear down (removing a lid or similar) is expected during the R&D testing. ANSWER: Fully Compliant BelAir products are designed with 0.8mm test points. The Wi-Fi Module test points will be located on one side to facilitate accessibility. At the onset of this program, BelAir recommends we hold a technical interchange session to discuss the exact locations of the test points. BelAir will share our experience in the testing of signal integrity with Ericsson to ensure the correct test approach is taken.


3 Electrical requirements (Section 3.0)

3.1 Power consumption (Section 3.1) The power consumption should be kept as low as possible. State typical and maximum power consumption. ANSWER: Fully Compliant Tx RF output power levels are dependent on the DC power consumption of the RF power amplifiers

Higher output power requires more DC power

Efficiency of power amplifiers varies from 8‐14%

There are 2 radios, each with 3 transmit chains and the radios operate simultaneously.

Overall PCB power consumption has a direct effect on estimated Tx output power per chain for the Wi-Fi card. The maximum DC power draw from the power supply occurs when both radios are transmitting. However, radios do not operate with 100% duty cycle, so the average DC power consumption is much less than the maximum:

80% Tx duty cycle is approximately the realistic maximum when running continuous

downstream traffic

10‐50% Tx duty cycle will more closely reflect actual average power consumption of the module

Power supply must be capable of providing the peak current, but the average current should be used to define the overall power and heat dissipation. With the above defined, the following table (Table 1: DC Power) captures the power consumption levels matched up to Transmit power levels options


Radio Max(peak)DCPower

AverageDCPower

2.4GHz conductedTxPowerperChain

5GHzconductedTxPowerperChain

SoC/MACInternalPA

6.8W 4.4W 15‐17dBm(Totalconductedpower21.7dBm)

10‐12dBm

MidPerformanceExternalPA

14.7W 8.8W 18‐20dBm(totalconductedpower24.7dBm)

17‐19dBm

HighPerformanceExternalPA

28.1W 15.6W 23‐25dBm(totalconductedpower29.7dBm)

22‐24dBm

Table 1: DC Power

3.2 Power supply (Section 3.2) Power supply requirements shall be according to Table 6.

ANSWER: Fully Compliant As described in the previous section, DC power is dependent on several factors, including required Transmit power. Table 1 includes support for the power supply/max current as defined in this requirement. However, limiting the power to that level will generate mid-performance TX characteristics. BelAir will work with Ericsson to design a card with the right balance of ultimate performance and power consumption. BelAir can support 5.5V or alternate higher voltages and will work with Ericsson to determine the most optimal way of powering the module to deliver the best possible output power.


3.3 Control interface (Section 3.3)

3.3.1 Reset signal (Section 3.3.1) The Wi-Fi-module has a reset input signal. This is used to make a hard reset of the Wi-Fi-module. This is intended to be used at power on. Electrical requirement as stated in Table 7.

ANSWER: Fully Compliant BelAir will include a reset input signal into the Wi-Fi Module design, based on the Table 7 requirements. This is simple to design and implement.

3.4 Communication interface (Section 3.4) All communication with module is using one SGMII interface. The characteristics of the interface are as follows: Bi-directional differential SERDES pairs (TX and RX), connected to EMAC port which is IEEE 802.3 compliant.

100O differential lines, termination TBD

SGMII is slave in Wi‐Fi‐module

Full duplex 1000Mbps forced configuration.

SGMII receiver equalizer configuration (EQ), differential output de‐emphasis and differential

output swing expected to be configurable in Wi‐Fi‐module. Cable and connector loss is

compensated.

ANSWER: Fully Compliant BelAir will design the Wi-Fi Module with one SGMII interface, with the characteristics outlined above. BelAir has significant experience with this type of design and often uses card to card magnetic-less ribbon cable interconnect in our existing products. BelAir will work with Ericsson to select the appropriate connector and ribbon, to ensure there are enough grounds between signals, thereby keeping the impedance correct.


4 Radio requirements (Section 4.0)

General requirements are stated in Chapter 1. Some other requirements are needed to guarantee following:

Good Wi‐Fi performance

The Wi‐Fi‐transmitter does not degrade cellular radio performance

The Wi‐Fi‐receiver is not degraded due to cellular radio performance

The Small‐RBS platform is designed to cover all defined 3GPP frequency bands between 700 MHz and 2.7 GHz. This means that the Wi‐Fi‐module must be designed to handle coexistence with all 3GPP bands. ANSWER: Fully Compliant

BelAir’s Wi-Fi technology has industry leading performance. The cards are designed to ensure that there is no interference from Wi-Fi to cellular or from cellular to Wi-Fi. All 3GPP bands have been included in this analysis. BelAir already produces products that are co-located with cellular basestations, including Macrocells and understands the requirements and designs needed to achieve this.

Figure 11: RF filtering architecture for co-location

• Transmit Path Wi-Fi chip has direct RF output Filter 1 reduces out-of-band noise and spurious from chipset output so that they

are not amplified by the power amplifier Power amplifier amplifies wanted RF signal Filter 3 reduces power amplifier out-of-band noise and spurious signals in the

cellular bands so there is no interference to cellular Rx • Receive Path

Filter 3 reduces incoming RF out-of-band signals from the cellular Tx so that they do not overload the LNA


Filter 2 provides additional out-of-band signal rejection to ensure that the Wi-Fi chip Rx input is not overloaded so that there is no Rx sensitivity degradation

Location of Filter 2 could be moved ahead of LNA, but doing so reduces the Rx sensitivity as the filter loss directly increases the receiver noise figure

A typical RF filter that is used on the card is shown in Figure 12: RF filtering specifications. Two of these are used in cascade to achieve the required performance.

Figure 12: RF filtering specifications

4.1 Transmitter output power (Section 4.1)

It is desired to have as much output power as possible from the Wi‐Fi‐module, which depends on what is allowed on different markets.

State suggested maximum output power.


BelAir’s Wi-Fi technology can support up to the full 4W EIRP allowed under FCC rules. We have proposed a full 4W EIRP (25dBm per chain, 29.7dBm total conducted power card) to ensure the maximum possible performance. This card can be used as a single world card.


If, for pricing or power consumption reasons, Ericsson desires to have a lower powered card, BelAir has also proposed a moderate power (1W EIRP, 20dBm conducted per chain) and a low power (100mW EIRP, 17dBm per chain) card as part of this proposal. BelAir will work with Ericsson to deliver the optimal blend of power and performance. In the interest of having a single worldwide card we, would propose the higher power card initially.

4.2 Transmitter spurious emission (Section 4.2)

The transmitter requirement is stated in documents listed in Chapter 1. These requirements are not good enough for the module because the attenuation between the cellular and Wi‐Fi radio is limited. In order to guarantee good coexistence between the radios, additional requirements are needed. ANSWER: Fully Compliant BelAir has included additional Transmit filtering to ensure that the cellular and Wi-Fi radio can co-exist without degradation. This filtering reduces the Wi-Fi out of band emissions to below the level where they would inject noise into the cellular front end.

4.2.1 Spurious emission for 2.4GHz radio (Section 4.2.1)

The transmitter spurious emission calculation is based on assumptions listed in Table 8.

Spurious emission requirement in addition to regulatory requirements stated in Chapter 1 is shown in Table 9 and Figure 1. Requirements for coexistence with Wi‐Fi @5GHz is not included and must be added by vendor.


BelAir has designed the radios to accommodate 20dB isolation between the antennas



BelAir has designed the radios to meet these emissions limits for colocation.

4.2.2 Spurious emission for 5GHz radio (Section 4.2.2) The transmitter spurious emission calculation is based on assumptions listed in Table 8.


Spurious emission requirement in addition to regulatory requirements stated in Chapter 1 is shown in Table 11 and Figure 2. Requirements for coexistence with Wi-Fi @2.4GHz is not included and must be added by vendor. ANSWER: Fully Compliant BelAir has included additional Transmit filtering to ensure that the cellular and 5GHz Wi-Fi radio can co-exist without degradation.


4.3 Receiver blocking (Section 4.3) The receiver requirement is stated in documents listed in Chapter 1. These requirements are not good enough for the module because the attenuation between the cellular and Wi-Fi radio is limited. In order to guarantee good coexistence between the radios, additional blocking requirements are needed.


ANSWER: Fully Compliant BelAir has included additional Rx filtering to ensure that the cellular and Wi-Fi radios can co-exist without degradation.

4.3.1 Outband blocking for 2.4 GHz radio (Section 4.3.1) The receiver blocking calculation is based on assumptions listed in Table 12.

Receiver blocking requirement in addition to regulatory requirements stated in Chapter 1 is shown in Table 13, Figure 3 and Figure 4Error! Reference source not found.. Requirements for coexistence with Wi-Fi @5GHz is not included and must be added by vendor.

ANSWER: Fully Compliant BelAir has included additional Rx filtering to ensure that the cellular and Wi-Fi radios can co-exist without degradation. BelAir has significant experience in this area and has designed the front end of our radio with an appropriate P1dB and IP3 to allow for cellular co-location and has additional front end filtering to ensure minimal degradation in performance when a +10dBm blocking signal is applied.


4.3.2 Outband blocking for 5 GHz radio (Section 4.3.2) The receiver blocking calculation is based on assumptions listed in Table 14.


Receiver blocking requirement in addition to regulatory requirements stated in Chapter 1 is shown in Table 15, Figure 5 and Figure 6. Requirements for coexistence with Wi-Fi @5GHz is not included and must be added by vendor.

ANSWER: Fully Compliant BelAir has included additional Rx filtering to ensure that the cellular and 5GHz Wi-Fi radios can co-exist without degradation.



5 Transmission requirements (Section 5.0)

5.1 Authentication (5.1) The Wi-Fi module must support authentication using IEEE 802.1x-2004. State supported methods:

Certificate

Pre‐shared key

Any other method

ANSWER: Fully Compliant The Wi-Fi Module will support the following encryption and authentication protocols, on a “per SSID” basis.

• WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐TLS • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐TLS • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐TLS • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐TLS • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐TTLS MSCHAPv2 • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐TTLS MSCHAPv2 • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐TTLS MSCHAPv2 • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐TTLS MSCHAPv2 • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐PEAPv0 EAP‐MSCHAPv2 • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐PEAPv0 EAP‐MSCHAPv2 • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐PEAPv0 EAP‐MSCHAPv2 • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐PEAPv0 EAP‐MSCHAPv2 • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐PEAPv1 EAP‐GTC • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐PEAPv1 EAP‐GTC • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐PEAPv1 EAP‐GTC • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐PEAPv1 EAP‐GTC • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐FAST • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐FAST • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐FAST • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐FAST • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐SIM • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐SIM • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐SIM • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐SIM • WPA Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐AKA • WPA Enterprise ‐ AES ‐ 802.1x ‐ EAP‐AKA • WPA2 Enterprise ‐ TKIP ‐ 802.1x ‐ EAP‐AKA • WPA2 Enterprise ‐ AES ‐ 802.1x ‐ EAP‐AKA • WEP • WPA‐Personal PSK • WPA2‐Personal PSK


In addition, all BelAir APs self-authenticate to the BelAir8000 and BelAir4000 Controllers using an X.509 certificate; this is part of the BelAirOS operating system firmware which is common to all BelAir products. The Wi-Fi Module will contain the advanced BelAirOS operating system and hence will support this functionality. If certificate is supported, state also if it is possible to revoke and install new or additional certificates after the module has done the initial authentication. ANSWER: Fully Compliant The current release supports pre-shared certificates. The following release (Q1 2012) will allow for certificates to be managed by a trusted CA and will enable time based and revoking of the default certificated.

5.2 Topology and link discovery (Section 5.2) To make it possible to discover the device, the integrated Wi-Fi module must support the Link Layer Discovery Protocol (LLDP) 802.1AB-2009. ANSWER: Fully Compliant BelAir already supports full auto discovery of our APs using a combination of DHCP and DNS methods. If it is determined that LLDP provides additional capability for the combined product, BelAir will add LLDP as an alternate method. The Wi-Fi module must also support Ericsson proprietary extensions of LLDP using Ericsson LLDP TLVs, and discovery methods. ANSWER: Fully Compliant BelAir will work with Ericsson to define and implement the proprietary extensions to LLDP.

5.3 Tunnels, Security and Encryption (Section 5.3) It should be possible to encrypt all traffic directly from the integrated Wi-Fi module. State support for following protocols, supported encryption algorithms and performance:

IPSec including IKEv2 key management.

CAPWAP including key management.

MACSec IEEE 802.1AE with 802.1x‐2010 key management.

GRE and others

State also support for any additional protocol. ANSWER: Fully Compliant The BelAirOS supports wide scale mobility with layer2 over layer 3 pseudowire protocols (L2TP, L2TPv2, L2VPN, L2GRE) or layer 3 protocols (Mobile IP, L3 GRE). BelAir has a fully functional PMIP solution to provide L3 mobility solution where mobility is provided by a PMIP enabled


Home Agent (HA), such as in 4G. The primary and back up MIP HAs are connected in the core network via conditional access gateway(s) to the internet. BelAir APs provide MIP Foreign Agent (FA) functionality together with a PMIP agent to enable standard IP clients to connect to the network. Thus yielding mobility between disparate systems such as Wi-Fi to 4G (LTE/WiMax) or to 3G (HSPA/HSPA+). IPSec and L2TPv3 are part of BelAir’s roadmap and will be available in BelAirOS release 13 in Q2 2012. In summary, the BelAirOS is a flexible tunneling and encapsulation engine that can be provisioned on a per Virtual AP basis. Regarding MACSec IEEE 802.1AE, BelAir recommends holding a technical interchange session with Ericsson to understand the use cases in which this type of protocol is required. Given the Wi-Fi Module will be internally co-located with Ericsson equipment within the Small-RBS, and communicating via a SGMII interface, BelAir believes “man-in-the-middle” attacks would be highly unlikely. BelAirOS supports encrypted tunnels to the Wi-Fi controller so all user and management traffic is already protected. However, should the need for 802.1AE over SGMII be required, BelAir will work with Ericsson and provide the most optimized implementation of the protocol.

5.4 QoS (Section 5.4) The Wi-Fi module must support at least 4 QoS classes and Diffserv marking of up-stream traffic. ANSWER: Fully Compliant BelAir APs include Quality of Service (QoS) settings that provide operators the ability to prioritize traffic. The BelAir APs work in conjunction with one another to optimize traffic flow based on the QoS settings. BelAirOS provides several prioritization options, including four QoS classes:

Background traffic

Best effort traffic

Video traffic, TI circuit emulation

Voice over IP (VoIP traffic)

BelAir will work with Ericsson to define the details of the most appropriate end-to-end QoS scheme to meet the overall system requirements. BelAirOS has an integral per user/interface/VLAN rate limiter that can be used to implement several of the functions outlined below. BelAirOS supports inside to outside marking of packets. BelAir shaping operates in-line When payload encryption is used the original Diffserv marking must be copied to the outer IP header. The QoS scheduler must support Modified Deficit Round Robin (MDRR) or similar with one low-latency queue.


The total available bandwidth for a logical or physical interface must be possible to configure to a lower value than the actual interface speed, using interface rate limit, and the scheduler must be able shape the traffic to this rate. It must be possible to change the rate of the shapers without interrupting traffic. Optionally the meters and shapers may be configured with a committed information rate CIR and excess information rate (EIR) and do Diffserv coloring based on a Two-Rate Three-Color Marker according to RFC 4115. It should be possible to dynamically change the QoS parameters using Ericsson proprietary extensions of LLDP.

5.5 Transport Configuration (Section 5.5) The module will be configured over the network. It must be possible to support configuration of a limited set of transport functionalities at initial start up as well as dynamic changes directly from the Small-RBS node connecting the Wi-Fi module. Initial start-up configuration possibilities will include configuration file download during BOOTP/DHCP. The Wi-Fi module should not become operational until it has received the initial configuration using BOOTP/DHCP. The LLDP protocol should still be running. Configuration of selected parameters should be possible using Ericsson proprietary extensions of LLDP with Ericsson TLVs. State other possible ways to do in-band configuration outside the flow from the Wi-Fi access controller. Example of protocols:

SNMP, SNMP over Ethernet

XML

CLI via Telnet/SSH

ANSWER: Fully Compliant Upon initial start-up, through the use of BOOTP/DHCP protocol, the Wi-Fi Module will retrieve a configuration file. Since all AP parameters are configurable and provisionable through the configuration file, the operator can select any parameter required to support the enablement of the required set of transport functionalities for the initial start-up. BelAir also supports DNS based auto-discovery and tunnel phone home capability offering full auto-discovery over L2 and L3 networks. All AP parameters can be configured through the configuration file, allowing for customizable boot-up sequences. In addition, the Wi-Fi Module will be designed to include the Dual Flash Memory Bank architecture that is currently in all BelAir Wi-Fi products. With the Dual Flash Memory Bank capability, the module can readily be loaded with two types of firmware to support a dual initialization procedure, if required. Only one bank is active, with the other used as a repository for a second load. The choice of firmware loaded is operator selectable and loads and


configurations can be reverted. Software download is in-service. Upon agreement with the customer, BelAir can preload a basic test version of the firmware in the active bank to allow for customer specific production type testing, with the other bank loaded with the full BelAirOS. Once initialization testing is complete, the operator can retrieve the BelAirOS firmware from the second bank and re-initialize the module with the OS uploaded. BelAir will work with Ericsson to define the correct LLDP commands that will allow the configurations of all required parameters via that protocol. BelAir Wi-Fi modules can also be accessed and configured locally or remotely using the following configuration interfaces:

CLI (via Telnet/SSH)

SNMP interface (SNMP v2c and v3)

Web interface (using HTTP or HTTPS)

BelAir devices also have TR‐069 support.

5.6 Access Gateway Address from Small-RBS (Section 5.6) The operator will provide the Wi-Fi modules gateway address through the Small-RBS. ANSWER: Fully Compliant The Wi-Fi Module can automatically retrieve the gateway address information and make it available to OA&M interfaces, such as BelView NMS, etc., or the information can be provisioned from the Small-RBS.

5.7 GPS positioning (Section 5.7) The Small-RBS contains a GPS-module that can provide the Wi-Fi-module with location coordinates and date/time. This data is sent from the Small-RBS using Ericsson LLDP extensions. ANSWER: Fully Compliant BelAirOS will forward the GPS information to the BelView NMS, which will utilize it to accurately auto-locate the device onto a pre-configured map of the region. The BelView Network Management System (BelView NMS) is a software package that allows network operators to configure, monitor and manage BelAir wireless mesh nodes, including Wi-Fi, WiMAX, 4.9 GHz public safety band, and cellular networks. Management features include fault, configuration, performance, inventory and security management to ease the installation, capacity planning, and proactive planning for network operations. BelAir products typically include a GPS for auto-location today. BelView is available for windows and Linux platforms and can be run in a virtual environment. Some BelView screen shots are captured below showing the live mapping and GIS features.


Figure 13: NMS map screenshot

Figure 14: Detailed NMS screenshots

Through these interfaces, the network operator can:

Configure, commission and manage nodes Track full statistics on each node Monitor node status and alarms Perform remote debugging when problems arise

Access Points can be fully auto discovered and will automatically connect to the core network without pre-provisioning. During system installation and commissioning a field technician may also connect locally to a wireless node for management purposes via the line interface or the access radio module. Once the network is up and running, the network operations center (NOC)


can manage the node remotely via the DOCSIS modem, Ethernet line interface or the wireless backhaul radio network. BelAir wireless node management functions are fully interoperable with many third-party standards-based solutions and allow direct connection to the APs, including:

Network management platforms such as CA Spectrum, Openview, Solarwinds Open-source tools Network monitoring, discovery, and subscriber management tools for cable operators

BelView NMS is built on a scalable data collector/server and client/server design that supports as many as 50,000 access points; each server supports up to ten java clients and hundreds of web clients for multi-user, multi-site management, and uses a database to store and export network management information. For each 5,000 APs under management a data collector machine is added. Users can be assigned different access privileges according to their network operations role. BelView NMS runs on Microsoft Windows XP, Linux and SUN Solaris; clients and servers can run on different operating systems. It offers a broad range of local and remote node management features via SNMP, including:

• Auto-discovery and topology update • Maps (both live street maps and site plan drawings) • Network configuration and provisioning • Performance management • Analysis, filtering and aggregation of network data • Real time graphical displays • Statistics collection • Full remote management capability over Ethernet, DOCSIS, fiber, backhaul radio, and

access radio • Command Line Interface -- Telnet and SSH • Web GUI -- http & https • SNMP -- v1, v2c & v3 • Automatic software upgrades • Remote software download

• Dual bank flash • In-service software download • Commit/save new load when happy with new load

• Automatic configuration transfer when upgrading • Centrally save and restore configurations

BelView supports advanced provisioning of access points with templates and service profiles enabling easy provisioning of SSIDs for different service and for wholesale partners. The latest BelView business intelligence module supports an easy to use web dashboard that gives the network operator detailed and summary views of the activity and usage on their network by SSID. BelView also supports synthetic clients that enable detailed monitoring of actual end user experience.


Figure 15: BelView Business Intelligence Module

Figure 16: BelView Synthetic Client

Figure 17: BelView Heat Maps


5.8 Status messages (Section 5.8) The Wi-Fi module shall be able to provide operational status to the Small-RBS. Examples of states to report may be “boot”, “normal operation”, “dormant”, “error”, and should be possible to forward to the Small-RBS O&M system. The status messages should be forwarded to the Small-RBS using LLDP. ANSWER: Fully Compliant BelAirOS provides a significant number of operational and performance statistics in the form of alarms or events (over 100 state conditions are reported on). These are available in SNMP format, and for the case of the Wi-Fi Module, they could be converted into LLDP and forwarded to the Small-RBS O&M system. BelAir recommends the use of GPIO and I2C interfaces for low level communications of HW status.

5.9 Wi-Fi as backhaul (Section 5.9) Is it possible to use the Wi-Fi module as a wireless backhaul? If so, would it be possible to configure it using LLDP? ANSWER: Fully Compliant The BelAir Wi-Fi module is a Dual Radio Unit (DRU) that provides a 2.4 GHz Wi-Fi radio and a 5 GHz Wi-Fi radio using enhanced performance links. Each radio can act as an Access Point (AP) and provide backhaul links. Backhaul links connect to other BelAir radios to create a radio mesh. BelAir was a pioneer of mesh networking and multiple mesh modes are supported and include:

Fully Shared

Point to Multipoint

Star

Point to Point.

BelAir invented the high performance switched mesh technology. Provisioning and configuration of the Wi-Fi Module will be done using software, and can be implemented either remotely or locally. BelAir will work with Ericsson to define the appropriate LLDP commands that will allow the Backhaul functionality to be configured via that protocol.


6 MMI requirements (Section 6.0)

6.1 Button and LED-indicators (Section 6.1) The Wi-Fi-module doesn’t need any buttons or LED indicators in the final product. It might however be good to have some LED indicators during the integration and verification phase of the project. Examples of useful LED indicators are:

Indicate that power is applied (Green)

Indicate when 2.4 GHz radio is enabled (Yellow)

Indicate when 5 GHz radio is enabled (Yellow)

Indicate when traffic is sent/received (Blue)

Indicate when a fatal error occurred 1) (Red)

1) A fatal error means that if the Wi‐Fi‐module detected a problem with high severity, the LED is lit.

Typical high severity cases include no transmission, can’t load software etc.

ANSWER: Fully Compliant Current BelAir products support LED functionality. BelAir does not foresee any difficulties in incorporating customized LED functionality to support the integration and verification phase of the product introduction. BelAir can also make available the LED state to the Small-RBS through GPIO and recommends the use of I2C for low level communications.

6.2 Messages to cellular (Section 6.2) The Wi-Fi-module is connected to the Wi-Fi AC. This means that error messages are sent to the Wi-Fi OEM from the Wi-Fi-module. If a general failure occurs that prevents the module to talk to the Wi-Fi AC, an error message is sent to the cellular part of the Small RBS. Used method for the transfer is LLDP, see Chapter 5.8. ANSWER: Fully Compliant Messages such as “Loss of communications to the AC” can be made available to the Small-RBS, as required. BelAir will work with Ericsson to generate a mutually agreed upon list of required messages. BelAir APs automatically connect to the Wi-Fi controller.


7 Security (Section 7.0) Chapter 5 discussed security on the transmission. What type of security does the module have? Example of security features are:

Encrypted software

Signed software

Secure storage of certificates and encryption keys

Describe supported security features (if any). ANSWER: Fully Compliant As described in previous sections, the Wi-Fi Module will operate under the BelAirOS operating system, and as a result, will take full advantage of the numerous networking and security features available. Supported security features include:

1. Software Security features.

All BelAir Access Points, including the Wi‐Fi‐module, fully authenticate to the BelAir

Controller using an X.509 certificate.

The AP database is kept in volatile memory when used with the controller, ensuring data

wipeout upon input power disconnection.

The AP software image is compressed and is md5sum protected.

OA&M. RADIUS authenticated admin login. This feature also allows the role definition of

the admin user (superuser/normal/observer).

BelAir is continuously improving the security of its APs by delivering security enhanced

features through its software upgrade process. This occurs several times a year. The

following security enhancements are planned for 2Q2012:

a. Encryption of AP internal database;

b. Signed and encrypted software image

2. BelAir Networks is fully compliant with the Wi‐Fi Alliance security requirements. All APs are

tested and certified. Over and above the standards, BelAir provides the industry’s most secure

solution with the following features:

AP to AP unauthorized/malicious traffic prevention.

Policy engine on AP. Prevents non‐authorized traffic from going beyond AP (into core

network).

Wireless bridge control/blocking. Prevents client to client communication on the same AP.

MAC black/white list.

Duplicate MAC detection on same AP. Block 2nd MAC.

Broadcast rate limiting. Limit the number of broadcast messages / second. Prevents

broadcast attack.

Wi‐Fi de‐authentication protection. Prevents malicious user from sending invalid Wi‐Fi de‐

auth message to AP.


DHCP exhaustion detection. Count # of DHCP requests / second; if above set threshold then

alarm. This warns of DHCP attacks.

NAV attack protection. NAV = network access vector (it is the length of airtime requested in

the packet. Some malicious clients request excessive airtime which blocks other users.

MIC key attack counter measures. MIC is a part of key encryption equation for TKIP. The

user sends many sequence of MIC and the peer responds with err codes. This allows a

malicious user to determine the pre‐shared key.

Secure GW. Only accept frames from default GW (source MAC must be def. GW MAC).

Auto‐secure GW. Compare binding of GW IP with GW MAC. Must match, else reject packet.

OA&M. Management interface blocking from air interface.


8 Test and verification (Section 8.0) Following describes test and verification of the module and when mounted inside the Small-RBS. Other ideas and suggestions are welcome.

8.1 Wi-Fi-module production test (Section 8.1) The Wi-Fi-module shall be delivered from vendor production with following characteristics:

Full tested to guarantee performance and compliant to specifications

Calibrated for full radio performance

Certificate

At least boot software stored in flash so it can start and connect to the Access Controller (and

download latest software).

ANSWER: Fully Compliant The BelAir Wi-Fi Module will undergo production testing prior to shipping. Production testing will be based on BelAir production testing procedures currently done on existing product line, which normally include:

- Calibration of transmitter - Verification of the EVM and transmit power level - Verification of receive functionality

Figure 18 shows a proposed test setup that is very similar to what is currently in our production environment.

Figure 18: Wi-Fi-Module Production Test Setup

This throughput type test, which consists of “pushing” as much traffic as possible within a specific timeframe (normally 10 seconds), validates successful AP client association and that radio performance is operating nominally and within specifications. A quality certificate is assigned to each unit that successfully passes the production tests. The Wi-Fi Module will be designed to include the Dual Flash Memory Bank architecture that is currently baselined in all BelAir Wi-Fi products. This architecture allow for two firmware loads to be included in the unit. Only one bank is active, with the other used as a repository for a second load. The choice of firmware loaded is operator selectable. Upon agreement with the customer, BelAir can preload a basic test version of the firmware in the active bank to allow for customer specific production type testing, with the other bank loaded with the BelAirOS.


Once the production test has been completed, the BelAirOS firmware can then be loaded into the active bank for normal operation. This can be done remotely of locally.

8.2 Wi-Fi-module type approval (Section 8.2) The module shall be type approved on a module level. ANSWER: Fully Compliant Please refer to responses in Section 1.1 of this document. Modular approval will be obtained. Valid markets are described in chapter 1. ANSWER: Fully Compliant Please refer to responses in Section 1.1 of this document. All documentation from type approval shall be handed over to Ericsson. It will be used to limit the type approval scope when the Small-RBS product is type approved. ANSWER: Fully Compliant BelAir will provide all required documentation from the Wi-Fi Module type approval testing to Ericsson.

8.3 Small-RBS verification (Section 8.3) The Wi-Fi-module needs to be verified in the correct environment in the Small-RBS product. Following needs to be verified:

Isolation between cellular and Wi‐Fi

ANSWER: Fully Compliant and Agreed

Wi‐Fi performance when cellular radio is used

ANSWER: Fully Compliant and Agreed

Cellular radio performance when Wi‐Fi is used

ANSWER: Fully Compliant and Agreed In order to do above tasks, following functionality must be available in the Wi-Fi-module:

Turn transmitter on and off using different power levels, channel types (different bandwidth) and

modulation types

Measure sensitivity of Wi‐Fi receiver

Wi‐Fi throughput measurements



The Wi-Fi Module will have undergone a series of BelAir Product Verification (PV) testing, which will include interfaces (communications, data, mechanical, power, etc…) testing, either through emulation or via a Small-RBS-prototype (TBD). To support the Small-RBS verification activities, BelAir will make available a low level test software load that will enable non-standard functionality, including the continuous transmission of the radios, either individually or simultaneously. This will facilitate the cellular radio and Wi-Fi radio performance testing To measure receive sensitivity, BelAir proposes a test set as per Figure 19.

Figure 19: Receive Sensitivity Test Setup

Sensitivity measurement procedure: - UDP traffic is sent through the test setup. - Initial Rx power level is set to ensure good connectivity - Rx power level is lowered in stepped increments. - At every increment, the sensitivity is measured and compared to a specification. - Once the specification threshold is breached, the sensitivity is recorded.

Throughput testing can be conducted using the test setup diagram depicted in Figure 20

Figure 20: Small-RBS Wi-Fi Throughput Test Setup

This throughput type test would consist of “pushing” as much traffic as possible while verifying the performance of the cellular radios.


8.4 Small-RBS type approval (Section 8.4) The Small-RBS product needs type approval. In order to limit the scope of this task, all documentation from the Wi-Fi-module type approval should be handed over to Ericsson. During the type approval same Wi-Fi-module functionality as stated in Chapter 8.3 is needed. ANSWER: Fully Compliant All Wi-Fi Module type approval documentation will be forwarded to Ericsson to support the Small-RBS type approval testing. Test setup as defined in section 8.3 of this document will also be provided to Ericsson, along with BelAir technical support required to facilitate the type approval activities.

8.5 Small-RBS production test (Section 8.5) The Wi-Fi-module will be assembled in the Small-RBS at a late stage together with other optional modules. A simple production tester will be used to check that the total product work as expected and fulfill our quality requirements. What functionality do we need in the Wi-Fi-module to fulfill the requirement? The full Wi-Fi-test should not be needed because it has already been tested in the module tester and it takes too much time. The focus should be on a very high level test that guarantees the quality of the product. ANSWER: Fully Compliant Systems level production testing should be similar to Wi-Fi Module level testing, with the one exception; it will need to be completed without cabling, since access to the antenna ports will be impossible. Figure 21 shows a proposed production type test setup. A simple throughput test will confirm that the Wi-Fi Module is powered on and has booted correctly, that it can associate with a client and create a session, and can receive data thereby confirming the antenna/radio chain is functioning nominally. This test should take place in a RF clean environment to ensure the validity of the test results.

Figure 21: Proposed Test Setup for Production Testing of Integrated Wi-Fi Module

RF Clean Test Cell


9 Summary BelAir Networks has delivered a comprehensive and technically accurate proposal that complies to all of Ericsson’s Wi-Fi Module requirements. BelAir’s proposal for a Wi-Fi card delivers industry leading radio performance: standards based 3*3 MIMO with beamforming and full ability to be co-located with a cellular radio. BelAir’s proposal is fully compliant with Ericsson’s specifications BelAir also delivers a full suite of advanced carrier grade software used by Tier 1 service providers worldwide to deliver 3G/4G offload and carrier Wi-Fi. Our extensive experience in delivering radios that meet the relevant regulatory emissions specifications at full power (4W EIRP) as well as our experience of delivering Wi-Fi while co-located with cellsites has been used to ensure that these cards will exceed the needs of Ericsson. BelAir has a suite of advanced network management and Wi-Fi controller products that would be part of the overall solution offer. BelAir also delivers a wide range of carrier Wi-Fi products for indoor and outdoor use that are widely deployed and field proven by Tier 1 carriers and that would enable Ericsson to deliver their customers a comprehensive solution. Should we be selected, we look forward to being Ericsson’s long term partner on this project.


www.belairnetworks.com

End of Document

Documents

BelAir Ericsson Wi-Fi RFQ Technical Responses Final