GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

12.1.2 Receipt of a TC-BEGIN indication
On receipt of a TC-BEGIN indication primitive, the MAP PM shall:
Page 153
GSM 09.02 version 5.3.0: August 1996
- if no application-context-name is included in the primitive and if the "Components present" indicator
indicates "no components", issue a TC-U-ABORT request primitive (note 2). The local MAP-User is
not informed.
- if no application-context-name is included in the primitive and if presence of components is indicated,
wait for the first TC-INVOKE primitive, and derive a version 1 application-context-name from the
operation code according to table 12.1/1 (note 1).
NOTE 1: In some cases, it may be necessary to analyse the operation argument.
Then:
a) if no application-context-name can be derived (i.e. the operation code does not exist in MAP
V1 specifications), the MAP PM shall issue a TC-U-ABORT request primitive (note 2). The
local MAP-User is not informed.
b) if an application-context-name can be derived and if it is acceptable from a load control point
of view, the MAP PM shall:
i) if this primitive requests the beginSubscriberActivity operation, the MAP PM shall check
whether more components have been received associated with this operation. If more
components are present, the MAP PM shall issue a MAP-OPEN
indication primitive with the version 1 application-context-name
"networkFunctionalSsContext-v1". The Destination-reference shall include the IMSI
taken from the argument of the beginSubscriberActivity operation; the
Originating-reference shall cover the originatingEntityNumber.
A beginSubscriberActivity operation that is not associated with any other Component
shall be rejected by the MAP PM by issuing a TC-U-ABORT request primitive (note 2).
The local MAP-User shall not be informed.
ii) otherwise, the MAP PM shall issue a MAP-OPEN indication primitive with the version 1
application-context-name set according to table 12.1/1. DestinationReference and
OriginatingReference must not be included in the MAP-OPEN indication primitive.
Then the MAP PM shall function in a way that the dialogue responding MAP behaves as specified in
the GSM phase 1 protocol (latest version of TS GSM 09.02 phase 1).
NOTE 2: If no AARQ apdu was included in the BEGIN message, TC (Component Sub-layer) will
not include an AARE apdu or an ABRT apdu in a TR-U-ABORT request primitive that is
to be issued on receipt of a TC-U-ABORT request primitive from the local MAP service
provider.