Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C CDD TS 102 894-2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ITS - Intelligent Transport SystemsITS - Intelligent Transport Systems
  • ASN1ASN1
  • CDD TS 102 894-2
  • Issues
  • #2
Closed
Open
Issue created Apr 20, 2021 by Matthew Banks@banksm

Release 2 message IDs

ITS-Container.asn contains the PDU header message ID for each message type. Currently this lists up to the "rtcmem" ID of 13.

ItsPduHeader ::= SEQUENCE {
    protocolVersion INTEGER (0..255),
    messageID INTEGER{ denm(1), cam(2), poi(3), spatem(4), mapem(5), ivim(6), ev-rsr(7), tistpgtransaction(8), srem(9), ssem(10), evcsn(11), saem(12), rtcmem(13) } (0..255),  -- Mantis #7209, #7005
    stationID StationID
}

However there are a number of newer message types that don't have a definition even though the specs refer to ETSI TS 102 894-2, this includes CPM, MCDM, VAM, PZM. Whilst these are Release 2 features I don't see where their message IDs are defined, especially since the BTP ports and ITS-AIDs are already defined for these services.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking