Circuiting Guidelines Issue 3 PDF

National Circuiting Team Guidelines – Issue 3
National Circuiting Team Guidelines
Summary
This document provides the information required to circuit all Nokia and NEC Node
Bs in Cramer. Not all scenarios are detailed explicitly but this document should
provide an experienced Cramer user with enough information to tackle any circuiting
requirements. The content of this document was based upon the need to handover all
circuiting responsibilities to the regional teams. Therefore it mainly covers THS to
RNC or OLO to RNC. However as the document is revised it is envisaged that this
emphasis will change and the complete end to end circuiting process will be included.
One key assumption that will remain unchanged is that all VC-4 and higher order
connectivity is left out of this reference and will still be implemented by NCT. This
version 3 has been amended to include the new Nortel OME6500s in Birmingham, the
new ATM model based on actual Nortel Passport device models and a section on
general reparenting.
Document Control
Document Ref: TBA
Version: Issue 3
Date: 11/03/2005
Authors: Andy Broadbent, Rob Platt
Page 1 of 79
national.circuiting.team@three.co.uk
Contents
Introduction....................................................................................................................4
UTRAN Network Overview ..........................................................................................5
The Basic Rules of Cramer Circuiting...........................................................................6
Location Creation.......................................................................................................6
Device Creation .........................................................................................................6
Link Creation .............................................................................................................6
Circuit Creation..........................................................................................................7
Nokia THS Circuiting Guidelines................................................................................12
Introduction..............................................................................................................12
ATM Cramer Model ................................................................................................12
ATM Router.............................................................................................................12
Nokia THS Datafill ..................................................................................................25
NEC THS Circuiting Guidelines .................................................................................27
Introduction..............................................................................................................27
Circuiting Assumptions ...........................................................................................27
Circuiting Process ....................................................................................................27
BT Leased Bandwidth Circuiting Guidelines ..............................................................31
Introduction..............................................................................................................31
BT Device Models ...................................................................................................31
BT Network Architecture in Cramer .......................................................................32
BT Circuiting Details...............................................................................................34
Circuiting BT Leased Line Process .........................................................................35
Nokia Datafill...........................................................................................................39
NTL, Telewest and Kingston Communications Circuiting Guidelines .......................40
Introduction..............................................................................................................40
Circuiting Process ....................................................................................................40
How E1’s are delivered into Three UK’s PoP and DC’s.........................................45
Nokia Datafill...........................................................................................................45
Circuiting Using Alcatel For Hemel 0 and Hemel 1....................................................46
Introduction..............................................................................................................46
Alcatel Network Equipment ....................................................................................46
NEC Circuiting Through a Nokia THS .......................................................................47
Introduction..............................................................................................................47
Physical Circuiting...................................................................................................47
Logical Circuiting ....................................................................................................48
NEC Datafill ............................................................................................................48
NEC Circuiting to STM-1 Based eRNC......................................................................49
Introduction..............................................................................................................49
Physical Circuiting...................................................................................................49
ATM Network Representation.................................................................................50
Transmission Architecture .......................................................................................51
Logical Circuiting ....................................................................................................52
NEC Logical Circuiting ...........................................................................................53
NEC STM-1 Datafill................................................................................................54
Birmingham OME6500 Circuiting ..............................................................................54
Node B Reparenting.....................................................................................................55
E1 Reparenting.........................................................................................................55
Page 2 of 79
ATM Reparenting ....................................................................................................66

NEC South Wales ATM Reparenting......................................................................66
Appendix......................................................................................................................67
Page 3 of 79
Introduction
This document describes the main procedures required to Circuit a Node B end to end
in the Cramer planning tool. Due to the history of this document its main focus is on
the core components of the access transmission network. That is circuiting across the
backbone, leased bandwidth and data centres. For example microwave connectivity is
currently not covered but as the document is revised it is envisaged it will be
expanded to address these areas. Therefore please ensure that this is the latest version
by looking at the circuiting knowledge share area on the Three intranet.
To simplify the creation of this document the material contained within this reference
has been split into the following key areas: Basic Cramer guidelines, Nokia THS
circuiting, NEC THS circuiting, BT leased bandwidth circuiting, OLO leased
bandwidth circuiting, Alcatel network circuiting, NEC sites through Nokia THS
circuiting, NEC STM-1 RNC circuiting, Birmingham OME6500 circuiting and
reparenting. Finally there is an appendix with numerous ‘quick reference sheets’ that
should be printed separately and used as a reference whilst reading this document.
Due to the nature of circuiting a number of the sections may need to be referenced to
circuit a particular Node B. For example to circuit an NEC Node B to an STM-1
RNC information will also need to be taken from the THS or leased bandwidth
section and possibly the Alcatel circuiting section. Also to complete the datafill the
ATM router is used which is described in the Nokia THS section.
The level of detail included in this document is based on the assumption that all the
VC-4 connectivity has already been built in Cramer.
Page 4 of 79
UTRAN Network Overview

A basic representation of the access network modelled in Cramer can be seen in
Figure 1 below.
The diagram shows the typical network configurations using microwave, leased lines
and transmission high sites (THS). Each Node B must be connected to its parent
RNC. In Cramer there are two layers of connectivity that must be planned to achieve
this.
• The first level of connectivity is at the physical layer, which is provided by

PDH microwave, other licensed operators (OLO) leased lines, and our own
backbone transmission network using SDH and DWDM technologies.
• The second level of connectivity is at the ATM layer. Each Node B requires a
number of ATM permanent virtual circuits (PVC)s.
Figure 1 Three UK UTRAN Network
More detailed examples with RAN vendor specific architectures can be found in the
appendix.
Page 5 of 79
The Basic Rules of Cramer Circuiting

Before the detail of circuiting specific Node Bs is documented this section looks at
some of the basic rules and features of Cramer. It is important to understand these
rules and features as later sections will rely on them.
Location Creation
All devices in Cramer must be related (parented) to a location. The majority of
locations in Cramer will be pre-created for the users. However the main exception is
the Node B location itself. Before creating a Node B the user must create a location.
The location should be created as a type ‘site’ with a parent location of their specific
region, using the Nominal to create the name. The complete format for a site name is
shown below;
Node B site naming conventions will be of the form;
XXXXXX
Where XXXXXX= the Net One Nominal ID
THS site naming conventions will use the form;
THS_XXXXXX
Where XXXXXX = the Net One Nominal ID.
Device Creation
All devices and therefore shelves and cards should only be created at a specific
location. All devices should also only be created using the provision status of In
Service. On creation of the majority of devices Cramer will automatically apply a
standard naming convention usually relating the device to its current location. Where
an automatic device name is not given it will need to be generated manually. The two
most common devices that will require manual naming conventions are where a
device represents another operator’s equipment and therefore requires their unique
reference. Or where a devices name is made up of its floor or rack position such as a
DDF of ODF (highlighted in more detail later).
Link Creation
All links should be created in Cramer using the In Service provision status with the
exception of Leased Line Links (see below). As with devices most links will be
created with an automatic naming convention provided by Cramer. However a
number of links will require manual intervention to utilise the correct naming
conventions. Such as microwave links where the enterprise number should be used or
leased line links where the OLO reference should be used.
Page 6 of 79
Link Orientation
All links (and circuits) are created in Cramer with a specific orientation. The RNC
end of a link is always considered the A end and the Node B end is considered the B
end. Therefore all links used in the connectivity must adhere to this rule.
Leased Line Links Statuses

The status of a Leased Line link is used by the Leased Bandwidth team to manage
their processes and provide billing validation with the OLOs. Therefore it is
important for a transmission planner to ensure the following link statuses are used in
Cramer during the relevant stages of a leased bandwidths lifecycle.
1. OLO link awaiting completion (delivery):

a. The Leased Line link status should be PLANNED.
2. OLO link delivered but not in use:

a. The Leased Line link status should be RESERVED.
b. The link should also go to a SPARE E1 Cloud.
3. OLO link delivered and in use:

a. The Leased Line link status should be IN SERVICE.
4. OLO link awaiting Cease or Cancellation:

a. The Leased Line link status should be CANCELLED.
b. The link should also go to a SPARE E1 Cloud.
Circuit Creation
Circuit Naming
All circuits created in Cramer have an automatic naming convention applied in the
following format.
$xxxxxx
Where xxxxxx is a unique 6-digit number and $ is a prefix based on the circuit type or
bandwidth, the current list of prefix’s are;
A = 2 Mbps/E1
AT = ATM Tunnel
B = STM-1
C = STM-4
D = STM-16
E = STM-64
F = STM-256
G = STM-1024
L = Low Order Path
M = Microwave Bearer
P = PDH Bearer
T = Low Order Trail
Page 7 of 79
W = ATM Bearer
X = VPI
Y = VCI
Z = PVC
These automatic naming conventions can all be manually overwritten but the
proposed value should in most cases be used. The only current exception is the
microwave bearer where the enterprise number should replace the 6 digit generated
number (highlighted later).
Circuit Lifecycle/Status
All PDH circuits in Cramer are controlled by a comprehensive circuit lifecycle. The
lifecycle seen in Figure 2 has been designed to track a circuit through its planning,
design, implementation, and finally decommission/deletion states. Each of the boxes
represents a valid status for a PDH circuit and the arrows show the valid transitions.
The key aim of the lifecycle is stop users simply deleting circuits without
understanding the consequences in the real world. For example once a circuit has
been tasked to operations (e.g. status ‘issued’) the user looses all ability to modify or
delete the circuit. To delete the circuit the user would have to transition it to
decommission and in the process of doing so the hope is that it will trigger the user to
re-task operations to ensure that any work done in the field is recovered.
The majority of statuses should be self explanatory as should the user restrictions for
each status but in summary: The only states were a user can modify a circuit is
Logged, Planned or National Planned and the only status that a circuit can be deleted
from is Cancelled, Decommissioned or Logged.
All status changes in Cramer can be done manually (following the lifecycle) however
the main planning and build statuses are also transitioned automatically by the
completion of Net One tasks.
The final point to note is that the circuit lifecycle and therefore restrictions are only
applied to the PDH circuit layer. However if an underlying circuit has a PDH circuit
using it then the PDH circuit will control the actions that can be taken. This is
important to note when using SDH capacities as one PDH circuit could restrict the
modification of an underlying high order circuit.
Page 8 of 79
Logged
Regional Regional
Regional
Regional Planned
Regional
Regional
Regional Regional Cancel

Regional
Regional
National Planned
Regional Regional
Regional
Issued
Regional
Regional
Regional
Regional Decommissioned
Tested - Passed In Service
Regional Regional
Regional
Regional
Out of Service
Figure 2 Circuit lifecycle. This diagram shows the valid provision statuses and transitions for a
PDH circuit.
Circuit Orientation
All circuits (and links) are created in Cramer with a specific orientation. The RNC
end of a circuit is always considered the A end and the Node B end is considered the
B end. Therefore all circuits used in the connectivity must adhere to this rule.
Circuit Hierarchy
PDH Circuit Hierarchy

There are three layers that need to be represented in Cramer for PDH, the link, the
bearer and the circuit. All are shown in Figure 3 with their appropriate naming
conventions.
Page 9 of 79
PDH Circuit = Axxxxxx
PDH Bearer = Pxxxxxx
PDH Copper Link PDH

