SOLVED - LTE-CATM1 connection via Amarisoft software issue! - SOLVED



  • Hello everyone. I've been trying to establish LTE-CATM1 connection with the amarisoft software. I've set up the eNb and the MME. I am using the LTE- CAT-M1 example from https://docs.pycom.io/chapter/tutorials/lte/cat_m1.html . I've got the GPy module. Followed the instructions , set up the atom and everything. But it is behaving weirdly.

    1. When i turn on the device, it sends RRC connection request on the uplink, it receives an answer by RRC connection setup but it never gets an RRC connection setup complete response?

    2. I've managed to get RRC connection setup complete response like 3 or 4 times.

    Weird thing is why is it not being constant? What am i missing? Any help / tips would be appreciated. Thanks!

    That's the messages exchanged between the eNb and the UE:
    1.1 Usually it get's blocked here, and it repeats this:

    12:08:43.303 [RRC] UL 0001 CCCH: RRC Connection Request
    {
    message c1: rrcConnectionRequest: {
    criticalExtensions rrcConnectionRequest-r8: {
    ue-Identity randomValue: 'D6AD23F485'H,
    establishmentCause mo-Signalling,
    spare '0'B
    }
    }
    }

    12:08:43.303 [RRC] DL 0001 CCCH: RRC Connection Setup
    {
    message c1: rrcConnectionSetup: {
    rrc-TransactionIdentifier 0,
    criticalExtensions c1: rrcConnectionSetup-r8: {
    radioResourceConfigDedicated {
    srb-ToAddModList {
    {
    srb-Identity 1,
    rlc-Config explicitValue: am: {
    ul-AM-RLC {
    t-PollRetransmit ms45,
    pollPDU pInfinity,
    pollByte kBinfinity,
    maxRetxThreshold t32
    },
    dl-AM-RLC {
    t-Reordering ms45,
    t-StatusProhibit ms0
    }
    },
    logicalChannelConfig defaultValue: NULL
    }
    },
    mac-MainConfig explicitValue: {
    ul-SCH-Config {
    maxHARQ-Tx n5,
    periodicBSR-Timer sf20,
    retxBSR-Timer sf320,
    ttiBundling FALSE
    },
    drx-Config release: NULL,
    timeAlignmentTimerDedicated infinity,
    phr-Config setup: {
    periodicPHR-Timer sf500,
    prohibitPHR-Timer sf200,
    dl-PathlossChange dB3
    }
    },
    physicalConfigDedicated {
    pdsch-ConfigDedicated {
    p-a dB-3
    },
    pucch-ConfigDedicated {
    ackNackRepetition release: NULL
    },
    pusch-ConfigDedicated {
    betaOffset-ACK-Index 9,
    betaOffset-RI-Index 6,
    betaOffset-CQI-Index 6
    },
    uplinkPowerControlDedicated {
    p0-UE-PUSCH 0,
    deltaMCS-Enabled en0,
    accumulationEnabled TRUE,
    p0-UE-PUCCH 0,
    pSRS-Offset 3
    },
    cqi-ReportConfig {
    nomPDSCH-RS-EPRE-Offset 0,
    cqi-ReportPeriodic setup: {
    cqi-PUCCH-ResourceIndex 24,
    cqi-pmi-ConfigIndex 38,
    cqi-FormatIndicatorPeriodic widebandCQI: NULL,
    simultaneousAckNackAndCQI FALSE
    }
    },
    soundingRS-UL-ConfigDedicated setup: {
    srs-Bandwidth bw3,
    srs-HoppingBandwidth hbw0,
    freqDomainPosition 0,
    duration TRUE,
    srs-ConfigIndex 37,
    transmissionComb 0,
    cyclicShift cs0
    },
    schedulingRequestConfig setup: {
    sr-PUCCH-ResourceIndex 92,
    sr-ConfigIndex 15,
    dsr-TransMax n64
    },
    epdcch-Config-r11 {
    config-r11 setup: {
    setConfigToAddModList-r11 {
    {
    setConfigId-r11 0,
    transmissionType-r11 distributed,
    resourceBlockAssignment-r11 {
    numberPRB-Pairs-r11 n2,
    resourceBlockAssignment-r11 '0'H
    },
    dmrs-ScramblingSequenceInt-r11 1,
    pucch-ResourceStartOffset-r11 0,
    numberPRB-Pairs-v1310 setup: n6,
    mpdcch-config-r13 setup: {
    csi-NumRepetitionCE-r13 sf1,
    mpdcch-pdsch-HoppingConfig-r13 off,
    mpdcch-StartSF-UESS-r13 fdd-r13: v1,
    mpdcch-NumRepetition-r13 r1,
    mpdcch-Narrowband-r13 1
    }
    }
    }
    }
    }
    }
    }
    }
    }
    }

    2.1 When it managed to get RRC connection setup complete, i got this:

    12:08:43.346 [RRC] UL 0001 DCCH: RRC Connection Setup Complete
    {
    message c1: rrcConnectionSetupComplete: {
    rrc-TransactionIdentifier 0,
    criticalExtensions c1: rrcConnectionSetupComplete-r8: {
    selectedPLMN-Identity 1,
    dedicatedInfoNAS '07417208091010103254769805E0E000000000270201D03127208080211001000010810600000000830600000000000300000A00000D00001000C0901103470800F1C16A011E5E0186'H,
    nonCriticalExtension {
    nonCriticalExtension {
    }
    }
    }
    }
    }

    12:08:43.346 [NAS] UL 0001 EMM: Attach request
    Protocol discriminator = 0x7 (EPS Mobility Management)
    Security header = 0x0 (Plain NAS message, not security protected)
    Message type = 0x41 (Attach request)
    EPS attach type = 2 (combined EPS/IMSI attach)
    NAS key set identifier:
    TSC = 0
    NAS key set identifier = 7
    Old GUTI or IMSI:
    IMSI = 001010123456789
    UE network capability:
    Length = 5
    Data = e0 e0 00 00 00
    ESM message container:
    Protocol discriminator = 0x2 (EPS Session Management)
    EPS bearer identity = 0
    Procedure transaction identity = 1
    Message type = 0xd0 (PDN connectivity request)
    Request type = 1
    PDN type = 3 (IPv4v6)
    Protocol configuration options:
    ext = 1
    configuration protocol = 0
    Protocol ID = 0x8021 (IPCP)
    Data = 01 00 00 10 81 06 00 00 00 00 83 06 00 00 00 00
    Protocol ID = 0x0003 (DNS Server IPv6 Address Request)
    Data =
    Protocol ID = 0x000a (IP address allocation via NAS signalling)
    Data =
    Protocol ID = 0x000d (DNS Server IPv4 Address Request)
    Data =
    Protocol ID = 0x0010 (IPv4 Link MTU Request)
    Data =
    Device properties = 0
    TMSI status = 0
    Mobile station classmark 2:
    Length = 3
    Data = 47 08 00
    Additional update type = 1
    MS network feature support = 0x1 (MS supports the extended periodic timer in this domain)
    T3324 value:
    value = 30
    unit = 0 (2 seconds)
    T3412 extended value:
    value = 6
    unit = 4 (30 seconds)
    12:08:43.346 [S1AP] TO 127.0.1.100:36412 Initial UE message
    initiatingMessage: {
    procedureCode id-initialUEMessage,
    criticality ignore,
    value {
    protocolIEs {
    {
    id id-eNB-UE-S1AP-ID,
    criticality reject,
    value 1
    },
    {
    id id-NAS-PDU,
    criticality reject,
    value '07417208091010103254769805E0E000000000270201D03127208080211001000010810600000000830600000000000300000A00000D00001000C0901103470800F1C16A011E5E0186'H
    },
    {
    id id-TAI,
    criticality reject,
    value {
    pLMNidentity '00F110'H,
    tAC '0001'H
    }
    },
    {
    id id-EUTRAN-CGI,
    criticality ignore,
    value {
    pLMNidentity '00F110'H,
    cell-ID '1A2D001'H
    }
    },
    {
    id id-RRC-Establishment-Cause,
    criticality ignore,
    value mo-Signalling
    }
    }
    }
    }

    12:08:43.347 [S1AP] FROM 127.0.1.100:36412 Downlink nas transport
    initiatingMessage: {
    procedureCode id-downlinkNASTransport,
    criticality ignore,
    value {
    protocolIEs {
    {
    id id-MME-UE-S1AP-ID,
    criticality reject,
    value 100
    },
    {
    id id-eNB-UE-S1AP-ID,
    criticality reject,
    value 1
    },
    {
    id id-NAS-PDU,
    criticality reject,
    value '07520022DF6E524BAE5E4278D64CDBB8D1E31E10610FFB3835D1900122CE4C610FDAA834'H
    }
    }
    }
    }

    12:08:43.347 [NAS] DL 0001 EMM: Authentication request
    Protocol discriminator = 0x7 (EPS Mobility Management)
    Security header = 0x0 (Plain NAS message, not security protected)
    Message type = 0x52 (Authentication request)
    NAS key set identifier:
    TSC = 0
    NAS key set identifier = 0
    Authentication parameter RAND:
    Data = 22 df 6e 52 4b ae 5e 42 78 d6 4c db b8 d1 e3 1e
    Authentication parameter AUTN:
    Length = 16
    Data = 61 0f fb 38 35 d1 90 01 22 ce 4c 61 0f da a8 34
    12:08:43.347 [RRC] DL 0001 DCCH: DL Information Transfer
    {
    message c1: dlInformationTransfer: {
    rrc-TransactionIdentifier 0,
    criticalExtensions c1: dlInformationTransfer-r8: {
    dedicatedInfoType dedicatedInfoNAS: '07520022DF6E524BAE5E4278D64CDBB8D1E31E10610FFB3835D1900122CE4C610FDAA834'H
    }
    }
    }

    12:08:49.347 [S1AP] FROM 127.0.1.100:36412 Downlink nas transport
    initiatingMessage: {
    procedureCode id-downlinkNASTransport,
    criticality ignore,
    value {
    protocolIEs {
    {
    id id-MME-UE-S1AP-ID,
    criticality reject,
    value 100
    },
    {
    id id-eNB-UE-S1AP-ID,
    criticality reject,
    value 1
    },
    {
    id id-NAS-PDU,
    criticality reject,
    value '07520022DF6E524BAE5E4278D64CDBB8D1E31E10610FFB3835D1900122CE4C610FDAA834'H
    }
    }
    }
    }



  • Hello everyone,
    The device is now attaching every time to the base station without problems in test environment with the amarisoft LTE software. What i did in order to change the outcome was the following:

    • For the eNodeB i was using PCI Express SDR board
    • I changed that with National Instruments USRP
    • After configuring the network for it, the device managed to attach from the first try without any issues

    So i guess the problem was in the PCI SDR board. What exactly, i have no idea. Results are below.

    0_1531298649376_cell acquired!.png
    0_1531298662770_Connected!.png
    0_1531298671526_attachedconnectedsuccess.png



  • @david1223 Thank you for the reply, but the problem is fixed, the device is successfully attaching to the eNb with the amarisoft lte software, will post explanation later



  • If you are getting any problem to install the LTE CATM1 patch number then you must consult with the Microsoft Support UK for the Microsoft user that they can easily solve this problem form that.



  • Hi everyone,
    After reducing the RX gain, i managed to get to this state:
    0_1528469748458_cell acquired.png
    0_1528469781442_connecting?.png
    The output value of CEREG is 2,2
    The output value of CSQ is 19,99

    I still cannot attach to the eNodeB though, but the eNodeB sends a RRC_Connection_Release. Does that mean the UE doesn't respond on time ( in 10 seconds ) to the eNodeB (With RRC_Setup_Complete)?



  • @jmarcelino Hi Marcelino,
    Yes, i am using test SIM, it is configured.
    I updated the firmware as instructed on the pycom official site. Also put the SQN3330 via microSD card on the pycom for CAT - M1. I went through the forum here and saw someone that managed to connect it, but to a network provider's eNB. Currently using the code he provided, but results are the same, stuck at RRC connection setup. Could it be SIM card issue?



  • @tsvetelin
    Are you using a test SIM card? Is it configured correctly in Amarisoft?


 

Pycom on Twitter