...
This section describes the purpose of the default batch and realtime real-time workflow configurations that are available in Routing Control.
The workflow configurations are intended as a baseline for implementation projects and can be adapted to meet specific customer requirements. For this reason, the description of the workflow configurations described in this document may deviate from your implementation. The default workflow configurations are designed for routing of Diameter messages but can be configured to handle other protocols, for example, Radius.
Front-End Workflow and Back-End Windows
...
The rationale behind separating the processing into two different workflow configurations is that it may enhance performance. When all use cases are executed in the front - end, rare but complex use cases may have a significant negative impact on the throughput. By offloading these use cases to the back - end, the overall throughput can be optimized. It is also possible to perform internal load balancing by executing multiple Back-End Workflows.
...
In case of errors when processing UDRs, a log UDR is stored before a response to the source network element. The location and content of the stored Error Log UDR is are implementation specific.
The default log UDRs contain the following fields:
| Field | Description |
|---|---|
timestamp | Time The time when the error was generated. |
subsKey | The subscriber id, IMSI or E164, if available. |
errorMessage | An error message defined in RC_APL_Constants. This is an APL code file imported by workflow configurations. |
There a are two workflow configurations for handling Error Log UDRs. The configuration, named RC_WFL_IWF_Error, collects Error Log UDRs from the Front-End Workflow in realtimereal-time. The UDRs are encoded and forwarded, via an Inter Workflow agent to a batch workflow named RC_WFL_Error_To_Disk that will send the UDRs to a local disk.
...
The Front-End Workflow and the Back-End Workflow configurations calculates calculate a number of KPIs and store these in UDRs on disk. The location and content of the stored KPI UDRs is are implementation specific.
There a are two workflow configurations that enable SLA Monitoring. The configuration, named RC_WFL_IWF_KPI, collects KPI UDRs from the Front-End Workflow in realtimereal-time.
The UDRs are encoded and forwarded, via an Inter Workflow agent to a batch workflow named RC_WFL_KPI_To_Disk that will send the UDRs to a local disk.
...
| Field | Description |
|---|---|
key | The subscriber id, IMSI or E164, if available. |
resultcode | An error code defined in RC_APL_Constants. This is an APL code file imported by workflow configurations. |
latency | The response time to the source. |
time | The timestamp of the incoming UDR. |
Batch Provisioning Workflows
The workflow RC_WFL_Provisioning_Import reads UDRs from file files and provisions the data using APL functions.
...
This section describes the default the preconfigured functions and use uses cases that are included in the default workflow configurations and which enable users to control routing of Diameter messages, through the Web GUI. Changes in the workflow configurations are typically required in order to introduce new uses use cases or when adding or changing communication endpoints, data formats, and protocols.
Routing Types
...