Device Device
Figure 3 Cramer PDH Circuit Hierarchy
SDH Circuit Hierarchy

There are up to six layers that need to be represented in Cramer for the SDH hierarchy.
All are shown in Figure 4 with their appropriate naming conventions. The high order
trail represents the VC-4 layer and the low order trail and low order path combine to
represent the VC-12 layer.
PDH Circuit
Low Order Path = Lxxxxxx
Low Order Trail = Txxxxxx
High Order Trail = Bxxxxxx
MS Bearer = ‘Bandwidth Prefix’xxxxxx
SDH Fibre Link SDH

Device Device
Figure 4 Cramer SDH Hierarchy
Microwave Circuit Hierarchy

There are three layers required to model a microwave connection in Cramer. The
microwave bearer and link should both contain the Enterprise planning tools link id
for the microwave link. See Figure 5 below.
Figure 5 Cramer PDH Microwave Hierarchy
Page 10 of 79
Leased Bandwidth Circuit Hierarchy

The leased bandwidth circuit hierarchy is the same as the standard PDH hierarchy
except that the link name should contain the OLO reference for the link (see Figure 6).
PDH Circuit
PDH Bearer
Leased Line Link = ‘OLO Reference’ OLO

Node B
NTE
Figure 6 Cramer Leased Bandwidth Circuit Hierarchy.
ATM Circuit Hierarchy

In Cramer the ATM circuit hierarchy was designed to represent networks that only
performed VP switching. Therefore it only manages VP numbers and the current
highest level of circuit used in Cramer is the VC layer (however PVCs can be shown).
The current hierarchy is shown below and it should be noted that the IMA parallel
circuit layer is optional depending if the physical layer is PDH and more than 1 E1.
The VPxxxx represents the actual VP number used by the overlying VC circuit.
PVC = Zxxxxxx
VC = Yxxxxxx
VP = Wxxxxxx VPxxxx
ATM Bearer = Wxxxxxx
Optional PDH IMA Parallel Circuit = PIMACxxxxxx
ATM SDH or PDH Circuit ATM

Node Node
Figure 7 Cramer ATM Hierarchy for VP Switching.
Page 11 of 79
Nokia THS Circuiting Guidelines

Introduction
The regional planner circuits the Nokia AXC to the SAXC at the THS using a number
of E1s. These E1 circuits terminate on the SAXC and the traffic is then carried at the
ATM layer via an STM-1 connection to the RNC. Therefore the planner must
complete the end to end circuiting using the ATM router. Before the steps to do that
are discussed a brief introduction to the Cramer ATM model is given.
ATM Cramer Model

In Cramer the main aim of the ATM layer is to show end-end connectivity and
provide datafill information. Therefore to improve maintainability and reduce
complexity it was agreed to model only the VP level connectivity. The VC
connectivity (numbers of circuits, Peak Cell Rates, VC numbers etc) is tracked as a
set of parameters and stored in the Network Parameter System (NPS).
The end result is that the ATM connectivity will be shown with an end to end VC
using the format Y******.
There is a slight deference between NEC and Nokia’s VC requirements in that NEC
requires one VC per E1 and Nokia uses one VC per Node B. The reason for this is
Nokia’s support of IMA.
The Y reference VC circuits will not replace the ‘A’ circuits used to show the PDH
connectivity but will be in addition. The relationship between the different circuits
can be seen in a typical Nokia example in Figure 8 below.
ATM VC
ATM VP ATM VP ATM VP
ATM Bearer ATM Bearer ATM Bearer
PDH IMA Parallel Circuit
STM-1 STM-1
E1 Port Port
Ports
PDH Circuit(s) STM-1
STM-1 SDH
Port SDH High Order Trail
Port High Order Trail
Nokia
Node B SAXC - AXC1 SAXC - AXC2
RNC
Figure 8 Example ATM Circuit Hierarchy through THS
Throughout this document the Node B will be referred to however for all Nokia
circuiting this implies the AXC (the same as for PDH circuiting).
ATM Router
To create ATM circuits in Cramer using the standard wizard functionality requires a
significant amount of time and detailed ATM understanding. The standard Cramer
model is overly flexible and open to significant human error. Therefore to limit the
amount of time taken to circuit and limit the amount of possible human error a
Page 12 of 79
Service Delivery Module (SDM) template has been created. This SDM is called
‘ATM Router’ and can be found under the ‘circuits’ wizard.
ATM Router Use

The ATM router SDM is fairly self explanatory during use however this section
highlights some of the key steps with screen shots:
Step 1: Run the ATM Router by selecting it from the circuits wizard.
Step 2: Process the SDM following all the steps, firstly by selecting the Z end device
(Node B end).
Page 13 of 79
Step 3: Enter the number of ATM hops between the Node B and the RNC. This
implies the number of hops between active ATM devices. To help understand the
number of ATM hops there is a guide in the Appendix showing the most common
scenarios.
Page 14 of 79
Step 4: For each of the ATM hops the underlying circuits will need to be entered. The
SDM has been written in such a way that it does not matter which level of circuit is
selected. The user can select anywhere in the hierarchy from the correct VP to the
underlying SDH High Order Trail or PDH Circuit. The SDM also allows for any
amount of ATM to be created (or not created in advance). In this example the first
PDH circuit at the Node B has been selected.
IMPORTANT NOTE: The number of ATM HOPS must carefully be calculated.

For example a site via a Nokia THS might in fact go via an SAXC in the DC. To
check for these types of scenarios the user should look at the SDH HOTs on each
SAXC and see if they go to an SAXC in the DC or an RNC.
Page 15 of 79
Step 5: When selecting the PDH circuit the SDM has calculated that there is more
than 1 PDH circuit at the Node B and an IMA group is required. Between all Nokia
Node Bs and SAXCs or RNCs an IMA group is created on the equipment.
However for NEC each E1 has its own ATM circuitry. Therefore NEC Node Bs
should be circuited with 1 ATM circuit per E1.
The next screen is a prompt for the number of other circuits that will be in the IMA
group.
Page 16 of 79
Step 6: Once the number of E1s in the IMA group has been set the other E1s must be
added to the SDM. Again the SDM will propose what it believes are the correct E1s
and in most cases they can just be accepted as correct.
Page 17 of 79
Step 7: After selecting all the E1s the IMA group numbers are created. Although at
this stage the user can modify the group numbers the user should just accept the
values proposed by the SDM.
Step 8: Depending on the scenario the user may also be prompted to create ATM If
IDs. Although at this stage the user can modify the group numbers the user should
just accept the values proposed by the SDM and move on. (NEC circuiting does not
require ATM if IDs).
Page 18 of 79
Step 9:
Once all the information has been added for the ATM hop the SDM will ask which
VP to use. The SDM will propose the next available VP on that ATM hop however
any value can be selected. The user in most cases should select the proposed value.
Page 19 of 79
Step 10: Each of the ATM hops will then need to be completed in the same way. In
this case the next hop is an SDH hop and the HOT has been selected. The user should
always be careful to select the correct HOTs in the right order. Ensuring that if
required the HOT between shelves of a Nokia SAXC is selected before the HOT to
the RNC.
Page 20 of 79
Step 11: With each hop the user will again be asked for the VP and the system will
propose the next available value.
Page 21 of 79
Step 12: On completion of all hops the user will then be shown the screen below which
creates the VC end to end over all of the VP values selected. The SDM will look at
what is already created and what is not over the entire route and ensure all the correct
ATM layers are created and labelled accordingly.
Page 22 of 79
Step 13: After completion of the whole SDM the ATM circuits can be seen using all
the normal methods. A circuit view on the Node B can be seen below.
Page 23 of 79
Step 14: To assist with the datafill a special web report has been created that brings
together all the information that is required. This report is accessed either at the Node
level or the circuit level and is part of the right click menu as shown below.
Modifications to ATM circuits

Once ATM circuits have been entered into Cramer using the ATM router the user
may need to make changes to some or all of the ATM details. The following section
lists the most common changes and how they can be made.
Additional E1s to IMA Circuits

A special additional SDM has been created to allow the user to increase or decrease
the number of E1s in an IMA group. ‘IMA Group Update’ can be found under the
circuits wizard. To add E1s the user simply needs to run the wizard and follow the on
screen instructions. To remove E1s the user firstly needs to use the circuit wizard on
the PDH IMA Parallel Circuit and remove the no longer required E1. The ‘IMA
Group Update’ should then re-run to update the PDH IMA Parallel Circuit to its now
reduced bandwidth.
Changing VP Values
Using the homepage of each Virtual Path the user can change the VP number.
Cramer will automatically validate the number to ensure it is in the permitted range
and unique on the ATM bearer.
Page 24 of 79
Changing ATM if Id Values

ATM if ID Values are associated with the ATM bearer. Therefore by running the
Circuit Wizard on the ATM bearer the user will get the option to change the values at
the attribute stage of the wizard. Values will be validated against their relevant
objects.
Changing IMA group Values

IMA group Values are associated with the PDH IMA Parallel Circuit. Therefore by
running the Circuit Wizard on the IMA Parallel Circuit the user will get the option to
change the values at the attribute stage of the wizard. Values will be validated against
their relevant objects.
Modifying a Circuits Route

The VC and VP circuit layer’s can all be manipulated by using the Data Circuit
Wizard. However if an ATM bearer is moved using the Circuit Wizard Cramer will
automatically move the VP and VC layers. It is important to note that when moving
ATM circuits with either the Data Circuit Wizard or the Circuit Wizard the user must
take responsibility for ensuring the validity of the new configurations.
Nokia THS Datafill

Currently the Nokia datafill is produce using the ATM report from Cramer. This
report should be generated (an example is shown in Figure 9 below) and saved on the
datafill shared area on the network (G:\Network_Rollout\Transmission\Nokia
Parameter\RAN 1.5.2 data). Each site should have an individual folder created on the
shared area and the ATM report file MUST contain the full name of each node B as
provided by the Radio Design team. An example file name would be:
NK.OP1.A3_AB0006.htm
It should be noted that this is a temporary process and will at the least be updated
periodically. Therefore it is important to check with the National Circuiting Team
what the current template/process is.
ATM Report AVM for Node

AXC/AB0006
Date: 01/07/2004 09:36:12
VC Circuit : Y001744
Device : Nokia AXC Optima Compact
Name : AXC/AB0006
Incoming :
None
Outgoing :
Port(s) : E1.1.2.1
E1.1.2.2
IMA Group : 33
Page 25 of 79
ATM Bearer Bandwidth : 2*E1

VP Number : 1
Device : Nokia SAXC
Name : SXC1/AB0026
Incoming :
Port(s) : E1.1.4.7
E1.1.4.8
IMA Group : 33
ATM Bearer Bandwidth : 2*E1
VP Number : 1
Outgoing :
Port(s) : STM-1.1.2.1
IMA Group :
ATM Bearer Bandwidth : 155M
VP Number : 15
Device : Nokia SAXC
Name : SXC1/AB0026
Incoming :
Port(s) : STM-1.2.2.1
IMA Group :
VP Number : 15
Outgoing :
Port(s) : STM-1.2.2.3
IMA Group :
VP Number : 15
Device : Nokia RNC
Name : MR0RNC08
RNC 3GPPP
ID :
Incoming :
Port(s) : STM-1.RNAC1.5.3
SET/PET : SET 02
ATM Interface ID: 201
IMA Group :
VP Number : 15
Outgoing :
None
This Report is created by: abroadbent

