Service Overview

AdvantEDGE provides a built-in V2X Information Service implementation that integrates with scenarios.

This feature provides the following capabilities:

• Predicting journey-specific QoS for vehicular UEs
• Obtaining V2X provisioning information
• Publishing and subscribing for V2X messages

Micro-Services

• V2X Information Service: Implements ETSI MEC030 northbound API with a custom integration with AdvantEDGE APIs

Northbound API

• V2X Information Service is compliant with the ETSI MEC030 Specification, v2.2.1:
  • ETSI GS MEC 030 V2.2.1
  • ETSI Forge - V2X Information Service API repository
• API
  • API Definition
  • Based on OpenAPI Specification (OAS) 3.0

AdvantEDGE Integration

• V2X Information service is implemented as a single sandbox pod within AdvantEDGE, providing service for all applications running as part of that sandbox

• 3 components:
  • Northbound Interface (NBI) & Core - (tightly coupled) implements the V2X Information Service API & internal service logic
  • Southbound Interface (SBI) - (decoupled from NBI/Core) implements glue logic between AdvantEDGE & the NBI/Core
• Threads:
  • Main thread - (NBI/Core) Handles requests to the V2X Information Service API (server) from users (i.e. scenario pods)
  • NBI event thread - (NBI/Core) Handles event channel from SBI (for V2X Information Service subscriptions)
  • SBI event thread - (SBI) Handle events from AdvantEDGE (scenario updates, mobility events, etc.) & updates V2X Information Service database)
• Supports hot-restart
  • User / app subscriptions with and without a duration parameter survive location service pod restarts