What would be the UE capabilities required for Uplink Carrier aggregation implementation and how UL allocation happens?
Hi,
Rel 10 UE supports UL carrier aggregation , there is no separate capability required. UL allocation can be same carrier or cross carrier, but If Secondary cell is aggregated then it should be DL & UL, UL alone aggregation is not allowed in CA.
I have a 3 part question 1) How does the EnodeB know if the user equipment supports carrier aggregation or not? 2) If a UE does not support carrier aggregation does it mean it’s a Release 9 or lesser compliant UE? 3) If the answer to question 2 is yes , then how does the UE not supporting carrier aggregation(release 9 or lesser UE) decode a DCI message sent from a EnodeB that is currently supporting LTE A(Release10) , as the DCI message (say DCI format 0) contains extra bits?
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.
What are the messages are exchanged between UE and network to evaluate the approximate position of the UE ?
In attach request, UE sends UE network capability which contains the list of security algorithms can be used to enable security between UE and network node. My question is, when UE already knows its supported algorithms then why MME resend the same list of security algorithm to UE in security mode command ? What would be the reasoning behind it ?
