Notes - MIECT
Redes E Sistemas Autónomos
Notes - MIECT
Redes E Sistemas Autónomos
  • Redes e Sistemas Autónomos
  • Peer-to-Peer Systems and Networks
    • Content Distribution Networks
    • Peer-to-peer networks
      • Types
    • Structured vs Unstructured
    • Fully Decentralized Information System
    • FastTrack/KaZaA
    • OpenNAP/Napster
    • BitTorrent
  • InterPlanetary File System (IPFS)
    • IPFS
      • Bitswap
    • Connecting an IPFS node to the P2P network
    • Searching in DHTs (Structured)
    • File Search
    • Security
  • Ad-Hoc Networks
    • Mobile Ad-hoc networks
    • Application Scenarios
    • Routing
      • AODV - Ad Hoc On-Demand Distance Vector Routing
      • OLSR - Optimized Link State Routing Protocol
      • LAR – Location Aided Routing
      • Batman
    • IP Address Assignment
  • Self-organized systems: Data, learning and decisions
    • Use Cases and Data
    • Machine Learning
      • Supervised Learning
      • Neural Networks
      • Reinforcement Learning
      • Unsupervised Learning: K-means
    • Learning
  • Vehicular Networks
    • Vehicular Ad Hoc Networks
    • How do they work?
    • SPAT: Signal Phase And Timing
    • MAP: MAP
    • Manoeuvre Coordination Message (MCM)
    • Communication Technologies
  • QoS and Security
    • TCP- and UDP-based applications
      • TCP-Cubic
    • QUIC
    • TCP-Vegas
    • Classification of Transport protocols
    • Exploiting Buffering Capabilities
    • QoS in UDP: trade-offs
    • Transmission Quality (Batman v.3)
    • QoS-OLSR
    • Security
      • Key Management
      • RSA (Rivest-Shamir-Adleman) Key
      • Key Management in ad-hoc networks
      • Self-organized public key management (SOPKM)
      • Self-securing ad-hoc wireless networks (SSAWN)
Powered by GitBook
On this page
  1. Vehicular Networks

Manoeuvre Coordination Message (MCM)

PreviousMAP: MAPNextCommunication Technologies

Last updated 1 year ago

Includes the intended (or planned) maneuvers and one or more desired (or alternative) trajectories.

  • Each trajectory is a spatial-temporal description of the vehicle C-ITS-Ss trajectory in the next 5 to 10s.

  • Planned trajectories are used by C-ITS applications to improve the prediction of future locations of nearby vehicles and to detect conflicts.

  • Desired trajectories are used to request coordination between vehicles.

It is expected that MCMs are generated continuously at a rate between 1 Hz and 10 Hz depending on the context.

  • Early detection of the need for maneuver coordination.

  • The MCS could include triggering conditions while also having the possibility of being triggered by an application.

For roadside applications, the MCMs are expected to include specific advice for specific vehicles, e.g. suggest a given speed or a lane change.

MCMs transmitted by roadside units are expected to be smaller in size (although they can include advice for multiple vehicles) and transmitted less frequently than those transmitted by vehicles.

Any Road user or other equipped road safety stakeholder could analyze the road traffic situation based on received information combined with other sensor data.

Advise or manage the road users on how to act to realize an efficient and safe resolution of the situation.

Examples

  • Goto maneuver;

  • Idle maneuver;

  • Follow Path maneuver;

  • Follow Trajectory;

  • Scheduled Goto;

  • Stop Maneuver;

  • Maneuver Done;

  • Teleoperation Maneuver;

  • Teleoperation Done;

  • ...

Vehicle S wants to overtake the stationary Bus