Got it

eLTE

Created: Jun 4, 2020 15:37:06Latest reply: Jun 5, 2020 01:22:13 507 2 0 0 0
  Rewarded HiCoins: 0 (problem resolved)
Dears;
Is there someone who can help me on basic of eLTE configuration on eCNS210 device

Featured Answers

Recommended answer

BetterMing
Created Jun 5, 2020 01:22:13

Hello, tesfama.

If you want to understand the basic configuration of eCNS210, then you need to first understand the product functions and positioning of eCNS210.


Product Functions

eCNS210 is a device of the core network in the LTE Trunk Radio System.

Deployed in a centralized manner, eCNS210 in the LTE Trunk Radio System provides subscription data management, authentication management, mobility management, session management, bearer management, and digital trunking services. eCNS210 works with an eAPP to enable the dispatching function of trunking systems.

Figure 1 shows how an eCNS210 networks with other devices.

Figure 1 eCNS210 networking diagram
tm-ecns210.png

The networking situations between the eCNS210 and neighboring NEs are as follows:

  • eCNS210 exchanges signaling and data with the DBS3900 through the public S1 interface.

  • eCNS210 exchanges signaling and data with the eAPP through the user-defined Tx, Rx and SGi interfaces.

  • eCNS210 exchanges data with the application server/external data network through the user-defined SGi interface.

  • eCNS210 exchanges offline CDR data with the CG through the public Ga interface.

  • eCNS210 communicates with other eCNS210s through the user-defined TR, to implement data backup, service signaling exchange, and heartbeat detection in the remote disaster recovery scenario; through the public S5/S8 interface and user-defined interface S6a, to support data and signaling exchanges in the roaming scenario. PTT service scenario partially supports S10 interface and does not support S5/S8 interface.

  • eCNS210 is managed by eOMC910 or eLMT through the user-defined operation and maintenance interface.

  • eCNS210 communicates with eUDC through the public S13 interface, to realize the management of user equipment.eCNS210 also communicates with eUDC through data configuration interface, to realize PS user subscription and data modification.


Physical Structure

An eCNS210 comprises a subrack and boards.

Subrack

The eCNS210 uses an ATCA-based T8290 subrack, including two fan boxes, two PEMs, and two SDMs.

Figure 1 shows the front view of the T8290 subrack.

Figure 1 Front view of the T8290 subrack
ts-t8290-front.png

1 Fan box

2 Slot number

3 Board

4 Air intake vent

SMU slot

NOTE:

Two SMU slots are provided at the bottom of the subrack. The SMU slot close to the ESD jack corresponds to slot 15 defined in the software layer and that far from the ESD jack corresponds to slot 14 defined in the software layer.

ESD jack

Figure 2 shows the rear view of the T8290 subrack.

Figure 2 Rear view of the T8290 subrack
ts-t8290-back.png

1 Air outtake vent

2 Slot number

3 Interface board

PEM

SDM slot

ESD jack

7 Subrack ground point

-

-

Boards

Table 1 lists the boards used by the eCNS210.

Table 1 eCNS210 boards
Board NameQuantitySlot AllocationDescription
SWU

2

NOTE:

Two SWUs are needed for both redundant configuration and non-redundant configuration.

6 or 7It is a switch unit, providing layer 2 switching, equipment management, and configuration recovery functions.
SWI

2 (redundant configuration)

1 (non-redundant configuration)

6R or 7R

NOTE:
For non-redundant configuration, slot 6R is preferred.
It is the rear board of the SWU, providing the external interface function for the SWU.
OMU

2 (redundant configuration)

1 (non-redundant configuration)

0 or 2

NOTE:
For non-redundant configuration, slot 0 is preferred.
It is an O&M unit, providing the functions to configure, monitor, and maintain the subrack.
USI

2 (redundant configuration)

1 (non-redundant configuration)

0R or 2R

NOTE:
For non-redundant configuration, slot 0R is preferred.
It is the rear board of the OMU, providing the external interface function for the OMU.
ISU

2/4/6/8/10 (redundant configuration)

1/2/3/4/5 (non-redundant configuration)

  • 1/4/5/10/11 (non-redundant configuration)

  • 1/3/4/5/8/9/10/11/12/13 (redundant configuration)

