# US 2022/0044180 A1 · User interface-based mobility transaction management on a maas platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0044180 A1
- Document ID: US20220044180A1
- Status: Published application
- Kind: A1
- Application number: 16/987,890
- Filed: 2020-08-07
- Published: 2022-02-10
- Earliest claimed: 2020-08-07
- Assignees: Sony Corporation
- Applicants: Sony Corporation
- Inventors: SADAYOSHI MURAO; MADHVESH SULIBHAVI; SRINIVASA PINGILI
- Web page: https://patentgrep.com/patent/US20220044180A1

## CPC

- G06Q 50/40: Business processes related to the transportation industry (shipping G06Q10/083)
- G06F 11/006: {Identification (G06F11/2289 takes precedence)}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06N 5/04: Inference or reasoning models
- G06N 20/00: Machine learning
- G06Q 10/06375: {Prediction of business process outcome or impact based on a proposed change}
- G06Q 20/045: {using payment protocols involving tickets}
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 51/046: Interoperability with other network applications or services
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/102: {Entity profiles}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- G06F 2201/87: Monitoring of transactions
- G06Q 20/202: {Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR}
- G06Q 30/0185: {Product, service or business identity fraud}
- H04L 41/147: for predicting network behaviour
- H04L 41/16: using machine learning or artificial intelligence
- H04L 43/045: for graphical visualisation of monitoring data
- H04L 51/214: using selective forwarding
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system including broker node device is provided. The broker node device collects operation information associated with first plurality of nodes of first MaaS network. The broker node device determines operational trouble associated with the first plurality of nodes, based on the operation information and receives, from first publisher node of the first plurality of nodes, first transaction message associated with first transaction of first transportation service of the first MaaS network. The first transaction message includes first correlation identifier generated by first publisher node. The broker node device receives, from second node of the first plurality of nodes, first notification associated with receipt of first transaction message at second node. The broker node device determines cause for failure of first transaction based on the first correlation identifier, the first notification, or the operational trouble, and further controls display device to display the cause for failure.

## Claims

### Claim 1

A system, comprising:
a broker node device configured to:
collect operation information associated with a first plurality of nodes of a first Mobility-as-a-Service (MaaS) network;
determine an operational trouble associated with one or more nodes of the first plurality of nodes of the first MaaS network, based on the collected operation information;
receive, from a first publisher node of the first plurality of nodes of the first MaaS network, a first transaction message which is associated with a first transaction of a first transportation service of the first MaaS network,
wherein the first transaction message includes a first correlation identifier (ID) generated by the first publisher node based on a generation of the first transaction message;
receive, from a second node of the first plurality of nodes of the first MaaS network, a first notification associated with a receipt of the first transaction message at the second node, wherein the first notification includes the first correlation ID;
determine a cause for failure of the first transaction based on at least one of the first correlation ID in the first transaction message, the received first notification, or the determined operational trouble; and
control a display device to display the determined cause for failure of the first transaction.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to:
receive routing information associated with each of the first plurality of nodes of the MaaS network from a central routing configuration repository; and
determine the cause for failure of the first transaction based on the routing information, and the at least one of the first correlation ID in the first transaction message, the received first notification, and the determined operational trouble.

### Claim 3 (depends on 1)

The system according to claim 1, further comprising a first server, wherein the broker node device is further configured to:
receive the first transaction message from the first publisher node;
transmit, to the first server, an authorization request associated with the received first transaction message, wherein the first server is associated with the broker node device and the first publisher node; and
receive, from the first server, an authorization to route the first transaction message to a first subscriber node of the first plurality of nodes of the first MaaS network, based on the transmitted authorization request.

### Claim 4 (depends on 3)

The system according to claim 3, wherein the authorization request comprises a first device profile and an authentication credential, associated with the first publisher node.

### Claim 5 (depends on 4)

The system according to claim 4, wherein the broker node device is further configured to transmit the first transaction message to the first server along with the first device profile and the authentication credential in the authorization request, and wherein the first server is further configured to:
authenticate the first transaction message as a valid message based on the first device profile; and
authorize the broker node device further based on the authenticated transaction message.

### Claim 6 (depends on 1)

The system according to claim 1, wherein the determined cause for failure of the first transaction comprises at least one of:
the operational trouble associated with the broker node device,
an operational trouble associated with a first server, wherein the first server is associated with the first publisher node and the broker node device,
an authentication error associated with the first publisher node,
an authentication error associated with the first transaction message,
an authorization error associated with the broker node device for the first transaction message,
the operational trouble associated with a first subscriber node from a plurality of subscriber nodes,
the operational trouble of the first publisher node,
the operational trouble of the one or more nodes due to an accident of a vehicle associated with the first transportation service or a delay in arrival for a pickup or drop by the vehicle of the first transportation service,
a natural calamity,
a disaster, or
a traffic disruption.

### Claim 7 (depends on 1)

The system according to claim 1, wherein the collected operation information includes at least one of a network connectivity status or a device operational status associated with each of the first plurality of nodes of the first MaaS network.

### Claim 8 (depends on 1)

