Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
50 commits
Select commit Hold shift + click to select a range
f499d3c
Merge pull request #592 from usdot-jpo-ode/master
SaikrishnaBairamoni Oct 27, 2025
0200f7a
Add constructor to OdeMessageFrameMetadata for ASN.1 hex string; refa…
Michael7371 Apr 2, 2026
b245585
json schemas in resources (#1)
iyourshaw Apr 9, 2026
03fc79a
Update CI action versions and clean up SonarCloud workflow (#594)
SaikrishnaBairamoni Apr 21, 2026
be05983
Configurable kafka concurrency (#3)
iyourshaw Apr 21, 2026
8a10079
tweak pom and ci yaml
SaikrishnaBairamoni Apr 22, 2026
9c22692
add trigger to check changes
SaikrishnaBairamoni Apr 22, 2026
0aaa75e
update jmockit.version
SaikrishnaBairamoni Apr 22, 2026
7419e23
update jmockit dependency
SaikrishnaBairamoni Apr 22, 2026
9be80dc
remove feature branch trigger
SaikrishnaBairamoni Apr 23, 2026
1e6f5f6
Update README.md
SaikrishnaBairamoni Apr 23, 2026
90677be
Add licence and badge check
SaikrishnaBairamoni Apr 23, 2026
defb711
Update README.md
SaikrishnaBairamoni Apr 23, 2026
500f707
add inline comments for sonar gates
SaikrishnaBairamoni Apr 24, 2026
126052a
Merge pull request #595 from usdot-jpo-ode/fix_sonar_coverage
SaikrishnaBairamoni Apr 24, 2026
9a10841
Quarterly release process update for jpo-asn-pojos (#5)
iyourshaw Apr 24, 2026
2ff74e3
Port remap receiver (#2)
John-Wiens Apr 24, 2026
1e1868c
shared kafka fix, resolve conflict (#9)
iyourshaw May 6, 2026
eea011b
Add ASN.1 validation to receiver tests by asserting that produced ASN…
Michael7371 May 8, 2026
36c2fea
update ODE TMC diagram
Michael7371 May 8, 2026
af4381d
resolve checkstyle formatting comments
Michael7371 May 8, 2026
3711e95
Update Kafka consumer configuration in application.yaml to adjust aut…
Michael7371 May 8, 2026
ff8f862
Add env vars for number of ACM processes, update test process (#7)
iyourshaw May 11, 2026
52cfa07
Release Prep 2026-Q2 (#10)
drewjj May 11, 2026
2f734b6
Enhance error logging in GenericReceiver to include detected message …
Michael7371 May 11, 2026
e1598af
Update Kafka configuration in docker-compose.yml and application.yaml…
Michael7371 May 13, 2026
0d564c6
Enhance UdpHexDecoder to support stripping of 1609.2 headers and impr…
Michael7371 May 13, 2026
eea0b91
Refactor UdpHexDecoder to ensure consistent casing for ASN.1 hex stri…
Michael7371 May 15, 2026
ff80952
Reverting changes to unintended files
Michael7371 May 15, 2026
550717a
resolve checkstyle comments
Michael7371 May 15, 2026
479e91f
Refactor OdeLogMetadata and OdeMsgMetadata constructors to use generi…
Michael7371 May 18, 2026
66755d5
Update receiver tests to replace "1609.3 WSMP header" with "1609.2 WS…
Michael7371 May 18, 2026
7592f0b
Update BSM and PSM receiver test files to correct expected output val…
Michael7371 May 18, 2026
aa29d7d
Refactor receiver tests to replace parameterized tests with individua…
Michael7371 May 19, 2026
bf9acd5
Remove commented-out local UDP_IP assignment in udpsender_generic.py …
Michael7371 May 19, 2026
7c10a92
updated BSM and PSM receiver tests to use IEE1609.2 signatures instea…
Michael7371 May 20, 2026
5d3f2c7
Merge pull request #596 from usdot-jpo-ode/fix/retain-asn1-message-si…
Michael7371 Jun 2, 2026
6ad5454
json schemas in resources (#1)
iyourshaw Apr 9, 2026
9a2eb8d
Configurable kafka concurrency (#3)
iyourshaw Apr 21, 2026
96303c8
Quarterly release process update for jpo-asn-pojos (#5)
iyourshaw Apr 24, 2026
afe6278
Port remap receiver (#2)
John-Wiens Apr 24, 2026
f56d818
shared kafka fix, resolve conflict (#9)
iyourshaw May 6, 2026
0a9d9be
Add env vars for number of ACM processes, update test process (#7)
iyourshaw May 11, 2026
d6cf0a1
Release Prep 2026-Q2 (#10)
drewjj May 11, 2026
0af7db9
Merge branch 'develop' into fix/merge-usdot-q2-changes
Michael7371 Jun 2, 2026
1918622
Update release notes for version 5.2.0 to include ASN Hex 1609.2 Sign…
Michael7371 Jun 2, 2026
e5fac0c
Update compatibility matrix and release notes for version 6.0.0, refl…
Michael7371 Jun 2, 2026
f73c930
Merge pull request #11 from neaeraconsulting/fix/merge-usdot-q2-changes
Michael7371 Jun 4, 2026
5d6f675
Fix duplicate commented message (#12)
Michael7371 Jun 5, 2026
58aef20
Merge pull request #597 from neaeraconsulting/develop
Michael7371 Jun 16, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/workflows/artifact-publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ on:
jobs:
build:
runs-on: ubuntu-latest
permissions:
contents: read
packages: write

steps:
- name: Checkout code (with submodules)
Expand Down
25 changes: 14 additions & 11 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,49 +7,52 @@ on:
- "develop"
- "master"
- "release/*"

jobs:
docker:
runs-on: ubuntu-latest
steps:
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
uses: docker/setup-buildx-action@v4
- name: Build
uses: docker/build-push-action@v5
uses: docker/build-push-action@v7
with:
cache-from: type=gha
cache-to: type=gha,mode=max

test-no-sonar:
if: github.event.pull_request.base.repo.owner.login != 'usdot-jpo-ode'
# Fallback for PRs from forks outside usdot-jpo-ode (e.g. cdot). Runs plain tests without SonarCloud since SONAR_TOKEN is not available to fork-triggered workflows.
if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.owner.login != 'usdot-jpo-ode'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v6
with:
submodules: recursive
- name: Set up JDK
uses: actions/setup-java@v4
uses: actions/setup-java@v5
with:
java-version: "21"
distribution: "temurin"
- name: Build and test
run: mvn clean verify

sonar:
if: github.event.pull_request.base.repo.owner.login == 'usdot-jpo-ode'
# Run SonarCloud analysis on:
# - pushes to develop/master/release branches (internal)
# - PRs opened from branches within the usdot-jpo-ode org
# Skipped for fork PRs (e.g. from cdot) because GitHub does not expose SONAR_TOKEN to workflows triggered from forks. Those PRs fall through to the test-no-sonar job instead.
if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.pull_request.head.repo.owner.login == 'usdot-jpo-ode')
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v6
with:
submodules: recursive
- name: Set up JDK
uses: actions/setup-java@v4
uses: actions/setup-java@v5
with:
java-version: "21"
distribution: "temurin"
- name: Run Sonar
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
run: |
ls -la && pwd
mvn -e clean org.jacoco:jacoco-maven-plugin:prepare-agent package sonar:sonar -Dsonar.projectKey=usdot.jpo.ode:jpo-ode -Dsonar.projectName=jpo-ode -Dsonar.organization=usdot-jpo-ode -Dsonar.host.url=https://sonarcloud.io -Dsonar.branch.name=$GITHUB_REF_NAME
mvn -e clean verify sonar:sonar -Dsonar.projectKey=usdot.jpo.ode:jpo-ode -Dsonar.projectName=jpo-ode -Dsonar.organization=usdot-jpo-ode -Dsonar.host.url=https://sonarcloud.io
45 changes: 0 additions & 45 deletions .sonarqube/sonar-scanner.properties

This file was deleted.

202 changes: 202 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,202 @@

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
25 changes: 22 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,4 @@
| Sonar Code Quality | Sonar Code Coverage |
|---------------------|---------------------|
[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=usdot.jpo.ode%3Ajpo-ode&metric=alert_status)](https://sonarcloud.io/dashboard?id=usdot.jpo.ode%3Ajpo-ode) | [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=usdot.jpo.ode%3Ajpo-ode&metric=coverage)](https://sonarcloud.io/dashboard?id=usdot.jpo.ode%3Ajpo-ode) |
![GitHub Release](https://img.shields.io/github/v/release/usdot-jpo-ode/jpo-ode) [![CI](https://github.com/usdot-jpo-ode/jpo-ode/actions/workflows/ci.yml/badge.svg)](https://github.com/usdot-jpo-ode/jpo-ode/actions/workflows/ci.yml) ![Docker Pulls](https://img.shields.io/docker/pulls/usdotjpoode/jpo-ode) [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=usdot.jpo.ode%3Ajpo-ode&metric=alert_status)](https://sonarcloud.io/dashboard?id=usdot.jpo.ode%3Ajpo-ode) ![GitHub License](https://img.shields.io/github/license/usdot-jpo-ode/jpo-ode)

# jpo-ode

Expand All @@ -12,6 +10,8 @@ The ITS ODE is a real-time virtual data router that ingests and processes operat

_Figure 1: ODE Dataflows_

For a module-by-module description of the components in this diagram, see [Architecture Section 5.2 – Architecture Module Reference](docs/Architecture.md#52---architecture-module-reference).

**Documentation:**

1. [ODE Architecture](docs/Architecture.md)
Expand Down Expand Up @@ -444,6 +444,23 @@ In order to utilize Confluent Cloud:

#### Note

### Port Mapped Receiver Configuration
Many production deployments may not send intersection data directly from an RSU unit. This often happens if another device is responsible for generating MAP / SPaT messages or if a proxy or load balancer is used between an RSU unit and the ODE. To handle these edge cases the ODE has a configurable port-mapped receiver which can be used for receiving data on a variety of ports. The intent of this feature is to allow the ODE to continue to identify different source RSU units based upon the port the data is forwarded on.

To use port-mapped ingest, add an entry similar to the below to the application.yaml file. The entry below creates a BSM receiver which listens on port 1234. Any BSM data received on port 1234 will be marked as having been received from the IP 1.2.3.4.

```
port-mapped-ingest:
sources:
- intersectipon-name: "Name"
intersection-id: 1234
origin-ip: 1.2.3.4
port: 1234
type: BSM
```

Please note, ports added here are not automatically opened in the host docker container. Any port added here should separately be added to the running docker container.

This has only been tested with Confluent Cloud but technically all SASL authenticated Kafka brokers can be reached using this method.

[Back to top](#table-of-contents)
Expand All @@ -464,6 +481,8 @@ The configuration that defines this is in the jpo-utils submodule [here](jpo-uti

For further documentation on configuring the MongoDB Kafka Connect image refer [to this readme](jpo-utils/README.md).



## Note

Kafka connect is being used for MongoDB in this implementation but it can interact with many types of databases, here is further documentation for [kafka connect](https://docs.confluent.io/platform/current/connect/index.html)
Expand Down
Loading
Loading