System and method of dynamic and scalable IoT framework

1. A method of providing one or more services to one or more user devices in an IoT network, the method comprising:

receiving, at a load balancer of the IoT network, a connection request from the one or more user devices, wherein

the IoT network comprises of one or more clusters, each of the one or more clusters is associated with a unique cluster identifier,

the connection request comprises at least a username, the username being a combination of at least a cluster identifier and a user device identifier,

the connection request is stateful request, and

the one or more user devices being associated with a cluster identifier assigned by an authentication server;

determining, by the load balancer, a cluster identifier based on the connection request; and

routing, by the load balancer, the connection request to at least one target cluster from the one or more clusters based on the determined cluster identifier to provide the one or more services to the one or more user devices.

2. The method as claimed in claim 1 , the method further comprising:

receiving, at the at least one target cluster, the connection request from the load balancer;

decrypting, by the at least one target cluster, a second connection request using a shared public key;

providing, by the at least one target cluster, the one or more services to the one or more user devices based on the decryption.

3. The method as claimed in claim 1 , further comprising:

receiving, at a load balancer of the IoT network, a first registration request from the one or more user devices prior to receiving the connection request, wherein the first registration request comprises at least a user device identifier;

routing, by the load balancer, the first registration request to a registration cluster based on the user device identifier;

assigning, by the registration cluster, the username and a password to the one or more user devices, wherein

the password is an encrypted combination of the user device identifier and the username; and

transmitting, by the registration cluster, the password and the username assigned to the one or more user devices.

4. The method as claimed in claim 3 , further comprising:

receiving, from the one or more user devices, an authentication request comprising the user device identifier prior to receiving the registration request at an Identity and Access Management System (IDAM);

validating, by a central authentication platform, a connection capability of the one or more user devices; and

assigning, by the central authentication platform, a token to the one or more user devices, said token being associated with a time period.

5. The method as claimed in claim 4 , wherein the first registration request received at the load balancer further comprises of the token.

6. The method as claimed in claim 4 , the method further comprising validating, by the registration cluster, the first registration request based on the token, wherein the username and the password is assigned to the one or more user devices based on the validation.

7. The method as claimed in claim 4 , wherein the one or more user devices request the central authentication platform, for a new token upon an expiration of the time period of the token.

8. A system for providing one or more services to one or more user devices in an IoT network, the system comprising:

a processor;

a memory storing instructions, which when executed by the processor, cause the system to:

provide the one or more services to the one or more user devices using one or more clusters, wherein each of the one or more clusters is associated with a unique cluster identifier; and

a load balancer connected to the one or more clusters, said load balancer being configured to:

receive a connection request from the one or more user devices, wherein

the connection request comprises at least a username, the username being a combination of at least a cluster identifier and a user device identifier,

the connection request is stateful request, and

the one or more user devices being associated with the cluster identifier assigned by an authentication server,

determine the cluster identifier based on the connection request, and

route the connection request to at least one target cluster from the one or more clusters based on the determined cluster identifier.

9. The system as claimed in claim 8 , wherein the processor is further configured to cause the system to:

receive the connection request from the load balancer;

decrypt a second connection request using a shared public key; and

provide the one or more services to the one or more user devices based on the decryption.

10. The system as claimed in claim 8 , wherein the load balancer is further configured to:

receive a first registration request from the one or more user devices prior to receiving the connection request, wherein the first registration request comprises at least a user device identifier; and

route the first registration request to a registration cluster based on the user device identifier.

11. The system as claimed in claim 10 , the system further comprising the registration cluster connected to the load balancer said registration cluster being configured to:

receive the first registration request from the load balancer;

assign the username and a password to the one or more user devices, wherein

the password is an encrypted combination of the user device identifier and the username; and

transmit the password and the username to the one or more user devices.

12. The system as claimed in 10 further comprising an Identity and Access Management System (IDAM) configured to receive, from the one or more user devices, an authentication request comprising the user device identifier prior to receiving the registration request.

13. The system as claimed in 12 further comprising a central authentication platform connected to the IDAM, said central authentication platform configured to:

validate a connection capability of the one or more user devices; and

assign a token to the one or more user devices, said token being associated with a time period.

14. The system as claimed in claim 13 , wherein the first registration request received at the load balancer further comprises the token.

15. The system as claimed in claim 13 , wherein the registration cluster is further configured to validate the first registration request based on the token, wherein the username and the password is assigned to the one or more user devices based on the validation.

16. The system as claimed in claim 13 , wherein the one or more user devices is configured to requests the central authentication platform for a new token upon an expiration of the time period of the token.