System and method for network slice admission control

A method for performing network slice admission control by a network slice admission control function (NSACF), the method comprising:

• maintaining data in a database, wherein the data comprises number of user equipment (UE) registration per slice per public land mobile network (PLMN), number of packet data unit (PDU) session per slice per PLMN, maximum number of UEs and PDU sessions supported per a single—network slice selection assistance information (S-NSSAI), an access management function (AMF) UE context, a session management function (SMF) UE context;
• maintaining frequently accessed or modified data from the database in a cache, wherein the cache is in sync with the database;
• deploying as a first NSACF entity and a second NSACF entity, wherein the first NSACF entity is an active entity and the second NSACF entity is a standby entity, wherein the standby entity is configured to remain in standby mode and fetch the cache served by the active entity;
• and
• in response to the first NSACF entity going down, initiate the second NSACF entity to function as the active entity and the first NSACF entity to function as the standby entity.

A system for performing network slice admission control, the system comprising a network slice admission control function (NSACF), the NSACF is configured to:

• maintain data in a database, wherein the data comprises number of user equipment (UE) registration per slice per public land mobile network (PLMN), number of packet data unit (PDU) session per slice per PLMN, maximum number of UEs and PDU sessions supported per a single network slice selection assistance information (S-NSSAI), an access management function (AMF) UE context, a session management function (SMF) UE context;
• maintain frequently accessed or modified data from the database in a cache, wherein the cache is in sync with the database;
• be deployed as a first NSACF entity and a second NSACF entity, wherein the first NSACF entity is an active entity and the second NSACF entity is a standby entity, wherein the standby entity is configured to remain in standby mode and fetch the cache served by the active entity;
• and
• in response to the first NSACF entity going down, initiate the second NSACF entity to function as the active entity and the first NSACF entity to function as the standby entity.

A user equipment (UE) attached to a network, the UE configured to:

• register with one of the plurality of slices associated with an access management function (AMF), wherein number of user equipment (UE) registration per slice per public land mobile network (PLMN) is maintained in a database by a network slice admission control function (NSACF);
• in responsive to registration with the slice associated with the AMF, perform a plurality of operations associated with services offered by the one of the plurality of slices;
• and
• in responsive to completion of operation, deregister with the slice associated with the AMF, wherein on determining that the UE registers or deregisters, the NSACF is configured to increment or decrement number of UE registration in the database, respectively.

A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for performing network slice admission control by a network slice admission control function (NSACF), the method comprising:

• maintaining data in a database, wherein the data comprises number of user equipment (UE) registration per slice per public land mobile network (PLMN), number of packet data unit (PDU) session per slice per PLMN, maximum number of UEs and PDU sessions supported per a single—network slice selection assistance information (S-NSSAI), an access management function (AMF) UE context, a session management function (SMF) UE context;
• maintaining frequently accessed or modified data from the database in a cache, wherein the cache is in sync with the database;
• deploying as a first entity and a second entity, wherein the first entity is an active entity, and the second entity is a standby entity, wherein the standby entity is configured to remain up and fetch the cache served by the active entity;
• and
• in response to the first entity going down, initiate the second entity to function as the active entity and the first entity to function as the standby entity.