( Andy.Broadbent@hutchison3G.com )
Figure 9 Nokia Datafill
Page 26 of 79
NEC THS Circuiting Guidelines

Introduction
This section details the process used to extend the regional PDH circuit(s) onto the
designated RNC (in the NEC THS scenario).
The NEC THS network diagram in the appendix should be used as a reference point
whilst reading this section.
There are 5 main events/tasks to undertake in order to successfully extend the regional
circuit onto the RNC.
1. Extend PDH Bearer (that currently runs from DDF2, 3 or 4 to the co-located Node
B or Paso link and vice versa) to the tributary side of the TN1X.
2. Create LOT (Low Order Trail) (Txxxxxx) between OM4100 aggregate port and
TN1X aggregate port.
3. Create LOP (Low Order Path) (Lxxxxxx) between OM4100 tributary port and
TN1X tributary port, this circuit will sit on top of the LOT.
4. Create PDH Bearer (Pxxxxxx) between RNC port and the OM4100 tributary port.
5. Extend PDH Circuit (that currently runs from DDF2, 3 or 4 to the Node B and vice
versa) onto the chosen RNC port; this will sit on top of the circuits that have just been
created.
Circuiting Assumptions
It is assumed the following criteria have been met.
• Circuit(s) will be “Resolved”

• Circuit(s) will terminate on either THS DDF2, 3 or 4
Circuiting Process
Extend PDH Bearer
Locate the PDH Bearer that runs to the access DDF of the THS (2, 3 or 4), extend this
onto the TN1X tributary side, use the next available TN1X port.
The “Yes” button on the “Create XC’s” option must be ticked in order to successfully
create the Cross Connect. (See Figure 10)
This automatically creates the cross connection between the Access DDF (2, 3 or 4)
and DDF1.
Page 27 of 79
Figure 10 PDH Bearer extension - create crossconnect
LOT (Low Order Trail) Creation

The next underlying circuit to create is the LOT; the “Bandwidth” of this circuit is
VC12, as is the “Circuit Subtype”.
The LOT runs from the Nortel ADM (OM4100) aggregate port to the TN1X
aggregate port, this is a VC12 timeslot within the VC4 (Bxxxxxx) (See Figure 11)
Figure 11 Circuit view of LOT
Create the LOT, ensuring that the timeslot used relates directly to the tributary port of
the TN1X (i.e. Port 1 of the TN1X should route on timeslot 1 of the VC4).
Page 28 of 79
There are 62 usable timeslots on the VC4 (for Iub traffic), whereas there are 64
tributary ports available on the TN1X.
The first 62 ports on the TN1X are used for Iub traffic, port 63 (Slot 11 port 15) is
used for the THS DCN traffic, and port 64 (Slot 11 Port 16) is unused at this time.
LOP (Low Order Path) Creation

The LOP also runs between the Nortel ADM (OM4100) and the TN1X, but where the
LOT runs between the aggregate ports, the LOP runs between the tributary ports.
As with the LOT, the “Bandwidth” of the LOP is VC12, the “Circuit Subtype” is E1
Timeslot.
Select the first available tributary port on the OM4100, and then select the tributary
port on the TN1X that your PDH bearer connected to.
The LOP sits on the LOT, the LOT then needs inserting underneath the LOP (see
Figure 12)
Figure 12 The LOT is inserted into the LOP
The combination of the timeslot (LOT) and the physical port on the OM4100 (LOP)
makes up the VC12 connection.
This is a software connection configured on Preside, the Nortel network management

tool.
Create PDH Bearer

The next circuit to create is a PDH bearer, this will run from the RNC port to the
tributary port of the OM4100 (this is the same port that the LOP terminates on)
Locate an RNC allocation by running a “Terminating Traffic AVM” on the RNC.

(See Figure 13)
Page 29 of 79
Figure 13 Terminating Traffic AVM on an NEC RNC
For guidance on allocating RNC ports please refer to the following document:
G:\Network_Rollout\Transmission\Access Transmission\NEC RNC Iub Port

Allocation Guidelines D1.13.doc
A PDH bearer between the chosen RNC port and the tributary port on the OM4100
needs creating, once again, ensure that the “Yes” button on the “Create XC’s” option
is ticked.
Both the RNC and the OM4100 are pre wired out to designated DSX frames, we then
have to jumper between the two frames (this is the Cross Connect that you are
creating).
Extend PDH Circuit

All the underlying circuits relevant to extend your PDH circuit round the backbone to
the RNC have now been created.
Use the “Circuits Wizard” to select and modify the PDH Circuit.
The A end of the circuit now needs amending, this should now route to the RNC port
chosen earlier.
Insert your LOT, LOP and PDH Bearer (created previously) underneath this circuit.
The circuit should now be resolved.
Page 30 of 79
BT Leased Bandwidth Circuiting Guidelines

Introduction
This chapter looks at the process of circuiting a BT leased line site in Cramer. The
leased bandwidth circuiting diagram in the appendix should be used as a reference for
this chapter.
In Scope
• Explanation of the BT device and network models in Cramer
• Explanation of the BT circuit details in relation to Cramer
• Creation of a VC-12 connection across the BT network and Three’s backbone
transmission network
• Creation of data centre connectivity
• Extension of PDH circuit to show the end to end E1 connectivity
• Nokia Datafill
Out of Scope
• BT Netstream 16 LL description
• Creation of BT MSH51c device models in Cramer
• Creation of BT MXLL High Order Trails in Cramer
• Circuits delivered by OLOs other than BT
• BT Northern Ireland deliveries (these should be circuited in the same way as
the directly connected NTL sites using all the BT references)
• There are 1 or more PDH circuits of E1 bandwidth circuited from the Node B
to an OLO device
• The circuits are routed over Leased Line links connected to the OLO device
with an MXGB reference
• The circuits are resolved and in a planned status
• BT circuiting details are available
BT Device Models
To understand how to circuit a leased line site it is important to understand the
equipment used by BT. To provide Three with the required connectivity BT install
three main types of network equipment. These are detailed here:
At a typical Node B site BT will use a 4 x 2 NTE.

BT 4 x 2 NTE
4 x 2MBit/s Ports
This provides connectivity for up to 4 E1 circuits.
Page 31 of 79
At a fibre nodal site the main NTE is a 16 x 2.

BT 16 x 2 NTE
16 x 2MBit/s Ports
This provides connectivity for up to 16 E1 circuits. In some fibre nodal sites instead
of a 16 x 2 NTE BT may install multiple 4 x 2 NTEs.
At a backbone point of presence or the datacentre BT use an MSH51c:
BT MSH51c NTE
10 x Slots for
Trib Cards
1 x STM-4 Port
Trib Card 2 x STM-1 Port
Trib Card
The MSH51c is a SDH ADM which is connected to the BT network at STM-16. This
provides BT with the capability to deliver both STM-4 and STM-1 interfaces to Three.
BT Network Architecture in Cramer

To model the BT network in Cramer Three have created a unique representation that:
• Provides enough information for all jumpering and provisioning

• Reduces the amount of unnecessary circuiting
• Avoids complex and meaningless network modelling (we don’t know or need
to know how the BT network is built)
The representation uses just one device an OLO (other licensed operator). This
device combines both the NTE at the Node B with the SDH NTE at the data centre or
backbone PoP. The following diagram (Figure 14) shows a ‘rack face layout’ of an
OLO device.
Page 32 of 79
BT SNEID (MSH51c)
Shelf 1
Node B NTE Cards
N N N N N N N N N N
T T T T T T T T T T
E E E E E E E E E E
Shelf 2
N N N N N N N N N N
T T T T T T T T T T
E E E E E E E E E E
Shelf 3
Shelf n
Figure 14 Rack face layout of the BT OLO device
One OLO device is required to model each BT MSH51c and is located in Cramer
within the relevant backbone PoP or data centre. Shelf 1 of the OLO device is used to
represent the MSH51c (although it has 16 slots only 10 are required and therefore 6
ignored). These 10 slots model the 10 slots in the MSH51c and are populated with
trib cards to match the actual build of the MSH51c on site. This allows Three to
create all the physical links from the MSH51c required by operations for jumpering.
The remaining shelves (as many as required) are used to hold NTE cards. Each NTE
card represents the NTE at the Node B site. This solution enables a single device to
represent the whole BT network.
Figure 15 is a screen shot of an ‘elevation view’ of a current Cramer OLO device

showing the population of the MSH51c and some of the NTE cards representing the
NTE at the Node B sites.
Page 33 of 79
Figure 15 OLO device Elevation view
An advantage of this BT network representation is that the OLO device is circuited as

any standard SDH ADM or network element. The MSH51c shelf (1) is treated as the
aggregate side of the MUX and the remaining shelves with their NTE cards are
treated as the tributary side of the MUX.
BT Circuiting Details
Each individual E1 circuit delivered by BT (as part of an STM-4) is supplied with the
circuiting details. These details are used to enable the Three transmission network to
be configured to ‘match’ the BT network and hence deliver the circuits at E1 level.
An example of the circuiting details are seen in Figure 16.
Page 34 of 79
Figure 16 BT leased bandwidth details
The A End SNEID, A End TRIB, A End ‘J’ value and MXLL reference can be used
to validate the details against Cramer. To assist with the task the MXLL or MXUK
reference is always put in the Alias 2 field of the VC-4 circuit (High Order Trail) in
Cramer.
Circuiting BT Leased Line Process

Circuiting a leased line in Cramer is the same for both Nokia, NEC and fibre Nodals.
Throughout this section the Node B will be referred to, however for Nokia this
implies the AXC i.e. the starting point of the PDH circuit. Fibre Nodals are also
considered identical because the part of the circuiting that is different is before the
OLO device under the ownership of the regional transmission planner.
To circuit a leased line site in Cramer the Node B must be created and connected
(with leased bandwidth links and PDH circuits) to its correct NTE card in the OLO
device. The circuiting details for the MXGB and MXLL should also be checked
against the details in Cramer. If there are any discrepancies these should be raised
back to BT for resolution
Once the checking is complete these simple steps provide the procedure for circuiting
a leased line site. Where necessary some example screen shots have been added.
Page 35 of 79
LOT Creation
Using the circuit wizard create a Low Order Trail (LOT) of VC-12 bandwidth in the
relevant timeslot of the High Order Trail (HOT) based on the JKLM reference
supplied by BT. The screenshot below (Figure 17) shows the HOT homepage with its
MXLL reference and the circuit wizard where the same HOT is being inserted into the
LOT.
Figure 17 HOT insertion into a LOT
LOP Creation
On completion of the LOT a Low Order Path (LOP) should be created using the LOT
as the underlying circuit. The LOP should start on any available port on the Nortel
OM4100 at the datacentre and end on the correct port on the correct NTE card in the
OLO device to match the BT MXGB reference. Figure 18 shows the end points of a
LOP being selected.
Page 36 of 79
Figure 18 LOP creation
PDH Bearer Creation

On completion of the previous step, the SDH element of the process is now complete.
A PDH connection is required between the Nortel OM4100 and the RNC. To choose
an RNC port the RNC allocation guidelines should be consulted. Once the RNC port
is selected a PDH bearer is created between that RNC port and the port on the
OM4100 corresponding to the termination point of the LOP. The screenshot below
(Figure 19) shows the creation of a PDH bearer.
Page 37 of 79
Figure 19 PDH bearer creation
PDH Circuit Extension

The final step of the construction process is to extend the original PDH circuit from
the OLO device to the RNC over the newly created PDH bearer and LOP. The
following screenshots (Figure 20, Figure 21, Figure 22) highlight some of the basic
steps in the circuit wizard.
Figure 20 Circuit wizard with original circuit
Page 38 of 79
Figure 21 New end points are defined for the circuit
Figure 22 New bearers are inserted to the circuit

The extended circuit will now be resolved.
Nokia Datafill
For each leased line Nokia Node B the ATM connectivity must be created in Cramer.
This is exactly the same as for the THS, therefore please see the Nokia THS section
for details.
Page 39 of 79
NTL, Telewest and Kingston Communications

Circuiting Guidelines
Introduction
This section details circuiting requirements for NTL, Kingston Communications and
Telewest from the OLO equipment to the RNC for Iub traffic.
In Scope
This section covers the following areas: -
• Creation of an OLO device

• Connectivity from the Node B to the OLO device
• Connectivity from the OLO device to the backbone transmission network
(BTN)
• Routing of the VC-12 over the BTN when delivered into a PoP
• De-multiplexing of the VC-4 onto the DDF
• Connectivity from the Multiplexor (MUX) to the required RNC
• Routing of the E1/VC-12 circuit when delivered into the DC (Data centre)
• Jumpering and provisioning requirements
• Extension of a PDH circuit end to end
• Method of delivering E1’s into Three UK’s PoP and DC’s
• Nokia ATM Datafill
Out of Scope
This section does not cover the following:-
• Circuits delivered by BT
• How to create PDH bearers or circuits
• SDH principles
• ATM principles
• The end to end circuiting information from the OLO must be available for
routing
Circuiting Process
Creation of an OLO device
The OLO device represents the NTE on site and therefore should be created in the
same location as the Node B. This NTE is unique to the site and hence cannot appear
in more than one location.
Page 40 of 79
The name of the OLO device depends on which OLO has delivered the circuit/NTE,
please see below for naming of the OLO device.
NTL delivered
SNEID NTL ‘nominal ID’
Telewest delivered
SNEID Telewest ‘nominal ID’
Kingston Communications delivered

SNEID KC ‘nominal ID’
Whereby ‘nominal ID’ is replaced by the nominal ID for the site.
To build the OLO device click as follows: - wizard – nodes – device. The OLO/NTE
device created is either a 4*2NTE or a 16*2NTE depending on what is delivered.
Obviously if an 8*2NTE is required this is built as 2 x 4*2NTEs.
Connectivity from the Node B to the OLO device

A Leased Line link is to be built from the Node B or AXC to the OLO device in the
case of a directly connected site. In the case of a nodal site a leased line is to be built
from the FIU or AXC (Nokia), pasolink or Node B (NEC). Please see below for
circuit references used by OLO’s, the leased line is to be called by this reference.
NTL delivered
CAL’ref’
Telewest delivered
Tf’ref’
Kingston Communications
MXTC’ref’
All circuit structures as normal are to be built upon these links up to the OLO device.
Connectivity from the OLO device to the BTN

There are six main PoP sites and 5 data centre’s (DC’s) within Three UK’s network.
Depending on where the leased line is delivered to depends on how the circuit will be
routed.
There are some cases where the leased line is delivered into a DC but the parent RNC
is in another DC, these circuits will need to be routed over the BTN.
In this Section we will be looking at PoP site deliveries.
Page 41 of 79
An E1 copper link is to be built from the OLO device to a cloud, this cloud represents
the OLO’s network and within this network will be multiplexed from E1 to VC-4 part
of an STM-4 presented into our DC/PoP site. See Figure 23 below.
The cloud the E1 copper link terminates on depends on the vendor, for Kingston
Communications the cloud should be Kingston Communication followed by the
location (DC or PoP) e.g. WGH, for Telewest the cloud should be Telewest Hemel
and so on. The port will be automatically generated when a link is built to it, the
Cloud port should be called the ‘nominal ID’.
Over this link a PDH bearer is to be built from the OLO device to the cloud.
The VC-4 link is built from the cloud to the ODF in the PoP site, the VC-4 is named
after the OLO’s ODF or the OLO circuit reference (depending on whether it is a
structured STM-1 or an STM-4) and the port is named after the STM-1 or STM-4w/p,
you will need to know which VC-4 or STM-1 the E1 circuit is to be routed over. This
information can be gained from the circuit routing details sent through by the OLO.
Figure 23 Kingston Communications circuiting
Routing a VC-12 over the BTN when delivered into a PoP

The MS bearer is built from the cloud to the access of the BTN and the High order
trail is built from the Cloud to the 4100 MUX in the DC.
The BTN High Order Trails have already been built in Cramer, so by relating the VC-
4 link this will show you the MS bearer and associated with this the High Order
Trail’s (HO trail). There are four HO trails for an STM-4 delivered circuit, the J value
on the circuiting information will tell you which HO trail you need to provision the
circuit over. The HO trails are not always in order of J’s so a circuit hierarch AVM
can be used to show which timeslots are being used for which HO trail. See Figure 24.
Over the HO trail a low order trail will need to be built, this will run the same route as
the HO trail, aggregate port to aggregate port. The time slot chosen on the HO trail
should be that of the KLM (see appendix) provided by the OLO. Over the LO trail a
low order path will also need to built, this will also run the same route as the HO trail
but will terminate on the trib ports rather than the aggregate ports.
Page 42 of 79
Figure 24 Circuit Hierarchy AVM on an MS Bearer
De-multiplexing of the VC-4 onto the DDF

The 4100 MUX in the DC is used for breaking the STM-4 into E1’s, these are pre-
cabled out onto the DDF frame and depending on which trib port you use depends
upon your position on the frame.
PDH Connectivity at the RNC

The MUX is already pre-cabled out to the DDF and so is the RNC, these are jumpered
to the end of suite line DDF and these are also pre-cabled out to the central DDF. All
these links are in Cramer, so it is just a case of selecting the correct links. A PDH
bearer between the MUX and the RNC will need to be built in Cramer, you will need
to select the required port on the MUX and the required port on the RNC. A cross
connection can be built in Cramer between DDF’s to represent the DDF jumper. Note
that in some DC’s there is a need to add tie cables between DDF frames, i.e. if the
MUX is jumpered to an NEC frame and the parent RNC is on a Nokia frame or the
DDF frame is in a different location than the central DDF. There will need to be one
tie cable and two cross connections/jumpers. See Figure 25 for PDH bearer with tie
cables.
Page 43 of 79
Cross connections and DDF ports tie cable

Figure 25 Technical routing AVM
Routing of the E1/VC-12 when delivered into the DC

If the E1/VC-12 circuit is delivered into the DC then this will be slightly different
circuiting in Cramer, the main difference being the circuit will not be routed over the
BTN.
If the circuit is delivered as a straight E1 the termination point will be in the OLO
room in the DC presented by the OLO on a Patch panel of some kind, this information
will be needed as we jumper the circuit from the OLO Patch panel onto our own RJ45
Patch panel in the same room. This is then tie cabled across to the main transmission
room and presented onto the main DDF frame. The port on the RNC needs to be
selected as above and a PDH bearer built/extended from the RNC to the Node B/AXC.
The PDH circuit can then also be extended end to end, this circuit will need to be
jumpered between the OLO Patch panel and our RJ45 Patch panel and also at the
central DDF frame.
If the circuit is delivered into the DC as part of an STM-4 (VC-4) then the circuit will
need to be routed through a stand alone 4100 MUX. As per OLO device to the BTN
section the VC-4 will need to be identified, once this is complete the LO trail and LO
path need to be built as per routing of the VC-12 over the BTN. Everything else is the
same as routing over the back bone where the 4100 MUX is cabled out to the DDF
and a PDH bearer built from the RNC to the MUX. The LO path and PDH bearer
will then need to be inserted into the PDH circuit end to end to complete the route.
This circuit will need to be jumpered and provisioned.
Page 44 of 79
Extension of the PDH circuit end to end

The PDH circuit is built from the Node B or AXC to the NTE/OLO device, this
circuit needs to be extended end to end. The PDH circuit needs to be modified and
the A end of the RNC selected, the LO path created between the OLO cloud and the
MUX and the two PDH bearers created between the NTE/OLO device and the OLO
cloud and between the MUX and the RNC need to be inserted into the PDH circuit.
This PDH circuit should then become resolved and the end to end circuit complete. If
a circuit view is done on the PDH circuit then this should look similar to Figure 26.
Figure 26 PDH Circuit view
How E1’s are delivered into Three UK’s PoP and DC’s
E1’s are delivered into the PoP sites as either part of an STM-4 (VC-4) or as part of a
structured STM-1, either way the circuits are routed over the BTN at VC-4 level.
E1’s are delivered into the DC’s as either STM-4 (VC-4) or E1’s straight into the DC,
for E1’s delivered straight into the DC there is no need to take the circuit over the
BTN. These circuits are to be taken from the OLO’s equipment to ‘Three’s’ RJ45
Patch panel (a jumper is required) the RJ45 is pre-cabled out to the Central DDF in
the main transmission room.
NTL will deliver E1’s into our network in the following locations and as straight E1’s.
Birmingham DC
Hemel DC
Manchester DC
Telewest will deliver E1’s into our network in the following locations as part of an
STM-4 (VC-4)
Leeds/Bradford (Westgate hill PoP)

Birmingham DC
Hemel DC
Kingston Communications will deliver E1’s into our network via Telewest structured
STM-1 into the following location
Leeds/Bradford (Westgate hill PoP)
Nokia Datafill
For each leased line Nokia AXC the ATM connectivity must be created in Cramer.
This is exactly the same as for the THS, therefore please see the Nokia THS section
for details.
Page 45 of 79
Circuiting Using Alcatel For Hemel 0 and Hemel 1

Introduction
In Q4 2003 a new Data Centre was created in Hemel Hempstead which meant a new
transmission solution was implemented using Alcatel transmission equipment.
Circuiting on this solution is done in almost exactly the same way as on the Nortel
equipment. The only real difference is that the PDH Bearers and cross-connects at the
RNCs in Hemel 1 are pre-built (the equivalent of the Nortel 4100 to RNC connection).
Therefore the aim of this section is simply to highlight the new equipment. However
a quick reference guide to the required circuiting is available in the appendix and a
simplified view can be seen below.
Alcatel Network Equipment

The following Alcatel equipment has been used:
Alcatel 1641SX – this is an SDH cross-connect with the capability for up to 960 (or
equivalent) STM-1 interfaces. This is located in the original Hemel DC and is used to
connect the existing Nortel equipment to the new Alcatel equipment. Therefore any
Node B that is parented to an RNC in Hemel 1 will connect through this device.
Alcatel 1670 – this is an SDH ADM capable of interfaces up to STM-64 and as low as
STM-4. This is used in both the Hemel DCs to provide connectivity at STM-64
between sites. In Hemel 0 it connects to the 1641SX and in Hemel 1 it connects to
the Alcatel 1660s.
Alcatel 1660 – this is an SDH ADM capable of interfaces up to STM-16 and as low as
E1. This is used in Hemel 1 to connect to the RNC at E1 level.
This diagram shows a simplified version of the initial configuration of the Alcatel
network.
Figure 27 Alcatel Network Install
Page 46 of 79
NEC Circuiting Through a Nokia THS

Introduction
Within the Three RAN architecture there was a need to change the vendor responsible
for a certain geographical area (South Wales). The resulting design is that a number
of Nokia THSs with Nokia SAXCs are actually being used by NEC Node B sites.
However unlike standard Nokia THS sites the STM-1 cannot interface directly to the
NEC RNC. Therefore a second Nokia SAXC at the data centre is used to allow
connection to the NEC RNCs at E1 level. The basic architecture can be seen in
Figure 28 below.
DC
RNC
Node B THS
NEC Node B SAXC SAXC
E1 E1 Backbone Transmission E1
STM-1 STM-1
Network
Access Transmission
Network
Figure 28 NEC Node B connectivity through a Nokia THS
Physical Circuiting
To circuit an NEC Node B via a Nokia SAXC there are two layers of connectivity that
need to be modelled in Cramer. The first is the physical connectivity (E1) and the
second is the logical (ATM) connectivity. A detailed diagram of the connectivity at
both levels can be seen in the Appendix. This section looks at the physical
connectivity.
Apart from the actual node B itself the physical connectivity for each NEC site up to
the SAXC at the THS is exactly the same as for any normal Nokia THS circuiting.
(In some cases the microwave equipment may be NEC but this does not affect the
actual circuiting just the devices being used). Therefore each E1 requires a PDH
circuit to be modelled from an available SAXC port that terminates on the Node B.
The other physical connectivity required is in the datacentre from the SAXC to the
RNC at E1 level. For all E1s which terminate on the SAXC at the THS a new PDH
circuit must be created from the RNC to the datacentre SAXC. These circuits should
be created in the usual way using PDH bearers and cross-connects to provide the
connectivity.
It is important to note that before ATM was implemented in Cramer the only way to
tie these completely separate datacentre PDH circuits to their counterparts at the THS
was by using the same ports on both SAXCs. Therefore where possible the same
ports should continue to be used, but if they are not available it is of no great concern
because the circuits are tracked in Cramer and therefore the next available ports
should be used.
Once both ends of the physical circuits are in place the ATM circuiting can
commence.
Page 47 of 79
Logical Circuiting
The ATM connectivity for each NEC Node B using this transmission solution is
represented in Cramer using the same model as for Nokia Node Bs. That is the end to
end connection is limited to VP switching and therefore can be represented by end to
end VCs. In fact the only difference is that for NEC a VC must be created for each
E1 as there is no IMA capability. Each of the VCs created must also use specific VP
values at the Node B and RNC end. The following table details the required values.
VP value at Node B VP value between VP Value at RNC

SAXCs
1st E1 0 Any 0
2nd E1 1 Any 1
3rd E1 2 Any 2
The creation of these VCs is done using the ATM Router SDM and is described in the
Nokia THS section above.
NEC Datafill
For these special sites there are two types of datafill. The first is the standard datafill
which configures the RNC and is done in the usual way as described in procedures
above. The second datafill required is to enable the ATM configuration in both the
SAXCs. Currently this is performed by third line operations and can be arranged by
sending an email which includes the ATM reports for each of the VC circuits.
Page 48 of 79
NEC Circuiting to STM-1 Based eRNC

Introduction
In Q4 2004 Three introduced new STM-1 IuB capable NEC RNCs. To utilise the
new interfaces an ATM network was built, a simplified version can be seen in Figure
29.
Figure 29 General network architecture for NEC STM-1 RNC circuiting.
The new ATM network is required to allow the Node B to connect to the STM-1
interface on the RNC. The ATM network switches the traffic from each of the E1s
onto the STM-1 link to the RNC. Therefore the end to end connection can no longer
be represented at the E1 level and the ATM layers must be modelled.
Each E1 will contain a single ATM VP with multiple ATM VCs depending on the
type and configuration of the Node B. However although the ATM network will
perform VC switching it will not alter the VC values therefore Cramer will only be
used to track the VP layer. The result is that each E1 will require just a single end to
end VC. The actual VC numbers and bandwidths will be stored similarly to Nokia in
the NPS system. The basic ATM circuit layers for this scenario can be seen below in
Figure 30.
Figure 30 ATM Connectivity.
Physical Circuiting
This section looks at the physical connectivity from the Node B to the ATM platform.
Each Node B will need to have E1 circuits terminated on the ATM Network. These
E1s are circuited across the network in the usual way. However there are two areas
that may cause confusion and are now detailed in the following sections, the ATM
network device models and the transmission architecture.
Page 49 of 79
ATM Network Representation

This section was updated in version 3 due to a change in the way the ATM network
has been modelled.
There are two UK ATM networks currently represented in Cramer, one for IuR and
one for IuB connectivity. The networks are completely separate and made up from a
number of Nortel Passport devices. Each of the Passport devices are modelled in
Cramer and grouped together into their separate networks using the cloud structure.
Figure 31 ATM Network Representation
The two UK ATM clouds are ATM UK 01 and ATM UK 02 IuR. Performing a
network view on either cloud will show all of the devices that make up that network
and therefore all of the possibilities for connectivity. An example showing the current
devices in the IuB network cloud can be seen in Figure 32. For IuB connectivity there
are two types of Nortel Passport device used. The Nortel Passport 7480 is used to
connect to the transmission network with a structured STM-1 interface and the Nortel
Passport 2000 which is used to connect to the RNCs with an unstructured STM-1
interface.
Figure 32 Example Network View of the IuB ATM Network
Page 50 of 79
The structured STM-1 interface on the Nortel Passport 7480 needs to be represented
in Cramer, however it cannot support such a port type and its associated circuit
hierarchy. It does not allow a HOT, LOT, LOP and a PDH E1 circuit to terminate
onto the same STM-1 port. Therefore a new structured STM-1 card was created to
overcome the limitations. The new card has a number of extra ports and links to
terminate each of the circuit layers on. An example of the new structured STM-1 card
can be seen in Figure 33.
Copper Link
111 LOP 111 PDH
Copper Link
112 LOP 112 PDH
STM-1 Copper Link
113 LOP 113 PDH
Copper Link
121 LOP 121 PDH
Copper Link
373 LOP 373 PDH
Sub Card
Sub Slot 0
Sub Slot 1
Card
Figure 33 Structured ATM-1 card for the Nortel Passport 7480
The diagram shows the structured card with it’s extra LOP and PDH ports which are
used to terminate the different circuit hierarchy layers. The rule when circuiting
using this model is that the LOP and PDH circuits should be terminated on the
corresponding ports to match the VC-12 timeslot utilised by the circuits on the
incoming HOT. A detailed example of the circuit hierarchy using this device can be
seen in the appendix.
Transmission Architecture
To connect to the ATM network we need to understand where it is located in each DC.
This section highlights the current installs in Hemel 1 and Birmingham.
In Birmingham all E1s are now delivered through a Nortel OME6500 cross-connect.
All of the OME6500s are connected to the ATM platform using 3 Nortel 4200s
(A16_006, A16_007 and A16_008). Between the 4200s & 4100s and the 6500s there
are numerous HOTs which can be used on a first come first served basis. A
simplified version can be seen in Figure 34, which also highlights the pre-built VC-4
HOT connectivity in Cramer.
Page 51 of 79
Figure 34 Birmingham ATM Network
In Hemel 1 DC the route to the ATM platform is via Alcatel 1660s. Therefore the
circuiting is almost identical to normal E1 circuiting except the final hop is not a PDH
bearer to the RNC but an SDH hop to the ATM network. A simplified version can be
seen in Figure 35, which also highlights the VC-4 HOT connectivity that will be pre-
built in Cramer.
Figure 35 Hemel ATM Network
Logical Circuiting
Before discussing NEC specific logical circuiting we need to consider a few general
points on the ATM network. As mentioned previously, in the same ATM network
any port on any Passport device can be connected to any port on any other Passport
device.1 In the real world this connectivity is provided by an ATM mesh between the
devices. The routing across this mesh is decided upon by the ATM routing protocol
PNNI. Therefore it becomes unnecessary to track the true connectivity between the
Passport devices in Cramer. However Cramer will not resolve an end to end circuit
unless there is a complete underlying path. Therefore a new circuit type, an ATM
Tunnel, is being utilised between the Passport devices to resolve the overlying ATM
circuitry. The impact of this on circuiting is minimal because the ATM Tunnel is
created automatically by the ATM router tool, however on modification it needs to be
1
The connectivity between Birmingham and Hemel DCs will not be in place until April 2005
Page 52 of 79
considered. An example of the ATM hierarchy across the Nortel Passport ATM
network can be seen in Figure 36.
ATM VC
ATM VP ATM Tunnel ATM VP
ATM Bearer ATM Bearer
PDH CCT
SDH LOP
SDH LOT
PDH
PDH Bearer SDH HOT Bearer SDH HOT
E1 STM-1 STM-1 (Unstructured)

Transmission ATM ATM
Node B Network Node Node RNC
Figure 36 ATM Circuit Hierarchy for Nortel Passport ATM Network
NEC Logical Circuiting

As discussed previously each E1 requires a single end to end VC. The creation of
each VC is done using the ATM router and therefore the majority of the required
information can be taken from the Nokia THS section. However there are a number
of differences and rules that must be followed when using the ATM router for NEC
node Bs.
1. The correct number of ATM hops will be 2, the first from the Node B to the
ATM platform and the second from the ATM platform to the RNC. The only
exception will be in South Wales were SAXCs are also used (see South Wales
Section).
2. VP numbering, the first E1 should have a VC using VP 0, the second E1

should have a VC using VP 1 and the third E1 should have a VC using VP 2.
These VP values should be followed at the Node B end only.
3. VC attributes, the ‘Full Name’ attribute of each VC circuit should be used to

store a VPCI reference. This will need to be filled in manually on the circuits
homepage by the regional planner. The first E1 should have a VPCI of 0, the
second E1 should have a VPCI of 2 and the third E1 should have a VPCI value
of 4. The format of the ‘Full Name’ attribute should be:
VPCI$
Where $ = the required value.
4. Maximum VPs per RNC STM-1 interface. There is a limitation on the STM-1
interface on the RNC that only 64 E1s and therefore VPs can be used.
This is not enforced by Cramer and therefore the Regional Planner has
responsibility to ensure the limits are not exceeded.
Page 53 of 79
5. Maximum VPs per Structured STM-1 interface on the ATM platform. There
is a limitation on the structured STM-1 interface that only 57 E1s and
therefore VPs can be used.
This is not enforced by Cramer and therefore the Regional Planner has
responsibility to ensure the limits are not exceeded.
6. The ATM router will not propose values for IMA groups or ATM if Ids
because these values are not required for NEC STM-1 circuiting.
The following table summarises the VC configuration required.
Node Port VP at Node B VC ‘Full Name’ attribute

