Release 4.16.0 - January 23, 2025

New features

New eSIM HUB

The BICS eSIM Hub is an optional module of the SIM for Things solution. Please contact your Account Manager for more information.
The BICS SIM for Things eSIM HUB is a new value-added service designed to enhance the SIM for Things Global SIM solution. This service aims to provide seamless management of eSIM profiles across multiple local operators and local SIM connectivity management platforms, all through a single invoice and a unified portal.

Functionalities:

• Access to local MNO networks via s single portal and API for managing both global roaming eUICC and local eSIM profile, simplifying the management process.

• EID (eUICC Identification) – the unique number to identify an eUICC which is used in the context of remote provisioning and management of eUICC.

• OTA (Over-The-Air) – a method of remotely managing and updating eUICCs. We support automatic updates over the air for targeted updates to specific eUICC cards that need to be localised.

• Endpoint view update:

  • we provide a near real-time visibility into the usage records for local profiles.

  • we add support to manage the localised eUICC card

  • new remote SIM provisioning parameters which include the history and state of the localisation operations (download, set fallback, enabled)

New APN group API – APN barring

In order to change the APN group via API we have added support via the following API’s. You can setup different APN groups on you account with different set’s of APN’s and when switching APN group on en endpoint, you can bar/unbar the APN assigned to an Endpoint.

• New API to fetch the APN group APN group - GET: https://sft.bics.com/api/fetchApnGroup

• The existing Modify Endpoint API will be updated to include the possibility of modifying the PDP Profile of the concerned endpoint. Endpoint - Modify: https://sft.bics.com/api/endpoint

• The existing bulk Modify Endpoint API , in order to give the user with the means to do a bulk modification of the PDP Profile for multiple endpoints. Endpoint – Bulk Modify: https://sft.bics.com/api/endpointbulk

New get User API

As a User of SFT portal at all level , I want to fetch the user information of my accounts and the direct accounts below me in order TO get their email address

• An API that can provide all the users under a specific accounts to get own user info via the getAccountUsers API.

Enhancements

SMS API enhancement – A2P SMS with alphanumeric Source Address

To Enrich the A2P SMS  such that Enterprise can set alphanumeric sender ID and platform will accept the API and SMSC will deliver the message to endpoint under this enterprise with same sender ID visible in endpoint end device/handset.

• The existing A2P API will be updated to include Alphanumeric values for the sourceAddr. The Alphanumeric values shouldn't exceed more than 12 characters in length.

Tariff page in-table changes

On the Tariff page, the “price per unit” will be editable in the table without moving to a new screen 

• We also added a new ModifyTariffPrice API to only change the tariff price.

Addon counter – throttling

Add an new “counter” to addon plans for throtteling data. The new Addon plan counter is specifically applicable to Endpoint Addon plans and includes only Throttle options.

• Throttling options: 128Kbps, 256Kpbs, 384Kpbs, 512Kpbs, 1250Kpbs, 1Mbps, 2Mbps, 5Mbps, 10Mbps, 20Mbps

• The Addon Counter is applicable only on Endpoint Addons.

• The Addon Counter has only Throttle options and does not include BLOCK options.

• The counters in the addon behave the same as the counter in the base plan for all services such as DATA, NBIOT, and LTEM.

• Multiple addons can be attached to an endpoint with multiple counters (one counter per service allowed).

• On every addon renewal, the respective counter will also be reset.

• On every reset of the counter, the counter threshold will be reset with the master plan counter configuration.

• The addon counter threshold can be modified from the endpoint CRM, which will be reset in the next counter reset.

• Any modification on the Plan counter will reflect on the endpoint/customer in the next reset. This applies to both the base plan and addon counter.

• The plan addon counter cannot be deleted if it is attached to any of the endpoints, similar to the base plan counter.

For API related changes and bug fixes you can check the API documentation and release notes here: https://api.sft.bics.com