Post on 19-Jan-2016
description
1 © Nokia Siemens Networks Presentation / Author / DateFor internal use
Changing WCEL UARFCN in WCDMA with Configurator toolsLeena Rasinaho
12 September 2012
2 © Nokia Siemens Networks Presentation / Author / DateFor internal use
About UARFCN 1/2
• WCEL UARFCN description: Parameter UARFCN defines the DL channel number and the DL carrier frequency of the cell.
RNC calculates the UL carrier frequency and the UL channel number from the DL carrier frequency and a duplex distance used in the RF band.
•Each RF band has its own range of allowed DL channel numbers, for example ” RF band IV: Allowed DL channel numbers are: 1537-1738. Allowed additional DL channel numbers are 1887, 1912, 1937, 1962, 1987, 2012, 2037, 2062, and 2087.”•Optional features: WCDMA 1900, WCDMA 850, WCDMA 1700 & 1800, WCDMA 1700/2100, WCDMA 900, Full WCDMA 1900 UARFCN range
3 © Nokia Siemens Networks Presentation / Author / DateFor internal use
About UARFCN 2/2
• It is not possible to modify WCEL UARFCN in the network element
•The main reason for this restriction is UARFCN’s impact on adjacency types: if the source and target cells have the same UARFCN, the adjancency needs to be of type ADJS; if the source and target cells have different UARFCNs, the adjancency needs to be of type ADJI
•Supporting adjacency type changes ”on-the-fly” would have been a big effor especially for the network element functionality not implemented in the NE UARFCN modification not allowed in the parameter metadata
4 © Nokia Siemens Networks Presentation / Author / DateFor internal use
Current solution
• Plan Editor supports:– Importing the WCEL UARFCN mofidification plan in Plan Editor
– WCEL deletion plan creation
– WCEL recreation plan creation
– Adjacency update plan creation
• Once plans are created with Plan Editor, they can be provisioned in the NE in correct order; there is no ready-made CM Operation Manager workflow for this, the user needs to know the order
5 © Nokia Siemens Networks Presentation / Author / DateFor internal use
Proposed solution
NMS
NetActXML
PlanningSystems
NMS
Planning tool
CM
Data
CM
Data
ConfiguratorRNW
plans
2) New workflow created
First operation: import WCEL UARFCN plan operation which initiates WCEL deletion plan and WCEL creation & adjancency creation plan generation in Configurator
Planning tool
Planning tool
CSV
NMSNMS
1) WCEL UARFCN modification plan
Alternatives:a) New non-network
parameter introduced: WCEL newUARFCN
b) Normal WCEL UARFCN used with special handling (annotation?)
3) Second operation: provision WCEL deletion plan in the RNC(s); all outgoing and incoming adjancencies are deleted
4) Third operation: provision WCEL creation and adjancecy creation plan
RNC
BSC
IADA
LTE BTS