Skip to content

[C4GT] Implement Beckn Mobility Sandbox Interface #55

@ravi-prakash-v

Description

@ravi-prakash-v

Project Details

Beckn protocol is a set of open specifications aimed to create a common language, that is machine-readable and enables interoperability for economic transactions between disparate platforms of any size and form - be it a cab reservation, or booking a stay, or confirming a doctor’s appointment, and many more. Thus it enables the creation of inclusive and equitable open networks offering a multitude of choices to the citizens, while at the same time negating the dependence on intermediaries to freely operate and generate economic transactions of value. It is akin to what SMTP is to E-mails or HTTP is to the Internet.

Since its inception in 2019 as a set of specifications, Beckn has been adopted across geographies in sectors such as mobility, retail, hyperlocal logistics, healthcare, skills, agriculture sectors, etc. Few notable examples of open networks built on the Beckn protocol are Open Network for Digital Commerce (ONDC), Namma Yatri at Bangalore, Kochi Open Mobility Network (KOMN), Unified Health Interface (UHI), etc.

The Beckn Mobility Interface is an API that emulates the behaviour of an Open Mobility Network. BAPs can build rich integrated experiences by combining services offered by multiple BPPs on the network. BPPs can build complex products by analyzing the nature of input from multiple BAPs. This is an important step in the set up and expansion of open networks. Businesses can test their implementations for protocol compliance by plugging into this sandbox.

Features to be implemented

  • Beckn-protocol compliant catalogs across multiple mobility services like ride hailing, rental, public transit etc.
  • BPP endpoints : search, select, init, confirm, status, update, track, cancel, rating, support
  • BAP endpoint : on_search, on_select, on_init, on_confirm, on_status, on_update, on_track, on_cancel, on_rating, on_support
  • BG endpoint : search
  • Registry endpoints : lookup

What exists

What needs to be built

  • A fully functioning scalable mobility sandbox compliant to beckn protocol specifications

Learning Path

Complexity

Medium

Skills Required

  • Open API 3.0
  • JSON Schema
  • NodeJS
  • JavaScript
  • TypeScript
  • MongoDB

Name of Mentors:

Product Understanding

Protocol Specification Design

Project Setup and Guidance

Product Setup

Product Architecture

Frontend Development

Backend Development

Deployment and Devops

Testing and QA

Project size

8 Weeks

Project Setup Guide

To set up this project, please connect with the Project Setup and Guidance mentor for this project and follow their instructions

Product Set Up

To set up this project, please connect with the Product Setup and Guidance mentor for this project and follow their instructions

Acceptance Criteria

  • End-to-end simulation of a ride hailing use case on a beckn mobility reference application
  • End-to-end simulation of a ride hailing use case on a Namma Yatri staging application
  • End-to-end simulation of a ride hailing use case on a Namma Yatri partner staging application
  • End-to-end simulation of a ride hailing use case on a beckn mobility driver reference application

Out of Scope

  • UI development, (however contributions to existing UI implementations are welcome)

Milestones

  • Understanding beckn protocol
  • Understanding beckn mobility protocol
  • Development of search / on_search API
  • Development of select / on_select API
  • Development of init / on_init API
  • Development of confirm / on_confirm API
  • Development of status / on_status API
  • Development of update / on_update API
  • Development of track / on_track API
  • Development of cancel / on_cancel API
  • Development of rating / on_rating API
  • Development of support / on_support API
  • Creation of Driver emulator

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions