Products>ECP WAP>Tehnical Description
  ECP WAP - Tehnical Description

Conceptual Overview
WAP Push
WAP Pull
 

Conceptual Overview
The ECP Wap offers the capability for ECPs to deliver the WAP contents via a platform called EWIG. This platform acts as an intermediary between the end user, the ECP and Maxis backend systems for subscribers validation and billing.

The EWIG platform uses SOAP as the underlying communication protocol over the internet using the HTTP. The technical specifications will be provided to Content Providers upon signing of NDA. Refer to Getting Started.

EWIG will capture the necessary details to carry out delivery of WAP Push/Pull, charging as well as refund activities. EWIG allows two modes of delivery, ie :
 
 
WAP Push
This allows delivery of content request by Maxis subscribers via SMS.
 

Figure 1: EWIG Architecture for Requests via SMS (click for larger view)
 
  		• The user will request for rich content using an SMS MO that will be delivered to the content provider using the existing ECPA platform.
  		• Content provider will then deliver a WAP PUSH message to EWIG containing the details of the download
  		• Users will then initiate the download directly to the content provider’s system using the WAP PUSH
    WAP Pull
    This allows delivery of content request by Maxis subscribers via WAP.
     
    Figure 2: EWIG Architecture for Requests via WAP (click for larger view)
     
  		• The user will browse the content provider’s WAP catalogue over GPRS, CSD or 3G (when available) and will make a request to download a particular content.
  		• The content provider will then send an immediate charging request to EWIG, which will perform the necessary charging procedures and will send out an SMS charging notification to the user if the charging request is successful.
  		• The user will then be able to download the contents requested.