Configuration Example of a UNI-UNI CES (VC12 Level) Service
This topic describes the configuration example of a UNI-UNI CES service.
Example Description
This topic describes the application scenario of UNI-UNI CES services, including the networking diagram and service planning.
- NE1 is OSN 9800 U32 Standard.
- The EC116 board is used between NodeBs and the RNC to receive and transmit VC12 CES services.
Service Planning
To transmit a CES service between NodeB and RNC, you need to create two CES services.
The UNI-UNI is used to access the local service, and then the UNI-UNI transmits the accessed service to RNC. A CES service is present between each NodeB and RNC. Two E1 timeslots of the CES service are fully used.
Table 4-20 lists the configuration parameters of NE1.
Attribute |
Value |
Value |
|
---|---|---|---|
NE |
NE1 |
NE1 |
|
Service ID |
1 |
2 |
|
Mode |
UNI-UNI |
UNI-UNI |
|
PW mode |
CESoPSN |
CESoPSN |
|
Service Name |
CES1 |
CES2 |
|
CES service type |
Common service |
Common service |
|
AC configuration list 1 |
Port |
Serial0/12/0/13:1:1:1 |
Serial0/12/0/14:1:1:1 |
AC configuration list 2 |
Port |
Serial0/12/0/15:1:1:1 |
Serial0/12/0/16:1:1:1 |
Configuring CES Services on a Per-NE Basis
This topic describes how to configure the two CES services in the example on a per-NE basis.
Prerequisites
You must be an NM user with "NE operator" authority or higher.
You must understand the networking, requirements and service planning of the example.
A network must be created.
Procedure
- Configure CES service interfaces, including the NodeB-side interface and RNC-side interface.
- Create local CES service 1.
- Create user-side-to-user-side CES2. For details, see 2.a to 2.d.
Item
Value
Service ID
2
Service type
UNI-UNI
PW type
CESoPSN
Service name
Local CES service 2
Service Type of CES
p2p
AC configuration list 1
Port
Serial0/12/0/14:1:1:1
AC configuration list 2
Port
Serial0/12/0/16:1:1:1