UMT_IRC_APP_040083_V01 01_EN_OEM_Node_B_Daisy_Chaining (3).pdf

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1


Node B Daisy Chaining (FRS 100791)Operational Engineering Method LR13.1 W

David Grandblaise

TIPS/NEA/ACT, APR 2013, v01.01

INTERNAL ONLY

This slide pack presents the Engg Guidelines for the introduction of Node B Daisy Chaining functionality as

supported in LR13.1 W.


3

Exec Summary for LR13.1 W 100791" feature

Scope- This feature is OPTIONAL and is subject to LICENSING. It is not activated by default.

- This feature allows using a single Ethernet backhaul interface for sites with multiple base stations 2G/3G/4G (it avoids using an external Ethernet aggregator).

Operational Requirements- 6 new counters introduced on the chaining 3G Node B to:

discriminate the traffic volumes and throughputs used by the chaining 3G Node B and chained BTSs.

calculate the bandwidth used by traffic originated in the chaining 3G Node B and chained BTSs in both ingress and egress directions

- Configuration Management and Parameters: New parameters introduced to configure the new functionalities. Node B Daisy chaining activation does NOT require any NodeB reset.

- Fault Management and Alarms: A new alarm is introduced with regards to SyncE performance in daisy chaining mode.

FRS 100791- LR13.1 W Feature name : Node B Daisy Chaining

Key Benefits- No external Ethernet aggregator required w/ multiple BTSs

Engg impacts


4

Pre-Requisites- Node B HW:

GE MDA required for daisy chaining & SyncE/PTP

eCCM-u required for analog 2.048/10/15 MHz sync source

xCCM(-u) or eCCM-u for remaining items of the feature

Dependencies- Sofware feature

FRS 113326 - Node B Synchronization Enhancements- External nodes or devices (Core Network, UE or others)

Requires external source for analogue 2.048/10/15 MHz sync option Requires external IEEE1588v2 Time Server for 1588v2 Synchronization Requires SYNCE compatible network for SYNCE External GPS receiver in case of GPS synchronization

Engg impacts-To activate the feature, the operator must first get the license, then set the flag IpRan:: isBackhaulDaisyChainingActivated = TRUE.- Traffic shaping is configured in the daisy chained BTS (egress direction) or in the transmission network (ingress direction) in order to ensure that the daisy chained traffic conforms with the transport network available SLA and does not affect the QoS of locally originated/terminated traffic.- The aggregated traffic (local and daisy chained) is dimensioned in order to ensure that it remains within the capacity of the 1GE interface.

Exec Summary for LR13.1 W 100791" feature

Node B Daisy Chaining known Limitations in LR13.1 WA. Port configuration- Daisy chaining can be activated ONLY in Native IP Iub configuration & when the backhaul interface is GE MDA.- 2 out of the 3 GE MDA ports can be used ONLY since GE MDA SFP2 and GE MDA RJ-45 CANNOT be used simultaneously(mutually exclusive)B. Synchronisation- The Node B itself does NOT modify the transparent clock correction field and CANNOT act as a transparent clock in Daisy Chaining mode Refer to Chapter 4c of PTP OEM- SyncE is only supported w/ GE MDA SFP optical and GE MDA RJ45 ports Refer to Chapter 4b of SyncE OEM- SyncE is supported w/ Node B daisy chaining feature in ingress (MBH) and egress (DC) ports Refer to Chapters 1b & 4b of SyncEOEM


5

C. Validation- Node B Daisy Chaining mode is only validated with ALU 2G/3G/4G products. Any support with 3rd party products requires someadditional IOT tests that will be required internally, and discussion between the local team and the customer.- Node B Daisy Chaining only supported configurations are: 3G->3G, 3G->3G->Smartbits, 3G->4G-IPv4, 3G->4G-IPv6, 3G->4G-IPv4-IPSECD. Features incompatibilityDaisy chaining cannot be deployed jointly with:- Dual port configuration (i.e. Split Iub) (feature 79362)- LAG (feature 112412)- IEEE803.3ah (EFM) introduced in the Node B with feature 103182 - Ethernet OAM in the Node B.E. Service- In case of 3G Node B failure or reset the daisy chained traffic will be interrupted

Publication History

v01.01/EN APR, 2013 Approved Preliminary RFOA - David Grandblaise, TIPS/NEA/ACT

LR13.1 W RFOA ready

v01.00/EN FEB, 2013 - Document creation, RFOA Draft - David Grandblaise, TIPS/NEA/ACT


Table of Content

1

2

3

5

Requirements & Dependencies

Functional Overview

Supported configurations

I& I&C Setting

Performance Monitoring

4


7

5 Performance Monitoring

Known Limitations

Documentation References

Appendix

6

7

8


1 Requirements & Dependencies

Requirements & Dependencies (1/2)

DescriptionLicensing RequiredNode B SW/HW GE MDA required for SyncE

eCCM-u required for analog 2.048/10/15 MHz sync source

xCCM(-u) or eCCM-u for remaining items of the feature

RNC SW/HW RNC independent featureFeatures FRS 113326 - Node B synchronisation Enhancements


9

Featuresdependencies

FRS 113326 - Node B synchronisation Enhancements

SW dependencies LR131.1 W (Both RNC and Node Bs) OAM09.1

HW dependencies SR77x0 and associated OAM (5620SAM)

Requirements & Dependencies (2/2)

DescriptionInterworking to ExternalNodes/Interfaces

Requires external source for analogue 2.048/10/15 MHzsynchronisation option

Requires external IEEE1588v2 Time Server for 1588v2 synchronization

Requires SyncE compatible network for SyncE synchronization

External GPS receiver in case of GPS synchronization


10


2 Functional Overview

Functional Overview (1/2)

Node B Daisy Chaining is a newly introduced feature in LR13.1 W (FRS 100791)

This Feature is optional and subject to licensing

Only applicable to Native IP 3G Node B configurations

This feature is enabled with SW upgrade, and is activated using

a class 3 parameter preventing the dropping BTS to reset

BTS A is the dropping/chaining B (head of the Daisy Chain, actsas a hub). BTS A is mandatory a 3G Node B.

Dropped/Chained BTS(s)

BTS C, D, E


BTS B (ALU products only) can be either a 3G Node B or a 4GeNodeB or a 2G BTS

Additionnaly, several BTS(s) B can be chained (namelydropped/chained BTSs)

As the BTS daisy chaining feature is only for GE MDA equippedBTS (2G, 3G, 4G) on full IP backhaul, each BTS is individually able

to synch on a synchronous Ethernet (SyncE) or IEEE1588 V2 (PTP)via the MBH

Chaining NodeB (BTS A) gets synchronization from backhaul

source (SYNCE, PTP) or external source (GPS, analogous

references) and disciplines its oscillator from this source

Switching is MAC address based (no IP routing in this feature)

Dropping NodeB

GE MDA PHY link

Dropping/Chaining NodeB

Functional Overview (2/2)

MBH port

DC port

Egress

Ingress

3G Node B (Chaining BTS)

Daisy ChainedBTSs


13

Ingress

Backhaul

The chaining BTS is MANDATORY a 3G Node B

When the Node B daisy chaining is active, each Ethernet port of the chaining Node B is

assigned to just one role:

Mobile Backhaul port (MBH): is used for the connection with the MBH (RNC, OMC, BSC, MME)

Daisy Chained port (DC): is reserved for the connection with the chained BTS(s)

Impacted Engg areas - Overview

Network topology (refer to sections 3, 4)

Synchronisation (also refer to section 4)

Backhaul bandwidth management

Traffic switching in chaining 3G Node B

Node B/eNodeB/BTS addressing

QoS


14

Security

IPv4/IPv6

Engg impacted areas - Synchronization (1/2)

The chaining 3G Node B clock sources options:

MBH based sources (PTP, SyncE) on GE MDA ports

External sources (GPS, 2.048/10/15 MHz)

The chaining 3G Node B synchronization operations are:

The chaining Node B can transmit MBH clock sources (PTP, SyncE) to the chained BTS through the GE

MDA DC port. SyncE only supported on MDA-RJ45, MDA SFP1/SFP2 optical (both MBH & MC MDAports)

Generally speaking, the presence or not of the SSM message in the egress DC port depends on the


15

Generally speaking, the presence or not of the SSM message in the egress DC port depends on the

type of source synchronizing the Node B and the eecOption

Note that SSM can be generated in egress DC port EVEN IF SyncE is not selected as a candidatesource in the synchronizationMethodList attribute Refer to Section 1b OEM SyncE for more details

If PTP method is used as synchronization method for the chained BTS(s), the chaining 3G NodeB

treats these traffic flows w/o strict priority and forward it to the chained BTS(s). No additional delay

or delay variation are expected since the switching is MAC @ based. So, PTP flows destinated to the

chained BTS are transparent for the chaining 3G Node B

In PTP operations, the chaining 3G Node B itself does NOT modify the transparent clock correctionfield and CANNOT act as a transparent clock in Daisy Chaining mode

The chaining 3G Node B CANNOT receive sync signals from chained BTS(s) via GE MDA ports.

Engg impacted areas - Synchronization (2/2)

The chained BTSs clock sources options:

MBH based sources (PTP, SyncE) on GE MDA ports

External sources (GPS, 2.048/10/15 MHz)

The chained BTSs synchronization operations are:

PTP flows destinated to the chained BTS are transparent for the chaining 3G Node B

The following IEEE1588v2 implementations are expected in the chained BTS: Unicastmode, one-step clock and PTP/UDP/IP


16

mode, one-step clock and PTP/UDP/IP

In case chaining 3G Node B facing the backhaul is lost, the chained BTS traffic isdropped. The chained BTS is notified that the MBH clock source is lost. Single point offailure.

In case the chaining 3G Node B fails (or during a SW upgrade / planed outage), thechained traffic is interrupted (with loss of service). The chained BTS is notified that theMBH clock source is lost. Single point of failure.

For FULL Engg related documentation on PTP for 3G Node B in Daisy Chaining : CLICK HERE

For FULL Engg related documentation on SyncE for 3G Node B in Daisy Chaining : CLICK HERE

Engg impacted areas - MBH BW management

The BW used by the daisy chained traffic CANNOT be managed by the chaining3G Node B.

The chaining 3G Node B takes ingress data on the EthernetPort role = daisychainport and ships it out the EthernetPort role = backhaul. The chaining 3G Node Bdoes NOT shape or police the daisychain data.

So the design relies on:

The originating node (chained BTS) to do the traffic shaping itself.


17

Each chained BTS is responsible to shape its own traffic, and the Iub must be

engineered to satisfy the traffic from both nodes. Unfortunately in this design, the Iub

cannot be shared, ie: Iub is 10M, each node is shaping at 5M, but neither node can

utilize 10M of Iub.

Overall throughput (chaining 3 G Node B + chained BTS(s) traffic) is limited to1 Gbps due the single GE MBH link. Indeed, the LAG feature CANNOT be usedjointly w/ Daisy Chaining feature to add additional link capacity (incompatibility).

Engg impacted areas - Traffic switching in chaining 3G Node B

Switching of the chained traffic is done at the MDA level of the chaining Node B.

The chaining Node B simply forwards chained traffic over the MBH.

On the chaining 3G Node B, ingress data on the EthernetPort role = backhaul ischecked as following:

If the IP packet is VLAN tagged for a VLAN which is NOT a local VLAN on the chaining3G Node B, the data is shipped out the EthernetPort role=daisychain, except for slow

protocols.


18

protocols.

Any packets containing slow protocols (synce SSM, EthernetOAM) are sent to the

chaining 3G Node B PQ3 and it deals with them.

VLAN Ids of chained BTS(s) cannot be configured by the chaining 3G Node B.

Engg impacted areas - Node B/eNodeB/BTS @ing

MAC address based. No IP routing performed by the chaining 3G Node B.


19

Engg impacted areas - QoS, Security, IPv4/IPv6

Description

QoS The QoS marking of the chained BTSs is performed by the BTS itself.

