GO - NAST3019 - E01 - 1 GSM End-To-End Optimization Methods 72

GSM End-to-end Optimization
Methods
Objectives
 End-to-end optimization is based on the user perception an
d targeted on the service type. It is conducted to trace the
whole process of the service from the terminal, the radio ac
cessing network, the core network, to the service platform.
And the purpose is to optimize the quality of service from th
e application layer to the bottom layer.
 This course describes the solutions for the end-to-end opti
mization of WAP, MMS and the Mobile Streaming Media. It
will help you get deeper understanding about end-to-end o
ptimizaiton.
Contents
 Concept of End-to-end Optimization

 End-to-end Optimization of WAP Service
 End-to-end Optimization of MMS
 Analysis of Mobile Streaming Media
Development of Services and Change of User Be
haviors
 The mobile communication network has kept continuous evolution. At the v
ery beginning, the analog network can only bear analog voice service; Later,
we get the digital network (e.g. the GSM network) to bear voice and SMS; Th
en, the GPRS/EDGE network has enhanced capability to bear low-speed data
services, and it can bear some simple data applications, such as browsing the
WAP, sending/receiving MMS. Now the 3G network can bear diversified hig
h-speed data services, including video phone, browsing WWW, streaming m
edia and online games etc.
 Along with the development of mobile communication network, the user's d
emand for network services has changed constantly, and the user's behavior
type also has changed a lot. At the beginning, the users used the cellular ph
one to make calls, they could talk to each other but could not see each other.
Now, they can enjoy the services of the wonderful multimedia world, such a
s video call, QQ chatting, online VOD, mobile securities, online games, and
e-mail etc.
© ZTE Corporation. All rights reserved

Change of Radio Network Optimization
 GSM Network
 Since the GSM network can only bear voice service and SMS service, the main optimization measure for
the network is analysing the DT/CQT and the network indexes.Basically, the user perception indexes ca
n be replaced by RxQuality, FER, and MOS of DT/CQT, and some of the network KPIs, such as the ratio
of successful wireless connection, ratio of successful handovers, ratio of call drops, ratio of service disco
nnection, etc.
 GPRS/EDGE Network
 The GPRS/EDGE network can bear some low-speed data services, such as WAP browsing and MMS. The
user experience quality (including the interruption of data transmission) cannot be presented by the KP
Is.The traditional optimization measure of DT/CQT/KPI cannot cope with the actual perception of the u
ser now.So the idea of end-to-end optimizaiton, which is based on user perception, has been created.F
oe example, the ratio of successful end-to-end MMS is valued by the Operator,and it has become a im
portant index for appraisal of the operator's branches.
 3G Network and LTE Network
 Video call, WWW browsing, online TV and online games are services relying on high-speed bearing net
work, we cannot use the traditional optimization measures to analyze the whether the service quality is
good or not, such as Mosaic in the image, data interuption, long delay, timeout without response etc.
 Therefore, along with the continuous development of mobile communication net
work and the expasion of service types, the end-to-end optimization based on us
er perception has become the trend of network optimization in the future.

Concept of End-to-end Optimization

QOE and QOS
 QOE: Quality of Experience

 QoE refers to the quality of user experience or user perception.It is the feeling of the ter
minal user about the service they get from the mobile network.It adopts quantified inde
xes to represent the experience and perception of the user and to reflect the difference
between the quality of network service and the user’s expectation.
 In QoE, the evaluation is conducted by the terminal user, and the evaluated objects are t
he services and the network that supports the services, including the core network, the r
adio network and the service platform.
 QOS: Quality of Service
 According to ITU-T, the orignial definition of QoS is “the comprehensive effect of the s
evice performances which decides the user satisfaction”. Currently, QoS is considered a
s the performance indexes of the bottom layer packets transmission, such as the delay, ji
tter, bandwidth, and bit error.
 The QoS mechanism is mainly used to manage the services and provide differences of th
e service from the network perspective. The network entities process different services a
ccording to different quality requirements.
 From the perspective of the mobile communication network, the best solution to get bet
ter QOE is to provide excellent end-to-end QOS.

Realization of End-to-end Optimization
 End-to-end optimization is base

d on the user perception and tar
geted on the service type. It is co
nducted to trace the whole proce
ss of the service from the termin
al, the wireless accessing networ
k, the core network ， to the ser
vice platform. And the purpose is
to optimize the quality of service
from the application layer to the
bottom layer.

Realization of End-to-end Optimization
 The subscriber layer is responsible to set up the index system to represent th
e impact on the user perception from the terminal performances, the subscri
ber rights and the subscriber behaviors.
 The radio bearer layer is responsible to evaluate the perfomance of the radio
access network, mainly focusing on the impact from the radio environment, t
he load of the system, and the radio resource management.
 The network control layer is responsible to evaluate the performance of the
