Flexi BSC 培训材料 - 图文

You can add up to four signalling links to the signalling link set. Repeat the last three parameters for each signalling link.

o

Create the signalling link set for the Ater interface transparently via the MGW to the MSC server.

ZNSC:,,:,;

The parameters signalling network and signalling point code define the network element where the signalling link set leads to.

4. Add links to the signalling link set (NSA).

This step is needed only if all the links were not added to the link set in the previous step.

ZNSA:,,:,;

5. Create the signalling route set (NRC).

To implement this step, choose one of the following alternatives:

o

Create the signalling route set for the control plane directly to the MSS.

ZNRC:,,

name>,,,:,,,0;

Parameter Explanation parameter set number Value 1 is recommended. load sharing status restriction status D is recommended. R is recommended. o

Create the signalling route set for the Ater interface transparently via the MGW to the MSC server.

Direct connections:

ZNRC:,,

name>,,,:,,,0;

STP configurations:

ZNRC:,,

name>,,,:,,0;

Parameter parameter set number Explanation Value 0 is recommended in STP configurations, value 1 for direct connections load sharing status D is recommended. restriction status N is recommended in STP configurations, R for direct connections. 6. Allow activation of the signalling links (NLA). ZNLA:;

7. Allow activation of the signalling route (NVA).

To implement this step, choose one of the following alternatives:

o

Allow activation of the signalling route for the control plane directly to the MSS.

ZNVA:,:;

o

Allow activation of the signalling route for the Ater interface transparently via the MGW to the MSC server.

ZNVA:,:,;

8. Change signalling link states (NLC).

ZNLC:,ACT:;

9. Change route set state (NVC).

To implement this step, choose one of the following alternatives:

o

Change route set state for the control plane directly to the MSS.

ZNVC:,::ACT;

o

Change route set state for the Ater interface transparently via the MGW to the MSC server.

ZNVC:,:

network>,:ACT;

Creating the SCCP

1.

Create service (NPC).

ZNPC:,03,SCCP:Y:Y,208,10F;

2. Define SCCP for the BSC's own signalling point (NFD). ZNFD:,

code>,:,,,;

Parameter Explanation signalling point parameter set number ETSI: value 1 is recommended. ANSI: no recommended value. subsystem number subsystem name subsystem parameter set number ETSI: FE, ANSI: DE. ETSI: BSSAP, ANSI: RSAP. ETSI: value 1 is recommended. ANSI: no recommended value. 3. Define SCCP for the MSC's or MSS's signalling point (NFD).

ZNFD:,,:,,;

See the previous step for recommended parameter values.

4.

Modify broadcast status of SCCP signalling points (OBM). ZOBM:,,::Y;

Parameter Explanation subsystem number ETSI: FE, ANSI: DE. subsystem name ETSI: BSSAP, ANSI: RSAP. 5. Modify the local broadcast status of SCCP subsystems (OBC). ZOBC:,,::Y;

Parameter Explanation subsystem number ETSI: FE, ANSI: DE. subsystem name ETSI: BSSAP, ANSI: RSAP. 6. Change the SCCP state at BSC side (NGC).

ZNGC:,:ACT;

7. Change the SCCP state at MSC side (NGC).

ZNGC:,:ACT;

8. Change subsystem state at BSC side (NHC).

ZNHC:,::ACT;

The value of the parameter subsystem is BSSAP in ETSI and RSAP in ANSI.