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).
Design Principles

Design Principles

The AMI solution falls into the Automatic Meter Reading (AMR) solution, small-sized AMI solution, and standard AMI solution:
  • AMR solution: Only the Huawei EEM and DCP are deployed. This solution supports only server deployment.
  • The small-sized AMI solution is used in a scenario where there are at most 20,000 smart meters. In addition to the EEM and DCP, the third-party application system needs to be deployed. This solution supports virtualization deployment.
  • The standard AMI solution supports a maximum of 6,000,000 smart meters. The third-party application system needs to be deployed at the application layer. This solution supports virtualization deployment.

To provide highly-efficient and sustainable services, the AMI solution supports remote disaster recovery. The remote disaster recovery solution can be deployed in the single-node system or cluster mode, and supports only server deployment. The AMR solution, small-sized AMI solution, and standard AMI solution support remote disaster recovery. When the cluster mode is used, the application system needs to be configured with load balancing. The remote disaster recovery solution supports only the F5 load balancer, so each application system needs to be configured with the F5 load balancer.

The architecture varies depending on the solution and deployment mode. The deployment mode and device selection are also different. Table 1-1 describes design principles of the AMI solution.
Table 1-1  AMI solution design

Solution Selection

Number of Smart Meters

Deployment Mode

Application System Configuration

Remote Disaster Recovery

Description

AMR

0-6,000,000

Server deployment

  • EEM
  • Database
  • DCP
  • (Optional) Load balancing

Remote disaster recovery is supported. For details, see Remote Disaster Recovery Design.

Only the EEM and DCP need to be deployed at the application layer, and can be configured in the single-node system or cluster mode. The solution supports MySQL and Oracle databases. Load balancing needs to be deployed when cluster deployment is used.

Small-sized AMI solution

0-20,000

Server deployment

  • Third-party application system
  • EEM
  • Database
  • DCP
  • (Optional) Load balancing

Remote disaster recovery is supported. For details, see Remote Disaster Recovery Design.

The third-party application system, EEM, and DCP need to be deployed at the application layer, and can be configured in the single-node system or cluster mode. The solution supports MySQL and Oracle databases. Load balancing needs to be deployed when cluster deployment is used.

VM deployment

Remote disaster recovery is not supported.

The third-party application system, EEM, DCP, and database need to be deployed on VMs, and can be configured in the single-node system or cluster mode. The solution supports MySQL and Oracle databases.

Standard AMI solution

0-6,000,000

Server deployment

  • Third-party application system
  • EEM
  • Database
  • DCP
  • (Optional) Load balancing

Remote disaster recovery is supported. For details, see Remote Disaster Recovery Design.

The third-party application system, EEM, and DCP need to be deployed at the application layer, and can be configured in the single-node system or cluster mode. The solution supports MySQL and Oracle databases. Load balancing needs to be deployed when cluster deployment is used.

VM deployment

Remote disaster recovery is not supported.

The third-party application system, EEM, DCP, and database need to be deployed on VMs, and can be configured in the single-node system or cluster mode. The solution supports MySQL and Oracle databases.

Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 6171

Downloads: 10

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next