0 0 VPCI0
2 1 VPCI2
4 2 VPCI4
Figure 37 NEC Node B VC requirements for STM-1 RNC
NEC STM-1 Datafill

Each NEC node B will require two types of datafill, one for the RNC and one for the
ATM network configuration. The RNC datafill will automatically be taken by NPS
and relies on the parameters entered above. The ATM network datafill is simply the
‘ATM report for Node’ as described in the Nokia datafill section above.
Birmingham OME6500 Circuiting

In March 2005 three Nortel OME6500 cross-connects were ‘cut in’ to the network in
Birmingham. Almost all circuits now transit through these 6500s. These devices
provide considerable network flexibility and allow for ‘soft reparenting’ in most
cases2. This implies that no physical work needs to be done in the data centres to
move circuits around the network. The basic scenario was shown in Figure 34 above.
The impact is that all new circuiting in Birmingham now requires to be completed
over multiple HOTs. Therefore each LOP will require multiple LOT one over each
HOT in the route. From the OLO device to the OME6500 the HOT which represents
the OLOs network must still be circuited over using the correct KLM as supplied with
the circuiting details. However from the OME6500 to the 4100s or 4200s (then onto
the ATM) the HOTs should be circuited on a first come first served basis.
Examples of both types of circuits are given on a quick reference sheet in the
appendix.
2
The main exception is reparenting between E1 RNC, where jumpers will either be moved or re-
provided.
Page 54 of 79
Node B Reparenting
This section deals with the technical issues of reparenting Node Bs in Cramer. It is
not intended that the section will detail the processes and procedures of actually
cutting over a live Node B in the network. Those procedures are owned locally in
each region with their local operations representatives.
There are two types of reparenting that will be discussed in this section; E1
reparenting and ATM reparenting. E1 reparenting means that the physical route of an
E1 is going to be changed somewhere. For example a DDF change may occur to
move the E1 to a new RNC in the same DC, or a backbone provisioning change may
occur to send the circuit to a new RNC in a new DC. ATM reparenting is where the
Node B is already connected to the Nortel ATM platform and the new RNC is also
connected to the platform. Therefore the only change in the end to end circuit will be
at the ATM layer.
For both types of reparenting it will be impossible to describe every scenario therefore
a selection of the most common have been described. However the basic principles
can be applied to any scenario.
E1 Reparenting
To assist with changing an E1 route across the network there is a rerouting tool in
Cramer. The rerouting tool enables a user to show a current route and a planned route
for the same circuit across the network. The complete routes are shown in a rerouting
AVM, which is essentially a technical routing AVM of the first route, a list of
changes and a technical routing AVM of the new route. An important point to note is
that both routes do not really exist in full in Cramer, only the current route will be
complete. In the majority of cases there will be network resources that need to be
shared on both the new and old route. To stop double allocation Cramer will not allow
this hence the development of the rerouting tool.
Cramer Rerouting SDM

The rerouting tool has been developed as an SDM and is found in the circuit wizards
menu as ‘Reroute Circuit’. To use the rerouting SDM a second circuit called a
rerouting circuit must be created. This rerouting circuit is an end to end circuit but it
is only resolved over the underlying resources that are in the new route. The rerouting
SDM is used to effectively swap the shared resources from the current circuit to the
new circuit. The rerouting SDM requires a number of questions to be answered
including how many divergence points there are and of what type. A divergence
point is defined as a point where the new and old circuit join/separate, and the type
relates to what device or circuit it occurs on.
This section now details 4 of the main E1 reparenting scenarios and highlights the
rerouting circuits that need to be created, how many divergence points and their types
as required by the rerouting SDM. The actual process of using the rerouting SDM
will be highlighted later.
Page 55 of 79
Scenario 1: RNC reparenting on the DDF

This scenario refers to a Node B being reparented from one RNC E1 port to another in
the same DC. The backbone transmission route remains the same and the change
occurs by moving a jumper cable on the DDF.
Figure 38 below shows a simplified network diagram with the required circuit
hierarchy.
Figure 38 Rerouting at the DDF
The red circuits in the diagram show the current end-end E1 circuit and all its
underlying hierarchy. The blue circuits show the new rerouting circuit that needs to
be created for the rerouting SDM. The new PDH bearer is used to reserve the RNC
port and link. The new PDH circuit starts on the new RNC port, utilises the new PDH
bearer and connects to the existing Node B port. It is clear form the diagram that in
such a scenario there will only be one divergence point and that will be of type cross-
connect on the DDF. It should be noted that the new PDH circuit will be unresolved
because it cannot share the implemented route of the original PDH circuit.
Scenario 2: RNC reparenting from Hemel 0 to Hemel 1

When a Node B is to be circuited to Hemel 1 the Alcatel transmission network
between Hemel 0 and 1 must be used. Therefore this is also the case if a site is being
reparented from an RNC in Hemel 0 to Hemel 1. Figure 39 below show a simplified
representation of this scenario.
Page 56 of 79
Rerouting HOT
Rerouting LOT
Rerouting LOP
Figure 39 Rerouting from Hemel 0 to Hemel 1
Again the red circuits in the diagram show the existing circuit hierarchy and the blue
circuits show what needs to be created to reserve all the capacity to the new RNC.
The LOTs and PDH bearer are created as normal. The LOP is created from the
corresponding trib port on the Alcatel 1660 to the last SDH device in the overlying
circuit. The last SDH device is likely to be either an OLO device or a Nortel TN1X at
a THS. The LOP will be unresolved from the Nortel 4100 to the last SDH device and
will have an unspecified port at the Node B end. This is because the required port is
in use by the original LOP circuit. The PDH circuit will run from the RNC to the
Node B and must terminate on the correct port as the original circuit, again this will
be unresolved.
For this scenario the device where the old and new route meet is the Nortel 4100,
therefore this will be the divergence point. Because the original LOP has a LOT that
will be used in the new route the divergence type will be an SDH Node (Persistent
LOT).
Scenario 3: RNC reparenting from Hemel 0 to Hemel 1 eRNC

This scenario is very similar to scenario 2. However it assumes that a new eRNC
with an STM-1 interface is the new parent RNC. Therefore instead of circuiting the
new E1to the new RNC it has to go to the ATM network device. It is important to
note that because of the target eRNC, ATM circuits must be created for the Node
B. These should be created using the ATM router in the normal way over the
rerouting circuit. The rerouting SDM will not affect the ATM circuits. Figure 40
below shows the basic scenario with both the new and old circuits required.
Page 57 of 79
Original PDH Circuit
Original LOP
Original LOT
Original PDH Bearer Original HOT Original PDH Bearer
E1
Node Transmission
B Nortel D D
D D RNC
4100
F F
Rerouting HOT
Rerouting LOT
LOP path
unresolved
Alcatel Alcatel
Rerouting LOP
ATM
1641SX 1660
PDH Circuit
unresolved Z-end
unresolved on
last SDH Rerouting
device in TX PDH Bearer
Rerouting HOT Rerouting HOT
(OLO)
Rerouting LOT Rerouting LOT
Rerouting PDH Circuit
Figure 40 Rerouting from Hemel 0 to Hemel 1 eRNC

From the diagram it is clear to see the divergence point will again be the Nortel 4100
and the type will again be an SDH Node (Persistent LOT).
Scenario 4: RNC reparenting from Birmingham to Elmdon eRNC

This scenario highlights what is required when a Node B is to be reparented from a
Birmingham E1 RNC port to an STM-1 based eRNC in Elmdon. This is fairly similar
to scenario 3 in that the E1 must be circuited to the ATM network and ATM circuits
will be required on the rerouting circuits. Figure 41 below shows the basic scenario.
Page 58 of 79
Original PDH Circuit
Original LOP
Original LOT Original LOT
Original PDH Bearer Original HOT Original HOT Original PDH Bearer
E1
Node Transmission D D
B Nortel RNC
Nortel 4100 D D
OME6500
F F
LOP path
unresolved
Nortel 4200 ATM
PDH Circuit
unresolved Z-end
unresolved on
last SDH Rerouting
device in TX PDH Bearer
Rerouting HOT
(OLO)
Rerouting LOT
Rerouting PDH Circuit
Figure 41 Node B reparenting from Birmingham to Elmdon eRNC

In this case the diagram clearly shows the divergence point will be the OME6500 and
because of the existing LOTs out to the transmission network it will be again of type
SDH Node (Persistent LOT).
Rerouting SDM Use

This section provides a step by step example with screen shots of an E1 reparent using
the rerouting SDM. It should be noted that as with all Cramer circuiting there are
many ways to achieve the same objective. Therefore some steps and screenshots may
be slightly different or not relevant depending on the users.
In the example Site SG0065 is being reparented from HH0RNC54 to HH1RNC68

which means the E1s must be reparented onto the ATM platform. (Please note this
example was done with the old ATM device model but this does not affect the
circuiting in anyway.)
Step 1: Create a rerouting circuit from the ATM platform to the Node B. The first
screenshot shows the 2 E1s for the site and a rerouting circuit (A025659) for the first
E1. Note that the rerouting circuit is un-resolved.
Page 59 of 79
This second screenshot shows how the rerouting circuit runs over a PDH bearer and
an LOP. An important point to note is that the LOP does not have a specified port,
seen by the lack of a black dot at the end of the circuit.
This third screenshot of the LOP again shows again how there is no specified end port
and that the circuit is unresolved from HEM_A04_005 to the TN1X at THS SG0047.
Step 2: Run the rerouting SDM , which is under the Circuits wizard as Reroute Circuit.
Page 60 of 79
Step 3: The first step in the SDM process is to select the circuit being rerouted
(A020836).
Step 4: The next step asks for the number of divergence points. As mentioned before
that is the number of times the original circuit and new circuit separate or join
together. For all reparenting this will be 1, but if a transmission solution was
changing i.e. leased line to microwave and the same RNC port was to be used there
could potentially be 2. In this example, which is the same as in the example above in
Figure 40 it is 1.
Page 61 of 79
Step 5: The next step in the process is to decide what the divergence type is. In this
case because the device where both routes meet is a Nortel 4100 it is an SDH Node
(Persistent LOT).
Step 6: Once the divergence type has been decided the actual point of divergence must
be selected. This is easiest by drilling down in the circuit view of the original PDH
circuit.
Page 62 of 79
Step 7: The next steps are generated based on the type of divergence point selected.
Each type will ask slightly different questions but they are all fairly self explanatory.
In this case it is asking for the persistent LOT which is the one that appears in both
routes and in this case goes from the Nortel 4100 to the TN1X at the THS. This can
be found by drilling down another layer on the LOP in the circuit view.
Step 8: Once all the details have been entered for the circuit to be rerouted the SDM
asks for the rerouting circuit to be selected. The rerouting circuit can be found from
the circuit view of the Node B.
Page 63 of 79
Step 9: The next step in the SDM is to create the rerouting report. This will send a
rerouting report to the user which shows a technical routing AVM of the old route and
the new route. It will also automatically rename the rerouting circuit.
Step 10: The renamed rerouting circuit can be seen here with the next option to actual
perform the cutover. This is intended to be the stage at which the rerouting report
should be sent to operations to perform the cutover. Once the cutover has been
confirmed the SDM can be re-run and progressed to cut over the circuit.
Page 64 of 79
Step 11: To re-run the SDM, relation the rerouting circuit and find the rerouting project
in the projects tab. From the wizards menu select SDM, Process Design Project, and
then insert the project in to the wizard to start it again.
Step 12: Process the cutover and once completed the SDM can be exited and the circuit
view refreshed. As can be seen below the circuits have been clearly swapped with the
old route now unresolved and labelled with Ready for Decommissioned. This
reference can the be used by operations to remove any remaining jumpers or
provisioning,
Step 13: Drilling down in the Ready for Decommissioned circuit view will show what
needs to be removed from the network, which once completed can then be deleted
from Cramer.
Page 65 of 79
ATM Reparenting
This sections looks at the requirements for reparenting a Node B from one NEC
eRNC to another NEC eRNC. Because both RNCs require the Node B to be
connected to the ATM platform there is no need to move the physical circuiting.
What is required is to plan the new ATM route, arrange for the cutover and then
remove the old ATM route. The following Figure 42 shows a basic example of the
required circuits to reroute a single E1 Node B.
Figure 42 ATM Rerouting eRNC