core network, focusing on the service management capabilities of the core n
etwork, including route addressing, call controlling, connection management,
session management, mobility management, authentication and encryption
etc.
 The service layer is mainly responsible for the service signaling interactions b
etween the service platform and the user, and to get the service conditions o
f the subscriber.It is also responsible to analyze the accessing delay, the uplo
ad/download rate of the service, the capability of maintaining the service, re-
transmission of the dropped packet, packet sequence error, service denial an
d no response.
Contents

End-to-end Optimization of WAP Service
 In the end-to-end optimization of

the WAP service, the tracked netw
ork elements mainly include UE, N
odeB, RNC, SGSN, GGSN, WAP Gat
eway etc., and the tracked interfac
es mainly include: Uu, Iub, Iu cs, Iu
ps, Gn, Gi etc..
 Uu: The data is collected via CNT a
nd MRR/CDT and analyzed via CA
N and NETMAX-T.
 Iub and Iu: The data is collected via
MRR/CDT and analyzed via NETM
AX-T.
 Gn and Gi: The data is collected via
network adapter and Wireshark.

Flow of WAP Accessing
 PS Domain Attach:

 The main purpose is to create the route to the SGSN. At first, UE sen
ds the RRC connection request. After the RRC is connected, UE will s
end "Attach Request" message on the GMM layer via initial direct sig
naling. After the signaling connection between RNC and SGSN is cre
ated, SGSN will send "Attach Accept" message (containing the new
P-TMSI of UE) to UE. UE replies with "Attach Accept Complete" mess
age, and the attach process is completed.
 UE may have been attached to the PS domain already when it is start
ed. It also may start attach when the service request is sent. So, the P
S Domain Attach may bot be tracked for certain service.
 After the PS Domain Attach is completed, there will be a logical rout
e between the UE and SGSN, and the UE can be recognized by the S
GSN.
PDP Context Activation
 The main purpose of PDP Context Activation is to create the rout

e from the UE to GGSN, that is to say, to assign the IP address for
the UE. Meanwhile, the related radio accessing bearers are create
d to transmit the data.
 In the GPRS system, the Gn interface is the interface between GG
SN and SGSN.GTP (GPRS Tunneling Protocol) is the first protocol
used to process the packets. It provides the virtual transmission p
ath ( i.e. the channel) from GGSN to SGSN.
 However, since the TCP/UDP connection between UE and the pe
er end is not created yet, the UE still cannot communicate with th
e external network directly.

PDP Context Activation


 WAP accessing generally can be divided into 4 steps.

 Step 1 and Step4: RADIUS start and RADIUS stop. The involved network elem
ents in the PDP Context Activation and PDP Context Deactivation processes ar
e GGSN and the WAP gateway.
 Step2: Setting up the connection on WSP layer. For the MMS service on WAP
2.0 protocol stack, the corresponding step is the standard 3-time TCP handsh
akes, i.e. Syn, Ack, Syn and Ack. After getting reliable WSP/TCP connection to
the WAP gateway, the UE is ready to communicate with the SP.
 Step3: UE sends GET message of WSP layer to the SP, which contains the desti
nation URL. For the WAP service on WAP2.0 protocol stack, UE sends GET mes
sage via HTTP protocol.
 WAP accessing process contains the following actions: Connect, Get and Post.

Connect
 After activating the PDP context and acquiring the IP address, the UE will use the
acquired IP address to send "WSP Connect" message to the WAP gateway, which
contains the parameters about the UE's capabilities and the formats of supported
contents.The WAP gateway will send "Connect Reply" to the UE. If needed, it may
modify the capability parameters of the UE according to its condition. After receiv
ing "Connect Reply", UE will send "WTP Acknowledge" message to the WAP gate
way, and the 3-way handshake connection process is completed.

Get

Get
 The UE sends "WSP GET" message (containing URL, i.e. the addre
ss of the website visited by the subscriber) to the WAP gateway.T
he WAP gateway translates the message into “HTTP GET” and
adds the parameter of content type accepted by the UE, and sen
ds the “HTTP GET” messgae to the corresponding SP. In
normal cases, the SP will send "Response" (with the status code
“200,OK”) to the gateway.WAP gateway will translate the mess
age into "WSP Reply".If the “WSP Reply” is too large, WTP will
divide the message into several segments of "WTP Segmented R
esult" and send the segments to the UE. After receiving the comp
lete Reply message, UE will send "WTP Acknowledge" message t
o the WAP gateway, and the "GET" process is completed.

Post
 The UE sends "WSP Post" message (containing URL, i.e. the address of the website
posted by the subscriber) to the WAP gateway.The WAP gateway translates the m
essage into "HTTP Post" message and sends it to the corresponding SP. In normal
cases, the SP will send "Response" (with the status code “200,OK”) to the gatew
ay.WAP gateway will translate the message into "WSP Reply".After receiving the R
eply message, UE will send "WTP Acknowledge" message to the WAP gateway, an
d the "POST" process is completed.

