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