Introduction to Mcrnc

May 29, 2019 | Author: Ghaza Horra | Category: Computer Network, Telecommunications, Networks, Teknologi, Computing
Share Embed Donate


Short Description

Introduction to Mcrnc...

Description

mcRNC Architecture and Functionality Introduction to mcRNC

© Nokia Siemens Networks

1 (12)

mcRNC Architecture and Functionality

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 2010. All rights reserved.

© Nokia Siemens Networks

2 (12)

mcRNC Architecture and Functionality

Table of Contents: 1 2 3 4 5

Introduction........................................................................................................ 4 Scaling According to Capacity Needs ................................................................ 5 Role of RNC within 3G Network ......................................................................... 6 RNC Interfaces ................................................................................................ 11 Exercise .......................................................................................................... 12

© Nokia Siemens Networks

3 (12)

mcRNC Architecture and Functionality

1

Introduction

The huge growth of traffic over recent years has brought new challenges to the design of radio network equipment. To satisfy current and future needs, Nokia Siemens Networks has developed a novel, compact and highly scalable multipurpose technology platform for various network element applications. The purpose of this course is to describe one such multicontroller network element, namely the multicontroller radio network controller (mcRNC). Other multicontroller network elements, such as the multicontroller base station controller (mcBSC) and multicontroller transcoder (mcTC) are not covered by this course. The ultra-high packing density of the multicontroller hardware results in various benefits, such as: 

unrivaled footprint



minimized site costs



minimized overall operational expenditure (OPEX).

In addition to the high scalability, high reliability and high performance, the multicontroller design offers high flexibility, that is, the controller role can be changed by loading different software. In this way, for instance, a multicontroller BSC (or parts of the BSC) can be converted into a multicontroller RNC - ensuring a future-proof evolution path for existing radio network equipment.

© Nokia Siemens Networks

4 (12)

mcRNC Architecture and Functionality

2

Scaling According to Capacity Needs

The multicontroller RNC provides highly scalable connectivity for voice and data applications. Because of the small size and easy installation the mcRNC can be located in a remote location near one or more base stations, at a separate RNC site, or at a core network site. The network element consists of between two and eight hardware modules, measuring only 444 mm x 450 mm x 176 mm each. The hardware modules can be installed as such or in any standard 19” ETSI rack. This makes it possible to optimize RNC configurations for different areas and use cases.

© Nokia Siemens Networks

5 (12)

mcRNC Architecture and Functionality

3

Role of RNC within 3G Network

Let us next examine the role of the radio network controller within a third generation (3G) mobile network. The radio network controller controls a number of base stations - also called base transceiver stations (BTSs). The radio access network (RAN) is connected to the circuit-switched core network via the Media Gateway (MGW). In the user plane, the circuit-switched user data (for instance, speech) is carried between the RNC and the MGW, which performs switching, transcoding and various other media processing tasks. In the control plane, the call control signaling messages are carried between the RNC and MSC Server (MSS). The RNC is connected to the packet-switched core network via the Serving GPRS Support Node (SGSN). Move your mouse pointer over the network elements in the figure to find out more details.

© Nokia Siemens Networks

6 (12)

mcRNC Architecture and Functionality

© Nokia Siemens Networks

7 (12)

mcRNC Architecture and Functionality

© Nokia Siemens Networks

8 (12)

mcRNC Architecture and Functionality

© Nokia Siemens Networks

9 (12)

mcRNC Architecture and Functionality

© Nokia Siemens Networks

10 (12)

mcRNC Architecture and Functionality

4

RNC Interfaces

Multicontroller RNC network elements connect to the outside world principally via four types of interfaces: 

Iub interface between the RNC and base transceiver stations



Iur interface between the RNC and another RNC, to be used during interRNC handovers



Iu-CS interface between the RNC and the MGW in the user plane, or between the RNC and MSC Server in the control plane



Iu-PS interface between the RNC and Serving GPRS Support Node (SGSN)

There are some additional interfaces that are not shown in the figure, such as the O&M interface towards NetAct, the Iupc interface towards the Standalone Assisted Global Positioning System Serving Mobile Location Center (SAS), and the Iu-BC interface towards the Cell Broadcast Center (CBC). All interfaces are based on IP over Ethernet transmission.

© Nokia Siemens Networks

11 (12)

mcRNC Architecture and Functionality

5

Exercise

© Nokia Siemens Networks

12 (12)

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF