Sony Group Corporation

Sony Corporation

Sadayoshi Murao

Srinivasa Pingili

Madhvesh R Sulibhavi

Takashi Togame

Srinivas Pingili

Koichi A Ono

Prashant Seethalakshmi

An electronic device for secure onboarding of users and organizations on a mobility-as-a-service (MaaS) platform is disclosed. A set of onboarding agreements is received from nodes of a MaaS network. A set of service and agreement templates are generated to create a MaaS node group corresponding to the set of nodes. The set of onboarding agreements and the set of service and agreement templates are transmitted to the MaaS node group. An onboarding request is received from a first node of the MaaS network. A decentralized identity (DID) of the first node is verified. A set of parameters and a service agreement associated with the first node is transmitted to the first node. The service agreement is transmitted to the MaaS node group. An Application Programming Interface (API) key of a data hub is generated for the MaaS network to onboard the first node to the MaaS node group.

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

A system, including a plurality of node packages, an aggregator database node, and an archival database node, is provided. Each node package includes a subscriber node, an MP node, and a MaaS node. A first MaaS node selects a first set of transaction records from the first MaaS node based on a first data retention threshold and a first storage duration, and transmits the first set of transaction records to the aggregator database node for storage. The first MaaS node further controls a selection of a second set of transaction records from a third set of transaction records stored on the aggregator database node and controls a transmission of the second set of transaction records to the archival database node for storage. The selection of the second set of transaction records is based on a second data retention threshold and a second storage duration.

Common database architecture to support largescale transactions and node archival on a MaaS platform

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.

User interface-based mobility transaction management on a MaaS platform

A system and method for implementation of transaction security on a distributed ledger-based Mobility-as-a-Service (MaaS) platform is provided. The system includes a message broker device which receives a transaction request associated with a transport service from a publisher node of a transportation provider. The message broker device routes, via an API gateway hosted on the message broker device, the transaction request to a subscriber node of the transportation provider. The API gateway validates the transaction request based on application of a set of security rules on the transaction request. The subscriber node is associated with a first node of a distributed ledger node that stores a first state object. The first state object includes transaction data associated with the transport service. The distributed ledger node receives the validated first transaction request from the API gateway, via the subscriber node and updates the transaction data based on the received transaction request.

Transaction security on distributed-ledger based MaaS platform

A system for determination of a revenue share of a mobility player (MP) of a MaaS network is disclosed. An MP node of the MP is on-boarded to a node package of the MaaS network and gets associated with a MaaS node of the node package, based on an on-boarding process. The on-boarding process includes a definition of a service structure including configuration data of the MP and a signing off of the MP node to a service agreement and a privacy policy associated with the MaaS network based on terms of service of the service agreement. Once, the MP node is on-boarded to the node package, the MaaS node and/or one or more external nodes, such as, a plurality of aggregator nodes and a central MaaS node may determine a revenue share of the MP based on receipt of a trigger event associated with the node package.

Revenue share determination for transactions on MaaS platform with common database architecture

A hybrid authentication system, a method, and a non-transitory computer-readable medium for single-sign-on authentication is provided. The hybrid authentication system is communicatively coupled to a web application server and a public ledger. The hybrid authentication system receives a request from the web application server to access secure content on a resource server and controls display of a set of user-selectable options on a user interface of a user device based on the received request. The hybrid authentication system selects at least one authentication option from the displayed set of user-selectable options and authenticates the received request based on the selected at least one authentication option. The selection of the at least one authentication option is based on a user input over the displayed set of user-selectable options.

Single sign-on authentication via multiple authentication options

A system and method for transaction flow management is provided. The system comprises a broker node device which collects operation information associated with a plurality of nodes of a MaaS network and determines an operational trouble associated one or more nodes of the plurality of nodes based on the collected operation information. The one or more nodes handle ticket transactions associated with a first trip plan of a sequence of trip plans included in a MaaS mobility service. The broker node device selects a first message routing policy based on the determined operational trouble and receives, based on the first message routing policy, a transaction message associated with the first trip plan from a first node of the first plurality of nodes. The broker node device routes the received transaction message to a second node of a same or different MaaS network based on the first message routing policy.

Transaction flow management based on operational troubles on a MAAS platform

A system including a server and a first publisher node device is provided. The first publisher node device transmits a request including an authentication credential associated with the first publisher node device to the server and receives a response including authentication of the first publisher node device as a ticket processing client for a first transportation service. The first publisher node device captures, as the ticket processing client, an event associated with the first transportation service based on the received response and transmits, based on the captured event, a transaction request to a broker node device. The transaction request includes a transaction message and an authorization request to route the transaction message to a first subscriber node device of the MaaS network. The server receives the authorization request from the broker node device and authorizes the broker node device to route the transaction message based on the received authorization request.

Access management of publisher nodes for secure access to MaaS network

A system for node configuration management for a MaaS platform is provided. The system includes a central node device and a group of node devices associated with a publish-subscribe pattern. The group of node devices includes a first node device that updates routing information associated with the first node device locally. The routing information includes routing rules for propagation of transaction requests to or from the first node device. The central node device receives the updated routing information from the first node device and records the updated routing information in a central routing configuration repository of the central node device. Based on the record, the central node device transmits the updated routing information to the set of second node devices, each of which receives the updated routing information, validates the updated routing information, and records the updated routing information locally based on the validation.

Growing community of inventors

Bengaluru, India

Sadayoshi Murao