Content of End-to-end WAP Service Optimizatio
n
 Setup RRC Connection
 In this stage, the evaluated object is the process of setting up signa
ling connection between the UE and the radio accessing network.In
the entire process, the setup of RRC connection is the starting stag
e for the signaling interactions between the UE and the network. T
he UE cannot interact with the core network via direct signaling unl
ess the RRC connection is successfully set up. For example, the Atta
ch process involves signaling interactions between the UE and the
SGSN via SMM layer signalings.
 Based on the information domain parameters and the condition of
signaling interactions, we can see the cause for the failure of RRC c
onnection setup and why the time spent on RRC connection is too
long.
Process of PS Domain Attach
 In the Attach process, the UE may get registered to the SGSN. Th

e time out error may occur in this process due to radio factors. B
esides, we also should pay attention to the capabilities of the UE
terminal and check whether the subscriber has the right to regist
er to the SGSN.In addition, it is also very important to check whet
her the SGSN can respond promptly to the Attach request from t
he UE.

Main Causes for Denial of Attach
 The following are some statistics about the denial of Attach.
 The above table shows the main causes for the denial of Attach.If
the cause is "GPRS services not allowed", it means the subscriber
cannot use the PS domain service.
 "Protocol error, unspecified" menas the protocol is in error. Usual
ly, the problem is caused by poor radio. Sometimes, it is caused b
y that the SGSN can not recognize different subscribers with the
same P-TMSI.
UE sends Attach request, SGSN doesn't respond
The handset has sent the Atta

ch request for several times, b
ut the SGSN doesn't give resp
onse.

PDP Context Activation Flow
 In the PDP Context Activaiton process, the route between the UE

and GGSN is set up, i.e. the GGSN will assign IP address for the U
E after the PDP context is activated.During this process, we shoul
d check whether the APN and IP address type parameters of the
UE are correct, and check wheter the GGSN can respond promptl
y to the PDP activation request from the UE. Besides, we also nee
d to check the downlink/uplink rates requested by the UE and th
e downlink/uplink rates assigned by the network.

Subscriber Reasons for Denial of Activation
 The IP address type of the subscriber is wrong - the IPv6 address is changed to IP
v4 address.
 The APN set by the subscriber is wrong - APN is changed to CMWAP or CMNET.
 The subscriber has set static IP address - The IP address is changed to be obtaine
d automatically.

Connection between UE and WAP Gateway
 Durig the connection process between the UE and the WAP Gate
way, the perfomance of the UE terminal and the responsing
capability of the WAP gateway are examined, no matter it is WSP
connection on WAP1.0 or 3 times TCP handshakes on WAP2.0.
The subscriber has sent Connect request f

or several times in successive manner, but
it has not received any response from the
WAP gateway.

Download/Upload between UE and SP
 For the download/upload between the UE and SP, we mainly sho

uld pay attention to the status code from the SP to the UE. Gener
ally, If the status code is "200 OK", it means the download or uplo
ad is successful. If the status code is lower than 400, it means the
download or upload is successful from the perspective of the net
work. If the status code is higher than 400, it means there must b
e some problem with the process.
 Although we cannot optimize the performance of the SP, we sitll
can compare some popular SPs in groups. We can calculate their
responsing time and compare the result with that of the Montern
et of China Mobile, so as to improve the Monternet system and i
mprove the user perception.

Download/Upload between UE and SP
 If the status code is 1XX, 2XX, or 3XX, it means the process is nor
mal; If the status code is 4XX, it means the UE terminal has some
problem; If the status code is 5XX, it means the server has some
problem.
Status Code
Categories Definition
1XX Message prompt Message prompt
2XX Succeeded The request from the client is accepted by the server successfully
The client is required to take more actions to implement the
3XX Redirected request.
4XX Client error The client may have some problem
The server may have some problem, or it cannot respond to the
5XX Server error request.

Causes for Download/Upload Failure between U
E and SP
Failure Reason Times Ratio Description
The link to the requested webpage was cancelled temporarily. The network will giv
e the new address in the responding message.Usually, the terminal will re-send th
302,Moved temporarily 95269 54.86%
e request to the new address. Some terminals may not respond to the new addres
s, thus the process is failed.
When the requested content was cached, the terminal sends request message wit
h certain conditions. if the response is "304", it means there is no content satisfyin
304,Not modified 25240 14.54%
g the updated conditions, and the terminal can use the cached content directly.Th
e status is normal.
The problem may be caused by the terminal. But the specific reason needs to be f
403,Forbidden 6341 3.65%
urther analyzed.
The link to the requested webpage was cancelled. The network will give the new a
ddress in the responding message.Usually, the terminal will re-send the request to
301,Moved Permanently 2354 1.36%
the new address. Some terminals may not respond to the new address, thus the pr
ocess is failed.
401,Unauthorized 75 0.04% Not authenticated, the terminal has some problem.
416 Requested Range Not

