«  
  »

Identifying the problem of Value Added Service (VAS) services

By engineer, on October 17th, 2009

There will be a lot of work should be done while they are receiving a lot of complaints from their subscribers according to Value Added Service (VAS) service through mobile internet service. VAS service is involving entire of network elements which to run voice call service and for some VAS services through mobile internet service they involve network element of data service. it is more difficult to identify the root cause of problem and fix it if its VAS service through mobile internet service is involving data service equipment. It means that telecommunication companies should check the entire of network element to find and fix it. There will be many three parties which responsible to the application service and vendors which expert on the telecommunication core network such as Base Transceiver Station (BTS), charging gateway, Intelligent Network, Public Data Serving Node (PDSN), Data Communication such as router, catalyst and load balancer

Value Added Service (VAS) through mobile internet servicewhich involves data service equipment such as download contents, mobile shopping, subscription service and service based on BREW platform, it is very though to identify partial problem such as error “network busy” during certainty period e.g. busy hour rather than we notice that the service goes down. While telecommunication companies experience this partial problem for example partial problem on download contents on BREW platform, the action they will do to identify root cause of problem and fix it soon are;

1. Identifying the pattern of problem through the mobile phone/ handset

Collecting the pattern of errors while subscriber experience such as whether subscriber completely getting a problem while accessing the download content, mobile shopping and subscription services or they are getting problem while accessing to particular application and what the message will appear on the mobile phone/handset while problem is coming

2. Identifying the Radio Frequency (RF) capacity

Network busy is the common issue on wireless/mobile internet service including Value Added Service (VAS). If the location which covers the service is having good quality of signal but the service is still getting problem, it means that RF capacity is not contributing to this partial problem. Confirmation that the capacity of signal is sufficient to carry out the traffic including VAS service is needed to go to the further investigation

3. Tracing the session from the central process of data service such as Public Data Serving Node (PDSN)

All sessions to access the entire of application on VAS services will go through PDSN node. By tracing a particular session which experience error “network busy”, we can identify whether the request from subscriber already sent to the application server and responded back to the subscriber or not

4. Identifying packet data received at data communication equipment, application server, Domain Name Server (DNS) and charging gateway

By tracing to the application systems related to VAS service we can identify packet data which come and go the each application service and analyze whether each element already receive and response the request from subscriber or not. This section will identify which part of network element that did not run proper while a request from subscriber is coming

Incoming search terms for the article:

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay
BREW, VAS, troubleshooting   , , , , , , , , , , , , , ,  
«  
  »

34 comments to Identifying the problem of Value Added Service (VAS) services

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

«  
  »