Terms

Term

Description

Application

An entity that is independently published, deployed, and run. It is a specific type of client program. Types include but are not limited to Android, iOS, HarmonyOS, Weex, H5, and PC.

Project

A group of applications used to manage related applications.

Service

A collection of specific features for an application that are available to developers. A service is the smallest billable unit. Examples include the Mobile Hotfix service and the Mobile Push service.

Solution

A collection of methodologies, design concepts, and service capabilities for a specific scenario. Examples include cross-platform solutions and continuous delivery solutions.

AppKey

The unique identifier of an app in EMAS. This key is required for software development kit (SDK) initialization and for calling OpenAPI to send pushes. Obtain the AppKey from the SDK Settings page under Application Settings in the EMAS console.

AppSecret

The secret key for an app. It is used during EMAS SDK initialization. Obtain the AppSecret from the SDK Settings page under Application Settings in the EMAS console.

RSA key

An RSA key is a decryption key stored locally on the client to decrypt a patch package. We recommend using the Chrome browser to download the package.

AccessKey ID and AccessKey secret

Required when an Alibaba Cloud user authenticates calls to the OpenAPI of a cloud product. Obtain your AccessKey ID and AccessKey secret from the Alibaba Cloud console.

Basic concepts

Description

Hotpatching

The process of applying a patch to a system that is running in a production state, not a development state.

Mobile Hotfix

The process of fixing online issues for mobile applications, such as Android applications, in real time without releasing a new version.

Baseline package

The original package of a newly released app version that has not been modified by any hotpatches.

Basic Concepts

Description

Notification

A notification that automatically appears in the notification bar on a mobile device. Users can open or clear the notification. iOS notifications are sent through the Apple Push Notification service (APNs). Android notifications are sent through the Mobile Push channel.

Message

A message that does not automatically appear in the notification bar. Instead, the app displays a receipt prompt. Both iOS and Android messages are sent through the Mobile Push channel.

Device ID

The unique identifier for a device in the push service. It is generated by the SDK and consists of a 32-character string of digits and lowercase letters. Obtain it programmatically. For Android, call the getDeviceId method of CloudPushService. For iOS, call the getDeviceId method of CloudPushSDK.

Alias

An alias attached to a device. It can be any account required by your business. A single device can have up to 128 aliases, and a single alias can be attached to up to 128 devices.

Push by device ID

Call getDeviceId on the client to obtain the device ID. Then, send pushes using the EMAS console or by calling the OpenAPI.

Push by alias

After attaching an alias to a device, filter aliases based on your business logic to send messages.

Broadcast push

A push sent to all devices. Also known as a "full push".

Offline message cache

A feature that lets you set a cache duration for pushes. Offline devices receive the message only if they come online within the specified duration.

Pass-through message

A custom message. The service only pushes the message without processing it. After the client receives the message, the client is responsible for handling how the message is displayed and what actions follow.

Vendor channel

An operating system-level push channel provided by a mobile device manufacturer. If the network is stable and the push message is valid, messages sent through this channel are guaranteed to be delivered to the target device, regardless of whether the application is running.

Proprietary channel

Alibaba Cloud Channel Service (ACCS), the basic push channel for Alibaba Cloud services.

Successful acceptances

For a request to be successfully accepted, the target device must be valid and capable of receiving messages. The device must not be expired (by default, Android devices must have been active within 90 days and iOS devices within 24 months, because push notifications cannot be sent to devices that have been inactive longer than these periods). The user must not have disabled PUSH.

The number of accepted requests excludes requests sent to devices that were unreachable at the time of the request.

Sent pushes

The number of messages that were successfully sent. For the proprietary channel, a message is considered sent when the service attempts to deliver the mobile terminated message after the device establishes a connection. For a third-party channel, a message is considered sent when it is successfully delivered to the third-party provider's server.

Arrival Count

The number of pushes that reached the device. Also known as "deliveries". The calculation method differs by device type:

• iOS devices: iOS notifications are delivered to Apple's APNs servers. A push is considered delivered if the APNs server does not return an error.

• Android devices: The number of delivered pushes is the sum of deliveries from both the proprietary and third-party channels. Each channel provides a delivery receipt.

Delivery rate

The ratio of delivered pushes to accepted pushes.

DeviceToken

A 64-bit device identifier returned when an iOS device registers with Apple. Note: An iOS device has both a deviceId and a deviceToken. Do not confuse them.

Message ID

The ID that identifies a specific push. This ID is returned when you send a push by calling the OpenAPI. You can also find it in the push console.