60 0.03%
Satisfiable
413,Request entity too larg The requested webpage content is too large (e.g. wmv and mp3 files), and it is lar
53 0.03%
e ger than the acceptable range of the terminal.
502 Bad Gateway 21 0.01% Gateway error
404 Not Found 19 0.01% The webpage is not found.
400 Bad Request 10 0.01%
307 Temporary Redirect 7 0.00% Temporary redirection occurs.
503,Service Unavailable 7 0.00% Web service unavailable.

303,See Other 7 0.00%
The website encounters some unexpected situation and cannot respond to the ser
500,Internal Server Error 4 0.00%
vice request. The stability of the website server should be improved.
User Perception for Downlod/Upload on UE
 Connection Delay
 The connection delay is the time between the UE sends the RRC connection r
equest and the connection to the WAP gateway is completed, which includes
the RRC conneciton setup delay, the Attach delay (Optional), the PDP context
activation delay and WAP gateway connection delay.
 If any of the time is too long, the user perception will be directly affected.
 Download/Upload Rate
 The purpose of this index is to prevent that the download/upload delays are
different due to the webpage sizes are different.
 The equation is as follows:

 WAP1.0: Application layer packet length/(Acknowledge time - Get time)
 WAP2.0: Application layer packet length/(Ack,Fin time - Get time)

Impact from Packet Loss and Re-transmission
 The segments on WAP 1.0 fall into the following three types:
 [WTP]GTR TTR with Flag bit "not last packet": After receiving this type of seg
ment, the gateway or terminal will not reply with the acknowledge message
(Ack).
 [WTP]GTR TTR with Flag bit "last packet of packet group": After receiving this
type of segment, the gateway or terminal must reply with the acknowledge m
essage (Ack) or with the re-transmission request (Nack) for the packets in the
packet group.
 [WTP]GTR TTR with Flag bit "last packet of message": It means the transmissi
on of the packet group is completed.After receiving this type of segment, the
gateway or terminal may reply with the acknowledge message.During the M
MS transmission process, the gateway may not reply with Ack message, it mu
st forward the MMS to the MMSC then.

Analysis of Re-transmission (Gateway Reason)
 Type1
 Unnecessary service traffics and network loads are increased due to that the g
ateway re-transmits the packets in a short period.
 In the following figure, the interval of re-transmission is only 1ms. It is sugges
ted to optimize the gateway performance.

 Type2
 The gateway stops the transmission of the packet group before it is completel
y transmitted, and the terminal doesn't receive the due packets for a long tim
e. The transmission times out.
 In the following figure, the gateway compleled the transmission of packet[3].
But it didn't continue to transmit the other packets in 5 secons, so the transmi
ssion timed out.

 From the analysis of the signaling file, we find that sometimes th

e gateway cannot properly respond to the request from the termi
nal for re-transmission.The typical flow is as follows:
 On the above figure, the terminal continuously send the "Negativ

e Ack" re-transmission request, and the gateway constantly re-tra
nsmit packet [18] as respondence. However, the packet requeste
d by the terminal is not packet [18]. So the terminal finally sends
"Abort ： No Response" to cancel the request.

 From the analysis of the signaling file, we find that sometimes the re-transmission
is caused by wrong sequence packet . As shown in the following figure, the gate
way sent packet[3] at first, but not packet[1] which is the correct packet according
to the sequence. Then the gateway responded with "Reply".After the terminal sent
the request for re-transmission, the gateway stopped data transmission just after i
t completed the transmission of the two packets before packet[3], and the termin
al continued to wait for the trasmission of the needed packets, the timeout was ca
used by that.

Analysis of Re-transmission (Terminal Reason)
 Normally, after the gateway sends a complete packet group, the terminal should r
espond with "Ack" message.If the terminal has some problem and cannot respon
d promptly, the gateway will re-transmit the last packet in seconds, thus the time
on transmitting the data is prolonged, and it may lead to timeout.
 In the following figure, after the gateway completed the transmission of packet[2
9] (the last packet in the packe group), the terminal didn't respond. So the gatewa
y re-transmits packet [29] 3 seconds later, and the terminal responds to it then.

Contents

End-to-end Optimization of MMS
 In the end-to-end optimization of the
MMS service, the tracked network ele
ments mainly include UE, NodeB, RN
C, SGSN, GGSN, WAP Gateway, MMS
C, SMSC etc., and the tracked interfac
es mainly include: Uu, Iub, Iu cs, Iu ps,
Gn, Gi, MM1, MM3, MM4, MM7, Push
etc.
 Uu: The data is collected via CNT and
MRR/CDT and analyzed via CAN and
NETMAX-T.
 Iub and Iu: The data is collected via
MRR/CDT and analyzed via NETMAX-
T.
 Gn, Gi, MM1, MM3, MM4, MM7, Push:
