The next upgrade to Samsung Galaxy Camera device

There is a possibility that all Digital Cameras [Amateur ones] may loose their space in coming years.
Many smartphones are available today enables customers overcome Digital Photo/Video on the go capturing ability at a decent quality.

Video Streaming devices like the one presented below may offer a bit enhanced help for customers who are fond of  recording high quality videos with the ability to upload/stream immediately through LTE Network.

Figure :1 - Samsung's Video Streaming Device with LTE Capability

           Figure :2 - LTE Data Growth Drivers and their respective Data Rate + Latency requirements

Huawei to unveil 4.5G at its MBB Global Forum in Shanghai BY November-2014

Huawei is in preparation of strategic solution in order to bridge the gap between 4G & 5G and use it as a steppingstone to develop a own proposal for 5G Contender.

During the recent GSMA Middle East 360, Hauwei unveiled the summary of the proposed 4.5G development plan to attract regional players to commit for candidature in deploying the Huawei solution in widespread.

The term "4.5G" created a HUGE buzz, but with very small detail on technological aspects it is not clear enough to conclude the expected improvement on existing 4G/LTE solutions.

In summary, Huawei's aim for 4.5G to achieve....

>  10 Gbps
>  100K Subscribers within a km² coverage
>  To serve the evolution between 2016 to 2020

Also willl support...

>  D2D in addition to M2M
>  4K Video Quality
>  3D Video
>  Complete control/service layer in cloud architecture

Pictures are sourced from Huawei's Presentation Slides.

The storm is coming " APT700 - 700 MHz Band Auction for Mobile Broadband "

Although 700 MHZ band is utilized well by US in the past, but in the recent past around 2010 Asia-Pacific Telecommunity (APT) developed the APT700 bandplan to offer the mobile broadband. Mainly focussing on 3GPP Standardized LTE Technology as the vehicle to utilize the 700 MHZ band for better coverage/speed for MBB services.The same has been adopted by Latin America. 

Meantime in US AT&T and Verizon already aggregated their 700 MHZ holding to implement the LTE Technology in widespread.

The benefits are...

• TRUE GLOBAL ROAMING OPPORTUNITY
• SIMPLE UE Hardware and Battery Saving
• Less CAPEX/OPEX for better MBB Services compare to other bands.

The frequency range : 698-806 MHz

Supports both TDD/FDD Mode technology of LTE.

Telstra is one of the major supporter for the same. Australia is one of the landscape that requires such benefits like Better Coverage + Better Speeds.
GSA-the Global mobile Suppliers Association too backing this strongly.

1. The field test carried out by Huawei proves to be 3.6 times of 1800 MHz band and 6 times of 2600 MHz band.
2. In addition to coverage benefits  throughput also 30% / 65% more compare to a 1800/2100 MHz spectrum.

India is planning to do the auction not before 2015 End, GSMA is pursuing the Govt. of India to release the roadmap soon. 

Going to be action full years ahead of us.

There will be two major fractions in future Operators with 2100/1800 band and Operators with 700/800/900 bands. The former being the target for "Small Cells" vendors. :-))

References : 

http://en.wikipedia.org/wiki/APT_band_plan_in_the_700_MHz_band#History
http://www.gsacom.com/apt700/
http://www.gsma.com/spectrum/wp-content/uploads/2013/07/ZTE-LTE-APT-700MHz-Terminal-White-Paper-ZTE-JUNE-2013.pdf

The difference between the "Marketed" Data Rates and the ones available practically..

ITU-T sets the standard requirements for each generation of mobile telecom services, then vendors and operators try to achieve that. However there are major difference between the "Marketed" Data Rates and practical ones.

Reason can be many for the shortcoming.

Following picture presents the theoretical and practical Mobile Dats Rates.

5G Ecosystem Requirements

5G Ecosystem Requirements as stated by NSN.

• I Hope that , nobody builds a 4.05 G / 4.15 G and claims it as 5G :-))
• I think many experts disagree the fact that LTE is 4G and LTE-A is 5G.
• Whereas technically LTE-A serves the ITU-T 4G Requirements.

Access Control Class & Class-15 SIM Cards - Part 1

