This action might not be possible to undo. Are you sure you want to continue?
dn00254734 Issue 1-0 en
# Nokia Networks Oy Nokia Proprietary and Confidential
WCDMA RAN Integration guidelines
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.
# Nokia Networks Oy Nokia Proprietary and Confidential
dn00254734 Issue 1-0 en
Contents 3 List of tables 4 List of figures 5 1 2 3 3.1 3.2 4 4.1 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.9.1 5.9.2 5.9.3 5.10 About WCDMA RAN Integration Guidelines 7 About integrating WCDMA RAN 9 Planning 17 Data flows 18 Parameters from planning
Integrating WCDMA RAN to Nokia NetAct 21 RNC split 22 Integrating WCDMA RAN 23 Configuring physical PDH/SDH interfaces 26 Creating IMA group 27 Creating ATM resources 28 Creating TCP/IP configuration 29 Defining external time source for network element 30 Creating signalling connections 30 Creating routing objects and digit analysis 31 Configuring synchronisation inputs 32 Radio network configuration 33 Configuring the radio network controller 33 Creating radio network connection configuration 34 Configuring the radio network objects 35 Testing integration 35
dn00254734 Issue 1-0 en
# Nokia Networks Oy Nokia Proprietary and Confidential
WCDMA RAN Integration guidelines List of tables Table 1 Parameters from planning 19 4 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .
23 Main integration phases in RNC 25 dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 5 (36) .List of figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Phases of setting up WCDMA RAN 10 WCDMA RAN commissioning and integration tasks in network elements 13 3G network architecture 14 3G network and logical interfaces between network elements.
WCDMA RAN Integration guidelines 6 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .
About WCDMA RAN Integration Guidelines 1 About WCDMA RAN Integration Guidelines Note THIS DOCUMENT DESCRIBES PRODUCTS AND SOLUTIONS STILL IN DEVELOPMENT AND THUS DOES NOT AS SUCH REFLECT THE FINISHED SOLUTION. This document describes the integration of WCDMA radio access network. The detailed integration instructions are in the network element libraries. After reading this document the operator has an overall knowledge about the integration and knows how to proceed with network element integration. It gives an overview of the integration procedures. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 7 (36) . MAINLY PHASE 1. For a general overview of the components and functionalities of Nokia WCDMA RAN. please refer to WCDMA Radio Access Network Technical Overview and WCDMA RAN Features. The document contains general information about planning and implementing the integration of the WCDMA radio access network.5. THE OPERATOR SHOULD CHECK THE PHASES AND THEIR SCHEDULE WITH THEIR LOCAL NOKIA REPRESENTATIVES. You can find definitions for terms used in this document in WCDMA RAN Glossary. RAN RELEASE 1 SOFTWARE WILL BE DELIVERED TO THE OPERATORS IN SEVERAL PHASES.0 AND 1.
WCDMA RAN Integration guidelines 8 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .
it is ready for commercial use and calls can be made via both the circuit and packet switched domains. During commissioning the network elements have been configured and tested as stand-alone entities. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 9 (36) . After integrating WCDMA RAN.About integrating WCDMA RAN 2 About integrating WCDMA RAN Integrating WCDMA radio access network (RAN) means configuring interconnections between network elements and customising their parameters. Integration is made after network elements have been installed and commissioned.
supported by the network element. The LMT is typically a laptop PC. The BTS and AXC EMs faciliate two types of commissioning operation: 10 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . commissioning of the constituent network elements must firstly be performed. which is connected to the network element. which are run from the local management tool (LMT). Communication between the EM and the network element O & M software utilises the TCP/IP based data communication network (DCN). Commissioning of both the BTS and the AXC is performed through the respective element manager (EM) application programs. Phases of setting up WCDMA RAN Prior to integration of the WCDMA RAN.WCDMA RAN Integration guidelines Figure 1. through the local management port (LMP).
The order is prescribed in the AXC commissioning manual. is not stored to the BTS. The AXC planned commissioning procedure is almost identical to the BTS planned commissioning procedure. however all needed parameter values are simply loaded from a pre-stored file on the LMT. The wizard guides the commissioning engineer through a series of form based dialogues. it is sent to BTS from RNC. The manual commissioning of the AXC does not yet use a commissioning wizard (coming later). Following the commissioning operation. the final commissioning report can be transferred for storage and subsequent use to Nokia NetAct. Radio network configuration in RNC can be done either with the element manager or with the RNW downloaded from Nokia NetAct. except for the connection configuration. Instead. When all parameters have been assigned.About integrating WCDMA RAN * manual commissioning planned commissioning * Manual commissioning of the BTS is achieved through a special menu of the graphical user interface (GUI) called the commissioning wizard. the data is transferred to the BTS itself and a final WCDMA loop test is performed in the BTS. The planned commissioning is easy to administer. during WCDMA RAN integration. after the network planning data has first been produced from the NetAct Planner tool. In the case of the BTS. The commissioning engineer fills in the needed parameter values for each field in the dialogue. which is maintained by the commissioning wizard. as part of the WCDMA RAN integration procedure. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 11 (36) . The XML format site configuration file is itself produced from the Nokia NetAct. the complex data set called radio network configuration (RNW). during the commissioning operation.5) The BTS and AXC commissioning are designed to program enough configuration data into the network element. Therefore the manual commissioning requires the commissioning engineer to enter a sequence of menu selections. It contains commissioning parameters for the BTS. The results of the commissioning operation are recorded to a commissioning report. in order to build up the needed AXC configuration. fast to complete and minimises the risk of incorrect parameter values being entered into the BTS. The file is called the site configuration file. The file stores the data in XML format. The RNW in the BTS is also activated under the control of the RNC. to facilitate starting it up and assuring its capability to function. (Note: Planned commissioning of AXC may not be supported prior to phase 1. Planned commissioning of the BTS is also activated through the commissioning wizard.
BTS and integrated or standalone AXC. The table WCDMA RAN commissioning and integration tasks in network elements shows the division into commissioning and integration tasks in RNC. creating an uplink DCN connection via a LAN network from RNC to NetAct during commissioning is needed in order to download the radio network configuration needed in integration. Nevertheless. Individual configuring of network elements can take place without functioning data communication network.WCDMA RAN Integration guidelines Network management connections. O & M connections can be set up at different stages. DCN connections in BTS and AXC are created also during the commissioning and they use IP over ATM. 12 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .
WCDMA RAN Integration Guidelines looks at the integration from the RNC's point of view.About integrating WCDMA RAN Figure 2. WCDMA RAN commissioning and integration tasks in network elements Based on this division. Radio network architecture The network elements of Nokia WCDMA RAN are: dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 13 (36) .
Figure 3. Transmission equipment is not handled in this document. Nokia NetAct Framework and their relations in the integrated network. interfaces. The figure is a logical picture of the network elements. 3G network architecture 14 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . The core network is not in the scope of this document. but is presented to show the relation between these two networks. but creating the needed PDH/SDH connections for transmission cards is covered.WCDMA RAN Integration guidelines * radio network controller (RNC) base station (BTS) ATM cross-connect (AXC) integrated with BTS stand-alone AXC * * * WCDMA RAN Integration Guidelines is based on the following 3G network architecture.
About integrating WCDMA RAN For more information on WCDMA RAN. transmission and DCN plans have been made RNC. Prerequisites for integrating WCDMA RAN These phases need to be completed before integration can start: * Radio network. refer to WCDMA Radio Access Network Technical Overview. BTS and AXC have been commissioned * dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 15 (36) . RNC to another RNC and RNC to BTS integration is covered in Integrating WCDMA RAN. Integration order Network entities in WCDMA RAN can be integrated in a certain order before the next network entity can be integrated. the network entities can be connected in this order: 1 2 3 4 RNC to Nokia NetAct RNC to core network RNC to another RNC (when applicable) RNC to BTS RNC to Nokia NetAct integration is described in Integrating WCDMA RAN to Nokia NetAct and RNC to core network. From the point of view of the RNC.
WCDMA RAN Integration guidelines 16 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .
ATM. Configuration files are used in the first phase of the first release. For more information on planning tools and services. IMA and other transmission parameters are created and completed with Nokia NetAct planning tools. Full scale network plan contains the configuration of the network level. Radio network configuration for RNC integration and site configuration files for BTS and AXC commissioning are created.Planning 3 Planning Planning the different aspects of WCDMA RAN by using planning tools and services. Storing plans Radio network plans and site configuration files are stored in Nokia NetAct from where they can be easily accessed. Input for WCDMA RAN integration is needed from these technical areas: * radio network planning transmission and transport planning DCN planning * * Creating plans Radio network plans and transmission plans including IP. produces the input for configuring and integrating WCDMA RAN. Nokia NetAct provides interfaces to network elements for downloading radio network parameters. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 17 (36) . refer to WCDMA Radio Access Network Technical Overview or to Nokia NetAct documentation. The following sections explain how these technical areas are planned and what the resulting input for integration is. such as Nokia NetAct Planner and Nokia Planning Services. later work orders can also be used. Plans are used both in commissioning and integration processes. Plans are made with Nokia NetAct planning tools. network elements (including NE identification) and connections.
the data flows work in both directions in regards to radio network data. After connecting the laptop to the local management port the element manager is started. The radio network topology and parameter data can be uploaded to Nokia NetAct for plan tuning purposes. In case of already operational networks. all RNW objects can be managed from NetAct using remote RNC element manager. the data flow is completely from Nokia NetAct to the network elements. the following radio network managed objects and their parameters can be handled via NWI3 network management interface. RNC propagates it to other network elements. including: * connection configuration (CoCo) (EM) ATM termination points (EM. access profile and termination point profiles in the RNC.WCDMA RAN Integration guidelines Using plans Radio network configuration is downloaded from Nokia NetAct to RNC and activated there. Remote RNC element manager applications can be used from Nokia NetAct to enter ATM interface. NetAct . MML) * 18 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .1 Data flows As long as the network is not operational. Site configuration file is downloaded to the local management tool.RNC When using plans. 3. * BTS site cell adjacent cell handover path Frequency measurement control * * * * In addition. or using remote MML session. Site configuration file is for AXC and BTS only. SDH/PDH nodes are configured using element manager locally or from Nokia NetAct remotely. the configuration is updated to the network element and site configuration is completed.
PowerControl.Planning * IMA group (MML) ATM interface (MML) ATM access profile (MML) * * 3.2 Parameters from planning The table gives an outline of the parameters produced during the planning phases. Admission Control. Parameters from planning Planned area Radio network planning Output * Radio link budget calculations Capacity calculations per BTS RNC requirements Cell number Cell global identity Carrier Frequency Downlink scrambling codes Primary common pilot channel coverage Information bit rates of the served MS in each cell Handover parameters Other WCDMA Cell related parameters (Handover Control. Load Control) * * * * * * * * * * dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 19 (36) . Table 1.
WCDMA RAN Integration guidelines Table 1. VPI/VCI values are reservedfor each BTS in the RNC Required type of a particular ATM connection: Constant Bit Rate(CBR) or Unspecified Bit Rate (UBR) Traffic parameters for CBR: Peak Cell Rate (PCR) or Cell TransferDelay (CTD) or Cell Delay Variation Tolerance (CDVT). RNC and any ATM switch). Traffic parameters forUBR: PCR IMA group and link numbers Required link transmission capacity and transmission type Time-slot allocation information of transmission links synchronisation plan with timing sources and hierarchy leveldefinitions ATM cross-connections (external devices) PDH/SDH cross-connections (external devices) IP address netmask default gateway host name domain name domain name system (DNS) server addresses network time protocol (NTP) server addresses and time zone OSPF area ID IP forwarding IP time-to-live (hops) Interface MTU Broadcast address VPI/VCI for O&M * * * * * * * * DCN planning * * * * * * * * * * * * * 20 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . Parameters from planning (cont. endpoints in BTS.) Planned area Transmission and transport planning Output * VPI/VCI values (translation tables) of ATM connections (in eachAXC.
Installing and commissioning of Nokia NetAct includes the following activities: * operation system and platform installed NWI3 up and running domain name system (DNS) and network time protocol (NTP) services running authentication server installed open shortest path first (OSPF) configured in DCN backbone routers licence management element managers installed and integrated radio network plans are ready transmission network plans are ready site configuration tool up and running * * * * * * * * * dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 21 (36) . Detailed instructions can be found from Integrating RNC in Nokia NetAct documentation. commissioned and configured.Integrating WCDMA RAN to Nokia NetAct 4 Integrating WCDMA RAN to Nokia NetAct Integrating WCDMA RAN to Nokia NetAct means making interconnections on the DCN network between RNC and Nokia NetAct. From the point of view of WCDMA RAN integration. the network plans can be downloaded to RNC and the rest of radio network integration can be accomplished. DCN connections in BTS and AXC have been already made during commissioning. Preconditions Nokia NetAct has been installed. this is part of commissioning of RNC. RNC has been installed. After integrating the DCN.
the rest of integration can be continued. 22 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . In this procedure.WCDMA RAN Integration guidelines Phases * configuring operation and maintenance unit (OMU) configuring network element management unit (NEMU) configuring the connection to Nokia NetAct LAN connection IP over ATM connection routing: static routes * * Result DCN connection for O & M operations between RNC and Nokia NetAct has been created. after which the already existing BTS sites can be configured to be under the control of the new RNC. It can receive information on other activities from the network as well.1 RNC split As the network grows and new capacity in WCDMA RAN is needed. there may be a need to rehost existing BTS sites under a new RNC. the new RNC needs first to be integrated in the surrounding network. 4. Nokia NetAct can now manage the radio network configuration as well as the network. More information on RNC split can be found from Nokia NetAct Rehosting WCDMA BTS Sites in Nokia NetAct documentation. This is called RNC split. Radio network plans can be downloaded from Nokia NetAct to RNC. After this.
For detailed information and instructions on integrating RNC. please refer to RNC Integration or Radio Network Configuration Management in RNC documentation. For detailed integration instructions.Integrating WCDMA RAN 5 Integrating WCDMA RAN The integration instructions are based on the following 3G network. They include commands and steps for the phases described in this section. Figure 4. 3G network and logical interfaces between network elements. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 23 (36) . please refer to the specific network element documents.
Logical interface between RNC and the serving GPRS support node (SGSN). In BTS update. Logical interface for the interconnection of two RNCs components of the radio access network. 24 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . Logical interface between the RNC and the core network. Logical interface between RNC and WCDMA BTS. This configuration data contains radio network parameters for the BTS.WCDMA RAN Integration guidelines Logical interfaces in the 3rd generation network: A' Iu-CS Iu-PS Iur Iub Logical interface between a multimedia gateway (MGW) and a mobile switching centre (MSC). RNC forwards the radio network configuration data to BTS. Also the common channel configurations are updated to the cells. which includes creating connection configuration. The figure Main integration phases in RNC illustrates the main phases in integrating RNC to the radio network starting from the transmission configuration and ending in the configuring of radio network. cell ids of those cells that are under a BTS and radio network parameters for each cell. radio network configuration and BTS update.
Main integration phases in RNC dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 25 (36) .Integrating WCDMA RAN Figure 5.
you must configure the PDH/SDH exchange terminals. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Configuring plesiochronous digital hierarchy (PDH) and/or synchronous digital hierarchy (SDH) interfaces Creating inverse multiplexing for ATM (IMA) groups Creating asynchronous transfer mode (ATM) resources for signalling. and signalling network. Before creating the ATM/TDM resources for the DCN. All the steps are from the RNC's point of view and are made by the element manager locally at a site.1 Configuring physical PDH/SDH interfaces Transmission between RNC and BTS has to be configured before the NE integration can start. user data and for DCN Creating TCP/IP and IP over ATM configuration for DCN network Connecting to Nokia NetAct Setting external time source Creating SS7 signalling configuration Creating routing objects and digit analysis Configuring synchronisation inputs Configuring the radio network controller Creating radio network connection configuration with element manager Creating frequency measurement control Creating a handover path Creating a WCDMA BTS site Creating a WCDMA cell Creating adjacency for a WCDMA cell Testing the integration 5. user data. 26 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . Steps 12-16 can also be made by downloading and activating a radio network plan in RNC.WCDMA RAN Integration guidelines Quick integration guide The main steps for integrating a 3G network element to the mobile network.
DCN integration should have been finished. The IMA groups are created at both ends of the transmission lines. RNC has to be installed and commissioned. NIP1 is an ATM interface unit containing PDH E1/T1/JT1 interfaces with IMA function. There can be several IMA groups per one functional unit. Preconditions The PDH exchange terminals (PETs) to be combined to an IMA group must belong to the same NIP1 functional unit. DCN connections and settings are operational in order to have a functional management interface. 5.2 Creating IMA group IMA groups need to be created to which you can later connect an external ATM interface. which are seen as one virtual IMA link.Integrating WCDMA RAN Preconditions BTS with integrated AXC must be installed and commissioned. When creating IMA groups. which allows for flexible grouping of physical links to logical IMA groups. External SDH/PDH equipment must be installed and commissioned. Result PDH/SDH exchange terminals and the physical PDH/SDH interfaces have been configured. Phases * Configuring physical PDH/SDH interfaces. meaning O & M connections and NWI3 mediator. All the PETs of one IMA group have to belong to the same NIP1 functional unit. but all the transmission lines of one IMA group must go to the same direction. the transmission lines are identified with PETs that they are connected to. These instructions are for configuring PDH/SDH interface cards. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 27 (36) . The purpose of Inverse Multiplexing in ATM network (IMA) is that the capacity of many low bit rate transmission lines can be combined into a group that is seen as a single virtual link by the ATM layer of a network element.
Phases * Creating ATM resources for Iub interface ATM interface and its access profile and termination points need to be created for Iub interface. If you connect the ATM interface to an IMA group. for signalling. Preconditions Hardware (including exchange terminals) has been configured. When defining traffic parameter values.WCDMA RAN Integration guidelines Phases Creating an IMA group. you need the MMLs only for creating ATM interface and its access profile. Result IMA group has been created. * Creating ATM resources for Iu-CS interface Creating ATM resources for Iu-PS interface Creating ATM resources for Iur interface * * 28 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . e. is needed.g. create first the IMA group.3 Creating ATM resources Creating resources for VP/VC connections. 5. routing and IP over ATM connections. Normally. use the Object Browser (in RNC providing a general view of radio network managed objects) for creating termination points. take into account the capacity limitations of a single ATM interface. The number of VP link termination points and VC link termination points for enabling different connections. For the Iub interface. The resources should not be misconfigured as this causes the system to reject the creation of the VP/VC connections later. depends on the capacity of the ATM interface and the structure of the network.
Integrating WCDMA RAN Result ATM resources have been created for the interfaces. The network elements internal subnet that connects network element management unit (NEMU) and units to a same subnetwork. The units that will forward information towards another network elements must be configured as IP routers. 5. and every unit includes one Ethernet interface. Preconditions The TCP/IP network has been planned very carefully before the actual configuration. The units can be connected to each other via LAN. You can not edit all the text files that include IP information. Phases * Configuring TCP/IP stack Configuring IP over ATM interfaces (with element manager in AXC) * Result TCP/IP stack in a network element has been configured to act as a router. can be established via a hub device (or Ethernet bridge). dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 29 (36) .4 Creating TCP/IP configuration In RNC only operation and maintenance unit (OMU) need to be configured to act as a router and a host. The units can be configured with MML commands or editing some of the text files that include IP information.
5. Iu-PS and Iur interfaces 30 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .5 Defining external time source for network element After defining the external time source the network element has the same time as Nokia NetAct time server has after a certain time period. Network elements check the correct time every 15 minutes from Nokia NetAct time server using NTP messages. Preconditions TCP/IP connections must be created before you can define the external time source in Nokia NetAct time server. Phases * Checking current date and time in the network element Checking the NTP server's IP address Setting the IP address to the NTP time server * * Result Network elements in WCDMA RAN have the same time that Nokia NetAct time server has. Preconditions Signalling plans must have been created carefully.WCDMA RAN Integration guidelines 5. Phases * SS7 signalling network configuration for Iu-CS.6 Creating signalling connections Signalling connections for control data are needed before user data connections can be created.
Result Signalling connections have been created. Digit analysis determines the destination of a call and selects an ATM route to the destination. use the GUI application for configuring ATM connections in which the routing objects and digit analysis are created automatically by the system. to the desired destination. In Iu-CS and Iu-PS interface digit analysis is not used. 5. The routing configuration in ATM network must be done in the following order: 1 2 3 4 creating ATM route creating VCC endpoint groups creating individual VCC endpoints creating digit analysis (not in Iu interface) Preconditions The SAAL UNI signalling links and appropriate broadband MTP3 signalling have been created and the associated VC link termination points (VCLtps) for the endpoints have been created. Routing objects and digit analysis for user data links can be created next. the route under which the endpoints are to be created must allow the type of the endpoints. Iur. The routing objects and digit analysis must be created at both ends of the Iub interface between two network elements before any user plane connections can be built between them. Iu-CS and Iu-PS interfaces and digit analysis for Iub and Iur interfaces with MML commands is needed. Furthermore. For the Iub interface. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 31 (36) . voice or data.Integrating WCDMA RAN * AAL2 signalling link creation for Iub interface.7 Creating routing objects and digit analysis Creating routing objects for Iub. The primary purpose of routing is to locate free resources in an ATM network in order to direct user plane traffic. Signalling links are created automatically when the GUI is used.
Inputs can be changed later.WCDMA RAN Integration guidelines Phases * Creating routing objects and digit analysis for Iub interface The associated signalling used is AAL2 signalling. Use the forced reference for example when the system clock synchronisation cannot for some reason be used for any line synchronisation references. 5. Phases * Setting parameters for all synchronisation references 32 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en . * Creating routing objects and digit analysis for Iur interface The associated signalling used is broadband MTP3 signalling. you can create connection configuration for Iub. The routing objects must be created at both ends of the Iu interface between two network elements before any user plane connections can be built between them. The routing objects and digit analysis must be created at both ends of the Iub interface between two network elements before any user plane connections can be built between them. Preconditions Interrogating the available synchronisation references. Result Routing objects and digit analyses have been created for the interfaces. The associated signalling used is broadband MTP3 signalling. The routing objects and digit analysis must be created at both ends of the Iur interface between two network elements before any user plane connections can be built between them. if needed. After the operation.8 Configuring synchronisation inputs Synchronisation inputs always need to be created when bringing a network element into use. * Creating routing objects for Iu-CS and Iu-PS interface Digit analysis is not used in Iu interfaces.
9. There are values in the RNC parameters. 5. Phases * Identifying the RNC Confirming the operation * Result The RNC has been identified.1 Configuring the radio network controller The very first task of configuring the radio network is identifying the RNC. If the RNC is not identified. Preconditions RNC is installed and commissioned and all the above mentioned configuration phases have been completed. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 33 (36) . These parameters can later be changed if the system's behaviour needs to be changed. Radio network configuration can also be made by downloading and activating the radio network plan in RNC. a graphical user interface in RNC.Integrating WCDMA RAN * Enabling the distribution of outgoing signal Setting operation mode of system clock * Result Synchronisation inputs have been created for the network elements and the whole of WCDMA RAN is synchronised. Obligatory parameters have been planned. You have to set the ID of the RNC and other obligatory parameters.9 Radio network configuration Radio network configuration can be made locally using the element manager (EM). you cannot proceed with the configuration management. The RNC must be identified before anything else is done. 5.
Without ATM layer configuration. If the automatic ATM configuration option is used. With ATM termination point configuration the needed ATM termination points are created to the system.WCDMA RAN Integration guidelines 5. Phases * Creating radio network CoCo Confirming the operation * The administrative state of the VP/VC link termination points should be unlocked if the termination points already exist in the system. Control/user plane configuration is initiated during the CoCo creation if the CoCo Id or ATM interface/VPI/VCI triplet of the C-NBAP link is found from a WCDMA BTS object. The connection configuration creation can be separated into two phases: * ATM layer configuration/ATM layer check. Control/user plane configuration (CoCo . Result The CoCo object with corresponding ATM layer configuration and control/user plane configuration has been created. 34 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .9. The virtual path link termination point (VPLtp) can be used by several CoCo objects and the VPLtp can exist in the system when the automatic ATM configuration is used. * Preconditions Required parameters have been planned. a check is performed to find that ATM termination points exist in the system. ATM connection should have been created to the system with an access profile related to it.2 Creating radio network connection configuration A new logical connection configuration (CoCo) object is created to display the transmission in the Iub interface and other connection-related parameters.WCDMA BTS connection). CoCo object is created to reserve the transmission resources in RNC for the WCDMA BTS. the termination points are created in unlocked state by default.
1 2 3 4 5 creating frequency measurement control creating handover path creating a WCDMA BTS site creating a WCDMA cell creating an adjacent WCDMA cell 5. Adjacencies have been created between BTSs. it is ready for traffic. Hardware elements perform self-testing or testing can take place during the activation for actual use. Testing can take place at different stages during integration.Integrating WCDMA RAN 5.9. dn00254734 Issue 1-0 en # Nokia Networks Oy Nokia Proprietary and Confidential 35 (36) .10 Testing integration After completing the integration of WCDMA RAN.3 Configuring the radio network objects Radio network objects can be configured in two ways: * by downloading the radio network plan from Nokia NetAct to RNC and activating the plan in RNC by using the element manager and configuring the objects one by one * Configuring the radio network objects with element manager The following objects are created using the element manager. Mobile phones are available. please refer to RNC Integration or Radio Network Configuration Management in RNC documentation. Preconditions Testcase has been planned. For detailed instructions on the steps. Several cells and BTSs have been created in order to make a handover. A test call can be made to check that a call can be set up and handovers are working after a BTS has been created.
36 (36) # Nokia Networks Oy Nokia Proprietary and Confidential dn00254734 Issue 1-0 en .WCDMA RAN Integration guidelines Phases * Setting up a call through a created BTS Locking the cell which is transferring the call and using a forced handover * Result Handover has been made and call has succeeded. Phases * Unlocking the cell if needed Checking for active alarms using Nokia NetAct Alarm Monitor * Result No unrelevant alarms have been set.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.