R13 Requirements Task Trace

Simulator

1. Be able to simulate analyzers and related interfaces that meet product line requirements.

2. Construct a proper body to send messages to the CCSDK.

blocked

CCSDK

1. The CCSDK/sli/plugins/ registers a listener for the Simulator and pushes events to the eventQueue so that the CCSDK can interact with the Simulator through rest call.

Incident management

1. SDNC/Northbound defines the request enumeration, compresses it into a JAR package, and re-edits it.

2. The SDNC/oam/modeling invokes the re-edited DG interface to write controller information (such as ID) to the AAI.

3. The SDNC/oam/platform-logic writes information into the diagnose logic, collects information from the simulator for root cause analysis, converts the information into events, and reports the events. Provides interfaces for querying, confirming, diagnosing, and rectifying incidents.

blocked

UUI Portal

1. Analyzers can be managed based on information such as the IP address and port number, and managed analyzers are displayed.

2. Subscribes to event notifications for a specified analyzer.

3. The incident status can be displayed, and the confirmation, diagnosis, and repair buttons are provided.

UUI：IAS

1. Be able to accept incidents from the DCAE.

DCAE

1. Design the incident structure to support receiving incidents from the SDNC.

2. Event events can be released to the message bus.

Policy

1. Write the resolve logic to provide a solution based on the diagnose analysis result and report the solution as an incident.

2. The SO interface can be invoked for network management based on the resolve result.

SO

1. Supports network orchestration based on policy instructions.