ACC & Class-15 SIM cards Continued here : Part-2 

LTE L3 SIB 2 Message from Live Network, Access Barring is not enabled in the eNodeB. More specifically in MME.

References : 3GPP TS 36.331

*** Layer 3 Message type: System Information (DL-BCCH-SCH)

Device: MS1
Time : 12:28:34.538
Vendor Header
  Length : 66
  Log Code (Hex) : 0xB0C0
  HW Timestamp : (9752550.00 ms) 02:42:32.550
    1.25 ms fraction : 0.00
    CFN : 8
    1.25 ms counter : 840230522040
  RRC Signaling Header
    Log Packet Version : 2
    RRC Release Number : 9.5.0
    Radio Bearer Id : 0
    Physical Cell Id : 64
    E-ARFCN : XXXXX
    System Frame Number
      System frame number : N/A
      Sub frame number : N/A
    Message Type : BcchSchDownlink
    Message Length : 41
criticalExtensions : systemInformation-r8
systemInformation-r8
  sib-TypeAndInfo :
    [0 ] :
      noName : choiceInSequence
      choiceInSequence : sib2
      sib2
        radioResourceConfigCommon
          rach-ConfigCommon
            numberOfRA-Preambles : n52
            sizeOfRA-PreamblesGroupA : n28
            messageSizeGroupA : b56
            messagePowerOffsetGroupB : dB10
            powerRampingStep : dB2
            preambleInitialReceivedTargetPower : dBm-104
            preambleTransMax : n10
            ra-ResponseWindowSize : sf10
            mac-ContentionResolutionTimer : sf64
            maxHARQ-Msg3Tx : 5
          bcch-Config
            modificationPeriodCoeff : n2
          pcch-Config
            defaultPagingCycle : rf128
            nB : oneT
          prach-Config
            rootSequenceIndex : 265
            prach-ConfigInfo
              prach-ConfigIndex : 6
              highSpeedFlag : False
              zeroCorrelationZoneConfig : 9
              prach-FreqOffset : 9
          pdsch-ConfigCommon
            referenceSignalPower : 15
            p-b : 1
          pusch-ConfigCommon
            n-SB : 4
            hoppingMode : interSubFrame
            pusch-HoppingOffset : 26
            enable64QAM : True
            ul-ReferenceSignalsPUSCH
              groupHoppingEnabled : False
              groupAssignmentPUSCH : 0
              sequenceHoppingEnabled : False
              cyclicShift : 0
          pucch-ConfigCommon
            deltaPUCCH-Shift : ds2
            nRB-CQI : 1
            nCS-AN : 0
            n1PUCCH-AN : 10
          soundingRS-UL-ConfigCommon
            SoundingRS-UL-ConfigCommon : setup
            srs-BandwidthConfig : bw2
            srs-SubframeConfig : sc9
            ackNackSRS-SimultaneousTransmission : True
            srs-MaxUpPts: true
          uplinkPowerControlCommon
            p0-NominalPUSCH : -67
            alpha : al07
            p0-NominalPUCCH : -105
            deltaFList-PUCCH
              deltaF-PUCCH-Format1 : deltaF0
              deltaF-PUCCH-Format1b : deltaF3
              deltaF-PUCCH-Format2 : deltaF1
              deltaF-PUCCH-Format2a : deltaF2
              deltaF-PUCCH-Format2b : deltaF2
            deltaPreambleMsg3 : 0
          ul-CyclicPrefixLength : len1
        ue-TimersAndConstants
          t300 : ms200
          t301 : ms200
          t310 : ms1000
          n310 : n10
          t311 : ms10000
          n311 : n1
        additionalSpectrumEmission : 1
        timeAlignmentTimerCommon : sf1920
    [1 ] :
      noName : choiceInSequence
      choiceInSequence : sib3
      sib3
        q-Hyst : dB2
        mobilityStateParameters
          t-Evaluation : s60
          t-HystNormal : s30
          n-CellChangeMedium : 4
          n-CellChangeHigh : 8
        sf-Medium : dB0
        sf-High : dB0
        s-NonIntraSearch : 9
        threshServingLow : 6
        cellReselectionPriority : 7
        q-RxLevMin : -64
        s-IntraSearch : 29
        presenceAntennaPort1 : False
        neighCellConfig
          Binary string (Bin) : 01
            [0 ] : 0
            [1 ] : 1
        t-ReselectionEUTRA : 1
        t-ReselectionEUTRA-SF
          sf-Medium : lDot0
          sf-High : oDot75
 


