Escolar Documentos
Profissional Documentos
Cultura Documentos
1 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
Legal notice Intellectual Property Rights All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks. Indemnity The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2007. All rights reserved.
2 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
Table of Contents: 1 Call Handling in MSC .........................................................................................4 1.1 IAM.............................................................................................................4 1.2 ACM, CPG and ANM ..................................................................................4 1.3 REL and RLC .............................................................................................5 2 Call Handling in MSC Server ..............................................................................7 2.1 IAM.............................................................................................................7 2.2 APM ...........................................................................................................7 3 Control and User Plane Routing .........................................................................9 3.1 Routing in an MSC Environment.................................................................9 3.2 Routing in an MSC Server Environment 1/2................................................9 3.3 Routing in an MSC Server Environment 2/2..............................................10 3.4 Exercise....................................................................................................11 4 MGW Selection ................................................................................................13 4.1 MGW Selection.........................................................................................13 4.2 Input for MGW Selection...........................................................................13 4.3 Example of MGW-A Selection - Selection of UPD.....................................14 4.4 Example of MGW-A Selection - Resource Reservation ............................15 4.5 Example of MGW-B Selection - Selection of UPD.....................................16 4.6 Example of MGW-B Selection - Resource Reservation ............................17
3 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
1.1 IAM
Let us start this course with a simple example, presenting the most important ISUP signalling sequences in the Nokia MSC environment. When subscriber A initiates a call via a mobile switching centre (MSC) to another subscriber B who is located under another MSC, the originating MSC transmits an ISUP Initial Address Message (IAM) to reserve a free circuit from the originating MSC to the destination MSC. The original ISUP IAM includes, for instance: the originating point code, the destination point code, circuit identification code and the called party number. The circuit identification code identifies the circuit that is to be used for the call. The IAM is routed via the home network of the originating MSC to the destination MSC.
4 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
The destination MSC connects the ringback tone to the calling party and sends the Connection Progress (CPG) message to the originating MSC to inform it that the destination phone is now alerting. When the called party picks up the phone, the destination MSC terminates the ringing tone and transmits an ISUP Answer Message (ANM) to the originating MSC. If the call is chargeable, the charging starts upon receipt of the ANM message.
5 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
6 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
2.1 IAM
When subscriber A initiates a call via an MSC Server, the originating MSC Server transmits a BICC initial address message (IAM) to the destination MSC Server. The key content is the digits of the called party. In contrast to traditional ISUP IAM, the BICC IAM message is sent without a circuit being hunted for the user plane. Therefore, the ISUP circuit identification code is renamed to Call Instant Code and used only for the identification of the signalling relation between the peer BICC entities not as an indication of the physical bearer for the user plane. This indication of the peer entities is required because the BICC IAM message does not include destination or originating point codes - as ISUP IAM does. The ISUP user service information and transmission medium requirements tags are used both in ISUP and BICC to identify the bearer requirements. In addition, the BICC IAM may include other user plane Bearer Network Characteristics in the BICC message section called APP container.
2.2 APM
Upon receipt of the IAM message, the destination MSS requests bearer information from the destination MGW and forwards this information to the originating MSS in the Application Transport Mechanism (APM) message.
7 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
The APM message contains addressing and optional codec information from the destination MGW. If the bearer is established in the backward direction and no codec negotiation is needed, the APM is not sent and the destination MGW starts the bearer establishment at this stage. In all other cases the APM is sent. At this stage, the codec negotiation can be performed i.e., the interchanges of supported codec information between originating and destination ends. Next, the bearer establishment takes place using AAL2 and Nb UP bearer establishment and initiation procedures. In Nokias solution, the ACM is sent backward immediately after the TCH assignment is completed. This is followed by the Connection Progress (CPG) message containing alerting indication. The answer message (ANM) flow is the same as for ISUP. The release signalling sequences are also unchanged from ISUP, although BICC Release and Release Complete messages contain the indication of the target bearer.
8 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
After this point routing basically ends, because the route always contains local circuits i.e. a physical resource connected to the destination MSC. In the IAM the CIC code is sent; in MSC-B a circuit is reserved based on the CIC reserved and therefore no routing analysis is executed in the destination MSC.
9 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
on adequate element for the user plane. The old analysis steps used in the earlier releases remain unchanged to ensure backward compatibility. New terms have been introduced for the user plane routing: User Plane Destination Reference, User Plane Destination, Bearer Establishment Action Indicator and BNC characteristics. New routing analysis steps have been defined to determine the network element through which the call is routed. These are: Succeeding BNC characteristics determination, Succeeding UPD determination and Succeeding Action Indicator determination. The MSC Servers maintain a new User Plane Topology database to keep record of the routing elements.
10 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
A Multimedia Gateway is then selected from this set, and finally the actual user plane resources can be reserved. The following routing steps are performed in MSS-B: Based on the incoming CGR, the UPDR information is sent to the User Plane Analysis. A preceding UPD determination is carried out. A MGW is selected from this set and then resources are reserved.
3.4 Exercise
Please read carefully the questions presented by the tutor and try to compose your own answers. Then look at the statements presented and select the correct one!
11 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
12 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
MGW Selection
13 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
The MGW Selection is a load-sharing-based selection. The operator can define load sharing values to MGWs on a per UPD basis. These load sharing values will govern how frequently a MGW is selected from a given UPD. The MGW Reselection is used when MGW has already been selected, but the resource reservation to it has failed (e.g. due to overloading). When this happens, the MSS selects another MGW if there is one available in the UPD. If the TDM bearer is to be used for the call, the circuit is hunted by the MSS; this explicitly defines the MGW to be used.
14 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
The succeeding UPD Determination is executed, with the result that the outgoing UPD will be UPD-A1.
15 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
16 (17)
Call Handing in Nokia MSC Server System - GSM Profile - Call Setup in MSS System
17 (17)