The system according to claim 1, wherein the determined operational trouble of the one or more nodes of the first MaaS network comprises at least one of:
a network connectivity failure associated with the one or more nodes,
an operational failure of the one or more nodes,
an application error on the one or more nodes,
an overload of a message handling capacity of the one or more nodes, or
an inability of the one or more nodes to process ticket transactions due to unavailability of a vehicle at a planned trip time or a delayed arrival of the vehicle for a pickup or drop in comparison to the planned trip time.

### Claim 9 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to control the display device to display at least one of routing information, the operation information, the operational trouble, identification information of the first publisher node, identification information of the one or more nodes, the first correlation ID, master configuration information associated with the first MaaS network, telemetry information associated with transactions of the the first MaaS network, or transaction statuses associated with one or more routes of the first MaaS network.

### Claim 10 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to:
receive, via a user interface (UI) associated with the display device, an input associated with routing information which is further associated with each of the first plurality of nodes of the MaaS network;
update the routing information based on the received input; and
transmit, to a central routing configuration repository, the updated routing information.

### Claim 11 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to:
receive, via a user interface (UI) associated with the display device, an input associated with a selection of a backup node or an alternate node for an operationally troubled node from the one or more nodes; and
initiate, via a node management device associated with the broker node device, the selection of the backup node or the alternate node for the operationally troubled node based on the received input.

### Claim 12 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to control the display device to display a notification about the determined cause for failure of the first transaction.

### Claim 13 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to:
receive, via a user interface (UI) associated with the display device, an input to view transaction failure information associated with the one or more nodes of the first MaaS network; and
control, the display device, to display the transaction failure information associated with the one or more nodes of the first MaaS network.

### Claim 14 (depends on 1)

The system according to claim 1, wherein the broker node device is further configured to:
determine the cause for failure for each of a plurality of transactions associated with the one or more nodes of the first MaaS network; and
control the display device to display the determined cause for failure for each of the plurality of transactions associated with the one or more nodes.

### Claim 15 (depends on 14)

The system according to claim 14, wherein the broker node device is further configured to:
determine a recovery time associated with an operationally troubled node of the one or more nodes, based on the determined cause for failure for each of the plurality of transactions associated with the one or more nodes; and
control the display device to display the recovery time associated with the operationally troubled node from the one or more nodes.

### Claim 16 (depends on 1)

The system according to claim 1, further comprising an Artificial Intelligence (Al) engine associated with the broker node device, wherein the AI engine is configured to:
determine a recommendation associated with a rectification of the failure of the first transaction; and
control the display device to display the determined recommendation.

### Claim 17 (depends on 16)

The system according to claim 16, wherein the AI engine is further configured to:
determine a predicted future impact on an operation of the first MaaS network based on the determined operational trouble and the determined cause for failure of the first transaction; and
control the display device to display the determined predicted future impact.

### Claim 18

A method, comprising:
in a system including a broker node device:
collecting operation information associated with a first plurality of nodes of a first Mobility-as-a-Service (MaaS) network;
determining operational trouble associated with one or more nodes of the first plurality of nodes of the first MaaS network, based on the collected operation information;
receiving, from a first publisher node of the first plurality of nodes of the first MaaS network, a first transaction message which is associated with a first transaction of a first transportation service of the first MaaS network,
wherein the first transaction message includes a first correlation identifier (ID) generated by the first publisher node based on a generation of the first transaction message;
receiving, from a second node of the first plurality of nodes of the first MaaS network, a first notification associated with a receipt of the first transaction message at the second node, wherein the first notification includes the first correlation ID;
determining a cause for failure of the first transaction based on at least one of the first correlation ID in the first transaction message, the received first notification, or the determined operational trouble; and
controlling a display device to display the determined cause for failure of the first transaction.

### Claim 19 (depends on 18)

The method according to claim 18, further comprising:
receiving, via a user interface (UI) associated with the display device, an input associated with routing information which is further associated with each of the first plurality of nodes of the MaaS network;
updating the routing information based on the received input; and
transmitting, to a central routing configuration repository, the updated routing information.

### Claim 20

A non-transitory computer-readable medium having stored thereon, computer-executable instructions that when executed by a system including a broker node device, causes the system to execute operations, the operations comprising:
collecting operation information associated with a first plurality of nodes of a first Mobility-as-a-Service (MaaS) network;
determining an operational trouble associated with one or more nodes of the first plurality of nodes of the first MaaS network, based on the collected operation information;
receiving, from a first publisher node of the first plurality of nodes of the first MaaS network, a first transaction message which is associated with a first transaction of a first transportation service of the first MaaS network,
wherein the first transaction message includes a first correlation identifier (ID) generated by the first publisher node based on a generation of the first transaction message;
receiving, from a second node of the first plurality of nodes of the first MaaS network, a first notification associated with a receipt of the first transaction message at the second node, wherein the first notification includes the first correlation ID;
determining a cause for failure of the first transaction based on at least one of the first correlation ID in the first transaction message, the received first notification, or the determined operational trouble; and
controlling a display device to display the determined cause for failure of the first transaction.
