top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

5g tunnel allocation of standalone and non standalone scenarios

+1 vote
281 views

Hi,

Could you help me with the 5g attach call flow, (attach) with regards to GTP tunnel allocation. (for both standalone and non standalone cases). with the CU-DU split.
I am looking for various scenarios, including, MCG, SCG and split bearers also,

I am also trying to understand, how this affects the CU split (into CU-CP and CU-UP) with the E1 interface..

thanks,
Pdk

posted Oct 16, 2018 by Pdk

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

I was comparing UE Context Release Cmd (defined in 36.413) with the NG-AP (38.413) UE Context Release Cmd. I couldn't realize the scenario in which only the AMF allocated UE NG-AP ID will be included in UE Cntxt Release Cmd. In LTE, both the S1-AP IDs were mandatory to send in UE Ctxt Rel Cmd from MME to eNodeB.
It would be helpful if someone can provide the reason.
Thanks in advance.

0 votes

In LTE, tracking area code was two bytes long but in 5G, it is three bytes long.
What could be the reason of doing so ?

+1 vote

I was going through the security specification of 5G network and stopped at a point where it was mentioned that UE shall support integrity protection of user data along with the integrity protection of RRC and NAS-Signalling. Section 5.1.3.1 also mentions that integrity protection of the user data between UE and gNB is optional to use.
I want to know that for which cases/scenarios, it would be needed to enable integrity protection for user data between UE and gNB ?
Enabling both integrity and ciphering for the user data would be an overhead, therefore I started thinking about scenarios/cases.

...