The data is collected via network ada
pter, no tool has been designed for a
nalyzing the dada
Flow of End-to-end MMS
 With the similar structure to the other WAP applications, MMS al

so needs to be authenticated by the WAP Gateway. However, the
MMS is not directly sent to the recepient. It is sent to a medium s
erver, MMSC first, just like the mail.MMSC saves the MMS tempo
rarily, and sends a notice to the receipient of MMS. After recievin
g the notice, the recepient may try to download the MMS from t
he MMSC.The WAP transmission protocol is used for the transmi
ssion between the UE and WAP Gateway, and the traditional TCP
/IP protocol is used for the transmission between WAP Gateway
and MMSC.

MMS Sending Flow
Step1
Step2
Step3
Step4

MMS Sending Flow
 Step 1 and Step4: RADIUS start and RADIUS. The involved networ
k elements in the PDP Context Activation and PDP Context Deacti
vation processes are GGSN and WAP Gateway.
 Step2 : Setting up the connection on WSP layer. For the MMS se
rvice on WAP2.0 protocol stack, the corresponding step is the sta
ndard TCP handshakes for 3 times, i.e. Syn, Ack, Syn and Ack. Aft
er getting reliable WSP/TCP connection with WAP Gateway, the
UE is ready to send MMS to the MMSC.
 Step3: Tranmission of the MMS layer packets.If the MMS is on W
AP2.0 protocol stack, The transmission of Ack message sent from
the UE is completed when the TCP layer shows "Fin".

MMS Receiving Flow

MMS Receiving Flow
 Basically, Step 1, 2 and 4 of MMS MT flow are the same with that of
MMS MO flow. The difference is in Step3. When UR receives the PUS
H message, it can use two methods to get the MMS. One method is
automatic get, i.e. the UE automatically sends GET request to the M
MSC according to the URI in the PUSH message, and automatically d
ownload the MMS.This process is unknown to the user.The other me
thod is manual get, i.e. the user can click the link to download the M
MS according to the URI in the PUSH message.The basic processes o
f the two mwthods are the same.But, if manual get is adopted, when
the user has no interest in the MMS, he may not extract the MMS, or
he may delete the PUSH message directly. Besides, the user may extr
act the MMS later.
 After receiving the MMS, the user needs to feed back to the MMSC t
o notify that.

Analysis of Successful End-to-end MMS Ratio:
 MMS Failures due to Network Reason:

 Attach failed
 PDP context activation failed
 Packets transmission failed due to radio reason
 SGSN or GGSN lost packets in the transmission
 The querying to E-DNS times out, no response
 WAP gateway times out, no response
 MMSC times out, no response
 MMSC failed to send the PUSH message

Analysis of Successful End-to-end MMS Ratio:
 MMS Failures due to Terminal Reason:
 Attach failed
 The SDU can not receive the data because its storage capacity is too small
 The terminal prorocol stack is in error
 The software has some bug, e.g. the terminal is not compatible with the MMS ID
 The bottom layer link (WSP, TCP) is broken due to the terminal is faulty
 The terminal has no MMS function
 MMS Failures due to Subscriber Reason:
 Attach failed
 The MMSC address set by the subscriber is wrong
 The MMS is sent to a China Unicom subscriber, a fixed telephone, or a China Mobile sub
scriber with prefix number.
 The MMS is too large
 The validity period of the MMS is expired when the subscriber starts to receive the MMS
 The subscriber abandoned the service during the sending/receiving process

Delay of End-to-end MMS
 The average delay between the calling end sending the MMS and the called
end receiving the MMS.Analysis of the main factors influencing the delay of
end-to-end MMS.Here we assume that both MO and MT processes can be
monitored by us.
 The MMS delay mainly occurs in the following stages: (listed according to th
e duration of delay)
 The terminal sends data to the gateway.
 The gateway queries the E － DNS for the user information
 Preparation for transmitting the MMS packets, including setting up connection between
NEs (terminal - gateway, gateway - MMSC) and setting up PDP activation.
 The gateway sends data to the MMSC.
 We need to get the delay on each stage and check the time loss on each NE
in the network (radio, corenetwork, WAP gateway) according to the message
flow.Besides, since the MMS delay is depending on the length of the MMS, s
o we also check the length of the MMS.

Special MMS - Performance Analysis of Mobile
News
 Mobile News is a value-added service operated by China Mobile.
Actually, its working principle is quite simple. It is the MT process
of MMS, i.e. the network sends the PUSH message to the UE to in
form the UE of the URI address of Mobile News, then the UE acq
uires the MMS according to the URI.
 Case Study
 The subscriber has downloaded Mible News for 12679 times in total, among
which 9764 times are succeeded, and the success ratio is 77.01%.During the s
ame period, the ration of successful MMS receiving is 92.07%. It means the ra
tion of successful receiving of Mobile News shoul be improved.

