3GPP TS V (). 2. Release 8. Keywords. UMTS, radio. 3GPP. Postal address. 3GPP support office address. Route des. Radio Resource Control (RRC); Protocol specification (3GPP TS version Release 11) Ocr ABBYY FineReader Ppi Release 8. 2. 3GPP TS V (). Keywords UMTS, radio. 3GPP Postal address 3GPP support office address Route des Lucioles – Sophia.
|Country:||United Arab Emirates|
|Published (Last):||26 February 2009|
|PDF File Size:||12.20 Mb|
|ePub File Size:||16.68 Mb|
|Price:||Free* [*Free Regsitration Required]|
Followings are not directly related to UE Capability, but sometimes we see various issues caused by these message correlation. Why we need to worry about the size limitation of RRC message?
Sometimes UE information says ‘Supported’ but in reality does not working correct. What would be the solution telease handling this kind of too over-sized message?
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10 – Techplayon
Followings are list of topics that will be dealt with in this page or a few other pages that are related to UE capability Information. Another possible solution seemingly better solution would be to limit the scope of the information that UE report in UE Capability Information message. Followings are some of the complete message example for UE Capability Information message. Network request UE to send capability information.
With this, Network can force UE to send the only re,ease information that are necessary to the current Network.
releqse One brutal solution would be to reserve super-large message buffer size and ensure that your ASN decoder works properly for such a super large tree structure. The process is very simple as shown below. Followings are some of common items you’d better check.
Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page. Take this as a guideline but don’t trust too much. This list would get longer as the technology evolves. It informs on all the details of its capabilities.
The current several hundred different combination is not with 3CC CA. In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE. As a result, interpreting the contents of the message has become pretty complicated.
If the UE support full capability of Rel 13 and a lot of band combination. Following is how UE Capability Enquiry works.
Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10
The real explosion of the size came out with the support of Carrier Aggregation. How long the message can be? But the size increase by FGI was minor. Also it would be a good idea to check these information first before you test anything on Measurement, InterRAT.
However, as higher carrier aggregation i. So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated. So I recommend you to check before troubleshoot especially for radio stack issue. The more you know of the contents gelease more you can understand about the UE and the better position you are at for troubleshooting.
I am not aware if there is any explicit size limit for any RRC message.
3GPP TS (1 of 18) – E-UTRA RRC
But I would suggest you to understand at least on how to interprete the contents of the highlighted items. As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’. We haven’t even thought of this for most of the case, but we start worrying about size limitation of RRC message as UE Capability Information message gets almost exploded in terms of message length size.
Very high level view of UE Capability Information message structure is shown below.
I want to show how this message has expanded as LTE evolves in following table. The root cause was a kind of message buffer overflow, meaning that the size of the incoming signaling message hit the size of memory allocated to store the message.