Development Scope
Scope and Basic Check
Determine the existing foundation, technical dependencies and content that needs to be developed based on fault logs, network topology, module firmware, link priorities, switching conditions and business recovery objectives.
Implementation and integration
Differentiate equipment, network, platform and service faults, and design detection, retry backoff, controlled reset, link switching and data synchronization after recovery.
Delivery Documentation
Deliver state machines and fault injection records.
Verification and Constraints
Avoid treating all failures as a complete machine restart; the cause of the failure and recovery records must be retained for regression.
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
- Fault logs, network topology, module firmware, link priority, switching conditions and business recovery goals.
- 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 state machines and fault injection records. | Inject network outages, DNS and server failures. |
| Integrated data | Versions and dependencies, interface configuration, usage or deployment steps, and integration changes | Verify retry cap and toggle anti-shake. |
| Verify records | Test conditions, execution records, problem lists and regression results | Record the time when the network and services were restored respectively. |
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
Why is the business still offline even though the network has been restored?+
Services may still retain expired sessions, old DNS, or incomplete authentication. Network layer recovery and application session reconstruction need to be handled separately, and recovery must be successfully confirmed with business messages.
4G What information is required for the development of abnormal reconnection and multi-link switching?+
Please give priority to providing fault logs, network topology, module firmware, link priorities, switching conditions and business recovery goals. 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 needs to pay attention to: avoid treating all failures as a complete machine restart; the cause of the failure and recovery records must be retained for regression. Existing and new functions must undergo regression testing within the agreed scope after the changes.
Online
Phone
WeChat
Top