Special MMS - Performance Analysis of Mobile
News
 The following table lists the result of statistics of the reasons for
Mobile News receiving failure.
Message Times Rate
Times of Mobile News receiving 12679 100.0%
Abort 510 4.0%
Disconnect 710 5.6%
Timeout_after_conf 1429 11.3%
Accounting(stop) 266 2.1%
Times of successful Mobile News receiving 9764 77.0%

Analysis of Abort Reasons
Reasons for Abort Times Description
No response, it is caused by the radio network pr

No Response 279
oblem in most of the cases.
Peer request 90 Subscriber behavior
User request 51 Subscriber behavior
Protocol Error 36 Protocol error
Network error 35 Network error (application layer)
Unknown 10

Analysis of Disconnect Reasons
Times of
Terminal model
disconnect
MAUI MMS User Agent 179
 In normal cases, after the terminal recei
NEC-N600/1.0 HopenOS/2.0 41
ves all the segments of Mobile News, it
W200_176220_WBMPGIFJPEGMIDI 40
should send [WTP]Ack and [MMS]Notif
NEWPLUS Tranzda-WAP/2.0 31
yresp － ind messages. However, some t
Nokia7650/1.0 SymbianOS/6.1 Series60/0.9 29
ypes of handset may send [WTP]Abort
or [WSP]Disconnect message after send TCL_A288_01/L3M0501.1.0_M411A/WAP2.0 Pro 17
ing [WTP]Ack, and the connection is re W100_128128_WBMPGIFJPEGMIDI 10

moved by the handset, so the receiving Nokia6708/2.0 (V1.0.0) SymbianOS/7.0 UIQ 6
of Moboile News is failed and the Mob
LCT_X700B_01/LBFM401A/WAP2.0Profile 5
oile News is accumulated at the MMSC.
AHONG_D05/1.0 4
The successful Moboile News receiving
ratio is also affected by this.In order to l LENOVO-P709/S100 NXP5210/DV7 Release/4.2 3
et the operator understand this kind of W300_128160_WBMPGIFJPEGMIDI 3
situations, the terminal types that have PHILIPS9A9R / Obigo Browser 2.0 3
such problem is collected: LG-KF600 Obigo/WAP2.0 MIDP-2.0/CLDC-1.1 3
CoreTek_WAP 3
KBT_L220A_B1/LB7M401A/WAP2.0 Profile 3

Analysis of Timeout Reasons
 From the statistics result, we can see that all the Mobile News tim
eouts are after the gateway sends Conf. It means that the gatewa
y can respond normally, and the tomeout is in the data transmissi
on process and the terminal receiving process.The reason for this
kind of failure may be that the network is too busy or the radio tr
ansmission is congested.
 Based on the telephone interview with some subscribers, we get
to know that both the download rate and the success ratio in the
peak hours are lower than that of the routine hours.
 So it is suggested to send the PUSH message during the period o
ther than peak hours.

Websites/Terminals that Send/Receive Mobile N
ews
Domain name of t Times of sending Times of receiving
Rank Rank Terminal Type
he website Mobile News Mobile News
1 MAUI MMS User Agent 1942
1 211.136.113.36 4409
2 NEC-N600/1.0 HopenOS/2.0 207
2 211.136.112.84 4137 Nokia2610/2.0 (06.70) Profile/MI
3 118
DP-2.0 C
3 211.140.11.198 547 Nokia6131/2.0 (05.50) Profile/MI
4 109
DP-2.0 C
4 218.200.244.197 499
Nokia6120c/2.0 Series60/3.1 Pro
5 81
file/MIDP
5 218.200.247.90 454
Nokia6300/2.0 (04.71) Profile/MI
6 77
6 221.131.128.129 367 DP-2.0 C
NokiaN72/2.0635.2.0.2 Series60/
7 76
7 211.140.16.36 284 2.8 Profi
Nokia2610/2.0 (04.90) Profile/MI
8 211.138.184.162 227 8 72
DP-2.0 C
Nokia7610/2.0 (6.0525.0ch) Sym
9 211.140.12.234 182 9 71
bianOS/7.0
10 221.131.143.7 139 NokiaN73-1/2.0 (3.0638.0.0.44_r

10 63
m132) S60

Analysis of Downloading Rate of Mobile News
Times of successful Mobile Ne

9764
ws receiving
Average size of Mobile News 18.442 (Kb)
Average downloading time 16.609 （ s ）
Average downloading rate 1.110 （ Kb/s ）

Analysis of Downloading Rate of Mobile News
Website of Mobil Average length of Mo Average downloadin Average downloading r
e News bile News (Kb): g time (s): ate (kbps):
211.136.113.36 18.510 17.527 1.056
211.136.112.84 18.260 18.302 0.998
211.140.11.198 18.158 12.782 1.421
218.200.244.197 18.331 14.045 1.305
218.200.247.90 20.078 16.136 1.244
221.131.128.129 16.375 15.878 1.031
211.140.16.36 14.864 11.916 1.247
211.138.184.162 14.688 16.234 0.905
211.140.12.234 18.403 13.897 1.324
221.131.143.7 16.044 11.496 1.396
The average downloading rates of different websites are quite close to each other,
it means the downloading bottleneck is not at the SP, but at the radio accessing n
etwor.

