Showing posts with label OTA. Show all posts
Showing posts with label OTA. Show all posts

Thursday, January 31, 2013

APN Configurational Issues in Android OS Enabled Phones : Part-2 (End)

Refer :- Part-1

As explained in part 1 it is must to have different QoS treatment according to the type of traffic like...


  • Web Browsing
  • MMS
  • Streaming Video
  • Gaming with high level of interactive communication mode.. 
Figure 1 : Major Customer Segment & their preferred data services

Majority of mobile customer base using internet,blackberry, MMS & corporate VPN services. In Figure 1 I have used IBM as an example of a corporate client.



 Figure 2 : Different types of Mobile Data Services Connectivity 

Figure 2 shows that the GGSN is interconnected with MMSC, IBM Corporate network (an example), BB Server & ISP for the services respectively for MMS, IBM-VPN,BES/BIS & internet browsing.

I expect that in coming days Android OS will be able to support 11 APNs [For 2G & 3G Networks]  as per 3GPP Standard TS 24.008. So that customers and the operators can benefit from each other by introducing "blackberry" kind of OTT based services.

For an example BB phones can have different APNs for MMS,internet & BB services.If the sim is subscribed to all these services then the customer can use them without having trouble in changing any APN settings.

Since most of the operators are earning their major share of Data revenue from their corporate clients, who are using for their intranet / corporate network access using VPN, it becomes unavoidable to have this ability in most of the Android OS installed phones or Tabs from Samsung, HTC , Sony etc. More and more new handset vendors are coming in to the market with the hope using the great Android OS and making it big in the market like Samsung. So it will be a disaster in future with such phones available in the market with this known issue.


As stated by Aeneas in COMMENTS Section [ with source code references] , Android OS has the ability to support multiple APNs.But the question remains same.......

"Why Android OS enabled handsets (2G / 2G+3G) are not  configured to show the option similar like Symbian / Microsoft OS Enabled Phones ? To reduce the complexity and simplify the users experience ?  why the network interface is not optimized well in smartphones "


Conclusion : Handset manufacturers using  Android OS should take immediate action in resolving this issue.


3GPP References : TS 24.008 & TS 23.107

Comments from Friends & Critics are welcome.
  
Samsung Galaxy Y Pro Duos B5512 phone Settings :-



  View S.Sunil Kumar's profile on LinkedIn

Sunday, September 30, 2012

APN Configurational Issues in Android OS Enabled Phones : Part-1



As many of us know, internet & MMS traffic are the most used data service types as of today. Streaming video, Corporate Intranet, Cloud services, VoD are gearing to take the customer experience to new levels . Still there are some of the fundamental issues to be dealt for a brighter win-win situation across the entire ecosystem of mobile telecom industry (Mobile Broadband + Voice) across the globe.

It is evident that offering mobile broadband using “LTE” technology is more efficient then any other existing one at present. LTE networks are mostly being built on existing 3G/2G Core Network infrastructures like SGSN/GGSN by duly upgrading them as MME/SGW respectively.

But the important big question is still on the “UE” Manufacturing.

There are big dilemmas like create only Dongle and move to VoLTE and get voice services or manufacture multi radio support capable handsets or not.
It is well known truth the Frequency Bands going o be one of the deciding factors of these questions.
For an example iPhone 5 supports few LTE Bands. And the handsets available in non US countries too but can it supports the frequency bands of those countries which may allocate different one than US?


This is an example of the main topic we are about to step into...APN

What is APN?

As explained in http://en.wikipedia.org/wiki/Access_Point_Name

Access Point Name (APN) is a configurable network identifier used by a mobile device when connecting to a Mobile Services carrier. The carrier will then examine this identifier to determine what type of network connection should be created, for example: what IP addresses should be assigned to the wireless device, what security methods should be used, and how or if, it should be connected to some private customer network.
More specifically, the APN identifies the packet data network (PDN), that a mobile data user wants to communicate with. In addition to identifying a PDN, an APN may also be used to define the type of service, (e.g. connection to wireless application protocol (WAP) server, multimedia messaging service (MMS)), that is provided by the PDN. APN is used in 3GPP data access networks, e.g. general packet radio service (GPRS), evolved packet core (EPC).

So it is evident that APN helps the network to determine proper routing of the data packets.
Nokia, Sony, Sony Ericsson, Samsung (Bada-OS) & iPhone  (iOS 6) - All of them support multiple APN-Application Context Names. But phones loaded with android OS offers only one APN definitions and which is applicable for any applications invoked in that particular phone as explained simply in the following Figure-2.


Figure-1 3GPP R8 Standard Architecture
 
Figure-2 Dats Service Types & APN Usage

Impact 1: Unnecessary load for GGSN in finding the proper route towards MMSC/Other services.
Solution 1: Based on the specific MMSC Proxy address, DNS can provide the routing,
Disadvantage: DNS Capacity is compromised.

Impact 2 : QoS treatment will not be proper. QoS to be differentiated based on invoked service based on the invoked service rather than applying a standard profile HLR passes differential QoS to SGSN if subscribed differently. Even SGSN itself can alter the QoS according the requested APN. But not as per the requested “SERVICE” if that comes via the same APN. SGSN don’t have the ability to treat a particular type of traffic within an established DATA PIPE (i.e. GTP Tunnel).

Disadvantage: Customer experience compromised. Normally for such bad performances the network will be vivtim to pay the price whereas the issue lies somewhere else which is not easy for all to understand.

Solution 2: It is important that Android Platform to have multiple APN Definition capability as per 3GPP standard and each of the service/application should have the freedom to choose appropriate APNs based on manual /OTA Push configurations.


This discussions is more about QoS handling in the Um/Uu & Gb/IuPS interface.

Part 2 : End and Conclusion

View S.Sunil Kumar's profile on LinkedIn