ETSI TS 149 008 V8.0.0 (2009-01) Technical Specification Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-Interface (3GPP TS 49.008 version 8.0.0 Release 8) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS 3GPP TS 49.008 version 8.0.0 Release 8 1 ETSI TS 149 008 V8.0.0 (2009-01) Reference RTS/TSGC-0149008v800 Keywords GSM ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI 3GPP TS 49.008 version 8.0.0 Release 8 2 ETSI TS 149 008 V8.0.0 (2009-01) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp. ETSI 3GPP TS 49.008 version 8.0.0 Release 8 3 ETSI TS 149 008 V8.0.0 (2009-01) Contents Intellectual Property Rights ................................................................................................................................ 2 Foreword ............................................................................................................................................................. 2 Foreword ............................................................................................................................................................. 4 1 Scope ........................................................................................................................................................ 5 2 References ................................................................................................................................................ 5 3 Abbreviations ........................................................................................................................................... 6 4 Principles for the use of BSSAP on the E-interface ................................................................................. 6 4.1 General ............................................................................................................................................................... 6 4.2 Transfer of DTAP and BSSMAP layer 3 messages on the E-interface .............................................................. 6 4.3 Roles of MSC-A, MSC-I and MSC-T ................................................................................................................ 7 5 Use of the BSSAP on the E-interface ....................................................................................................... 7 5.1 DTAP ................................................................................................................................................................. 8 5.2 Assignment ......................................................................................................................................................... 8 5.3 Handover resource allocation ............................................................................................................................. 8 5.4 Handover execution ............................................................................................................................................ 8 5.5 Internal handover indication ............................................................................................................................... 9 5.6 Release due to BSS generated reasons ............................................................................................................... 9 5.7 Classmark handling ............................................................................................................................................ 9 5.8 Cipher mode control ........................................................................................................................................... 9 5.9 Trace invocation ................................................................................................................................................. 9 5.10 Queuing indication ........................................................................................................................................... 10 5.11 Data link control SAPI not equal to "0" ........................................................................................................... 10 5.12 Location Acquisition ........................................................................................................................................ 10 5.13 LSA handling ................................................................................................................................................... 10 5.14 Common ID ...................................................................................................................................................... 10 5.15 Service Change procedure ................................................................................................................................ 11 6 BSSMAP messages transferred on the E-interface ................................................................................ 11 7 Exceptions for BSSMAP message contents and information element coding when transferred on the E-interface ........................................................................................................................................ 12 7.1 Message contents .............................................................................................................................................. 12 7.2 Information element coding ............................................................................................................................. 13 8 BSSAP message error handling when transferred on the E-interface .................................................... 14 Annex A (informative): Change history ....................................................................................................... 15 History .............................................................................................................................................................. 16 ETSI 3GPP TS 49.008 version 8.0.0 Release 8 4 ETSI TS 149 008 V8.0.0 (2009-01) Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document provides a mechanism giving reliable transfer of signalling messages within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI 3GPP TS 49.008 version 8.0.0 Release 8 5 ETSI TS 149 008 V8.0.0 (2009-01) 1 Scope The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in 3GPP TS 48.006 and 3GPP TS 48.008, which is used on the E-interface. A general description can be found in 3GPP TS 23.002 and 3GPP TS 23.009. For the initiation and execution of handover between MSCs a subset of BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC. 2 References 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] Void. [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP TS 23.009: "Handover procedures". [2a] 3GPP TS 23.002: "Network Architecture". [3] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [4] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". [6] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)". [7] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2)". [8] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". ETSI 3GPP TS 49.008 version 8.0.0 Release 8 6 ETSI TS 149 008 V8.0.0 (2009-01) 3 Abbreviations For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [1a] and the following apply: BSS Base Station System BSSAP Base Station System Application Part BSSMAP Base Station System Management Application Part CCCH Common Control CHannel DLCI Data Link Connection Identifier DTAP Direct Transfer Application Part MSC Mobile-services Switching Centre MSC-A Mobile-services Switching Centre, Anchor (Anchor MSC) MSC-I Mobile-services Switching Centre, Intermediate (Intermediate MSC) MSC-T Mobile-services Switching Centre, Target (Target MSC) SAPI Service Access Point Identifier SCCP Signalling Connection Control Part TCAP Transaction Capabilities Application Part 4 Principles for the use of BSSAP on the E-interface 4.1 General The mechanisms for the transfer of the BSSAP messages on the E-interface is defined in 3GPP TS 29.002. The operation of the handover procedures between MSCs and the use of the BSSMAP messages for those procedures is described in 3GPP TS 23.009 and 3GPP TS 29.010. In the same way as a SCCP signalling connection is used for the messages relating to one MS on the MSC-BSS interface a TCAP dialogue is used on the E-interface for messages relating to one MS. As no correspondence to the connectionless service on the MSC-BSS interface is used on the E-interface none of the global procedures (see 3GPP TS 48.008 subclause 3.1) are applicable. The management of the terrestrial circuits between the MSCs is outside the scope of the E-interface (see 3GPP TS 23.009), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the BSSMAP procedures and messages used on the E-interface. 4.2 Transfer of DTAP and BSSMAP layer 3 messages on the E-interface The BSSAP data which on the MSC-BSS interface is contained in the user data field of the exchanged SCCP frames (see 3GPP TS 48.006) is on the E-interface transferred as the contents of the signalling info in a BSS-APDU parameter as described in 3GPP TS 29.002. The BSSAP data consists of a BSSAP header and a DTAP or BSSMAP layer 3 message. The BSSAP header contains, as specified in 3GPP TS 48.006 (subclauses 6.3.1, 6.3.2 and 6.3.3), of a discrimination parameter, possibly a Data Link Connection Identification (DLCI) parameter, and a length indicator. ETSI 3GPP TS 49.008 version 8.0.0 Release 8 7 ETSI TS 149 008 V8.0.0 (2009-01) 4.3 Roles of MSC-A, MSC-I and MSC-T For the description in the present document, the MSC's functionality related to the handover between MSCs has been split into three logical parts, MSC-A, MSC-T and MSC-I. The different roles need not necessarily be performed by different MSCs. MSC-A is the call/connection controlling part of the MSC where the call/connection was originally established and the switching point for handover between MSCs. (This corresponds to MSC-A as defined in 3GPP TS 23.009 and 3GPP TS 29.002). The MSC that is the MSC-A will not be changed during the duration of a call/connection. MSC-T is the part relating to the transitory state during the handover for the MSC to which the MS is handed over when Basic handover or Subsequent handover (see 3GPP TS 23.009) take place. (This corresponds, depending on the type of handover to MSC-A, MSC-B or MSC-B' in 3GPP TS 23.009 and 3GPP TS 29.002). MSC-I is the part of an MSC through which the MSC-A, via an E-interface (or an internal interface) is in contact with the MS. (This corresponds, depending on the type of handover to MSC-A, MSC-B or MSC-B' in 3GPP TS 23.009 and 3GPP TS 29.002). The MSC that is the MSC-A can also have the role of either the MSC-I or the MSC-T during a period of the call/connection. The following is applicable for the involved MSCs concerning the exchange of BSSAP data on an E-interface before and after a successful inter MSC handover: 1) At Basic handover, two MSCs are involved, one MSC being MSC-A and one being MSC-T. When this handover has been performed, the two MSCs interworking on the E-interface have the roles of MSC-A and MSC-I respectively, i.e. the MSC that is the MSC-T during the handover is now the MSC-I. 2) At Subsequent handover back to MSC-A, two MSCs are involved. The MSC having the role of MSC-A has also the role of MSC-T. The other MSC involved has the role of MSC-I. When this handover has been completed, there is no exchange of BSS data on the E-interface, i.e. the MSC being the MSC-I before and during the handover is now no longer taking part. 3) At subsequent handover to an MSC not being MSC-A, three MSCs are involved. The roles of these MSCs are MSC-A, MSC-I, and MSC-T respectively. When this handover has been performed, the two MSCs interworking on an E-interface have the roles of MSC-A and MSC-I respectively, i.e. the MSC that is the MSC-T during the handover is now the MSC-I and the MSC being MSC-I during the handover is now no longer taking part. 5 Use of the BSSAP on the E-interface DTAP is used on the E-interface for the transfer of messages between the MSC-A and the MS. The dedicated BSSMAP procedures (3GPP TS 48.008 subclause 3.1) used on the E-interface to some extent are: - assignment; - handover resource allocation; - handover execution; - internal handover indication; - release due to BSS generated reasons; - classmark handling; - cipher mode control; - trace invocation; - queuing indication; - data link control SAPI not equal to "0"; ETSI 3GPP TS 49.008 version 8.0.0 Release 8 8 ETSI TS 149 008 V8.0.0 (2009-01) - Location Acquisition; - LSA handling; - Common ID. One dedicated BSSMAP procedure is used only on the E-interface: - Service Change (subclause 5.15). 5.1 DTAP For the exchange of the DTAP messages (3GPP TS 48.008 subclause 2.2), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. 5.2 Assignment The Assignment procedure (3GPP TS 48.008 subclause 3.1.1) is applied on the E-interface with following conditions: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. The handling of terrestrial resources is not applicable. 5.3 Handover resource allocation At Basic Inter-MSC Handover (3GPP TS 23.009) the Handover resource allocation procedure (3GPP TS 48.008 subclause 3.1.5.2) is applied on the E-interface with the following conditions: - the MSC-A acts as the MSC; - the MSC-T acts as the target BSS. At Subsequent Inter-MSC Handover (3GPP TS 23.009) the Handover resource allocation procedure (3GPP TS 48.008 subclause 3.1.5.2) is applied on the E-interface with the following conditions: - the MSC-I acts as the MSC; - the MSC-T acts as the target BSS; - if the MSC that is the MSC-A is not also the MSC-T, then this MSC shall act as the target BSS towards the MSC-I and as the MSC towards the MSC-T. The handling of terrestrial resources is not applicable. 5.4 Handover execution For the Handover execution procedure (3GPP TS 48.008 subclause 3.1.5.3) the applicable parts on the E-interface are the transfer of HANDOVER DETECT, HANDOVER COMPLETE and HANDOVER FAILURE messages at inter MSC handover. For those parts, the involved MSCs shall act according to the following: - the MSC that is the MSC-A, acts as the MSC; - the MSC that is the MSC-I, if it is not also the MSC-A, acts as the serving BSS; ETSI 3GPP TS 49.008 version 8.0.0 Release 8 9 ETSI TS 149 008 V8.0.0 (2009-01) - the MSC that is the MSC-T, if it is not also the MSC-A, acts as the target BSS. 5.5 Internal handover indication For the Internal handover indication (3GPP TS 48.008 subclauses 3.1.6 and 3.1.7), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. MSC internal handovers (inter-BSS and intra-BSS handover) at the MSC-I are decided and executed autonomously by that MSC together with the connected BSSs. At completion of the handover execution the MSC-I initiates the internal handover indication procedure. 5.6 Release due to BSS generated reasons For the Release due to BSS generated reasons procedure (3GPP TS 48.008 subclause 3.1.9.2) the involved MSCs shall act according to the following: - the MSC-I acts as the BSS; - no further action is taken by the MSC-A. Additionally, at Basic Inter-MSC Handover and at Subsequent Inter-MSC Handover (3GPP TS 23.009), if the MSC that is the MSC-A is not also the MSC-T, the Release due to BSS generated reasons procedure (3GPP TS 48.008 subclause 3.1.9.2) is applied on the E-interface with the following conditions: - the MSC-T acts as the BSS; - no further action is taken by the MSC-A. 5.7 Classmark handling For the Classmark handling (3GPP TS 48.008 subclause 3.1.13), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. 5.8 Cipher mode control For the Cipher mode control (3GPP TS 48.008 subclause 3.1.14), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. 5.9 Trace invocation For the Trace invocation (3GPP TS 48.008 subclause 3.1.11), the involved MSCs shall act according to the following: - the MSC-A acts as the MSC; - the MSC-I acts as the BSS. ETSI