{"id":7092,"date":"2025-02-14T16:07:55","date_gmt":"2025-02-14T05:07:55","guid":{"rendered":"https:\/\/nickvsnetworking.com\/?p=7092"},"modified":"2025-01-19T07:40:00","modified_gmt":"2025-01-18T20:40:00","slug":"basic-camel-charging-flow","status":"publish","type":"post","link":"https:\/\/nickvsnetworking.com\/basic-camel-charging-flow\/","title":{"rendered":"Basic CAMEL Charging Flow"},"content":{"rendered":"\n

CAMEL handles charging in 2G and 3G networks, much like Diameter handles charging in LTE.<\/a><\/p>\n\n\n\n

CAMEL runs on top of SS7<\/a>, specifically it sits on top of TCAP, which sits on top of SCCP, which can ride on M3UA or MTP3<\/a> (so it sits at the same layer as MAP).<\/p>\n\n\n\n

CAMEL is primarily focused on charging for Voice & SMS services, as data generally uses Diameter, so it’s voice and SMS we’ll focus on.<\/p>\n\n\n\n

CAMEL is spoken between the MSC (gsmSSF) and the OCS (gsmSCF).<\/p>\n\n\n\n

Basic Call State Model<\/h2>\n\n\n\n

CAMEL is closely related to the Intelligent Network stuff on the 1980s, and steals a lot of it’s ideas from there, unfortunately if you’re to read the CAMEL standard it also implies you were involved in IN stuff and had been born at that point, alas I was neither.<\/p>\n\n\n\n

So the key to understanding CAMEL is the Basic Call State Model (BCSM) which is a model of all the different states a call can be in, such as ringing, answered, abandoned, call failed, etc, etc.<\/p>\n\n\n\n

Over CAMEL, our OCS can be told by the MSC when a certain event happens; the MSC can tell the OCS, that the call has changed state. For example a BCSM event might indicate the call has hung up, is ringing, cancelled, etc.<\/p>\n\n\n\n

Below is the list of all the valid BCSM states:<\/p>\n\n\n\n

\"\"
List of BCSM states for events<\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Basic MO Call with CAMEL<\/h2>\n\n\n\n

Our subscriber makes an outbound call. <\/p>\n\n\n\n

Based on the data the MSC has in it from the HLR, it knows that we should use CAMEL for this call, and it has the SCCP Address of the OCS (gsmSCF)<\/a> it needs to send the CAMEL messages to.<\/p>\n\n\n\n

So the MSC sends an InitialDP<\/code> message to the OCS (via it’s Global Title Address) to Authorize the call that the user is trying to make.<\/p>\n\n\n\n

This is like any other Authorization step for an OCS, which allows the OCS to authorize the call by checking the subscriber is valid, check if they’re allowed to call that destination and they’ve got the balance to do so, etc.<\/p>\n\n\n\n

\"\"
initialDP message from an MSC to an OCS<\/figcaption><\/figure>\n\n\n\n

The initialDP<\/code> (Initial Detection Point) is telling our OCS all about the call event that’s being requested, who’s calling, what number they’ve dialed, where they are in the network (of note especially if they’re roaming<\/a>), etc, etc.<\/p>\n\n\n\n

The OCS runs through it’s own checks to see if it wants to allow the call to proceed by checking if the subscriber has got enough balance, unit reservation, etc, etc, <\/a>and if it does, the OCS sends back a Continue<\/code> message to the MSC to allow the call to continue.<\/p>\n\n\n\n

Generally the OCS also uses this message as a chance to subscribe to BCSM Events using RequestReportBCSMEventArg<\/code> so the OCS will get notified by the MSC when the state of the call changes. This means the MSC will tell us when the state of the call changes; events like the call getting answered, disconnected, etc. This is critical so we know when the call gets answered and hung-up, so we can charge correctly.<\/p>\n\n\n\n

In the below example, as well as sending the Continue<\/code> and RequestReportBCSMEventArg<\/code> the OCS is also setting the ChargingArgs<\/code> for this call, so the MSC knows who to charge (the caller) set via sendingSide<\/code> and that the MSC must send an Apply Charging Report<\/code> (ACR) messages every 300 units (1 unit = 100 ms, so a value of 300 = 300 x 100 milliseconds = 30 seconds) so the OCS keeps track of what’s going on.<\/p>\n\n\n\n

\"\"
continue<\/code> sent by the OCS to the MSC, also including reportBCSMEvent<\/code> and applyCharging<\/code> messages<\/figcaption><\/figure>\n\n\n\n

At this point the call can start to proceed – In ISUP terms the InitialDP<\/code> is triggered between the Initial Address Message and the Address Complete message is sent after the continue<\/code> is sent back<\/a>. <\/p>\n\n\n\n

Or in a slightly less appropriate analogy but easier to understand for SIP folks, the InitialDP is sent for INVITE and the 180 RINGING is sent once the continue<\/code> message is received. <\/p>\n\n\n\n

Call is Answered<\/h2>\n\n\n\n

So at this stage our call can start to ring.<\/p>\n\n\n\n

As we’ve subscribed to BCSM events in our last message, the MSC is going to tell us when the call gets answered or the call times out, is abandoned or the sun burns out.<\/p>\n\n\n\n

The MSC provides this info a eventReportBCSM<\/code>, which is very simple and just tells us the event that’s been triggered, in the example below, the call was answered.<\/p>\n\n\n\n

\"\"
eventReportBCSM<\/code> from MSC to OCS<\/figcaption><\/figure>\n\n\n\n

These eventReportBCSM<\/code> are informational from the MSC to the OCS, so the OCS doesn’t need to send anything back, but the OCS does need to mark the call as answered so it can start timing the call.<\/p>\n\n\n\n

At this stage, the call is connected and our two parties are talking, but our MSC has been told it needs to send us applyChargingReport<\/code>s every 30 seconds (due to the value of 300 in maxCallPeriodDuration<\/code>) after the call was connected, so the MSC sends the OCS it’s first applyChargingReport<\/code> 30 seconds after the call was answered:<\/p>\n\n\n\n

\"\"
applyChargingReport sent by the MSC to the OCS every reporting period<\/figcaption><\/figure>\n\n\n\n

We can calculate the duration of the call so far based on the time of the eventReportBCSM<\/code>, then the OCS must make a decision of if it should allow the call to continue or not.<\/p>\n\n\n\n

For simplicity’s sake, let’s imagine we’re still got a balance in the OCS and the OCS wants the call to continue, the OCS send back an applyCharging<\/code> message to the MSC in response, and includes the current allowed maxCallPeriodDuration<\/code>, keeping in mind the value is x100 and in nanoseconds (so this is 30 seconds).<\/p>\n\n\n\n

\"\"
applyCharging<\/code> from the OCS back to the MSC<\/figcaption><\/figure>\n\n\n\n

Perfect, our call is good to go for another 30 more seconds, son in 30 seconds we’ll get another ACR<\/code> messages from MSC to the OCS to keep it abreast of what’s going on.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Now one of two things is going to happen, either subscriber is going to burn through all of their minutes, and get their call cutoff, or the call will end while they’ve still got balance, let’s look at both scenarios.<\/p>\n\n\n\n

Normal Hangup Scenario<\/h2>\n\n\n\n

When the call ends, we get an applyChargingReport<\/code> from the MSC to the OCS.<\/p>\n\n\n\n

As we’ve subscribed to reportBCSMEvent<\/code> we get both the applyChargingReport<\/code> with legActive: <\/code>False` so we know the call has hungup, and we’ve got an event report to tell us more about the event, in this case a hangup from the Originating Side.<\/p>\n\n\n\n

\"\"
reportBCSMEvent<\/code> and applyChargingReport<\/code> Sent by the MSC to the OCS to indicate the call has ended, note the legActive<\/code> flag is now false<\/figcaption><\/figure>\n\n\n\n

Lastly the OCS confirms by sending a releaseCall<\/code> to the MSC, to indicate all legs should now terminate.<\/p>\n\n\n\n

\"\"
releaseCall<\/code> Sent by OCS to MSC at the very end<\/figcaption><\/figure>\n\n\n\n

So that’s it!<\/p>\n\n\n\n

Obviously there are other flows, such as running out of balance mid-call, rejecting a call, SMS and PBX \/ VPN services that rely on CAMEL, but hopefully you now understand the basics of how CAMEL based charging looks and works.<\/p>\n\n\n\n

If you’re looking for a CAMEL capable OCS or a CAMEL to Diameter or API gateway, get in touch!<\/p>\n","protected":false},"excerpt":{"rendered":"

A look at how CAMEL is used in Online Charging for 2G\/3G networks and while roaming<\/p>\n","protected":false},"author":1,"featured_media":7125,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[350,349,161,22],"tags":[689,524,346,682,523,601,544],"class_list":["post-7092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-gsm","category-plmn","category-notes","category-standards","tag-camel","tag-charging","tag-gsm","tag-map","tag-ocs","tag-roaming","tag-ss7"],"_links":{"self":[{"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/posts\/7092","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/comments?post=7092"}],"version-history":[{"count":8,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/posts\/7092\/revisions"}],"predecessor-version":[{"id":7445,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/posts\/7092\/revisions\/7445"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/media\/7125"}],"wp:attachment":[{"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/media?parent=7092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/categories?post=7092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nickvsnetworking.com\/wp-json\/wp\/v2\/tags?post=7092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}