T his marking MUST NOT be modified by the Node B facing the MBH (either L2 or L3).

Security If IPSec is implemented on the chained BTS to secure the traffictowards the MBH, the Node B is able to handle this traffic

transparently between the BTS and the MBH regardless on the


20

transparently between the BTS and the MBH regardless on the implementation of IPSec for 3G traffic in the dropping Node B.

IPSec compliancy is based on what is provided via Virtual Interface

(VI).

IPv4/IPv6 The Node B handles transparently both IPv4 and IPv6 packets of the chained traffic as switching is MAC @ based


3 Supported Configurations

Network supported configurations (1/3)

A 3 G Node B chaining a 3G Node B

ST VALIDATEDST VALIDATED


22

The chained 3G Node B is unaware of the daisy chaining

3G Node B A & B are handled by the same OMC and RNC

No specific provisioning is needed for 3G Node B B, apart from the addressingscheme which has to be compatible w/ Node B As one.

1 Gbps1 Gbps


A 3 G Node B chaining a LTE eNode B

1 Gbps1 Gbps

ST VALIDATEDST VALIDATED


23

The chained LTE eNode B is unaware of the daisy chaining

The main drawback being that the overall throughput of the MBH is limited to 1Gbps, to be shared between a 3G Node B and a LTE eNode B.


A 3 G Node B chaining a 2G BTS

1 Gbps1 Gbps

NOT ST VALIDATEDNOT ST VALIDATED


24

The chained 2G BTS is unaware of the daisy chaining

No traffic limitation is expected in this case

The 2G BTS has to be configured with Abis over IP/Ethernet

ST validated configurations (1/2)

Chaining Equipment Chained Equipment

3G Node B 3G Node B

3G Node B 3G Node B -> Smartbits

3G Node B LTE eNode B (IPv4)

3G Node B LTE eNode B (IPv4)

3G Node B LTE eNode B (IPSec)


25

These configurations are only validated by ST with ALU 2G/3G/4G BTS

IOT with non ALU BTS is OUT of the scope of this feature.

Any support with 3rd party products requires some additional IOT tests thatwill be required internally, and discussion between the local team and the

customer.

ST validated configurations (2/2)

Note 1: The Node-B handles transparently both IPv4 or IPv6 packets as chainedtraffic. Daisy chaining feature is independent of the IPv6 feature and is handled

transparently as switching is MAC address based.

Note 2: The Smartbits is an IP test tool, it transmits and validate the receivedpackets of various sizes and rates. Basically it was used to daisychain

performance accuracy and transparency. As the ST Lab did not have the

environment to test 3G->2G daisy chaining, this tool provides a level of

confidence that 3G->2G daisy chaining will work when it is available.


26

confidence that 3G->2G daisy chaining will work when it is available.

Chaining 3G Node B supported configurations (1/3)

The daisy chaining feature is supported on the GE MDA ports of the xCCM(u)and eCCMu controllers on the chaining 3G Node B.

The GE MDA ports are: SFP1, SFP2 and RJ45

Only 2 out of 3 GE MDA ports can be used since GE MDA SFP2 and GE MDA RJ45CANNOT be used simultaneaously. SFP2 cage and GE MDA RJ45 ports areconnected to the same physical layer and hence only one port of these two can

be used.

SFP1 and SFP2 can have either fiber (optical) or copper (electrical) transceiver.


27

SFP1 and SFP2 can have either fiber (optical) or copper (electrical) transceiver.

SyncE can only be propagated on optical SFP and GE MDA RJ45 (electrical). Ifelectrical SFP1 or elecrical SFP2 is used, then SyncE CANNOT be used as

synchronization source.


Node B supported configurations if SyncE source is NOT used in daisy chaining

MBH / DC GE MDA SFP 1 GE MDA SFP 2 GE MDA RJ-45

GE MDA SFP 1

N/A

Y

optical & electrical

GE & FE rate

Y


GE & FE rate

GE MDA SFP 2 Y


28

GE MDA SFP 2 Y


GE & FE rate

N/A N

GE MDA RJ-45 Y


GE & FE rate

