No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AMI Smart Meter Reading Solution V200R010C10 Planning and Design Guide

This document describes the overall and detailed design of functions and services in the AMI Smart Meter Reading Solution.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
EPMS Design

EPMS Design

Software and Hardware Configuration of the EPMS

The EPMS is the third-party application system of the AMI solution and provides electricity services. It supports server and VM deployment. The EPMS can be deployed in the single-node system or cluster mode when server or VM deployment is used. Depending on the number of terminals, the deployment scenarios, server configuration, and server quantity of the EPMS are different. You can select configurations according to the actual situation. The EPMS allows a maximum of 500,000 terminals. When there are over 20,000 terminals, use the standard AMI solution. To ensure service and data reliability, you are advised to use cluster deployment.

EPMS deployment includes deployments of the EPMS component and Portal. The EPMS component and Portal can be deployed on the same server or different servers, and can be deployed in the single-node system or cluster mode.

Software Configuration of the EPMS
Table 2-5 describes the software configuration of the EPMS.
Table 2-5  Software configuration of the EPMS

Parameter

Maximum Number of Managed Devices

Solution Selection

Recommended Configuration

Operating system

0 to 20,000 access devices

Small-sized AMI solution

Novell SuSE LINUX Enterprise Server 11.3

0 to 500,000 access devices

Standard AMI solution

Database

0 to 20,000 access devices

Small-sized AMI solution

  • Oracle database in the single-node system
  • Oracle RAC
  • Oracle HA

0 to 500,000 access devices

Standard AMI solution

  • Oracle database in the single-node system
  • Oracle RAC
  • Oracle HA

Browser

0 to 500,000 access devices

  • Small-sized AMI solution
  • Standard AMI solution

Chrome 26 or later

Hardware Configuration of the EPMS
Table 2-6 describes the hardware configuration of the EPMS.
Table 2-6  Hardware configuration of the EPMS

Maximum Number of Managed Devices

Solution Selection

Deployment Mode

Deployment Solution

Recommended Configuration

Description

0 to 20,000 access devices

Small-sized AMI solution

Server deployment

The Portal, EPMS component, and database in the single-node system can be deployed on the same device.

PC12C64G*1

The EPMS is deployed in the single-node system, and there is no need to deploy the load balancer.

The Portal, EPMS component, and database in the single-node system are deployed separately.

PC12C64G*3

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on the same server, and any two EPMS component servers can have the Portal cluster deployed.

PC12C32G*3

When cluster deployment is used, the EPMS cluster is deployed and load balancing needs to be configured. The EPMS supports software load balancing and F5 load balancer. A small number of smart meters are connected, so software load balancing is recommended to save costs. Software load balancing also uses the cluster deployment mode.

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on different servers.

PC12C32G*3

VM deployment

The Portal and EPMS component in the single-node system are deployed on the same device.

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

The EPMS single-node system is installed on the VM running Linux operating system, and load balancing does not need to be configured.

The Portal and EPMS component in the single-node system are deployed separately.

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on the same server, and any two EPMS component servers can have the Portal cluster deployed.

When cluster deployment is used, the EPMS single-node system is installed on the VM running Linux operating system and software load balancing in cluster mode is configured.

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on different servers.

20,000 to 100,000 access devices

Standard AMI solution

Server deployment

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on the same server, and any two EPMS component servers can have the Portal cluster deployed.

PC12C32G*3

When cluster deployment is used, the EPMS cluster is deployed and load balancing needs to be configured. The EPMS supports software load balancing and F5 load balancer. Software load balancing uses the cluster mode, whereas the F5 load balancer works in active/standby mode.

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on different servers.

PC12C32G*5

VM deployment

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on the same server, and any two EPMS component servers can have the Portal cluster deployed.

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

When cluster deployment is used, the EPMS single-node system is installed on the VM running Linux operating system and software load balancing in cluster mode is configured.

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on different servers.

100,000 to 500,000 access devices

Standard AMI solution

Server deployment

The Portal and EPMS component are deployed in cluster mode. The Portal cluster contains two Portal nodes, and the EPMS component cluster contains three nodes. The Portal cluster and EPMS component cluster are deployed on different servers.

PC12C32G*5

When cluster deployment is used, the EPMS cluster is deployed and load balancing needs to be configured. The EPMS supports software load balancing and F5 load balancer. Software load balancing uses the cluster mode, whereas the F5 load balancer works in active/standby mode.

VM deployment

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

When cluster deployment is used, the EPMS single-node system is installed on the VM running Linux operating system and software load balancing in cluster mode is configured.

Configuration of the EPMS Database

The EPMS supports the Oracle database. The Oracle database in the single-node system, Oracle RAC, or Oracle HA can be deployed. Different deployment modes have different requirements for the software and hardware of the database server. The requirements for the database depend on the number of connected devices. You can select configurations according to the actual situation.

Software Configuration of the Oracle Database
Table 2-7 describes the Oracle database software configuration of the EPMS.
Table 2-7  Software configuration of the Oracle database

Parameter

Maximum Number of Managed Devices

Solution Selection

Deployment Mode

Recommended Configuration

Operating system

0 to 20,000 access devices

Small-sized AMI solution

Server deployment

Novell SuSE LINUX Enterprise Server 11.3

VM deployment

  • Novell SuSE LINUX Enterprise Server 11.3
  • Windows Server 2008

0 to 500,000 access devices

Standard AMI solution

Server deployment

Novell SuSE LINUX Enterprise Server 11.3

VM deployment

  • Novell SuSE LINUX Enterprise Server 11.3
  • Windows Server 2008
Hardware Configuration of the Oracle Database
Table 2-8 describes the Oracle database hardware configuration of the EPMS.
Table 2-8  Hardware configuration of the Oracle database

Maximum Number of Managed Devices

Deployment Mode

Minimum Server Configuration

0 to 20,000 access devices

Oracle database in the single-node system

The Oracle database and application system are deployed on the same device.

  • Server configuration: PC12C64G*1
  • Database configuration: ORACLE_STD*12

The Oracle database and application system are deployed separately.

Oracle database in active/standby mode

  • Server configuration: PC12C64G*2
  • Database configuration: ORACLE_STD*12

Oracle RAC

Oracle HA

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

20,000 to 100,000 access devices

Oracle database in active/standby mode

  • Server configuration: PC12C64G*2
  • Database configuration: ORACLE_STD*12

Oracle RAC

Oracle HA

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G

100,000 to 500,000 access devices

Oracle database in active/standby mode

  • Server configuration: PC12C64G*2
  • Database configuration:
    • ORACLE_ENT_RAC*12
    • ORACLE_PARTITION*12

Oracle RAC

Oracle HA

  • VM configuration
    • Memory: 72 GB or more
    • Hard disk: 1200 GB or more
  • Physical server configuration
    • PC14C72G
Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 8679

Downloads: 15

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next