NOTE:
For non-redundant configuration, slot 1 is preferred. For redundant configuration, slot 1 and 3 are preferred.
It is a service processing unit, providing the service processing function.
QXI

2/4/6/8/10 (redundant configuration)

1/2/3/4/5 (non-redundant configuration)

  • 1R/4R/5R/10R/11R (non-redundant configuration)

  • 1R/3R/4R/5R/8R/9R/10R/11R/12R/13R (redundant configuration)

NOTE:
For non-redundant configuration, slot 1R is preferred. For redundant configuration, slot 1R and 3R are preferred.
It is the rear board of the ISU, providing the external interface function for the ISU.
SMU

2 (redundant configuration)

1 (non-redundant configuration)

-It is a management module of a subrack that manages all hardware devices in the subrack and performs the functions including device management, event management, asset management, power management, remote maintenance, configuration recovery, and energy conservation.
icon-note.gif NOTE:
  • R in the Slot Allocation column refers to the rear board. For example, 1R indicates the slot 1 in Figure 2.

  • Slot 0 and 2, slot 1 and 3, slot 4 and 8, slot 5 and 9, slot 10 and 12, and slot 11 and 13 are redundant for each other. The former one is an active board and the later one is a standby board during the initial configuration, so as the rear boards.


Logical Structure

This section describes the logical structure of an eCNS210, which consists of an MME, a GW, an HSS, a PTT and an SPC subsystem.

Figure 1 shows the eCNS210 logical structure.

Figure 1 eCNS210 logical structure
td-ecns-logic.png

MME Subsystem

The MME subsystem incorporates network access control, mobility management, security, bearer management, and data flow routing. Specifically, it provides the following functions:

  • Mobility management, including the attachment, detachment, tracking area update, paging, service request, and handover processing.

  • Session management, including the default bearer setup, dedicated bearer setup, bearer update, bearer deletion, and associated processing for bearer modification.

  • Subscription data management, including processing of location updates and registration, location update and registration cancellation, subscription data insertion and deletion, authentication vector acquisition, and authentication failure reports.

  • User database management, including the addition, deletion, and modification of user contexts, session contexts, bearing/forwarding contexts, and connection contexts, table relationship maintenance, global database management, database backup, handover, data synchronization, data consistency check, and resource check.

  • S1AP signaling messaging encoding and decoding, S1AP connection management, S1AP message passing and conversion, S1AP connection and SCTP association maintenance and management.

  • SCTP association management and SCTP message receive and transmit function.

  • GTP-C signaling transport supports GTP-C-based encapsulation, reliable transmission, and path management.

  • Ethernet/IP/Route management.

  • Packet data forwarding, including external interface data receiving/transmitting, intra-system data receiving/transmitting, Ethernet processing, and IP-layer forwarding processing.

  • S10AP, including heartbeat detection, active/standby status management, and backup management.

  • DNS agent.

  • Diameter link management, protocol handling, and link receiving and transmission.

  • ENUM protocol handling.

  • Interacts with eUDC for authenticating trunk terminal equipment and IMEI check.

GW Subsystem

The GW subsystem typically implements session management and bearer management. Specifically, it provides the following functions:

  • User and group session management, which accepts event notifications from an access processing module, constructs session-level state machine instances, and dispatches internal message procedures for setups, upgrades, deletions, handovers, and tracking area updates of user and group sessions.

  • Policy management, which is responsible for service policy local acquisition, integration, maintenance, and decision making.

  • User IP allocation, including static address allocation and dynamic address allocation.

  • User-plane resource statistics and allocation, and session access control.

  • GTP-V2 signaling protocol analysis and GTP-V2 protocol entrance processing.

  • Multicast bearer management.

  • Route management with other subsystems.

  • Charging protocol processing and CDR management.

HSS Subsystem

The HSS subsystem typically implements PS user data storage and management. Specifically, it provides the following functions:

  • Data configuration and maintenance.

  • Subscription data storage.

  • Processing of updates in user subscription data, including authentication information and user subscription information.

  • Authentication algorithm support.

PTT Subsystem

The PTT subsystem typically processes basic services for PTT groups and point-to-point calls. Specifically, it provides the following functions:

  • PTT group service procedure processing.

  • Mobility management and session status processing for users within a Trunk Radio System.

  • Group-level data and user data of PIS storage and indexing.

  • SIP processing and SIP session adaptation.

