top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

LTE:What is the meaning of this marker " [[ ", "]]" in RRC Spec

+3 votes
451 views

I have gone through the message in RRC Spec. In release 10 onwards they introduced a marker "[[ " , "]]" in the asn messages ...

What is the use importance of it and its meaning ?
see this example I have taken from spec...
enter image description here

posted Jan 3, 2014 by Sachidananda Sahu

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

Reference http://www.etsi.org/deliver/etsi_ts/136300_136399/136331/10.07.00_60/ts_136331v100700p.pdf
Page 102 - 103

Items in [[..]] represents the extention addition group and here is a explanation -

-- Example with extension addition group

ItemInfoList ::= SEQUENCE (SIZE (1..max)) OF ItemInfo 

ItemInfo ::= SEQUENCE { 
 itemIdentity INTEGER (1..max), 
 field1 Field1, 
 field2 Field2 OPTIONAL, -- Need ON 
 ... 
 [[ field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 
 field4-r9 Field4-r9 OPTIONAL -- Need ON 
 ]] 
} 

-- Example with traditional non-critical extension (empty sequence) 

BroadcastInfoBlock1 ::= SEQUENCE { 
 itemIdentity INTEGER (1..max), 
 field1 Field1, 
 field2 Field2 OPTIONAL, -- Need ON 
 nonCriticalExtension BroadcastInfoBlock1-v940-IEs OPTIONAL 
} 

BroadcastInfoBlock1-v940-IEs::= SEQUENCE { 
 field3-r9 Field3-r9 OPTIONAL, -- Cond Cond1 
 field4-r9 Field4-r9 OPTIONAL, -- Need ON 
 nonCriticalExtension SEQUENCE {} OPTIONAL -- Need OP 
} 

The UE shall, apply the following principles regarding the levels applicable in case of nested error handling:

  • an extension additon group is not regarded as a level on its own. E.g. in the ASN.1 extract in the previous, a error regarding the conditionality of field3 would result in the entire itemInfo entry to be ignored (rather than just the extension addition group containing field3 and field4)

  • a traditional nonCriticalExtension is not regarded as a level on its own. E.g. in the ASN.1 extract in the
    previous, a error regarding the conditionality of field3 would result in the entire BroadcastInfoBlock1 to be
    ignored (rather than just the non critical extension containing field3 and field4).

answer Jan 3, 2014 by Salil Agrawal
Similar Questions
+2 votes

It may be an easy question but still I have some doubt.
How RRC Connection setup procedure gets impacted with the presence of "S-TMSI" as an UE-Identity within the RRC Connection Request message ?
Note: RRC Connection request message can carry either 5 bytes long (S-TMSI) or 5 bytes long random value.

...