My device creates dual sessions, how will the quota allocation work with my device?

My device creates dual sessions, how will the quota allocation work with my device?

When a device requests two simultaneous sessions from the CityKinect platform, then the platform allows two distinct sessions and reserves 5MB of quota for each session. While the platform reserves 5MB of data, it also has to deduct this from the balance/monthly limit of the endpoint for accurate rating/charging.

5MB * 2 = 10MB Reserved

This reserved volume of data is already deducted from the available monthly limit. If one of the sessions exhausts its allocated 5MB data and requests an additional 5MB of data then the CityKinect platform will allocate based on the remaining monthly limit, if the monthly limit is reached it will refuse and give a low balance notification. Though the 2nd session will still have its 5MB allocated volume of data not fully exhausted.

NONE

  1. Monthly Data Limit/Balance - 10MB

  2. First Data session - 5MB reserved

  3. Second Datasession - 5MB reserved

  4. ....

  5. First Data Session - 5MB consumed - Re-request for reservation

  6. Session Data session - 0MB consumed - 5MB reserved


  8. Low Balance as 0MB of balance remaining

Now the second 5MB is in the hands of the device and it’s the device only who can decide to consume data or end the session and release the reservation. If the device consumes the second 5MB, the platform doesn’t have to do anything as it has already deducted that from the monthly limit/balance, but if the device decides to release the session and return back some of the unused reservation (for example it uses 2 MB and returns 3MB), the platform will increase the already deducted monthly limit/balance by 3MB, and this 3MB will become available for the endpoint to use in additional sessions. If any additional sessions is requested for the endpoint then 3MB can still be allocated to that session before a low balance notification is given.
Thus, consumption or return of the second session’s 5MB is in hands of the device and only device can decide what to do with it.
The session can also be closed by the platform based on session timers but usually these timers are quite long (e.g. 30 mins to 24 hours).

    • Related Articles

    • Device Requirements and Recommendations

      How to ensure proper device interworking with a Multi-IMSI SIM solution? Device should have a 3 minute minimum active period: IMSI rotation may fail if this isn’t ensured. Sleep mode (or disabling modem) in between will disrupt the IMSI rotation ...

    • What are the different SIM states and how does SIM life-cycle work?

      In the Citykinect platform an endpoint represents a real world customer device What is an endpoint and why do I need to create one? , a SIM is used as a connectivity module for this endpoint and can be linked or de-linked from an endpoint as per the ...

    • SIM for Things Glossary

      An alphabetical list of all the terms and abbreviations used in the Citykinect platform with a concise definition of those terms. A-D Name Definition AAA Authentication, authorization, and accounting Account Account is primary representation of a ...

    • What is an endpoint and why do I need to create one?

      An endpoint in the SIM for Things platform represents an actual physical IoT device of the customer. Whereas the SIM card is just a connectivity module linked to it. A SIM card can be swapped / linked / de-linked from an endpoint but all the ...

    • What is the SIM-Swap operation and where has my old SIM gone?

      The operation SIM-Swap allows a user to link a new SIM card in Ready to Activate state to an existing endpoint which already has a SIM linked to it. The operation replaces the ‘old’ SIM with a ‘new’ SIM but keeps all the existing properties of the ...