Delivering push notifications reliably across iOS and Android requires managing multiple vendor channels — APNs, Huawei Push Kit, Xiaomi push, and others — through separate integrations. Message Push Service (MPS) consolidates these into a single integration point, letting you send targeted notifications to individual devices or large user segments from the mPaaS console or API.
mPaaS Message Push Service (MPS) now uses a new console. The four previous push methods — Simple Push, Template Push, Batch Push, and Broadcast Push — are consolidated into two methods: Simple Push and Batch Push. Template Push (legacy) and Broadcast Push (legacy) are no longer available in the new console.
What MPS gives you
Multi-platform delivery: Route notifications through APNs for iOS and through vendor channels (Huawei Push Kit, Xiaomi push, and others) for Android, from a single integration.
Two push methods for different scales: Use Simple Push for testing, validation, and ad-hoc sends; use Batch Push for large-scale campaigns targeting segments or all users.
Console and API access: Send and manage messages from the mPaaS console without writing code, or automate delivery via the MPS API and SDK.
Delivery tracking: Monitor send status, arrival rates, and click-through rates per message in the console.
Choose a push method
|
Push method |
Best for |
How to send |
|
Simple Push |
Testing, system validation, ad-hoc operational support, and low-frequency sends |
Console or API |
|
Batch Push |
Large-scale campaigns, scheduled sends, and audience-segmented delivery |
Console or API |
Template Push and Broadcast Push are legacy names from the previous console. They map to Simple Push and Batch Push respectively in the new console. If you see references to these names in older guides, use the equivalents above.
How MPS works
Register your app and configure vendor channel credentials (APNs certificate or key for iOS; Huawei Push Kit credentials for Android) in the mPaaS console.
Integrate the mPaaS SDK into your iOS or Android app. The SDK handles device token registration and vendor channel routing automatically.
Send a push notification using Simple Push (console or API) to verify end-to-end delivery before going to production.
Use Batch Push to send to segments or all registered devices at scale.
Track delivery and click-through rates in the console message report.
Supported platforms
|
Platform |
Delivery channel |
Credential required |
|
iOS |
Apple Push Notification service (APNs) |
APNs certificate or APNs authentication key |
|
Android (Huawei devices) |
Huawei Push Kit |
Huawei Push Kit app credentials |
|
Android (Xiaomi devices) |
Xiaomi push |
Xiaomi push app credentials |
|
Android (other devices) |
mPaaS default channel |
None (uses SDK direct connection) |
Android devices on Huawei or Xiaomi require the corresponding vendor channel to deliver notifications when the app is not running. Without vendor channel configuration, notifications only arrive while the app is in the foreground or the mPaaS SDK maintains an active connection.
Get started
Complete these steps in order to send your first push notification:
Configure vendor channel credentials — Set up APNs, Huawei Push Kit, or Xiaomi push credentials in the console.
Integrate the SDK — Add the mPaaS SDK to your iOS or Android project.
Send a message with Simple Push — Send a test notification to a single device token.
Send a message with Batch Push — Send to a segment or all users at scale.
View message reports — Check delivery status and arrival rates.
See also
Simple Push
Batch Push
SDK integration guide
Troubleshooting push delivery