Development Scope
Scope and Basic Check
Determine the existing foundation, technical dependencies and content that needs to be developed based on the Broker address, TLS and certificate, device identity, topic, message model, QoS and session rules.
Implementation and integration
Develop connection authentication, publish and subscribe, heartbeat, session recovery and error diagnosis, and unify device fields, command identification and message confirmation.
Delivery Documentation
Deliver client code, protocol description and server integration testing records.
Verification and Constraints
Certificates, time synchronization, module or main controller protocol stack capabilities need to be confirmed one by one; the device status cannot be judged only by TCP connection.
Project implementation process
Verification of data and interfaces → Confirmation of technical solutions and verification use cases → Implementation of integration with the target environment → Regression of abnormal scenarios → Transfer of version data.
Verify the implementation results in the target hardware and software environment, and deliver records of associated interface configurations, version dependencies, and problem handling to facilitate subsequent integration and maintenance by the enterprise R&D team.
Project Inputs
- Broker address, TLS and certificate, device identity, topic, message model, QoS and session rules.
- Design information, code, interface permissions and target test equipment can be provided.
- Source files, programs or tools expected to be delivered, inter-module integration testing responsibilities and project nodes.
- Acceptance samples, environment, test conditions and passing thresholds.
Deliverables and Acceptance
| Deliverables | Delivery content | Verification method |
|---|---|---|
| achieve results | Deliver client code, protocol description and server integration testing records. | Verify legal and invalid identity access. |
| Integrated data | Versions and dependencies, interface configuration, usage or deployment steps, and integration changes | Test session reconstruction and message re-delivery. |
| Verify records | Test conditions, execution records, problem lists and regression results | Check fields, timestamps and duplicate message handling. |
The delivery scope and acceptance criteria are determined based on the target environment. Third-party SDK, licenses, laboratories, cloud resources, equipment materials and on-site support are listed separately; when the existing information is insufficient, follow-up work will be determined through interface verification or key function verification.
Frequently Asked Questions
Can using MQTT QoS avoid duplication of business execution?+
QoS describes the message delivery mechanism, and the business still needs to define unique identifiers, execution status, and idempotent processing. Control messages should check the validity period and results and cannot rely solely on transmission confirmation.
4G MQTT What information do I need to provide first for device access development?+
Please provide the Broker address, TLS and certificate, device identity, topic, message model, QoS and session rules first. At the same time, the existing implementation, problems encountered, expected changes, and compatible test conditions are explained to facilitate the determination of implementation scope and reproduction methods.
Can it be implemented on existing products?+
You can first evaluate the scope of existing designs and versions that can be changed, retain the verified parts, and determine the interfaces and dependencies that need to be adjusted. This service requires attention: certificates, time synchronization, module or main controller protocol stack capabilities need to be confirmed one by one; the device status cannot be judged only by TCP connection. Existing and new functions must undergo regression testing within the agreed scope after the changes.
Online
Phone
WeChat
Top