Professional Documents
Culture Documents
Transaction-based
Configuration Management
for Mobile Networks
Henning Sanneck, Christoph Schmelz
Siemens Communications Mobile Networks
Alan Southall, Joachim Sokol,
Christian Kleegrewe,
Christoph Gerdes
Siemens Corporate Technology
Copyright Siemens
Protection
AG 2006.
noticeAll
/ Copyright
rights reserved.
notice
Outline
Goal
Automated assurance of network-wide configuration data consistency
Use cases: Network optimization and growth
Example: cell adjacency management
Proposed solution:
Transaction-oriented CM data management subsystem
Integration into the element management architecture
Conclusions
Page 2
June 2006
EMS
Align ment
NE
NE
Error sources
Description
Non-ideal system
components
Concurrency
Logical errors
June 2006
RAN CM property
Roll-out
phase
Transaction-oriented protocol
configuration
NEs need to function autonomously (NE is the master of
Parallelization of transactions
Delta alignment
phase
Non-
Bandwidth efficiency
Robustness, online assurance of
consistency
Numerous NE
Scalability
downtime)
(network configuration)
June 2006
June 2006
Operator
CLI script
Low-level workflow:
Verification
Correlation of individual results
Roll-out
Alignment / FM
RNC2
RNC1
2
3
1
7
6
5
Page 6
June 2006
Operator
CLI script
High-level workflow:
Roll-out
Temporary revocation of
dependency & rescheduling of few
transactions (this example)
Alignment
RNC2
RNC1
2
3
1
7
6
5
Page 7
June 2006
Network Transaction
NE group
Transaction Group
Single NE
Transaction
Single operation on NE
Command
Transaction
Generator
Transaction
Manager (TM)
TT
1..n
1..n
T
1..n
T
1..n
TG
Master
final commit
Sync
Procedure
dependencies
TG Synchronization Table
Transaction ID
Node ID
State
UUID1
UUIDR1
INIT
UUIDI
UUIDRI
PRECOMM
UUIDZ
UUIDRZ
EXEC
UUID1
T1
UUIDz
PTn
PT1
UUIDn
UUID1
UUIDn
PTz
UUIDz
Tn
Tz
Replica
Replica
R1
Rn
Rz
UUIDR1
UUIDRn
UUIDRz
Transaction
PT
Propagating Transaction
Refresh
Local access
Page 8
UUID1
Tx
June 2006
TG
Transaction Group
Configuration
Preparation Tool
RV PV
-
CLI
CLI script
Element
Manager
Application GET
(Committed
read)
Transaction
Compiler /
Manager
RV Master
Protocol adapter
Management SET
protocol GET (Dirty read)
PT
Transaction-based protocol
Network
Elements
Page 9
June 2006
Agent
Protocol adapter
Replica
Page 10
June 2006
implemented
Requirements to a
Solution properties
full solution
Roll-out
Assurance of inter-NE
phase
consistency
Parallelization
Automation
Transaction-oriented protocol Transaction-oriented protocol between master / replica (=NE),
transactions at replica
Alignment
Delta alignment
phase
Non-
Bandwidth efficiency
functional
Robustness, online
properties
assurance of consistency
Scalability
Page 11
June 2006
Summary
Network Planning
OK
(recent view planned view)
escalate
Policy-based
rescheduling reschedule
Policy-based
transaction
generation
(parallelization /
execution plan)
Analyze
Plan
Policy repository
TG Sync Table
Trans. ID
Node ID
State
UUID1
UUIDR1
INIT
TT
1..n
1..n
T
1..n
T
1..n
TG
Master DB
Monitor
Execute
Knowledge
T
PT
Replica
DB
Sensor
Page 12
June 2006
Actuator
Conclusions
Improvement of CM data consistency (NE/EMS & inter-NE), degree of
automation
Manufacturer: reduced and simplified CM software development:
State-of-the-art data management technology can be applied
Applications do not need to consider low-level data consistency
Mobile Network Operator:
OPEX reduction (less (skilled) operational personnel needed)
Increasingly important with 3G RAN evolution
Parallel operation to legacy CM protocols possible
Partial introduction possible (transaction manager at EMS only)
Info model upgrades can be nicely integrated into the roll-out process
Proof-of-concept implementation has been done at Siemens Communications
Future work: policy development process (encapsulating human operators
knowledge) based on operational experience
Page 13
June 2006