SPC Subsystem

The SPC subsystem mainly implements service policy control. Specifically, it provides the following functions:

  • Service policy control.

  • Trunk Diameter routing management and link management.

Software Architecture

This section describes the software architecture of an eCNS210. The software uses a distributed architecture and each function module is deployed on the corresponding board, so it can be flexibly configured based on network applications.

eCNS210 software can be divided into host software and backend software based on distribution positions.

  • Host software is used to implement the functions such as signaling access and processing, service control, resource management. It cooperates with backend software to respond to the operation commands issued by maintenance engineers, to implement the functions such as data management, equipment management, alarm management, performance statistics, and signaling tracing.

  • Backend software cooperates with host software by providing eCNS210 with unified OM interface, such as unified MMI, for maintenance and management engineers to implement functions such as data management, equipment management, alarm management, performance statistics, signaling tracing, and CDR management on an NE.

Figure 1 shows the software architecture of the eCNS210.

Figure 1 Overall software architecture of an eCNS210
ts-cgp-soft.png

The software architecture of the eCNS210 is designed in a top-down and hierarchically modularized manner. It consists of the OS, middleware, and application software from the bottom up.

  • OS

    The eCNS210 software uses the Linux OS. The Linux version is 2.6.16.60-0.83.2.

  • Middleware

    The eCNS210 uses the middleware technology between the OS and application software so that the upper-layer service software is irrelevant to the OS (platform).

  • Application software

    Application software implements the functions of the eCNS210 software. Different types of boards are configured with different software to implement various functions.

For more operations, you can refer to the product documentation in the following link, which details the various configurations and operations of eCNS210.

https://support.huawei.com/hedex/hdx.do?docid=EDOC1100083111&lang=en

Thanks!

View more
  • x
  • convention:

All Answers

Hello,

eCNS210 Boards and Modules

This section describes the configuration principles of the eCNS210 and the descriptions of the corresponding boards and modules.

Table 1 lists the boards used in the eCNS210.

Table 1 Boards used in the eCNS210

Board Name

Function Description

SWU

It is a switch unit, providing Layer 2 switching, equipment management, and configuration recovery functions.

SWI

It is the rear board of the SWU, providing the external interface function for the SWU.

OMU

It is an O&M unit, providing the functions to configure, monitor, and maintain the subrack.

USI

It is the rear board of the OMU, providing the external interface function for the OMU.

ISU

It is a service processing unit, providing the service processing function.

QXI

It is the rear board of the ISU, providing the external interface function for the ISU.

SMU

It is a management module of a subrack that manages all hardware devices in the subrack and performs the functions including device management, event management, asset management, power management, remote maintenance, configuration recovery, and energy conservation.

SDM

The SMU board obtains the subrack data from the SDM to manage all system hardware devices.

Thanks

View more
  • x
  • convention:

Hello, tesfama.

If you want to understand the basic configuration of eCNS210, then you need to first understand the product functions and positioning of eCNS210.


Product Functions

eCNS210 is a device of the core network in the LTE Trunk Radio System.

Deployed in a centralized manner, eCNS210 in the LTE Trunk Radio System provides subscription data management, authentication management, mobility management, session management, bearer management, and digital trunking services. eCNS210 works with an eAPP to enable the dispatching function of trunking systems.

Figure 1 shows how an eCNS210 networks with other devices.

Figure 1 eCNS210 networking diagram
tm-ecns210.png

The networking situations between the eCNS210 and neighboring NEs are as follows:

  • eCNS210 exchanges signaling and data with the DBS3900 through the public S1 interface.

  • eCNS210 exchanges signaling and data with the eAPP through the user-defined Tx, Rx and SGi interfaces.

  • eCNS210 exchanges data with the application server/external data network through the user-defined SGi interface.

  • eCNS210 exchanges offline CDR data with the CG through the public Ga interface.

  • eCNS210 communicates with other eCNS210s through the user-defined TR, to implement data backup, service signaling exchange, and heartbeat detection in the remote disaster recovery scenario; through the public S5/S8 interface and user-defined interface S6a, to support data and signaling exchanges in the roaming scenario. PTT service scenario partially supports S10 interface and does not support S5/S8 interface.

  • eCNS210 is managed by eOMC910 or eLMT through the user-defined operation and maintenance interface.

  • eCNS210 communicates with eUDC through the public S13 interface, to realize the management of user equipment.eCNS210 also communicates with eUDC through data configuration interface, to realize PS user subscription and data modification.


