7 Functional requirements of network entities

03.183GPPBasic call handlingRelease 1998TS

The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams.

The entities described in this clause interwork with other entities over three different types of interface:

– the A interface, used to interwork between the MSC and the BSS or the MS;

– the C, D & F interfaces, used to interwork between the MSC & HLR (C), VLR & HLR (D) and MSC & EIR (F);

– telephony signalling interfaces, used to interwork between an MSC and another exchange.

The protocols used over the A interface are BSSMAP, which is specified in GSM 08.08 [22], for interworking with the BSS and DTAP, which is specified in GSM 04.08 [20], for interworking with the MS.

The protocol used over the C, D & F interfaces is MAP, which is specified in GSM 09.02 [23].

For the purposes of this specification, the protocol used over telephony signalling interfaces is ISUP, which is specified in ETS 300 356‑1 [27]; other telephony signalling systems may be used instead.

This specification shows the call handling application processes interworking with a protocol handler for each of the protocols listed above. Each protocol defines supervision timers. If a supervision timer expires before a distant entity responds to a signal, the handling is as defined in the appropriate protocol specification. In general, the protocol handler reports timer expiry to the application as an error condition or negative response. Where a timer is shown in this specification, therefore, it is an application timer rather than a protocol timer. Interworking with the protocol handlers uses functional signal names which do not necessarily have a one-to-one correspondence with the names of messages used in the protocols.

An MSC which receives an IAM from an originating exchange may react in three different ways:

– it acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called party address, and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. This behaviour is not specific to GSM;

– it acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service area of the MSC;

– it acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a destination exchange determined by analysis of the routeing information from the HLR.

Annex A describes the method which the MSC uses to decide how to process the IAM.

The SDL diagrams in this clause show the handling for a number of optional features and services. If the handling consists only of a call to a procedure specific to the feature or service, the procedure call is omitted if the entity does not support an optional feature or service. If the handling consists of more than a call to a procedure specific to the feature or service, the text associated with each SDL diagram specifies the handling which applies if the entity does not support an optional feature or service. For simplicity of description, it is assumed that support for Operator Determined Barring and the Call Forwarding and Call Barring supplementary services is mandatory.

For the entities which support CAMEL, the references to GSM 03.78 are to the version of GSM 03.78 for the appropriate phase of CAMEL.