blob: 0dfe7c6501d0671609ec2dab8bab2e7a6d22f5d1 [file] [log] [blame]
Harald Welteb8666592015-08-30 14:28:10 +02001IU-Common { }
2
3-- Humble attempt of extracting the common part of RUA, HNBAP and RANAP out of
4-- their respective ASN.1 syntax definitions. Hidden in all those information
5-- object classes is a quite classic 'message header' structure that is identical
6-- to all of the messages of the above protocols. Only the actual information element
7-- contents is specified as 'real' ASN.1 complex data type.
8
9DEFINITIONS AUTOMATIC TAGS ::=
10
11BEGIN
12
13maxProtocolExtensions INTEGER ::= 65535
14maxProtocolIEs INTEGER ::= 65535
15
16Criticality ::= ENUMERATED { reject, ignore, notify }
17
18ProcedureCode ::= INTEGER (0..255)
19
20ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs)
21
22MessageType ::= ENUMERATED { initiatingMessage, successfulOutcome, unsuccessfulOutcome }
23
24ProtocolIEContainer ::= SEQUENCE (SIZE (0..maxProtocolIEs)) OF ProtocolIE-Field
25
26ProtocolExtensionContainer ::= SEQUENCE (SIZE (1..maxProtocolExtensions)) OF ProtocolIE-Field
27
28ProtocolIE-Field ::= SEQUENCE {
29 id ProtocolIE-ID,
30 criticality Criticality,
31 value ANY
32}
33
34
35IUCommon-PDU ::= SEQUENCE {
36 choice MessageType,
37 procedureCode ProcedureCode,
38 criticality Criticality,
39 protocolIEs ProtocolIEContainer,
40 protocolExtensions ProtocolExtensionContainer OPTIONAL,
41 ...
42}
43
44
45END