srsran / srsRAN_4G

Open source SDR 4G software suite from Software Radio Systems (SRS) https://docs.srsran.com/projects/4g
https://www.srsran.com
GNU Affero General Public License v3.0
3.43k stars 1.13k forks source link

multiuser communication, srsRAN 21.04, one EPC and ENB connects two UEs #723

Closed zsy9512 closed 2 years ago

zsy9512 commented 3 years ago

Issue Description

[Describe the issue in detail] Our goal: one EPC and ENB connects two UEs at the same time

Hello, we were running srsRAN with release 21.04, and we got a problem about multi users. We tried to connect one EPC and ENB with two UEs, but we failed. For example, we connected UE1 with EPC and ENB, it worked well. However, when we connected UE2 with EPC and ENB, UE1 was disconnected in few seconds, which meant UE1 was disconnected and UE2 was connected. We could not connect the two UEs with EPC and ENB at the same time.

We thought there were some configurations that need to be set for multiuser communication, and tried some ways, but they did not work.

Setup Details

[Specify details of the test setup. This would help us reproduce the problem reliably] e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions

**Our orders are as follows:(we did not change ue.conf. all orders are default. srsRAN 21.04)

first: PC1 with B210:(we consider it as a base station) sudo srsepc sudo srsenb

then: PC2 with B210:(we consider it as an UE) sudo srsue (PC2 is connected)

then: PC3 with B210:(we consider it as an UE) sudo srsue (PC2 is disconnected, PC3 is connected)

so the problem is that we can not make PC2 and PC3 connect PC1 at the same time.**

Expected Behavior

[What you expect to happen] we want PC1 can connect PC2 and PC3 at the same time.

Actual Behaviour

[What happens instead e.g. error message] only one PC can connect to PC1

Steps to reproduce the problem

[Tell us how to reproduce this issue e.g. RF setup, application config files]

Additional Information

[Any additional information, configuration or data that might be necessary to reproduce the issue] PC2 logs: sudo srsue Reading configuration file /home/shuangc/.config/srsran/ue.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 1c6dd8c4a on branch HEAD.

Opening 1 channels in RF device=default with args=default [INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; UHD_3.14.0.HEAD-0-g6875d061 [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. Waiting PHY to initialize ... done! Attaching UE... Starting plot for worker_id=0 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' . Found Cell: Mode=FDD, PCI=1, PRB=50, Ports=2, CFO=0.1 KHz Found PLMN: Id=00101, TAC=7 Random Access Transmission: seq=49, tti=3381, ra-rnti=0x2 RRC Connected Random Access Complete. c-rnti=0x9a, ta=1 Network attach successful. IP: 172.16.0.4 Software Radio Systems RAN (srsRAN) 8/9/2021 8:1:21 TZ:0 Scheduling request failed: releasing RRC connection... Random Access Transmission: seq=4, tti=7061, ra-rnti=0x2 Random Access Transmission: seq=7, tti=7081, ra-rnti=0x2 Random Access Complete. c-rnti=0x9a, ta=1 Scheduling request failed: releasing RRC connection... Random Access Transmission: seq=12, tti=4541, ra-rnti=0x2 Random Access Complete. c-rnti=0x9a, ta=1 Scheduling request failed: releasing RRC connection... Random Access Transmission: seq=31, tti=9621, ra-rnti=0x2 Random Access Complete. c-rnti=0x9a, ta=1

PC1 epc log: 07:38:46.302618 [EPC ] [I]

Built in Release mode using commit 1c6dd8c4a on branch HEAD.

--- Software Radio Systems EPC log ---

07:38:46.302623 [EPC ] [I] Using binary srsepc with arguments: 07:38:46.302655 [HSS ] [I] Opened DB file: /home/zsy/.config/srsran/user_db.csv 07:38:46.302688 [HSS ] [I] HSS Initialized. DB file /home/zsy/.config/srsran/user_db.csv, MCC: 61441, MNC: 65281 07:38:46.302705 [S1AP ] [I] S1-MME Initializing 07:38:46.302734 [S1AP ] [I] S1AP Initialized 07:38:46.302734 [MME GTPC] [I] Initializing MME S11 interface. 07:38:46.302739 [MME GTPC] [I] MME S11 Initialized 07:38:46.302742 [MME GTPC] [I] MME GTP-C Initialized 07:38:46.302743 [S1AP ] [I] MME Initialized. MCC: 0xf001, MNC: 0xff01 07:38:46.302759 [GTPU ] [I] TUN file descriptor = 6 07:38:46.304346 [GTPU ] [I] Initialized SGi interface 07:38:46.304356 [GTPU ] [I] S1-U socket = 7 07:38:46.304359 [GTPU ] [I] S1-U IP = 127.0.1.100, Port = 2152 07:38:46.304361 [GTPU ] [I] Initialized S1-U interface 07:38:46.304362 [GTPU ] [I] SPGW GTP-U Initialized. 07:38:46.304367 [SPGW GTPC] [I] Initializing SPGW S11 interface. 07:38:46.304496 [SPGW GTPC] [I] SPGW S11 Initialized. 07:38:46.304501 [SPGW ] [I] SP-GW Initialized. 07:38:46.328348 [GTPU ] [I] IPv6 not supported yet. 07:38:50.824218 [GTPU ] [I] IPv6 not supported yet. 07:38:52.428339 [S1AP ] [I] Received S1AP msg. Size: 49 07:38:52.428425 [S1AP ] [I] Received Initiating PDU 07:38:52.428428 [S1AP ] [I] Received S1 Setup Request. 07:38:52.428441 [S1AP ] [I] Received S1 Setup Request. 07:38:52.428450 [S1AP ] [I] S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b 07:38:52.428452 [S1AP ] [I] S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 07:38:52.428455 [S1AP ] [I] S1 Setup Request - TAC 7, B-PLMN 0xf110 07:38:52.428464 [S1AP ] [I] Adding new eNB context. eNB ID 411 07:38:52.428527 [S1AP ] [I] Sending S1 Setup Response 07:38:54.029579 [S1AP ] [I] Received S1AP msg. Size: 59 07:38:54.029607 [S1AP ] [I] Received Initiating PDU 07:38:54.029610 [S1AP ] [I] Received Initial UE Message. 07:38:54.029622 [S1AP ] [I] Initial UE message: NAS Message Type Unknown 07:38:54.029628 [S1AP ] [I] Received Initial UE message -- Service Request 07:38:54.029630 [NAS ] [I] Service request -- S-TMSI 0xbbeabaf 07:38:54.029635 [NAS ] [I] Service request -- eNB UE S1AP Id 1 07:38:54.029642 [NAS ] [E] Could not find IMSI from M-TMSI. M-TMSI 0xbbeabaf 07:38:56.599572 [S1AP ] [I] Received S1AP msg. Size: 98 07:38:56.599597 [S1AP ] [I] Received Initiating PDU 07:38:56.599599 [S1AP ] [I] Received Initial UE Message. 07:38:56.599610 [S1AP ] [I] Initial UE message: LIBLTE_MME_MSG_TYPE_ATTACH_REQUEST 07:38:56.599615 [S1AP ] [I] Received Initial UE message -- Attach Request 07:38:56.599637 [NAS ] [I] Attach request -- M-TMSI: 0xbbeabad 07:38:56.599642 [NAS ] [I] Attach request -- eNB-UE S1AP Id: 2 07:38:56.599645 [NAS ] [I] Attach request -- Attach type: 1 07:38:56.599650 [NAS ] [I] Attach Request -- UE Network Capabilities EEA: 11110000 07:38:56.599655 [NAS ] [I] Attach Request -- UE Network Capabilities EIA: 01110000 07:38:56.599658 [NAS ] [I] Attach Request -- MS Network Capabilities Present: false 07:38:56.599662 [NAS ] [I] PDN Connectivity Request -- EPS Bearer Identity requested: 0 07:38:56.599665 [NAS ] [I] PDN Connectivity Request -- Procedure Transaction Id: 1 07:38:56.599670 [NAS ] [I] PDN Connectivity Request -- ESM Information Transfer requested: false 07:38:56.599677 [NAS ] [I] Packing Identity Request 07:38:56.639301 [S1AP ] [I] Received S1AP msg. Size: 57 07:38:56.639312 [S1AP ] [I] Received Initiating PDU 07:38:56.639314 [S1AP ] [I] Received Uplink NAS Transport Message. 07:38:56.639317 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:38:56.639318 [S1AP ] [I] UL NAS: Received Identity Response 07:38:56.639323 [NAS ] [I] ID response -- IMSI: 001010123456789 07:38:56.639348 [NAS ] [I] Packing Authentication Request 07:38:56.639389 [NAS ] [I] Downlink NAS: Sent Authentication Request 07:38:56.671548 [S1AP ] [I] Received S1AP msg. Size: 57 07:38:56.671556 [S1AP ] [I] Received Initiating PDU 07:38:56.671557 [S1AP ] [I] Received Uplink NAS Transport Message. 07:38:56.671557 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_PLAIN_NAS, mac_vaild: no, msg_encrypted: no 07:38:56.671558 [S1AP ] [I] UL NAS: Received Authentication Response 07:38:56.671566 [NAS ] [I] Authentication Response -- IMSI 001010123456789 07:38:56.671568 [NAS ] [I] Authentication response -- RES 0000: 40 6a 00 21 34 18 50 0b 07:38:56.671569 [NAS ] [I] Authentication response -- XRES 0000: 40 6a 00 21 34 18 50 0b 07:38:56.671571 [NAS ] [I] UE Authentication Accepted. 07:38:56.671572 [NAS ] [I] Packing Security Mode Command 07:38:56.671575 [NAS ] [I] Key NAS Encryption (k_nas_enc) 0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07:38:56.671576 [NAS ] [I] Key NAS Integrity (k_nas_int) 0000: 35 b0 f1 9e 72 b8 3b 0c 01 87 ec 1f 5f ea e9 1c 0010: 23 74 f4 73 06 11 59 0c e2 89 69 8b af fc 8d eb 07:38:56.671578 [NAS ] [I] Generating KeNB with UL NAS COUNT: 0 07:38:56.671584 [NAS ] [I] Key eNodeB (k_enb) 0000: dd 9c d9 c9 5b c3 13 8a fc 34 ce 0d b3 80 d3 03 0010: ff af 2c 53 f5 d5 ed e2 5a 15 0f 2f 4c bb f2 d0 07:38:56.691604 [S1AP ] [I] Received S1AP msg. Size: 54 07:38:56.691610 [S1AP ] [I] Received Initiating PDU 07:38:56.691611 [S1AP ] [I] Received Uplink NAS Transport Message. 07:38:56.691709 [NAS ] [I] Integrity check ok. Local: count=0, Received: count=0 07:38:56.691712 [S1AP ] [I] UL NAS: sec_hdr_type: LIBLTE_MME_SECURITY_HDR_TYPE_INTEGRITY_AND_CIPHERED_WITH_NEW_EPS_SECURITY_CONTEXT, mac_vaild: yes, msg_encrypted: yes 07:38:56.691712 [S1AP ] [I] UL NAS: Received Security Mode Complete 07:38:56.691721 [NAS ] [I] Security Mode Command Complete -- IMSI: 001010123456789 07:38:56.691725 [HSS ] [I] Found User 001010123456789 07:38:56.691729 [MME GTPC] [I] Sending Create Session Request. 07:38:56.691734 [MME GTPC] [I] Next MME control TEID: 2 07:38:56.691736 [MME GTPC] [I] Allocated MME control TEID: 1 07:38:56.691769 [SPGW GTPC] [I] SPGW Received Create Session Request 07:38:56.691772 [SPGW GTPC] [I] Creating new GTP-C context 07:38:56.691777 [SPGW GTPC] [I] SPGW: get_new_ue_ipv4 pool ip addr 172.16.0.2 07:38:56.691788 [SPGW GTPC] [I] Sending Create Session Response 07:38:56.691799 [MME GTPC] [I] Received Create Session Response 07:38:56.691804 [MME GTPC] [I] MME GTPC Ctrl TEID 1, IMSI 1010123456789 07:38:56.691809 [MME GTPC] [I] Create Session Response -- SPGW control TEID 1 07:38:56.691813 [MME GTPC] [I] Create Session Response -- SPGW S1-U Address: 127.0.1.100 07:38:56.691819 [S1AP ] [I] Preparing to send Initial Context Setup request 07:38:56.691829 [S1AP ] [I] Initial Context Setup Request -- Key eNB (k_enb) 0000: dd 9c d9 c9 5b c3 13 8a fc 34 ce 0d b3 80 d3 03 0010: ff af 2c 53 f5 d5 ed e2 5a 15 0f 2f 4c bb f2 d0 07:38:56.691833 [S1AP ] [I] Adding attach accept to Initial Context Setup Request 07:38:56.691834 [NAS ] [I] Packing Attach Accept 07:38:56.691834 [NAS ] [I] Attach Accept -- MCC 0xf001, MNC 0xff01 07:38:56.691949 [NAS ] [I] Packed Attach Accept 07:38:56.691972 [S1AP ] [I] Initial Context -- S1-U TEID 0x1. IP 127.0.1.100 07:38:56.691974 [S1AP ] [I] Initial Context Setup Request -- eNB UE S1AP Id 2, MME UE S1AP Id 2 07:38:56.691975 [S1AP ] [I] Initial Context Setup Request -- E-RAB id 5 07:38:56.691976 [S1AP ] [I] Initial Context Setup Request -- S1-U TEID 0x1. IP 127.0.1.100 07:38:56.691977 [S1AP ] [I] Initial Context Setup Request -- S1-U TEID 0x1. IP 127.0.1.100 07:38:56.691983 [S1AP ] [I] Initial Context Setup Request -- QCI 7 07:38:56.739577 [S1AP ] [I] Received S1AP msg. Size: 67 07:38:56.739585 [S1AP ] [I] Received Initiating PDU 07:38:56.739585 [S1AP ] [I] Ignoring UE capability Info Indication. 07:38:56.940222 [S1AP ] [I] Received S1AP msg. Size: 38 07:38:56.94023

PC1 enb log: ==== eNodeB started === Type to view trace Setting frequency: DL=2680.0 Mhz, UL=2560.0 MHz for cc_idx=0 nof_prb=50 RACH: tti=5621, cc=0, preamble=5, offset=43, temp_crnti=0x46 RACH: tti=5621, cc=0, preamble=7, offset=1, temp_crnti=0x47 RACH: tti=5621, cc=0, preamble=10, offset=7, temp_crnti=0x48 Disconnecting rnti=0x48. Disconnecting rnti=0x46. User 0x47 connected RACH: tti=3861, cc=0, preamble=21, offset=43, temp_crnti=0x49 RACH: tti=3861, cc=0, preamble=23, offset=1, temp_crnti=0x4a RACH: tti=3861, cc=0, preamble=26, offset=7, temp_crnti=0x4b Disconnecting rnti=0x4b. Disconnecting rnti=0x49. User 0x4a connected

andrepuschmann commented 2 years ago

Impossible to tell without proper logs. Please make sure RF is fine for each UE individually before attaching two. I am closing the issue in the meanwhile. Please feel free to reopen if you still see issues.

umapriyam commented 2 years ago

whats the max no of UE srs supports here?

rwangu07 commented 2 years ago

whats the max no of UE srs supports here?

Did you find the number ? Even im not able to connect 2 UE's

frankist commented 2 years ago

The LTE eNB can work in real time for more than 2 UEs. Currently, the only limit is either your computer or the constant MAX_NOF_UES.

pemo75 commented 8 months ago

MAX_NOF_UES

hello frankist could you please tell me where can i find MAX_NOF_UES? can i change it to any number i want?