Session billing scenarios (RBM)

Definitions

Single RBM Message – represents chargeable event; Mobile Terminated (MT) A2P message which was sent from Brand.

Session – is type of chargeable communication event, in which all messages that are being exchanged between End user and Brand are not being billed withing this session duration; usually lasts 24 hours.

Session message – type of message that was sent prior to MO message, which triggered 24 hour session, and it is included in session billing.

Mobile terminated (A2P) Session Scenarios

Scenario 1.

Brand sends message (MT 1) towards end-user, to which end-user responds with MO 1 and therefore triggering session billing. Session lasts 24 hours starting from response from end-user (MO 1). First message from brand (MT 1) is also included in session billing.

Scenario 2.

Brand sends message to which end-user never responded to. Message is being billed as single/basic.

Scenario 3.

Inside 24 time period, Brand has sent two messages. Each time brand sends a message, time period resets and starts again for next 24 hours. That means that MT1 will be billed as single message. Rest of the communication goes under scope of session (that lasts 24 hours).

Scenario 4.

Brand sent message (MT 1) to which enduser (MO 1) responded after 24 hours period. This MT1 message is being billed as single / basic. Response (MO 1) from the enduser, in this case, hasn’t triggered any session or any type of billing. This is only because MT 2, also occured after 24 hours of MO 1 message. So, after second MT2 message from Brand, Session procedure is same as in scenario 1.

Mobile originated (P2A) Session Scenarios

Scenario 5.

Here we have example of P2A communication, which means that the enduser initiated communication. In this situation 24 hour window session is starting with MOx message prior to A2P and all A2P messages from that point are being billed as Session (until the 24 hours window runs out).

Scenario 6.

In case of multiple MO messages, only the last MO message (in this case MO3), prior to MT1, will be start of 24 hour window session, and same logic applies as in Scenario 5.

MO1 – 9:00 – 24 window begins
MO2 – 10:00 – 24 hour window begins
MO3 - 11:00 - 24 hour window begins
MT1 - 24:00 - first message
MO4 - 9:00 next day
MT2 - 10:59:59 - 24 hour session ends

Scenario 7.

This scenario covers situation where there was no response to Brand message (MT 1) in 24 hour period. Even though Enduser responded (MO 1) after some point, this response was after first 24 hour session period, which means this is beginning of P2A session now.