BuNGee Deliverable: D4.3 BuNGee System Integration Report · Project Number: 248267 Project acronym: BuNGee Project title: Beyond Next Generation Mobile Networks BuNGee Deliverable:

Project Number: 248267

Project acronym: BuNGee

Project title: Beyond Next Generation Mobile Networks

BuNGee Deliverable: D4.3

BuNGee System Integration Report

Due date of deliverable: 31.12.2011

Actual submission date: 19.01.2012

Start date of project: January 1, 2010 Duration: 30 months

Lead Participant: ALV

Contributors: See page 3

Release number: 1.0

Keywords: 2-tier deployment, joint access and backhaul design, multi-beam antenna, MIMO, multi-beam assisted MIMO, RRM, FFR, mmWave, WiMAX, In-band backhauling, self-deafening

Project co-funded by the European Commission within the Seventh Framework Programme (2007-2013)

Dissemination Level: Public

The research leading to these results has received funding from the European Community’s Seventh Framework Programme (FP7/2007-2013) under grant agreement n 248267

D4.3- BUNGEE SYSTEM INTEGRATION REPORT BUNGEE 248267 19 JANUARY 2012

Confidential Page 2 of 96 BuNGee Consortium

Executive Summary

Beyond Next Generation networks project (BuNGee) has been established with objectives to dramatically improve the overall infrastructure capacity density of the mobile network by an order of magnitude (10x) to an ambitious goal of 1 Gbps/Km

2 in the cell at a commercially viable cost.

To achieve such throughput density, BuNGee aims several fundamental paradigm shifts in ultra-high capacity designs which pertain to:

joint design of access and backhaul networks using heterogeneous radio elements and licensed and license-exempt spectrum;

below-rooftop access radio network deployment, exploiting natural radio isolation between neighbour cells;

innovative antenna technologies tailored to urban ultra-high capacity needs;

MIMO & interference elimination techniques;

autonomous architectures capitalising on very aggressive spatial and spectral reuse combined with high spectrum efficiency, by using novel antenna, RF, base-band and network techniques.

BuNGee Live Demo is planned to measure the effectiveness of the BuNGee developed concepts. For this purpose we build a high capacity radio cell prototype targeting 1 Gbps/Km

2 throughput density demonstration

in real urban cellular deployment scenarios.

Serving as the project proof-of-concept, the Live Demo incorporates the components, prototyped by the BuNGee partners:

Hub & Access BS prototypes based on Alvarion commercial 4Motion platforms implementing 4G mobile broadband wireless access and broadband wireless backhauling networks with WiMAX/ IEEE 802.16 suite;

BuNGee Multi-beam antenna for Hub Base Station and directional antennas for Backhauling Subscriber Station (BHSS) and Access BS, designed by CASMA as a part of BuNGee research;

Ultra high capacity mmWave 60 GHz point-to-point link, designed by SIKLU.

As a part of preparations to the Live Demo, system planning, engineering and integration testing was executed in Lab conditions. The purpose of the Integration activities is to verify cross-product and cross-feature functionalities and proper operation. Some tests shall provide baseline reference measures for KPIs. As a part of System Integration, all the BuNGee components are integrated and tested.

Main objective of this document is to present the BuNGee System Integration activities and the testing results. Additionally, in this document, we present preliminary planning of the Live Demo, including project planning, site and end-to-end setup configuration, system engineering and finally the demonstration scenarios preparation.



Contributors

Participant #

Participant short name

Name of the Contributor E-mail

1 ALV Evgeny Voytko [email protected]

1 ALV Noy Blum [email protected]

1 ALV Miki Harshish [email protected]

1 ALV Oleg Marinchenco [email protected]

1 ALV Alex Tipograff [email protected]

1 ALV Rotem Barda [email protected]

1 ALV Rafi Iluz [email protected]

1 ALV Oscar Sporn [email protected]

mailto:[email protected]



Table of Contents

Executive Summary ......................................................................................................................................... 2

Contributors ..................................................................................................................................................... 3

Table of Contents ............................................................................................................................................ 4

List of Tables .................................................................................................................................................... 6

List of Figures .................................................................................................................................................. 6

Definitions ........................................................................................................................................................ 8

List of Acronyms ............................................................................................................................................. 9

1. Introduction ............................................................................................................................................ 10

2. The Project Planning ............................................................................................................................. 10

3. Lab setup description ............................................................................................................................ 12

4. Equipment List ....................................................................................................................................... 14

5. Lab Cross-product and cross-feature Integration tests and results ................................................ 16

5.1 BuNGee Multi-Beam Antenna Integration with a Hub BS ........................................................... 16 5.1.1 Test Procedures ......................................................................................................................... 18

5.2 BuNGee Antennas in Relay Station (BHSS and ABS) ................................................................ 21 5.2.1 BHSS Antennas Test Procedures ............................................................................................. 23 5.2.2 ABS Antennas Test Procedures ................................................................................................ 26

5.3 MIMO B Integration ...................................................................................................................... 29 5.3.1 Test Procedures ......................................................................................................................... 31

5.4 Multi-beam Assisted MIMO .......................................................................................................... 33 5.4.1 Test Procedures ......................................................................................................................... 34

5.5 In-band Backhauling Network Architecture Based on L3 Tunnelling .......................................... 35 5.5.1 Backhauling Tier ........................................................................................................................ 40 5.5.2 Access Tier ................................................................................................................................ 43

5.6 Multi-Carrier Support ................................................................................................................... 46 Test Procedures .................................................................................................................................. 49

5.7 Multi-Carrier Link Aggregation ..................................................................................................... 52 5.7.1 Test Procedures ......................................................................................................................... 53

5.8 Inter-Carrier Load Balancing ........................................................................................................ 56 5.8.1 Test Procedures ......................................................................................................................... 57

5.9 Backhauling Multi-Link Aggregation ............................................................................................ 61 5.9.1 Test procedures ......................................................................................................................... 63

5.10 Reuse 1 Fractional Frequency Reuse ......................................................................................... 66 5.10.1 Test Procedures................................................................................................................... 68

5.11 Neighbour Data Distribution ......................................................................................................... 70 5.11.1 Test Procedures................................................................................................................... 71

5.12 Cross-Product/ Cross-Feature Integration Status Report ........................................................... 75

6. Live Demo preparation .......................................................................................................................... 76

6.1 Live Demo setup .......................................................................................................................... 76 6.1.1 Central Site and Access Sites locations .................................................................................... 78 6.1.2 Network IP and VLAN Engineering ............................................................................................ 79 6.1.3 Live Demo Setup Acceptance Test Plan (ATP) ......................................................................... 83

6.2 Demonstration Scenarios ............................................................................................................ 86 6.2.1 Total System Throughput ........................................................................................................... 86 6.2.2 Performance of Multi-Beam Assisted MIMO .............................................................................. 88 6.2.3 Backhauling Tier Broadband Coverage ..................................................................................... 88 6.2.4 Access Tier Mobile Coverage .................................................................................................... 89 6.2.5 In-band Backhauling Network Functionality ............................................................................... 90 6.2.6 Backhauling Multi-Link Aggregation .......................................................................................... 90 6.2.7 Lab-based In-band backhauling treatment of self-deafening issue ........................................... 91

7. Conclusions ............................................................................................................................................ 94



8. Bibliography ........................................................................................................................................... 95

9. Release History ...................................................................................................................................... 96



List of Tables

TABLE ‎4-1: LAB SETUP BTS EQUIPMENT LIST ................................................................................................................ 14 TABLE ‎4-2: LAB SETUP CPE EQUIPMENT LIST................................................................................................................ 15 TABLE ‎4-3: LABORATORY EQUIPMENT LIST ..................................................................................................................... 15 TABLE ‎5-1: HBS MULTI-BEAM ANTENNA TEST PROCEDURES ....................................................................................... 18 TABLE ‎5-2: RELAY STATION BHSS ANTENNA TEST PROCEDURES ............................................................................... 23 TABLE ‎5-3: RELAY STATION ABS ANTENNA TEST PROCEDURES .................................................................................. 26 TABLE ‎5-4: MIMO B TEST PROCEDURES ....................................................................................................................... 31 TABLE ‎5-5: MULTI-BEAM ASSISTED MIMO TEST PROCEDURES .................................................................................... 34 TABLE ‎5-6: SETUP IP NETWORK PLANNING .................................................................................................................... 37 TABLE ‎5-7: BACKHAULING VPWS TEST PROCEDURES .................................................................................................. 41 TABLE ‎5-8: ACCESS TIER TEST PROCEDURES ............................................................................................................... 43 TABLE ‎5-10: MULTI-CARRIER TEST PROCEDURES ......................................................................................................... 49 TABLE ‎5-11: MULTI-CARRIER LINK AGGREGATION TEST PROCEDURES ........................................................................ 54 TABLE ‎5-12: INTER CARRIER LOAD BALANCING TEST PROCEDURES ............................................................................ 57 TABLE ‎5-13: MULTI-LINK AGGREGATION TEST PROCEDURES ....................................................................................... 63 TABLE ‎5-14: FFR TEST PROCEDURES ............................................................................................................................ 68 TABLE ‎5-15: NDD TEST PROCEDURES ........................................................................................................................... 71 TABLE ‎5-16: INTEGRATION STATUS REPORT .................................................................................................................. 75 TABLE ‎6-1: THE LIVE DEMO NETWORKING CONFIGURATION ......................................................................................... 79 TABLE ‎6-2: THE LIVE DEMO ATP .................................................................................................................................... 83 TABLE ‎6-3: THE TOTAL SYSTEM THROUGHPUT DEMONSTRATION ................................................................................. 86 TABLE ‎6-4: MULTI-BEAM ASSISTED MIMO DEMONSTRATION ........................................................................................ 88 TABLE ‎6-5: BACKHAULING TIER BROADBAND COVERAGE DEMONSTRATION ................................................................. 88 TABLE ‎6-6: ACCESS TIER BROADBAND COVERAGE DEMONSTRATION .......................................................................... 89 TABLE ‎6-7: IN-BAND BACKHAULING APPROACH DEMONSTRATION ................................................................................ 90 TABLE ‎6-8: BACKHAULING MULTI-LINK AGGREGATION ................................................................................................... 90 TABLE ‎6-9: LAB BASED IN-BAND BACKHAULING SELF-DEAFENING ISSUE RESOLUTION .................................................. 91

List of Figures

FIGURE ‎2-1: THE BUNGEE INTEGRATION AND LIVE DEMO PROJECT TIME LINES .......................................................... 11 FIGURE ‎3-1: MICRO-BS (ABS) VIEW ............................................................................................................................... 12 FIGURE ‎3-2: LAB SETUP TOPOLOGY ............................................................................................................................... 13 FIGURE ‎5-1: BUNGEE MULTI-BEAM ANTENNA ................................................................................................................ 17 FIGURE ‎5-2: BUNGEE MULTI-BEAM ANTENNA PERFORMANCE ....................................................................................... 18 FIGURE ‎5-3: BUNGEE BHSS ANTENNA TYPICAL RADIATION PATTERN .......................................................................... 22 FIGURE ‎5-4: BUNGEE BHSS ANTENNA .......................................................................................................................... 22 FIGURE ‎5-5: BUNGEE ABS ANTENNA TYPICAL RADIATION PATTERN ............................................................................. 23 FIGURE ‎5-6: N X N MIMO ANTENNA SYSTEM .................................................................................................................. 29 FIGURE ‎5-7: MIMO MATRIX B ......................................................................................................................................... 30 FIGURE ‎5-8: IMPLEMENTING MIMO MATRIX B FOR DOWNLINK ...................................................................................... 30 FIGURE ‎5-9: MULTI-BEAM ASSISTED MIMO ................................................................................................................... 33 FIGURE ‎5-10: NETWORK ARCHITECTURE FOR RELAY/ IN-BAND BACKHAULING .............................................................. 36 FIGURE ‎5-11: PHYSICAL SCHEME OF END–TO-END LABORATORY TOPOLOGY ............................................................. 36 FIGURE ‎5-12: VPWS SERVICE ........................................................................................................................................ 40 FIGURE ‎5-13: 20 MHZ BEAM ........................................................................................................................................... 47 FIGURE ‎5-14: IF-MUX INSTALLATION ............................................................................................................................. 48 FIGURE ‎5-15: IF-MUX ..................................................................................................................................................... 48 FIGURE ‎5-16: MULTI-CARRIER SETUP ............................................................................................................................ 49 FIGURE ‎5-17: EQUAL STATIC LINK AGGREGATION ......................................................................................................... 52 FIGURE ‎5-18: MULTI-CARRIER LINK AGGREGATION SETUP ........................................................................................... 53 FIGURE ‎5-19: INTER-CARRIER LOAD BALANCING SETUP ............................................................................................... 57 FIGURE ‎5-20: UNEQUAL STATIC DATA LOAD-SHARING .................................................................................................. 62 FIGURE ‎5-21: BACKHAULING MULTI LINK AGGREGATION SETUP ................................................................................... 63 FIGURE ‎5-22: FREQUENCY REUSE PATTERNS: (A) 3 FREQUENCIES; (C) 1 FREQUENCY (OFDMA) ............................. 67



FIGURE ‎5-23: NDD MESSAGES ....................................................................................................................................... 71 FIGURE ‎6-1: THE END–TO-END LIVE DEMO TOPOLOGY ................................................................................................ 77 FIGURE ‎6-2: THE SITE LOCATION .................................................................................................................................... 78 FIGURE ‎6-3: SSS ALLOCATION THROUGHOUT THE SECTORS ....................................................................................... 87 FIGURE ‎6-4: BACKHAULING MULTI LINK AGGREGATION DEMONSTRATION .................................................................... 91 FIGURE ‎6-5: IN-BAND BACKHAULING SELF-DEAFENING ISSUE DEMONSTRATION - SETUP .............................................. 93 FIGURE ‎6-6: IN-BAND BACKHAULING SELF-DEAFENING ISSUE DEMONSTRATION – AIR FRAME STRUCTURE .................. 93



Definitions

AAA – Authentication, Authorization and Accounting server. In the context of this document, represents WiMAX Forum NWG-defined Home AAA function that is located in the Core Service Network (CSN) and provides services for WiMAX ASN and WiMAX subscribers. Access BS – BuNGee-defined Base Station entity that maintains radio link communications with end-user equipment (typically PHY and MAC layers) and represents Access Tier. Access BS belongs to Access Site. ASN – Access Service Network, WiMAX Forum NWG-defined access network segment, incorporating one or more WiMAX BSs and one or more WiMAX ASN GWs. ASN GW – Access Service Network GateWay, WiMAX Forum NWG defined entity that provides certain networking functions in the WiMAX access network. BHSS – Backhauling Subscriber Station, radio access technology specific entity that maintains radio link level communications with HBS. BHSS belongs to Access Site and normally is used to feed the Access BS. BS – Base Station, represents the radio access technology specific entity that maintains radio link level communications with end-user equipment (typically PHY and MAC layers). The examples are WiMAX Base Station and 3GPP eNodeB. CN – Core Network is defined as a set of network functional entities responsible for user/ device authentication, authorization, accounting and required to provide connectivity services for end-user equipment. Hub BS – Hub Base Station, the radio access technology specific entity that maintains radio link communications with Backhauling Subscriber Station (BHSS) - typically PHY and MAC layers. The examples are WiMAX Base Station and 3GPP eNodeB. HBS may use overlay spectrum or so called “inband backhauling” (in-band, time division based resource allocation) to provide backhauling services for the Access Sites. MS/ SS – Mobile Station/ Subscriber Station equipment, radio access technology specific entity that maintains radio link level communications with RAN/ BS. It is a part of user equipment. RAN – Radio Access Network is normally defined as a set of network functions required to provide radio including BS and ASN GW, while in 3GPP architecture it may include E-UTRAN and some EPC functions (such as MME and S-GW).

UE – User Equipment is defined as a set of functions required to provide one or more radio access link(s), connectivity services and other user-specific functions. UE equipment may be Mobile or Stationary and may be “integrated” device or “compound” device (i.e. composed of multiple stand-alone devices, which is typically the case for stationary equipment). UE may also integrate multiple radio access technologies – such as WiMAX NIC (or CPE) and LTE NIC (or CPE).