Physical Structure

An eCNS210 comprises a subrack and boards.

Subrack

The eCNS210 uses an ATCA-based T8290 subrack, including two fan boxes, two PEMs, and two SDMs.

Figure 1 shows the front view of the T8290 subrack.

Figure 1 Front view of the T8290 subrack
ts-t8290-front.png

1 Fan box

2 Slot number

3 Board

4 Air intake vent

SMU slot

NOTE:

Two SMU slots are provided at the bottom of the subrack. The SMU slot close to the ESD jack corresponds to slot 15 defined in the software layer and that far from the ESD jack corresponds to slot 14 defined in the software layer.

ESD jack

Figure 2 shows the rear view of the T8290 subrack.

Figure 2 Rear view of the T8290 subrack
ts-t8290-back.png

1 Air outtake vent

2 Slot number

3 Interface board

PEM

SDM slot

ESD jack

7 Subrack ground point

-

-

Boards

Table 1 lists the boards used by the eCNS210.

Table 1 eCNS210 boards
Board NameQuantitySlot AllocationDescription
SWU

2

NOTE:

Two SWUs are needed for both redundant configuration and non-redundant configuration.

6 or 7It is a switch unit, providing layer 2 switching, equipment management, and configuration recovery functions.
SWI

2 (redundant configuration)

1 (non-redundant configuration)

6R or 7R

NOTE:
For non-redundant configuration, slot 6R is preferred.
It is the rear board of the SWU, providing the external interface function for the SWU.
OMU

2 (redundant configuration)

1 (non-redundant configuration)

0 or 2

NOTE:
For non-redundant configuration, slot 0 is preferred.
It is an O&M unit, providing the functions to configure, monitor, and maintain the subrack.
USI

2 (redundant configuration)

1 (non-redundant configuration)

0R or 2R

NOTE:
For non-redundant configuration, slot 0R is preferred.
It is the rear board of the OMU, providing the external interface function for the OMU.
ISU

2/4/6/8/10 (redundant configuration)

1/2/3/4/5 (non-redundant configuration)

  • 1/4/5/10/11 (non-redundant configuration)

  • 1/3/4/5/8/9/10/11/12/13 (redundant configuration)

NOTE:
For non-redundant configuration, slot 1 is preferred. For redundant configuration, slot 1 and 3 are preferred.
It is a service processing unit, providing the service processing function.
QXI

2/4/6/8/10 (redundant configuration)

1/2/3/4/5 (non-redundant configuration)

  • 1R/4R/5R/10R/11R (non-redundant configuration)

  • 1R/3R/4R/5R/8R/9R/10R/11R/12R/13R (redundant configuration)

NOTE:
For non-redundant configuration, slot 1R is preferred. For redundant configuration, slot 1R and 3R are preferred.
It is the rear board of the ISU, providing the external interface function for the ISU.
SMU

2 (redundant configuration)

1 (non-redundant configuration)

-It is a management module of a subrack that manages all hardware devices in the subrack and performs the functions including device management, event management, asset management, power management, remote maintenance, configuration recovery, and energy conservation.
icon-note.gif NOTE:
  • R in the Slot Allocation column refers to the rear board. For example, 1R indicates the slot 1 in Figure 2.

  • Slot 0 and 2, slot 1 and 3, slot 4 and 8, slot 5 and 9, slot 10 and 12, and slot 11 and 13 are redundant for each other. The former one is an active board and the later one is a standby board during the initial configuration, so as the rear boards.


Logical Structure

This section describes the logical structure of an eCNS210, which consists of an MME, a GW, an HSS, a PTT and an SPC subsystem.

Figure 1 shows the eCNS210 logical structure.

Figure 1 eCNS210 logical structure
td-ecns-logic.png

MME Subsystem

The MME subsystem incorporates network access control, mobility management, security, bearer management, and data flow routing. Specifically, it provides the following functions:

  • Mobility management, including the attachment, detachment, tracking area update, paging, service request, and handover processing.

  • Session management, including the default bearer setup, dedicated bearer setup, bearer update, bearer deletion, and associated processing for bearer modification.

  • Subscription data management, including processing of location updates and registration, location update and registration cancellation, subscription data insertion and deletion, authentication vector acquisition, and authentication failure reports.

  • User database management, including the addition, deletion, and modification of user contexts, session contexts, bearing/forwarding contexts, and connection contexts, table relationship maintenance, global database management, database backup, handover, data synchronization, data consistency check, and resource check.

  • S1AP signaling messaging encoding and decoding, S1AP connection management, S1AP message passing and conversion, S1AP connection and SCTP association maintenance and management.

  • SCTP association management and SCTP message receive and transmit function.

  • GTP-C signaling transport supports GTP-C-based encapsulation, reliable transmission, and path management.

  • Ethernet/IP/Route management.

  • Packet data forwarding, including external interface data receiving/transmitting, intra-system data receiving/transmitting, Ethernet processing, and IP-layer forwarding processing.

  • S10AP, including heartbeat detection, active/standby status management, and backup management.

  • DNS agent.

  • Diameter link management, protocol handling, and link receiving and transmission.

  • ENUM protocol handling.

  • Interacts with eUDC for authenticating trunk terminal equipment and IMEI check.

GW Subsystem

The GW subsystem typically implements session management and bearer management. Specifically, it provides the following functions:

  • User and group session management, which accepts event notifications from an access processing module, constructs session-level state machine instances, and dispatches internal message procedures for setups, upgrades, deletions, handovers, and tracking area updates of user and group sessions.

  • Policy management, which is responsible for service policy local acquisition, integration, maintenance, and decision making.

  • User IP allocation, including static address allocation and dynamic address allocation.

  • User-plane resource statistics and allocation, and session access control.

  • GTP-V2 signaling protocol analysis and GTP-V2 protocol entrance processing.

  • Multicast bearer management.

  • Route management with other subsystems.

  • Charging protocol processing and CDR management.

HSS Subsystem

The HSS subsystem typically implements PS user data storage and management. Specifically, it provides the following functions:

  • Data configuration and maintenance.

  • Subscription data storage.

  • Processing of updates in user subscription data, including authentication information and user subscription information.

  • Authentication algorithm support.

PTT Subsystem

The PTT subsystem typically processes basic services for PTT groups and point-to-point calls. Specifically, it provides the following functions:

  • PTT group service procedure processing.

  • Mobility management and session status processing for users within a Trunk Radio System.

  • Group-level data and user data of PIS storage and indexing.

  • SIP processing and SIP session adaptation.

SPC Subsystem

The SPC subsystem mainly implements service policy control. Specifically, it provides the following functions:

  • Service policy control.

  • Trunk Diameter routing management and link management.

Software Architecture

This section describes the software architecture of an eCNS210. The software uses a distributed architecture and each function module is deployed on the corresponding board, so it can be flexibly configured based on network applications.

eCNS210 software can be divided into host software and backend software based on distribution positions.

  • Host software is used to implement the functions such as signaling access and processing, service control, resource management. It cooperates with backend software to respond to the operation commands issued by maintenance engineers, to implement the functions such as data management, equipment management, alarm management, performance statistics, and signaling tracing.

  • Backend software cooperates with host software by providing eCNS210 with unified OM interface, such as unified MMI, for maintenance and management engineers to implement functions such as data management, equipment management, alarm management, performance statistics, signaling tracing, and CDR management on an NE.

Figure 1 shows the software architecture of the eCNS210.

Figure 1 Overall software architecture of an eCNS210
ts-cgp-soft.png

The software architecture of the eCNS210 is designed in a top-down and hierarchically modularized manner. It consists of the OS, middleware, and application software from the bottom up.

  • OS

    The eCNS210 software uses the Linux OS. The Linux version is 2.6.16.60-0.83.2.

  • Middleware

    The eCNS210 uses the middleware technology between the OS and application software so that the upper-layer service software is irrelevant to the OS (platform).

  • Application software

    Application software implements the functions of the eCNS210 software. Different types of boards are configured with different software to implement various functions.

For more operations, you can refer to the product documentation in the following link, which details the various configurations and operations of eCNS210.

https://support.huawei.com/hedex/hdx.do?docid=EDOC1100083111&lang=en

Thanks!

View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.