Creating routing objects and digit analysis for Iur interface in RNC

Purpose

This procedure describes how to create routing objects and digit analyses for the Iur interface with MML commands. The analysis tree used for configuring the Iur interface is set by using the RNC RNW object browser application.

Note

When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 49, add digits 4 and 9.

Before you start

Before you create routing objects, make sure that the appropriate

signalling (broadband MTP3) has been created and the associated VC link termination points (VCLtps) for the endpoints have been created.

Additionally, the route under which the endpoints are to be created must allow the type of the endpoints.

Steps

1. Create an AAL type 2 route (RRC)

ZRRC:ROU=<route number>,TYPE=AAL2:PRO=<protocol>:

NET=<signalling network>,SPC=<signalling point code>,ANI=<aal2 node identifier>;

The ANI is to be identical for all routes with the same SPC and the same signalling network.

2. Create an endpoint group (LIC)

ZLIC:<route number>,<ep group index>:<ingress service category>,<egress service category>;

The ingress and egress service categories should always be Constant Bit Rate (CBR).

3. Check that there is a free VCLtp (LCI) ZLCI:<interface id>,VC:<VPI>:FREE;

Out of these VCIs all these with the service category CBR in both directions can be used in the next step.

4. Create an endpoint (LJC)

ZLJC:<ep type>,<route number>,<connection id>:

<interface id>,<VPI>,<VCI>:<ownership>:[<loss ratio>,<mux delay>];

The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match.

Repeat steps 1-4 in the remote RNC before continuing with step 5.

Note

You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifiermust have the same value in both ends of a certain connection.

5. Unblock the AAL type 2 path (LSU)

The endpoints must have been created at both ends of the interface before the AAL type 2 path between them can be unblocked.

ZLSU:<ANI>:<AAL type 2 path identifier>:<execution time>;

Expected outcome

The execution printout followed by the unblocking should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state and the state has been agreed with the remote end.

Unexpected outcome

If the AAL type 2 path is still in blocked state, Then

repeat the unblocking command Unexpected outcome

If the remote end has not agreed to unblocking, Then

verify that the remote end is working properly and it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it.

6. Create digit analysis (RDC)

Create a digit analysis without charging for a specific digit sequence.

Add an AFI before the digit sequence in order to avoid conflicts with other number formats. The analysis tree has been set for the Iur interface by using the RNC RNW object browser.

ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<route number>;

Note

The address identifies the location of a network termination point. ATM End System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits long. The IDP specifies an administration authority which has the responsibility for allocating and assigning values of the DSP.

The first two digits of IDP are called Authority and Format Identifier (AFI). The AFI indicates the type of AESA that will follow. The last part of IDP is the actual IDP address. The leading zeroes of AESA numbers are used as padding digits to fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digit analysis. This is important because, when system analyses received digits a corresponding conversion is made. If digit analyses are created otherwise, the correct, matching analysis result cannot be found.

. E.164 AESA

E.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part may include leading zeroes and/or a trailing F. The rest of the number is DSP part.

. DCC AESA

DCC part of DCC AESA is 4 digit ISO country code after AFI (39). DCC part may include F(s). The rest of the number is DSP part.

. ICD AESA

ICD part of ICD AESA is 4 digits after AFI (47). ICD part may include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when handling analyses:

. E.164 ATM format (AFI = 0 x 45)

. Zeros between AFI and the following non-zero digit are removed.

. The 16th digit of E.164 part (F digit) is removed.

. Example: 45000000358951121F --> 45358951121

. DCC ATM format (AFI = 0 x 39)

. The fourth digit (F digit) is removed.

. Example: 39123F1234 --> 391231234

. ICD ATM format (0 x 47)

. Possible F digits are removed from the ICD part of the number (F digits are removed from digits 1-4).

. Example: 47123F1234 --> 471231234

Example Create routing objects and digit analysis for Iur interface 1. Create an AAL type 2 route between two RNCs. The route number is

13, the protocol is Message Transfer Part Level 3, the signalling network is NA0, the signalling point code is 35, and AAL type 2 node identifier is AAL2HEL1.

ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=35, ANI=AAL2HEL1;

2. Create an endpoint group under route 13. The endpoint group ID is automatically selected by the system. The termination points in this group have the Constant Bit Rate service category for both ingress and egress directions.

ZLIC:13:C,C;

3. Check that there is a free VCLtp.

ZLCI:5,VC:<VPI>:FREE;

Note that you can check all the VPIs available. Out of these VCIs all those with service category CBR in both directions can be used in the next step.

4. Create an endpoint of VC level (VCCep) under the route 13 created in the first step. AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI 1045. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10^–3and the AAL type 2 multiplexing delay is 10 ms.

ZLJC:VC,13,11:5,12,1045:LOCAL:3,100;

The system will automatically sort this endpoint into the endpoint group of step 2 since their service categories match.

Note

You must create a corresponding routing structure (steps 1-4) in the remote (PEER) network element before you can proceed to step 5. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifiermust have the same value in both ends of a certain connection.

5. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed waiting time for the execution of the blocking command is 18 seconds.

ZLSU:AAL2HEL1:11:18;

6. Create digit analysis without charging for a digit sequence 491234 in analysis tree 24.

ZRDC:DIG=491234,TREE=24:ROU=13;