Contents

Analysis of Mobile Streaming Media
 Streaming media is also called as stream-type media. It refers to that the SP uses a video tran
smisison server to send the program to the network as data packets,and after the subscriber
decompress the data useing decompress device, the program is displayed in the format befo
re the transmission.The mobile streaming media refers to the streaming media on the mobile
network.
 Currently, downloading and streaming transmission are two major solutions to transmit the
multimedia information (including Audio/Video) on the network.The Audio/Vedio file is large
in size and requires large storage capactiy, meanwhile the network bandwidth is limited, so it
may take minutes even hours to download the file, and the delay of downloading is long.By s
treaming transmission, the time-based media (sound, image or animation) is transmitted fro
m the Audio/Video server to the user's PC in continuous and real-time manner. The user can
start to view the file just after several seconds of delay of starting, and doesn't need to wait f
or receiving the whole file.When the received time-based media is played on the user's PC, th
e remaining of the file is still downloaded continuously from the server at the backstage.Stre
aming transmission reduces the starting delay by tens even hundreds of times, and it doesn't
need large cache capacity.It overcomes the weakpoint that the user cannot start to view the
media unless he has downloaded the whole file from the Internet.

Analysis of Mobile Streaming Media
 The mobile streaming media service system consists of the strea

ming media terminal, NodeB, RNC, SGSN, GGSN, WAP Gateway a
nd the streaming media server.

Protocols Related to Mobile Streaming Media
 The steaming media data (video and audio) are mainly beared by
RTP/UDP, the static image and text can be beared by HTTP.Capbi
lity Exchange and Presentation Description can be encapsulated
via HTTP or RTSP.RTSP and SDP are used to set up and control th
e session. MIME describes the media type and RTP is the transmi
ssion protocol carried by the streaming media.

RTP
 RTP is a protocol dedicated to transmittin the multimedia data st

reams on Internet. It is published as RFC1889 by IETF.The RTP is d
efined to work in conditions of one-to-one or one-to-multi trans
mission, provide time information and realize stream synchroniza
tion. The RTP usually uses the UDP to transport data, but it can al
so work over TCP, ATM and other protocols. The RTP can only en
sure real-time data transport. It does not provide a reliable trans
port mechanism for sequential transport of data packets; neither
does it offer traffic control or congestion control. Instead, it relies
on the RTCP to deliver these services.

RTCP
 Real-time Transport Control Protocol (RTCP) provides traffic cont

rol and congestion control service together with RTP.During the c
ourse of an RTP session, participants periodically transport RTCP
packets. An RTCP packet contains statistics information about the
number of packets sent and the number of packets lost. So the s
erver can make use of the information to dynamically change the
transmission rate and even the payload type. Used together in a
complementary manner, the RTP and RTCP can optimize transmis
sion efficiency with effective feedback at the smallest cost. Thus t
hey are very suitable to transport real-time data on networks.

RTSP
 The Real-Time Streaming Protocol (RTSP) is proposed together b

y RealNetworks and Netscape. It defines how to effectively transp
ort integrated multimedia data over the IP network in one-to-ma
ny communications.RTSP is above RTP and RTCP. It uses TCP or R
TP to complete the data transmission.

SDP
 The Session Description Protocol (SDP) file is generated by the se

rver. It describes the coding information of the media file and the
information about the links to the hosting server.it is used by the
client to configure the settings of the media player, such as the vi
deo/audio decoder and the port to receive the video/audio data.

Signaling Flow of Mobile TV over GW Interface

Signaling Flow of Mobile TV over GW Interface
 Generally, the signaling flow from the terminal to the WAP gateway and then fro
m the WAP gateway to the streaming media server consists of 6 steps:
 Step1: Set up connection between the user terminal and the WAP gateway and the streaming media se
rver via the 3-time TCP handshakes protocol.
 Step2: The terminal provides the model and version number of the media player software to the stream
ing media server.
 Step3: Use "DESCRIBE" to get the description of the media file on the server, such as the encoding/dec
oding format of audio/video, the format of the streaming media and informaiton about needed bandw
idth; The corresponding REPLY message contains the SDP information.The SDP message basically inclu
des: session information (session name and purpose, session time, bandwidth used by the session, the
user informaiton of the session)) and media infromation (media type , transmission protocol, media for
mat, address and media transmission port for multi-cast, contact address and media transmission port f
or IP uni-cast session)
 Step 4: Set up the radio bearer. From the figure, we can see that there are two setip processes, the first
