03 02 RN33253EN20GLA0 Activate IP Based Iu Iur Interfaces

Nokia Siemens Networks WCDMA RAN, rel. RU20, operating documentation, issue 1

Activating RAN750 and RAN75: IP based Iu-PS and IP based Iu-CS

DN70481497

Issue 02Approval Date 2009-12-02

2 DN70481497Issue 02

Activating RAN750 and RAN75: IP based Iu-PS and IPbased Iu-CS

Id:0900d80580647a40

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation 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 documentation 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 documentation 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 and finally 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 this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY 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 documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

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

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN70481497Issue 02

3


Id:0900d80580647a40

Table of ContentsThis document has 21 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Activating IP based Iu-PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Verifying IP based Iu-PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Deactivating IP based Iu-PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Activating IP based Iu-CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5 Verifying IP based Iu-CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 Deactivating IP based Iu-CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 DN70481497Issue 02


Id:0900d80580647a40

List of FiguresFigure 1 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 2 IP-based Iu-PS connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 3 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4 IP-based Iu-CS connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

DN70481497Issue 02

5


Summary of changes

Id:0900d8058063e548

Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Please note that our issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.

Changes between issues 02 and 1-2Instructions have been updated in both Activating IP based Iu-PS and Activating IP based Iu-CS.

Changes between issues 1-2 and 1-1Activating IP based Iu-PS and Activating IP based Iu-CS

• Steps for VLAN configuration in the RNC added • Instructions in Activating IP based Iu-CS updated

Changes between issues 1-1 and 1-0Activating IP based Iu-PS and Activating IP based Iu-CS

• IP address examples and MML commands have been updated and modified in figures and configuration instructions

• The structure of steps has been modified

6 DN70481497Issue 02


Id:0900d8058063e548

Summary of changes

DN70481497Issue 02

7


Activating IP based Iu-PS

Id:0900d8058063e0c3

1 Activating IP based Iu-PSPurposeFollow the procedure below to activate feature RAN750: IP based Iu-PS.

For more information on the feature, see RAN750: IP based Iu-PS in WCDMA RAN, rel. RU10, feature descriptions.

The configuration examples in the activation instructions use the IP addressing pre-sented in figures Network configuration and IP-based Iu-PS connectivity.

Figure 1 Network configuration

Figure 2 IP-based Iu-PS connectivity

Before you startNPGE(P) HW unit is required to enable the IP-based Iu-PS.

This is an optional feature which is under a separate license control and belongs to the application software. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the RNC. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previ-ously set state remains as the default.

For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN.

8 DN70481497Issue 02


Id:0900d8058063e0c3


Use the ZW7M; command to activate the license for the feature with feature code 1070.

Feature-specific parameters have to be defined for each IP-based Iu interface. The dif-ferentiated services code point (DSCP) mapping for the user plane connections is con-figured with the IPQM object attributes. The corresponding DSCP to PHB mapping is configured and needs to be aligned at the IP layer resources configuration. Each used DSCP needs to have the corresponding DSCP to PHB mapping for the IP egress sched-uling.

The following parameters are related to this feature.

IPQM parameters:

• IPQMId • ConversationalTCToDSCP • StreamingTCToDSCP • InteractiveTHP1TCToDSCP • InteractiveTHP2TCToDSCP • InteractiveTHP3TCToDSCP • BackgroundTCToDSCP

IUPS parameters:

• IPQMIdPS • IPBasedRouteIdPS • DestIPAddrListPS • DestIPPrefixPS • DestIPAddressPS • IPNetmaskPS

RNC parameters:

• EchoRequestSending • IPStackErrorTimer • N3Requests • T3Response

g The EchoRequestSending, N3Requests, and T3Response corresponding alarm is 3472 IU-PS IP ROUTING ERROR. It is raised when GTP level Echo Request has been enabled and sent, but Echo Response has not been received.

Steps

1 Configure the basic IP layer resources for the control plane.

g Before starting with a new IP layer configuration, check and review the existing IP layer configuration with the ZQRI MML commands.