SUT – System Under Test



List of Acronyms

Abbreviation / acronym Description

3GPP 3rd Generation Partnership Project

4G 4th Generation

AAA Authentication, Authorization, and Accounting server

ABS Access BS

Alvaristar Alvarion‟s EMS

ART Above Roof Top

ASN Access Service Network

BHSS BackHaul Subscriber Station

BRT Below Roof Top

BS Base Station

BTS Base transceiver station. Equivalent to BS.

BuNGee Beyond Next Generation Mobile Broadband

BW Bandwidth

CDD Cyclic delay diversity

CPE Customer Premises Equipment

CTC Convolutional Turbo Code

CQI Channel quality indicator

DL Downlink

EAP Extensible Authentication Protocol

FEC Forward error correction

FFR Fractional Frequency Reuse

FFT Fast Fourier Transfornation

HBS Hub Base Station

IDU In-Door Unit

LE License Exempt (frequency band)

LOS Line of sight

MBA Multi-beam antenna

MIMO Multiple Input Multiple Output

MRC Maximum ration combining

MS Mobile Station

ODU Out-Door Unit

PUSC Partial Usage of Sub Channels

QoS Quality Of Service

RAN Radio Access Network

RRH Remote Radio Head

RRM Radio Resource Management

RS Relay Station

SON Self Organizing Network

TDD Time Division Duplex

Tx Transmitter

UE User Equipment

UL Uplink

VPWS Virtual Private Wire Service

WiMAX Worldwide Interoperability for Microwave Access

SG Service Group

SI Service Interface

INE Initial Network Entry

VPWS Virtual Pseudo-Wire Service

AU Access Unit

NDD Neighbor Data Distribution

NBL Neighbor List

NBS Neighbor Base Station

SBS Serving Base Station

TBS Target Base Station



1. Introduction

The goal of this deliverable is to describe BuNGee System Integration activities performed during Bungee System integration phase by ALV and to prepare the ground for the Live Demo setup and demonstration scenarios.

BuNGee Live Demo represents the ultimate Proof of Concept for the deployment model and mechanisms developed as a part of BuNGee research project. To serve this demo, we build a high capacity radio cell prototype targeting 1 Gbps/Km

2 throughput density demonstration. This includes Hub and Access BS

prototypes integrated in a wider system and network solution, including prototypes of BuNGee-specific antennas (multi-beam antenna, BHSS and ABS directional antennas) and ultra-high capacity mmWave point-to-point links.

The Live Demo preparation activities include the following stages:

products and features testing at Phase 1,

cross-product and cross-feature integration and testing at Phase 2, and finally

Live Demo system integration, acceptance testing and performance testing at Phase 3.

Phase 3 presents the preliminary step for the Live Demo and will be performed when the final outdoor setup is established.

The document presents mainly Phase 2 integration activities and paves the way for the Phase 3 activities.

2. The Project Planning

The BuNGee Integration project is built up from the following activities:

Project Management.

The Project Management activities cover a common work plan preparation, resources estimation and Laboratory Integration/ Live Demo work groups organization. The Project Management task is carried out through the entire project.

Lab setup design and Engineering activities.

This step includes preparation of Engineering Guidelines for the Lab setup.

Generate equipment list and Bill Of Materials (BoM).

The purpose of this task is the BoM for Lab setup equipment and materials estimation and ordering.

Integration/Testing documentation design.

Under this task, the Lab setup integration Test Procedures are created and arranged, including the appropriate documents preparation, tests review and evaluation.

Lab setup Establishment.

The Lab setup should be installed, adjusted and evaluated.

Integration testing and fine tuning.

The Integration Test Procedures should be carried out with accordance to the pre-defined testing scenarios.

Integration testing Reporting.

The results of performed Integration Procedures should be evaluated and reported.

System Integration activities duration is 3Q’11-1Q’12.



The BuNGee Live Demo preparation phase consists of the following steps:

Live Demo System Engineering.

This step comprises the Live Demo‟s common Engineering Guidelines formation.

Live Demo BoM.

The Equipment and Materials List for the Live Demo will be estimated and ordered.

Radio Network Planning (RNP).

The Radio Network Planning should be performed with accordance to the Site‟s geographical conditions.

The Live demo site design.

This step consists of detailed Live Demo site designing, including preparation of ATP and Live demo testing procedures.

Live Demo Site Installation.

The Demo site should be installed and provisioned with accordance to the procedures described at the Live demo designing step.

Live demo ATP.

The Live Demo Acceptance Plan should be carried out.

Live Demo scenarios testing.

The Live Demo setup will be tested by means of conducting of real test scenarios.

Live Demo Performance evaluation.

This step implies a performance of all Live Demo test scenarios, collecting of results and measurement and reporting.

Live Demo Results Evaluation.

The results of Live Demo testing will be evaluated and compared to the simulation scenarios.

Live Demo activities duration – 1Q’12 - 2Q’12

The BuNGee Integration and Live Demo Project time lines are presented in the Figure below:

Figure ‎2-1: The BuNGee Integration and Live Demo project time lines



3. Lab setup description

The laboratory‟s setup is used for the BuNGee Live Demo functionality simulation and is planned to be as close as possible to the real Live Demo topology, excluding air interface and replacing it by RF cables with certain levels of attenuation. The Lab setup contains a subset of the full Live Demo configuration with components and devices similar to the real outdoor installation.

The setup emulates the real 2-tier deployment, including:

Backhaul tier RAN, and

Access tier RAN.

The backhaul tier contains 2 Macro Wireless Base Station sites (Hub Base Station sites), based on Alvarion 4Motion product family, providing backhauling connectivity for the Base Stations in the access tier. The access tier includes 8 micro outdoor 4Motion Base Stations located in 4 portable access sites (Access BS sites). These Access BSs will be used as the access points for the end-user mobile devices.

Hub BSs use indoor macro-BS equipment suitable for dense-urban and suburban deployments.

Every modular 4Motion unit can support:

Up to 3 sectors with two carriers, or

Up to 6 sectors with one carrier.

Micro and Macro BS solutions share similar functionality with the same ecosystem, offering a flexible mix-and-match approach to address the specific needs. Micro Outdoor base station complements Alvarion‟s Macro base station deployments to enable coverage extension in areas where multi-sector Macro base station is not required. The Micro base station has been chosen for the Access tier deployment since it provides the following advantages:

Simple architecture. The micro Base Station compact box comprises the following building blocks:

Modem: Access Unit (AU) card;

Radio module in a 2x2 configuration.

Installation convenience. The Micro Outdoor Base Station enables the one-man-mount of a lightweight single box product with various mounting options including rooftops, walls, poles, and towers for easy installation.

Figure ‎3-1: Micro-BS (ABS) view

The complete Lab setup topology is presented on the Figure below:



BTS1 (F1\F2) 3.5 GHz

1

2

3

4

2

3

4

IF-

MUX 1

IF-

MUX 2

AU1

AU2

ODU1 (2x2)

(F1\F2)1

2

1 1BHSS 1

(F1)

BHSS 3

(F1)

BHSS 5

(F1)

1BHSS 2

(F2)

BHSS 4

(F2)

BHSS 6

(F2)

1ABS 1

(f1)

ABS 3

(f1)

ABS 5

(f1)

1ABS 2

(f2)

ABS 4

(f2)

ABS 6

(f2)

1ODU 1

1x1

ODU 3

1x1

ODU 5

1x1

1ODU 2

1x1

ODU 4

1x1

ODU 6

1x1

Backhaul tier

Dual Carrier (20 MHz), 3.5 GHz

1SS 1

SS 3

SS 5

1SS 2

SS 4

SS 6

Access tier

Single Carrier (10 MHz), 2.5 GHz

Core

Network

Sector

1

Sector

2

Sector

3BTS2 (F1\F2) 3.5 GHz

1

2

1

2

1BHSS 7

(F1)1

ABS 7

(f1)1

ODU 7

1x11SS 7

Sector

4

ODU4 (2x2)

(F1\F2)Aggregation

Router 1

Aggregation

Router 2RG-45 link

Gi0/1

Gi0/2

Gi0/1

Gi0/2

1BHSS 8

(F2)1

ABS 8

(f2)1

ODU 8

1x11SS 8

1

Radio Cluster 1

Radio Cluster 2 1

2

1

ODU2 (2x2)

(F1\F2)

Radio Cluster 3

1

2

1

ODU3 (2x2)

(F1\F2)

1

2

3

4

2

3

4

IF-

MUX 1

IF-

MUX 2

AU21

Radio Cluster 1

2

2

2

AU1

AAA

ASNGW

Applic.

Server

1st

Link of Aggregation - Gigabit Ethernet

2nd

Link of Aggregation - Wimax Link

Aggregated from Wimax and Gigabit

Ethernet Link

Internet

Figure ‎3-2: Lab Setup Topology

Setup network is based on the L3 private packet segment, which has connectivity to Internet via separate service subnet terminated in ASN GW. Network Core equipment, such as WiMAX Home AAA, ASN GW, Application Server, etc. are connected to the private packet segment.

Additionally, Multiple Access Link aggregation functionality utilizes aggregation equipment (Cisco routers) connected to Point-to-Multipoint link based on WiMAX backhauling network and Point-to-Point 60 GHz mmWave link. In the Lab Setup, mmWave link of Siklu is emulated as 1 Gbps wired link, potentially with Network Emulator test equipment (emulating delay and packet loss distortions).

Hub Base Stations are connected to the private packet segment and communicate with WiMAX ASN GW. Hub BSs use IF cables for connectivity to the Outdoor radio units (ODUs), as presented by red and brown lines on the Figure ‎3-2. ODUs, in Lab Setup, are not connected to the real antennas, but instead use RF

cables to connect to the corresponding BHSSs.



4. Equipment List

The following table represents the equipment list used for the Lab Setup:

Table ‎4-1: Lab Setup BTS Equipment list

Product Qty Description

AAA 1 AAA Server

Router Cisco 1800 3 Cisco Routers

Shelf 2 BreezeMAX Base Station Shelf. Include air ventilation unit (AVU)

PSU 4 BreezeMAX Base Station Power Supply Unit

NPU 2 BreezeMAX 4Motion 2.x Network Processor Unit

PIU 2 BreezeMAX Base Station Power Interface Unit. Includes DC power cable. High Power

AU 8 BreezeMAX 4motion 2.X Base Station Access Unit interface module for (4 channels)

GPS 2 Outdoor GPS Receiver for BreezeMAX 4Motion Macro Base Station.

GPS cable 2

GPS cable connecting the GPS outdoor receiver to the NPU card in Macro Indoor BTS (no adaptor is required) and to the NAU (in Macro Outdoor BTS).

ODU 3.5 2*2 4

BreezeMAX Base Station High Power Outdoor Radio Unit - for 3,400 -3,600 MHz for 2Tx+2Rx config. Include RF connector for a separate external antenna (antenna not included).

BMAX ODU MICRO 2.5 8

Single sector 2x2 all-outdoor base station in 2.5Ghz (2485Mhz to 2690Mhz), which is comprised of modem and radio components. Mounting kit included

GPS for ODU MICRO 8

Standard GPS antenna Kit including antenna, 3m cable, pole mount bracket, mounting band and lightning protector (for BTS side) to be ordered ONLY with Micro OD BST

IF-MUX 4 IF-MUX splitter

TNC 8

Indoor unit to Outdoor unit Cable, for use with BreezeMAX models that include outdoor units; Terminating connectors:



Table ‎4-2: Lab Setup CPE Equipment list


4M-CPE-USB-2.5 16 USB Dongle for 802.16e Mobile WiMAX at 2.5Ghz frequency band

4M-CPE6000-Si-2D-2V-WiFi-2.5 4 “Premium” Indoor CPE based on BreezMAX4000 series 2Data/2Voice/Wi-Fi, 2.5G.

4M-CPE6000-Si-1D-1V-3.5 10 Indoor, 1Data/1Voice, 3.3-3.6G.

Table ‎4-3: Laboratory Equipment list


ZX10-2-42+ 8 RF splitter for MS

940-60-33-1 2 Variable attenuator

MDC9131B-20-SMA 15 High power attenuator (10W, 20db)

BW-S30W2+ 30 Fixed attenuator (2W,30db)

CBL-3FT-SMSM+ 11 RF cable (1m) Blue

CBL-6FT-SMSM+ 11 RF cable (2m) Blue

CN0458 15 N-type to SMA connector

3COM 4 3COM switch

CN1 20 Ethernet cable (1m)

EQ1182 1 R&D/Intg smartbit 200/2000

Compaq 2.4G PC 1G 2 SFF PC



5. Lab Cross-product and cross-feature Integration tests and results

In order to get prepared for the Live Demo complicate testing scenarios, it is essential to perform cross-product and cross-feature integration testing. Most of the tests will be conducted in the indoor Lab setup, described in the section [‎3], though some tests demanding the real air interface and outdoor field conditions will be carried out on the Live Demo setup.

The following cross-product integration is required:

Broadband Wireless Hub and Access Base Stations/ Radio Access Network;

BuNGee-specific antennas: Hub BS multi-beam antenna, BHSS antenna and ABS antenna;

Ultra-high capacity mmWave Point-to-Point link in 60 GHz band.

The following cross-feature integration is required:

BuNGee Multi-Beam Antenna Integration with Hub BS;

BuNGee Antennas integration in the Relay Station (BHSS and ABS);

MIMO B Integration;

Multi-Beam Assisted MIMO;

In-Band Backhauling Network Architecture Based on L3 Tunnelling including:

Backhauling Tier Integration;

Access Tier Integration;

Multi-Carrier Support Integration;

Multi-Carrier Link Aggregation;

Inter-Carrier Load Balancing;

Backhauling Multi-Link Aggregation;

Reuse 1 Fractional Frequency Reuse;

Neighbour Data Automatic Distribution.

5.1 BuNGee Multi-Beam Antenna Integration with a Hub BS

The dual-polar multi-beam antenna is suitable for installation on a Hub Base Station in order to communicate with Hub Subscriber Stations in the BuNGee platform. As a part of the project, a multiple beam forming network in the form of a Butler matrix has been specified and is integrated with the terminations of the antenna radiating element and feed network array. The dual-polarization multi-beam antenna developed for BuNGee includes a number of narrow beams intended to create spatial reuse for system capacity increase. This antenna is planned to be deployed with Hub BS in the Backhaul tier.



Figure ‎5-1: BuNGee Multi-beam antenna

BuNGee developed novel, extremely high capacity MIMO techniques, specifically adapted to the BuNGee architecture. This supposes to exploit the BuNGee multi-beam high gain antenna to introduce multi-beam assisted MIMO (MBA-MIMO), in which MIMO principles are applied in beam space following the antenna feed matrix. It should allow the gain and selectivity of the antenna to be exploited with relatively low cost of the radio equipment.

The specification of the Multi-Beam Antenna, confirmed by the BuNGee is as follows:

Frequency: 3.4 – 3.6 GHz

Gain of each beam of complete array: 19dBi

VSWR: approx 2:1

Polarisation: Dual-polar (+ and - 45˚ polarisations)

Cross Polar: approx 15dB

Sidelobes: 12dB maximum for each beam in elevation and azimuth

Front to Back: approx 30dB

Isolation between beams: approx 15dB

Power requirement of each beam: 15W

Beamwidth of each beam: 15˚ (azimuth) x 10˚ (elevation); 2˚ elevation downtilt

Number of Beams: 6 beams x 2 overlaid polarisations = 12

Azimuth beam angles: -37.5˚, -22.5˚, -7.5˚, 7.5˚, 22.5˚, 37.5˚, achieved using Butler matrix beamforming technology.

Total beam coverage: 90˚ per antenna; four antennas per HBS achieving 360˚ azimuth coverage

Phase deviation between beams: ± 10˚ max

Performance of the assembly for one polarisation without the attenuators is presented on the figure below:



Figure ‎5-2: BuNGee Multi-beam antenna performance

5.1.1 Test Procedures

Table ‎5-1: HBS Multi-Beam Antenna Test Procedures

Test N

Test Purpose

Test Description Expected Results Actual Results Pass\Fail

1. To perform successful Initial Network Entry in LOS

condition

Perform INE with the following combination:

LOS

0.5- 1KM from the ANT

Location – the CPE needs to be in the ANT aperture

ANT tilt = 2 deg

Num of Enable beam = 6 (all)

The INE should be successfully accomplished.

The INE is successful.

Pass

2. To perform successful Initial Network Entry in Near LOS

condition

Perform INE based on the following combination:

Near LOS


Location –


In progress1

1 Some Test Cases require real outdoor configuration. They will be performed as a part of Live Demo

preparation outdoor activities.



the CPE needs to be in the ANT aperture

ANT tilt = 2 deg

Num of Enable beam = 6(all)

3. To perform successful Initial Network Entry in Hidden

condition


Hidden



ANT tilt = 2 deg



In progress1

4. To perform successful Initial Network Entry in Side lob condition


Side lob



ANT tilt = 2 deg




Pass

5. To perform Unsuccessful Initial Network Entry in OUT of the ANT aperture

condition

Perform Unsuccessful INE with the following combination:

Location – the CPE need to be in the OUT of the ANT aperture

ANT tilt = 2

The INE should be Unsuccessful

The INE failed. Pass





deg



With tilt 4 deg


LOS


Location – the CPE need to be in the ANT aperture

ANT tilt = 4 deg



In progress1


with long range


LOS

Long distance (e.g. 2-5 km) from the ANT


ANT tilt = 2 deg



In progress1


Condition with part of the Beams


LOS



ANT tilt = 2 deg


In progress1





Num of Enable beam = 1,3,5




LOS



ANT tilt = 2 deg

Num of Enable beam = 2,4,6


In progress1




LOS



ANT tilt = 2 deg

Num of Enable beam = 1,2, 4,6


In progress1

5.2 BuNGee Antennas in Relay Station (BHSS and ABS)

The Backhauling Subscriber Station Antenna (BHSS) is required to operate at the 3.5 GHz Band with +45˚ azimuth and a peak gain of 13.2 dBi. By means of diamond formation elements the reduction of side lobe levels is achieved. The antenna‟s typical radiation pattern is represented at the figure below:





Figure ‎5-3: BuNGee BHSS antenna typical radiation pattern

The BuNGee BHSS antenna is presented at the figure below:

Figure ‎5-4: BuNGee BHSS antenna

The BuNGee Access Base Station (ABS) antenna is required to operate at 2.4 – 2.6 GHz as a dual polar, slant 45˚ 17 dBi unit. For the purposes of the BuNGee tests a stock CASMA V & H antenna was adapted to suit and is mounted in a diamond formation for radiation pattern tests. It consists of a 4 x 4 element and parasite design carried in a machined aluminium, iridescent coated housing and glass fibre radome.

Frequency: 2.4 – 2.6 GHz

Gain of each beam: 17dBi

VSWR: approx 2:1

Polarisation: Dual-polar (+ and - 45˚ polarisations)

Cross Polar: approx 20dB

Front to Back: approx 30dB

Isolation between beams: approx 30dB

Power requirement of each beam: 20W

The ABS plot of typical radiation pattern is represented at the figure below.



Figure ‎5-5: BuNGee ABS antenna typical radiation pattern

5.2.1 BHSS Antennas Test Procedures

Table ‎5-2: Relay Station BHSS Antenna Test Procedures

Test N

Test Purpose


1 To perform successful Initial Network Entry in LOS

condition


LOS



ANT tilt = 2 deg


INE is succeeded.

Pass

2 To perform successful Initial Network Entry in Near LOS condition


Near LOS



ANT tilt = 2


In Progress1





Test N

Test Purpose


deg

3 To perform successful Initial Network Entry in Hidden

condition


Hidden



ANT tilt = 2 deg


In Progress1

4 To perform successful Initial Network Entry in Side lob

condition


Side lob



ANT tilt = 2 deg


INE is succeeded.

Pass

5 To perform Unsuccessful Initial Network Entry in OUT of the ANT aperture

condition

Perform Unsuccessful INE based on the following combination:

Location – the CPE needs to be in the OUT of the ANT aperture

ANT tilt = 2 deg

The INE should be not successful

INE is failed. Pass


With tilt 4 deg


LOS




In Progress1





Test N

Test Purpose


ANT tilt = 4 deg


With long range


LOS

5 from the ANT


ANT tilt = 2 deg


In Progress1

8 To perform deviation in the radio parameters in back lob

Condition

Perform deviation in the radio parameters based on the following combination:


Location – back lob

Condition

ANT tilt = 2 deg

The deviation should be in the radio parameters.

In Progress1


Condition with part of the ports


LOS



ANT tilt = 2 deg

Num of Enable ports = 2


In Progress1




LOS


Location – the CPE needs to


In Progress1





Test N

Test Purpose


be in the ANT aperture

ANT tilt = 2 deg


5.2.2 ABS Antennas Test Procedures

Table ‎5-3: Relay Station ABS Antenna Test Procedures

Test N

Test Purpose



condition


LOS



ANT tilt = 2 deg


INE is succeeded.

Pass

2 To perform successful Initial Network Entry in Near LOS condition


Near LOS



ANT tilt = 2 deg


INE is succeeded.

Pass

3 To perform successful Initial Network Entry in Hidden

condition


Hidden




INE is succeeded.

Pass



Test N

Test Purpose


ANT tilt = 2 deg

4 To perform successful Initial Network Entry in Side lob condition


Side lob



ANT tilt = 2 deg



Pass

5 To perform Unsuccessful Initial Network Entry in OUT of the ANT aperture

condition

Perform Unsuccessful INE based on the following combination:

Location – the CPE needs to be in the OUT of the ANT aperture

ANT tilt = 2 deg

The INE should be Unsuccessfully

In Progress1


With tilt 4 deg


LOS



ANT tilt = 4 deg


In Progress1

7 To perform successful Initial Network Entry in LOS with long range


LOS

Long distance (e.g. 2-5 km) from the ANT

Location –


In Progress1





Test N

Test Purpose


the CPE needs to be in the ANT aperture

ANT tilt = 2 deg

8 To perform deviation in the radio parameters in back Lob Condition

Perform deviation in the radio parameters based on the following combination:


Location – back lob Condition

ANT tilt = 2 deg

It should be deviation in the radio parameters.

In Progress1

9 To perform successful Initial Network Entry in LOS Condition with part of the ports


LOS



ANT tilt = 2 deg

Num of ports = 2


In Progress1




LOS



ANT tilt = 2 deg



In Progress1





5.3 MIMO B Integration

Multiple-Input, Multiple-Output (MIMO) describes systems that use more than one radio and antenna system at each end of the wireless link. In the past it was too costly to incorporate multiple antennas and radios in a subscriber terminal. Recent advances in radio miniaturization and integration technology now makes it feasible and cost effective. Combining two or more received signals has the most immediate benefit of improving received signal strength, but MIMO also enables transmission of parallel data streams for greater throughput. For example, in a 2 x 2 MIMO (two transmit and two receive elements), dual polarization point-to-point system, the carrier‟s allocated frequency can be used twice, effectively doubling the throughput data rate.

In point-to-multipoint systems employing MIMO, each base station antenna transmits a different data stream and each subscriber terminal receives various components of the transmitted signals with each of its subscriber antennas as illustrated in the figure below. By using appropriate algorithms, the subscriber terminal is able to separate and decode the parallel simultaneously received data streams. A suite of MIMO encoding techniques for up to four antennas at each end of the link, (4 x 4 MIMO), is defined.

Figure ‎5-6: n x n MIMO Antenna System

Deployment of multiple antennas at both transmitter and receiver ends improves communication performance. MIMO benefits include the ability to provide a significant increase in coverage and capacity while leveraging bandwidth through higher spectral efficiency and link reliability.

MIMO Matrix B implementation leverages Spatial Multiplexing (SM) utilizing two (or more) multiple antenna elements at the base station and the mobile station for processing independent data streams. Data bits are split between two antennas and transmitted simultaneously as separate (non-redundant) streams. A receiver separates the independent data streams via space-time processing techniques, leveraging two orthogonal pilot patterns. As a result, MIMO Matrix B positively affects throughput capacity. Although it entails added complexity at both transmitter and receiver ends, a carrier‟s allocated frequency bandwidth capacity can be enhanced by up to 60%.



Figure ‎5-7: MIMO Matrix B

Implementation of MIMO Matrix B, efficiently employs two data streams over two antenna elements, thereby easing mobile station implementations in such a way that even basic receivers realize substantially higher performance. In addition, it increases throughput for user terminals, raising aggregate capacity and facilitating mobile station implementations.

Figure ‎5-8: Implementing MIMO Matrix B for Downlink




Table ‎5-4: MIMO B Test Procedures

Test N

Test Purpose


1 To perform successful Initial Network Entry in MIMO B condition with 1 CPE


MIMO B

1 CPE


INE is succeeded.

Pass

2 To perform successful Initial Network Entry in MIMO B condition with 3 CPE


MIMO B

3 CPEs


INE is succeeded.

Pass

3 To perform matching between theoretical & measured DL throughput in MIMO B condition with 1 CPE

Perform matching between theoretical & measured DL throughput in

MIMO B

1 CPEs

The measured DL throughput should match the theoretical one.

The measured DL throughput matches the theoretical one.

Pass

4 To perform matching between theoretical & measured UL throughput in MIMO B condition with 1 CPE

Perform matching between theoretical & measured UL throughput in

MIMO B

1 CPE

The measured UL throughput should match the theoretical one

The measured UL throughput matches the theoretical one.

Pass

5 To perform matching between theoretical & measured DL throughput in MIMO B condition with 3 CPEs


MIMO B

3 CPEs



Pass

6 To perform matching between theoretical & measured UL throughput in MIMO B


MIMO B

3 CPEs

The measured UL throughput should match the theoretical one.


Pass



Test N

Test Purpose


condition with 3 CPEs

7 To perform matching between theoretical & measured UL+ DL (bidirectional) throughput in MIMO B condition with 1 CPE

Perform matching between theoretical & measured UL+ DL (bidirectional) throughput in

MIMO B

1 CPE

The measured DL+UL (bidirectional) throughput should match the theoretical one.

The measured DL+UL (bidirectional) throughput matches the theoretical one.

Pass

8 To perform matching between theoretical & measured UL+ DL (bidirectional) throughput in MIMO B condition with 3 CPE


MIMO B

3 CPEs


The measured DL+UL (bidirectional) throughput matches the theoretical one.

Pass

9 To verify the MIMO A mode upon working with low SINRs (~10dB)

MIMO A mode will be achieved upon working with low SINRs (~10dB)= 2,4

The achieved MIMO mode should be MIMO A

The MIMO mode is MIMO A

Pass

10 To perform successful Initial Network Entry in MIMO B with 15 CPEs


MIMO B

15 CPE


INE is succeeded.

Pass



5.4 Multi-beam Assisted MIMO

By means of basic MIMO functionality, described in the previous chapter, and benefits providing by the BuNGee Multi-Beam Antenna, the Multi-Beam Assisted MIMO feature will be integrated and tested. With 4-channel MIMO, 2 channels will be using one of the antenna beams, while other 2 channels will be sent over another, adjacent antenna beam. It is assumed that urban reflections will contribute significantly to multi-path of the adjacent beams to the CPE thus improving MIMO performance.

The configuration with 4 channels MIMO over BuNGee Multi-beam antenna is presented below (in this figure Multi-Beam Antenna ports 1 and 2 are forming beam 1, while ports 3 and 4 – beam 2, adjacent to beam 1):

HBS

Beam1

Beam 2

BHSS

Multi-

Beam

Antenna

Port 1Port 2

Port 3Port 4

Figure ‎5-9: Multi-Beam Assisted MIMO




Table ‎5-5: Multi-Beam Assisted MIMO Test Procedures

Test N

Test Purpose


1 To perform successful Initial Network Entry in MIMO B with 1 CPE


MIMO B

1 CPE


In progress1



MIMO B

3 CPEs


In progress1

3 To perform matching between theoretical & measured DL throughput in MIMO B with 1 CPE

Perform matching between theoretical & measure DL throughput in

MIMO B

1 CPE


In progress1

4 To perform matching between theoretical & measured UL throughput in MIMO B with 1 CPE


MIMO B

1 CPE


In progress1

5 To perform matching between theoretical & measured DL throughput in MIMO B with 3 CPEs


MIMO B

3 CPEs


In progress1

6 To perform matching between theoretical & measured UL throughput in MIMO B with 3 CPEs


MIMO B

3 CPEs


In progress1





7 To perform matching between theoretical & measured UL+ DL (bidirectional) throughput in MIMO B with 1 CPE


MIMO B

1 CPE


In progress1

8 To perform matching between theoretical & measured UL+ DL (bidirectional) throughput in MIMO B with 3 CPEs


MIMO B

3 CPEs


In progress1

9 To verify the MIMO A mode upon working with low SINRs (~10dB)

MIMO A mode will be achieved upon working with low SINRs (~10dB)= 2,4

The achieved MIMO mode should be MIMO A

In progress1



MIMO B

15 CPEs


In progress1

5.5 In-band Backhauling Network Architecture Based on L3 Tunnelling

In-band backhauling link solution (called also “relay”) is based on the standard IEEE 802.16 PHY/ MAC layers without significant air interface changes. This implies reuse of WiMAX industry eco system – BS and access device chipsets.

The solution assumes decomposition of “Relay” entity into two functional elements - Relay BS (Access BS) and Relay MS (BHSS), used as the feeding for the Relay BS. Off-the-shelf networking interface (such as Eth) is assumed between BHSS and ABS. Multiple Relay BS entities (ABSs) may be fed by a single Relay MS (BHSS).

For BuNGee Live Demo deployment, based on the allocated frequency bands, Backhauling and Access tiers are implemented using 20 MHz channels in different frequency bands – 3.5 GHz and 2.5 GHz correspondingly. As such, there is enough isolation provided between RS CPE (BHSS) and RS BS (ABS) to avoid self-deafening relay station blocking issue. Separate test scenario, emulating self-deafening issue is considered.

Network architecture for Relay solution is using L3 approach – based on standard networking R6/ R8 interfaces:





Figure ‎5-10: Network architecture for Relay/ in-band backhauling

In order to simplify the description, each device mentioned at the Topology scheme is assigned a unique identifier. It has a format of dot-separated numbers and contains the following details: [“Hub BTS number” . ”Sector Number”. “Carrier Number“]. For instance – “HBS 1.1.1” means that the mentioned HBS belongs to the HUB BTS = 1, Sector Number = 1 and Carrier Number = 1.

Schematically the End–To-End Lab Setup network topology can be presented as follows:

AAA

Router

172.30.16.2

ASNGW

172.30.16.1

Bearer VID=11

Bearer IP = 192.168.1.100

Bearer DG = 192.168.1.254

AAA server. = 172.30.16.2

Trunk port

HBS 1.1.1

BHSS 1.1.1

Bearer VID=11

Bearer IP = 192.168.1.1

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100VPWS (VID=21)

ABS 1.1.1

Bearer VID=21

Bearer IP = 192.168.200.1

Bearer DG = 192.168.200.254

Authent. = 192.168.1.100VLAN 11 IP = 192.168.1.254

VLAN 21 IP = 192.168.200.254

VLAN 23 IP = 192.168.201.254

SS 1.1.1

IP=10.0.0.X

HBS 1.1.2

BHSS 1.1.2

Bearer VID=11

Bearer IP = 192.168.1.2

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=23)

ABS 1.1.2

Bearer VID=23

Bearer IP = 192.168.201.1

Bearer DG = 192.168.201.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 1.1.2

Switch\ Hub

HBS 2.1.2

BHSS 2.1.2

Bearer VID=11

Bearer IP = 192.168.1.8

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=35)

ABS 2.1.2

Bearer VID=35

Bearer IP = 192.168.207.1