one is setting up the video stream, and the second one is setting up the audio stream.
 Step5: PLAY. Resuqests the server to start transmitting the media stream in the manner specified by SE
TUP.You can specify the period for transmitting the streaming file, e.g. specify the starting time and en
ding time.
 PAUSE. Stop the transmission of media stream temporarily.You can specify a time point for stopping th
e transmission.If the time point is before the starting time of transmission, the player will reply with "45
7 Invalid Range".If there is no specified time point, the transmission will stop immediately.
 Step6: TEARDOWN Stop the transmission of the media stream and release the related session resource
s.

Analysis of Successful Mible TV Playing Ratio
 If the signalig from OPTIONS to PLAY is considered as successful playing, the succ
ess ratio is 69.68%, If the signaling from SETUP2 (set up radio bearer for the audi
o) to PLAY is considered as successful playing, the success ratio is 99.74%.We can
say that the successful playing is depending on the successful setup of wireless be
arer.According to the signalings, there is no specific status code to indicate the re
ason for the setup failure. If we want to find out the reason, we have to consider t
he factors from multiple aspects, such as the radio environment and the condition
s of core network devices.
Item options describe setup setup2 play pause teardown
Number of
1679 1679 1185 1173 1170 986 982
times
Percentage 100% 100% 70.58% 69.86% 69.68% 58.73% 58.49%

Analysis of Mobile TV Playing Delay
 Mobile TV playing delay refers to the time between the start of options and the st
art of PLAY. The longest duration is 35.141s, and the shortest duration is 768ms.
 The following figure shows the playing times of mobile TV with different delays. T
he horizontal coordinates are the playing delays, and the vertical coordinates are t
he playing times of mobile TV.Most of the palying delays are within 2 seconds.

Analysis of Play Duration
 Play duration refers to the time between the "Play" signaling and
"teardown" signaling.The shortest duration is 494ms, and the lon
gest duration is about 33 minutes.We can see that most of the pl
ay connection time are less than 1 minute.

Analysis of Subscriber Traffics
 The largest mobile TV downloading traffic is 488M, and this subs

criber has the longest playing time. The smallest downloading tra
ffic is 77k.
 In the following figure, most of the Mobile TV traffics are no mor
e than 200k.

Top 10 Terminals that Fail to Play Mobile TV
Success Time Success
descrebe_user_agent Play Counts
s Rate
RealMedia Player HelixDNAClient/10.0.1.3 636 501 78.77%
Nokia5300/2.0 (05.50) Profile/MIDP-2.0 C 81 58 71.60%
RealMedia Player/mc.30.19.01 (s60; epoc_ 257 183 71.21%
RealMedia Player (HelixDNAClient)/10.0.0 218 149 68.35%
RealMedia Player HelixDNAClient/10.0.0.1 154 104 67.53%
RealMedia Player (epoc_av20_thumb)/S60.2 35 23 65.71%
Nokia6300/2.0 (06.01) Profile/MIDP-2.0 C 44 26 59.09%
 Some terminals may report the model of the media player, some may report the manufacturer and model of the term
inal.
 The above table shows the top10 of the media players or terminal models that are most frequently used to play TV pr
ograms. From the table, we can see that RealMedia Player is most frequently used software to play mobile TV, and it
has the highest ratio of successful playing.The handset Nokia5300 is used to play mobile TV for 81 times, and the rati
o of successful playing is 71.6%.

GO - NAST3019 - E01 - 1 GSM End-To-End Optimization Methods 72

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GO - NAST3019 - E01 - 1 GSM End-To-End Optimization Methods 72

Uploaded by

Copyright:

Available Formats

GSM End-to-end Optimization

 Concept of End-to-end Optimization

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 QOE: Quality of Experience

© ZTE Corporation. All rights reserved

 End-to-end optimization is base

© ZTE Corporation. All rights reserved

 Concept of End-to-end Optimization

 In the end-to-end optimization of

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 The main purpose of PDP Context Activation is to create the rout

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 WAP accessing generally can be divided into 4 steps.

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 In the Attach process, the UE may get registered to the SGSN. Th

© ZTE Corporation. All rights reserved

 The following are some statistics about the denial of Attach.

The handset has sent the Atta

© ZTE Corporation. All rights reserved

 In the PDP Context Activaiton process, the route between the UE

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

The subscriber has sent Connect request f

© ZTE Corporation. All rights reserved

 For the download/upload between the UE and SP, we mainly sho

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

416 Requested Range Not

307 Temporary Redirect 7 0.00% Temporary redirection occurs.

503,Service Unavailable 7 0.00% Web service unavailable.

 The equation is as follows:

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 From the analysis of the signaling file, we find that sometimes th

 On the above figure, the terminal continuously send the "Negativ

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 Concept of End-to-end Optimization

 With the similar structure to the other WAP applications, MMS al

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 MMS Failures due to Network Reason:

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

Message Times Rate

Times of Mobile News receiving 12679 100.0%