Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.011  Word version:  17.0.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 6

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.
Clause 2 describes general procedures for interworking between the A- and D- physical interfaces.
Clause 3 describes the general procedures for the SS version negotiation.
Clause 4 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.
Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity.
Clause 6 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).
Up

1.1  Normative referencesp. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.004: "General on supplementary services".
[3]
TS 22.024: "Description of Charge Advice Information (CAI)".
[4]
TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
[5]
TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1".
[6]
TS 22.093: "Completion of Calls to Busy Subscriber - Stage 1".
[7]
TS 23.011: "Technical realization of supplementary services".
[8]
TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2".
[9]
TS 23.093: "Completion of Calls to Busy Subscriber - Stage 2".
[10]
TS 24.008: "Mobile radio interface layer 3 specification".
[11]
TS 24.010: "Mobile radio interface layer 3 Supplementary services specification General aspects".
[12]
TS 24.072: "Call Deflection supplementary service - Stage 3".
[13]
TS 24.080: "Mobile radio interface layer 3 supplementary services specification Formats and coding".
[14]
TS 24.081: "Line identification supplementary services - Stage 3".
[15]
TS 24.082: "Call Forwarding (CF) supplementary services - Stage 3".
[16]
TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3".
[17]
TS 24.084: "Multi Party (MPTY) supplementary services - Stage 3".
[18]
TS 24.085: "Closed User Group (CUG) supplementary services - Stage 3".
[19]
TS 24.086: "Advice of Charge (AoC) supplementary services - Stage 3".
[20]
TS 24.088: "Call Barring (CB) supplementary services - Stage 3".
[21]
TS 24.090: "Unstructured supplementary services operation - Stage 3".
[22]
TS 24.091: "Explicit Call Transfer (ECT) supplementary services - Stage 3".
[23]
TS 24.093: "Completion of Calls to Busy Subscriber - Stage 3".
[24]
TS 29.002: "Mobile Application Part (MAP) specification".
[25]
TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)".
[26]
TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2".
Up

1.2  Definitions and abbreviationsp. 7

Abbreviations used in this specification are listed in TR 21.905.

2  Introductionp. 7

This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces.

2.1  MSC/VLR procedures for handling supplementary service signalling received over the A-interfacep. 8

Upon receipt of supplementary service signalling on the A-interface, the MSC/VLR shall:
  • perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5);
  • if necessary request access to the HLR over the D-interface using the procedures defined in this specification and MAP, TS 29.002;
  • use the version indicator received from the MS to set up the right AC context name towards the HLR (see clause 3). The version indicator is described in TS 24.010 and TS 24.080. AC names are defined in TS 29.002;
  • perform mapping between layer 3 messages on the radio path and TC transaction sublayer messages as required (see clause 3).
Up

2.2  MSC/VLR procedures for handling supplementary service signalling received over the D-interfacep. 8

Upon receipt of supplementary service signalling on the D-interface, the MSC/VLR shall:
  • perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5);
  • handle any information elements according to the screening indicator procedure as described in TS 24.010;
  • perform mapping between TC transaction sublayer messages and layer 3 messages on the radio path as required (see clause 3).
  • 3  SS version negotiationp. 8

    This clause describes the general procedures for the call related and call independent supplementary services version negotiation.

    3.1  Call related supplementary services interworkingp. 8

    No interworking identified.

    3.2  Call independent supplementary services interworkingp. 8

    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.
    Up

    Up   Top   ToC