[srslte-users] NAS Authentication Failure with COTS UE & B210

Thu Jul 8 10:13:21 UTC 2021

Dear Mr. Tallon,

Sure. I attached them to this email. In case it helps you to understand the
issue better, I attached additional documents too. Thanks a lot for your
prompt reply by the way.

Best,
So

PS: Sorry for sending it twice. I forgot to cc srslte-users mailing list.

On Thu, Jul 8, 2021 at 6:41 PM Justin Tallon <justin at srs.io> wrote:

> Hey,
>
> Can you share the logs of the enb and epc please?
>
> Regards,
> Justin
> Justin Tallon
>
> Senior Engineer
>
> Software Radio Systems Ltd.
> +353860670753
> justin at srs.io
> www.srs.io
> Barcelona, Spain
> [image: twitter] <https://twitter.com/srssystems>
> [image: linkedin] <https://www.linkedin.com/in/justin-tallon-71807136/>
> Create Your Own Free Signature
> <https://www.hubspot.com/email-signature-generator?utm_source=create-signature>
>
>
> On Thu, Jul 8, 2021 at 11:37 AM So Randomem <sorandomem at gmail.com> wrote:
>
>> Dear srsRAN Support Team,
>>
>> I am following the srsRAN official guideline, COTS UE Application Note (
>> https://docs.srsran.com/en/latest/app_notes/source/cots_ue/source/index.html#cots-ue-application-note),
>> in order to connect my phone (UE) to my PC (srsEPC & srsENB). However, it
>> seems like my phone is failing to respond to the NAS Authentication request
>> sent by MME as the log shows that srsEPC releases UE after sending the NAS
>> Authentication request. Following is some information that might be useful
>> for you to understand my setup.
>>
>> 1. UE / phone: LG X4 w/ a programmable sim card written with following
>> parameters-ue1,mil,901700000020936,4933f9c5a83e5718c52e54066dc78dcf,opc,fc632f97bd249ce0d16ba79e6505d300,9000,000000000000,9,dynamic
>>
>> 2. srsENB: USRP B210 w/ four VERT 2450 antennas
>> 3. srsEPC: PC w/ Ubuntu 20.04
>>
>> 4. log from srsEPC:
>> Built in Release mode using commit 89f16eed2 on branch master.
>>
>>
>> ---  Software Radio Systems EPC  ---
>>
>> Reading configuration file /root/.config/srsran/epc.conf...
>> HSS Initialized.
>> MME S11 Initialized
>> MME GTP-C Initialized
>> MME Initialized. MCC: 0xf901, MNC: 0xff70
>> SPGW GTP-U Initialized.
>> SPGW S11 Initialized.
>> SP-GW Initialized.
>> Received S1 Setup Request.
>> S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b
>> S1 Setup Request - MCC:901, MNC:70
>> S1 Setup Request - TAC 7, B-PLMN 0x9f107
>> S1 Setup Request - Paging DRX v128
>> Sending S1 Setup Response
>> Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST
>> Received Initial UE message -- Attach Request
>> Attach request -- IMSI: 901700000020936
>> Attach request -- eNB-UE S1AP Id: 1
>> Attach request -- Attach type: 2
>> Attach Request -- UE Network Capabilities EEA: 11100000
>> Attach Request -- UE Network Capabilities EIA: 01100000
>> Attach Request -- MS Network Capabilities Present: true
>> PDN Connectivity Request -- EPS Bearer Identity requested: 0
>> PDN Connectivity Request -- Procedure Transaction Id: 1
>> PDN Connectivity Request -- ESM Information Transfer requested: false
>> Downlink NAS: Sending Authentication Request
>> Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST
>> Received Initial UE message -- Attach Request
>> Attach request -- IMSI: 901700000020936
>> Attach request -- eNB-UE S1AP Id: 2
>> Attach request -- Attach type: 2
>> Attach Request -- UE Network Capabilities EEA: 11100000
>> Attach Request -- UE Network Capabilities EIA: 01100000
>> Attach Request -- MS Network Capabilities Present: true
>> PDN Connectivity Request -- EPS Bearer Identity requested: 0
>> PDN Connectivity Request -- Procedure Transaction Id: 2
>> PDN Connectivity Request -- ESM Information Transfer requested: false
>> Attach Request -- Found previously attach UE.
>> Downlink NAS: Sending Authentication Request
>> ^CStopping ..
>> Deleting eNB context. eNB Id: 0x19b
>> Deleting UE EMM context. IMSI: 901700000020936
>>
>> 5. log from srsENB:
>> ---  Software Radio Systems LTE eNodeB  ---
>>
>> Reading configuration file /root/.config/srsran/enb.conf...
>> WARNING: cpu0 scaling governor is not set to performance mode. Realtime
>> processing could be compromised. Consider setting it to performance mode
>> before running the application.
>>
>> Built in Release mode using commit 89f16eed2 on branch master.
>>
>> Opening 1 channels in RF device=default with args=default
>> [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100;
>> UHD_3.15.0.0-release
>> [INFO] [LOGGING] Fastpath logging disabled at runtime.
>> Opening USRP channels=1, args: type=b200,master_clock_rate=23.04e6
>> [INFO] [UHD RF] RF UHD Generic instance constructed
>> [INFO] [B200] Detected Device: B210
>> [INFO] [B200] Operating over USB 3.
>> [INFO] [B200] Initialize CODEC control...
>> [INFO] [B200] Initialize Radio control...
>> [INFO] [B200] Performing register loopback test...
>> [INFO] [B200] Register loopback test passed
>> [INFO] [B200] Performing register loopback test...
>> [INFO] [B200] Register loopback test passed
>> [INFO] [B200] Asking for clock rate 23.040000 MHz...
>> [INFO] [B200] Actually got clock rate 23.040000 MHz.
>> Setting frequency: DL=2680.0 Mhz, UL=2560.0 MHz for cc_idx=0 nof_prb=50
>>
>> ==== eNodeB started ===
>> Type <t> to view trace
>> RACH:  tti=1131, cc=0, preamble=35, offset=1, temp_crnti=0x46
>> RACH:  tti=671, cc=0, preamble=41, offset=1, temp_crnti=0x47
>>
>>
>> Any insight would be greatly appreciated! If any of you had the same
>> issue before, please let me know how you dealt with this problem. Thanks a
>> lot in advance for your assistance.
>>
>> Best,
>> So
>>
>> _______________________________________________
>> srslte-users mailing list
>> srslte-users at lists.softwareradiosystems.com
>> https://lists.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: enb.log
Type: text/x-log
Size: 1565 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: enb.conf
Type: application/octet-stream
Size: 12775 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uhd_find_devices.log
Type: text/x-log
Size: 206 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc.conf
Type: application/octet-stream
Size: 3545 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: epc.log
Type: text/x-log
Size: 7953 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uhd_usrp_probe.log
Type: text/x-log
Size: 3566 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: user_db.csv
Type: text/csv
Size: 1887 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210708/f153e329/attachment.csv>