Secure onboarding of users and organizations on mobility-as-a-service (MaaS) platform

1. An electronic device, comprising:

circuitry configured to:

receive a set of onboarding agreements from a set of nodes of a mobility-as-a-service (MaaS) network, wherein

the set of nodes includes at least one of a first set of mobility provider nodes and a second set of MaaS player nodes;

generate a set of service and agreement templates based on the received set of onboarding agreements to create a MaaS node group corresponding to the set of nodes;

transmit the received set of onboarding agreements and the generated set of service and agreement templates to the created MaaS node group;

receive an onboarding request from a first node of the MaaS network;

verify a decentralized identity (DID) of the first node based on the received onboarding request;

transmit, to the first node, a set of parameters and a service agreement associated with the first node, based on the verified DID, transmitted set of onboarding agreements, and the set of service and agreement templates;

transmit the service agreement associated with the first node to the created MaaS node group; and

generate an Application Programming Interface (API) key of a data hub for the MaaS network, based on the DID of the first node and the transmitted service agreement, wherein

the first node is onboarded to the created MaaS node group of the MaaS network based on the generated API key and the transmitted service agreement associated with the first node.

2. The electronic device according to claim 1 , wherein the set of onboarding agreements corresponds to at least one of a master service agreement, a terms-of-service agreement, or a privacy policy agreement.

3. The electronic device according to claim 1 , wherein the MaaS network includes at least one of:

an issuer node associated with a credential issuing authority,

a set of holder nodes corresponding to the set of nodes,

a verifier node associated with a MaaS network owner, and

a distributed ledger database.

4. The electronic device according to claim 3 , wherein

each of the issuer node, the set of holder nodes, and the verifier node, is associated with the distributed ledger database, and

each of the issuer node, the set of holder nodes, and the verifier node includes a corresponding DID agent.

5. The electronic device according to claim 3 , wherein the issuer node generates credentials associated with each holder node of the set of holder nodes.

6. The electronic device according to claim 5 , wherein

the generated credentials correspond to a set of attributes including at least one of an organization name, an organization ID, a name and electronic-mail ID of an administrator user, a role of a user of a node, or a user privilege level associated with the user of the node.

7. The electronic device according to claim 3 , wherein the verifier node:

receives a credential verification request associated with the first node, based on the received onboarding request of the first node;

queries a holder node of the set of holder nodes for verified credentials of the first node, based on the received credential verification request; and

receives, from the holder node, the verified credentials of the first node, based on the query, wherein

the DID of the first node is verified based on the received verified credentials of the first node.

8. The electronic device according to claim 1 , wherein

the circuitry is further configured to create a user and a role for the user, associated with the first node in the MaaS network, and

the creation of the user and the role is based on the verified DID of the first node and a scheduler.

9. The electronic device according to claim 1 , wherein the circuitry is further configured to:

receive, from a first MaaS player node of the second set of MaaS player nodes, a first master service agreement (MSA) and counterparty details associated with the first MaaS player node, wherein

the counterparty details correspond to a first mobility provider node of the first set of mobility provider nodes;

transmit, to the first mobility provider node, the first MSA, based on received the counterparty details; and

receive, from the first mobility provider node, an input indicative of an acceptance of the transmitted first MSA, wherein

the first MSA is established between the first MaaS player node and the first mobility provider node, based on the received input indicative of the acceptance of the transmitted first MSA.

10. The electronic device according to claim 9 , wherein the circuitry is further configured to:

receive, from the first MaaS player node, a first service agreement associated with the first MaaS player node;

associate the received first service agreement with process service information and the first MSA, to determine an MSA bound service agreement;

transmit, to the first mobility provider node, the determined MSA bound service agreement; and

receive, from the first mobility provider node, an input indicative of an acceptance of the transmitted MSA bound service agreement, wherein

the first service agreement is established between the first MaaS player node and the first mobility provider node, based on the received input indicative of the acceptance of the transmitted MSA bound service agreement.

11. The electronic device according to claim 10 , wherein the circuitry is further configured to:

receive, from the first MaaS player node, a first terms-of-service (ToS) associated with the first MaaS player node;

associate the received first ToS with the first service agreement to determine a service agreement bound-ToS;

transmit, to the first mobility provider node, the determined service agreement bound-ToS; and

receive, from the first mobility provider node, an input indicative of an acceptance of the transmitted service agreement bound-ToS, wherein

