1. Overview

The HUAWEI Ability Gallery provides content ability by obtaining content from a developer server through an API. The service display is defined by the HUAWEI.

To create a content ability:

1. Register as a HUAWEI Developer.
   To register a HUAWEI Developer account, please refer to Registration and ID Verification.

2. Develop the ability.
   The content API provided by developers must comply with Huawei’s requirements. For details, see API Specifications.

3. Register the ability.
   Register the ability on HUAWEI Ability Gallery.

2. Registration Process

2.1 Preparations for Connection

The developer should provide the content API. For detailed API requirements, see the API Specifications.

2.2 Creating an Ability

Step 1: Log in to HUAWEI Developer and go to Console > Abilities > HUAWEI Ability Gallery.

Step 2: Click Create to create a content ability.

On the Create page, select the ability category and enter the ability name, for example, weather broadcasting. Click create to enter the configuration page.

Step 3: Under the interaction menu, add intent triggers.

Instructions:
− Intent: Enter the intent name.
− Intention category: Select a category from the drop-down list.
− Trigger mode:

• Picture: Users can search for the ability by taking photos.
• Bar code: Users can search for the ability by scanning a Bar code.
• Keywords: Enter keywords for this intent. When users enter a keyword in global search, related abilities will be displayed. Keywords can contain only letters and numbers, separated by commas (,).

Step 4: Fullfillment
If system card is selected, click Fulfillment to complete the detailed configurations.

Step 5: Data permissions: choose the data permissions of the user authorization.

Step 6: Account binding: You can select an authentication method and set an access key and secret key. Then complete the service deployment information and save the settings.

Step 7: Surface capabilities: choose the specific capabilities, then the service will be automatically distributed to available devices.

Step 8: On the Ability info page, enter the basic information about the service.

• Ability name: Use the name created in the previous step. For example: Food delivery, movie ticket booking, air ticket booking, hotel booking, etc.
• Summary and description: a brief description of the ability.
• Version: enter numbers only.
• Version description: Enter the detailed description for the current version of the ability. Icon: upload a small icon of the ability. Size: 72*72px; format: .png, .jpg, or .jpeg.
• Click Save.
  

2.3 Testing an Ability

2.3.1 Click the Test button to submit your ability for release a test.

2.3.2 Release an Ability

• Choose the release countries.
• Click Save and HUAWEI Operations will review the submission and release it on HUAWEI Ability Gallery once approved.
  

2.4 Updating an Ability

If you need to update an ability after submission, click the edit button. After you have updated it, you need to release it for test again, and click the Upgrade button after a successful test.

2.5 Removing an Ability

To remove an ability from HUAWEI Ability Gallery, click the Delete button.

2.6 Management Ability Version

Developer can check their released ability versions under the Version management menu.

3. API Specifications

Performance requirements:

• The interface TPS must be greater than 2000.

• When the TPS is at its maximum, the latency should be less than 150 ms in 99% of cases.

• Successful call rate should be higher than 99.99%. The service interruption is no longer than 20 minutes over a year.

• The system should support horizontal scaling to support business development. Security requirements:

• Interface protocol: HTTPS

• HTTPS certificate requirements: Use valid CA certificate. Do not use a certificate with your signature.

• Request method: POST

• Max response size for an interface: 24KB. See the API definition for details.

• Resource links (such as image and audio links) in interfaces must be HTTPS.

• Certification requirements:
  Standard OAuth2.0 or AK/SK authentication is required for interfaces.
  (1) AK/SK authentication:

(2) Replay prevention

To prevent replay, the server needs to check whether the time difference between the TS in the packet and the current time is within a certain range.

For example: The absolute value (ABS) of the difference between the timestamp on the server and that in the request packet is less than 15 minutes.

(3) Signature algorithm

The following is an example code for Sign. The server can calculate “sign” based on the TS and check it against the one in the request to verify the client identity.

Mac mac = Mac.getInstance(HMAC_SHA256);
SecretKey secretKey = new
SecretKeySpec(secret.getBytes(SystemCharsets.UTF_8), HMAC_SHA256);
mac.init(secretKey);
byte[] byteHMAC = mac.doFinal(ts.getBytes(SystemCharsets.UTF_8));
byte[] sign = Base64.encodeBase64(byteHMAC);

(4) OAuth2.0

OAuth2.0 standard is applied.

Error codes are described in the following table.

If a response contains any of the preceding errors, detailed error description is in the returned errorCode and errorMessage.

Service result code (errorCode) and result description are described in the following table.

4. Service Flow