Tuesday, December 30, 2008

Basic introduction

Recently I came across a project which is developed for Campaigning Purpose.   The users were given three options for campaigning those are Text Messaging, Voice messaging and Emailing. For Text messaging the services Ericsson is used for United States, while the  esendex services used for United Kingdom. 

Here I will be giving a detailed way to register for service, implementing and using it successfully.
 Ericsson IPX 
Internet Payment eXchange (IPX) is a solution and technology for micro payments. IPX acts as a transparent, white-label Content Acquirer and Transaction Router between Operators and Content Providers. Content Providers are provided with an easily implemented interface to connect to IPX, which handles integration to the Operators. The Content Provider’s interface to IPX is independent of the Consumer’s device type (PC, mobile phone, PDA, etc.).

The IPX system provides the following basic functionality for short messaging:

  • Sending mobile terminated (MT) short messages, such as text or binary.(e.g. EMS) messages, premium and non-premium.
  • Receiving delivery reports for submitted MT messages.
  • Receiving mobile originated (MO) short messages, premium and nonpremium.

Steps involved in sending message
  1. The Content Provider makes a request to send an SM to the IPX system.
  2. IPX handles routing, charging (in case of premium message) and delivers the message to the addressed Consumer.
  3. A message ID is returned to the Content Provider synchronously. This ID can be used for tracing a certain message.

    Step 4 and 5 are executed if the Content Provider requested a delivery report in step 1.
     4.  A delivery report is triggered, e.g. when the message is delivered to the Consumer’s mobile station.
     5. The delivery report is sent to the Content Provider (the report contains the same message ID as returned in step 3.

Steps involved in receiving message
  1. The Consumer sends an SM to a short number.
  2. IPX transmits the SM to the Content Provider.
  3. The Content Provider acknowledges the SM.

IPX provides an API exposed as a web service with a SOAP interface. The SOAP protocol and the IPX server are independent of the platform used on the client side, although the installation of the SOAP tools could be different. The web service API is described in WSDL. For those not familiar with web services, IPX also provides a set of Java classes generated from the web service WSDL description. These classes can be used as an SDK and are provided by IPX upon request.
System requirements
The Content Provider needs the following:
  • Web server with a fixed domain name or IP address
  • SOAP Toolkit/SDK

No comments: