36.331 RELEASE 8 PDF

I am not aware if there is any explicit size limit for any RRC message. Latency reductions for LTE. But the size increase by FGI was minor. UL multiple antenna transmission for LTE.

Author:Faezshura Kajiran
Country:Madagascar
Language:English (Spanish)
Genre:Music
Published (Last):27 May 2007
Pages:288
PDF File Size:15.95 Mb
ePub File Size:4.9 Mb
ISBN:683-5-53826-387-6
Downloads:52108
Price:Free* [*Free Regsitration Required]
Uploader:Malanos



But I would suggest you to understand at least on how to interprete the contents of the highlighted items. UE reports the information to NW as requested.

I want to show how this message has expanded as LTE evolves in following table. However, as higher carrier aggregation i. If the UE support full capability of Rel 13 and a lot of band combination.

Followings are list of topics that will be dealt with in this releasse or a few other pages that are related to UE capability Information.

Rrelease it would be a good idea to check these information first before you test anything on Measurement, InterRAT. The root cause was a kind of message releawe overflow, meaning that the size of the incoming signaling message hit the size of memory allocated to store the message.

What would be the solution for handling this kind of too over-sized erlease But the size increase by FGI was minor. 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 would split the message into a couple of categories as shown below and post separate pages for each of the categories. Since the message is too long and too complicated, it would be tricky to describe all of the contents in the single page.

The process is very simple as shown below. Following is how UE Capability Enquiry works. The real explosion of the reoease came out with the support of Carrier Aggregation. How long the message can be? I am not aware if there is any explicit size limit releas any RRC message.

So I recommend you to check before troubleshoot especially for radio stack issue. In some case, we spend pretty much time and effort to troubleshoot something which is not supported by UE. 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? As a result, interpreting the contents of the message has become reelase complicated. This list would get longer as the technology evolves.

The Enquiry item is configured very simple. Very high level view of UE Capability Information message structure is shown below.

Another possible solution seemingly better solution would be to limit the scope of the information that UE report in UE Capability Information message.

The current several hundred different relewse is not with 3CC CA. With this, Network can force UE to send the only capability information that are necessary to the current Network.

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.

Related Posts

LAZY LEUKOCYTE SYNDROME PDF

Feature Group Indicators (FGI bits) in LTE – Rel. 8, Rel. 9 and Rel. 10

Gunos I want to show how this message has expanded as LTE evolves in following table. Another possible solution seemingly better solution would be to limit the scope of the information that UE report in UE Capability Information message. But the size increase by FGI was minor. How long the message can be? Why we need to worry about the size limitation of RRC message? As a result, interpreting the contents of the message has become pretty complicated.

BETTELHEIM PSYCHANALYSE DES CONTES DE FES PDF

36.331 RELEASE 11 PDF

New version to fix ASN. 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. General Versions Responsibility Related. Followings are some of the complete message example for UE Capability Information message.

HOFMANNSTHAL DER SCHWIERIGE PDF

36.331 RELEASE 8 PDF

I want to show how this message has expanded as LTE evolves in following table. What would be the solution for handling this kind of too over-sized message? However, as higher carrier aggregation i. 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. If the UE gelease full capability of Rel 13 and a lot of band combination. Another possible solution seemingly better solution would be to limit the scope of the information that UE report in UE Capability Information message.

HISTORY OF PHNET PDF

3GPP TS 36.331

.

Related Articles