Bearer DG = 192.168.207.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 2.1.2

VLAN 35 IP = 192.168.207.254

VLAN-CS IP-CS

SI VID = 101

Trunk port

Trunk port

Trunk port

Trunk port

Core Server

172.31.16.1

172.31.16.2

VLAN 101 IP = 10.0.0.101

SG Own IP=10.0.0.100

SI Next Hop = 10.0.0.101

Figure ‎5-11: Physical scheme of End–To-End Laboratory topology

The setup should be provisioned according to the following IP-Network Planning table:



Table ‎5-6: Setup IP Network Planning

N Device name

Configuration Object

Configuration Parameter Value

1. ASNGW Service Interface (type = “Vlan”)

VLAN ID 101


Next Hop IP-Address 10.0.0.101

3. ASNGW IP-CS Service Group 1

Own IP-Address 10.0.0.100


DHCP Pool (10.0.0.1..10.0.0.24)\24

5. ASNGW Bearer Interface VLAN ID 11

6. ASNGW Bearer Interface Default Gateway 192.168.1.254

7. ASNGW AAA Client AAA Server IP-Address 172.30.16.2

8. ASNGW VPWS Service Group 1

VLAN ID 21


VLAN ID 23


VLAN ID 25


VLAN ID 27


VLAN ID 29


VLAN ID 31


VLAN ID 33


VLAN ID 35

16. Router VLAN 11 IP-Address 192.168.1.254










26. Router Interface Gi0/1 (towards AAA)

IP-Address 172.30.16.1



27. Router Interface Gi0/2 (towards ASNGW)

Switchport Mode Trunk (all possible VLANs are forwarded)

28. Router Interface Gi0/3 (towards Switch)


29. Router Interface Gi0/4 IP-Address 172.31.16.1

30. Core Server NIC IP-Address 172.31.16.2

31. Switch Gi0/1 Switchport Mode Trunk (all possible VLANs are forwarded)



34. HBS 1.1.1 Bearer Interface VLAN ID 11

35. HBS 1.1.1 Bearer Interface IP-Address 192.168.1.1

36. HBS 1.1.1 Bearer Default Gateway

IP-Address 192.168.1.254

37. HBS 1.1.1 Default Authenticator

IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100






IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100

66. ABS 1.1.1 Bearer Interface VLAN ID 21

67. ABS 1.1.1 Bearer Interface IP-Address 192.168.200.1

68. ABS 1.1.1 Bearer Interface Default Gateway IP-Address 192.168.200.254

69. ABS 1.1.1 Default Authenticator

IP-Address 192.168.1.100





IP-Address 192.168.1.100





IP-Address 192.168.1.100





IP-Address 192.168.1.100





IP-Address 192.168.1.100







IP-Address 192.168.1.100





IP-Address 192.168.1.100





IP-Address 192.168.1.100

5.5.1 Backhauling Tier

The transport of user‟s Ethernet frames across the Core Network of Service Provider is performed by means of Virtual Pseudo-Wire Service (VPWS) with functional type = “Transparent”. This is point-to-point cross-connect address un-aware service, based on VLAN tagging in the network. This is implemented using L2 leased line service, aka VPWS capability. The end-to-end L2 virtual link provides connectivity to any L2 traffic between the two end-points. In the VPWS mode all ip-addresses for network elements (BS, CPE) are allocated statically and won‟t be obtained by means of DHCP. User traffic (Ethernet frames) is carried across the ASN in the form of VLAN frames. User VLAN is generated either by user equipment (for example office router or switch) or appended by WiMAX CPE.

Figure ‎5-12: VPWS service

Eventually each Access Base Station should segregate its own R6 data, using separate VLANs. Thereby – the VPWS Transparent Service Group will be defined within an ASNGW and for each pre-provisioned CPE (BHSS) the particular VLAN ID will be allocated in order to allow proper downlink and uplink classification.



5.5.1.1 Test Procedures

The following list of test procedures will be repeated for each of 8 Hub Base Station carrier-sectors.

Table ‎5-7: Backhauling VPWS Test Procedures

Test N

Test Purpose

Test Description Expected Results Actual Results Status

1. To perform successful Initial Network Entry


SG type = VPWS Transparent

The VLAN Classification Rule is included


INE is succeeded.

Pass

2. To transmit successfully tagged by proper VLAN ID traffic in both directions

Transmit bi-directional traffic tagged by VLAN ID = X between the Core Server and the BHSS based on the following configuration:

Service Group type = VPWS Transparent.

Classification Rule VLAN ID=X

The traffic tagged by VLAN ID = X should successfully pass in both directions (downlink and uplink).

The tagged traffic is passed successfully in both directions.

Pass

3. To verify that untagged traffic is rejected

Transmit bi-directional untagged traffic between the Core Server and the BHSS based on the following configuration:



The bidirectional untagged traffic should be rejected (downlink and uplink).

The untagged traffic is rejected.

Pass

4. To verify that traffic tagged by irregular VLAN ID is rejected (anti-spoofing)

Transmit bi-directional traffic tagged by VLAN ID = Y between the Core Server and the BHSSbased on the following configuration:



The bidirectional traffic tagged by VLAN ID = Y should be rejected (downlink and uplink).

The bidirectional traffic tagged by VLAN ID = Y is rejected (downlink and uplink).

Pass

5. To verify that INE is failed

Perform INE based on the following

The INE should fail

The INE is failed Pass



Test N

Test Purpose


unless proper Classification rule is defined

combination:

no VLAN Classification Rule is included

Service Group type = VPWS Transparent

6. Check whether Accounting Start Message is sent properly




The VLAN Classification Rule is included.

Verify that ASNGW sends Accounting Start Message on successful data path establishment.

The Accounting Start Message should be sent by ASNGW towards AAA upon the successful INE is performed.

The Accounting Start Message has been sent as expected.

Pass

7. Check whether Accounting Stop Message is sent properly




The VLAN Classification Rule is included.

Verify that at least 1 CPE is connected. De-register this CPE and verify that the Accounting Stop Message is sent by ASNGW towards a AAA server.

The Accounting Stop Message should be sent by ASNGW towards an AAA server upon CPE de-registration.

The Accounting Stop Message has been sent as expected.

Pass

8. Verify correctness of IP-CS/VLAN-CS co-existence




Then Perform additional INE with the following configuration:

Both INEs (either IP-CS and VLAN-CS) should be successfully accomplished and bi-directional traffic should pass

Both INEs are successful, traffic is passed

Pass



Test N

Test Purpose


SG type=”IP-CS”

Both services will be defined within the same ASNGW

9. To measure the VPWS Maximum Downlink Traffic Rate per 1 BHSS




From the Core Server Generate DL traffic towards BHSS with a rate = 30 Mbps. Measure the received by BHSS traffic rate.

The DL traffic rate received by BHSS should be about 30 Mbps

The DL traffic rate received by BHSS is about 30 Mbps

Pass

10. To measure the VPWS Uplink Traffic Rate per 1 BHSS




From the BHSS generate an UL traffic towards the Core Server with the rate = 4.3 Mbps. Measure the received by the Core Server traffic rate.

The received by the Core Server traffic rate should be about 4.3 Mbps

The received by the Core Server traffic rate is about 4.3 Mbps

Pass

5.5.2 Access Tier

The Access tier implementation is performed on the IP-CS basis. The IP-address allocation will be done by means of the DHCP process. For this purpose the IP-CS Service Group will be defined within the ASNGW. It will be configured as a DHCP server and will be responsible for the IP-Address allocation procedure. Every connected user will be assigned to the common Service Interface providing an access to the subscriber‟s service domain (such as Internet, applications zone, etc.).

5.5.2.1 Test Procedures

Table ‎5-8: Access Tier Test Procedures

Test N

Test Purpose


1. To perform successful

Perform INE based on the following

The INE should be successfully

INE is succeeded, IP-

Pass



Test N

Test Purpose


Initial Network Entry

configuration:

SG type = IP-CS

SG DHCP mode = “Server”

accomplished; IP-address should be allocated.

Address is allocated.

2. To transmit successfully traffic in both directions

Transmit bi-directional traffic between the Core Server and the SS based on the following configuration:

Service Group type = IP-CS

The traffic should successfully pass in both directions (downlink and uplink).

The traffic is passed successfully in both directions.

Pass

3. To verify the Bearer VLAN modification mechanism

Configure a bearer VLAN for each of ABSs with the appropriate VLAN ID (refer the Setup IP Network Planning table).

The ABS should tag packets transmitted towards ANSGW via the R6 interface with the defined VLAN ID and not with default VLAN ID = 11.

Packets are tagged with correct VLAN ID.

Pass

4. To measure the IP-CS Uplink Traffic Rate per 1 SS


SG type = IP-CS


From the SS generate an UL traffic towards the Core Server with the rate = 4.3 Mbps. Measure the received by the Core Server traffic rate.

The received by the Core Server traffic rate should be about 4.3 Mbps

The received by the Core Server traffic rate is about 4.3 Mbps.

Pass

5. To measure the VPWS Maximum Downlink Traffic Rate per 1 BHSS


SG type = IP-CS


From the Core Server Generate DL traffic towards SS with a rate = 30 Mbps.

The DL traffic rate received by SS should be about 30 Mbps.

The DL traffic rate received by SS is about 30 Mbps.

Pass



Test N

Test Purpose


Measure the received by SS traffic rate.

6. To test Intra-Site Hand Over


SG type = IP-CS


Initiate a SS1 HO between BHSS 1.1.1 and BHSS 1.1.2. Verify that no packet loss is occurred.

The Intra-Site Handover should be successful.

The Intra-Site HO proceeded as expected.

Pass

7. To test Inter-Site Hand Over


SG type = IP-CS


Initiate a SS6 HO between BHSS 1.1.6 and BHSS 2.1.1. Verify that no packet loss is occurred.

The Inter-Site Handover should be successful.

The Inter-Site HO proceeded as expected.

Pass

8. To test various kinds of traffic - FTP


SG type = IP-CS


Run an FTP server at the Core Server. From the PC behind the SS1 by means of FTP copy a 1MByte test file to the Core Server.

The FTP copying process is supposed to take about 1 min and 40 sec (with UL traffic rate = 5Mbps)

The FTP copying process has taken about 1 min and 40 sec (with UL traffic rate = 5Mbps)

Pass

9. To test various kinds of traffic – Video Stream


SG type = IP-CS


Run a Streamer Server in the Core

The quality of receiving video should be high.

The quality of the received video stream is as expected.

Pass



Test N

Test Purpose


Server.

Run a Stream Client in the PC behind a SS.

Transmit a clip with HD quality from the Stream Server towards the SS.

10. To check the Keep Alive Mechanism


SG type = IP-CS


Enabled ASNGW KA and ABS KA

Verify that upon CPE is connected – the appropriate ABS polls an ASNGW as per pre-defined KA time out.

Make reset to ASNGW.

Verify that ABS disconnects the connected CPE as soon as KA time out, retransmissions time out and retransmissions attempts number are exceeded.

Verify that the ABS disconnects a CPE upon ASNGW reset

ABS has disconnected a CPE upon ASNGW reset.

Pass

5.6 Multi-Carrier Support

Joining more than 1 AU channels (e.g. of 10 MHz) to the same radio head using an IF-MUX device enables multi carrier environment with cost effective deployment. A base station implements multiple sectors. Each sector may employ multiple carriers. Sector is defined by the location of the base station, the direction of the pointed antennas and the beam width. Sector may have more than 1 frequency range. For this purpose radio cluster entity is introduced. Total bandwidth is the sum of 1 channel and its adjacent channel bandwidth. Frequency of the shared radio resource is defined as the frequency between the 2 adjacent carriers.

An AU is able to transmit with bandwidth 10 MHz and ODU has a saw filter of 20 MHz, therefore by joining 2 AUs by means of Mixer Unit (IF_MUX) it is possible to achieve a transmit total bandwidth of 20MHz.



Figure ‎5-13: 20 MHz beam

The basic unit allows a single ODU TX/RX IF channel to be connected via the IF-MUX to 2 AU IF channels. AUs belonging to the same Radio Cluster should be defined either with Multi-Carrier Mode = Master or Slave. The Master AU will manage the cable compensation over TCP/IP protocol via inter AUs internal management interfaces and will manage the ODU considering ASK channel and RF algorithms. The Slave AU will be managed by the master for cable compensation and will not affect on ODU management.

For simplicity purposes, according to the current concept, master failure will not be replaced by the slave. In order to recover the Master AU the operator shall replace the Master or reset it.

Schematically the IF-MUX installation is presented at the figure below.



Figure ‎5-14: IF-MUX Installation

The cables attachment to the box and to the connectors shall be water proof. Cable type attached to the box integrally shall be LMR-195. Each integrally attached cable length shall be 1m and extendable to 5m or more. It is required to use the same length extensions for cable compensation balancing. The maximum cable length can be used between the IFMUX and the ODU assuming that the DC voltage drop over the cable is 1VDC is as follows:

LMR-400 – up to 150m



Figure ‎5-15: IF-MUX



Test Procedures

In order to test the basic Multi-carrier functionality the following setup will be constructed:


1

2

3

4

2

3

4

IF-

MUX 1

IF-

MUX 2

AU1

Master

AU2

Slave

ODU1 (2x2)

(F1\F2)1

2

1 1SS 1

(F1)

SS 3

(F1)

1SS 2

(F2)

SS 4

(F2)

Core

Network

Sector

1

Sector

2


1

2

1

2

ODU3 (2x2)

(F1\F2)

1

Radio Cluster 1

1

2

1

ODU2 (2x2)

(F1\F2)

2

2

1

2

3

4

2

3

4

IF-

MUX 3

IF-

MUX 4

AU3

Master

AU4

Slave

1

Radio Cluster 2

SS 5

(F1)

SS 6

(F2)

Sector

3

1

2

3

4

2

3

4

IF-

MUX 5

IF-

MUX 6

AU1

Master

AU2

Slave

1

Radio Cluster 1

Figure ‎5-16: Multi-Carrier Setup

Table ‎5-9: Multi-Carrier Test Procedures

Test N

Test Purpose Test Description Expected Results Actual Results Status

1. To verify proper configuration options

By means of CLI\ Alvaristar within the same Radio Cluster will be configured 1 AU as Master and another – as Slave. Will be verified that the configuration is accepted and the system is started in a correct way

The configuration should be accepted and the system should be started properly

The configuration has been accepted and the system has been started properly

Pass

2. To verify invalid configuration treatment

By means of CLI\ Alvaristar within the same Radio Cluster will be configured both AUs as Master. Will be verified that the configuration is not accepted and the related notification

The invalid configuration (both Aus within the same Radio Cluster are defined as Master) should be rejected

The invalid configuration (both Aus within the same Radio Cluster are defined as Master) is rejected

Pass



Test N


message is issued by CLI\Alvaristar

3. To verify that a Slave AU stops transmitting upon a Master AU is faulty\shut down

Configure two collocated AUs -Master and Slave. Connect an IF MUX as shown at the Multi-Carrier Setup figure.

Verify that the AUs are up and work properly. Turn off the Master BS.

The Slave AU must stop transmit.

To verify that a Slave AU doesn‟t transmit if a Master AU is down.

The Slave AU stops transmission as soon as the Master AU is turned off.

Pass

4. To verify the Master‟s AU behaviour in a case when a Slave AU is shut down. In such occasion a Master AU should begin behave as a stand-alone AU.

Configure two collocated AUs -Master and Slave. Connect an IF MUX as shown at the Multi-Carrier Setup figure.

Verify that the AUs are up and work properly. Turn off the Slave BS.

After passing of 4 minutes - the Master AU should begin working as a Stand-Alone AU with no IF-MUX installed.

To verify that after passing of 4 minutes - the Master AU begins working as a Stand-Alone AU with no IF-MUX installed.

The Master AU behaves as expected.

Pass

5. To perform successful Initial Network Entry with 2 different Central Frequencies within the same sector

For each of 3 sectors will be connected 2 CPEs where the 1

st

will be connected with a Central Frequency (F1) and the 2

nd – with (F2).

