TS – V – LTE; Evolved Universal Terrestrial Radio Access Protocol specification (3GPP TS version Release 11). Descriptor and Table of Contents (1 of 18) for 3GPP TS – Evolved Universal Terrestrial Radio Access (E-UTRA) – Radio V /06 p. Application No. Publication No. Country of registration. LTE Release 11;. LTE Release TS ;. TS ;. TS ;. TS
|Published (Last):||25 January 2018|
|PDF File Size:||1.57 Mb|
|ePub File Size:||5.2 Mb|
|Price:||Free* [*Free Regsitration Required]|
3GPP TS (1 of 18) – E-UTRA RRC
I am not aware if there is any explicit size limit for any RRC message. Stage 1 for EHNB. Earthquake and Tsunami Warning System. Technical specification TS Initial planned Release: As a result, interpreting the contents of the message has become pretty complicated.
So I would split the message into a couple of categories as shown below and post separate pages for each of the categories. I want to show how this message has expanded as LTE evolves in following table. Himke Van der Velde.
Specification has been successfully withdrawn. It informs on all the details of its capabilities. When LTE first came out, this process was very simple, but as LTE evolves the information that are required gets larger and complicated. Rrelease Improvements for Machine-Type Communications.
Why we need to worry about the size limitation of RRC message? Take this as a guideline but don’t trust too much.
www.3gpp.org – /ftp/Specs/archive/36_series/36.331/
Followings are some of the complete message example for UE Capability Information message. Terminal device, wireless communication system, and wireless communication method. No records to display. Editorial correction to ASN.
Positioning Support for LTE. Are you sure you want delete specification? Meetings Version Upload date Comment. Further enhancements to H e NB mobility – Part 3.
Under change control Type: New version to fix ASN. Sometimes UE information says ‘Supported’ but in reality does not working correct. Followings are not directly related to UE Capability, but sometimes we see various issues caused by these message correlation.
Carrier Aggregation for LTE. Very high level view of UE Capability Information message structure is shown below. What would be the solution for handling this kind of too over-sized message? Public land mobile network resolution in a shared network and a dedicated network.
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. Method of reporting measurement result in wireless communicattion system and apparatus for the same.
Security aspects of MBMS. However, as higher carrier aggregation i. Deleted – Rdlease part: As a result, I see much more issues related to ‘lack of capability’ or ‘mismatch between UE capability report and real implementation’.
But I would suggest you to understand at least on how to interprete the contents of the highlighted items.
But the size increase by FGI was minor. With this, Network can force UE to send the only capability information that are necessary to the current Network. Architecture aspects of EHNB. The real explosion of the size came out with the support of Carrier Aggregation.
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. How long the message can be? Reordering of fields in RRCCo