Umts Network

1.
The UMTS network

1.1 Quality in UMTS networks
1.2 UMTS evolution 1.3 UMTS Protocols 1.4 Performance Data 1.5 Key Performance Indicators
TA-TC 6270 /Version 01/Chap. 01 The UMTS network
1.1. Quality in UMTS networks

1.2 UMTS evolution 1.3 UMTS Protocols 1.4 Performance Data 1.5 Key Performance Indicators
What is network Quality?

Customers viewpoint
Not able to register to the network Not able to set up calls Dropped calls Poor information transmission speed, especially for PS calls Bad quality of transmitted information, especially for conversational calls ....
Operators viewpoint
Blocking Call drops Throughput Service Quality Coverage Faulty equipment .....
Network Quality has different aspects, mainly to mention the differences in the customers or operators perception. An operator has to provide service to many subscribers and maintain a certain service quality in a competetive environment at reosonable prices.
Quality monitoring
Grade of service Quality of service Present and future demand Cost efficiency Customer feedback Need for continuous monitoring, optimization and development of the network
Performance data Field tests

Monitoring the network quality is vital for an operator. There are mainly three sources of information to monitor the network quality: The customer feedback, performance data and drive tests. While doing this the operator could for example evaluate before a new service is introduced, what the impact on the network will be.
Quality targets
In order to guarantee a certain service quality, the operator should define Quality targets. When considering the information the operator gets there will be advantages and disadvantages with each of the resources. Customer feedback is important, but it is better to avoid customer complaints. And it is difficult to define objective quality targets on customer complaints.
Customer feedback
Performance data
The operator collects statistical data in defined areas in defined intervals. The operator can define objective targets, because it will see for example how often a call drop happens or how often no capacity is left. The problem is that huge amount of data has to be handled, sometimes the real problem may be hidden within huge files and so intelligent mechanisms are required to reduces the data to for example a visual graph, where possible problems can be seen easily. This is what Key Performance Indicators are about. The problem is, that sometimes the real source of a problem can not be found. One sees the problem, but the source and so the potential solution can not be found. Some KPI show the average customers perception of network quality.
Field tests
Field tests are perfectly suited to reflect the customer perceived service quality, to verify the system configuration or to find sources of problems in defined ares. As well they are necessary for Radio Frequency planning aspects. One can make with advanced tools an very good analyses of the RF signal and so detect problems in the network. But Drive Tests are expensive and not suitable to collect statistical data. So they can be seen as complementary to performance data.
Quality aspects
A mobile network has different aspects to consider, mainly to mention Quality of service, which corresponds to the perceived service quality by the end user, coverage which is in the nature of a mobile network and capacity, a operator offers services to many subscribers. Off course the three aspects are linked with each other. Especially in UMTS, where multiple services can be offered. Especially new services like video calls are demanding what concerns coverage and capacity.
UMTS is a multi-service network, GSM experience is not enough In UMTS coverage areas vary with services Different services need to be monitored individually Data services are very different from voice service
The focus is moved between the 3 aspects. During network roll the main focus was to offer coverage, QoS and capacity were less important in the beginning. In the next step the capacity aspects had to be fulfilled. With QoS the operator can define its position in its market environment.
UMTS is a network technology, which is at its beginning.

Not only, that the network has to be build up and new features are integrated (e. g.HSDPA, HSUPA), as well it has to compete with mature mobile systems and so to offer a very good service quality from the very beginning!
Continuous change is a fact!
Network life cycle

Importance
very important Coverage QoS for UMTS Operator can define its position important Quality
less important
Capacity
roll out
Time (years)
During network roll out the main focus is on providing coverage. This aspect is less dominant, when the network has grown up. Then capacity issues potentialy are the main focus. This may be the same with UMTS. There is a big difference what concerns the QoS. It is important from the very beginning and the importance is growing with the years. In fact here the operator can define its position. UMTS has to compete (?) with mature 2G systems and so QoS is very important from the beginning. And QoS has to be defined per service.
1.2 UMTS evolution

1.3 UMTS Protocols 1.4 Performance Data 1.5 Key Performance Indicators
Network evolution
Release 99: The first UMTS networks consist of an UMTS Terrestrial Radio Access Network (UTRAN) which is connected to a circuit switched core network, the MSC/VLR via IuCS, and to a packet switched core network (GPRS) i.e. SGSN/SLR via IuPS. The central instance within UTRAN is the Radio Network Controller (RNC). The RNCs within UTRAN are connected with each other via the Iur interface.The base stations in UMTS are called NodeB, which is its working name and has no other meaning. The interface between NodeB and RNC is the Iub interface. Release 4: In CS CN the user data flow will go through Media Gateways (MGW), which are elements maintaining the connection and performing switching functions when required. The process is controlled by a separate e element evolved from MSC/VLR called MSC Server. One MSC Server can handle numerous MGWs. The Transition of is transparent to UTRAN. Release 5/6: An IP Multimedia Subsystem (IMS) is defined in order to allow more flexible packet switched services, as well to allow the transfer towards Real Time applications on top of IP. The circuit switched core network is not needed anymore (but still present). Major enhancments are defined for UTRAN, mainly HSDPA (High Speed Downlink Access) and the enhancment for the Uplink (HSUPA , High Speed Uplink Access or better enhanced Uplink). GERAN: Starting with Release 4 the BSS is referred to as GSM/EDGE Radio Access Network (GERAN).
The Release 99 GSM/UMTS network
10
UMTS Network Architecture Release 4
11
UMTS Network Architecture Release 5/6
HSDPA/HSUPA
12
UMTS Bearer / QoS Architecture

Bearer Service and Quality of Service (QoS) in UMTS have more or less the same meaning. In 2G systems where a Bearer was a traffic channel, now in 3G the Bearer represents a selected QoS for a specific service. Finally on the physical layer a Bearer uses channels. The End-to-end Service will define the constraints for the QoS. These constraints will be given to the lower Bearer Services, translated into their configuration parameters and again passed to the lower layer. UMTS sets up a connection through its own layer architecture fulfilling the requested QoS. Problems are foreseen in the External Bearer Services because they are outside of UMTS and the responsibility of the UMTS network operator. To realize this concept the constraints have been specified in QoS Classes with QoS Attributes. A Bearer Service is classified by Traffic class Maximum bit rate Guaranteed bit rate Delivery order Maximum SDU size SDU format information SDU error ratio Residual bit error ratio Delivery of erroneous SDUs Transfer delay Traffic handling priority Allocation/Retention Priority
13
UMTS Bearer / QoS Architecture
14
UMTS Bearer / QoS Classes

Conversational class: real-time applications with short predictable response time. Symmetric transmission without buffering of data and guaranteed data rate.
Streaming class: real-time applications with short predictable response time. Asymmetric transmission with possible buffering of data and guaranteed data rate.
Interactive class: non-real-time applications with acceptable variable response time. Asymmetric transmission with possible buffering of data but without guaranteed data rate.
Background class: non-real-time applications with long response time. Asymmetric transmission with possible buffering of data but without guaranteed data rate.
15
UMTS Bearer / QoS Classes
The main difference between the four traffic classes is the delay-sensitivity of the underlying End-to-end services!
16
1.2 UMTS evolution
1.3. UMTS Protocols

1.3.1 NAS Protocols 1.3.2 UTRAN Protocols
1.4 Performance Data 1.5 Key Performance Indicators
17
Protocols in UMTS
The functional splitt into Core Network (CN) domains and Radio Access Network (GERAN, UTRAN) allows a smooth independent evolution. As a result of this functinal splitt the Radio Resource Management (RRM) is completely handled between the RAN and the User Equipment (UE). RRM covers all aspects of allocation of Radio Resources including handover control. The RRM is task of the RNC, the control entity is called Radio Resource Control (RRC). RRC manages the physical layer and its activities whenever required. The RRC protocol defines procedures between UE and RNC. So called Non Access Stratum (NAS) procedures are handled by the CN domains and the UE. It includes Mobility Management (MM), Session Management (SM) and Call Control (CC) layers. The functions depend on whether the core network domain is the CS (circuit switched) or PS (packet switched). The higherlayer functions performed between the UE and CN are often called Communication Management (CM). The CM entity covers the topics like call control (CC), supplementary services (SS) and short message service (SMS). NAS messages and procedures are inherited from GSM/GPRS and extended when needed.
18
NAS procedures
CM,MM,GMM,SM (3)
Non-Access Stratum
CM,MM,GMM,SM (3)
Radio Protocols (1)
Radio Protocols (1)
Iu Protocols (2)
Iu Protocols (2)
Access Stratum UE Radio (Uu) Iu UTRAN CN
(1)The radio interface protocols are defined in documents TS 25.2xx and TS 25.3xx (2)The protocol is defined in documents TS 25.41x. (Description of Iu interface). (3) CM,MM,GMM,SM: This exemplifies a set of NAS control protocols between UE and CN. There may be different NAS protocol stacks in parallel.
19
NAS signalling (as seen by UE)

