GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

14.1.2 Use of TC
Page 197
GSM 09.02 version 5.3.0: August 1996
The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which
is based on CCITT Recommendation Q.773 (1992).
NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1
operation type definition.
Class 1: RESULT and ERROR appear in ASN.1 operation type definition.
Class 2: only ERROR appears in ASN.1 operation type definition.
Class 3: only RESULT appears in ASN.1 operation type definition.
Class 4: both RESULT and ERROR do not appear in ASN.1 operation type definition.
The ASN.1 data type which follows the keywords "ARGUMENT", "PARAMETER" or "RESULT"
(for OPERATION and ERROR) is always optional from a syntactic point of view. However, except when
specifically mentioned, it has to be considered as mandatory from a semantic point of view.
When an optional element is missing in an invoke component or in an inner data structure while it is
required by the context, an error component is returned if specified in the operation type; the associated
type of error is DataMissing. This holds also when the entire parameter of an invoke component is missing
while it is required by the context.
NOTE 2: When a mandatory element is missing in the parameter or inner data structure of any
component, a reject component is returned (if the dialogue still exists). The problem
code to be used is "Mistyped parameter".
The Timer Values used in the operation type definitions are indicated as ASN.1 comment. The Timer Value
Ranges are:
s = from 3 seconds to 10 seconds;
m = from 15 seconds to 30 seconds;
ml = from 1 minute to 10 minutes;
l = from 28 hours to 38 hours.
14.1.3 Use of information elements defined outside MAP
An information element or a set of information elements (messages) transparently carried in the Mobile
Application Part but defined in other recommendation/technical specifications are handled in one of the
following ways:
i) The contents of each information element (without the octets encoding the identifier and the length in
the recommendation/technical specification where it is defined) is carried as the value of an ASN.1
NamedType derived from the octet STRING data type. Additionally, the internal structure may be
explained by means of comments. In case of misalignment the referred to recommendation/technical
specification takes precedence.
ii) The complete information element (including the octets encoding the identifier and the length in the
recommendation/technical specification where it is defined) or set of information elements and the
identity of the associated protocol are carried as the value of the ExternalSignalInfo data type
defined in this ETS. Where more than one information element is carried, the information elements
are sent contiguously with no filler octets between them.