All Products
Search
Document Center

Use third-party service data

Last Updated: Mar 10, 2021

Some of the components and services provided by mPaaS are based on features of third-party services. Therefore, when you use these components or services in mPaaS, you must obtain verification from the third-party services or send requests to obtain relevant data. This topic provides details based on different platforms.

Android

UC core

UC cores require UCKEY verification. Therefore, you must obtain verification from relevant third-party services.

Location-based service (LBS)

The LBS component in mPaaS is a location service based on Amap. To use LBS, you must send requests for data to the Amap server.

Mini programs

The map and positioning services in mini programs are location services based on Amap. To use these services in mini programs, you must send requests for data to the Amap server.

Social media sharing

The social media sharing component in mPaaS supports such platforms as Weibo, WeChat, Alipay, QQ, SMS messages, and DingTalk. The sharing feature in mPaaS is based on share SDKs from third-party services. If a share SDK of a third-party service contains a request for data that is to be sent to the third-party server, which is the server of the third-party service, the sharing component in mPaaS will send the request to the third-party server.

The following table describes the types of and relevant information about the third-party share SDKs that are supported by the social media sharing component in mPaaS.

Third-party SDK SDK description Scenario
WeChat share SDK This SDK allows sharing texts, pictures, music, videos, webpages, and mini programs from a third-party application to WeChat friends, or Moments, or adding these objects to Favorites. Redirect from the share page of an app to WeChat.
QQ share SDK This SDK allows sharing content, such as news, pictures, texts, and apps, to QQ friends or Qzone. Redirect from the share page of an app to QQ.
Alipay share SDK This SDK allows sharing pictures and webpages to Alipay. Redirect from the share page of an app to Alipay.
Weibo share SDK This SDK allows sharing content to Weibo. Redirect from the share page of an app to Weibo.
DingTalk share SDK This SDK allows sharing content to DingTalk. Redirect from the share page of an app to DingTalk.

Message push.

To improve the arrival rate of pushed messages, mPaaS connects to the message push services (MPS) of Huawei, Xiaomi, OPPO, and VIVO by integrating their MPS SDKs. The MPS SDKs of Huawei and Xiaomi are already integrated in mPaaS. You can manually integrate the MPS SDKs of OPPO and VIVO based on your needs.

The following table describes the types of and relevant information about the third-party MPS SDKs that are supported by the message push component in mPaaS.

Third-party SDK SDK description Scenario
Huawei MPS SDK This SDK is used to push messages to user terminals in real time. It helps build better user relationships and improve user experience and activeness. Push messages to Huawei mobile phones.
Xiaomi MPS SDK Xiaomi MPS is a system-level channel in MIUI and is available across all platforms. It provides a stable, reliable, and efficient push service. Push messages to Xiaomi mobile phones.
OPPO MPS SDK This SDK establishes a stable, reliable, and persistent connection channel between a server and an operating system. Through this channel, this SDK allows pushing real-time messages to apps on ColorOS, the operating system of OPPO mobile phones. This message push service efficiently improves user retention rate and user activeness for an app owned by a developer, and optimizes product experience. Push messages to OPPO mobile phones.
VIVO MPS SDK VIVO MPS is a message push service that VIVO provides for developers. VIVO MPS establishes a stable, reliable, and persistent connection channel between the cloud and a client. Through this channel, VIVO MPS allows developers to push messages to apps on the client in real time. This SDK provides the capability of pushing billions of messages or notifications with a second-level arrival rate. Push messages to VIVO mobile phones.

iOS

Mini programs

The map and positioning services in mini programs are location services based on Amap. To use these services in mini programs, you must send requests for data to the Amap server.

Social media sharing

The social media sharing component in mPaaS supports such platforms as Weibo, WeChat, Alipay, QQ, SMS messages, and DingTalk. The sharing feature in mPaaS is based on share SDKs from third-party services. If a share SDK of a third-party service contains a request for data that is to be sent to the third-party server, which is the server of the third-party service, the sharing component in mPaaS will send the request to the third-party server.

The following table describes the types of and relevant information about the third-party share SDKs that are supported by the social media sharing component in mPaaS.

Third-party SDK SDK description Scenario
WeChat share SDK This SDK allows sharing texts, pictures, music, videos, webpages, and mini programs from a third-party application to WeChat friends, or Moments, or adding these objects to Favorites. Redirect from the share page of an app to WeChat.
QQ share SDK This SDK allows sharing content, such as news, pictures, texts, and apps, to QQ friends or Qzone. Redirect from the share page of an app to QQ.
Alipay share SDK This SDK allows sharing pictures and webpages to Alipay. Redirect from the share page of an app to Alipay.
Weibo share SDK This SDK allows sharing content to Weibo. Redirect from the share page of an app to Weibo.
DingTalk share SDK This SDK allows sharing content to DingTalk. Redirect from the share page of an app to DingTalk.

Conflict-free versions of fast payment components on Alipay Open Platform

mPaaS provides conflict-free versions for some components on Alipay Open Platform. Therefore, if a component requests data from a third-party server, the conflict-free version of the component provided by mPaaS also requests data from the third-party server.