Академический Документы
Профессиональный Документы
Культура Документы
1.2 UMTS evolution 1.3 UMTS Protocols 1.4 Performance Data 1.5 Key Performance Indicators
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
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.
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.
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).
10
11
HSDPA/HSUPA
12
13
14
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
The main difference between the four traffic classes is the delay-sensitivity of the underlying End-to-end services!
16
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)
Iu Protocols (2)
Iu Protocols (2)
(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
20
SM SM
TI
SM SMS
TI TI
SM CC
TI
SM SS
TI
GMM
PD
MM
PD
MM sublayer
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
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
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
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
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
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
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
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
AM /UM DTCH
MAC
BCH PCH FACH Transport channnels RACH DCH HSDSCH
HSDPA Rel 5
Physical Layer
SCH CPICH
PRACH
HS-PDSCH HS-DPCCH
30
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
31
Broadcast PS Data Data User User Plane Plane User data PDCP BMC RLC MAC
Node B
WCDMA
Uu
32
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
33
Node B
RLP
Iub
34
Iur
35
DTCH DCCH
MAC-d MAC-es
NodeB
Ue
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
RANAP ALCAP
Transport Network User Plane SCCP MTP3 -B SSCF -NNI SSCOP AAL5 IP IP M3UA SCTP M3UA SCTP
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
Q.2150.1 MTP3b SSCF NNI SSCOP AAL5 AAL2 *) RTCP is optional. RTP/ RTCP*) UDP/IP
Data Link
ATM
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
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
Mc
Mc
Nb UP AAL2
MGW
AAL5
ATM Nb
40
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
43
44
Counters
45
46
NAS message
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
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
51
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
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
INITIATING MESSAGE [ Procedure,parameter ] SUCCESSFUL OUTCOME [parameter ] Successful Unsuccessful INITIATING MESSAGE [ Procedure,parameter ] UNSUCCESSFUL OUTCOME [ Cause ]
Attempt Success Failure
Procedure
56
57
Possible causes
Case 1 Observation window Attempt Case 2 Success Time
Observed Cell A
Attempt
Cell B
Success
Case 3
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
Cell A1 attempt
1 failure Failure-rate: 100%
Cell A+B
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
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
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
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)
64