Tracing the network problem of BREW services

As BREW service on mobile internet service is implemented to the low-end handset/mobile phone, it means that there will be a less memory allocated on the mobile phone to download an application from the BREW servers. The good news is BREW clients (mobile phone) on the mobile internet service only need a few RF resources as well while they try to access and download the contents from the BREW server. BREW services need less RF capacity than another same service such as WAP or wireless or mobile internet services. In addition, services, WAP and wireless internet services need bigger RF capacity than voice and messaging (SMS) services

Although BREW services need a less RF capacity but sometime session will also retrieve error message that could be from any network element. BREW client will generate error such as “network busy” while they are trying to access the BREW application. This error could be caused by many reasons such as lack of RF capacity; the server was down etc. this error should be identified and get a resolution immediately to reduce many complaints from subscribers

There are many ways to ensure what the root cause of this problem and how to fix it. Analyzing to all of network elements is needed as one network element connect and support to another one. One of the methods to identify the root cause of problem and fix it is by tracing the session from each network elements. BREW services on mobile internet service are running on application layer and once we ensure that no issue on the application, tracing the entire of session to produce the complete logs and analyze it is very useful.

The network elements which need to be traced to get a useful data are;

1. Base Station Controller (BSC)
2. Mobile Switching Controller (MSC)
3. Public Data Service Node (PDSN)
4. BREW server

By tracing on the BSC we will notice if user already sent the request to PDSN and get the response through A10/11 protocol. We can say that no issue found on the BTS, BSC and MSC once we confirm that the connection between BSC to PDSN is established. We can ensure it once the request from BSC was responded by PDSN. Tracing log from the PDSN will give more information whether the session is established or not and whether user retrieves the application from BREW server or not. Here also we can find why the session was disconnected and who did it. PDSN is the central processing of wireless or mobile internet service including BREW services (download content). The entire of data service process is happening in this network element. Therefore, information about the failed session we can find here; who is not responding and why they are not.

We also can do tracing the session from the BREW server to identify if the request from subscriber arrive to the server or not and if server gives a response to this request. Once we have complete information from each network elements then we can take a resolution to avoid the same case happen in the future