INEs should be successful

INEs are successful

Pass

6. To verify successful Hand Over procedure between 2 IF Mux sectors and same frequencies (F1->F1,F2->F2)

Will be performed HO with SS1 between the Sector 1 and the Sector 2 with Central Frequency (F1).

Then will be run HO with SS2 between the Sector 1 and the Sector 2 with the Central Frequency (F2).

The appropriate HOs

HOs should be successful

HOs are successful

Pass



Test N


will be done for SS3...SS6 as well.

7. To verify successful Hand Over procedure within the same sectors with different frequencies (F1->F2,F2->F1)

Will be performed HO with SS1 within the Sector 1 from Central Frequency (F1) to (F2).

Then will be run HO with SS2 within the Sector 2 from Central Frequency (F2) to (F1).

The appropriate HOs will be done for SS3...SS6 as well.

HOs should be successful

HOs are successful

Pass

8. To achieve the Downlink throughput=60 Mbps within 1 sector

Perform INE for SS1 and SS2.

From the Core Server Generate DL traffic towards SS1 with a rate = 30 Mbps and for SS2 – 30 Mbps.

Measure the received by SS1 and SS2 traffic rate.

Make the appropriate tests for rest of SSs (SS3…SS6)

The DL traffic rate received by each of SSs should be about 30 Mbps

Ongoing

9. To achieve the Uplink throughput = 10Mbps within 1 sector

Perform INE for SS1 and SS2.

From the SS1 and SS2 generate an UL traffic towards the Core Server, each - with the rate = 4.3 Mbps. Measure the received by the Core Server traffic rate.

Repeat the test for the rest of SSs (SS3..SS6)

The total received by the Core Server traffic rate should be about 10 Mbps (from SS1+SS2)

Ongoing

10. To achieve the total throughput density for 3 sectors about 210 Mbps

Perform INE for SS1..SS6.

From the Core Server Generate DL traffic for each of connected SSs (SS1..SS6) with a rate = 30 Mbps.

Simultaneously from each of connected SSs (SS1..SS6) generate an UL

The total traffic (DL+UL) should be about 210 Mbps

Ongoing



Test N


traffic with the rate = 5Mps.

Measure the total throughput of traffic received by the Core Server and SSs (SS1..SS6)

5.7 Multi-Carrier Link Aggregation

Multi-carrier link aggregation is used in order to achieve increased throughput between Backhaul and Access tiers. The topology of the Multi-Carrier Link Aggregation is presented in the figure below. The project does not develop the specific aggregation and network load balancing functionality but rather uses off-the-shelf products emulating the required functions.

Nowadays there are many various load-balancing algorithms and methods based on dynamic routing protocols (e.g. EIGRP, RIP, OSPF), vendor‟s proprietary protocols (e.g. Cisco‟s CEF, GLBP) or static configuration. The convenience, maintenance simplicity and high functional reliability of the Cisco‟s static load-balancing mechanism can encourage network designers to implement it for various wired and wireless networks. Cisco router was selected as the emulator of the required functionality.

Static load-balancing in Cisco routers may be enabled using the following approaches ‎[1]:

per-destination basis;

per-packet basis.

Per-destination load balancing means the router distributes the packets based on the destination address. Given two paths to the same network, all packets for destination 1 on that network go over the first path; all packets for destination 2 on that network go over the second path, and so on. This preserves packet order, with potential unequal usage of the links. If one host receives the majority of the traffic all packets use one link, which leaves bandwidth on other links unused. A larger number of destination addresses leads to more equally used links.

Per-packet load-balancing means that the router sends one packet for destination 1 over the first path, the second packet for (the same) destination 1 over the second path, and so on. Per-packet load balancing guarantees equal load across all links. For per-packet load balancing, the forwarding process determines the outgoing interface for each packet by looking up the route table and picking the least used interface. This ensures equal utilization of the links.

For our case the Per-packet load-balancing method will be used.

Aggregation Router 1

WiMax Multi-Carrier Link 1 (Vlan 21)

Vlan 23

192.168.2.100

Vlan 23

192.168.2.1

Vlan 21

192.168.1.1

WiMax Multi-Carrier Link 2 (Vlan 23)

Aggregation Router 2

Vlan 21

192.168.1.100

Figure ‎5-17: Equal Static Link Aggregation



It is supposed that both Wimax links have approximately equal throughput ability, therefore the system will be provisioned in such a way that in both directions 50 percents of traffic will pass via the Link 1 and 50 per cent – via the Link 2. In order to achieve this, both routers will be defined with multiple static entries of default routes on the second router, e.g.:

Router1(config)#ip route 0.0.0.0 0.0.0.0 192.168.1.100




The configuration described above will urge traffic to be shared between 2 equal-throughput connections.


The laboratory installation should be built with accordance to the figure below. The bi-directional traffic issued by packet generators will be spit between 2 WiMax Multi-Carrier links.

The aggregation routers are responsible for the equal load-balancing performance. They should be configured in such way that in Downlink and Uplink directions (traffic issued by the Packet Generator A towards the Packet Generator B and vice-versa) data should be split with respect to the equal proportion.

In order to measure Downlink and Uplink throughput 4 sniffers will be connected along the links. Each of 2 WiMAX links should be provisioned as described in the item 5.5.1 “Backhauling tier” (based on the VPWS principles).

The Interface Gi0/2 of the Aggregation Router 1 will be defined as a trunk and will allow VLAN 21 and VLAN 23 (VLANs used for data-plane traffic tagging by VPWS services of Multi-Carrier Links 1 and 2).

The Interface Gi0/2 of the Aggregation Router 2 will be defined as a trunk and will allow VLAN 21. The Interface Gi0/3 will be defined as a trunk and will allow VLAN 23.

Packet Generator A Packet Generator BAggregation

Router 1

HBS1

BHSS 1Aggregation

Router 2

WiMax Multi-Carrier Link 1

Sniffer 3

Hub 2

Sniffer 1 Sniffer 4

Hub 1 Hub 4

Gi0/1Gi0/2

Gi0/3Sniffer 2

HBS2

BHSS 2

WiMax Multi-Carrier Link 2

Hub 3

ASNGW

Gi0/1Gi0/2

VLAN21

VLAN23

VLAN21

VLAN23

Figure ‎5-18: Multi-Carrier Link Aggregation Setup



Table ‎5-10: Multi-Carrier Link Aggregation Test Procedures

Test N


1. To ensure correctness of the setup configuration

The setup will be installed and configured as described above.

The full End-To-End setup should be properly installed and provisioned. The Aggregation Router‟s interfaces, connected towards Wimax Multi-Carrier links should be UP. Will be checked that HBSs are UP and BHSSs are connected.

The Setup is prepared successfully.

Pass

2. Backhauling Redundancy.

To verify that upon deletion in the Aggregation Router 1 of a static route towards VLAN 23, all the DL traffic is directed through the VLAN 21, i.e. Multi-Carrier Link 1.

The static route towards VLAN 23 will be deleted in the Aggregation Router 1.

From the Packet Generator A will run traffic with bit rate = 30 Mbps. By means of the Sniffer 2 will be checked that all t the DL traffic is directed through the VLAN 21, i.e. Multi-Carrier Link 1.

All the DL traffic should be sent via the VLAN 21, i.e. Multi-Carrier Link 1. The traffic rate is about 30 Mbps.

All the DL traffic is sent via the VLAN 21, i.e. Multi-Carrier Link 1. The traffic rate is about 30 Mbps as expected.

Pass


To verify that upon deletion in the Aggregation Router 1 of a static route towards VLAN 21, all the DL traffic is directed through the VLAN 23, i.e. Multi-Carrier Link 2.


From the Packet Generator A will run traffic with bit rate = 30 Mbps. By means of the Sniffer 3 will be checked that all the DL traffic is directed through the VLAN 23, i.e. Multi-Carrier Link 2.

All the DL traffic should be sent via the VLAN 23, i.e. Multi-Carrier Link 2. The traffic rate should be about 30 Mbps.

All the DL traffic is sent via the VLAN 21, i.e. Multi-Carrier Link 2. The traffic rate is about 30 Mbps as expected.

Pass


To verify that upon deletion in the Aggregation


From the Packet

All the UL traffic should be sent via the VLAN 21, i.e. Multi-Carrier Link 1. The traffic rate should be about

All the UL traffic is sent via the VLAN 21, i.e. Multi-Carrier Link 1. The traffic rate is about 4.3

Pass



Test N


Router 2 of a static route towards VLAN 23, all the UL traffic is directed through the VLAN 21, i.e. Multi-Carrier Link 1.

Generator B will be run traffic with bit rate = 4.3 Mbps. By means of the Sniffer 2 will be checked that all the UL traffic is directed through the VLAN 21, i.e. Multi-Carrier Link 1.

4.3 Mbps. Mbps as expected.


To verify that upon deletion in the Aggregation Router 2 of a static route towards VLAN 21, all the UL traffic is directed through the VLAN 23, i.e. Multi-Carrier Link 2.


From the Packet Generator B will run traffic with bit rate = 4.3 Mbps. By means of the Sniffer 3 will be checked that all the UL traffic is directed through the VLAN 23, i.e. Multi-Carrier Link 2.

All the UL traffic should be sent via the VLAN 23, i.e. Multi-Carrier Link 2. The traffic rate should be about 4.3 Mbps.

All the UL traffic is sent via the VLAN 21, i.e. Multi-Carrier Link 2. The traffic rate is about 4.3 Mbps as expected.

Pass

6. To check that DL traffic is split with proportion 50:50 between 2 Multi-Carrier WiMax links.

Will be verified that both Wimax Multi-Carrier links are UP.

From the Packet Generator A run traffic with data rate = 30 Mbps.

By means of Sniffers 2 and 3 verify that data is shared between both Multi-Carrier Links in a proportion 50:50.

The DL data rate of traffic passing through each of links should be about 15 Mbps.

The DL data rate of traffic passing through each of links is about 15 Mbps.

Pass

7. To check that UL traffic is split with proportion 50:50 between 2 Multi-Carrier WiMax links.

Will be verified that both Wimax Multi-Carrier links are UP.

From the Packet Generator B run traffic with data rate = 6 Mbps.

By means of Sniffers 2 and 3 verify that data is shared between both Multi-Carrier Links in a proportion 50:50.

The UL data rate of traffic passing through each of links should be about 3 Mbps.

The UL data rate of traffic passing through each of links is about 3 Mbps.

Pass

8. To measure The static route The maximum DL The measured Pass



Test N


the maximum DL and UL throughput via a single link.

towards VLAN 23 will be deleted in the

Aggregation Routers 1 and 2. From the Packet Generator A will be run traffic with bit rate = 60 Mbps and from the Packet Generator B will be run traffic with data rate = 8.6 Mbps.

By means of Sniffers 1 and 4 will be verified that the maximum DL throughput through the Wimax link is about 30 Mbps and UL – 4.3 Mbps.

throughput via WiMax connection should be about 30 Mbps.

The Maximum UL traffic throughput via WiMax connection is about 4.3 Mbps

throughput is as expected.

9. To ensure that the selected Data Aggregation approach implies an increase of total DL throughput.

Will be verified that both Multi-Carrier Links are UP and the related routing entries are defined.

From the Packet Generator A will be run traffic with data rate = 60 Mbps. With the Sniffer 4 will be checked that the received data rate is about 60 Mbps.

By means of the Link Aggregation approach, the total DL throughput should be about 60 Mbps.

As expected. Pass

10. To ensure that the selected Data Aggregation approach implies an increase of total UL throughput.

Will be verified that both Multi-Carrier Links are UP and the related routing entries are defined.

From the Packet Generator B will be run traffic with data rate = 8.6 Mbps. With the Sniffer 1 will be checked that the received data rate is about 8.6 Mbps.

By use of the Link Aggregation approach, the total UL throughput should be about 8.6 Mbps

As expected. Pass

5.8 Inter-Carrier Load Balancing

The Multi-Carrier approach implies providing of 20 MHz bandwidth for a single sector. Two co-located Base Stations serve such sector; each of them provides its own Central Frequency. Thereby there is a dilemma – which Base Station to select for associating of new connections. In order to decrease a load of each of Base Stations and prevent resource starvation, it‟s essential to use the Load Balancing mechanism within the Multi-Carrier sector. The implemented by Alvarion Multi-Carrier Load Balancing approach is based on the round-robin method of incoming CPEs distribution between both Master and Slave Base Stations serving the



sector. A Radio Cluster‟s scheduler modifies a connection pointer between Master and Slave BS within the sector each time when new CPE performs an Initial Network Entry.

Master BS

Slave BS

ODU 2x2

Antenna

CPE 1

CPE 2

CPE 3

CPE 4

Figure ‎5-19: Inter-Carrier Load Balancing Setup


In order to evaluate the Inter-Carrier Load Balancing functionality the testing setup should be installed with accordance to the figure above. In the laboratory conditions the RF wires between ODU and CPEs can be used instead of antenna and air links. The following installation variations should be used for the described below tests:

1 BTS including 1 Multi-Carrier sector;

1 BTS including 2 Multi-Carrier sectors;

2 BTSs, where each of them includes 1 Multi-Carrier sector.

2 BTSs, where 1 of them includes 1 Multi-Carrier sector and the second – 1 Single-Carrier sector.

Table ‎5-11: Inter Carrier Load Balancing Test Procedures

Test N


1. To verify that the 1

st CPE is

connected to Master BS.

The sector will be provisioned with a Radio Cluster including a Master BS and a Slave BS.

Will be performed INE for 1 CPE and verified that it‟s connected to the Master BS.

The first coming CPE will connect to the Master BS.

The CPE is connected to the Master BS.

Pass

2. To check the round-robin mechanism

Will be connected 4 CPEs and verified that each of BSs

Upon 4 CPEs enters the network – 2 should be

The CPEs are connected as

Pass



Test N


for 4 MSs. within the Radio Cluster (Master and Slave) holds 2 connected MS.

connected to the Master and 2 – to the Slave BS.

expected

3. To verify the system‟s behavior upon Slave BS shut down.


Will be ensured that both BS are up.

4 CPEs will be connected. Among them 2 will be connected to the Master BS and 2 – to the Slave BS.

Then the Slave BS will be shut down.

Will be verified that 2 CPEs disconnected from the Slave BS will connect to the Master BS.

The disconnected CPEs from the faulty\shut down Slave BS should connect to the Master BS.

The CPEs have been connected to the Master BS as expected.

Pass

4. To verify the Inter-Carrier Load Balancing in case of Inter-BTS Hand Over

In 2 BTSs will be provisioned 2 sectors (1 sector per BTS) , where each of them will include a Radio Cluster with 2 BSs (Master and Slave). 4 CPEs will be connected to the first sector.

By means of modification of links attenuation all 4 CPEs will be urged to perform HO towards the second sector.

Will be verified that from 4 MSs performed HO, 2 are connected to the Master BS and 2 – to the Slave BS.

Upon performing HO by 4 CPEs -they should be distributed equally between target BSs (2 CPEs should be connected to the Master BS and 2 – to the Slave).

The CPEs have been collocated between the Master and the Slave BSs as expected.

Pass

5. To verify the Intra-Carrier Load Balancing in case of Inter-BTS Hand Over.

In 1 BTSs will be provisioned 2 sectors, where each of them will include a Radio Cluster with 2 BSs (Master and Slave). 4 CPEs will be connected to the

Upon performing HO by 4 CPEs -they should be distributed equally between target BSs (2 CPEs should be connected to the

The CPEs have been collocated between the Master and the Slave BSs as expected.

Pass



Test N


first sector.

By means of modification of links attenuation all 4 CPEs will be urged to perform HO towards the second sector.

Will be verified that from 4 MSs performed HO, 2 are connected to the Master BS and 2 – to the Slave BS.

Master BS and 2 – to the Slave).

6. To verify that as a result of re-INE – CPEs are still distributed equally between BSs – members of the same Radio Cluster (Master and Slave).

Will be connected 4 CPEs and verified that each of BSs within the Radio Cluster (Master and Slave) holds 2 connected MS.

