Abstract: The present disclosure generally relates to providing extremely high read availability for data repositories within a telecommunication network. Systems described herein implement a novel architecture and backup scheme in connection with non-customized data servers to provide at least 99.99999% read availability within a telecommunication network. In one or more examples, the novel architecture includes a primary database and hot backup database that mirrors the primary database. Additionally, the novel architecture further includes a tepid backup database that stores asynchronous snapshot replications of the primary database that are sent to the tepid backup database out-of-band. In the event of a cascading failure that affects the primary database and the hot backup database, the best snapshot replication stored by the tepid backup database is initialized to service a read request that would otherwise have failed.

Abstract: The present disclosure generally relates to predicting and remediating fraudulent activity associated with a roaming SIM card. Systems described herein involve detecting potential fraud signals associated with a roaming SIM card and applying one or more machine learning models to those signals to generate a fraud prediction. In one or more examples, the potential fraud signals are detected in connection with one or more core network components of a 5G telecommunication network and provide unique insight into the network activities of a user equipment where the roaming SIM card is installed. As such, the systems described herein generate fraud predictions that take into account signals that are not necessarily indicative of fraud by themselves. Once fraud is predicted, the systems described herein execute various remediation actions to correct the fraudulent activities.

Abstract: The present disclosure generally relates to providing extremely high read availability for data repositories within a telecommunication network. Systems described herein implement a novel architecture and backup scheme in connection with non-customized data servers to provide at least 99.99999% read availability within a telecommunication network. In one or more examples, the novel architecture includes a primary database and hot backup database that mirrors the primary database. Additionally, the novel architecture further includes a tepid backup database that stores asynchronous snapshot replications of the primary database that are sent to the tepid backup database out-of-band. In the event of a cascading failure that affects the primary database and the hot backup database, the best snapshot replication stored by the tepid backup database is initialized to service a read request that would otherwise have failed.

Abstract: A method performed by a health service configured to update a domain name system (DNS) to enable clients, which use the DNS, to allocate service requests to a plurality of service instances which provide the service wherein each service instance comprises a microservice architecture is presented. The health service requests outcome data from at least one of the service instances, and calculates a status indicator for the service instance, wherein the status indicator is calculated based on results from internal recursive checks performed throughout the microservice architecture of the service instance and heuristic calculations performed on service request performance data. After calculating the status indicator, the health service triggers a dynamic update to the DNS according to the calculated status indicator.

Abstract: A method performed by a health service configured to update a domain name system (DNS) to enable clients, which use the DNS, to allocate service requests to a plurality of service instances which provide the service wherein each service instance comprises a microservice architecture is presented. The health service requests outcome data from at least one of the service instances, and calculates a status indicator for the service instance, wherein the status indicator is calculated based on results from internal recursive checks performed throughout the microservice architecture of the service instance and heuristic calculations performed on service request performance data. After calculating the status indicator, the health service triggers a dynamic update to the DNS according to the calculated status indicator.