N N/A

MBH port = Mobile Backhaul portDC port = Daisy Chained port


Node B supported configurations if SyncE source IS used in daisy chaining

MBH port

DC port

SyncE egress

SyncE ingress

MBH / DC GE MDA SFP 1 GE MDA SFP 2 GE MDA RJ-45


29

MBH / DC GE MDA SFP 1

Optical

GE MDA SFP 2

Optical

GE MDA RJ-45

GE MDA SFP 1

OpticalN/A Y (GE & FE rate) Y (GE & FE rate)

GE MDA SFP 2

OpticalY (GE & FE rate) N/A N

GE MDA RJ-45 Y (GE & FE rate) N N/A

MBH port = Mobile Backhaul port

DC port = Daisy Chained port


4 I&C Setting

BTSEquipment IpRAN object - LR13.1 W RAN Model

BTSequipement

IpRan

EthernetPort administrativeState (class 3)

portRole (class 2)

Configuration Data


31

IpRan

IsBackhauldaisyChainingActivated (class 3)

LR13.1 W RAN Model parameters (1/3)

1) BTSEquipment\EthernetPort RndId parameter identifies the GE MDA

ports. Range is 0: SameAsCommissioning, 1: SFP1, 2: SFP2, 3:RJ45_MDA

All the GE MDA SFP1/SFP2/RJ45 Ethernet driver instances are created

at startup

2) BTSEquipment\EthernetPort\adminstrativeState parameter (class 3)

manages the DC port:


32

manages the DC port:

When the DC port is locked, traffic can no longer flow over that port

If it is unlocked, then traffic can flow to/from the chained BTS(s)

As the GE MDA SFP2 and RJ45 ports are mutually exclusive, when the

administrative status of one of the two ports is set to unlocked, the

other one cannot be modified and the operational status has to be set

to desabled.


3) BTSEquipment\EthernetPort\portRole parameter (class 2) selects and

identifies the GE MDA port used for Iub (backhaul side), and the GE

MDA port used on the daisy chaining side:

Identify and select the port acting as the Iub backhaul port (MBH port)

portRole = Backhaul (Only one port can be set as Backhaul)

Identify and select the port acting as the daisy chained port (DC port)


33

portRole = DaisyChaining (Only one port can be set as DaisyChaining)

Note:

Make sure the MBH and DC selected ports are SyncE capable and compatible if daisy chaining

is used jointly with SyncE (Section 3).

At least one EthernetPort shall be configured with backhaul value

By default, the Ethernet port has backhaul role.

portRole can set as a DC port provided IsBackhauldaisyChainingActivate flag = TRUE

Once a port is set as DC, no EthernetBandwidthPool can refer to this Ethernet port.

EthernetBandwidthPool only applies to Ethernet backhaul port.


4) BTSEquipment\IpRan\IsBackhauldaisyChainingActivate parameter(class 3) indicates if backhaul daisy chaining is activated on the

NodeB. Range of value is: false or true

As this is a class 3 parameter, the operator is able to activate or de-

activate the Node B daisy chaining feature without restarting the Node B.

Whe IsBackhauldaisyChainingActivate flag = TRUE (daisy chainingactivated), the port role CANNOT be modified from DaisyChaining to


34

activated), the port role CANNOT be modified from DaisyChaining to

Backhaul

Overall LR13.1 W activation approach

PTP activation in a Node B Daisy Chaining configuation is fullydocumented in Chapter 4 of the PTP OEM

SyncE activation in a Node B Daisy Chaining configuation is fullydocumented in Chapters 1b and 4b of the SyncE OEM


35

Startup/Upgrade (1/2)

Activation

The activation of this feature does NOT require Node B reset

When Node B daisy chaining has to be activated on a running Node B, the

following sequence must be respected to prevent aby traffic disruption on the

daisy chaining Node B (steps 1 & 2 are pre-provisioned at startup or upgrade):

Step # DescriptionStep 1 A first Ethernet port is set with port role = backhaul


36

Step 1 A first Ethernet port is set with port role = backhaulStep 2 A second Ethernet port is set with the port role =

daisy chainStep 3 Set IsBackhauldaisyChainingActivate flag = TRUEStep 4 Admin Unlock the DC port

Startup/Upgrade (2/2)

De-Activation

When Node B daisy chaining has to be de-activated on a running Node B, the

following sequence must be followed:

Step # DescriptionStep 1 Admin Lock the DC portStep 2 Set IsBackhauldaisyChainingActivate flag = FALSE


37

Step 2 Set IsBackhauldaisyChainingActivate flag = FALSE

WMS LR13.1 W RAN Model

The Wireless Management System (WMS) for Iub is covered in:

9353 WMS - Activation of an Operator Configurable Split of IP Traffic over Hybrid Iub

9353 WMS - Activation of an Operator Configurable Split of IP Traffic over Native IP Iub

9353 WMS - Activation of Hybrid Iub

9353 WMS - Activation of Native IP Iub


38


5 Performance monitoring

LR13.1 W alarm

The newly UNEXPECTED SSM ON DAISY CHAINING PORT alarm is introduced :

Assuming:

- SyncE is listed in the synchronizationMethodList parameter

- An MDA port is configured as daisy chaining

- SSM check is configured (eecOption is set to value 2 or 3 refer to SyncE

OEM)

This alarm is raised if:


40

This alarm is raised if:

- The daisy chaining Node B is receiving from the daisy chained Node B SSM

with non DNU value on its daisy chaining port

- The daisy chaining Node B is not assigned with the appropriate port

LR13.1 W counters (1/7)

New counters are introduced in LR13.1 W related to the introduction of the Node daisychaining feature.

These new counters allow measuring the daisy chaining traffic and backhaul traffic, andthe relative load both use on the MBH port, as follows:

Total number of frames handled through the Ethernet port:

- One counter in ingress: ifOutFramesEthPort

- One counter in egress: ifInFramesEthPort


41

Kilo Bytes handled through the Ethernet port:

- One counter in ingress: ifOutKbytesEthPort

- One counter in egress: ifInKbytesEthPort

Total number of discarded on the Ethernet port:

- One counter in ingress: ifOutDiscardsEthPort

- One counter in egress: ifInDiscardsEthPort

Labels DescriptionCounter name ifOutFramesEthPortPurpose Throughput monitoringFamily IP statisticsApply to Ethernet portUnit Frame



42

Unit FrameMeaning Total number of Ethernet frames transmitted out of the

interfaceTriggering event Every sending of an Ethernet frameScreening NoNotes The throughput indicator is defined as a total number of

transmitted or received Ethernet frames

Labels DescriptionCounter name ifInFramesEthPortPurpose Throughput monitoringFamily IP statisticsApply to Ethernet portUnit Frame



43

Unit FrameMeaning Total number of Ethernet frames received on the

interfaceTriggering event Every reception of an Ethernet frameScreening NoNotes The throughput indicator is defined as a total number of

transmitted or received Ethernet frames

Labels DescriptionCounter name ifOutKbytesEthPortPurpose Bandwidth monitoringFamily IP statisticsApply to Ethernet portUnit Kbyte



44

Unit KbyteMeaning Total number of Kbytes transmitted out of the interfaceTriggering event Every sending of an Ethernet frameScreening NoNotes The bandwidth indicator is defined as an Ethernet data

volume transmitted or received in Kbytes

Labels DescriptionCounter name ifInKbytesEthPortPurpose Bandwidth monitoringFamily IP statisticsApply to Ethernet portUnit Kbyte



45

Unit KbyteMeaning Total number of Kbytes received on the interfaceTriggering event Every reception of an Ethernet frameScreening NoNotes The bandwidth indicator is defined as an Ethernet data

volume transmitted or received in Kbytes

Labels DescriptionCounter name ifOutDiscardsEthPortPurpose Daisy chaining frame loss monitoringFamily IP statisticsApply to Ethernet portUnit FrameMeaning Total number of outbound Ethernet frames discarded



46

Meaning Total number of outbound Ethernet frames discarded due to lack of resources, transmission error or output queue is full, even if no error has been detected.