The diagram shows the Node B connected to the ATM platform with an existing VC
circuit (Y000011OLD in Blue) connecting it to RNC 1. A second new route is shown
to RNC 2 (Y000011 in Red). This new VC is created across the same VP from the
ATM platform to the Node. Due to the nature of ATM and Cramer this can be done
using the ATM router in the normal way. The only slight exception or important
point to remember, is to select the same VP on the first hop and not the HOT or ATM
Bearer. If the HOT or ATM Bearer is selected then the ATM router will create a new
VP which will not have the correct value for the Node B. The final step before cut
over is to rename the new VC and the old VC as shown in the diagram here. This will
enable operations to easily identify which is the new route when performing the
network change. Once the cutover has occurred in the Network the old VC can then
be deleted from Cramer.
NEC South Wales ATM Reparenting

Due to the network architecture in South Wales there is a slightly more complicated
circuiting process to reparent a Node B. A detailed diagram has been included in the
Appendix which should be used as an aide to follow these steps:
1. Reroute only the E1s from the DC SAXC to the RNC on to the ATM platform.
This will require using a spare trib port on any 4100 in the correct side of the
DC.
2. Create new ATM circuits to the new RNC using the same VPs as the original
route up to the SAXC in the DC and then the new rerouting circuit.
Page 66 of 79
Appendix
This appendix contains the following quick reference guides:
• Nokia UTRAN
• NEC UTRAN
• NEC THS Circuiting
• Leased Bandwidth Circuiting (BT)
• Data Centre Circuiting
• Alcatel Circuiting
• Nokia ATM Circuiting
• NEC Circuiting via a Nokia THS
• NEC STM-1 RNC Circuiting
• OME 6500 Circuiting
• NEC South Wales ATM Reparenting
• JKLM Chart
Page 67 of 79
Nokia UTRAN
Page 68 of 79
NEC UTRAN
Direct Connection Node B Site

Node B Terminal
Site
THS site Node B Intermediate Node B Terminal Site
Site
Pasolink NODE B
E1
NTE - Pasolink Pasolink Pasolink Pasolink
E1 E1
E1
Backbone Node Site E1 E1 E1
E1 E1
Fibre Nodal Site
NODE B
STM-1 NORTEL
BT Netstream 16 MUX DDF DDF
DDF
LEASED LINE SMA 4 E1 NODE B NODE B
Pasolink MSH5 NODE B
BT Netstream 16
1C
LEASED LINE
E1 STM-1
E1 ODF
NODE B Infrared
NTE -
STM-1
Backbone Node Site

ADM
OM 4200
MSH5
1C
STM-4 WOC
WOC
Pasolink
STM-16
ODF E1
E1 THS site
Node B Terminal Site
NODE B Pasolink Pasolink
VC-4 VC-4 NODE B
Pasolink
RING ADM RING ADM

DX3
E1
DX3 E1 E1
Node B Terminal Intermediate Site E1
STM-64
Site NORTEL
DDF DDF
STM-1 MUX
SMA 4 E1 NODE B NODE B
BT Netstream 16
LEASED LINE
STM-64
STM-64
Data Centre
Backbone Node Site

Node B Terminal MSH5 Node B Terminal Site
1C
Site Backbone Team
STM-4 Pasolink
VC-4 STM-64 Pasolink
Pasolink
ODF
Field Operations
RING ADM RING ADM E1 E1
E1 DX3 DX3 STM-4
Nortel Responsibility
ADM NODE B
NODE B Fibre Nodal Site OM 4100 OLO Leased Bandwidth
Suppliers Responsibility
Pasolink STM-4
STM-4 E1 NEC's Responsibility
E1 ADM
(Backbone Provisioning)
NODE B OM 4100 E1
NTE - E1 E1 Plan - National Circuiting Team
E1 ADM
Impliment - Ops
OM 4100 E1 This diagram is
significantly out of
BT Netstream 16
DDF
DDF DDF RNC date and only left in to NEC Access Network Circuiting
Direct Connection Node B Site
LEASED LINE
MSH5 ADM
E1 highlight typical (BT leased line example)
1C ODF OM 4100 examples. It is in the Owner: National Circuiting Team
E1 STM-4
STM-4 process of being
Author: Andy Broadbent
NODE B
revised.
E1 Status: Issue 7
NTE -
Date: 14/1/2003
Page 69 of 79
NEC THS Circuiting
Data Centre
RNC
DDF DDF Nortel TN1 -X DDF DDF

Leased Bandwidth Node B Nortel OM 4100
PDH Circuit E1
Node B
SDH Low Order Path
STM- STM-
E1 E1
1 4
TRIB TRIB
AGG SDH Low Order Trail AGG PDH Bearer
PDH Bearer Jumper FIXED CABLING
SDH High Order Trail FIXED CABLING (Cross- (LINKS)
FIXED CABLING
(LINKS) Connect)
Jumper (LINKS)
FIXED CABLING
(Cross-
(LINKS)
Connect)
THE LOT SHOULD BE CREATED IN

WHEN EXTENDING THE PDH THE TIMESLOT ON THE HOT THAT
BEARER USE THE NEXT MATCHES THE TRIB PORT USED
AVAILABLE FREE PORT ON ON THE TN1-X (i.e. if trib port 16 is
used the timeslot 16 should eb used on
B END of Circuiting TN1-X
the HOT)
A END of Circuiting
All 'dashed line' circuits within this diagram need to be built by

the circuiting engineer.
Circuiting THS - NEC
Owner: National Circuiting Team
Status: Draft 1
Date: 5/8/2003
Page 70 of 79
Leased Bandwidth Circuiting
Nominal Site ID Site ID Text25 CCT No. MXGB No A End SNEID A End TRIB A End JKLM B End SNEID B End TRIB/PORT MXLL No
EN0010 201030 South 1 MXGB247308 70275 1 1123 89108 T1 MXLL150302
THE KLM IDENTIFIES WHICH

A END SNEID WILL MATCH
TIMESLOT IN THE HOT THAT
THE CRAMER SNEID
THE LOT MUST BE BUILT
A END TRIB IDENTIFIES THE
Data Centre
STM-4 PORT WHERE THE
HOT LEAVES THE CRAMER THE J IDENTIFIES WHICH
OLO DEVICE HOTWITHIN THE TRIB
SHOULD BE USED RNC
Backbone PoP or Data Centre

DDF DDF
Nortel OM 4100
PDH Circuit E1
BT SNEID (MSH51c)
SDH Low Order Path

STM-
E1
4
SDH Low Order Trail TRIB
Leased Bandwidth Node B
AGG PDH Bearer
Jumper FIXED CABLING
SDH High Order Trail FIXED CABLING (Cross- (LINKS)
(LINKS) Connect)
Node B
Node B NTE Cards
N N N N N N N N N N
T T T T T T T T T T
PDH Bearer E E E E E E E E E E
THE MXLL IDENTIFIES THE

N N N N N N N N N N HOT AND IS STORED IN THE
T T T T T T T T T T
E E E E E E E E E E
'ALIAS 2' FIELD OF THE HOT
THE B END TRIB IDENTIFIES

B END of Circuiting THE PORT THAT SHOULD BE A END of Circuiting
USED ON THE NODE B NTE
CARD
THE MXGB SHOULD BE USED THE B END SNEID SHOULD
AS THE NAME OF THE LINK BE USED AS THE NAME OF
FROM THE NODE B TO THE THE NODE B NTE CARD
OLO DEVICE
Nominal Site ID Site ID Text25 CCT No. MXGB No A End SNEID A End TRIB A End JKLM B End SNEID B End TRIB/PORT MXLL No
EN0010 201030 South 1 MXGB247308 70275 1 1123 89108 T1 MXLL150302
Circuiting BT leased line
All 'dashed line' circuits within this diagram need to be built by Author: Andy Broadbent
the circuiting engineer. Status: Draft 1
Date: 5/8/2003
Page 71 of 79
Data Centre Circuiting
Data Centre
OLO Room Main Room

RNCs
Central DDF East
OLO DDF Jumper
TIE PAIRS (LINKS)
(Cross-Connect)
FIXED CABLING
OLO E1
(LINKS)
Delivery Mux OLO PATCH
(LINK)
Jumper
Jumper (Cross-Connect)
(Cross-Connect)
FIXED CABLING
(LINKS)
T
A
R
G
I
G
B
Nortel
Transmission
Jumpering Rules:
1. You can only jumper between DDFs if they are in the

same suite line. (i.e. you can jumper between BIR_1/K/ TIE PAIRS (LINKS)
1E_DDF and BIR_1/K/3E_DDF)
East
2. You must use a tie pair if you are trying to connect
between DDFs not in the same suite line. (i.e. if you were
connecting between BIR_1/K/1E_DDF and BIR_1/J/ West
7W_DDF you would need to use a tie pair which goes
between the K/E and J/W suite lines)
3. When using a tie pair you have to jumper from the

equipment termination port to the tie port at both ends of
the tie pair (except in the OLO room). Jumper
(Cross-Connect)
4. When an E1 is delivered from an OLO a patch (link)
must be created between the OLO delivery port and the FIXED CABLING T
A
(LINKS) R
port of a tie pair that connects to the required suite line in I
G
G
the main DC room. B
Nortel
Transmission
Central DDF West
Data Centre Circuiting
All 'dashed line' circuits within this diagram need to be built by Author: Andy Broadbent
the circuiting engineer. Status: Draft 1
Date: 5/8/2003
Page 72 of 79
The LOPs should be created to the 1660 trib

