The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces.
The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification.
Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification.
describes general procedures for interworking between the A- and D- physical interfaces.
describes the general procedures for the SS version negotiation.
describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces.
describes specific interworking procedures for all interfaces relating to call related SS activity.
describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see TS 29.002
) and the SS handling functions of the network entities (see TS 24.010
and TS 24.080
Reference is made to the following Technical Specifications:
3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series,
for definition of supplementary services;
3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series,
for technical realisation of supplementary services;
3GPP TS 24.010, TS 24.080, 3GPP TS 24.08x and 3GPP TS 24.09x-series,
for radio path signalling procedures for supplementary services;
3GPP TS 29.002 (MAP).
This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces.
This clause describes the general procedures for the call related and call independent supplementary services version negotiation.
No interworking identified.
On receipt of the REGISTER message from the MS, the MSC/VLR will include the appropriate AC name in the dialogue control portion of the BEGIN message based on the following rules:
if no version indicator is present, no AC name is included in the BEGIN message towards the HLR (no AC name indicates "version1");
if the version indicator is less or equal to the highest AC name the MSC/VLR and HLR both support, the "dialogue" will be handled according to the AC name corresponding to the version indicator and to the SS operation received;
if the version indicator is greater than the highest commonly supported AC name within the network (MSC/VLR, HLR), the "dialogue" will be handled according to this highest AC name if the request from the MS can also be fulfilled with this version of the "dialogue".
The selection of the highest commonly supported AC name by the network is described in TS 29.002
It should be noted that unknown parameters of the extension field within the Facility Information Element shall be forwarded to a phase 2 HLR according to the Extensibility rules as defined in TS 29.002
. They may be discarded when sent to a phase 1 HLR.
According to this version of the standards, the highest AC name is "version3".
The description method employed in the clauses 4 to 6 is tabled showing the mapping of parameter values. The exact values of the parameters and parameter tags can be found in the referenced specifications.