We use essential cookies for the website to function, as well as analytics cookies for analyzing and creating statistics of the website performance. To agree to the use of analytics cookies, click "Accept All". You can manage your preferences at any time by clicking "Cookie Settings" on the footer. More Information.

Only Essential Cookies
Accept All

Overview

Content overview

The Pushing Scenario-Specific Messages section describes all push scenarios of Push Kit. The development of each scenario can be roughly divided into two major steps:

  1. Obtain a push token and complete push scenario ArkTS code development for the device side.

  2. Send a request to the Push Kit server to send a scenario-specific message.

This section provides more detailed server-side (also referred to as "cloud-side") development content based on the major steps, so you can better conduct device-cloud debugging after device-side development. Before performing operations in this section, ensure that you have successfully obtained a push token.

Service Process

The main service process on the Push Kit server is as follows:

  1. The app server sends a request to the Push Kit server for pushing a scenario-specific message. Then the app server receives a response from the Push Kit server.

  2. The Push Kit server delivers the scenario-specific message to the device where the app is installed, and the Push Kit client returns the response status to the Push Kit server.

  3. The Push Kit server sends a message receipt to the app server. You can complete operations in (Optional) Developing the Message Receipt, so your server can receive the returned status after the Push Kit server delivers the message to the device side. If the message receipt function is not enabled, message delivery will not be affected.

Search in Guides
Enter a keyword.