Triggering event Every sending of an Ethernet frameScreening NoNotes The frame loss indicator is defined as a total number of

Ethernet frames discarded due to lack of resources, transmission error or output queue is full, even if no error has been detected.

Labels DescriptionCounter name ifInDiscardsEthPortPurpose Daisy chaining frame loss monitoringFamily IP statisticsApply to Ethernet portUnit FrameMeaning Total number of inbound Ethernet frames discarded due



47

Meaning Total number of inbound Ethernet frames discarded due to lack of resources, bad FCS, alignment error or oversized frames, even if no error has been detected.

Triggering event Every reception of an Ethernet frameScreening NoNotes The frame loss indicator is defined as a total number of

Ethernet frames discarded due tolack of resources, bad FCS, alignment error or oversized frames, even if no error has been detected.


6 Known Limitations

Port configuration

Daisy chaining can be activated ONLY in Native IP Iub configuration & when the backhaul interface is GE MDA.

2 out of the 3 GE MDA ports can be used ONLY since GE MDA SFP2 and GE MDA RJ-45 CANNOT be used simultaneously (mutually exclusive)

Synchronisation

Known limitations (1/2)


49

The Node B itself does NOT modify the transparent clock correction field and CANNOT act as a transparent clock in Daisy Chaining mode See Chapter 4c of PTP OEM

SyncE is only supported with GE MDA SFP optical and GE MDA RJ45 ports See Chapter 4b of SyncE OEM

SyncE is supported with Node B daisy chaining feature in ingress (MBH) and egress (DC) ports See Chapter 4b of SyncE OEM

Validation

Node B Daisy Chaining mode is only validated with ALU 2G/3G/4G products. Any support with 3rd party products requires some additional IOT tests that will berequired internally, and discussion between the local team and the customer.

Node B Daisy Chaining only supported configurations are: 3G->3G, 3G->3G->Smartbits, 3G->4G-IPv4, 3G->4G-IPv6, 3G->4G-IPv4-IPSEC

Features incompatibility

Known limitations (2/2)


50

Daisy chaining cannot be deployed jointly with:

Dual port configuration (i.e. Split Iub) (feature 79362)

LAG (feature 112412)

IEEE803.3ah (EFM) introduced in the Node B w/ feature 103182 - Ethernet OAM in

the Node B

Service

In case of 3G Node B failure or reset, the daisy chained traffic will be interrupted. Single point of failure.


7 Documentation References

Documentation References

[1] FN BTS Daisy chaining through the NodeB (LR13.1 W - FRS 100791)

[2] SDS IP in UTRAN (LR13.1 W - FRS 113326)

[3] FN IP in UTRAN (UA07)

[4] Native IP Iub in UA7.1 - Operational Engineering Method (OEM) (U07)

[5] Iub Transport Engineering Guide (LR13.1 W)

[6] Iub Transport Engineering Guide (UA08.1)

[7] RAN Model (UA07/UA08.1/LR13.1 W)

[8] 9353 WMS - Activation of an Operator Configurable Split of IP Traffic over Hybrid Iub


52

[8] 9353 WMS - Activation of an Operator Configurable Split of IP Traffic over Hybrid Iub

[9] 9353 WMS - Activation of an Operator Configurable Split of IP Traffic over Native IP Iub

[10] 9353 WMS - Activation of Hybrid Iub

[11] 9353 WMS - Activation of Native IP Iub

[12] PPM (Domain: WCDMA; Folder: UA09.1)

[13] Mercury QC (domain: UMTS; Project: LR_13_UA09)

[14] LR13.1 W RNC PEI

[15] LR13.1 W Node B PEI

[16] UTRAN IP WG (Engage)


8 Appendix

Traffic directions (1/2)

Downlink traffic


54

Traffic directions (2/2)

Uplink traffic


55


56


57

UMT_IRC_APP_040083_V01 01_EN_OEM_Node_B_Daisy_Chaining (3).pdf

Documents

Transcript of UMT_IRC_APP_040083_V01 01_EN_OEM_Node_B_Daisy_Chaining (3).pdf