Message Push Service (MPS) is a mobile push solution provided by Mobile PaaS (mPaaS). It supports multiple push types and channels — including APNs, Firebase Cloud Messaging (FCM), and vendor channels from Huawei and Xiaomi — so you can reach users reliably whether they are online or offline.
Features
MPS lets you send messages through self-hosted channels and third-party vendor channels, using either the console or an API. The following features are available:
Multiple push methods: Send targeted messages to a single user, a custom user group, or all users — from the Mobile Push Service console or via API calls.
Custom message validity period: If a device is offline when a message is first sent, MPS resends the message when the device reconnects or a user binding is initiated within the validity period, ensuring delivery to the target user.
Device and user targeting: Establish a relationship between devices and logged-in users, then push messages by device ID or user ID.
Custom message templates: Create and manage templates on the template management page to support personalized push requirements.
SMS fallback: When users cannot receive app pushes due to network issues, background restrictions, or message delays, MPS automatically falls back to SMS delivery.
Scheduled pushes: Schedule a one-time push for a specific time, or set up recurring pushes within a defined period — reducing manual operations overhead.
Message revocation: Revoke sent messages from the console or via API — useful when incorrect content is sent or a business change requires immediate recall.
Usage analytics: Based on client-side instrumentation data, MPS tracks delivery rate and open rate across dimensions such as platform, version, push channel, push type, and time. Analysis reports support minute-level granularity.
User tags: Tag users to send targeted pushes to specific groups, enabling fine-grained campaign operations.
Push configuration: Configure push certificates on the push configuration page to select the Apple Push Notification service (APNs) gateway for iOS devices.
Vendor channel integration: Connect to Huawei, Xiaomi, and other vendor push channels to improve push delivery rates across Android devices.
Key management: All external MPS API requests are signed for security. Configure your own signing keys on the key configuration page. MPS also provides message receipts to track delivery results.
How it works
MPS is a core mPaaS component that communicates directly with client apps. It transmits notification data over long-lived TCP connections or through third-party vendor channels.
The client app uses the mPaaS Mobile Gateway Service (MGS) to make remote procedure calls (RPCs) to the gateway. This registers the device, binds the user, and establishes a relationship with the appropriate vendor channel — enabling pushes based on device and user dimensions. The backend collects and uploads client behavior logs per predefined specifications; MPS analyzes this push data in real time to generate statistical reports.
For sending messages, MPS supports both API pushes and console pushes. Use API calls on your server to send custom messages driven by your business logic, or send directly from the console. To maximize delivery rates, MPS integrates channels including Huawei, Xiaomi, Firebase Cloud Messaging (FCM), and APNs. This integration is transparent to your backend — your business systems do not need to handle per-device or per-vendor differences.
Benefits
High delivery reliability: MPS routes messages through long-lived TCP connections and vendor channels (Huawei, Xiaomi, FCM, APNs), with offline retry within the validity period.
Low integration cost: Reduces integration costs and improves efficiency by providing unified access to push channels through a single integration point.
Measurable results: Built-in analytics report delivery rates and open rates at minute-level granularity, giving clear visibility into push effectiveness.
-
Precise targeting:
Send personalized messages to individual users, custom user groups, or segments defined by tags.
Use the console for simple one-off pushes, or use the server-side API for automated, high-volume campaigns.
Track delivery results via message receipts to measure reach and improve user retention.
Link device IDs to your app's user accounts and address messages to usernames directly — delivered to whichever device the user is currently logged in on.
Use cases
-
Marketing campaigns
Use the push API to send promotions or business reminders to targeted user segments. Proactively reaching users at the right moment drives conversions and improves campaign effectiveness.
-
System notifications
Specify the target audience based on your server-side business logic and push messages directly to target devices — for example, account alerts, order status updates, or real-time service events.
MPS provides the following push types:
Simple Push: Push a message to a single user or device with minimal configuration. Supports both custom message content and pre-created templates.
Template Push: Push a message to a single user or device using a template. Placeholders are replaced with specified values to generate the message content.
Multiple Push: Push messages to many devices or users at once using a configuration file that maps different placeholder values to different targets.
Broadcast Push: Push the same template message to all Android or iOS devices on the network.
-
Simple Push
Push a message to a single user or device with minimal configuration. Choose between custom message content for one-off targets (such as testing an APNs certificate or verifying an Android SDK integration) or a pre-created template for repeated pushes to multiple targets. Validate the template feature by creating a template push message in the console before using it in automation or at scale.
-
Multiple Push
Push messages to many devices or users using a configuration file that maps placeholder values to individual targets. Multiple Push supports broadcast and non-broadcast modes: broadcast sends the same template message to all Android or iOS devices on the network; non-broadcast sends it to a specified user group.