[srslte-users] Fwd: Having troubles to connect the srsUE
Nehemiah Chan
nehemiahchan1999 at gmail.com
Fri May 10 08:03:48 UTC 2019
HI Francisco,
Sorry to keep you waiting. I have increased the UE tx_gain from 80 to 100
not sure if I should increase more. If I continued to run the same commands
like sudo srsepc, sudo srsenb and sudo srsue, I would still face the same
output as the initial post. I clarify with my supervisor he told me to use
command if_masq.sh(if I remember correctly) under srsepc folder. The boards
are just placed one over the one He told me it should correctly if I check
the active connections I would see the tun_srsue(shown), although I would
see the other active connections(WIFI). I am not familiarize with Ubuntu
but I assumed that if I see something on the active connections tab, which
means the computer is using that internet(srslte server as the base
station), I am not very clear on this part maybe someone can help to
enlighten me. If it is correct, I would like to thank you guys Francisco
and Alejandro for your help. I am now waiting for sysmoUSIM_SJS1 to arrive
to configure my own UE. For the smart card reader, I will be using the
ACR38U-N1.
Best Regards,
Nehemiah
On Wed, May 8, 2019 at 6:48 PM Francisco Paisana <
francisco.paisana at softwareradiosystems.com> wrote:
> In the logs you provided earlier, your UL SNR looks very low. Can you
> increase your UE tx_gain? You can do this by changing the ue.conf or
> passing the cmd line flag: "--rf.tx_gain=<value>".
>
> Take a look at your device maximum gain, and set something within those
> bounds. If it does not work, try to put the boards closer to each other.
>
> On Wed, May 8, 2019 at 9:53 AM Nehemiah Chan <nehemiahchan1999 at gmail.com>
> wrote:
>
>>
>>
>> ---------- Forwarded message ---------
>> From: Nehemiah Chan <nehemiahchan1999 at gmail.com>
>> Date: Tue, 7 May 2019 at 6:11 PM
>> Subject: Re: [srslte-users] Having troubles to connect the srsUE
>> To: Francisco Paisana <francisco.paisana at softwareradiosystems.com>
>>
>>
>> Hi Francisco,
>>
>> Thanks for your quick reply. I followed your instructions.
>>
>> With computer 1,
>>
>> =========================================ue-================================
>>
>> pi at pi:~/srsLTE/build/lib/examples$ ./pdsch_ue -f 2630e6 -r 0x1234
>>
>> linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>> UHD_003.009.007-5-ge8202128
>>
>> SNR: +9.1 dB | -inf dB
>>
>> Opening RF device with 1 RX antennas... Mbps (net/maximum/processing)
>>
>> Opening USRP with args: type=b200,master_clock_rate=30.72e6
>>
>> -- Detected Device: B210
>>
>> -- Operating over USB 3.s=904
>>
>> -- Initialize CODEC control...
>>
>> -- Initialize Radio control...
>>
>> -- Performing register loopback test... passsubframe.
>>
>> -- Performing register loopback test... pass
>>
>> -- Performing CODEC loopback test... pass
>>
>> -- Performing CODEC loopback test... pass
>>
>> -- Asking for clock rate 30.720000 MHz...
>>
>> -- Actually got clock rate 30.720000 MHz.
>>
>> -- Performing timer loopback test... pass
>>
>> -- Performing timer loopback test... pass
>>
>> Starting AGC thread...
>>
>> Tunning receiver to 2630.000 MHz
>>
>> Searching for cell...
>>
>> *Found Cell_id: 0 CP: Normal , DetectRatio=100% PSR=15.24, Power=-25.9
>> dBm
>>
>> Found Cell_id: 0 CP: Normal , DetectRatio= 0% PSR=0.00, Power=-inf dBm
>>
>> Found Cell_id: 0 CP: Normal , DetectRatio= 0% PSR=0.00, Power=-inf dBm
>>
>> Decoding PBCH for cell 0 (N_id_2=0)
>>
>> -- Asking for clock rate 23.040000 MHz...
>>
>> -- Actually got clock rate 23.040000 MHz.
>>
>> -- Performing timer loopback test... pass
>>
>> -- Performing timer loopback test... pass
>>
>> Setting sampling rate 5.76 MHz
>>
>> - PCI: 0 7.2, FrameCnt: 0, State: 1
>>
>> - Nof ports: 1
>>
>> - CP: Normal
>>
>> - PRB: 25
>>
>> - PHICH Length: Normal
>>
>> - PHICH Resources: 1
>>
>> - SFN: 476
>>
>> Decoded MIB. SFN: 476, offset: 3
>>
>> Tx scheme: Single
>>
>> nof layers: 1
>>
>> nof codewords: 1
>>
>> CFO: -841.97 Hz
>>
>> RSRP: +37.7 dBm | -inf dBm
>>
>> SNR: +11.9 dB | -inf dB
>>
>> Rb: 0.72 / 0.70 / 3.31 Mbps (net/maximum/processing)
>>
>> PDCCH-Miss: 20.64%
>>
>> PDSCH-BLER: 0.02%
>>
>> TB 0: mcs=1; tbs=904
>>
>> TB 1: mcs=0; tbs=0
>>
>> Press enter maximum printing debug log of 1 subframe.
>>
>> SIGINT received. Exiting...
>>
>> Hangup layers: 1
>>
>> pi at pi:~/srsLTE/build/lib/examples$
>>
>> CFO: -841.97 Hz
>>
>> RSRP: +37.5 dBm | -inf dBm
>>
>> SNR: +11.7 dB | -inf dB
>>
>> Rb: 0.72 / 0.70 / 3.24 Mbps (net/maximum/processing)
>>
>> PDCCH-Miss: 20.23%
>>
>> PDSCH-BLER: 0.00%
>>
>> TB 0: mcs=1; tbs=904
>>
>> TB 1: mcs=0; tbs=0
>>
>> Press enter maximum printing debug log of 1 subframe.
>>
>> With computer 2,
>>
>>
>> ===================enodeb=====================================
>> ~/srsLTE/build/lib/examples$ ./pdsch_enodeb -f 2630e6
>> Opening RF device...
>> [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501;
>> UHD_3.15.0.git-84-g164d76dc
>> Opening USRP with args:
>> Error opening UHD: code 11
>> Opening bladeRF...
>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>> Setting sampling rate 5.76 MHz
>> Set TX gain: 60.0 dB
>> set TX frequency to 2630000127
>> Set TX freq: 2630.00 MHz
>> - Resource Allocation Type: Type 0
>> + Resource Block Group Size: 2
>> + RBG Bitmap: 0x1fff
>> - HARQ process: 0
>> - TPC command for PUCCH: --
>> - Transport blocks swapped: false
>> - Transport block 1 enabled: true
>> + Modulation and coding scheme index: 1
>> + New data indicator: No
>> + Redundancy version: 0
>> - Transport block 2 enabled: false
>> - PRB Bitmap Assignment 0st slot:
>> 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
>> 21, 22, 23, 24,
>> - PRB Bitmap Assignment 1st slot:
>> 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
>> 21, 22, 23, 24,
>> - Number of PRBs: 25
>> - Number of TBs: 1
>> - Transport block: 0
>> -> Modulation type: QPSK
>> -> Transport block size: 904
>> Type new MCS index (0-28) and press Enter: ^CSIGINT received. Exiting...
>> Done
>>
>>
>> If I switched the outputs around,
>>
>>
>>
>> =====ue================================
>>
>> pi at pi-ubuntu:~/srsLTE/build/lib/examples$ ./pdsch_ue -f 2630e6 -r 0x1234
>>
>> Opening RF device with 1 RX antennas...
>>
>> [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501;
>> UHD_3.15.0.git-84-g164d76dc
>>
>> Opening USRP with args:
>>
>> Error opening UHD: code 11
>>
>> Opening bladeRF...
>>
>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>
>> Starting AGC thread...
>>
>> Tunning receiver to 2630.000 MHz
>>
>> set RX frequency to 2629999999
>>
>> Searching for cell...
>>
>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>
>> *Found Cell_id: 0 CP: Normal , DetectRatio=100% PSR=16.90, Power=20.9
>> dBm
>>
>> Found Cell_id: 0 CP: Normal , DetectRatio= 0% PSR=0.00, Power=-inf dBm
>>
>> Found Cell_id: 0 CP: Normal , DetectRatio= 0% PSR=0.00, Power=-inf dBm
>>
>> Decoding PBCH for cell 0 (N_id_2=0)
>>
>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>
>> Setting sampling rate 5.76 MHz
>>
>> Set RX sampling rate 5.76 Mhz, filter BW: 5.00 Mhz
>>
>> - PCI: 0 3.3, FrameCnt: 0, State: 1
>>
>> - Nof ports: 1
>>
>> - CP: Normal
>>
>> - PRB: 25
>>
>> - PHICH Length: Normal
>>
>> - PHICH Resources: 1
>>
>> - SFN: 640
>>
>> Decoded MIB. SFN: 640, offset: 1
>>
>> Tx scheme: Single
>>
>> nof layers: 1
>>
>> nof codewords: 1
>>
>> CFO: +1059.34 Hz
>>
>> RSRP: +37.0 dBm | -inf dBm
>>
>> SNR: +18.5 dB | -inf dB
>>
>> Rb: 0.71 / 0.70 / 1.18 Mbps (net/maximum/processing)
>>
>> PDCCH-Miss: 20.18%
>>
>> PDSCH-BLER: 0.00%
>>
>> TB 0: mcs=1; tbs=904
>>
>> TB 1: mcs=0; tbs=0
>>
>> Press enter maximum printing debug log of 1 subframe.
>>
>> SIGINT received. Exiting....1, FrameCnt: 1231, State: 0 0
>>
>> Hangup layers: 1
>>
>> pi at pi-ubuntu:~/srsLTE/build/lib/examples$
>>
>> CFO: +1059.34 Hz
>>
>> RSRP: +19.6 dBm | -inf dBm
>>
>> SNR: +1.3 dB | -inf dB
>>
>> Rb: 0.44 / 0.00 / 0.01 Mbps (net/maximum/processing)
>>
>> PDCCH-Miss: 26.56%
>>
>> PDSCH-BLER: 0.00%
>>
>> TB 0: mcs=1; tbs=904
>>
>> TB 1: mcs=0; tbs=0
>>
>> Press enter maximum printing debug log of 1 subframe.
>>
>> =====================enb=================================
>> pi at pi:~/srsLTE/build/lib/examples$ ./pdsch_enodeb -f 2630e6
>> linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>> UHD_003.009.007-5-ge8202128
>>
>> Opening RF device...
>> -- Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex...
>> Opening USRP with args: type=b200,master_clock_rate=30.72e6
>> -- Detected Device: B210
>> -- Loading FPGA image: /usr/local/share/uhd/images/usrp_b210_fpga.bin...
>> done
>> -- Operating over USB 3.
>> -- Detecting internal GPSDO.... No GPSDO found
>> -- Initialize CODEC control...
>> -- Initialize Radio control...
>> -- Performing register loopback test... pass
>> -- Performing register loopback test... pass
>> -- Performing CODEC loopback test... pass
>> -- Performing CODEC loopback test... pass
>> -- Asking for clock rate 30.720000 MHz...
>> -- Actually got clock rate 30.720000 MHz.
>> -- Performing timer loopback test... pass
>> -- Performing timer loopback test... pass
>> -- Asking for clock rate 23.040000 MHz...
>> -- Actually got clock rate 23.040000 MHz.
>> -- Performing timer loopback test... pass
>> -- Performing timer loopback test... pass
>> Setting sampling rate 5.76 MHz
>> Set TX gain: 60.0 dB
>> Set TX freq: 2630.00 MHz
>> - Resource Allocation Type: Type 0
>> + Resource Block Group Size: 2
>> + RBG Bitmap: 0x1fff
>> - HARQ process: 0
>> - TPC command for PUCCH: --
>> - Transport blocks swapped: false
>> - Transport block 1 enabled: true
>> + Modulation and coding scheme index: 1
>> + New data indicator: No
>> + Redundancy version: 0
>> - Transport block 2 enabled: false
>> - PRB Bitmap Assignment 0st slot:
>> 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
>> 21, 22, 23, 24,
>> - PRB Bitmap Assignment 1st slot:
>> 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
>> 21, 22, 23, 24,
>> - Number of PRBs: 25
>> - Number of TBs: 1
>> - Transport block: 0
>> -> Modulation type: QPSK
>> -> Transport block size: 904
>> Type new MCS index (0-28) and press Enter: ^CSIGINT received. Exiting...
>> UDone
>>
>>
>>
>> Both the outputs in the pictures seems to be the same. If I let them
>> connected to the computers, and running the commands, the one with enodeb
>> tends to hang showing error uhd 30 is there performance settings i need to
>> change or necessary changes, while the one with ue keeps looping with could
>> not find any cell in this frequency. cell not found after ... trials.
>> Trying again
>>
>> I am not sure if i should take note but using the normal setup, under my
>> enb conf file my log(running sudo srsenb and sudo srsepc) all level is
>> warning while, the ue conf file on the other computer(running sudo srsue)
>> under log all_level is info. I would like to ask if I should ignore it.
>> Besides that, the pcap enable should I enable it?
>> Apologies for my bad knowledge in troubleshooting this project.
>> Thanks for your help.
>> The 17-51-35 image is when I switched around the commands with the two
>> computers.
>>
>>
>> Best Regards,
>> Nehemiah
>>
>>
>> On Tue, May 7, 2019 at 5:37 PM Francisco Paisana <
>> francisco.paisana at softwareradiosystems.com> wrote:
>>
>>> Hey Nehemiah,
>>>
>>> Your uplink signal seems quite weak in the UL. It is always a good idea
>>> to test your physical link first to see if everything is working as
>>> expected. Can you run the "pdsch_ue/pdsch_enb" example, as suggested by
>>> Alejandro, but in both directions? You can find these examples in your
>>> srsLTE build folder (I am gonna assume your build folder is called
>>> "build"). To run the examples, run the following commands:
>>> *computer 1*: ./build/lib/examples/pdsch_ue -f 2630e6 -r 0x1234
>>> *computer 2*: ./build/lib/examples/pdsch_enb -f 2630e6
>>> If the constellation looks ok, swap it around: run the pdsch_ue in
>>> computer 2 and pdsch_enb in computer 1. It should look fine in both
>>> directions. If not, it is either your tx gains are too low in one of the
>>> boards, the distances are too high, or you have a faulty device.
>>>
>>> Regards,
>>> Francisco
>>>
>>> On Mon, May 6, 2019 at 7:23 AM Nehemiah Chan <nehemiahchan1999 at gmail.com>
>>> wrote:
>>>
>>>> Hi Francisco
>>>>
>>>> I do apologise if I am sending you too many files, I am unsure why the
>>>> log files have a different output. I just reopen the terminals and redo
>>>> sudo srsepc, sudo srsenb --log.all_level=info, sudo srsue
>>>> --log.all_level=info. Just to double check, is using the srsenb log file is
>>>> using the computer building sudo srsenb --log.all_level=info, and the other
>>>> computer using sudo srsue --log.all_level=info?
>>>>
>>>>
>>>>
>>>> Best regards,
>>>> Nehemiah
>>>>
>>>>
>>>> On Fri, May 3, 2019 at 9:26 PM Francisco Paisana <
>>>> francisco.paisana at softwareradiosystems.com> wrote:
>>>>
>>>>> Can you also share the UE and eNB logs? To get the logs, follow the
>>>>> steps:
>>>>> - for the UE:
>>>>> run: "sudo srsue --log.all_level=info"
>>>>> the log file can be found in "/tmp/ue.log"
>>>>> - for the eNB:
>>>>> run: "sudo srsenb --log.all_level=info"
>>>>> the enb log file can be found in "/tmp/enb.log"
>>>>>
>>>>> Regards,
>>>>> Francisco
>>>>>
>>>>> On Fri, May 3, 2019 at 8:33 AM ALEJANDRO BLANCO PIZARRO <
>>>>> 100283180 at alumnos.uc3m.es> wrote:
>>>>>
>>>>>> Hi Nehemiah,
>>>>>>
>>>>>> From my experience when you have several unsuccessful random access
>>>>>> is probably because of insuficient power. Do you have LTE compliant
>>>>>> antennas?
>>>>>>
>>>>>> Check the power from the side of the UE, with pdsch_ue -f (frequency
>>>>>> of the enb) in example folder. To have a proper communication you
>>>>>> should have more than 5dB of SNR.
>>>>>>
>>>>>> BTW, I would use the usrp as a enb and a bladerf as a UE, the usrp
>>>>>> was more tested as a enb.
>>>>>>
>>>>>> Good luck! Best,
>>>>>> Alejandro
>>>>>>
>>>>>> El vie., 3 may. 2019 9:00, Nehemiah Chan <nehemiahchan1999 at gmail.com>
>>>>>> escribió:
>>>>>>
>>>>>>> Hi everyone, I am totally new to srslte let alone linux, I am
>>>>>>> currently trying to connect the laptop running with sudo srsue to go into
>>>>>>> the internet, while building sudo srsepc and sudo srsenb simultaneously. Do
>>>>>>> correct me if I am wrong, before using a mobile device as the ue, I heard
>>>>>>> it is possible to connect the computer running the sudo srsue to connect to
>>>>>>> the internet( from the srslte) . Before that, I have entered several
>>>>>>> configurations inside using IP address 172.16.0.2. I am able to see the
>>>>>>> tun_srsue with the ip address with 172.16.0.2 while looking for active
>>>>>>> network connections while running the three commands. I have looked into
>>>>>>> several posts in srslte regarding this matter, please do let me know if I
>>>>>>> should amend. I will appreciate if anyone can add the steps too. I was told
>>>>>>> to make changes to the epc.conf file, however I am only able to identify
>>>>>>> srsue/ srsenb. Down below are the outputs while building sudo srsepc, sudo
>>>>>>> srsenb and sudo srsue. If you do need any necessary files please let me
>>>>>>> know. Thanks
>>>>>>>
>>>>>>> pi at pi-ubuntu:~$ sudo srsenb
>>>>>>>
>>>>>>> Built in Release mode using commit 429ee901 on branch master.
>>>>>>>
>>>>>>> --- Software Radio Systems LTE eNodeB ---
>>>>>>>
>>>>>>> Reading configuration file /home/pi/.config/srslte/enb.conf...
>>>>>>> [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501;
>>>>>>> UHD_3.15.0.git-84-g164d76dc
>>>>>>> Opening USRP with args:
>>>>>>> Error opening UHD: code 11
>>>>>>> Opening bladeRF...
>>>>>>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>>>>>> Setting frequency: DL=2685.0 Mhz, UL=2565.0 MHz
>>>>>>> set TX frequency to 2684999936
>>>>>>> set RX frequency to 2564999936
>>>>>>> Setting Sampling frequency 11.52 MHz
>>>>>>> Set RX sampling rate 11.52 Mhz, filter BW: 10.00 Mhz
>>>>>>>
>>>>>>> ==== eNodeB started ===
>>>>>>> Type <t> to view trace
>>>>>>> RACH: tti=1151, preamble=7, offset=0, temp_crnti=0x46
>>>>>>> SCHED: Could not transmit RAR within the window (RA TTI=1151,
>>>>>>> Window=10, Now=1165)
>>>>>>> RACH: tti=1181, preamble=49, offset=0, temp_crnti=0x47
>>>>>>> SCHED: Could not transmit RAR within the window (RA TTI=1181,
>>>>>>> Window=10, Now=1195)
>>>>>>> RACH: tti=1211, preamble=23, offset=0, temp_crnti=0x48
>>>>>>> SCHED: Could not transmit RAR within the window (RA TTI=1211,
>>>>>>> Window=10, Now=1225)
>>>>>>> Disconnecting rnti=0x46.
>>>>>>> RACH: tti=1241, preamble=0, offset=0, temp_crnti=0x49
>>>>>>> SCHED: Could not transmit RAR within the window (RA TTI=1241,
>>>>>>> Window=10, Now=1260)
>>>>>>> RACH: tti=1271, preamble=6, offset=0, temp_crnti=0x4a
>>>>>>> Disconnecting rnti=0x47.
>>>>>>> Disconnecting rnti=0x48.
>>>>>>> Disconnecting rnti=0x49.
>>>>>>> User 0x4a connected
>>>>>>> Disconnecting rnti=0x4a.
>>>>>>>
>>>>>>> pi at pi-ubuntu:~$ sudo srsepc
>>>>>>>
>>>>>>> Built in Release mode using commit 429ee901 on branch master.
>>>>>>>
>>>>>>>
>>>>>>> --- Software Radio Systems EPC ---
>>>>>>>
>>>>>>> Reading configuration file /home/pi/.config/srslte/epc.conf...have
>>>>>>> consulted others some tell me to configure the
>>>>>>> HSS Initialized.
>>>>>>> MME GTP-C Initialized
>>>>>>> MME Initialized. MCC: 0xf001, MNC: 0xff01
>>>>>>> SP-GW Initialized.
>>>>>>> Received S1 Setup Request.
>>>>>>> S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b
>>>>>>> S1 Setup Request - MCC:001, MNC:01, PLMN: 61712
>>>>>>> S1 Setup Request - TAC 7, B-PLMN 0
>>>>>>> S1 Setup Request - Paging DRX 2
>>>>>>> Sending S1 Setup Response
>>>>>>> Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST
>>>>>>> Received Initial UE message -- Attach Request
>>>>>>> Attach request -- GUTI Style Attach request
>>>>>>> Attach request -- M-TMSI: 0x7ec9d66e
>>>>>>> Attach request -- eNB-UE S1AP Id: 1
>>>>>>> Attach request -- Attach type: 1have consulted others some tell me
>>>>>>> to configure the
>>>>>>> Attach Request -- UE Network Capabilities EEA: 11100000
>>>>>>> Attach Request -- UE Network Capabilities EIA: 01100000
>>>>>>> Attach Request -- MS Network Capabilities Present: false
>>>>>>> PDN Connectivity Request -- EPS Bearer Identity requested: 0
>>>>>>> PDN Connectivity Request -- Procedure Transaction Id: 1
>>>>>>> PDN Connectivity Request -- ESM Information Transfer requested: false
>>>>>>> UL NAS: Received Identity Response
>>>>>>> ID Response -- IMSI: 001010123456789
>>>>>>> Downlink NAS: Sent Authentication Request
>>>>>>> UL NAS: Received Authentication Response
>>>>>>> Authentication Response -- IMSI 001010123456789
>>>>>>> UE Authentication Accepted.
>>>>>>> Generating KeNB with UL NAS COUNT: 0
>>>>>>> Downlink NAS: Sending NAS Security Mode Command.
>>>>>>> UL NAS: Received Security Mode Complete
>>>>>>> Security Mode Command Complete -- IMSI: 001010123456789
>>>>>>> Getting subscription information -- QCI 7
>>>>>>> Sending Create Session Request.
>>>>>>> Creating Session Response -- IMSI: 1010123456789
>>>>>>> Creating Session Response -- MME control TEID: 1
>>>>>>> SPGW: Allocated Ctrl TEID 1
>>>>>>> SPGW: Allocated User TEID 1
>>>>>>> SPGW: Allocate UE IP 172.16.0.2
>>>>>>> Received Create Session Response
>>>>>>> Create Session Response -- SPGW control TEID 1
>>>>>>> Create Session Response -- SPGW S1-U Address: 127.0.1.100
>>>>>>> SPGW Allocated IP 172.16.0.2 to ISMI 001010123456789
>>>>>>> Adding attach accept to Initial Context Setup Request
>>>>>>> Initial Context Setup Request -- eNB UE S1AP Id 1, MME UE S1AP Id
>>>>>>> 1have consulted others some tell me to configure the
>>>>>>> Initial Context Setup Request -- E-RAB id 5
>>>>>>> Initial Context Setup Request -- S1-U TEID 0x1. IP 127.0.1.100
>>>>>>> Initial Context Setup Request -- S1-U TEID 0x1. IP 127.0.1.100
>>>>>>> Initial Context Setup Request -- QCI 7
>>>>>>> Received Initial Context Setup Response
>>>>>>> E-RAB Context Setup. E-RAB id 5
>>>>>>> E-RAB Context -- eNB TEID 0x4a0003; eNB GTP-U Address 127.0.1.1
>>>>>>> UL NAS: Received Attach Complete
>>>>>>> Unpacked Attached Complete Message. IMSI 1010123456789
>>>>>>> Unpacked Activate Default EPS Bearer message. EPS Bearer id 5
>>>>>>> Sending EMM Information
>>>>>>> Received UE Context Release Request. MME-UE S1AP Id 1
>>>>>>> There are active E-RABs, send release access bearers request
>>>>>>> UE is ECM IDLE.
>>>>>>> Received UE Context Release Complete. MME-UE S1AP Id 1
>>>>>>> UE is not ECM connected. No need to release S1-U. MME UE S1AP Id 1
>>>>>>> UE Context Release Completed.
>>>>>>> SCTP Association Shutdown. Association: 24
>>>>>>> Deleting eNB context. eNB Id: 0x19b
>>>>>>> Releasing UEs context
>>>>>>> Releasing UE ECM context. UE-MME S1AP Id: 0
>>>>>>> ^CDeleting UE EMM context. IMSI: 001010123456789
>>>>>>> Deleting UE context in HSS. IMSI: 001010123456780
>>>>>>> Deleting UE context in HSS. IMSI: 001010123456789
>>>>>>>
>>>>>>> pi at pi:~$ sudo srsuehave consulted others some tell me to configure
>>>>>>> the
>>>>>>>
>>>>>>> linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>>>>>>> UHD_003.009.007-5-ge8202128
>>>>>>>
>>>>>>> Reading configuration file /home/pi/.config/srslte/ue.conf...
>>>>>>>
>>>>>>> Built in Release mode using commit 429ee90 on branch master.
>>>>>>>
>>>>>>> --- Software Radio Systems LTE UE ---
>>>>>>>
>>>>>>> Opening RF device with 1 RX antennas...
>>>>>>>
>>>>>>> Opening USRP with args: type=b200,master_clock_rate=30.72e6
>>>>>>>
>>>>>>> -- Detected Device: B210
>>>>>>>
>>>>>>> -- Operating over USB 3.
>>>>>>>
>>>>>>> -- Initialize CODEC control...
>>>>>>>
>>>>>>> -- Initialize Radio control...
>>>>>>>
>>>>>>> -- Performing register loopback test... pass
>>>>>>>
>>>>>>> -- Performing register loopback test... pass
>>>>>>>
>>>>>>> -- Performing CODEC loopback test... pass
>>>>>>>
>>>>>>> -- Performing CODEC loopback test... pass
>>>>>>>
>>>>>>> -- Asking for clock rate 30.720000 MHz...
>>>>>>>
>>>>>>> -- Actually got clock rate 30.720000 MHz.
>>>>>>>
>>>>>>> -- Performing timer loopback test... pass
>>>>>>>
>>>>>>> -- Performing timer loopback test... pass
>>>>>>>
>>>>>>> Waiting PHY to initialize...
>>>>>>>
>>>>>>> ...
>>>>>>>
>>>>>>> Attaching UE...
>>>>>>>
>>>>>>> Searching cell in DL EARFCN=3400, f_dl=2685.0 MHz, f_ul=2565.0 MHz
>>>>>>>
>>>>>>> ...
>>>>>>>
>>>>>>> Found Cell: PCI=1, PRB=50, Ports=1, CFO=-0.4 KHz
>>>>>>>
>>>>>>> Found PLMN: Id=00101, TAC=7
>>>>>>>
>>>>>>> Setting PDN protocol to IPv4
>>>>>>>
>>>>>>> Random Access Transmission: seq=7, ra-rnti=0x2
>>>>>>>
>>>>>>> Random Access Transmission: seq=49, ra-rnti=0x2
>>>>>>>
>>>>>>> Random Access Transmission: seq=23, ra-rnti=0x2
>>>>>>>
>>>>>>> Random Access Transmission: seq=0, ra-rnti=0x2
>>>>>>>
>>>>>>> Random Access Transmission: seq=6, ra-rnti=0x2
>>>>>>>
>>>>>>> RRC Connected
>>>>>>>
>>>>>>> Random Access Complete. c-rnti=0x4a, ta=0
>>>>>>>
>>>>>>> Network attach successful. IP: 172.16.0.2
>>>>>>>
>>>>>>> Software Radio Systems LTE (srsLTE)
>>>>>>>
>>>>>>> Warning: Detected Radio-Link Failure
>>>>>>>
>>>>>>> RRC Connection Reestablishment
>>>>>>>
>>>>>>> RRC IDLE
>>>>>>>
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Nehemiah
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> srslte-users mailing list
>>>>>>> srslte-users at lists.softwareradiosystems.com
>>>>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>>>>
>>>>>> _______________________________________________
>>>>>> srslte-users mailing list
>>>>>> srslte-users at lists.softwareradiosystems.com
>>>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>>>
>>>>> _______________________________________________
>> srslte-users mailing list
>> srslte-users at lists.softwareradiosystems.com
>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190510/11092716/attachment.htm>
More information about the srsran-users
mailing list