that corresponds to the required RNC port as
all available PDH bearers are already created
Alcatel Circuiting between the 1660 and the RNC.
The LOP should run over all SDH LOTs

which can include those on the Nortel
Network or the BT network.
All PDH bearers are
created in advance
SDH Low Order Trail - 'T' reference
PDH Bearer - 'P' reference
Agg 21 Port
SDH High Order Trail - 'B' reference

63 Port
Card E1 Card E1 Card
PDH Circuit Extended to Hemel 2 RNC - 'A' reference
STM-4 E1 E1
Alcatel 1670 E1
Physical DDF
SDH Low Order Path Extends to 1660 Trib card - 'L' reference DDF DDF RNC
Link
Alcatel 1660
SDH Low Order Trail - 'T' reference SDH Low Order Trail - 'T' reference
STM-64 Hemel 1 DC
SLOT SLOT
SDH High Order Trail - 'B' reference 6 14
STM-4 STM-1
AGG TRIB
SDH High Order Trail
STM-4 - 'B' reference
Node B STM-16
Transmission Network ADM OM 4100
STM -1 Alcatel 1641SX
Alcatel 1670
Hemel 0 DC
When connecting via the Nortel
network to the Alcatel 1641sx it may
not always be via the agregate cards The LOTs should be created in
and could be via a PDH interface from the next available timeslot on
the DSX. each HOT. The HOTs should be
selected to ensure they attach to
the correct 1660s for the required
RNCs
Alcatel Circuiting
the circuiting engineer. Owner: National Circuiting Team
Status: Issue 1
Date: 14/11/2003
Page 73 of 79
ATM Circuiting
How do I know how many ATM hops and which circuits to use when creating ATM circuits?
Data Centre
THS or Data Centre
RNC
ATM Virtual Circuit Y Refernce (3 HOPS)
Node B SAXC - AXC1 SAXC - AXC2
ATM HOP ATM HOP ATM HOP

E1 STM-1 STM-1
Port Port Port
PDH Circuit STM-1 SDH STM-1 SDH
Port High Order Trail Port High Order Trail
THS or Data Centre Data Centre

RNC
ATM Virtual Circuit Y Refernce (2 HOPS)
Node B SAXC - AXC2
ATM HOP E1 ATM HOP

Port STM-1
Port
PDH Circuit STM-1 SDH
Port High Order Trail
Data Centre
THS
RNC
ATM Virtual Circuit Y Refernce (5 HOPS as shown)
Node B SAXC - AXC1 SAXC - AXC2 SAXC - AXC1 SAXC - AXC2
ATM HOP E1 ATM HOP ATM HOP ATM HOP ATM HOP E1
STM-1 STM-1 STM-1
Port Port
Port Port Port
PDH Circuit STM-1 SDH STM-1 SDH STM-1 SDH E1
PDH Circuit
Port High Order Trail Port High Order Trail Port High Order Trail Port
B END of Circuiting The number of HOPS in this scenario may vary depending on which AXCs are used in each SAXC
A END of Circuiting
ATM Circuiting
All 'dashed line' circuits within this diagram need to be built by the circuiting engineer. This Author: Andy Broadbent
is done using the 'ATM Routing SDM' by selecting all the underling circuits (PDH Circuits
Status: Draft 1
(possibly multiples with IMA) and SDH High Order Trails).
Date: 6/8/2003
Page 74 of 79
Page 75 of 79
NEC STM-1 ATM Circuiting Version 2: New ATM Tunnel Model

The two ATM bearers
imply this would be a two
hop ATM route
ATM VC
ATM VP ATM VP
ATM Tunnel
PDH Circuit
SDH LOP The ATM Tunnel is

automatically created by
Cramer when using the ATM
SDH LOT router. The ATM Tunnel is
not counted as an ATM HOP.
SDH HOT PDH Bearer SDH HOT
PDH Bearer
Copper Link 0
Transmission 111 LOP 111 PDH
STM-1
STM-1 RNC
Node E1 Network STM-1
Copper Link
1
112 LOP 112 PDH
B STM-1 Copper Link
113 LOP 113 PDH
Copper Link 2
The SDH LOT should 121 LOP 121 PDH
terminate on the 3
STM-1 port
The PDH circuit shout
Copper Link
The transmission network terminate on the PDH
373 LOP 373 PDH
may be much more port that matches the
complicated than a the KLM on the HOT. The
B END of Circuiting normal E1 RNC circuiting PDH Bearer and links will A END of Circuiting
however all VC-4s will be pre Sub Slot
xN be created between LOP xN
built. and PDH ports
The LOP circuit

should terminate
on the LOP port
that matches the
KLM on the HOT
15
Sub Slot Card

Card
Slot
Slot
Passport 7K Passport 20K

NEC STM-1 ATM Circuiting

All 'dashed line' circuits within this diagram need to be built by the regional planning engineer.
The ATM device has now been broken down into its discrete network elements. The internal
connectivity within the ATM network is now represented by automatically created ATM tunnels. Status: Issue 2
The impact for the user is only that they must now select the correct Nortel Passport device in Date: 12/01/2005
Cramer instead of a generic ATM node. All devices are listed under Nortel Passport.
Page 76 of 79
E1 circuitng through the new Birmingham OME6500
New e RNC via ATM network
PDH Circuit
LOP
LOT LOT LOT
PDH Bearer HOT HOT HOT PDH Bearer
Nortel
Node B OLO Nortel 4200 Nortel ATM
OME6500
Original E1 based RNCs
PDH Circuit
LOP
LOT LOT
PDH Bearer HOT HOT PDH Bearer
Nortel Nortel
Node B OLO RNC
OME6500 OM4100
B END of Circuiting A END of Circuiting
OME Circuiting
the circuiting engineer.
Status: Issue 1
Date: 07/03/2005
Page 77 of 79
Y009999 OLD
VP VP VP
ATM Bearer ATM Bearer ATM Bearer
PDH Circuit Original PDH Circuit (To be rerouted)
PDH Bearer SDH HOT Original PDH Bearer
NEC E1 STM-1 STM-1 E1 E1

Port THS Port Port DC Port Port
Node Jumper
SAXC SAXC BM0RNC
B DDF
(Cross- DDF
Connect)
VC is resolved over original

VPs up to DC SAXC
E1 Nortel Nortel
Port
Nortel Nortel BM1RNC
DDF OME6500 Passport Passport
4100 4200
7480 20000
New PDH Bearer SDH HOT SDH HOT SDH HOT PDH Bearer SDH HOT
SDH LOT SDH LOT SDH LOT
SDH LOP
New PDH Circuit (Rerouting Circuit)

B END of Circuiting
VP VP
Y009999
A END of Circuiting
Red circuits represent original ATM circuits and associated hierarchy including the E1 circuit that needs to be rerouted.
Blue circuits show the new ATM route and the new rerouting circuit from the SAXC to the ATM platform.
This example shows 4 ATM hops for the new ATM route, but please note it could be more if different sides of the SAXCs
at the THS or DC were used.
Status: Draft 1
Date: 11/3/2005
Page 78 of 79
KLM Conversion Chart:

VC 12 Allocation K L M
1 1 1 1
2 1 1 2
3 1 1 3
4 1 2 1
5 1 2 2
6 1 2 3
7 1 3 1
8 1 3 2
9 1 3 3
10 1 4 1
11 1 4 2
12 1 4 3
13 1 5 1
14 1 5 2
15 1 5 3
16 1 6 1
17 1 6 2
18 1 6 3
19 1 7 1
20 1 7 2
21 1 7 3
22 2 1 1
23 2 1 2
24 2 1 3
25 2 2 1
26 2 2 2
27 2 2 3
28 2 3 1
29 2 3 2
30 2 3 3
31 2 4 1
32 2 4 2
33 2 4 3
34 2 5 1
35 2 5 2
36 2 5 3
37 2 6 1
38 2 6 2
39 2 6 3
40 2 7 1
41 2 7 2
42 2 7 3
43 3 1 1
44 3 1 2
45 3 1 3
46 3 2 1
47 3 2 2
48 3 2 3
49 3 3 1
50 3 3 2
51 3 3 3
52 3 4 1
53 3 4 2
54 3 4 3
55 3 5 1
56 3 5 2
57 3 5 3
58 3 6 1
59 3 6 2
60 3 6 3
61 3 7 1
62 3 7 2
63 3 7 3
Page 79 of 79

Circuiting Guidelines Issue 3 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Circuiting Guidelines Issue 3 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

National Circuiting Team Guidelines – Issue 3

National Circuiting Team Guidelines

ATM Reparenting ....................................................................................................66

UTRAN Network Overview

• The first level of connectivity is at the physical layer, which is provided by

Figure 1 Three UK UTRAN Network

The Basic Rules of Cramer Circuiting

Node B site naming conventions will be of the form;

Where XXXXXX= the Net One Nominal ID

THS site naming conventions will use the form;

Where XXXXXX = the Net One Nominal ID.

Leased Line Links Statuses

1. OLO link awaiting completion (delivery):

2. OLO link delivered but not in use:

3. OLO link delivered and in use:

4. OLO link awaiting Cease or Cancellation:

Regional Regional Cancel

PDH Circuit Hierarchy

PDH Circuit = Axxxxxx

PDH Bearer = Pxxxxxx

PDH Copper Link PDH

Figure 3 Cramer PDH Circuit Hierarchy

SDH Circuit Hierarchy

Low Order Path = Lxxxxxx

Low Order Trail = Txxxxxx

High Order Trail = Bxxxxxx

MS Bearer = ‘Bandwidth Prefix’xxxxxx

SDH Fibre Link SDH

Figure 4 Cramer SDH Hierarchy

Microwave Circuit Hierarchy

Figure 5 Cramer PDH Microwave Hierarchy

Leased Bandwidth Circuit Hierarchy

Leased Line Link = ‘OLO Reference’ OLO

Figure 6 Cramer Leased Bandwidth Circuit Hierarchy.

ATM Circuit Hierarchy

ATM Bearer = Wxxxxxx

Optional PDH IMA Parallel Circuit = PIMACxxxxxx

ATM SDH or PDH Circuit ATM

Figure 7 Cramer ATM Hierarchy for VP Switching.

Nokia THS Circuiting Guidelines

ATM Cramer Model

ATM VP ATM VP ATM VP

ATM Bearer ATM Bearer ATM Bearer

PDH IMA Parallel Circuit

Figure 8 Example ATM Circuit Hierarchy through THS

ATM Router Use

IMPORTANT NOTE: The number of ATM HOPS must carefully be calculated.

Modifications to ATM circuits

Additional E1s to IMA Circuits

Changing ATM if Id Values

Changing IMA group Values

Modifying a Circuits Route

Nokia THS Datafill

ATM Report AVM for Node

ATM Bearer Bandwidth : 2*E1

This Report is created by: abroadbent

NEC THS Circuiting Guidelines

• Circuit(s) will be “Resolved”

Figure 10 PDH Bearer extension - create crossconnect

LOT (Low Order Trail) Creation

Figure 11 Circuit view of LOT

LOP (Low Order Path) Creation

Figure 12 The LOT is inserted into the LOP