BREW client (mobile phone injected with BREW platform) for many reason such memory capacity, default application for mobile phone that should be available and price will have expire time while it is trying to get BREW application from the BREW server on the mobile internet service . It is starting when subscriber push the application bottom available on the BREW client mobile phone and few second after this effort, BREW client must get an application they are trying to get other wise BREW client will generate error “network busy” and session is fail. It is depending on the handset/mobile phone capacity how long expiry time will be configured on that mobile phone but usually it is about 20 seconds. It means that after 20 seconds since the subscriber access to the application on mobile internet service and getting no response from the BREW server, BREW client will terminate the session

Late response from BREW server could be caused by many things such as network topology from user (BREW client) to BREW server, the capacity of BREW server and response time from the network element on mobile internet service between them such as charging gateway etc. Once it is coming, telecommunication companies should identify this case and resolve immediately. The first thing they need to do is identify which network element that contributes to this late response. To get this information, telecommunication engineer have to do some effort below;

1.      Dump the traffic from the network element which involved to the BREW application such as BREW server, charging gateway and Domain Name Server (DSN) server

They can use tcpdump command if they are using Linux operating system to identify whether request is arriving to those network elements and responded back by them or not. It is also can be done if the network element such as charging gateway on the mobile internet service has the tool to capture the full packet come and go through it.

2.      Snoop the traffic from the data communication network such as router etc

Snoop has the same goal that is the identify whether the traffic come and go through the data com network such as router

3.      Tracing from the handset it self

Each handset/mobile phone vendor usually has a tool to get information about any packet come and go through the mobile phone/handset

Actually the critical issue while late response happened to the application service based on BREW platform is contributing from the network topology itself where BREW application implemented on the mobile internet service . This is how the traffic will be routed from the mobile phone/handset to the BREW server and vice versa. The best network topology to run the BREW service is efficient network where it is required less time to deliver the traffic from source and destination address