De-register all of CPEs and verify that they perform re-INE with accordance to the same equal proportion to the members of the sector (2 CPEs will re-enter the Master BS and 2 – the Slave).

After de-registration and re-INE, CPE should be equally distributed between the Master and the Slave BSs within the sector.

The CPEs performed a re-INE with respect to the Inter-Carrier load Balancing algorithm, as expected.

Pass

7. To check a HO between Multi-Carrier and Single-Carrier sectors.

The 1st BTS will be

provisioned with 1 Multi-Carrier sector, which includes a Radio Cluster with 2 BSs (Master and Slave). 4 CPEs will be connected to the first sector (2 CPEs will be connected to the Master BS and 2 – to the Slave).

The second BTS will be provisioned with 1 Single-Carrier sector.

By means of modification of links attenuation all 4 CPEs will be urged to perform HO towards the Single-Carrier Sector. Will be verified that no de-registrations or

The HO between Multi-Carrier and Single-Carrier sectors should be successful.

The HO between Multi-Carrier and Single-Carrier sectors is successful.

Pass



Test N


re-INE are performed.

8. Stability test: To check a massive inter-BTS HO by CPEs with running traffic.

In 2 BTSs will be provisioned 2 sectors (1 sector per BTS) , where each of them will include a Radio Cluster with 2 BSs (Master and Slave). 50 CPEs will be connected to the first sector. For each of connected CPEs will be generated UL\DL traffic.

By means of modification of links attenuation 10 CPEs will be urged to perform HO towards the second sector.

Will be verified that all 10 performed HO CPEs successfully entered to the second sector and equally distributed between the Master and the Slave BSs. Will be ensured that no de-registrations are performed and no re-INE discovered. The traffic should remain stable.

The massive inter-BTS HO between 2 Multi-Carrier sectors should be successful.

The Massive inter-BTS HO is successful.

Pass

9. Stability test: To check a massive intra-BTS HO by CPEs with running traffic.

In 1 BTS will be provisioned 2 sectors where each of them includes a Radio Cluster with 2 BSs (Master and Slave). 50 CPEs will be connected to the first sector. For each of connected CPEs will be generated UL\DL traffic.

By means of modification of links attenuation 10 CPEs will be urged to perform HO towards the second sector.

Will be verified that all 10 performed HO

The massive intra-BTS HO between 2 Multi-Carrier sectors should be successful.

The Massive intra-BTS HO is successful.

Pass



Test N


CPEs successfully entered to the second sector and equally distributed between the Master and the Slave BSs. Will be ensured that no de-registrations are performed and no re-INE discovered. The traffic should remain stable.

10. Stability test:

To perform a massive simultaneous INE and verify the Multi-Carrier Load Balancing behaves as defined.


Simultaneously connect 350 CPEs. Verify that CPEs are distributed equally between the Master

and the Slave BSs.

175 CPEs should be connected to the Master BS and 175 – to the Slave.

The massive INE is performed successfully, CPEs distributed in an equal proportion between the Master and the Slave.

Pass

5.9 Backhauling Multi-Link Aggregation

In order to achieve increased throughput in the Backhaul tier the link aggregation and load balancing between Point-to-Multipoint WiMAX system (HBS-BHSS) and mmWave Point-to-Point link is used. The topology is presented at the figure below. In the laboratory‟s conditions the mmWave link is replaced by the Gigabit Ethernet Point to Point wired connection.

The Cisco‟s static load-balancing functionality has been selected as a tool the Backhauling Multi-Link Aggregation purposes. This approach is particularly described at the chapter 5.7 “Multi-Carrier Link Aggregation”.

The static equal load-balancing approach doesn‟t cover transparently non-equal load balancing between links with different data rates, which is the case of Backhauling Multi-Link aggregation. With the current implementation, data utilization will be divided equally between the “fast” and “slow” links. Furthermore the slower link can be overloaded and faster connection – underutilized. In order to solve this issue, it is essential to prepare the unequal load-balancing configuration.

Today, by means of Cisco IOS, the unequal load-sharing with static routes is almost impossible as there is no configuration command to assign non-default traffic share count to a static route. For example, if you configure two default routes, one pointing to a low-speed interface and another one pointing to a high-speed interface, there is no mechanism to force majority of the traffic onto the high-speed link (IOS ignores interface bandwidth when calculating load sharing ratios). However, it is possible to use a workaround by means of configuration of multiple routes for the same prefix pointing to the same interface. Since Cisco IOS allows defining multiple ip-addresses per 1 router‟s interface, the multiple next hop addresses can point on the same physical interface. Please see the figure below.



Router 1Router 2

Link1 (GigabitEthernet)

Link2 (Wimax)

Gi0/1

192.168.1.1

Gi0/1

192.168.1.100

Gi0/2

192.168.2.100

192.168.2.101 secondary

192.168.2.102 secondary

192.168.2.103 secondary

192.168.2.104 secondary

Gi0/2

192.168.2.1

192.168.2.2 secondary









Figure ‎5-20: Unequal Static Data Load-Sharing

Since the Wimax link has lower throughput ability than direct Gigabit Ethernet connection, the system will be provisioned to pass about 85 percents of data downlink traffic through the fast link and 15 percent through the slower link. In the opposite direction above of 90 percents of traffic will be forwarded through the fast link and all the rest - via the slower connection. In order to achieve this, both routers will be configured with multiple ip-addresses on the interface GigabitEthernet0/2:

Router1(config-if)#ip address 192.168.2.100 255.255.255.0

Router1(config-if)#ip address 192.168.2.101 255.255.255.0 secondary




Then will be defined with multiple static entries of default routes on the second router:












The similar configuration will be done on the second router.



5.9.1 Test procedures

The laboratory installation should be built with accordance to the figure below. The bi-directional traffic issued by packet generators will be spit between 2 links:

Wimax wireless connection

Gigabit-Ethernet wire

The aggregation routers are responsible for load-balancing performance. They should be configured in such way that in Downlink direction (traffic issued by the Packet Generator A towards the Packet Generator B) data should be split in the following proportion:

85 per cent – via Gigabit Ethernet connection

15 per cent – via Wimax Connection

In Uplink direction (traffic issued by the Packet Generator B towards the Packet Generator A) data should be split in the following proportion:

90 per cent – via Gigabit Ethernet connection

10 per cent – via Wimax Connection

In order to measure Downlink and Uplink throughput 4 sniffers will be connected along the links.

The Wimax BTS should be provisioned as described in the item 5.5.1 “Backhauling tier” (based on the VPWS principles).

Packet Generator A Packet Generator BAggregation

Router 1

HBS+ASNGW

BHSSAggregation

Router 2

Gigabit Ethernet Link

Wimax Link

Sniffer 2 Sniffer 3

Hub 2

Hub 3

Sniffer 1 Sniffer 4

Hub 1 Hub 4

Gi0/1Gi0/2

Gi0/3

Gi0/1Gi0/2

Gi0/3

Figure ‎5-21: Backhauling Multi Link Aggregation Setup

Table ‎5-12: Multi-Link Aggregation Test Procedures

Test N


1. To ensure correctness of the setup configuration

The setup will be installed and configured as described above.

The full End-To-End setup should be properly installed and provisioned. The

The Setup is prepared successfully.

Pass



Test N


Aggregation Router‟s interfaces, connected towards Wimax and wired links should be UP. Will be checked that HBS is UP and BHSS is connected.


To verify that upon physical disconnection of WiMax connection, all the DL traffic is directed through the wired connection

Will be physically disconnected the Gi0/2 interface of the Aggregation Router 1. From the Packet Generator A will run traffic with bit rate = 100 Mbps. By means of Sniffer 2 will be checked that all the traffic is sending via the GigabitEthernet wire (rate = 100Mbps).

All the DL traffic should be sent via the Gigabit Ethernet link with rate = 100Mbps

The DL traffic has been passed via the Gigabit Ethernet interface with data rate = 100 Mbps.

Pass


To verify that upon physical disconnection of Gigabit Ethernet connection, all the DL traffic is directed through the WiMax connection

Will be physically disconnected the Gi0/3 interface of the Aggregation Router 1. From the Packet Generator A will run traffic with bit rate = 30 Mbps. By means of Sniffer 3 will be checked that all the traffic is sending via the WIMax connection (rate = 30 Mbps).

All the DL traffic should be sent via the WiMax link with rate = 30 Mbps

The DL traffic has been passed via the WiMax interface with data rate = 30 Mbps.

Pass


To verify that upon physical disconnection of WiMax connection, all UL the traffic is directed through the wired connection

Will be physically disconnected the Gi0/2 interface of the Aggregation Router 2. From the Packet Generator B will run traffic with bit rate = 100 Mbps. By means of Sniffer 2 will be checked that all the traffic is sending via the GigabitEthernet wire (rate = 100Mbps).

All the UL traffic should be sent via the Gigabit Ethernet link with rate = 100Mbps

The UL traffic has been passed via the Gigabit Ethernet interface with data rate = 100 Mbps.

Pass



Test N



To verify that upon physical disconnection of Gigabit Ethernet connection, all the UL traffic is directed through the WiMax connection

Will be physically disconnected the Gi0/3 interface of the Aggregation Router 2. From the Packet Generator B will run traffic with bit rate = 4.3 Mbps. By means of Sniffer 3 will be checked that all the traffic is sending via the WIMax connection (rate = 4.3 Mbps).

All the UL traffic should be sent via the WiMax link with rate = 4.3 Mbps

The UL traffic has been passed via the WiMax interface with data rate = 4.3 Mbps.

Pass

6. To check that DL traffic is split with proportion 85:15 between wired and WiMax links

Will be verified that both links (Gigabit Ethernet and WiMax) are UP.

From Packet Generator A run traffic with data rate = 100 Mbps.

By means of Sniffers 2 and 3 verify that data is shared between Gigabit Etherner link and WiMax connection with proportion 85:15

The DL data rate of traffic passing through the Gigabit Ethernet link should be about 85 Mbps.

The data rate of traffic passing through the WiMax connection should be about 15 Mbps

The DL data has been split as expected (85:15)

Pass

7. To check that UL traffic is split with proportion 90:10 between wired and WiMax links


From Packet Generator B run traffic with data rate = 50 Mbps.

By means of Sniffers 2 and 3 verify that data is shared between Gigabit Ethernet link and WiMax connection with proportion 90:10

The UL data rate of traffic passing through the Gigabit Ethernet link should be about 46.7 Mbps.

The data rate of traffic passing through the WiMax connection should be about 4.3 Mbps

The UL data has been split as expected (90:10)

Pass

8. To measure the maximum DL and UL throughput via a Wimax connection while Gigabit Ethernet link is disconnected.

Will be physically disconnected the Gi0/3 interface of the Aggregation Routers 1 and 2. From the Packet Generator A will run traffic with bit rate = 290 Mbps and from the Packet Generator B will be run traffic with data

The maximum DL throughput via WiMax connection should be about 30 Mbps.

The Maximum UL traffic throughput via WiMax connection is about 4.3 Mbps

The measured throughput is as expected.

Pass



Test N


rate = 55 Mbps By means of Sniffers 1 and 4 will be verified that the maximum DL throughput through the Wimax link is about 30 Mbps and UL – 4.3 Mbps.

9. To ensure that the selected Data Aggregation approach implies an increase of total DL throughput.


From the Packet Generator A will be run traffic with data rate = 290 Mbps. With the Sniffer 4 will be checked that the received data rate is about 290 Mbps.

By use of the Link Aggregation approach, the total DL throughput should be much higher than in the test 8 (without aggregation).

As expected. Pass

10. To ensure that the selected Data Aggregation approach implies an increase of total UL throughput.


From the Packet Generator B will be run traffic with data rate = 55 Mbps. With the Sniffer 1 will be checked that the received data rate is about 55 Mbps.

By use of the Link Aggregation approach, the total UL throughput should be much higher than in the test 8 (without aggregation).

As expected. Pass

5.10 Reuse 1 Fractional Frequency Reuse

To maximize coverage and frequency reuse while minimizing interference, terrestrial wireless systems cover the service area with multiple cells, which are further subdivided into multiple sectors. Since some subscribers may be located at the boundaries between cells or sectors and potentially receive signals from multiple sources – thus creating interference – each sector is typically assigned a different frequency channel. Then, in accordance with an overall radio plan for the area, each channel is reused with a spatial separation in order to maximize the use of the limited spectrum while minimizing self-interference from the same channel being reused elsewhere in the network. This is commonly referred to as co-channel interference (CCI).

The „reuse factor‟, a measure of how aggressively a given frequency is reused, is expressed as a fraction of the sectors or cells operating with the same frequency channel. Typical reuse factors for traditional cellular systems is 3 – resulting in the need for 3 different frequency channels to implement a specific multi-cellular radio plan.



Figure ‎5-22: Frequency Reuse Patterns: (a) 3 frequencies; (c) 1 frequency (OFDMA)

An alternative approach, used in OFDMA, is to use all available frequency channels within each sector and to use robust modulation schemes, such as OFDMA, to deal with the high levels of interference from adjacent sectors or cells. This is referred to as having a reuse factor of 1 – sometimes called „reuse-1‟ or „universal frequency reuse‟ – and is very popular with today‟s carriers since it eliminates the need for detailed network radio planning. To support universal frequency reuse, these modulation schemes handle interference through the use of strong error correction codes such as convolution turbo codes (CTC) and by using subcarriers in the case of OFDMA. The mobile WiMAX standard also provides the ability to orthogonally split resources within a cell while randomizing subcarrier allocations between cells. The orthogonal split within the cell assures that there is little or no interference between adjacent sectors, while the randomization of subcarrier allocations between cells assures that there is little overlap between subcarriers used for specific subscribers in adjacent cells. This mitigates the potential for cell-to-cell interference and enables the air link to operate at higher modulation efficiency, resulting in higher data throughput.

Reuse-1 is better than reuse-3 in almost all aspects considered (except for MAP performance), however it suffer large difference between performance of weak and strong MSS. When the weak MSS dominated deployment performance as with Equal Data performance metric (e.g. Voice), the Reuse-1 deployment suffers. It is possible to provide better CINR to cell edge MSS, while not sacrificing BW. This is exactly what is achieved by Fractionally Frequency Reuse (FFR).

There are 3 types of FFR implementation:

Type 1 – FFR is implemented by defining two zones:

a) First data zone using reuse 3 for maps broadcasts and users data;

b) Second data zone for reuse 1 user data.

Type 2 – FFR is implemented by the transmission of two boosted major groups and 4 de-boosted major groups (transmitted using of relative attenuation of ~10dB). The boosted major groups are used for the transmission of the cell edge users (the first zone users of the type 1 method), while the de-boosted major groups are used by the inner ring users (the second zone users of the type 1 method). This method allows for better spectral efficiency than the type 1 as it uses the entire spectrum at all time.

Type 3 – In this FFR method the major-groups are divided to three groups. First two groups include two boosted major groups each, while the third group includes two de-boosted major groups. For this method the selection of the de-boosted group of each sector is done in a way that ensures that each cell edge user sees at least one group with low level of interference. The control algorithm target in this case is to assign the user to the major groups with least interference. From 3 types of FFR this method provides the highest spectral efficiency.




Table ‎5-13: FFR Test Procedures

Test N

Test Purpose


1 To perform the successful INE of a single CPE within the Radio Sector with enabled FFR mode

Perform the INE based on the following combination:

The FFR mode is enabled

1 CPE to connect


2 CQICH (R1, R3) should be opened.

The INE is succeeded.

Pass

2 To perform the successful INE of a 3 CPEs within the Radio Sector with enabled FFR mode



3 CPE to connect


2 CQICH (R1, R3) should be opened.

The INE is succeeded.

Pass

3 Validate the match between theoretical & measured DL throughput in

the Radio Sector with enabled FFR mode and 1 connected CPE

Validate the match between theoretical & measured DL throughput in the following conditions:


1 connected CPE



Pass

4 Validate the match between theoretical & measured UL throughput in


Validate the match between theoretical & measured UL throughput in the following conditions:


1 connected CPE



Pass

5 Validate the match between theoretical & measured

