Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.108  Word version:  16.0.0

Top   Top   None   None   Next
1…   5…

 

1  ScopeWord‑p. 5

The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in TS 25.413, which is used on the E interface. A general description can be found in TS 23.002 and TS 23.009.
For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G_MSC.
Up

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]
TR 21.905: "Vocabulary".
[2]
TS 23.009: "Handover procedures".
[3]  Void
[4]
TS 25.413: "UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling".
[5]
TS 29.002: "Mobile Application Part (MAP) specification".
[6]
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]
TS 23.002: "Network architecture".
[8]  Void
Up

3  Abbreviations

For the purposes of the present document, the abbreviations defined in TR 21.905 and the following apply:
3G_MSC
A third generation Mobile services Switching Centre that supports the Iu interface (and possibly also the A-interface)
3G_MSC-A
The controlling 3G_MSC on which the call was originally established
3G_MSC-B
The 3G_MSC to which the UE is handed over in a Basic Handover
3G_MSC-B'
The 3G_MSC to which the UE is handed over in a Subsequent Handover
3G_MSC-I
Interworking 3G_MSC
3G_MSC-T
Target 3G_MSC
EP
Elementary Procedure
NNSF
NAS Node Selection Function
RNC
Radio Network Controller
Up

4  Principles for the use of RANAP on the E interfaceWord‑p. 6

4.1  General

The mechanism for the transfer of the RANAP messages on the E interface is defined in TS 29.002. The operation of the relocation procedures between 3G_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 and TS 29.010.
RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, messages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface.
In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G_MSC RNS interface a TCAP dialogue is used on the E interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G_MSC RNS interface is used on the E interface none of the global procedures are applicable.
The management of the terrestrial circuits between the 3G_MSCs is outside the scope of the E interface (see TS 23.009), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E interface.
Up

4.2  Transfer of RANAP layer 3 messages on the E interface

The RANAP data which on the 3G_MSC RNS interface is contained in the user data field of the exchanged SCCP frames is on the E interface transferred as the contents of the access network signalling info in the AN APDU parameter as described in TS 29.002, indicating the access network protocol identification "ts3G-25413".

4.3  Roles of 3G_MSC A, 3G_MSC I and 3G_MSC T

For the description in the present document, the 3G_MSC's functionality related to the relocation between 3G_MSCs has been split into three logical parts, 3G_MSC A, 3G_MSC T and 3G_MSC I. The different roles need not necessarily be performed by different 3G_MSCs.
3G_MSC A is the call/connection controlling part of the 3G_MSC where the call/connection was originally established and the switching point for relocation between 3G_MSCs. (This corresponds to 3G_MSC A as defined in TS 23.009 and TS 29.002). The 3G_MSC that is the 3G_MSC A will not be changed during the duration of a call/connection.
3G_MSC T is the part relating to the transitory state during the relocation for the 3G_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the type of relocation to 3G_MSC A, 3G_MSC B or 3G_MSC B' in TS 23.009 and TS 29.002).
3G_MSC I is the part of a 3G_MSC through which the 3G_MSC A, via an E interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G_MSC A, 3G_MSC B or 3G_MSC B' in TS 23.009 and TS 29.002).
The 3G_MSC that is the 3G_MSC A can also have the role of either the 3G_MSC I or the 3G_MSC T during a period of the call/connection.
The following is applicable for the involved 3G_MSCs concerning the exchange of RANAP data on an E interface before and after a successful inter 3G_MSC relocation:
  1. At basic relocation, two 3G_MSCs are involved, one 3G_MSC being 3G_MSC A and one being 3G_MSC T. When this relocation has been performed, the two 3G_MSCs interworking on the E interface have the roles of 3G_MSC A and 3G_MSC I respectively, i.e. the 3G_MSC that is the 3G_MSC T during the relocation is now the 3G_MSC I.
  2. At subsequent relocation back to 3G_MSC A, two 3G_MSCs are involved. The 3G_MSC having the role of 3G_MSC A has also the role of 3G_MSC T. The other 3G_MSC involved has the role of 3G_MSC I. When this relocation has been completed, there is no exchange of RANAP data on the E interface, i.e. the 3G_MSC being the 3G_MSC I before and during the relocation is now no longer taking part.
  3. At subsequent relocation of SRNS to an 3G_MSC not being 3G_MSC A, three 3G_MSCs are involved. The roles of these 3G_MSCs are 3G_MSC A, 3G_MSC I, and 3G_MSC T respectively. When this relocation has been performed, the two 3G_MSCs interworking on an E interface have the roles of 3G_MSC A and 3G_MSC I respectively, i.e. the 3G_MSC that is the 3G_MSC T during the relocation is now the 3G_MSC I and the 3G_MSC being 3G_MSC I during the relocation is now no longer taking part.
Up

Up   Top   ToC