Communications Process Flow

Communication Requests are triggered

The Communications process starts when a communication request is triggered. A trigger can be:

Internal - for example a CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. workflow event, raised either manually or automatically

External - a request from an external system. A communication request can be created automatically on receipt of a notification from an external system.

When a trigger is invoked, CMP creates an entry in the core table in Communications, the Comms Request Header table.

Communication details are produced

When created in this table, the Comms Request Job will be triggered to process this comms request header and produce a comms request detail. This job will:

• Work out the appropriate delivery method and target e.g. mobile number, email address etc. There may be multiple targets in the senario where a comms is to be distributed to all subs on an account In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices..
• Work out the comms to send if a Comms Rule is involved
• Derive the values of the fields that are associated with the comms

• In the case of Push, online and sms it will also merge the data of the derived fields with the message template to produce the actual message. In the case of letters and email this merging will be carried out via a separate job.

Push Online and SMS Short Message Service. A text messaging service component of most mobile telephone systems. SMS uses standardized communication protocols to enable mobile phone devices to exchange short text messages. comms are distributed

After the Comms Request Job has completed, Daemons will then pick up the requests to distribute them to the destination e.g. mobile handset A mobile phone etc.

Letters and Emails are distributed