Vendor quotas-Enterprise Mobile Application Studio(EMAS)-阿里云帮助中心

EMAS Mobile Push provides a feature to query quotas for Android vendor channels. This helps developers monitor real-time daily push quota usage for each vendor and prevent message delivery failures caused by exceeding the quota.

Procedure

Log on to the EMAS console and select the Mobile Push product.
On the Mobile Push product page, in the navigation pane on the left, choose Troubleshooting Tools > Vendor Quotas.
On the Vendor Quotas page, you can view the daily quota limit and the current quota usage for each vendor channel.

Quota query

Vendor channel	Daily quota query	Vendor remaining quota query
Xiaomi	Supported. Queries and updates every 60 s.	Supported. Queries and updates every 60 s.
OPPO	Supported. Queries and updates every 60 s.	Supported. Queries and updates every 60 s.
vivo	Supported. Queries and updates every 60 s.	Supported. Queries and updates every 60 s.
Huawei	Not supported	Not supported
Meizu	Not supported	Not supported
Honor	Not supported	Not supported
FCM	Not supported	Not supported

Multi-package name scenarios

Prerequisites

You have completed the integration with the corresponding vendor channel. For more information, see Vendor channel integration.
You have added a main package and one or more channel packages to your EMAS application. For more information, see Configure multiple package names.

Comparison of vendor rules

EMAS supports configuring multiple package names for an Android application to enable synchronous pushes to different channels.

However, the mapping between an application on a vendor's developer platform and a package name in EMAS varies by vendor. This directly affects how push quotas are calculated.

Vendor platform	Relationship between an EMAS package name and a vendor application	Quota calculation method	Configuration requirements
Xiaomi Open Platform	One application can be attached to multiple packages.	All packages share one quota.	All packages must belong to the same application on the Xiaomi Open Platform.
OPPO Open Platform	Each package corresponds to an independent application.	Each package has its own quota.	The main package and channel packages are separate, independent applications.
vivo Open Platform	Each package corresponds to an independent application.	Each package has its own quota.	The main package and channel packages are separate, independent applications.

Configuration example

Suppose your application package name is com.company.test, and you plan to use different package names for different vendors to implement multi-package pushes on the EMAS platform:
- Xiaomi: com.aliyun.emas.xiaomi
- OPPO: com.aliyun.emas.oppo
- vivo: com.aliyun.emas.vivo

First, create your application on each vendor platform. Configure the applications as follows:

Vendor platform	Configuration method	Quota result
Xiaomi Open Platform	Create an application for `com.company.test` and add `com.company.test.xiaomi` as a multi-package name for the application	Shared quota
OPPO Open Platform	Create two separate OPPO applications for `com.company.test` and `com.company.test.oppo`	Independent quota
vivo Open Platform	Create two separate vivo applications for `com.company.test` and `com.aliyun.emas.vivo`	Independent quota

Note

For information about how to configure multiple package names for Xiaomi, see Multi-package name push usage guide.

In the EMAS console, create an Android application with the package name com.company.test.
In the navigation pane on the left, choose Configuration Management > Application Configuration. Configure the multiple package names and then click Save:
- com.aliyun.emas.xiaomi
- com.aliyun.emas.oppo
- com.aliyun.emas.vivo
After you save the settings, on the Application Configuration page, configure the package information as follows:
- Xiaomi: Configure com.company.test and com.company.test.xiaomi using the information from the same application on the Xiaomi Open Platform.
- OPPO: Configure com.company.test and com.company.test.oppo using the information from their corresponding applications on the OPPO Open Platform.
- vivo: Configure com.company.test and com.company.test.vivo using the information from their corresponding applications on the vivo Open Platform.
See Vendor channel integration to complete the integration with the corresponding vendor channels.
In the navigation pane on the left, choose Troubleshooting Tools > Vendor Quotas to view the quota details for each vendor.