g For the Iu interface control plane configuration it is recommend to use two different NPGEs and SCTP multi-homing. In these configuration examples the multihoming is not enabled. For further information on SCTP and signaling configuration on IP, see Configuring Signalling Transport over IP over ATM for Control Plane in Config-uring IP Connection for RNC.

a) Enable the IP forwarding of NPGE(P):ZQRT:NPGE,0:IPF=YES;

DN70481497Issue 02

9



Id:0900d8058063e0c3

If VLAN is used:

b) Enable the IFGE0 Ethernet interface:ZQRN:NPGEP,0:IFGE0:::::UP;

c) Create a VLAN interface for the NPGE-0 unit. The VLAN name is VL1, VLAN ID is 2 (VLAN ID can have value between 2 to 4094), and the VLAN is attached to the physical interface IFGE0.ZQRM:NPGE,0:VL1:2:IFGE0;

d) Configure the IP address of the VLAN interface.ZQRN:NPGE,0:VL1:(a).(b).(c).(d),P:X:;where (a), (b), (c), and (d) have to be replaced with the corresponding values from-network planning.g Pay attention to the IP address planning with the VLAN configuration at system

level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option.

If VLAN is not used:

e) Configure the IP address for the NPGE GE interface:ZQRN:NPGE,0:IFGE0:10.4.1.193,:29:;

Proceed with the configuration for both cases:

f) Create a static route to the gateway for the NPGE for PS Core:ZQKC:NPGE,0:10.25.114.128,25:10.4.1.194:PHY;

g) Configure DSCP to PHB mapping profile for the Ethernet interface (IFGE0).Refer to the ZQ8B; command in the MML manual.This is optional; a default value can also be used.

h) Configure PHB queue profile.Refer to the ZQ8V; command in the MML manual.

i) Assign a DSPM profile to an IP interface in NPGE by the given profile IDs:ZQ8S:NPGE,0:IFGE0:ENA:ID1=1:ID2=1; or use the default profile:ZQ8S:NPGE,0:IFGE0:ENA::;

j) Check the internal IPoA to ICSU:ZQMQ:ICSU,0::NPGE,0:::ALL;

k) Reuse the internal IPoA from the Iub.While reusing the internal IPoA, there is no need for additional MML commands. An alternative solution is to create new IPoA with ZQMC MML command and assign IPs manually to the NPGE and ICSU for the IPoA with the ZQRN; MML command.ZQMC:ICSU,0,L:AA0:NPGE,0,P:IFAI0::;or in case of using NPGEP unit:ZQMC:ICSU,0,L:AA0:NPGEP,0,L:IFAI0::;Proceed with the configuration for both cases:ZQRN:NPGE,0:IFAI0,U:10.4.1.193,:32;ZQRN:ICSU,0:AA0,U:10.1.1.193,:32:10.4.1.193:;

l) Configure the IPoA interface on ICSU and LO0 IP.In this example the internal IPoA interface AA511 was created in the system auto-matically.ZQRN:ICSU,0:LO0:10.1.1.193,L:; ZQRN:ICSU,0:AA511,:10.1.1.193,:32:10.4.1.193:;

m) Create a static route for ICSU, NPGE as gateway:ZQKC:ICSU,0::10.4.1.193:LOG;

10 DN70481497Issue 02


Id:0900d8058063e0c3


n) Verify connectivity between ICSU and SGSN:ZQRX:ICSU,0:IP=10.25.114.169;

2 Configure the IP-based user plane for the Iu-PS.

a) Configure the IP address for the NPGE(P) GE interface if needed for Iu-PS. The configuration in Step 1 can be applied.

b) Configure DSCP to PHB mapping profile and PHB queue profile if not yet assigned.Refer to the ZQ8B; and ZQ8V; command in the MML manual.

c) Assign the DSPM profile to an IP interface in NPGE by the given profile IDs if not yet assigned:ZQ8S:NPGE,0:IFGE1:ENA:ID1=1:ID2=1; or use the default profile:ZQ8S:NPGE,0:IFGE1:ENA::; g If the IP based route committed bit rate is zero, no connection admis-

sion control (CAC) is performed in this IP-based route. Only IP-based routes for which no CAC is done can be used for load sharing.