Validate the match between theoretical & measured DL throughput in the following conditions:



Pass



Test N

Test Purpose


DL throughput in

the Radio Sector with enabled FFR mode and 3 connected CPEs


3 connected CPEs

6 Validate the match between theoretical & measured UL throughput in


Validate the match between theoretical & measured UL throughput in the following conditions:


3 connected CPE



Pass

7 Validate the match between theoretical & measured total bidirectional throughput (UL+DL) in


Validate the match between theoretical & measured UL+DL throughput in the following conditions:


1 connected CPE

The measured UL+DL throughput should match the theoretical one.

The measured UL+DL throughput matches the theoretical one.

Pass

8 Validate the match between theoretical & measured total bidirectional throughput (UL+DL) in


Validate the match between theoretical & measured UL+DL throughput in the following conditions:


3 connected CPE

The measured UL+DL throughput should match the theoretical one.

The measured UL+DL throughput matches the theoretical one.

Pass

9 To verify the maximum frame utilization in

Get 5-7 dB DL CINR for each CPE. In order to achieve this, use attenuators or

The frame should be highly utilized. Minimum free slots should be

Minimum free slots have been observed. 5 CPEs function in

Pass



Test N

Test Purpose


the conditions of low level of R1 CINR (less than 8 dB).

10 CPEs should be connected.

place CPE in appropriate outdoor conditions. Run DL traffic to each CPE. Verify the CPE‟s equal distribution levels between R1 & R3 zones.

observed. R1, 5 CPEs - in R3.

10 To verify the maximum frame utilization in the conditions of high level of R1 CINR (more 8 dB).

10 CPEs should be connected.

Get 20 dB DL CINR for each CPE. In order to achieve this, use attenuators in the lab conditions or place CPE in appropriate outdoor conditions. Run DL traffic to each CPE.

The frame should be highly utilized. Minimum free slots should be observed.

Minimum free slots have been observed.

Pass

5.11 Neighbour Data Distribution

The neighbor data distribution (NDD) feature allows automatic distribution of relevant BS configuration (i.e. UCD/DCD) to its neighbors BSs in order to allow MS handover between the BSs. The feature is based on direct communication between BSs (R8 reference point). Each BS obtains up-to-date radio configuration information, including UCD/DCD settings, from all its Neighbor BSs using standard R8 Radio_Config_Update messages. Each BS can then compare the NBS UCD/DCD settings with its own UCD/DCD settings and derive a list of “delta UCD/DCD”, i.e. the NBS UCD/DCD fields that are not identical to those in the BS. The BS will then transmit the list of delta UCD/DCD for each NBS in the NBR-ADV message.

The NDD feature comprises the following functions:

UCD/DCD count update

Radio configuration exchange

Neighbor advertisement messages construction

UCD/DCD count update is done each time the BS UCD/DCD contents change.

The radio configuration is exchanged between BSs by means of two mechanisms:

Push: when radio configuration has been changed (in particular after BS initialization) the BS sends an unsolicited Radio_Config_Update_Rpt messages to all its NBSs containing its up-to-date radio configuration.

Pull: Periodically, the BS sends all its Neighbor BSs a Radio_Config_Update_Req message asking the NBS to send a Radio_Config_Update_Rpt message including its radio configuration.

Neighbor advertisement messages construction mechanism allows to the BS to go over all the fields in the NBS UCD/DCD. If a field is not present in the BS UCD/DCD or if the field is present but the value is not the same, the BS adds this field to the list of delta UCD/DCD. Thereby the BS constructs the NBR-ADV message including the neighbor BS-ID, preamble index, and delta UCD/DCD settings.



Figure ‎5-23: NDD messages


The laboratory‟s setup should be installed as presented at the figure above.

The NBS1 and NBS2 should be mutually defined as neighbors of the BS1.

At least 1 MS should be connected to the BS1.

Table ‎5-14: NDD Test Procedures

Test N Test Purpose Test Description Expected Results Actual Results Status

1. To verify that upon BS reset, it sends Radio_Config_Update_Req message to all its neighbours.

Perform reset to the BS1 and verify that as soon as the BS1 is restarted – it generates the Radio_Config_Update_Req towards NBS1 and NBS2.

The Radio_Config_Update_Req message should be generated by the BS1 towards NBS1 and NBS2.

The Radio_Config_Update_Req has been generated towards both neighbours.

Pass

2. To verify that as soon as NBS receives a Radio_Config_Up

Will be verified that as soon as NBS1 and NBS2 received Radio_Config_Updat

NBS1 and NBS2 should send a Radio_Config_Rpt towards BS1.

NBS1 and NBS2 send a Radio_Config_Rpt towards BS1 as

Pass




date_Req message, it sends a Radio_Config_Rpt message.

e_Req, they respond by the Radio_Config_Rpt including DCD, UCD parameters.

expected.

3. To verify that a BS sends towards a connected MS a NBR-ADV message comprising correct DCD, UCD parameters.

Will be ensured that BS1 has received Radio_Config_Rpt messages from the NBS1 and NBS2.

Then will be checked that the NBR-ADV message, sending by the BS1 towards MS1, comprises a correct neighbour list and correct values of DCD\UCD parameters, as they have been received from NBS1 and NBS2.

The values of DCD\UCD parameters sending within the NBR-ADV message should be the same as they have been received from the NBS 1 and NBS2 and the neighbour list should be correct.

The values of DCD\UCD parameters are correct, the neighbour list is valid.

Pass

4. To check the Radio_Config_Update_Req re-transmission mechanism.

To disable NDD in the NBS1.

Ensure that the NBS1 is in the Neighbour list of the BS1.

Make Reset to the BS1.

Verify that as soon as the BS is up – it sends a Radio_Config_Update_Req to the NBS1.

NBS shouldn‟t response since NDD is disabled.

BS1 should re-transmit the Radio_Config_Update_Req message 1 more time if no response is received during 50 ms.

The BS1 should re-transmit the Radio_Config_Update_Req message 1 time.

The BS1 re-transmitted the Radio_Config_Update_Req message 1 time.

Pass

5. To verify that the NBR-ADV is updated in case that NBS is down

The NBS2 will be shut down.

The BS1 should send a Radio_Config_Update_Req towards NBS2 a re-transmission it should decide that the NBS2 is down

The BS1 shouldn‟t include the NBS2 information within the NBR-ADV message.

The BS1 doesn‟t comprise the NBS2 information within the NBR-ADV message.

Pass




and in the next NBR-ADV won‟t comprise the NBS2 information.

6. To verify that HO can‟t be performed if NDD is disabled.

Disable the NDD feature within the BS1.

Make an attempt of enforcing MS1 to perform HO towards NBS1 and NBS2. The HO should fail.

The HO should fail. The HO failed. Pass

7. To check the Unsolicited Radio_Config_Rpt message.

Verify that the NBS1 and the NBS2 are compromised into the Neighbour List of the BS1.

Make a reset to the BS1.

Check that as soon as the BS1 is up – it sends the Unsolicited Radio_Config_Rpt message towards the NBS1 and the NBS2.

The Unsolicited Radio_Config_Rpt should be sent by BS1 to the NBS1 and the NBS2.

Unsolicited Radio_Config_Rpt has been sent as expected.

Pass

8. To validate that no NBR-ADV has been sent in case there are no neighbours in the list.

Make sure the Neighbour list of the BS1 is empty.

Validate that no NBR-ADV has been sent to MSs in such case.

The BS1 should not sent the NBR-ADV message.

No NBR-ADV message has been sent.

Pass

9. Validate the structure of the Radio_Config_Rpt message.

Impose the BS1 to send the Radio_Config_Rpt message (e.g. – make a BS1 reset).

Validate the Radio_Config_Rpt structure. It should comprise the following fields:

1. NBS BS-ID 2. NBS preamble index 3. NBS UCD and DCD count 4. NBS UCD and DCD settings.

The Radio_Config_Rpt should comprise the following fields:

1. NBS BS-ID 2. NBS preamble index 3. NBS UCD and DCD count 4. NBS UCD and DCD settings.

The structure of the Radio_Config_Rpt is correct.

Pass

10. Validate the sending with the Radio_Config_Rpt message DCD settings.

Make sure that the BS1 comprises the NBS1 in its Neighbour List.

Configure the NBS1‟s

The Unsolicited Radio_Config_Rpt sending by the NBS1 to the BS1 should comprise the correct

The Unsolicited Radio_Config_Rpt sending by the NBS1 to the BS1 comprises the correct values of

Pass




parameters:

TX Power = 34,

BS Frequency = 2520.

Make reset to the NBS1.

Make sure that the Unsolicited Radio_Config_Rpt sending by the NBS1 to the BS1 comprises the correct values of the DCD settings Frequency (2520) and TX Power (34)

values of the DCD settings Frequency (2520) and TX Power (34).

the DCD settings Frequency (2520) and TX Power (34).



5.12 Cross-Product/ Cross-Feature Integration Status Report

The most of Integration test procedures have been conducted using the Integration Setup, though some tests can‟t be carried out within the indoor installation framework since the mandatory requirement for them is existence of Live Demo outdoor environment. The remaining tests will be conducted as soon as the Live Demo Setup is installed and provisioned. The current status of the BuNGee Cross-Product and Cross-Feature Integration tests is represented at the table below.

Table ‎5-15: Integration Status Report

N Test Area Number of Tests

Passed Failed In progress

1. Multi-beam antenna integration with Hub BS

10 3 0 7

2. BuNGee antennas in Relay Station (BHSS and ABS)

20 7 0 13

3. MIMO B Integration 10 10 0 0

4. Multi-beam assisted MIMO

10 0 0 10

5. In-band backhauling network architecture based on L3 tunnelling

20 20 0 0

6. Multi-carrier support (PHY)

10 7 0 3

7. Multi-carrier link aggregation (networking)

10 10 0 0

8. Inter-carrier load balancing

10 10 0 0

9. Backhauling Multi-Link Aggregation

10 10 0 0

10. Reuse 1 Fractional Frequency Reuse

10 10 0 0

11. Neighbour Data Distribution

10 10 0 0

Total (%) 130 (100 %) 97 (75 %) 0 33 (25 %)



6. Live Demo preparation

6.1 Live Demo setup

This section presents the Live Demo setup topology planning, network engineering and configuration description. The Outdoor Live Demo deployment configuration is similar to the Indoor Lab Integration setup and will be based on the VLAN-CS service for the Backhauling Tier and IP-CS - for the Access Tier.

The Backhauling BS will transmit within the Radio Band = 3.5 GHz, while Access Tier will use the Radio Band = 2.5 MHz.

In particular, for demonstration of Data Load Balancing and Redundancy capabilities, the Siklu‟s 60 GHz mmWave link will be installed in parallel with WiMAX backhauling system. Furthermore the Load Balancing and Redundancy abilities will be also achieved by installing 2 parallel WiMAX Links passing traffic towards the same destinations. Both of these configurations will be temporary and won‟t take part in the rest of the tests.

Generally the End-To-End Live Demo topology is presented at the figure below.



AAA

Router

172.30.16.2

ASNGW

172.30.16.1

Bearer VID=11

Bearer IP = 192.168.1.100

Bearer DG = 192.168.1.254

AAA server. = 172.30.16.2

Trunk port

HBS 1.1.1

BHSS 1.1.1

Bearer VID=11

Bearer IP = 192.168.1.1

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100VPWS (VID=21)

ABS 1.1.1

Bearer VID=21

Bearer IP = 192.168.200.1

Bearer DG = 192.168.200.254

Authent. = 192.168.1.100VLAN 11 IP = 192.168.1.254

VLAN 21 IP = 192.168.200.254

VLAN 23 IP = 192.168.201.254

SS 1.1.1

IP=10.0.0.X

HBS 1.1.2

BHSS 1.1.2

Bearer VID=11

Bearer IP = 192.168.1.2

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=23)

ABS 1.1.2

Bearer VID=23

Bearer IP = 192.168.201.1

Bearer DG = 192.168.201.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 1.1.2

Switch

HBS 1.2.2

BHSS 1.2.2

Bearer VID=11

Bearer IP = 192.168.1.8

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=27)

ABS 1.2.2

Bearer VID=27

Bearer IP = 192.168.203.1

Bearer DG = 192.168.203.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 1.2.2

VLAN 35 IP = 192.168.207.254

SI VID = 101

172.31.16.1VLAN 101 IP = 10.0.0.101

SG Own IP=10.0.0.100

SI Next Hop = 10.0.0.101

EMS Server

172.31.16.3

HBS 1.2.1

BHSS 1.2.1

Bearer VID=11

Bearer IP = 192.168.1.2

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=25)

ABS 1.2.1

Bearer VID=25

Bearer IP = 192.168.202.1

Bearer DG = 192.168.202.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 1.2.1

HBS 1.3.1

BHSS 1.3.1

Bearer VID=11

Bearer IP = 192.168.1.1

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=29)

ABS 1.3.1

Bearer VID=29

Bearer IP = 192.168.204.1

Bearer DG = 192.168.204.254

Authent. = 192.168.1.100

SS 1.3.1

IP=10.0.0.X

HBS 1.3.2

BHSS 1.3.2

Bearer VID=11

Bearer IP = 192.168.1.2

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=31)

ABS 1.1.2

Bearer VID=31

Bearer IP = 192.168.205.1

Bearer DG = 192.168.205.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 1.3.2

HBS 2.1.2

BHSS 2.1.2

Bearer VID=11

Bearer IP = 192.168.1.8

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=35)

ABS 2.1.2

Bearer VID=35

Bearer IP = 192.168.207.1

Bearer DG = 192.168.207.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 2.1.2

HBS 2.1.1

BHSS 2.1.1

Bearer VID=11

Bearer IP = 192.168.1.2

Bearer DG = 192.168.1.254

Authent. = 192.168.1.100

VPWS (VID=33)

ABS 2.1.1

Bearer VID=33

Bearer IP = 192.168.206.1

Bearer DG = 192.168.206.254

Authent. = 192.168.1.100

IP=10.0.0.X

SS 2.1.1

Core Server172.31.16.2

Switch

Ext Mgmt VID=21

Ext Mgmt IP = 192.168.200.2

Ext Mgmt VID=23

Ext Mgmt IP = 192.168.201.2

Ext Mgmt VID=25

Ext Mgmt IP = 192.168.202.2

Ext Mgmt VID=27

Ext Mgmt IP = 192.168.203.2

Ext Mgmt VID=29

Ext Mgmt IP = 192.168.204.2

Ext Mgmt VID=31

Ext Mgmt IP = 192.168.205.2

Ext Mgmt VID=33

Ext Mgmt IP = 192.168.206.2

VLAN 25 IP = 192.168.202.254

VLAN 27 IP = 192.168.203.254

VLAN 29 IP = 192.168.204.254

VLAN 31 IP = 192.168.205.254

VLAN 33 IP = 192.168.206.254

Ext Mgmt VID=35

Ext Mgmt IP = 192.168.207.2

Backhauling

Site 2

Trunk port

Trunk

port

Trunk port

Backhauling

Site 1

VLAN-CS IP-CS

mWave BS mWave BS

mWave Link

Router

Figure ‎6-1: The End–To-End Live Demo topology



6.1.1 Central Site and Access Sites locations

The Backhauling tier consists of 2 Central Hub BS Sites located on the Roof Top of Alvarion building. The first Central Site mounted on the Roof-top A, maintains several multi-carrier sectors by means of 6 Hub Base Stations. The dual-polar multi-beam antenna is used to communicate with Hub Subscriber Stations. The narrow beams are intended to create a spatial reuse for system capacity increase.

The second Central Site is mounted on the Roof-top C and contains 1 multi-carrier sector including 2 Hub Base Stations and 1 single-beam antenna.

In total the Central BTS maintaining multi-carrier sectors, provides backhauling services for 8 ABSs in 4 ABS sites. Also the backhauling infrastructure includes the following elements:

ASNGW; The ASNGW will provide services for both – Backhauling tier and Access tier.

AAA Server; The authentication, authorization and accounting of BHSS and SS will be performed by means of the AAA server.