The NAS protocols are contained in so called sub-layers. Two sub-layers exist: MM sub-layer : The MM sub-layer contains both mobility management protocols GMM and MM. The MM sub-layer controls the registration status of the UE and controls also the status of the signaling connections to the CN.The MM sub-layer can block higher layer activities when necessary (e.g.location area update before call set up). CM sub-layer : The CM (Connection Management) sub-layer is responsible for all core network services that are not related to mobility management handling. So the protocols CC (call control), SM (session management), SMS(short message service), SS (non-call related supplementary service) are contained in here.All protocols GMM, MM, CC, SS, SMS, SM are transmitted directly in RRC messages (Initial Direct Transfer, UL Direct Transfer, DL Direct Transfer). To distinguish between the NAS protocols a Protocol Discriminator PD is used. This PD is transmitted always ahead of the message itself, so it is easy to see from which protocol the message is.The protocols in the CM sub-layer handle calls, sessions, messaging service, etc.Each of these services is called a transaction. The specification allows that several transactions of the same type of protocols (e.g. several calls, several sessions, etc.) are running simultaneously. Therefore each of the CM sub-layer protocols can occur in several instances. Now with that there is the problem to assign a message to a certain transaction. Well from the PD it is known which protocol it is. But for the transactions of this protocol a Transaction Identifier TI is needed. Like the PD theTI is transmitted ahead of the CM sub-layer message. The RAB manager is responsible for PDP contexts (sessions) only. When no RAB is assigned to a session but uplink data has to be sent, the RAB manager triggers the reestablishment of the RAB.
20
NAS signalling (as seen by UE)

user data
RAB manager
RAB RAB 1 2
RAB RAB control
application and user control

CM sublayer
SM SM
TI
SM SMS
TI TI
SM CC
TI
SM SS
TI
GMM
PD
MM
PD
MM sublayer
Access Stratum Protocols (RRC, RLC, MAC, PHY)
21
NAS procedures
MM Procedures well known from GSM procedures to establish and release connections.

Transfer of Connection Management (CM) sublayer messages. MM common procedures for security functions, e.g. Authentication procedure. MM specific procedures for location functions like Periodic location updating or IMSI attach procedure. UE identified by IMSI or TMSI.
GMM

Procedures well known from GPRS (GMM)
GMM protocol makes use of a signalling connection between UE and SGSN. GMM establishes and releases GMM contexts, e.g. GPRS Attach. GMM specific procedures for location functions like periodic routing area updating. New message implemented to provide service to CM sublayer on top of GMM: SERVICE REQUEST message Initiated by UE, used to establish a secure connection to the network and to request the bearer establishment for sending data.
CC/SMS/SS

Procedures well known from GSM
CC establishes and releases CC connections between UE and CN. Activation of voice/multimedia codec. Based on 3G-324M, variant of H.324. See 3GPP 26.111. Interworking with RANAP for establishment of a RAB. CC SETUP QoS will be mapped onto RANAP RAB assignment.
SM

Procedures well known from GPRS (SM)