d) Configure the IP-based route to the NPGE:ZQRU:ADD:3,"IUPSUP":; ZQRC:NPGE,0:IFGE0:IPV4=10.4.1.193:ID=3;

e) Create a static route:ZQKC:NPGE,0:10.25.114.145,25:10.4.1.194:PHY;

f) Verify connectivity between NPGE and SGSN:ZQRX:NPGE,0:IP=10.25.114.145;

3 Configure the IP-based control plane for the Iu-PS.

a) MML configuration:1. Create the SCTP association set:

ZOYC:IUPS:C::;,2. Add assocations into assocation set:

ZOYA:IUPS:ICSU,0:SS7:;

3. Configure the local and remote IP addresses of the assocation:ZOYP:M3UA:IUPS,0:"10.1.1.193",:"10.25.114.169",29,;,

4. (Optional) Modify the association state:ZOYS:M3UA:IUPS,0:ACT;,g This step is needed only when you want to activate the SCTP association

without affecting M3UA level signaling interactions.5. Create the IP-based signaling link set:

ZNSP:NA0,2031,SGSNV:2:IUPS:;

6. Create the signaling route set:ZNRC:NA0,2031,SGSNV,0,,N:,,,7:;

7. Allow the activation of signaling link:ZNLA:2:;

8. Allow the activation of signaling route:ZNVA:NA0,2031:;

9. Change the signaling link state:ZNLC:2,ACT:;

DN70481497Issue 02

11



Id:0900d8058063e0c3

10. Change the signaling route state:ZNVC:NA0,2031::ACT:;

11. Define the SCCP subsystem RANAP for the remote end:ZNFD:NA0,2031,0:8E,RANAP,0,Y:;

12. Set the broadcast status of the SCCP signaling point:ZOBC:NA0,2031,8E::Y;

13. Change the SCCP state:ZNGC:NA0,2031:ACT:;

14. Change the subsystem state:ZNHC:NA0,2031:8E:ACT:;

b) OMS configuration:1. Create the destination SPC in Iu-PS.g At this stage RANAP reset should be sent by the RNC and be replied correctly

by the Core.

4 Configure the Radio Network layer information.

a) Start the RNC OMS application RNW Object Browser, or alternatively use the RNW interface.

b) Create the IPQM object for the DiffServ DSCP selection if needed. Already existing IPQM can also be used. • You can use the default DSCP values within the IPQM. The already created

IPQM object can be used as well if the same DSCP mapping applies. • By default only one IPQM is needed for all the IP Iu interfaces.

c) IP configuration for the IUPS object: • The IPQMId has to refer to the IPQM object created in step b. • IP-Based Route reference for the Iu-PS user plane transport bearer setup is

retrieved based on the peer IP address signalled at RANAP RAB assignment. IP-based route identification has to refer to the already created IP-Based Route entity in the RNC.

• In case one IP-based route entity is used for the Iu-PS user plane setups, the following entry can be used: 0.0.0.0/0 -> IP-based route id 3. In this case only one entry is defined at IUPS - DestIPAddrListPS.

• In case a detailed destination IP address based references are used, the entry 10.25.114.145/28 -> IP-based route id 3 (netmask /28, 255.255.255.240) can be configured. IUPS object may contain several destination IP address and netmask-based references to different IP-based route entities if required from the transport network configuration point of view.

Expected outcomeThe feature RAN750: IP based Iu-PS has been activated.

12 DN70481497Issue 02


Id:0900d8058065ee8b

Verifying IP based Iu-PS

2 Verifying IP based Iu-PSPurposeFollow the procedure below to verify that the activation of RAN750: IP based Iu-PS feature has been successful.

Steps

1 Check that the following alarms do not show up:

• 3313 IU INTERFACE SIGNALLING FAILURE indicates that a single Iu link is down.

• 3314 CORE NETWORK SERVICE INTERRUPTION indicates that all Iu links are down.

2 Register and authenticate the user equipment (UE) into the network.

3 Perform the FTP download to the UE.

Expected outcomeThe RAN750: IP based Iu-PS feature interface functionality has been verified after the data is successfully received by the UE through the PS domain.

DN70481497Issue 02

13


Deactivating IP based Iu-PS

Id:0900d8058067241d

3 Deactivating IP based Iu-PSThe RAN750: IP based Iu-PS feature is not separately deactivated. The Iu-PS interface user plane and control plane can be configured either by using the ATM or IP/Ethernet transport option.

14 DN70481497Issue 02


Id:0900d8058063e0e4

Activating IP based Iu-CS

4 Activating IP based Iu-CSPurposeFollow the procedure below to activate feature RAN75: IP based Iu-CS.

For more information on the feature, see RAN75: IP based Iu-CS in WCDMA RAN, rel. RU10, feature descriptions.

The configuration examples in the activation instructions use the IP addressing pre-sented in the figures Network configuration and IP-based Iu-CS connectivity.

Figure 3 Network configuration

Figure 4 IP-based Iu-CS connectivity

Before you startCS Core (MGW and MSS) must be configured. For the MSS and MGW configuration refer to the corresponding customer documentation.

NPGE(P) HW unit is required to enable the IP-based Iu-CS.

g If the Support for Tandem/Transcoder Free Operation and AMR Codec Set features have been enabled on CS Core side, then those need to be enabled on the RNC side as well before the RAN75: IP based Iu-CS can be activated.

DN70481497Issue 02

15



Id:0900d8058063e0e4

This is an optional feature which is under a separate license control and belongs to application software. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the RNC. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previ-ously set state remains as the default.

For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN.

Use the ZW7 command to activate the license for the feature with feature code 1069.

Feature-specific parameters have to be defined for each IP-based Iu interface. The dif-ferentiated services code point (DSCP) mapping for the user plane connections is con-figured with the IPQM object attributes. The corresponding DSCP to PHB mapping is configured and needs to be aligned at the IP layer resources configuration. Each used DSCP needs to have the corresponding DSCP to PHB mapping for the IP egress sched-uling.

g The IP addresses and subnets must be set according to the actual network plan, the ones used in the document are only examples.

The following parameters are related to this feature.

IPQM parameters:

• IPQMId • ConversationalTCToDSCP • StreamingTCToDSCP • InteractiveTHP1TCToDSCP • InteractiveTHP2TCToDSCP • InteractiveTHP3TCToDSCP • BackgroundTCToDSCP

IUCS parameters:

• IPQMIdCS • IPBasedRouteIdCS • DestIPAddrListCS • DestIPPrefixCS • DestIPAddressCS • IPNetmaskCS • MinUDPPortCS • RtcpActivation • Iu Interface Identifier • Core Network Identity • Mobile Country Code • Mobile Network Code • Network Indicator • Signalling Point Code • Release version of Core Network

16 DN70481497Issue 02


Id:0900d8058063e0e4


Steps

1 Configure the basic IP layer resources for the control plane.

g Before starting with a new IP layer configuration, check and review the existing IP layer configuration with the ZQRI MML commands.

g For the Iu interface control plane configuration, it is recommended to use two differ-ent NPGEs for the SCTP multi-homing. In these configuration examples the multi-homing is not enabled. For further information on SCTP and signaling configuration on IP, see Configuring Signalling Transport over IP over ATM for Control Plane in Configuring IP Connection for RNC.

a) Enable the IP forwarding of NPGE(P):ZQRT:NPGE,0:IPF=YES;

If VLAN is used:

b) Enable the IFGE0 Ethernet interface:ZQRN:NPGEP,0:IFGE0:::::UP;

c) Create a VLAN interface for the NPGE-0 unit. The VLAN name is VL1, VLAN ID is 2 (VLAN ID can have value between 2 to 4094), and the VLAN is attached to the physical interface IFGE0.ZQRM:NPGE,0:VL1:2:IFGE0;

d) Configure the IP address of the VLAN interface.ZQRN:NPGE,0:VL1:(a).(b).(c).(d),P:X:;where (a), (b), (c), and (d) have to be replaced with the corresponding values from network planning.g Pay attention to the IP address planning with the VLAN configuration at system

level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option.

If VLAN is not used:

e) Configure the IP address for the NPGE(P) GE interface:ZQRN:NPGE,0:IFGE0:10.25.125.1,P:30:;

Proceed with the configuration for both cases:

f) Create a static route to the gateway for the NPGE for CS Core:ZQKC:NPGE,0:10.25.114.64,29:10.25.125.2:PHY;

g) Configure DSCP to PHB mapping profile for the Ethernet interface (IFGE0).Refer to the ZQ8B command in the MML manual.This is optional; a default value can also be used.

h) Configure PHB queue profile.Refer to the ZQ8V; command in the MML manual.

i) Assign a DSPM profile to an IP interface in NPGE by the given profile IDs:ZQ8S:NPGE,0:IFGE0:ENA:ID1=1:ID2=1; or use the default profile:ZQ8S:NPGE,0:IFGE0:ENA::;

j) Check the internal IPoA to ICSU:ZQMQ:ICSU,0::NPGE,0:::ALL;

k) Configure the local subnet for internal IPoA.ZQMN:1:10.25.123.0,26:;

DN70481497Issue 02

17



Id:0900d8058063e0e4

l) Verify (interrogate) the local subnet.ZQML:1;

m) Reuse the internal IPoA from Iub. An alternative solution is to create a new IPoA with the ZMQC MML command and assign IPs manually to the NPGE and ICSU for the IPoA with the ZQRN MML command:ZQMC:NPGE,0,L:IFAI2:ICSU,0,L:AA2::;ZQRN:NPGE,0:IFAI2,U:10.25.125.1,P:32:10.25.114.65:::;ZQRN:ICSU,0:AA2,N:10.25.114.65,L:32:10.25.125.1:1500;

n) Configure the IPoA interface on ICSU and LO0 IP.In this example the internal IPoA interface AA511 was created to system automati-cally.ZQRN:ICSU,0:LO0:10.25.114.65,L:; ZQRN:ICSU,0:AA511,:10.25.114.65,:32:10.25.125.1:;

o) Create a static route for ICSU, NPGE as gateway:ZQKC:ICSU,0::10.25.125.1:LOG;

2 Configure the IP-based user plane for Iu-CS.

a) Configure the IP address for the NPGE(P) GE interface if needed for Iu-CS. The configuration from Step 1 can be applied.

b) Configure DSCP to PHB mapping profile and PHB queue profile if not yet assigned.Refer to the ZQ8B; and ZQ8V; command in the MML manual.

c) Assign the DSPM profile to an IP interface in NPGE by the given profile IDs if not yet assigned:ZQ8S:NPGE,0:IFGE1:ENA:ID1=1:ID2=1; or use the default profile:ZQ8S:NPGE,0:IFGE1:ENA::; g If the IP based route committed bit rate is zero, this means that no

Connection Admission Control (CAC) is performed in this IP-based route. Only IP-based routes for which no CAC is done can be used for load sharing.

d) Configure the IP-based route to the NPGE:ZQRU:ADD:2,"IUCSUP":; ZQRC:NPGE,0:IFGE0:IPV4=10.25.125.1:ID=2;

e) Configure a static route toward the MGW UP subnet:ZQKC:NPGE,0:10.25.114.72,29:10.25.125.2:PHY;

f) Configure a static route toward the MGW TPG subnet:ZQKC:NPGE,0:10.25.(a).(b),(c): 10.25.125.2:LOG;where (a), (b), and (c) have to be replaced with the corresponding values from network planning.

3 Configure the IP-based control plane for Iu-CS.

a) MML configuration:1. Create the SCTP association set:

ZOYC:IUCS:C::;,2. Add assocations into assocation set:

ZOYA:IUCS:ICSU,0:SS7:;

3. Configure the local and remote IP addresses of the assocation:ZOYP:M3UA:IUCS,0:"10.25.124.1",,:"10.25.114.65",29::;

18 DN70481497Issue 02


Id:0900d8058063e0e4


4. Modify the association state:ZOYM:IUCS:REG=N:;ZOYS:M3UA:IUCS,0:ACT;,

5. Define RNC own signalling point data:ZNRP:NA0,RNC-SPC,RNC-SPCNAME,:::;