*** Layer 3 Message type: System Information Block 2

Device: MS1
Time : 11:48:41.907
radioResourceConfigCommon
  rach-ConfigCommon
    numberOfRA-Preambles : n52
    sizeOfRA-PreamblesGroupA : n28
    messageSizeGroupA : b56
    messagePowerOffsetGroupB : dB10
    powerRampingStep : dB2
    preambleInitialReceivedTargetPower : dBm-104
    preambleTransMax : n10
    ra-ResponseWindowSize : sf10
    mac-ContentionResolutionTimer : sf64
    maxHARQ-Msg3Tx : 5
  bcch-Config
    modificationPeriodCoeff : n2
  pcch-Config
    defaultPagingCycle : rf128
    nB : oneT
  prach-Config
    rootSequenceIndex : 175
    prach-ConfigInfo
      prach-ConfigIndex : 6
      highSpeedFlag : False
      zeroCorrelationZoneConfig : 9
      prach-FreqOffset : 9
  pdsch-ConfigCommon
    referenceSignalPower : 15
    p-b : 1
  pusch-ConfigCommon
    n-SB : 4
    hoppingMode : interSubFrame
    pusch-HoppingOffset : 26
    enable64QAM : True
    ul-ReferenceSignalsPUSCH
      groupHoppingEnabled : False
      groupAssignmentPUSCH : 0
      sequenceHoppingEnabled : False
      cyclicShift : 0
  pucch-ConfigCommon
    deltaPUCCH-Shift : ds2
    nRB-CQI : 1
    nCS-AN : 0
    n1PUCCH-AN : 10
  soundingRS-UL-ConfigCommon
    SoundingRS-UL-ConfigCommon : setup
    srs-BandwidthConfig : bw2
    srs-SubframeConfig : sc0
    ackNackSRS-SimultaneousTransmission : True
    srs-MaxUpPts: true
  uplinkPowerControlCommon
    p0-NominalPUSCH : -67
    alpha : al07
    p0-NominalPUCCH : -105
    deltaFList-PUCCH
      deltaF-PUCCH-Format1 : deltaF0
      deltaF-PUCCH-Format1b : deltaF3
      deltaF-PUCCH-Format2 : deltaF1
      deltaF-PUCCH-Format2a : deltaF2
      deltaF-PUCCH-Format2b : deltaF2
    deltaPreambleMsg3 : 0
  ul-CyclicPrefixLength : len1
ue-TimersAndConstants
  t300 : ms200
  t301 : ms200
  t310 : ms1000
  n310 : n10
  t311 : ms10000
  n311 : n1
additionalSpectrumEmission : 1
timeAlignmentTimerCommon : sf1920



Through this analysis the major principles that I have understood are given below.

1.     ACC-Access Control Class Feature introduced to control various Mobile users access in to GSM Network. The same is extended to 3G/4G.

2.    Normal Customers are programmed with Access Class 0-9 and allowed in HPLMN/VPLMN

3.    PLMN Team/Staffs are programmed with Access Class 11/15 allowed Only in HPLMN.

4.    Access Class 12/13/14 allowed to roam in HPLMN & VPLMN. (No MCCMNC Check)

5.    Some MS/UE Vendors manufacture their equipment to support only ACC-0 to 9.

6.    EFACC – A 2 byte information stored in each SIM’s ROM which will be transferred to MS/UE when it is powered on. Ref : 3GPP TS 22.011

7.    System Info Type 3 (GSM/WCDMA) broadcasted from the network will carry the barred class info.In case of LTE/LTE-A it will be System Info Type 2

Reference: http://msc.mpirical.com/mod/forum/discuss.php?d=103

[External Blogs were failing to keep the Blog Material. So I have used the Mpirical.com’s forum.]

Anyway I have re-posted it here... for everybody's reference...

References : 

http://www.3gpp.org/ftp/Specs/archive/11_series/11.11/

http://www.3gpp.org/ftp/Specs/archive/22_series/22.011/

http://en.wikipedia.org/wiki/Subscriber_Identity_Module

http://www.emsec.rub.de/media/crypto/attachments/files/2011/04/sim_card_security.pdf



I will be posting the details of how this can be used for commercial purpose/social responsibilities/ network maintenance activities....in upcoming posts....

Network Architecture Evolution - 1G to 4G

As we can see in the above diagram, aprt from transport technology migration from TDM to "All-IP"  LTE/4G architecture retains many similarity to 1G - AMPS Network. 

The major difference is that the Central Core (i.e. MTSO) in AMPS was handling both User and Control Planes. But in 4G they are separated to allow independent growth and modernization along with extensive reduction in "LATENCY".

LATENCY was not at all a factor during 1G or Initial 2G Periods. 

Since LTE is more of a "DATA" network and supports Voice in the form of VoIP, it provides the flexibility in using the Voice CODECS  depending upon various factors. But 2G Networks are still having a fixed rate/codec (sets) due to their radio access technology.

Eventhough GSM networks are suffering the lack of flexibility like LTE/LTE-A/3G networks, there are some steps taken by major vendors to revive this market based on the interest from existing 2G Only operators/ the ones who has a license in hand.

There are many hurdles in the form of existing 2G operator to become a LTE Operator. May be a regulatory/license obligation/business viability can halt them.

From my opinion, Voice is still going to rule for a while in the form of 2G Networks.The proof, Single Radio Voice Call Continuity (SRVCC) /VoLTE are developed not only to provide a smooth migration, also will help 4G Operators to offload all their Voice Service demand from their customers to 2G Networks.

So Technology oriented licensing which cornered the 2G Operators hsa a greater chance in reviving their business in the form tie ups with 4G Operators.

Reference :Telefónica makes first multivendor VoLTE-to-3G call handover

Reference : US Wireless Carriers Move to New Technology—for Voice

 

 

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 :-

 

Access Control Class & Class-15 SIM Cards - Part 2

With reference to my earlier post  Access Control Class & Class-15 SIM Cards - Part 1, 

Following is the description of 3 identified usage possibilities of ACC feature in live 2G-GSM/3G-WCMDA networks.

 

Figure 1 : Commercial Usage of ACC Feature

Normally the indoor sites allotted to corporate customers in an important location of a city is good enough to serve the customers (Corp. Mainly) during 9AM to 6PM. But most of networks where I have worked, the peak busy hour starts from 5~6 PM only and lasts up to 11 ~ 12 PM.During which the indoor coverage/IBS solution capacity unnecessarily wasted.Either they will be idle / used at minimum level.

Instead those corp. customer indoor sites  should be a microcell with some external exposure. Corp. customers to have Class 15 (Example) SIM Cards. During morning hours these particular indoor sites can be configured to serve only those for CLASS-15 SIM cards.And in evening should be configured to allow all sim class. Such optimum usage will help operator to leverage those indoor BTS/NodeBs (i.e Infrastructure) . to handle those excessive  traffic at Busy Hour.

 

Figure 2 : Disaster Recovery Usage of ACC Feature

During any disaster situation in certain countries it is evident from past experiences, it will be better to cease the public communications in order to speed up the recovery actions and streamline safety of public.Also helps to prevent  unnecessary rumor based mis-behavior from public or from a particular segment of public.

So all BTS/NodeBs to be configured to serve the Class-1X which is allotted for Public Safety Organizations based on a pre-agreement.

This can be done for a particular geography/selected areas/cells in order to achieve quicker & un-interrupted recovery actions.

 

Figure 3 : Network Maintenance Usage of ACC Feature

The widely used model, doing all sort of maintenance activities like DT & Optimization etc while preventing customers from accessing the network through that particular BTS/s under maintenance and eventually avoids unnecessary disturbance to customers. 



   

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?

http://www.gsmarena.com/apple_iphone_5-4910.php

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