Counterpart to CS CC protocol, i.e.it is used to establish and release packet data sessions. SM procedures to setup and release one or more PDP contexts. PDP Contexts are handled in UE and GGSN. SGSN represents interworking function.
Specified in 3GPP 24.008
22
NAS signalling
TMSI Reallocation Authentication Identification MM Information Abort IMSI Detach Normal Location Update Periodic Location Update IMSI Attach MM connection set up MM connection release
SS ( SS
MM
MM sublayer
P-TMSI Reallocation Authentication Identification Information
GMM
GPRS Attach GPRS Detach Routing Area Update Periodic Area Update Service Request
- Activate PDP context -Activate secondary PDP context -Modify PDP context -Deactivate PDP context
A supplementary service modifies or supplements a basic Telecommunication service. CLIP, AoC, BAOC,.
SS
SM
-MOC (Mobile Originated Call) / MTC (Mobile Terminated Call), -call related supplementary services -emergency call set up
CC
CM sublayer
-DTMF tone interaction
23
UTRAN network
The Elements of UTRAN Radio Network Controller (RNC), and Node-B . One Radio Network Systems (RNS) is controlled by a Radio Network Controller (RNC). The RNC is connected to several Node-Bs, each of which serves one or several cells. UTRAN tasks: Admission Control: admit or deny new users, new radio access bearers or new radio links. The admission control should try to avoid overload situations and base its decisions on interference and resource measurements. The admission control is employed at for example initial UE access, RAB assignment/reconfiguration and at handover. Functionality is located in RNC. Congestion Control: to monitor, detect and handle situations when the system is reaching a near overload or an overload situation with the already connected users. System Information Broadcasting: provides the UE with the Access Stratum and Non Access Stratum information which are needed by the UE for its operation within the network. Ciphering: between UE and RNC. Handover: manages the mobility of the radio interface. It is based on radio measurements and it is used to maintain the Quality of Service requested by the Core Network. Handover may be directed to/from another system (e.g. UMTS to GSM handover). Further functions of UTRAN are configuration and maintenance of the radio interface, power control, paging and macro diversity.
24
UTRAN network
25
UTRAN network
The physical layer offers its services to the higher layer by so called transport channels. A transport channel is the mean with which properties (data rate, channel coding) bits are transmitted over the air. These transport channels are accessed by the MAC (medium access control) protocols. This protocol belongs to the layer 2 and has two general tasks: - multiplexing of several UE to the shared radio resource (e.g. random access control, multiplexing of UEs to shared channels -multiplexing of logical channels within one UE to transport channels (logical channels describe the type of information to be transmitted, they are the services offered by MAC to higher layers). As already mentioned, the MAC protocol offers its transport services via logical channels. The information to be transmitted is mapped onto logical channels according to the type of information (e.g. dedicated control information, dedicated data, common control information). The layer contains now several protocols to enhance the logical channel service offered by MAC. The first protocol of this is the RLC (radio link control). The RLC protocol creates for every logical channel an instance of an RLC protocol. Such an instance is able to provide three different reliability services for the corresponding logical channel. These services are -transparent mode : The RLC protocol instance provides no further reliability -unacknowledged mode : The RLC protocol instance provides sequence order control functionality. -acknowledged mode : The RLC protocol instance performs backward error correction.
26
UTRAN Protocols
Drift Serving
NAS
Non-Access Stratum
RRC (Radio Resource Control) Access Stratum
RLC (Radio Link Control) Iu Protocols MAC/MAC es (Medium Access Control)
HSPA Rel 5/6
MAC-hs/e (high speed) Iub/Iur Protocols Physical Layer UE Uu Iub/Iur Iu CN
27
UTRAN network
The physical layer offers its services to the higher layer by so called transport channels. A transport channel is the mean with which properties (data rate, channel coding) bits are transmitted over the air. These transport channels are accessed by the MAC (medium access control) protocols. This protocol belongs to the layer 2 and has two general tasks: - multiplexing of several UE to the shared radio resource (e.g. random access control, multiplexing of UEs to shared channels -multiplexing of logical channels within one UE to transport channels (logical channels describe the type of information to be transmitted, they are the services offered by MAC to higher layers). As already mentioned, the MAC protocol offers its transport services via logical channels. The information to be transmitted is mapped onto logical channels according to the type of information (e.g. dedicated control information, dedicated data, common control information). The layer contains now several protocols to enhance the logical channel service offered by MAC. The first protocol of this is the RLC (radio link control). The RLC protocol creates for every logical channel an instance of an RLC protocol. Such an instance is able to provide three different reliability services for the corresponding logical channel. These services are -transparent mode : The RLC protocol instance provides no further reliability -unacknowledged mode : The RLC protocol instance provides sequence order control functionality. -acknowledged mode : The RLC protocol instance performs backward error correction.
28
Channels in UMTS
AICH BCCH BCH CCCH CPICH CTCH DCCH DCH DPCCH DPCH DPDCH DTCH E-DCH E-DPCCH E-DPDCH E-HICH EE-RGCH HSDSCH Acquisition Indicator Channel Broadcast Control Channel Broadcast Channel Common Control Channel Common Pilot Channel Common Traffic Channel Dedicated Control Channel Dedicated Channel P-CCPCH PCCH PCH PCPCH PRACH PCPCH RACH SCH Primary Common Control Physical Channel Paging Control Channel Paging Channel Physical Common Packet Channel (not shown) Physical Random Access Channel Physical Common Packet Channel Random Access Channel Synchronization Channel
Dedicated Physical Control Channel (not shown) Dedicated Physical Channel Dedicated Physical Data Channel Dedicated Traffic Channel Enhanced Uplink Dedicated Channel Enhanced Dedicated Physical Control Channel Enhanced Dedicated Dedicated Control Channel DCH HARQ Indicator Channel E-DCH Relative Grant Channel FACH High Speed Downlink Shared Channel Forward Access Channel S-CCPCH Secondary Common Control Physical Channel
HS-PDSCH High Speed Downlink Physical Shared Channel
29
Channels in UMTS
RRC
BCCH PCCH CCCH DCCH Logical channnels
User Applications
CTCH DTCH DTCH
TM BCCH
TM PCCH
TM /UM CCCH
UM /AM DCCH
RLC
Logical channnels
UM /AM TM/AM /UM CTCH DTCH
AM /UM DTCH
MAC
BCH PCH FACH Transport channnels RACH DCH HSDSCH
HSDPA Rel 5
P-CCPCH Physical channnels
S-CCPCH AICH PICH
Physical Layer
SCH CPICH
PRACH
DPDCH DPCCH HS-SCCH
HS-PDSCH HS-DPCCH
30
Channels for 3GPP Rel 6

DCCH DTCH DCCH DTCH
Rel 6
HSDSCH
DCH
Transport channnels
E- DCH
DCH
HS-PDSCH
E-DPDCH
E-RGCH
E-HICH
E-AGCH
HS-SCCH
HS-DPCCH
E-DPCCH
Physical Layer (new physical channels)
31
Uu protocols (Rel 99)

RLC RRC 3GPP 25.322 3GPP 25.331
System Network Layer Radio Network Layer Transport Network Layer
CS Data User Plane User data TAF RLP
CS Voice User Plane AMR Codec
Broadcast PS Data Data User User Plane Plane User data PDCP BMC RLC MAC
MM/CC/SS Radio Network Control Plane RRC
Node B
WCDMA
Uu
32
Iub Transport options

Protocol Stack for ATM Transport option Protocol Stack for IP Transport option
Control Plane
IP option Rel 5 Control Plane NodeB Application Part (NBAP)
Data Link Layer

FP for RACH, FACH, PCH, HS-DSCH
Data Link Layer FP for RACH, FACH, PCH, HS-DSCH
Radio Network Layer
Transport network control plane
ALCAP Transport Network Layer AAL2 SSSAR (I.366.1) AAL2 CPS (I.363.2) STC AAL5 SSCS AAL5 Common Part ATM Physical Layer
SSCF UNI SSCOP CPCS SAR
Radio Network Layer
NodeB Application Part (NBAP)
Transport Network Layer UDP IP Data Link Physical Layer SCTP IP
33
Iub protocols (Rel 99)

RLC RRC NBAP ALCAP 3GPP 25.322 3GPP 25.331 3GPP 25.433 ITU-T Q.2630

CS Voice User Plane AMR Codec PDCP BMC RLC MAC UP FP AAL2 ATM STC SSCF- UNI SSCOP AAL5 Broadcast PS Data Data User User Plane Plane User data Radio Network Control Plane MM/CC/SS RRC NBAP Transport Network Control Plane ALCAP
CS Data User Plane User data TAF
Node B
RLP
Iub
34
Iur protocols (Rel 99)

RLC RRC RNSAP ALCAP 3GPP 25.322 3GPP 25.331 3GPP 25.432 ITU-T Q.2630

CS Voice User Plane AMR Codec PDCP ALCAP RLC MAC UP FP AAL2 ATM STC SSCF- UNI SSCOP AAL5 PS Data User Plane User data
Radio Network Control Plane
CS Data User Plane User data TAF RLP
MM/CC/SS RRC RNSAP
Transport Network Control Plane
Iur
35
HSDPA/HSUPA User Plane

Rel 6 DTCH DCCH MAC-d MAC es/ MAC-e
HSUPA user plane
DTCH DCCH
MAC-d MAC-es
MAC-e EDCH FP PHY Uu TNL Iub
EDCH FP TNL CRNC/SRNC DCCH DTCH
PHY UE DTCH DCCH Rel 5/6
NodeB
HSDPA user plane
Ue
MAC-d MAC-hs PHY UE Uu HSMAChs DSCH-FP PHY TNL
MAC-d
HS-DSCH-FP TNL
NodeB
Iub
CRNC/SRNC
36
Iu PS
Radio Network Layer
Control Plane User Plane
IP option Rel 5
RANAP
Iu UP Protocol Layer
Transport Network Layer
RANAP ALCAP
3GPP 25.413 ITU-T Q.2630
Transport Network User Plane SCCP MTP3 -B SSCF -NNI SSCOP AAL5 IP IP M3UA SCTP M3UA SCTP
Transport Network Control Plane
Transport Network User Plane
GTP-U UDP IP AAL5
GTP-U UDP
ATM
Data Link
ATM
Data Link
Physical Layer
Physical Layer
Iu PS
37
Iu CS
Control Plane User Plane
IP option Rel 5
RANAP
Transport Network User Plane Transport Network Control Plane ALCAP
Iu UP Protocol Layer
Transport Network User Plane
SCCP M3UA MTP3b SSCF NNI SCTP IP SSCOP AAL5
Q.2150.1 MTP3b SSCF NNI SSCOP AAL5 AAL2 *) RTCP is optional. RTP/ RTCP*) UDP/IP
Data Link
ATM
ATM Physical Layer
ATM
Data Link
Iu CS
38
PS core network
System Network Layer
MAP TCAP SCCP M3UA SCTP IP AAL5 ATM MTP-L3 MTP-L2 PCM GTP-C UDP IP AAL5 ATM Ethernet AAL5 ATM Ethernet GTP-U UDP IP Application Data IP CAP
Radio Network Layer Transport Network Layer
Gr, Camel
Iub
Gn
39
Rel4 CS Protocols
BICC STC MTP3B Nc CBC (H.248) M3UA SCTP IP L2 SCTP IP L2
MTP3B SAAL AAL5 ATM
SAAL AAL5 ATM
Mc
transport network control plane
Mc
AAL2L3 STC MTP3B SAAL

MGW
user plane
Nb UP AAL2
MGW
AAL5
ATM Nb
40
1.2 UMTS evolution 1.3 UMTS Protocols
1.4 Performance Data

1.5 Key Performance Indicators
41
Performance Data
Performance data is collected in the network elements and then post-processed in postprocessing tools where basically the data is stored and translated into KPIs. KPIs can be graphically displayed and allow an easy comparison of different cells, areas. Possible trouble areas can be identified and one can think about a possible solution. Different groups are targeted by performance data as there are the network planning the network operation the network optimization the management the marketing (chose the operator with least call drops...). As a result there may be different KPIs defined to describe one problem, some KPI focus on the network quality, as seen by the subscriber, some show more a network quality. For example it is normal event that a operator refuses a service because the subscriber didnt pay ist bill, but for the subscribers it is anyway not satisfying. So partly KPIs reflect partly as well network philosophy. Many operators require that the analyses is done at least for special urgent events in real time and some vendors allow partly the triggering of alarms in some cases. Correct operation of network elements is supervised by the O&M (Operation and Maintenance) department which may now take care of alarms. Online Monitoring is here the key.
42
Performance Data
Network Optimisation Network Planning Management Marketing
Postprocessing tool . Performance Data Analyses and Storage Network Operation Performance Data Upload Online Monitoring
Customer Care
Mobile network elements
Performance Data collection
43
What is Performance Data?

Performance Data is based on measurements, that are done in the system. Different types of measurements can be distinguished. Basis is always a predefined granularity period, a certain time within which performance data is collected, usually this is configured in the system with 5 Min, 15 Min, 30 Min, ... , dayly. TYPES OF PERFORMANCE MEASUREMENTS According to the definitions from 3GPP TS 32.104 3G Performance Management (PM), the following types of PM counters can be distinguished: Cumulative Counter: This collection method describes measurements in the form of Number of events. The counters are increased on every occurrence of the event specified. The result contains the total number of events during the granularity period. The counter is reset at the beginning of the granularity period. Typically these events are triggered by messages, reception of one message, the value is increased by one or the expiry of timers, so the event is the non occurance of a expected message. Counters have discrete values, 1 or 59 or 139958883, but not 1.4332! Gauge This collection method describes measurements in the form of Number of additions/deletions. Gauges are increased / decreased on every occurrence of the matching event. Depending on the function of a gauge, it may or may not be reset at the beginning of a granularity period. The results file may list the mean, minimum and maximum value of all measurements taken during the granularity period. Usually gauges are as well discrete.
44
Counters
a certain Event occurs 0 1 2 012 01 2 3 Countervalue time
Granularity Period (or observation time) 2
3 Values are written to file
Max Mean Min Granularity Period time
45
Procedure Related Counters

Procedure related measurements are related with the (not) occurrence of a certain message. That means each message will increase the counter by one so usually cumulative counters. Dependant of the procedure the measurement is related to a certain interface. Procedures between the UE and the MSC (NAS) could be traced in the Uu, Iu, IuCS in some cases on the Iur interface. In the first approach the data for many UEs is collected. So it is statistical data. A message contains Information Elements, which indicate for example cause values or identifiers. In order to filter the messages related to one UE for example, one has to look for the corresponding identifier, for NAS procedures, that is the IMSI or TMSI. In many cases, the messages do not contain the identifier anymore, but during the procedure, depending on the interface a context has been created, that means it is not possible to identify the receiver or sender of a message if the whole procedure is not monitored. A message usually expects a response, so another counter has to be defined to monitor the response. So another counter can in some cases be defined for the case that the message is lost. This is often ruled by timers. If the sender is getting no response, a timer will expire and in many cases the original message is retransmitted. If the message in this case would be lost on the air interface it is of course not possible to see the message in the network. Quite often defined procedures are reused in order to support new features just by modifying the content - for example by defining new cause values.
46
Procedure Related Counters
NAS message
Response
Obviously there is no response!
0 1
012
01
2 3 Countervalue
time
47
Subcounters
Causes within the message can be distinguished, a UE may initiate a message for example in order to -set up a voice call -send a SMS -set up a video call .... So different subcounters can be distinguished, the name of the message is the same, but is used for different reasons. (The term subcounter is not protected, many discuss allready the different causes as counters) This is especially within UTRAN the case, where for example a cell Update message initiated by the UE towards the RNC could indicate a problem (Radio Link Failure), a normal procedure (a response to a paging or mobiliy related procedure when UEs are on common resources. Then the response may be a success or an unsucessfull event. Especially the unsuccesfull events will give for each procedure the reason of the failure. At least on open interfaces causes are specified by 3GPP. Reject causes can be distinguished according to subcounter.
48
Subcounters
Counter
Subcounter
INITIATING MESSAGE [ Procedure,parameter ]
1. Call setup 2. SMS 3. Video call ...
SUCCESSFUL OUTCOME [parameter ] UNSUCCESSFUL OUTCOME [ Cause ]
Failure causes 1. Congestion 2. Network not available 3. .......
49
Performance Data
Performance Data can be collected on all interfaces and on network-element level. -For each -cell -UE -Physical interface (E1, STM 1) -logical interface (Iur, Iub, IuCS, IuPS, CN interfaces) -NodeB -Controlling RNC -Serving RNC -Drift RNC -MSC (-Server) -SGSN -GGSN -HLR And depending on the procedure on different level. ATM, RRC, GTP-C, SS7, NBAP ,.....
50
Performance Data
Iub
cell cell
IuCS
IuPS Iur
cell cell
cell cell cell
cell cell
51
1.2 UMTS evolution 1.3 UMTS Protocols 1.4 Performance Data
1.5 Key Performance Indicators
52
What is a KPI?
Key Performance Indicators can be found everywhere, in technical units as well as in economy. The probably most well-known KPI is the speed of a car measured by a tachometer instrument.
KPI = Key Performance Indicator KPI does not need to be a technical parameter Typical KPI Examples:
New York Stock Exchange KPI: DOW JONES Company KPIs: Gross Margin, OIBT PLMN KPIs: BHCA (SS#7), Attach Failure Rate (GPRS)
53
Key issues definig KPIs

Key Problem #1: Defining good (meaningful) network KPIs Key Problem #2: Verify KPI measurement results Key Problem #3: Which statements can be derived from measured KPIs? KPIs within the UMTS network are defined based on counters, performance data measured within the Network.
Procedure
Attempt
Success
Failure
54
Succes-rates
Many procedure related measurements can be split in 3 sub-measurements -number of attempts (initiating message) -number of successes (sucessfull outcome)and -number of failures (unsuccessfull outcome) In most cases the number of Success + number of Failures = number of Attempts. The success/failure rate of a procedure is calculated by dividing the number of success/failures with the number of attempts and multiply the result with 100%. SuccessRate + FailureRate = 100% For procedure related KPI analysis it gives the Success Rate and the Failure Rate. A failure cause is indicated in the failure message, according to which the source of the problem may be further analyzed. There are good and bad causes depending on the procedure and the viewpoint (customer oriented or network oriented), simple example: if a User tries to access the GPRS network, and there is no roaming, then it is normal from the network, from the users point of view not satifiing.
55
KPI s based on procedures

Peer entities
INITIATING MESSAGE [ Procedure,parameter ] SUCCESSFUL OUTCOME [parameter ] Successful Unsuccessful INITIATING MESSAGE [ Procedure,parameter ] UNSUCCESSFUL OUTCOME [ Cause ]
Attempt Success Failure
Procedure
56
Problems related with KPIs

The simple formula Successes + Failures = Attempts. matches not for all cases the real situation, a certain amount of events is required to get a reasonable statistic, simple example is that one observes the initiating message, but the success happens outside the observation window. Or one observes the messages related to one cell, the attempt is seen, but the success happens in another cell. Another mismatch may be caused by messages which when lost will be repeated. So one me see two attempts on terrestrial interfaces, but only success/failure, because the first attempt is lost on the air interface For some procedures there is no message in some cases, then the failure/success has to be derived by other messages on other layers. A correction has to be added. This is for eaxample the case in an intersystem handover from UTRAN to GERAN. Successes + Failures + correction = Attempts.
57
Possible causes
Case 1 Observation window Attempt Case 2 Success Time
Observed Cell A
Attempt
Cell B
Success
Case 3
1. Attempt 2. Attempt Success
58
KPI topics
If the Formula, which is the basis of the KPI is correct, and the counter is correctly implemented the mismatch should not be big. Many reasons will disappear in the case that a sufficient statistic is available. As a rule of thumb, because many KPIs are expressed in percent, a statistic of 100 events should be contained. If this is not available, one may sum up the events from many objects (interfaces, Node Bs, cells) or granularities (one day, busy hour every day, ..) to achieve a sufficient number, this kind of KPIs are sometimes referred to as high level indicators (call drop rate, handover-successrate,-failure-rate, callsetup successrate) per Radio Network Subsystem for example. When accumulation is done, first the counters of different objects, granularities should be accumulated. In the example with 2 cells, where in cell1 1 attempt is observed and one failure, the failure-rate is 100 %, while in cell 2 100 attempts are seen and 0 failures, the failure-rate would give 0 %. Of course the average of the 2 cells is not 50 %, but 1% failures (Even if in this case obviously something is wrong in cell 1). If anyway the miss-match is still in the range of several percent, then obviously the formula to calculate the KPI is wrong or the counter is not correctly implemented. What means wrong formula? An example could be that one considers call -setups, -releases and incoming handovers for a certain cell/area, but not outgoing handovers. That will so give a traffic absorbing cell (what is sometimes a good behaviour).
59
Mismatch causes
a certain Event occurs
time Granularity Period The absolute number should be considerred!!!
Cell A1 attempt
1 failure Failure-rate: 100%
Cell B 100 attempts

0 failure Failure-rate: 0%
Cell A+B
Failure-rate: 1 %(not 50%!)
60
KPI topics
Capacity related KPI including the level of both, user traffic and signalling traffic provides data which is the basis for planning and operation of the network service types: load on radio interface, usage of resources within the network nodes, user activity and use of services, etc. Examples of measured values may include: paging per LA; Busy Hour Call Attempts (BHCA) per cell, RNC, MSC; handovers per RNC per hour, etc. NETWORK CONFIGURATION KPI Effectiveness of actual plan or planned changes of the network. E.g. traffic level distribution in dependence on area, time etc. QUALITY OF SERVICE (QOS), GRADE OF SERVICE KPI As perceived by the end-user of a 3G system. Service related: E.g. speech quality. set-up durations, drop ratio, packet-throughput, etc. Described by Quality of Service (QoS), Grade of Service (GoS) Maximum congestion allowed RESOURCE AVAILABILITY Duration / probability of availability and unavailability of resources Dependent on the defined objectives, i.e. life cycle of the system, physical and administrative conditions.
61
KPI related Specs

There is no complete KPI definition by 3GPP! KPIs are defined individually by equipement vendors (Siemens, Lucent, Alcatel etc.) and operators (Vodafone, T-Mobile, Cingular etc.) 3GPP 32.401: Concepts and Requirements for Performance Measurement
Measurement Job Admin Tasks Measurement Types (cumulative counters, gauges [max./min/mean] etc.) Granularity Accuracy
3GPP 32.403: Performance Measurements UMTS and combined UMTS/GSM (Definition of Protocol Event Counters)
62
The challenge
Many protocol-related events are not defined in detail. It is hard to distinguish
NODE B SRNC
DCH DL RLC AMD RRC PhysicalChannelReconfiguration
WHICH IS YOUR FAVOURITE? Case 1 Intra-Frequency Hard Handover Case 2 Inter-Frequency Hard Handover Case 3 Intra-Cell (Hard) Handover [Channel Type Switching]
63
Specific KPIs
Different services (voice, video, packet) have different quality requirements and the radio interface shall handle all of them Quality attributes are defined for the channels on the radio interface based on information received from the core network: Parameters for signalling link Radio bearer parameters Transport channels parameters MAC configuration parameters Transfer mode for RLC and its parameters
Service specific KPI Handset specific KPI
The minimum radio resources needed to fulfil the quality requirement are reserved in order to maximize the utilization of the radio interface Each handset has itw own peculiar behaviour within the network and causes different network reactions (e.g. some handsets support ciphering and some do not support ciphering yet) KPIs can be calculated per handset type using the IMEI (International Mobile Equipment Identifier) to understand if specific handsets are creating specific problems to the network. Special subscribers generate more revenue than other subscribers (e.g. business users or roamers) KPIs can be calculated per subscriber type using the IMSI (International Mobile Subscriber Identifier) to understand if specific subscriber types are experiencing network problems (e.g. roamers not allowed to attach to the network due to wrong configuration in the HLR leading)
Subscriber specific KPI
64

Umts Network

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Umts Network

Enviado por

Direitos autorais:

Formatos disponíveis

1.

The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

1.1. Quality in UMTS networks

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

What is network Quality?

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

Performance data Field tests

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS is a network technology, which is at its beginning.

Continuous change is a fact!

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

Network life cycle

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

1.1 Quality in UMTS networks

1.2 UMTS evolution

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

The Release 99 GSM/UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Network Architecture Release 4

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Network Architecture Release 5/6

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Bearer / QoS Architecture

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Bearer / QoS Architecture

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Bearer / QoS Classes

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

UMTS Bearer / QoS Classes

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

1.1 Quality in UMTS networks

1.2 UMTS evolution

1.3. UMTS Protocols

1.4 Performance Data 1.5 Key Performance Indicators

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

Radio Protocols (1)

Radio Protocols (1)

Access Stratum UE Radio (Uu) Iu UTRAN CN

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

NAS signalling (as seen by UE)

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

NAS signalling (as seen by UE)

application and user control

Access Stratum Protocols (RRC, RLC, MAC, PHY)

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

Procedures well known from GPRS (GMM)

Procedures well known from GSM

Procedures well known from GPRS (SM)

Specified in 3GPP 24.008

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

P-TMSI Reallocation Authentication Identification Information

-DTMF tone interaction

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

TA-TC 6270 /Version 01/Chap. 01 The UMTS network

RRC (Radio Resource Control) Access Stratum

RLC (Radio Link Control) Iu Protocols MAC/MAC es (Medium Access Control)

HSPA Rel 5/6