Access management of publisher nodes for secure access to MaaS network

1. A system, comprising:

a server; and

a publisher node device communicatively coupled to the server via a communication network, wherein the publisher node device is configured to:

transmit a request comprising an authentication credential associated with the publisher node device to the server;

receive a response to the transmitted request from the server, the response comprising authentication of the publisher node device as a ticket processing client for a transportation service;

capture, as the ticket processing client, an event associated with the transportation service based on the received response, wherein the event associated with the transportation service includes at least one of an issuance of an electronic ticket for the transportation service, recharge of the electronic ticket for the transportation service, or scan of the electronic ticket for the transportation service; and

transmit, based on the captured event, a transaction request to a broker node device of a Mobility-as-a-Service (MaaS) network associated with a publish-subscribe pattern, the transaction request comprising a transaction message and an authorization request to route the transaction message to a subscriber node device of the MaaS network, wherein the authorization request includes a first device profile associated with the publisher node device and the authentication credential associated with the publisher node device,

wherein the server is configured to:

receive the authorization request from the broker node device;

compare the received first device profile associated with the publisher node device with one or more profiles of valid transportation providers;

compare the received authentication credential associated with the publisher node device with a stored authentication credentials; and

authorize the broker node device to route the transaction message based on a result of the comparison of the received first device profile associated with the publisher node device with the one or more profiles of valid transportation providers and the comparison of the received authorization credential associated with the publisher node device with the stored authentication credentials.

2. The system according to claim 1 , wherein the server is further configured to:

receive, from the publisher node device, the request comprising the authentication credential associated with the publisher node device;

authenticate the publisher node device based on the authentication credential associated with the publisher node device; and

transmit, to the publisher node device, the response for the received request based on the authentication of the publisher node device.

3. The system according to claim 1 , wherein the broker node device is further configured to transmit the transaction message to the server along with the first device profile and the authentication credential in the authorization request, wherein

the server is further configured to:

authenticate the transaction message as a valid message from the publisher node device based on the first device profile; and

authorize the broker node device further based on the validation of transaction message.

4. The system according to claim 1 , wherein the first device profile comprises at least one of a company name, a company identifier (ID), a station name, a station ID, a gate name, a gate ID, a geography, a region, or an address associated with the publisher node device.

5. The system according to claim 1 , wherein the authentication credential comprises at least one of a device identifier (ID), a network ID, or a client certificate associated with the publisher node device.

6. The system according to claim 1 , wherein the publisher node device is further configured to:

receive a user input comprising a selection of an authentication option as one of a network-based authentication option or a certificate-based authentication option; and

select the authentication credential based on the selected authentication option in the received user input.

7. The system according to claim 1 , wherein the publisher node device is further configured to:

read the electronic ticket issued to a user for the transportation service; and

capture the event based on the reading of the electronic ticket.

8. The system according to claim 1 , wherein the publisher node device is associated with a node management device for a first transportation provider of the transportation service.

9. The system according to claim 8 , wherein the node management device is configured to:

transfer a second device profile associated with a second transportation provider to the publisher node device;

replace, on the publisher node device, a first device profile associated with the first transportation provider with the transferred second device profile; and

operationalize the publisher node device as the ticket processing client associated with the second transportation provider based on the replacement.

10. The system according to claim 8 , wherein the node management device is configured to:

detect an operational failure associated with at least one of an authentication failure of the publisher node device, a network failure of the publisher node device, a power failure of the publisher node device, or a fault caused by a malfunctioning component associated with the publisher node device; and

determine an operational state of the publisher node device as an inactive state based on the detection.

11. The system according to claim 10 , wherein the node management device is further configured to:

transfer the authentication credential and a first device profile associated with the publisher node device to a backup publisher node device based on a determination that determined operational state is the inactive state; and

operationalize the backup publisher node device as a replacement for the publisher node device based on the transferred first device profile and the transferred authentication credential.

12. The system according to claim 1 , wherein the subscriber node device is configured to:

receive the transaction message from the broker node device; and

share the received transaction message with a first node of a distributed ledger of the MaaS network, wherein the subscriber node device is associated with the first node of the distributed ledger.

13. The system according to claim 12 , wherein the first node of the distributed ledger is configured to:

receive the shared transaction message; and

execute a transaction associated with the transportation service based on information associated with the captured event in the received transaction message.

14. The system according to claim 1 , wherein the publisher node device is associated with a plug-in module configured to convert the transaction message from a message format associated with the publisher node device to a message format associated with the MaaS network.

15. The system according to claim 1 , wherein the subscriber node device is associated with a node management device, the node management device is configured to:

detect an operational failure associated with at least one of a network failure of the subscriber node device, a power failure of the subscriber node device, or a fault caused by a malfunctioning component associated with the subscriber node device; and

determine an operational state of the subscriber node device as an inactive state based on the detection.

16. The system according to claim 15 , wherein the node management device is further configured to:

operationalize a backup subscriber node device of a plurality of subscriber nodes of the MaaS network as a replacement for the subscriber node device in the inactive state; and

route, based on the operationalization, the received transaction message to the backup subscriber node device which temporarily stores the routed transaction message.

17. The system according to claim 16 , wherein the node management device is further configured to:

initialize a recovery of the subscriber node device; and

instruct, after the recovery is complete, the backup subscriber node device to reroute the stored transaction message to the subscriber node device.

18. A method, comprising:

transmitting, by a publisher node device, a request comprising an authentication credential associated with the publisher node device to a server, wherein the publisher node device is communicatively coupled to the server via a communication network;

receiving, by the publisher node device, a response to the transmitted request from the server, the response comprising authentication of the publisher node device as a ticket processing client for a transportation service;

capturing, by the publisher node device as the ticket processing client, an event associated with the transportation service based on the received response, wherein the event associated with the transportation service includes at least one of an issuance of an electronic ticket for the transportation service, recharge of the electronic ticket for the transportation service, or scan of the electronic ticket for the transportation service;

transmitting, by publisher node device, a transaction request to a broker node device of a Mobility-as-a-Service (MaaS) network associated with a publish-subscribe pattern, based on the captured event,

the transaction request comprising a transaction message and an authorization request to route the transaction message to a subscriber node device of the MaaS network, wherein the authorization request includes a device profile associated with the publisher node device and the authentication credential associated with the publisher node device;

receiving, by the server, the authorization request from the broker node device;

comparing, by the server, the received device profile associated with the publisher node device with one or more profiles of valid transportation providers;

comparing, by the server, the received authentication credential associated with the publisher node device with a stored authentication credentials; and

authorizing, by the server, the broker node device to route the transaction message based on a result of the comparison of the received device profile associated with the publisher node device with the one or more profiles of valid transportation providers and the comparison of the received authorization credential associated with the publisher node device with the stored authentication credentials.