Keep the colleague's microbu-esp32c5 tree in this repository

obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but that tree was gitignored, so a clone of this repository could not build the firmware it ships. It is now committed here as ordinary files in its own folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP bridge's signature verification (--trust) used on the bench. Nothing is fetched from or pushed to the colleague's repository; this repository and its remotes carry everything. The folder's own .gitignore keeps build output, downloaded components and private key material out, as it did there; the committed file set is identical to that repository's tracked files. The ESP32-C5 is still flashed from obu-firmware/, which only takes vanetza-idf from microbu-esp32c5/, so the two stay separate folders. FLASHING.md says how to take a newer version of the colleague's tree (copy it over the folder, rebuild, test, commit).
2026-09-23 17:46:40 +02:00
parent 2f60623e18
commit 0e9525162d
9881 changed files with 1582523 additions and 17 deletions
@@ -0,0 +1,68 @@
+POIM-CommonContainers {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) poi(103916) common(99) major-version-1 (1) minor-version-1 (1)} 
+
+DEFINITIONS AUTOMATIC TAGS ::= BEGIN
+
+IMPORTS
+
+Identifier2B, IvimReferences, MapReferences, Provider, TimestampIts
+FROM ETSI-ITS-CDD {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) major-version-4 (4) minor-version-1 (1)} WITH SUCCESSORS
+
+PoiType
+FROM POIM-PDU-Description {itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) poi(103916) poim(0) major-version-1 (1) minor-version-1 (1)} 
+;
+
+/**
+ * This type represents the common management container of the POI Information Blocks. 
+ *
+ * It shall include the following components: 
+ *
+ * @field serviceProviderId: identifier of the organization that provided the POI Information Block.
+ *
+ * @field blockIdentificationNumber: identifier of the POI Information Block, as assigned by the organization identified in serviceProviderId.
+ *
+ * @field timestamp: timestamp of the generation or last change of the POI Information Block
+ *
+ * @field linkedIvims: the optional list of references to IVIMs that are semantically connected because providing signage information applying to the POI.
+ *
+ * @field linkedMapem: the optional list of references to MAPEMs that are semantically connected because providing information applying to the POI.
+ *
+*/
+PoiBlockManagementContainer::= SEQUENCE {
+	serviceProviderId			Provider, 
+	blockIdentificationNumber	Identifier2B,
+	timestamp					TimestampIts,
+	linkedIvims                 IvimReferences OPTIONAL,
+    linkedMapems                MapReferences OPTIONAL,
+    ...  
+}
+
+/**
+ * This type can be used to reference to other related POI Information Blocks. 
+ *
+ * It shall include the following components: 
+ *
+ * @field poiInfoBlockType: the type of related POI Information Blocks
+ *
+ * @field serviceProviderId: identifier of the organization that provided the related POI Information Block.
+ *
+ * @field blockIdentificationNumber: identifier of the related POI Information Block, as assigned by the organization identified in serviceProviderId.
+ *
+ * @field timestamp: optional timestamp of the generation or last change of the related POI Information Block
+ *
+*/	
+
+RelatedPoiInfoBlock::= SEQUENCE{
+   poiInfoBlockType             PoiType,
+   serviceProviderId			Provider, 
+   blockIdentificationNumber	Identifier2B, 
+   timestamp					TimestampIts OPTIONAL,
+    ...
+}
+
+/** 
+ * This DF shall contain a list of @ref RelatedPoiInfoBlock and represents a commmon container to refer to other POI Information Blocks.
+ *
+*/
+RelatedPoiInfoBlockContainer::= SEQUENCE OF RelatedPoiInfoBlock
+
+END