El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- What's New
- Service Overview
- Getting Started
-
User Guide
- Management Platform
- Developer Center
-
Developer Guide
-
Product Development
- Obtaining Development Resources
- Creating a Project and Product
- Developing a Product Model
-
Developing a Codec
- Development Guide
- Offline Development
- Codec Development Examples
-
Reference
- Message Processing Flow
- decode API Description
- Description of encode API
- getManufacturerId Interface Description
- getModel Interface Description
- Precautions on Interface Implementation
- Input/Output Format of the Codec Plug-In
- Implementation Sample Interpretation
- Appendix: Encryption Algorithms Supported by the JDK
- Developing an Application
- Developing a Device
- Self-Service Testing
- Product Release
- Device Interconnection
- Application Interconnection
-
SDK Usage Guide on the Device Side
-
LiteOS SDK Integration Development Guide
- Overview
-
Processfor Connecting Devices to OceanConnect on the Device Side
- Preparations
- Entrypoint Function for LiteOS SDK Device-Cloud Interconnect Components
- Initializing LiteOS SDK Device-Cloud Interconnect Components
- Creating a Data Reporting Task
- Command Processing Function for LiteOS SDK Device-Cloud Interconnect Components
- Main Function Body for LiteOS SDK Device-Cloud Interconnect Components
- Data Structure
- Appendix 1 LWM2M
-
LiteOS SDK Integration Development Guide
-
SDK Usage Guide on the Application Side
-
Huawei IoT Platform Java SDK Usage Guide
- Before You Start
- Requirements for the Development Environment
- Downloading Related Development Resources
- Importing the Java SDK Demo
- Initializing and Configuring Certificates
- Calling Service APIs
- Implementing Callback APIs and Making, Exporting, and Uploading a Callback Certificate
- Service API Calling Process and Precautions
- Testing the SDK
-
Huawei IoT Platform Java SDK Usage Guide
-
Product Development
-
API Reference
-
Northbound API Reference
- Overview
- API Usage Statement
- Secure Application Access
- Device Management
- Data Collection
-
Subscription Management
- Subscribing to Service Data of the IoT Platform
- Subscribing to Management Data of the IoT Platform
- Querying a Subscription
- Querying Subscription in Batches
- Deleting a Subscription
- Deleting Subscriptions in Batches
-
Push Notification
- Pushing Device Registration Notifications
- Pushing Device Binding Notifications
- Pushing Device Information Change Notifications
- Pushing Device Data Change Notifications
- Pushing Batch Device Data Change Notifications
- Pushing Device Service Capability Change Notifications
- Pushing Device Service Capability Addition Notifications
- Pushing Device Service Capability Deletion Notifications
- Pushing Device Deletion Notifications
- Pushing Device Acknowledgment Notifications
- Pushing Device Command Response Notifications
- Pushing Command Status Change Notifications
- Pushing Rule Event Notifications
- Pushing Device Shadow Status Change Notifications
- Pushing Software Upgrade Status Change Notifications
- Pushing Software Upgrade Result Notifications
- Pushing Firmware Upgrade Status Change Notifications
- Pushing Firmware Upgrade Result Notifications
- Command Delivery
- Batch Processing
- Device Group Management
- Device Upgrade
-
Northbound Java SDK API Reference
- SDK Demo Architecture and Usage Guide
- SDK Initialization Configuration and Test
-
Service API List
- Secure Application Access
- Device Management
- Batch Processing
- Subscription Management
-
Message Push
- Pushing Device Registration Notifications
- Pushing Device Binding Notifications
- Pushing Device Information Change Notifications
- Pushing Device Data Change Notifications
- Pushing Batch Device Data Change Notifications
- Pushing Device Service Information Change Notifications
- Pushing Device Deletion Notifications
- Pushing Device Acknowledgment Notifications
- Pushing Device Command Response Notifications
- Pushing Device Event Notifications
- Pushing Device Model Addition Notifications
- Pushing Device Model Deletion Notifications
- Pushing Device Shadow Status Change Notifications
- Pushing Software Upgrade Status Change Notifications
- Pushing Software Upgrade Result Notifications
- Pushing Firmware Upgrade Status Change Notifications
- Pushing Firmware Upgrade Result Notifications
- Pushing NB-IoT Command Status Change Notifications
- Command Delivery (NB-IoT Commands)
- Command Delivery (Non-NB-IoT Commands)
- Data Collection
- Device Group Management
-
Device Upgrade
- Querying a Version Package List
- Querying a Specified Version Package
- Deleting a Specified Version Package
- Creating a Software Upgrade Task
- Creating a Firmware Upgrade Task
- Querying the Result of a Specified Upgrade Task
- Querying Details About Subtasks of a Specified Upgrade Task
- Querying an Upgrade Task List
-
Northbound PHP SDK API Reference
- SDK Demo Architecture and Usage Guide
- SDK Initialization Configuration and Test
-
Service API List
- Secure Application Access
- Device Management
- Batch Processing
- Subscription Management
-
Message Push
- Pushing Device Registration Notifications
- Pushing Device Binding Notifications
- Pushing Device Information Change Notifications
- Pushing Device Data Change Notifications
- Pushing Batch Device Data Change Notifications
- Pushing Device Service Information Change Notifications
- Pushing Device Deletion Notifications
- Pushing Device Acknowledgment Notifications
- Pushing Device Command Response Notifications
- Pushing Device Event Notifications
- Pushing Device Model Addition Notifications
- Pushing Device Model Deletion Notifications
- Pushing Device Shadow Status Change Notifications
- Pushing Software Upgrade Status Change Notifications
- Pushing Software Upgrade Result Notifications
- Pushing Firmware Upgrade Status Change Notifications
- Pushing Firmware Upgrade Result Notifications
- NB-IoT Device Command Status Change Notification
- Command Delivery (NB-IoT Commands)
- Command Delivery (Non-NB-IoT Commands)
- Data Collection
- Device Group Management
-
Device Upgrade
- Querying a Version Package List
- Querying a Specified Version Package
- Deleting a Specified Version Package
- Creating a Software Upgrade Task
- Creating a Firmware Upgrade Task
- Querying the Result of a Specified Upgrade Task
- Querying Details About Subtasks of a Specified Upgrade Task
- Querying an Upgrade Task List
-
Northbound Python SDK API Reference
- SDK Demo Architecture and Usage Guide
- SDK Initialization Configuration and Test
-
Service API List
- Secure Application Access
- Device Management
- Batch Processing
- Subscription Management
-
Message Push
- Pushing Device Registration Notifications
- Pushing Device Binding Notifications
- Pushing Device Information Change Notifications
- Pushing Device Data Change Notifications
- Pushing Batch Device Data Change Notifications
- Pushing Device Service Information Change Notifications
- Pushing Device Deletion Notifications
- Pushing Device Acknowledgment Notifications
- Pushing Device Command Response Notifications
- Pushing Device Event Notifications
- Pushing Device Model Addition Notifications
- Pushing Device Model Deletion Notifications
- Pushing Device Shadow Status Change Notifications
- Pushing Software Upgrade Status Change Notifications
- Pushing Software Upgrade Result Notifications
- Pushing Firmware Upgrade Status Change Notifications
- Pushing Firmware Upgrade Result Notifications
- NB-IoT Device Command Status Change Notification
- Command Delivery (NB-IoT Commands)
- Command Delivery (Non-NB-IoT Commands)
- Data Collection
- Device Group Management
-
Device Upgrade
- Querying a Version Package List
- Querying a Specified Version Package
- Deleting a Specified Version Package
- Creating a Software Upgrade Task
- Creating a Firmware Upgrade Task
- Querying the Result of a Specified Upgrade Task
- Querying Details About Subtasks of a Specified Upgrade Task
- Querying an Upgrade Task List
- AgentLite API Reference (Android)
-
AgentLite API Reference (C)
- Before You Start
- API Description
-
Common Data Structures
- ST_IOTA_DEVICE_INFO Structure
- IEs in EN_IOTA_BIND_IE_TYPE Messages
- Enumerated Values of the EN_IOTA_BIND_RESULT_TYPE Parameter
- IEs in EN_IOTA_LGN_IE_TYPE Messages
- Enumerated Values of the EN_IOTA_LGN_REASON_TYPE Parameter
- Enumerated Values of the EN_IOTA_CFG_TYPE Parameter
- IEs in EN_IOTA_HUB_IE_TYPE Messages
- Enumerated Values of the EN_IOTA_HUB_RESULT_TYPE Parameter
- IEs in EN_IOTA_DATATRANS_IE_TYPE Messages
- IEs in EN_IOTA_DEVUPDATE_IE_TYPE Messages
- Data Types
- AgentLite API Reference (Java)
- MQTT Interface Reference
-
Northbound API Reference
-
FAQs
- FAQs
- Specifications
- Product Use
-
Secondary Development
-
FAQs About Product Development
-
Profile Definition
- How to Develop a Profile
- Upload Is Unavailable When Uploading a Profile to the Developer Center
- Incorrect File Format Is Displayed When Uploading a Profile to the Developer Center
- Message Is Displayed Indicating That the Manufacturer ID and Device Model Exist When Uploading a Profile to the Developer Center
- How to Select a Data Type When Developing a Profile Online
- Profile Cannot Be Edited
-
Plug-In Development
- How to Develop Codecs
- Failed to Deploy a Plug-in That Is Developed Online
- What Is the Code Rule for Fields of the string and varstring Types
- What Is the Code Rule for Fields of the array and variant Types
- Whether Plug-Ins That Are Developed Online Support Transparent Transmission
- How to Use messageId During Online Codec Development
- How to Configure a Command Delivery Response During Online Codec Development
- Failed to Deploy a Plug-in That Is Developed Offline
- Failed to Upload a Plug-in That Is Developed Offline
- Plug-In Package Developed Offline Has Been Checked But Cannot Be Found When Uploading to the IoT Platform
- Codec Exception Occurs After a Plug-In Package Developed Offline That Has Been Checked Is Uploaded to the IoT Platform
- Offline Signature Fails
-
Device Development
- Registered Devices Cannot Connect to the IoT Platform
- Message 513 Is Reported When Devices Are Connected to the IoT Platform
- DTLS Encryption Algorithms Supported by the IoT Platform
- What Does CTNB Mean
- How to Select PSM, DRX, and eDRX
- Devices Cannot Receive Commands from the IoT Platform
- IoT Platform Does Not Receive Data Reported by Devices
- Historical Data Does Not Contain Data Reported By Devices While No Error Occurs
- Duration for Devices to Receive Commands
- Devices Fail to Receive Data Reporting Responses
- Data Reporting Is Successful at One Position But Fails at Another Position
- Command Status Is Not Changed to Successful After a Device Reports the Command Execution Result
- Whether the IoT Platform Can Switch Between the Big-Endian and Little-Endian
- Commands Fail to Be Delivered When a Device in DRX Mode Does Not Report Data in One to Two Days
-
Profile Definition
-
FAQs About Application Development
-
Calling APIs
- Authentication API of the IoT Platform Is Successfully Called Locally But Fails to Be Called on Application Servers
- Error Occurs When an NA Calls an API
- Online Application Simulator Fails to Deliver Commands
- Command Is Successfully Delivered Using the Simulator But Fails to Be Delivered by Calling the API
- Application Server Fails to Deliver Commands and Receives Error Code 403
- How Does an Application Server Deliver a Cache Command
- What Does an Expired Command Mean
- Does the IoT Platform Support Command Resending
- What Does a Timeout Command Mean
- Can the IoT Platform Deliver Commands in Batches
- Are the APIs of the IoT Platform Called Only Using Java
- What Are the Command States on the IoT Platform
- Failed to Call the Calling the Registering Directly Connected Devices API
- APIs Fail To Be Called After a Period of Time While Parameters Remain Unchanged
- Commands Fail to Be Sent After a Period of Time While the Previous Commands Are Successfully Sent
- Historical Data Is Not Returned When the Querying Historical Device Data API Is Called
- Devices Registered with the IoT Platform Are Deleted After a Period of Time
-
Subscription and Push
- Invalid Callback Address Occurs When Calling the Subscription API
- How to Obtain the subscriptionId When Calling the Querying Subscription in Batches API
- Application Server Fails to Receive Data Pushed by the IoT Platform
- How Do I Export the HTTPS Push Certificate
- Difference Between deviceDatachanged and deviceDataschanged
- How Does an Application Server Obtain the IMEI of Devices
- Application Server Receives Data But an Error Is Displayed on the IoT Platform
- Push Messages May Fail to Be Sent to Application Servers
- How Does an Application Servers Obtain The Address Used by the IoT Platform to Push Messages
- Does the IoT Platform Supports Re-push
- How Does an Application Server Receive a Command Status Change Notification
- Application Servers That Have Subscribed to Confirmation Notifications and Command Response Notifications Fail to Receive Push Messages
- Does the IoT Platform Support Only HTTPS Callback Addresses
- Can the IoT Platform Push Data Reported by Different Devices Under the Same Application to Two Servers
- Can a Subscription Address Be a Domain Name
- Can a Callback Address Be Changed
- How Do I Obtain the Callback URL When Calling the Subscription API
-
Calling APIs
-
FAQs About Software/Firmware Upgrade
- What Is Software/Firmware Upgrade
- Can IoT Platform Download Software/Firmware Packages From Third-party Servers
- Can the Target Version Be Earlier Than the Source Version?
- How Do I Obtain Software/Firmware Packages and Their Version Numbers
- Software/Firmware Upgrade Task Is Ended Immediately After Being Created
- What Is the Source Version Required for Uploading a Firmware Package on the Management Portal
- When Reporting Data, Devices Receive the Software/Firmware Version Query Command from the IoT Platform
- Are Services Interrupted During the Software/Firmware Upgrade
- What Are Common Software/Firmware Upgrade Errors
- Retry When Some Devices in the Group Failed to Be Upgraded
- Is Resumable Transmission Supported When the IoT Platform Sends Software/Firmware Packages to Devices
-
Others
- Does the IoT Platform Support Device Registration in Batches
- Does the IoT Platform Perform Flow Control on Applications and Devices
- How Does an Application Server Obtain Data Reported by Devices to the IoT Platform
- Is the Maximum Number of Applications and Devices Restricted on the IoT Platform
- Why Is an Online Device Changed to an Abnormal or Offline State After a Period of Time
- Are Command Delivery and Data Reporting Successful After a Device Becomes Abnormal or Offline
- How Long Does a Device Receive an Immediately-Delivered Command in eDRX Mode
- How Long Is Data Stored on the IoT Platform
- Can Multiple Devices Use One IMEI
-
FAQs About Product Development
- General Reference
Copied.
Packaging the Codec
This topic describes how to package the codec and prepare the package.
Packaging the Codec Using Maven
After the codec is programmed, use Maven to package the codec. On the Windows OS, perform the following steps:
- Open the DOS window and access the directory where the pom.xml file is located.
- Run mvn package.
- After BUILD SUCCESS is displayed in the DOS window, open the target folder in the same directory as the pom.xml file to obtain the .jar package.
The naming rule of the .jar package is as follows: device type-manufacturer ID-device model-version.jar, for example: WaterMeter-Huawei-NBIoTDevice-version.jar.
Figure 1 Structure of the .jar file- The com directory stores class files.
- The META-INF directory stores description files of .jar packages under the OSGi framework, which are generated based on configurations in the pom.xml file.
- The OSGI-INF directory stores service configuration files and is used to register the codec as a service for the platform to call. (Only one .xml file can be called.)
- Other .jar packages are .jar packages referenced by codecs.
Preparing a Codec Package
- Create a folder named package, which contains the preload/ sub-folder.
- Place the packaged .jar package in the preload/ folder.
Figure 2 Structure of the codec package
- In the package folder, create the package-info.json file. The fields and templates in this file are described as follows:
NOTE:
The package-info.json file is encoded using UTF-8 without BOM. Only English characters are supported.
Table 1 Description of fields in the package-info.json file Field
Description
Mandatory or Optional
specVersion
Specifies the version of the description file. The value is fixed at 1.0.
Mandatory
fileName
Specifies the name of the software package. The value is fixed at codec-demo.
Mandatory
version
Specifies the version number of the software package. The version of the package.zip file must be the same as the value of bundleVersion.
Mandatory
deviceType
Specifies the device type, which must be the same as that defined in the profile file.
Mandatory
manufacturerName
Specifies the manufacturer name, which must be the same as that defined in the profile file. Otherwise, the package-info.json file cannot be uploaded to the IoT platform.
Mandatory
model
Specifies the product model, which must be the same as that defined in the profile file.
Mandatory
platform
Specifies the platform type, which is the operating system of the IoT platform on which the codec package runs. The value is fixed at linux.
Mandatory
packageType
Specifies the software package type. This field is used to describe the IoT platform module where the codec is deployed. The value is fixed at CIGPlugin.
Mandatory
date
Specifies the time when a packet is sent. The format is as follows: yyyy-MM-dd HH-mm-ss. For example, 2017-05-06 20:48:59.
Optional
description
Specifies the self-defined description about the software package.
Optional
ignoreList
Specifies the list of bundles to be ignored. The default value is null.
Mandatory
bundles
Specifies the description of a bundle.
NOTE:
A bundle is a .jar package in a compressed package. Only one bundle needs to be described.
Mandatory
Table 2 Description of the bundles field Field
Description
Mandatory or Optional
bundleName
Specifies the bundle name, which is consistent with the value of Bundle-SymbolicName in the pom.xml file.
Mandatory
bundleVersion
Specifies the bundle version, which must be the same as the value of version.
Mandatory
priority
Specifies the bundle priority. This parameter can be set to the default value 5.
Mandatory
fileName
Specifies the codec file name.
Mandatory
bundleDesc
Describes the bundle function.
Mandatory
versionDesc
Describes the functions and features of different versions.
Mandatory
Template of the package-info.json file
{ "specVersion":"1.0", "fileName":"codec-demo", "version":"1.0.0", "deviceType":"WaterMeter", "manufacturerName":"Huawei", "model":"NBIoTDevice", "description":"codec", "platform":"linux", "packageType":"CIGPlugin", "date":"2017-02-06 12:16:59", "ignoreList":[], "bundles":[ { "bundleName": "WaterMeter-Huawei-NBIoTDevice", "bundleVersion": "1.0.0", "priority":5, "fileName": "WaterMeter-Huawei-NBIoTDevice-1.0.0.jar", "bundleDesc":"", "versionDesc":"" }] }
- Select all files in the package folder and compress them into a package.zip file.
NOTE:
The package.zip file cannot contain the package directory.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot