Reference Ipa2800
Reference Ipa2800
Reference Ipa2800
Nokia Networks Oy
1 (42)
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 Networks' customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia 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 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 cannot be considered binding but shall be defined in the agreement made between Nokia Networks and the customer. However, Nokia 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 Networks will, if necessary, explain issues which may not be covered by the document. Nokia Networks' liability for any errors in the document is limited to the documentary correction of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Networks Oy 2001. All rights reserved.
2 (42)
Nokia Networks Oy
Contents
Contents
1 2 2.1 2.2 3 3.1 3.2 3.2.1 3.2.2 4 4.1.1 4.2 5 5.1 5.2 5.3 5.3.1 5.3.2 5.4 6 6.1 7 8 8.1 8.2 8.3 9 Objectives ............................................................................................. 4 Introduction .......................................................................................... 5 IPA2800 Packet Platform functionality.................................................... 6 Aspects of the Nokia IPA2800 platform .................................................. 7 Basic architecture of Nokia IPA2800................................................... 8 Redundancy in the Nokia IPA2800 platform ........................................... 9 Capacity of the Nokia IPA2800 platform ............................................... 10 Interface and switching capacity........................................................... 10 Processing capacity ............................................................................. 11 IPA2800 platform hardware ............................................................... 12 ESD protection ..................................................................................... 15 IPA2800 hardware management system.............................................. 16 IPA2800 processing platform ............................................................ 17 Computing platform .............................................................................. 17 Switching platform ................................................................................ 19 Signal processing platform ................................................................... 21 Speech transcoding.............................................................................. 22 Macro-Diversity Combining .................................................................. 23 Example of user traffic through the RNC to MGW ................................ 23 Transmission management in the IPA2800 ...................................... 28 Basic implementation of ATM in the IPA2800....................................... 29 Synchronisation and timing in the IPA2800 platform ...................... 31 Operating and maintaining the IPA2800 ........................................... 33 IPA2800 maintenance system .............................................................. 33 IPA2800 user interfaces ....................................................................... 34 Network Element Management Unit (NEMU) ....................................... 36 Review of IPA2800 basics.................................................................. 38 Glossary of platform terminology ..................................................... 41
Nokia Networks Oy
3 (42)
Objectives
The aim of this module is to give the participant the conceptual knowledge needed for explaining the basics of the Nokia IPA2800 platform. Topics to be covered in this module include a look at the general architecture and the hardware used. As the IPA2800 is used in 3G networks, the module looks at the different types of processing platforms that are utilised. A short look of transmission and synchronisation is included for completeness. Finally, the module examines the role of operation and maintenance in the IPA2800. After completing this module, the participant should be able to:
Identify and list the key aspects of the Nokia IPA2800 platform in terms of its computing platform, motivation for development, and its application in the mobile network. Using a block diagram, list and identify the key functional units. Also, list and briefly explain each of the three redundancy principles that can be found in the IPA2800. Furthermore, explain how platform's capacity can be increased. List and explain the different hardware mechanics found in the IPA2800 cabinet. Also, identify the relationship between the subrack and plug-in unit. Furthermore, list the precautions that should be taken when handling the plug-in units. Using an illustrated figure, identify what are the three domains of the processing platform. Identify the differences between each domain in terms of its functions. Also, clarify what is the signal-processing domain and give an example of its use. Using a very brief model, explain the different types of ATM protocols used in the transmission of the IPA2800 and how it is visualised. Briefly explain how synchronisation and timing is achieved in the IPA2800 RNC and MGW units. List the four basic functions of the operating and maintenance system. Also, clarify the use of the web-based (NEMU) and text-based (MML) interfaces. Make reference to practical uses of each.
All of the objectives can be met through the use of this material and access to NOLS.
4 (42)
Nokia Networks Oy
Introduction
Introduction
The IPA2800 Packet Platform Principles have been developed to meet the needs of the evolution in mobile networks. As networks move from being circuit switched to packet switched, the requirements on the physical platform change. The physical platform must be fault tolerant, scaleable, low cost to maintain, and reliable. However, unlike the GSM circuit switched world, the 3G mobile network requires increased computer and signal processing power assuring QoS (Quality of Service).
Figure 1.
The hardware mechanism for the IPA2800 platform is designed to use the minimal amount of footprint space (that is, physical space) as possible. In the Nokia 3G Solution, the IPA2800 platform is used in the Nokia Radio Network Controller (RNC) and the MGW (MSC Media Gateway).
Nokia Networks Oy
5 (42)
2.1
Applications
Application Software Signal Fault Tolerant Switching Processing Computing Platform Platform Platform Software SW SW Modular and Scaleable Hardware
Figure 2.
The switching platform provides common telecom functions (for example, statistics, routing, and address analysis) as well as generic packet switching/routing functionality common for several application areas (for example, connection control, traffic management, ATM network operations and maintenance, and resource management). The fault tolerant computing platform provides a distributed and fault tolerant computing environment for the upper platform levels and the applications. It is ideal for use in implementing flexible, efficient, and fault tolerant computing systems. The computing platform is based upon general-purpose computer units with inter-processor communications implemented using ATM virtual connections. The number of computer units can be scaled according to application and network element specific processing capacity requirements. The hardware platform based on standard mechanics provides cost efficiency through the use of modular optimised and standardised solutions that are largely based on commercially available chipsets. The signal-processing platform provides generic services for all signalprocessing applications. Digital signal processing (DSP) is needed in providing computation intensive end-user services, such as speech transcoding, echo cancellation, or macro-diversity combining. The adjunct platform (NEMU) provides a generic platform for O&M application services and different NE management applications and tools.
6 (42)
Nokia Networks Oy
Introduction
2.2
Nokia Networks Oy
7 (42)
NIS1
NIS0
A2SU
NEMU
OMU
FDU WDU
TBU
Figure 3.
IPA2800 architecture
8 (42)
Nokia Networks Oy
Network Interface Units (NIUs) are used for connecting the network element to various types of transmission systems (e.g. E1 or STM-1). (Please note that the actual names of functional units are different, e.g. NIS1 and NIP1 instead of NIU). Network Interworking Units (NIWUs) are used for connecting the network element to non-ATM transmission systems (e.g. TDM E1). The IPA2800 is designed to work with different interfaces. There are different types of NIUs, and the choice is dictated by the choice of physical transmission. The ATM Multiplexer Unit (MXU) and ATM Switching Fabric Unit (SFU) are used for switching both circuit and packet switched data channels, for connecting signalling channels, as well as for system internal communications. The AAL2 Switching Unit (A2SU) performs switching of AAL type 2 packets. Timing and Hardware Management Bus Unit (TBU) is used for timing, synchronisation, and system maintenance purposes. Unlike in GSM, in 3G, distributed Signal Processing Units (SPU) provide support for e.g. transcoding, macro-diversity combining, data compression, and ciphering. The units are connected to the SFU either directly (in the case of units with high traffic capacity) or via the MXU (in the case of units with lower traffic capacity). Network Element Management Unit (NEMU) provides graphical user interface and is responsible for element management tasks, as well as interfacing the Network Management System.
3.1
Nokia Networks Oy
9 (42)
If the spare unit is designated for only one active unit, the software in the unit pair is kept synchronised so that taking the spare in use in fault situations (switchover) is very fast. This is called 2N redundancy principle or duplication. For less strict reliability requirements, the spare unit may also be designated to a group of functional units. The spare unit can replace any unit in the group. In this case the switchover is a bit slower to execute, because the spare unit synchronisation (warming) is performed as a part of the switchover procedure. This redundancy principle is called replaceable N+1. A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of unit in the pool is selected so that there is some extra capacity available. If a few units of the pool are disabled because of faults, the rest of the group can still perform its designated functions. This redundancy principle is called complementary N+1 or load sharing.
3.2
Figure 4.
3.2.1
10 (42)
Nokia Networks Oy
3.2.2
Processing capacity
Complexity of services envisioned for future networks calls for computing power in the network elements. IPA2800 Packet Platform is well positioned to provide required scalability and flexibility through the distributed, fault-tolerant computing environment provided by the Fault Tolerant Computing Platform. Processing capacity can be increased by distributing the functionality of the network element to multiple computer units, and by upgrading computer units with more powerful variants. Processing capacity of IPA2800 Packet Platform based network elements is scalable from one computer unit (pair) up to tens of computer units depending on the application requirements. In the IPA2800 platform, computer system forms a three level hierarchy:
In the lowest level, digital signal processors and control processors (micro-controllers or microprocessors) perform low-level functions, often involving real-time processing of data flow. Digital signal processors can also be classified belonging to this level. The next level consists of the unit computers that perform e.g. control and operations & maintenance tasks. These are typically embedded in network interface or switch element plug-in units. The third level consists of the control computers that form the basis for scalable processing capacity of the fault-tolerant computing platform. Typical applications include signalling and call control functions, as well as operation and support functions.
In addition, a fourth level of computers is also used. The management computers or adjunct computers are used for post-processing and management functions. For example, graphical user interface and other added-value applications can be implemented in a commercial operating system environment. Adjunct computers may be physically integrated with the IPA2800 based network elements based on the needs of network element concepts. Please note that adjunct computers are not under system maintenance of the IPA2800 system.
Nokia Networks Oy
11 (42)
Figure 5.
12 (42)
Nokia Networks Oy
Cabinet mechanics Dimensions of the cabinet are: width 600 mm, depth 600 mm, and height 1800 mm (based on standard ETS 300 119-2 and IEC 917-2). 19-slot subrack Subrack has a height of 300 mm, a depth of 300 mm, and a width of 500 mm. The nominal plug-in unit slot in the subrack is 25 mm, which results in 19 slots per one subrack. The basic construction allows dividing a part of a subrack vertically into two slots with optional guiding mechanics for the use of half-height plug-in units.
SF05-A NI16P1 NI4S1-A CDSP AL2S MDS MCPC2 Fuse / Power Distribution Panel T B MEU CSF PA C1T 2 6B U F ESA16 TBUF IC186 FTR CPD80
Switching Fabric, 5 Gbit/s Network Interface, 16 x PDH E1/T1/J1 (ATM) Network Interface, 2 x STM-1 Configurable Dynamic Signal Processor AAL2 Switching Unit Magneto-optical disk, SCSI (2.6 GB/side) Management Computer, P III, Connector 2 Ethernet Switch Timing Buffer Indoor Cabinet, 1800 * 600 * 600 mm Fan Tray Cabinet Power Distribution, 80 A Cable Patch Panels and Cabling
S F 0 5 A
N I 1 6 P 1
N I 4 S 1 A
C PA DDL S2 2 P0 S
M D S
Fan Tray
PD20
Figure 6.
Backplane and front plate mechanics The backplane and cabling system provides reliable interconnections between plug-in units. In addition to this, the backplane provides EMC shield to the rear side of the subrack. Common signals are delivered via the backplane and all other interconnection signals are connected via cabling. This allows backplane modularity and flexibility in different configurations. Because of flexible cabling and redundancy it is possible to scale the system to a larger capacity in an active system without shutting down the whole system. Connector and cabling system Cabinet power distribution equipment and four subracks with cooling equipment can be installed in one cabinet. Openings in the sides of the cabinet behind the subrack backplanes allow direct horizontal cabling between cabinets.
Nokia Networks Oy
13 (42)
Cooling equipment Fans are situated throughout the equipment to maintain a normal working condition. The supervision of these fans is made by the OMU.
The Nokia customer documentation (available through NOLS) contains detailed information on the installation and commissioning of the IPA2800 platform. For more information, please refer to this material.
Figure 7.
The physical platform of the IPA2800 acts as base where the applications (such as functions of the RNC and MGW) are placed. When we commission a new unit inside the IPA2800, we must make the correct configuration entries for the unit. The IPA2800 platform has a function known as configuration management. This is where all the definitions for the units are made. If we are to add in additional signal processing capability, we must define the card and location, and then must allocate this card to a particular controlling unit. The plug-in units themselves are of the same dimension can be easily added and removed from the cabinet.
14 (42)
Nokia Networks Oy
Figure 8.
4.1.1
ESD protection
When adding or removing units from the IPA2800, remember to always use protection against electrostatic energy. Failure to do so may result in the plug-in units becoming faulty. This is because the components on the cards are very susceptible to shorting should a static charge be applied. Precautions can be taken to ensure that the static energy produced by our bodies and clothes is reduced by making a ground. This means that we can wear special shoes, bracelets, etc. that are connected to a point which is connected into ground. This gives a route for static energy to travel, rather than through the sensitive cards. Also, the cards should always be packed in anti-static material and when on a desk, you should use special mats. If you are expected to physically deal with plug-in units, please refer to the Nokia customer documentation.
Nokia Networks Oy
15 (42)
4.2
Reading hardware configuration of a network element Bootloading configuration data to control and unit computers Forced control of functional states (restart, active, passive, separated) of physical functional units Collecting HW fault notifications Providing message link between control and unit computers having no other message link Controlling auxiliary network element equipments like fan trays and AC/DC power supplies Supervising or controlling equipment and space external to network element (temperature, door locking, alarms, etc.).
The HMS itself has no other functions than providing fault tolerant message passing between operation and maintenance computer and other plug-in units and supervise its own service level. When a fault occurs, the HMS reports this to the OMU, that then takes a corrective course of action.
16 (42)
Nokia Networks Oy
5.1
Computing platform
The computing platform is divided into eight domains. Each domain is responsible for certain functionality.
Operation and Maintenance functions
Multiple ways to configure/manage features are available. The Man Machine Interface (MMI) is operated by MML commands. MML sessions are established by using the Telnet protocol (usage via serial interface is not supported). In the RNC it is used for configuring features of the platform (e.g. alarm system administration, system support and communication, SS7 services, I/O system). The configuration of the system is modified by using web based user interface. It is implemented in the NEMU. It also supports a set of standardised interfaces, SNMP, Corba, and is used as a network management interface between the network element and the OSS and for managing selected features of the RNC and ATM Module.
SS7 Services
Narrowband MTP2: the Message Transfer Part level 2 (MTP2) in narrowband environment provides a signalling link for reliable transfer of signalling messages between two network nodes. It supports MTP3b: SS7 signalling channels over an ATM network and the SCCP: Signalling Connection Control Part. Also, the unit has facilities for SS7 statistics.
Data Communication Services
Transmission Control Protocol (TCP) for reliable connection-oriented communication of the unit. Also, User Datagram Protocol (UDP) for unreliable connectionless communication. ICMP for communication errors and various network conditions and IGMP to support multicasting. ARP for mapping IP addresses to MAC addresses. There are two different link layers supported: AAL5; Ethernet (100Base-TX).
Nokia Networks Oy
17 (42)
Computing Platform
O&M Services O&M Services Management management protocols and protocols and platforms platforms User interfaces user
SS7 Services SS7 Services Narrowband MTP2 narrowband MTP2 MTP3 MTP3 SCCP SCCP SS7 statistics SS7 statistics
Data Communication Data Services Communication Services Data transfer data Applications applications
Configuration Data Management Configuration Data Management Hardware configuration hardware Software configuration software System configuration system Application parameters application Core Services Core Services Kernel services kernel Local services local Networking services networking
Fault Management Fault Management HW supervision HW supervision Diagnostics diagnostics Alarm system alarm Recovery recovery I/O System and File I/O System and File System Services System Services Device drivers device drivers File systems file
Database Database Management Management Database database management management services services
Figure 9.
Set of functions used to control the configuration of the system. These can be divided into separate categories that are responsible for the hardware and software configuration of the unit. Also, services exist to support the configuration of the equipment and configuration parameters.
Fault Management
Provides services to handle fault situations within the system in a manner that meets availability requirements set by the operators.
Core Services
This domain provides basic services for loading and executing programs in computer units of the IPA2800 platform for both DMX and Chorus operating systems.
Database Management
This domain offers an administrative MML interface to databases, database queries, integrity check, concurrency control, and recovery. The IPA2800 databases are main memory databases, which means that they are entirely stored and maintained in RAM. A backup copy of the database can, however, reside on disk.
18 (42)
Nokia Networks Oy
Provides services to handle both memory and disk files and to perform I/O operations:
DMX specific memory file system User interface. File loading, distribution, conversion and supervision services. Disk updating queues I/O system Shadows file system for hard disks MSDOS file system for floppy disks Printer services: only virtual printers connected via TCP/IP (LAN) are supported; it is not possible to connect local printers via serial ports Virtual terminal: only virtual terminals on the top of Telnet servers are supported; it is not possible to connect terminals directly to the system, because serial interfaces are reserved for service terminal use Optical disk: the magneto-optical disks are used for file/database backup, charging data backup and event log Service terminal Event log services I/O diagnostics support.
5.2
Switching platform
The basic services that are offered by the switching platform can be divided into three parts: Common services are services that are not related to hardware. For example, digit analysis and statistics are these kind of common functions. The goal is to use common functions whenever feasible. Circuit switching services are specific to TDM, like circuit hunting or circuit group administration. These are needed in the interworking between TDM and ATM based services in the MGW. The third group consists of the ATM switching services.
Nokia Networks Oy
19 (42)
Switching Platform
Packet Switching Packet Switching Physical Layer Processing Physical Layer Processing ATM Switching ATM Switching AAL2 Switching AAL2 Switching AAL Termination AAL Termination Connection Management Signalling Signalling Resource Configuration Resource Configuration Network Maintenance Network Maintenance
Analysis, Routing and Circuit Analysis, Routing and Circuit Switching Switching
Figure 10.
Covers the management functions of both PDH and SDH based transmission interfaces (e.g. Inverse Multiplexing for ATM (IMA) for all PDH based ATM interfaces).
ATM Layer Processing
VPI/VCI translation (header translation) is done by modifying VPI and VCI fields in the ATM cell header. Header lookup checks if VPI/VCI values of incoming cell are allowable and detects OAM and ABR cells.
Policing
Consists in the set of actions taken by the network to monitor and control the traffic. The main purpose is to protect resources from misbehaviour, which can affect the QoS of other already established connections.
Traffic Shaping
Is done to ensure that submitted traffic is within the negotiated limits. Traffic shaping function is done by delaying the cells until they can be emitted in accordance with the traffic contract. Traffic shaping is usually done together with the scheduling function, which itself controls the order in which individual cells get served.
20 (42)
Nokia Networks Oy
Buffer Management
Selects which cells are dropped when network element is overloaded. In general, it is more feasible to drop whole frame (e.g. AAL5 packet) instead of dropping individual cells from many upper layer packets.
Logical Resource Management layer
ATM OAM (Operation, Administration and Maintenance): it supervises all layers of the ATM network. It provides performance monitoring, alarm generation, and failure location services for OSS and other applications.
ATM unit-to-unit communication
In the IPA2800 platform the messages are delivered between computer units via ATM virtual channel connections. Connections have to be explicitly created by software and can be of two major types: point-to-point full duplex ones and point-to-multi-point unidirectional ones. The hardware management system (HMS) provides communication means to set up the ATM connections during unit start up.
ATM Logical Resources
Provides the configuration management of the resources related to switching (parameters of physical and logical interfaces; IMA group parameters, permanent connections / termination points, QoS parameters, static routes). Data is stored permanently in a database and/or in files.
5.3
Nokia Networks Oy
21 (42)
WMSC
TC
Transcoder
RNC BS
WCDMA Base Station
MDC
Macro Diversity Combining WCDMA Radio Network Controller
Figure 11.
Signal processing applications are network element specific. Signal processing applications of ATM Module and Radio Network Controller (RNC) are described below.
5.3.1
Speech transcoding
Speech transcoding function implements speech encoding and decoding necessary in speech transmission from mobile station to public networks. Other supplementary features, such as voice activity detection (VAD) and discontinuous transmission (DTX), are also implemented. Feature supports Adaptive Multi-Rate codec (AMR) towards the UMTS Terrestrial Radio Access Network (UTRAN) side (Iu interface) as specified by 3GPP, and both A-law and mu-law encoded Pulse Code Modulation (PCM) at 64 kbit/s towards the MSC side (A interface). Multiple speech channels can be processed with one digital signal processor. Speech transcoding application is used in Media Gateway (MGW) network element and it resides on the Transcoding Unit (TCU).
22 (42)
Nokia Networks Oy
5.3.2
Macro-Diversity Combining
The Macro-Diversity Combining (MDC) application handles the combining and splitting of the Media Access Control (MAC) frames in the Iub/Iur interface during a diversity handover. The main functions offered by the MDC feature are:
Iu user plane protocol towards Core Network (CN) Radio Link Control (RLC) layer for RT data Ciphering of the RLC/MAC PDUs Media Access Control (MAC) layer for dedicated channels Macro-Diversity Combining and splitting of the MAC frames Frame Protocol (FP) layer for Iub and Iur interfaces Outer loop Power Control (PC) support Macro-Diversity Combining application is used in the Radio Network Controller (RNC) network element and it resides on the Data and Macrodiversity Combining Unit (DMCU).
5.4
Nokia Networks Oy
23 (42)
ICSU A2SU NIP1 DMCU GTPU ICSU MXU 2-0 2-1 A2SU NIP1 DMCU
NEMU
TO WMSC or MGW
Iu-CS
Figure 12.
Step 1: User data from three BTSs (including one that is drift)
The RNC is receiving both user and control data from the BTS. The base stations are connected via ATM and are physically connected into the Network Interface Unit (NIU). The choice of NIU is dependent on the physical network. An A2SU (AAL2 Signalling Unit) is needed to manage the ATM link, as the NIU only supports the lower signalling layers. The NIU and A2SU are connected through an internal ATM connection. The Iub (RNC-BTS) link also contains control information (i.e. BTS commands), on the C-NBAP (Control-Node B Application Part). The RNC uses computer units such as the RRMU (Radio Resource Management Unit) to control the activities of the BTS. Other computer management units are also performing tasks simultaneously, for example the OMU constantly supervises the status of the whole unit. The use of multiple radio links is called macro-diversity and its purpose is to use multiple signals to gain a better quality of connection, at the least cost of air-interface capacity. Ideally the signals should be combined and/or the best signal chosen. To perform this function, a signal-processing unit called the DMCU (Data and Macro-Diversity Unit) is used.
24 (42)
Nokia Networks Oy
ICSU A2SU NIP1 DMCU GTPU ICSU A2SU MXU 2-0 2-1 NIP1 DMCU
NEMU
TO WMSC or MGW
Iu-CS
Figure 13.
Therefore, the user data from all the BTSs (via the A2SU) have to be routed through the ATM fabric switch to the same DMCU. The DMCU is a series of signal-processing cards and the unit will decide on which signal-processing card should be used for which connection. This is part of load sharing within inside the unit. If the student recalls from the previous chapter, the capacity is scaleable and therefore the maximum connection is determined by the hardware configuration of the RNC. The DMCU signal processor then combines and/or selects the best signal that will be the user's data. In the reverse direction (i.e. network user), the mobile takes care of this function.
Nokia Networks Oy
25 (42)
ICSU A2SU NIP1 DMCU GTPU ICSU A2SU MXU 2-0 2-1 NIP1 DMCU
NEMU
TO WMSC or MGW
Iu-CS
Figure 14.
The student should visualise this as a concurrent process. As mentioned before, the unit may have many connections happening simultaneously. Each connection may contain a different service, for example, voice (as in the above case), Internet traffic, video, etc. The DMCU is only processing low level user information. The unit may also be supervising BTS restarts and downloading new software. The operator may be adding new sites and making configurational changes to the network via the NEMU (Network Element Management Unit). In both of these cases, the different units have to communicate with each other. This is usually achieved through the cross-connections in the switching fabric unit. The resulting user information after being processed is then ready for transmission to the Nokia MGW (or 3G compatible MSC). There is one and very likely more physical connection between the RNC and MGW/MSC. The user data is routed through the switching fabric unit not towards the NIU but towards the A2SU controlling the NIU. The higher level ATM signalling is added before the resulting signal is transmitted on the Iu interface towards the MGW/MSC, via the NIU.
26 (42)
Nokia Networks Oy
ICSU A2SU NIP1 DMCU GTPU ICSU A2SU MXU 2-0 2-1 NIP1 DMCU
NEMU
Figure 15.
If the data was destined for the packet core network, the GTPU (GPRS Tunnelling Packet/Protocol Unit) is then used before the connection onto the Iu-PS interface. To continue this example briefly, the resulting information would be received by the MGW, and similar processes also take place. The NIU is supervised by the A2SU, and in the case of voice, the user data is sent to a signal processor that performs the signal processing of speech. This case should clarify the student's understanding of the different between the different computer units, whilst re-enforce the philosophy of the Nokia IPA2800 platform.
Nokia Networks Oy
27 (42)
- Interface type: UNI/NNI - Access profile (VPI/VCI bits, # of connections (VPC/VCC), bandwidth)
AAL2 connection
Figure 16.
28 (42)
Nokia Networks Oy
The access profile created for an ATM interface defines the connection structure built under that ATM interface. Following access profile parameters are defined: number of VPI/VCI bits, number of connections (VPC/VCC), and bandwidth. External termination points are created both on VP level and VC level. They are the terminating ends of the VP/VC connections. Virtual Path Link termination points (VPLtp) must be created before any Virtual Channel Link termination points (VCLtp) and VC level connections can be created under the VPLtp. Each VPLtp is related to one ATM interface. The ATM interface configuration defines the limits to the total VPLtp capacity reservations. The number of VCLtps created under each VPLtp depends on the total VPLtp capacity. Therefore, when reserving capacity for a VPLtp, number of VC level connections under the VPLtp should be planned. Note It is beyond the scope of this module to discuss the basics of ATM or the ATM routing and digital analysis in the IPA2800 platform.
6.1
AAL5 is used for internal communication, SS7 and UNI signalling links, and IP over ATM (multi-protocol encapsulation over ATM Adaptation Layer 5 according to RFC 1483). AAL2 supports bandwidth efficient transmission for low bit rate and short length packet applications that are delay sensitive (e.g. voice packets produced by speech codecs). It is used on Iub and Iur for the transport of user data.
The IPA2800 utilises a technique known as Inverse Multiplexing for ATM (IMA); a methodology that provides modular bandwidth, for user access to ATM networks and for connection between ATM network elements, at rates between the traditional order multiplex level. An example is to achieve rates between the DS1/E1 and DS3/E3 levels in the asynchronous digital hierarchies. DS3/E3 links are not necessarily readily available throughout a given network, and therefore the introduction of ATM Inverse Multiplexes provides an effective method of combining the transport bandwidths of multiple links (e.g. DS1/E1 links) grouped to collectively provide higher intermediate rates.
Nokia Networks Oy
29 (42)
e.g. BTS
IMA Group
PHY Layer
PHY Layer
Physical Link # 2 E1
PHY Layer
PHY Layer
Physical Link # 3 E1
PHY Layer
Figure 17.
Streams of information from the BTS to the RNC, through IMA channels
The ATM Inverse Multiplexing technique involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links grouped to form a higher bandwidth logical link whose rate is approximately the sum of the link rates. This is referred to as an IMA group. The above figure provides a simple illustration of the ATM Inverse Multiplexing technique in one direction. The same technique applies in the opposite direction. IMA groups terminate at each end of the IMA virtual link. In the transmit direction, the ATM cell stream received from the ATM layer is distributed on a cell-by-cell basis, across the multiple links within the IMA group. At the farend, the receiving IMA unit recombines the cells from each link, on a cell-bycell basis, recreating the original ATM cell stream. The aggregate cell stream is then passed to the ATM layer. The IMA interface periodically transmits special cells that contain information that permit reconstruction of the ATM cell stream at the receiving end of the IMA virtual link after accounting for the link differential delays, smoothing CDV introduced by the control cells, etc. These cells, defined as IMA Control Protocol (ICP) cells, provide the definition of an IMA frame.
30 (42)
Nokia Networks Oy
PRC
MSC
MSC
PRC
PRC
ATM Module
RNC
PRC
PRC
PRC
BS
BS
BS
Figure 18.
Platform provides SDH equipment slave clock (SEC) as defined in EN 300 462 series standards. The system clock is synchronised to incoming network timing signal. External timing reference signal can be selected from four possible types of input (2048 kbit/s, 2048 kHz, 1544 kHz, 64 kHz + 8 kHz). The synchronisation unit also provides an external timing output, which can be used to transmit either system clock or one of the timing reference signals extracted from the network interface units. The synchronisation unit has three timing inputs that are connected by cabling to three selected network interface plug-in units (SDH or PDH). The system clock can be synchronised to the SDH network by detecting the signal from incoming STM-1 line. In the network interface plug-in unit one of the STM-1 ports is selected to give timing. In similar fashion, PDH transmission based
Nokia Networks Oy
31 (42)
network interfaces (E1/T1/JT1) can also be used as timing reference sources. With this configuration at least three timing inputs from upper network level can be made available. The previous figure illustrates an example of timing distribution chain. Primary Reference Clock (PRC) feeds the network, and an optional feeding from alternative synchronisation sources is included in the picture with dashed line. Arrows between network elements present timing information flow.
32 (42)
Nokia Networks Oy
8.1
Iub interface
RNC
BTS disables and reconfigures resources ff t d Disabling information is sent to RNC via logical resource management An alarm is set
RNC supervision detects connection break Resources are disabled An alarm is set
Figure 19.
Nokia Networks Oy
33 (42)
The alarm system stores and maintains a history of past alarm events on a disk file. It offers a user interface for displaying the history. On receiving a notice, disturbance, or fault observations from the supervision system, it filters incoming observations and generates alarms from them. It cancels observations on request or after a predefined alive time. It informs recovery which functional unit or other maintenance instance is suspected to be faulty. In addition, the network element level alarm system performs network element level handling for alarm events received from different elements, such as transmission devices connected to the RNC. It defines the common alarm output format, the user interface, and the NetAct interface for alarms. If the fault is an IPA2800 unit, IO device or clock, the system will attempt to diagnose the location of the fault (to the closest plug-in unit). Where possible, a recovery is attempted. If a unit is faulty, then the system will take a redundant unit into use, if possible. It monitors the correction of a fault together with fault recovery by periodically asking diagnostics to test the functional unit in question.
8.2
Figure 20.
34 (42)
Nokia Networks Oy
The graphical interface is accessed from NEMU (Network Element Management Unit) and supports operation and maintenance functions such as viewing alarms and making on-line statistics about the network element. This is the primary tool used in the operation of the element. However, for those tasks that are of a much lower and specialised level (e.g. adding a new unit, integrating the Iu interface), a textual menu- driven interface exists, called MML (Man-Machine Language). The MML is designed for use of a system engineer, who occasionally needs to perform certain tasks. The common or daily tasks are possible through the webbased interface. The web-based interface can be launched from a computer, with a web-browser and the correct JAVA plug-in. The MML sessions can be launched remotely from a Telnet connection.
DX 220
DX220-LAB
2000-09-14
21:53:55
MAIN LEVEL ? ..... A ..... D ..... I ..... L ..... N ..... O ..... Q ..... R ..... T ..... U ..... W ..... Y ..... Z; .... DISPLAY MENU ALARM SYSTEM ADMINISTRATION SYSTEM SUPPORT AND COMMUNICATION I/O SYSTEM ADMINISTRATION BROADBAND ADMINISTRATION SS7 NETWORK ADMINISTRATION SUPPLEMENTARY SS7 NETWORK ADMINISTRATION O&M NETWORK ADMINISTRATION ROUTING ADMINISTRATION TRAFFIC ADMINISTRATION UNIT ADMINISTRATION SYSTEM CONFIGURATION ADMINISTRATION SYSTEM SUPERVISION END DIALOGUE/DESTINATION SELECTION (:)
Figure 21.
MML commands
The IPA2800 uses individual login names and group profiles to control access to the network element. These are configured by the system administrator who defines the correct access rights for each user. As a footnote for the student, a lower level interface exists, called the service terminal. This is an interface on the computer level and is used in the testing, commissioning and troubleshooting of the network element. These are very low level commands such as disk and memory handling.
Nokia Networks Oy
35 (42)
8.3
Figure 22.
Using NEMU
If you take the routine preventive maintenance tasks of checking the status of the interfaces, you can open up the web browser and connect to the network element. You will be required to type in our name and password. Then, depending on the access rights, you will be given menu options of the functions you can perform. In the case of checking the status, you can select from the menu network interfaces and start to examine each individual state looking for a situation where the interface is not in an UP state. This example is shown in the following figure.
36 (42)
Nokia Networks Oy
Figure 23.
The IPA2800 NEMU supports the open TCP/IP and COBRA based protocols and is used as a network management interface between the network element and the network management system (NetAct).
Nokia Networks Oy
37 (42)
3.
4.
5.
Which of the following is not a valid redundancy principle? a. b. c. d. n+1 2N load sharing N*2
38 (42)
Nokia Networks Oy
6.
Which of the following statements about processing capacity is true? a. b. c. d. It is fixed. It is related to signal processing cards installed. It is dependent on the OMU unit. None of the above.
7.
No
8.
Why is ESD protection necessary? a. b. c. d. To avoid injury to the engineer handling the card. To avoid damage to the plug-in unit. To avoid damage to the cabinet. To avoid damage to environment.
9.
10.
No
11.
Which of the following best describes the signal processing platform? a. b. c. d. It is dynamically allocated dependent on the processing need. It is part of the distributed management units. It controls the ATM resources. All of the above.
12.
Which of the following units are signal processing units? a. b. c. d. OMU NIU DMCU SFU
Nokia Networks Oy
39 (42)
13.
14.
15.
No
16.
17.
If you were to check the states of the BTS alarms, which interface would you use? NEMU
MML
18.
If you were to create the Iu interface, which IPA2800 interface would you use? NEMU
MML
40 (42)
Nokia Networks Oy
Nokia Networks Oy
41 (42)
MAC MDI MII M-PHY MUX OAM O&M PCB PDH PHY RISC SAR SCSI SDH SMD STM-n SF T1 TC TDM UTOPIA VC VP
Media Access Control. Set of protocol that is the lower part of data link layer and the basis of the IEEE LAN specifications. Medium Dependent Interface Media Independent Interface Multiple PHY connection of UTOPIA devices Multiplexer Operations Administrations and Maintenance Operations and Maintenance. Set of administrative and supervisory actions regarding network performance monitoring, failure detection and system protection. Printed Circuit Board Plesiochronous Digital Hierarchy Physical Layer. The bottom layer of ATM protocol reference model. It provides ATM cell transmission over the physical interfaces that connect ATM devices. Reduced Instruction Set Computing Segmentation and Reassembly. Partitions information frames into cells at the source and reassembles these cells back into information frames at the destination. Small Computer System Interface Synchronous Digital Hierarchy. A hierarchy that designates signal interfaces for very high-speed digital transmission over optical fibre links. Surface Mounted Device Synchronous Transport Module-n. An ITU-T-defined SDH physical interface for digital transmission in ATM at n times the basic STM-1 rate. Switch Fabric. The central functional block of ATM switch, which is responsible for buffering and routing the incoming cells to appropriate output ports. A TDM digital channel carrier that operates at rate of 1.544 Mbps. North American hierarchy level 1 interface. Transmission Convergence. One of the two PHY sublayers that are responsible for adapting the ATM cells into a stream of bits to be carried over the physical medium. Time Division Multiplexing. A technique for splitting the total bandwidth into several channels to allow bit streams to be combined. Time axis divided to fixed length slots. Universal Test and Operation Physical Interface. An Interface to provide connectivity at PHY level among ATM entities. Virtual Channel. A term to describe unidirectional flow of ATM cells between connecting points (switching or end-user) that share a common identifier number VCI. Virtual Path. A term to describe a set of VCs grouped together, between crosspoints (i.e. switches).
42 (42)
Nokia Networks Oy