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

LTE / LTE-A :- Integarted / Dedicated PGW

Many vendors are proposing an integrated SGW/PGW platform approach for operators, who just started rolling out LTE Networks. Combining both SGW+PGW in same hardware platform ( more specifically, the ever promising ATCA) has advantages over dedicated platforms.

The operator should decide whether to deploy the combined/dedicated platform according to their own projected traffic over their planned coverage.

For some operators who don't want piggyback their LTE traffic on existing 3G/2G platforms can opt for a dedicated infrastructure for LTE GWs (May be from different vendors). But in future if they decide to Upgrade their existing GGSN platform to have GW potentialities then  they should be careful in choosing their combined SGW+PGW Node for the present situation.

The important part is that integrated node should be able to offload part of the traffic on S5 interface to the upgraded GGSN (to PDN-GW) node. This is in a way will ensure the investment protection for existing infrastructure.

What is your view ?....

Overall PCC logical architecture (non-roaming) - 3GPP TS 23.203

Subscription Profile Repository (SPR) & HSS relationship

While reading the 3GPP TS 23.203 Specifications to Undestand PCC,It looks like the only objective of SPR is to manage the QoS based on PDN through which the dedicated EPS Bearer establishment is being attempted. Also couple of doubts arising on the "SPR" functionality.

# What is the relationship between SPR & HSS ?
    No relationship between SPR & HSS as same as PCRF.
# Is it a standalone or integrated with HSS/PCRF ?
    Can be stand alone or Intergarted with PCRF format.
# How the subscriber QoS data in SPR is administrated , similar like HSS Node or combined ?

 Still an open question and looking for the answer....


In case of NSN, the functionality is built in OneNDS and can operate along-with LTE-HSS & IMS-HSS mode depending upon the traffic.
In case of E///, SPR functionality is part of SAPC-Service Aware Policy Controller






CISCO is providing the functionality as part of their ASR5000

References :-

http://www.nokiasiemensnetworks.com/portfolio/products/convergence-ims/cms-8200-home-subscriber-server-for-lte-and-ims

http://www.ericsson.com/si/res/thecompany/docs/publications/ericsson_review/2010/sapc.pdf

http://www.linkedin.com/groupItem?view=&gid=136744&type=member&item=218670693&qid=450b4db5-2dd8-46e3-ad36-838a56d2cbc2&trk=group_most_recent_rich-0-b-ttl&goback=.gmr_136744

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

 

 

High Speed Links (HSL) & ATM Bundling

Since HSL is using ATM Bundling technology, they create one tunnel containing 30 time slots to achieve the 2 Mbps link speed. (30 * 64 = 1920) is the actual available bandwidth for the signaling traffic.

Nowadays both NSN & HUAWEI support the bundling of 8 time slots to one HSL Link. So that they can use the remaining time slots for some other purpose/links. For an example in Huawei they can map some of the incoming signaling link to another PCM without even doing any MTP3 level analysis.

Even though number of SIGTRAN deployments are growing fast, but still HSL will exist for a while till the IP-fication completes everywhere.

The traditional Narrow-band / LSL C7 Link Set capacity was 16 Links * 64 Kbps = 1024 Kbps.Where using HSL technology we can achieve a capacity of 16 Links * 1920 Kbps = 30 Mbps capacity.

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

 

Open Queries related Mobile Telecom

 
I am searching answers and references for the following queries.This is for a thesis project. If you happen to know the answer / reference please post it in "COMMENTS" section.

Thanks to Gavin for the below answers.

1. Iu-FLEX/ A- Flex is recommended in which release of 3GPP ? 

   R5  - Refer 3GPP TS 23.236 V5.4.0 (2005-09) for Iu-Flex Covering CS + PS

   Reference : http://www.3gpp.org/ftp/Specs/html-info/23236.htm
 
2. Gb- Flex is recommended in which release of 3GPP ? 

   R5  - Refer  3GPP TS 23.236 V5.4.0 (2005-09) 

   Reference : http://www.3gpp.org/ftp/Specs/html-info/23236.htm

3. Mobile Internet Traffic Growth Graph since 1990s

    Reference : http://www.cisco.com/en/US/solutions/collateral/ns341/ns525/ns537/ns705/ns827/white_paper_c11-520862.html

4. Internet Traffic Growth Graph since 1990s 

     Reference : http://www.internetworldstats.com/stats.htm

5. ATM [Used in Iu] is part of any standard recommendations ?

     Reference : http://www.itu.int/ITU-T/recommendations/rec.aspx?rec=4560