Transforming Service Innovation with Deep Packet Inspection

• Triple-E partners with a leading provider to revolutionize its service offerings through DPI Solution Management.
• Deep Packet Inspection (DPI) is instrumental for telecom network providers in delivering innovative products and solutions for customers.

One of Indonesia’s largest network providers aimed to revolutionize its service and product offerings by customizing solutions based on customer behavior, location, and demographic segments. Their innovation involved working with digital platforms (or brands) to create differentiated service plans and personalized packages. To be able to roll out products and services that always evolve to adapt to customer requirements, they identified a need for a robust system.

Triple-E’s Solution and Lifecycle Management team partners with this enterprise to design, plan, customize, configure, test, and hence integrate the DPI system into our client’s Packet Core System. The challenge lay in configuring the Deep Packet Inspection (DPI) system within the Packet Core System – a task requiring speed, agility, and high configurability.

Triple-E Solution and Lifecycle Management is an end-to-end DPI Solution Management service. T his involved analyzing, configuring, testing, verifying, implementing, and rolling out deep packet inspection solutions in response to the client’s product team Change Requests (CR). Here’s how we executed our project in 6 phases:

1. Analyze : Ensuring that data and information required for Change Requests are complete and aligned with existing configurations, preventing potential conflicts.
2. Solution Configuration : This part is one of the key activities in DPI Solman, where intended CRs are translated into logical diagrams and system configurations, serving as the baseline for script creation.
3. Scripting & Test Bed Testing : Scripts are written based on the Solution Configuration. Once ready, it is then loaded and tested in the test bed to ensure that it is aligned with product objectives.
4. MOP Definition : Define and develop the Method of Procedure (MOP) after test bed testing, then modify the script to match each of the nodes for rollout.
5. Verification & Testing : Re-check the modified script to ensure alignment for all nodes and configurations, including necessary fallback procedures.
6. FNI Execution : Implement the MOP to the first node, then undergo monitoring period to ensure successful implementation without adverse impacts.
7. Rollout Implementation : After successful FNI, the rollout is intended to all remaining nodes, again followed by a monitoring period.
8. Final UAT and Acceptance : Document CR implementation for final User Acceptance Testing (UAT) and acceptance.