EMS Server; The EMS server will be used for the HBS, ABS, ASNGW provisioning and monitoring.

Core Server; The Core server will be used for the traffic generation (video streaming) purposes.

Aggregation Router; The Aggregation router will be used for the Data Load-Balancing and Redundancy performing.

VLAN Switches; The data will be tagged with the pre-defined Vlan IDs by means of Vlan Switches. The Backhauling BTS is supposed to provide a continuous coverage using the Frequency Band = 3.5 GHz within the wide geographical area. The planning coverage of all the radio beams is represented on the figure below. The figure presents just one example of ABSs physical locations, not necessary implemented in the live outdoor scenario. The final location of ABS stations will be defined during the Live Demo preparation stage when Radio Network Planning is performed.

Central Site 1

Central Site 2

ABS1 ABS2

ABS3 ABS4

ABS5 ABS6

ABS7 ABS8

Figure ‎6-2: The Site Location



6.1.2 Network IP and VLAN Engineering

The networking configuration of both Backhauling and Access tiers in the Live Demo setup is presented in the table below:

Table ‎6-1: The Live Demo Networking Configuration

N Device name

Configuration Object

Configuration Parameter Value


VLAN ID 101


Next Hop IP-Address 10.0.0.101


Own IP-Address 10.0.0.100


DHCP Pool (10.0.0.1..10.0.0.24)\24

5. ASNGW Bearer Interface VLAN ID 11

6. ASNGW Bearer Interface Default Gateway 192.168.1.254

7. ASNGW AAA Client AAA Server IP-Address 172.30.16.2


VLAN ID 21


VLAN ID 23


VLAN ID 25


VLAN ID 27


VLAN ID 29


VLAN ID 31


VLAN ID 33


VLAN ID 35













26. Router Interface Gi0/1 (towards AAA)

IP-Address 172.30.16.1

27. Router Interface Gi0/2 (towards ASNGW)


28. Router Interface Gi0/3 (towards Switch)


29. Router Interface Gi0/4 IP-Address 172.31.16.1

30. Core Server NIC IP-Address 172.31.16.2







IP-Address 192.168.1.254


IP-Address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100






IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100




IP-Address 192.168.1.254


IP-address 192.168.1.100





IP-Address 192.168.1.100

70. ABS 1.1.1 External Management Interface

VLAN ID 21


IP-Address 192.168.200.1





IP-Address 192.168.1.100


VLAN ID 23


IP-Address 192.168.201.1







VLAN ID 25


IP-Address 192.168.202.1


IP-Address 192.168.1.100





IP-Address 192.168.1.100


VLAN ID 27


IP-Address 192.168.203.1





IP-Address 192.168.1.100


VLAN ID 29


IP-Address 192.168.204.1





IP-Address 192.168.1.100


VLAN ID 31


IP-Address 192.168.205.1







IP-Address 192.168.1.100


VLAN ID 33


IP-Address 192.168.206.1





IP-Address 192.168.1.100


VLAN ID 35


IP-Address 192.168.206.1

114. EMS Server NIC IP-Address IP-Address 172.31.16.3

115. Core Server NIC IP-Address IP-Address 172.31.16.2

6.1.3 Live Demo Setup Acceptance Test Plan (ATP)

As soon as the Live Demo setup is established, the basic acceptance tests validating End-To-End functionality should be performed. The related test procedures will ensure the correctness of the topology engineering, installation and provisioning. The ATP execution is essential in order to adjust the setup for the geographical characteristics of the Live Demo area. Eventually the proceeding of the tests will contribute to the ABS locations selection for the best system performance achievement.

This section must be filled during the Live Demo setup ATP testing by outdoor team (Phase 3).

Table ‎6-2: The Live Demo ATP


1. The Initial Network Entry of BHSSs.

For each Radio Beam will be connected at least 1 BHSS.

The INE of BHSSs should be successful for each HBS sector

2. The Initial Network Entry of SSs.

At least 1 SS will be connected to each ABS.

The INE of SSs should be successful throughout all the ABSs.

3. The Network Exit of BHSSs.

BHSSs will be disconnected from the network (by means of the appropriate CLI\EMS command) and verified that CPEs

BHSSs should perform the Network Exit in a proper way.




perform successful Network Exit.

4. The Network Exit of SSs.

SSs will be disconnected from the network (by means of the appropriate CLI\EMS command) and verified that CPEs perform successful Network Exit.

SSs should perform the Network Exit in a proper way.

5. Traffic between SSs and a Core Server.

For each sector the traffic will be generated between SSs and the Core Server.

The traffic should successfully pass; no packet loss and long delays should be discovered.

6. Traffic between SSs connected to the same Backhauling site.

The traffic between SSs connected to different sectors belonging to the same Backhauling site will be generated


7. Traffic between SSs connected to several Backhauling sites.

The traffic between SSs connected to the several Backhauling sites will be generated


8. To check that every HBS is manageable via the EMS server.

Via the EMS system access each of HBS. Verify that all of them are configurable/

All HBSs should be reachable and configurable from the EMS server.

9. To check that every ABS is manageable via the EMS server.

Via the EMS system access each of ABSs. Verify that all of them are configurable.

All ABSs should be reachable and configurable from the EMS server.

10. Intra-Site Handover.

Perform the SS Handover between ABSs connected to the same Backhauling site.

The HO should be successful, handover latency should be low (doesn‟t exceed 100 ms).

11. Inter-Site Handover.

Perform the SS Handover between ABSs connected to several Backhauling sites.

The HO should be successful, handover latency should be low (doesn‟t exceed 100 ms).

12. Drive Test in the cell core (13 < SINR > 20 and 20 < SINR < 25).

The Test Drive will be performed in the cell core. Will be verified that the throughput in every particular location matches the pre-calculated values. with respect to SNR and MCS.

The throughput should match the pre-calculated values.




Will be verified that MCS is fully adaptive to related values of radio conditions.

13. Drive Test in the cell edge (-85 < RSSI < -75).

The Test Drive will be performed in the cell edge point. Will be verified that the throughput in this location matches the pre-calculated values with respect to SNR and MCS. Will be verified that MCS is fully adaptive to related values of radio conditions.

The throughput should match the pre-calculated values.

14. Performance Test Will be tested simultaneously on 3 under the roof CPEs (SSs) the following services:

1. VoIP

2. Real time video stream

3. FTP traffic

All types of traffic should pass successfully.

15. Maximum DL traffic per carrier.

The DL traffic with bit rate 30 Mbps will be generated from the Core Server towards a SS.

The measured CPE DL traffic rate should be about 30 Mbps.

16. Maximum UL traffic per carrier.

The UL traffic with bit rate 4.3 Mbps will be generated from the SS towards the Core Server.

The measured UL traffic rate received by the Core Server should be about 4.3 Mbps.



6.2 Demonstration Scenarios

This section describes the Test Procedures which are supposed to be executed during the Live Demo Presentation phase. In process of the tests execution, the necessary measurements, calculations, performance assessments and functionality estimations will be collected and included into the final Demonstration Scenarios Reports.

6.2.1 Total System Throughput

Table ‎6-3: The Total System Throughput Demonstration

The Scenario Purpose The Scenario Description Report

Demonstrate the total bidirectional throughput (DL + UL) of about 270 Mbps within the geographical area with square of about 0.25 Km

2

8 SSs will be connected to the system as presented on the figure below.

The DL traffic with the bit rate = 30 Mbps will be generated from the Core Server towards each of connected CPE (the total DL throughput should be about 240 Mbps)

The UL traffic with bit rate = 4.3 Mbps will be generated from each SS towards the Core Server (the total UL throughput should be about 34.4 Mbps)

Verify that the total bidirectional throughput within the area of 0.25 Km2 is about 270 Mbps.



Core Server

SS 1.1.1

SS 1.1.2

Carrier 1

Carrier 2

Sector 1

SS 1.1.3

SS 1.1.4

Carrier 1

Carrier 2

Sector 2

SS 1.1.5

SS 1.1.6

Carrier 1

Carrier 2

Sector 3

SS 2.1.1

SS 2.1.2

Carrier 1

Carrier 2 Sector 4

HUB BTS

240 Mbps

4.3

Mbps

4.3

Mbps

4.3 M

bps

4.3 M

bps

4.3 Mbps

4.3 Mbps

4.3 Mbps

4.3 Mbps

Figure ‎6-3: SSs Allocation Throughout The Sectors



6.2.2 Performance of Multi-Beam Assisted MIMO

Table ‎6-4: Multi-Beam Assisted MIMO Demonstration


Demonstrate benefits of using Multi-Beam Assisted MIMO B.

No MIMO will be enabled within the Radio Sector.

A single SS will be connected to the Radio Sector.

The maximum SS DL and UL throughput will be measured.

The MIMO B will be enabled within the Radio Sector.

Will be ensured that a single SS is connected through this sector and operates in the MIMO B mode.

The maximum SS DL and UL throughput will be measured and compared with the results received without MIMO.

Perform the INE for 1 SS with conditions of the Multi-Beam Assisted MIMO B.

The maximum SS DL and UL throughput will be measured and compared with the results received without MIMO and with single-beam MIMO B.

6.2.3 Backhauling Tier Broadband Coverage

Table ‎6-5: Backhauling Tier Broadband Coverage Demonstration


Demonstrate the Backhauling Tier broadband coverage.

The BHSSs will be disposed in few points within the Radio Sector core.

In each BHSS disposition the SINR and maximum UL\DL throughput will be measured. Will be verified that the factual throughput matches the pre-calculated values.

The BHSSs will be disposed in few points in the Radio Sector edge.



In each BHSS disposition the SINR and maximum UL\DL throughput will be measured. Will be verified that the factual throughput matches the pre-calculated values.

Validate that the maximum throughput is achieved within the Radio Sector core points.

6.2.4 Access Tier Mobile Coverage

Table ‎6-6: Access Tier Broadband Coverage Demonstration


Demonstrate the Access Tier broadband coverage.

The SSs will be disposed in few points within the Radio Sector core.

In each SS disposition the SINR and maximum UL\DL throughput will be measured. Will be verified that the factual throughput matches the pre-calculated values.

The SSs will be disposed in few points in the Radio Sector edge.

In each SS disposition the SINR and maximum UL\DL throughput will be measured. Will be verified that the factual throughput matches the pre-calculated values.

Will be validated that the maximum throughput is achieved within the Radio Sector core points.

The SS Intra-Site Handover will be performed (while HBSs feeding Serving and Target ABSs) belong to the same Backhauling BTS.

The SS Inter-Site Handover will be performed (while HBSs feeding Serving and Target ABSs) belong to different Backhauling BTSs.



6.2.5 In-band Backhauling Network Functionality

Table ‎6-7: In-Band Backhauling Approach Demonstration


Demonstrate the In-band Backhauling Network functionality

The Backhauling Tier functionality will be presented (VPWS service).

The Access Tier functionality will be presented (General IP-CS service, IP-CS over VPWS relay).

The actual Backhauling and Access Tiers installation will be demonstrated and verified that it is done with accordance to the topology scheme represented on the figure 6.1.

6.2.6 Backhauling Multi-Link Aggregation

Table ‎6-8: Backhauling Multi-Link Aggregation


Demonstrate the Multi-Link Aggregation benefits.

As presented on the figure below, 2 parallel connection towards the same ABS will be established:

WiMAX link;

mmWave link.

The Aggregation routers will be provisioned in such way the 85 % of DL traffic will be passed through the mmWave link and 15 – via the WiMAX link.

The Aggregation routers will be provisioned in such way the 90 % of UL traffic will be passed through the mmWave link and 10 % – via the WiMAX link.

The DL and UL traffic will be generated and verified that the traffic is forwarded towards the relevant destination according to the pre-defined multi-link conditions.



Figure ‎6-4: Backhauling Multi Link Aggregation Demonstration

6.2.7 Lab-based In-band backhauling treatment of self-deafening issue

Table ‎6-9: Lab based In-band backhauling self-deafening issue resolution


Demonstrate the impact of the self-deafening issue in the “relay”/ in-band backhauling configuration.

Construct the Lab setup as presented on the Figure ‎6-5, including 2 Base Stations – one emulating Hub BS and another one emulating Access BS element or Relay Station, peered with 2 CPEs. Connect all the radio elements over the same radio environment (use attenuators as appropriate)

Activate both BSs. Perform INE for CPE1 and CPE2

Try traffic delivery for both CPEs.

Confirm the radio links are unstable – links dropped, no or minimum traffic delivery

Demonstrate functionality of the solution for self-deafening issue by shifting air frames of Access BS in relation to Hub BS.

Construct the Lab setup as presented on the Figure ‎6-5, including 2 Base Stations – one emulating Hub BS and another one emulating Access BS element or Relay Station, peered with 2 CPEs. Connect all the radio elements over the same radio environment (use



attenuators as appropriate)

Activate in-band backhauling demo functionality - shift air frame timing of the Access BS by N symbols. Restrict DL/ UL frame utilization in both HBS and ABS – as presented on the Figure ‎6-6.


Confirm CPEs perform INE and the links is stable – no drops.

Demonstrate performance of the solution for self-deafening issue by shifting air frames of Access BS in relation to Hub BS.

Construct the Lab setup as presented on the Figure ‎6-5

Activate in-band backhauling demo functionality.


Try traffic delivery for both CPEs.

Confirm the radio links are stable – no drops, traffic performance is as expected.



CPE1 (BHSS)

CPE2 (SS)

BS1 (HBS)

BS2 (ABS)WiMAX ASN

ASN GW

AAA

RF cableWiMAX Netw IFUser Eth IF

Traffic Generators

Figure ‎6-5: In-band backhauling self-deafening issue demonstration - Setup

Frame k-1 Frame k Frame k+1

HBS Tx TTG RxRTG Tx

ABS Tx TTG RxRTG Tx TTG Rx

RTG

Frame i Frame i+1

Frame shift

Time

MAP

DL Data

MAP

DL Data

FB

UL Data

HBS

ABS

FB

UL Data

ABS TDD Frame

HBS TDD Frame

Figure ‎6-6: In-band backhauling self-deafening issue demonstration – Air frame structure



7. Conclusions

The document presents System Integration activities performed by ALV in Labs and paves the way for Live Demo preparation.

System Integration activities performed in the Lab and presented in the first part of the document, are focusing mainly on cross-product and cross-feature integration. The following prototyping components from BuNGee partners were integrated into the system:

Backhauling and Access RANs based on Hub and Access BS prototypes;

Multi-beam antenna for Hub BS and directional antennas for BHSS and Access BS;

60GHz mmWave point-to-point backhauling link.

The second part of the document describes the Live Demo preparation activities, including setup and sites planning, engineering and description of demonstration scenarios.

System Integration activities started in the 7th project quarter, the main volume is performed during Q8, but

testing of some features and KPIs, especially those requiring outdoor installations, will be continued during Q9. 75% of the Test Cases reported as successfully completed. The rest of the Test Cases require real outdoor environment and will be performed during the Live Demo outdoor setup.

As most of the features and all the cross-product functionalities are tested and found operational, the system is considered ready for the Live Demo.



8. Bibliography

[1] http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094820.shtml

[2] BuNGee Deliverable D1.2 “Baseline BuNGee Architecture”.

[3] BuNGee Deliverable D3.1 “Baseline RRM & Joint Access/Self-Backhaul Design”.

[4] BuNGee Deliverable D4.2.1 “MM Wave Backhaul Prototypes”.

[5] BuNGee Deliverable D4.2.2 “Multi-Beam Antenna Prototypes”.

[6] BuNGee Deliverable D4.2.3 “Hub and Access BST Prototypes”.

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094820.shtml



9. Release History

Please give details in the table below about successive releases:

Release number

Date Comments Dissemination of this release (task level, WP/SP level, Project Office Manager, Steering Committee, etc)

1.0.0 19.01.12 Final version Document submitted to EC

Documents

BuNGee Deliverable: D4.3 BuNGee System Integration Report · Project Number: 248267 Project acronym: BuNGee Project title: Beyond Next Generation Mobile Networks BuNGee Deliverable: