A.1 EXAMPLE MESSAGE Layout
25.4533GPPRelease 17TSUTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling
Assume the following message format:
Table A.1
|
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
YES |
Reject |
|||
|
Transaction ID |
M |
– |
||||
|
A |
M |
YES |
reject |
|||
|
B |
M |
YES |
reject |
|||
|
>E |
1..<maxE> |
EACH |
ignore |
|||
|
>>F |
1..<maxF> |
– |
||||
|
>>>G |
0..3, … |
EACH |
ignore |
|||
|
>>H |
1..<maxH> |
EACH |
ignore |
|||
|
>>>G |
0..3, … |
EACH |
ignore and notify |
|||
|
>>G |
M |
YES |
reject |
|||
|
>>J |
1..<maxJ> |
– |
||||
|
>>>G |
0..3, … |
EACH |
reject |
|||
|
C |
M |
YES |
reject |
|||
|
>K |
1..<maxK> |
EACH |
ignore and notify |
|||
|
>>L |
1..<maxL> |
– |
||||
|
>>>M |
O |
– |
||||
|
D |
M |
YES |
reject |
NOTE: The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Single-Container.
For the corresponding ASN.1 layout, see clause A.4.