the first ToS is established between the first MaaS player node and the first mobility provider node, based on the received input indicative of the acceptance of the transmitted service agreement bound-ToS.

12. The electronic device according to claim 11 , wherein the circuitry is further configured to:

receive, from the first MaaS player node, a second ToS associated with the first MaaS player node, wherein

the second ToS corresponds to a new version of the established first ToS;

transmit, to the first mobility provider node, the second ToS;

receive, from the first mobility provider node, an input indicative of an acceptance of the second ToS; and

disable the first ToS established between the first MaaS player node and the first mobility provider node, based on the received input indicative of the acceptance of the second ToS, wherein

the second ToS is established between the first MaaS player node and the first mobility provider node, based on the disablement of the first ToS.

13. A method, comprising:

in an electronic device:

receiving a set of onboarding agreements from a set of nodes of a mobility-as-a-service (MaaS) network, wherein

the set of nodes includes at least one of a first set of mobility provider nodes and a second set of MaaS player nodes;

generating a set of service and agreement templates based on the received set of onboarding agreements to create a MaaS node group corresponding to the set of nodes;

transmitting the received set of onboarding agreements and the generated set of service and agreement templates to the created MaaS node group;

receiving an onboarding request from a first node of the MaaS network;

verifying a decentralized identity (DID) of the first node based on the received onboarding request;

transmitting, to the first node, a set of parameters and a service agreement associated with the first node, based on the verified DID, transmitted set of onboarding agreements, and the set of service and agreement templates;

transmitting the service agreement associated with the first node to the created MaaS node group; and

generating an Application Programming Interface (API) key of a data hub for the MaaS network, based on the DID of the first node and the transmitted service agreement, wherein

the first node is onboarded to the created MaaS node group of the MaaS network based on the generated API key and the transmitted service agreement associated with the first node.

14. The method according to claim 13 , wherein the set of onboarding agreements corresponds to at least one of a master service agreement, a terms-of-service agreement, or a privacy policy agreement.

15. The method according to claim 13 , wherein the MaaS network includes at least one of:

an issuer node associated with a credential issuing authority,

a set of holder nodes corresponding to the set of nodes,

a verifier node associated with a MaaS network owner, and

a distributed ledger database.

16. The method according to claim 15 , wherein

each of the issuer node, the set of holder nodes, and the verifier node is associated with the distributed ledger database and

each of the issuer node, the set of holder nodes, and the verifier node includes a corresponding DID agent.

17. The method according to claim 15 , wherein

the issuer node generates credentials associated with each holder node of the set of holder nodes, and

the generated credentials correspond to a set of attributes including at least one of an organization name, an organization ID, a name and electronic-mail ID of an administrator user, a role of a user of a node, or a user privilege level associated with the user of the node.

18. The method according to claim 15 , wherein the verifier node:

receives a credential verification request associated with the first node, based on the received onboarding request of the first node;

queries a holder node of the set of holder nodes for verified credentials of the first node, based on the received credential verification request; and

receives, from the holder node, the verified credentials of the first node, based on the query, wherein

the DID of the first node is verified based on the received verified credentials of the first node.

19. The method according to claim 13 , further comprising

creating a user and a role for the user, associated with the first node in the MaaS network, wherein

the creation of the user and the role is based on the verified DID of the first node and a scheduler.

20. A non-transitory computer-readable medium having stored thereon, computer-executable instructions that when executed by an electronic device, causes the electronic device to execute operations, the operations comprising:

receiving a set of onboarding agreements from a set of nodes of a mobility-as-a-service (MaaS) network, wherein

the set of nodes includes at least one of a first set of mobility provider nodes and a second set of MaaS player nodes;

generating a set of service and agreement templates based on the received set of onboarding agreements to create a MaaS node group corresponding to the set of nodes;

transmitting the received set of onboarding agreements and the generated set of service and agreement templates to the created MaaS node group;

receiving an onboarding request from a first node of the MaaS network;

verifying a decentralized identity (DID) of the first node based on the received onboarding request;

transmitting, to the first node, a set of parameters and a service agreement associated with the first node, based on the verified DID, transmitted set of onboarding agreements, and the set of service and agreement templates;

transmitting the service agreement associated with the first node to the created MaaS node group; and

generating an Application Programming Interface (API) key of a data hub for the MaaS network, based on the DID of the first node and the transmitted service agreement, wherein

the first node is onboarded to the created MaaS node group of the MaaS network based on the generated API key and the transmitted service agreement associated with the first node.