6. Create the IP-based signaling link set:ZNSP:NA0,990,MGWTM:1:IUCS:;

7. Create the signaling route set:ZNRC:NA0,990,MGWTM,0,,N:,,,7:;

8. Allow the activation of the signaling link:ZNLA:1:;

9. Allow the activation of the signaling route:ZNVA:NA0,990:;

10. Change the signaling link state:ZNLC:1,ACT:;

11. Change the signaling route state:ZNVC:NA0,990::ACT:;

12. Create the signaling route set to the MSS:ZNRC:NA0,391,MC1NI,6,,:NA0,990,MGWTM,7:;

13. Allow the activation of the signaling route:ZNVA:NA0,391:NA0,990:;

14. Define SCCP service:ZNPC:NA0,03,SCCP:Y:Y,::;

15. Define SCCP for RNC own signalling point:ZNFD:NA0,RNC-SPC,0:8E,RANAP,0,N:;

16. Define SCCP for MGW signalling point:ZNFD:NA1,MGW-SPC,0:;

17. Change the signaling route state to the MSS:ZNVC:NA0,391:NA0,990:ACT:;

18. Define the SCCP subsystem RANAP for the remote end:ZNFD:NA0,391,0:8E,RANAP,0,Y:;

19. Set the broadcast status of the SCCP signaling point:ZOBC:NA0,391::Y;

20. Set the local broadcast status of the SCCP signaling point:ZOBM:NA0,391::Y;

21. Change the SCCP state:ZNGC:NA0,391:ACT:;

22. Change the subsystem states:ZNGC:NA0,MGW-SPC:ACT:;ZNHC:NA1,RNC-SPC:8E:ACT:;ZNHC:NA0,391:8E:ACT:;

b) OMS configuration:1. Create the destination SPC in Iu-CS.

4 Configure the Radio Network layer information.

a) Start the RNC OMS application RNW Object Browser, or alternatively use the RNW interface.

b) Create the IPQM object for the DiffServ DSCP selection if needed:

DN70481497Issue 02

19



Id:0900d8058063e0e4

• You can use the default DSCP values within the IPQM. • Only one IPQM is needed for all the IP Iu interfaces by default and the already

created IPQM object can be used as well if the same DSCP mapping applies. • The default values apply for the minimum default port.

c) IP configuration for the IUCS object: • Activate the RTCP, the default values apply.

g Check if the RTCP activation status is consistent with the MGW configura-tion.

• IP-Based Route identification has to refer to the already created IP-Based Route entity in the RNC. In this example the id 2 is used in Step 2 d.

• The destination IP address list for Iu-CS must contain the MGW user plane IP subnet. The system validates at RAB assignment that the IP address signalled to the RNC belongs to the configured IP subnets in the related IUCS object.

• add mobile country code, mobile network code, network indicator, and signaling point code.

Expected outcomeThe feature RAN75: IP based Iu-CS feature has been activated.

20 DN70481497Issue 02


Id:0900d8058065ee89

Verifying IP based Iu-CS

5 Verifying IP based Iu-CSPurposeFollow the procedure below to verify that the activation of RAN75: IP based Iu-CS feature has been successful.

Steps

1 Check that the following alarms do not show up:

• 3313 IU INTERFACE SIGNALLING FAILURE indicates that a single Iu link is down.

• 3314 CORE NETWORK SERVICE INTERRUPTION indicates that all Iu links are down.

2 Register and authenticate the user equipment (UE) into the network.

3 Perform an AMR call from the UE.

Expected outcomeThe RAN75: IP based Iu-CS feature interface functionality has been verified with per-forming a normal voice call.

DN70481497Issue 02

21


Deactivating IP based Iu-CS

Id:0900d8058067241b

6 Deactivating IP based Iu-CSThe RAN75: IP based Iu-CS feature is not deactivated separately. The Iu-CS interface user plane and control plane can be configured either by using the ATM or IP/Ethernet transport option.

03 02 RN33253EN20GLA0 Activate IP Based Iu Iur Interfaces

Documents

Transcript of 03 02 RN33253EN20GLA0 Activate IP Based Iu Iur Interfaces