Community Attendees:

@Thorsten Lohmar @Steve Vickers @Stefano Brivio @Masaharu Hattori @Hubert Przybysz @Barath K

Community Attendees:

LF Staff:

Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Agenda 1
Agreement of last minutes (link)
TSC agreed, that the Dedicated Networks API is continued under the umbrella of the QoD Working group. See 2025-09-18 TSC Minutes - CAMARA Project - CAMARA Project
- Wiki Page already moved.
- Regular Community meetings on every second Fridays at 1300h UTC (14:00 CET, 15:00 CEST).
  - separate breakout meeting on a need basis.
- Only one Mailing list, i.e. sp-qod@lists.camaraproject.org (will be renamed soon, see Find a better name for the Sub Project Quality On Demand (not the API) · Issue #498 · camaraproject/QualityOnDemand).
  - the mailing list sp-dedicated-networks@lists.camaraproject.org will be removed.
  - Please ensure to subscribe to the qod mailing list
Closed Pull Request
Issues and Pull Requests:
- Scope of Dedicated Networks API version 0.2.0 · Issue #69 · camaraproject/DedicatedNetworks
- Remove `oAuth2` security scheme · Issue #56 · camaraproject/DedicatedNetworks
- [Profiles API] NetworkProfileId is a string but format is not yet specified · Issue #47 · camaraproject/DedicatedNetworks
- [Accesses API] Improve error handling when access is requested at incorrect time · Issue #46 · camaraproject/DedicatedNetworks
  - Suggestion to use Status Code 409 with a DN specific code. Hubert will create a PR
- [API Design Guideline] Potential usecases / reuse of DeviceResponse Object · Issue #44 · camaraproject/DedicatedNetworks
- [API Design Guideline] Does an API not implementing OIDC Discovery make it non-CAMARA compliant · Issue #43 · camaraproject/DedicatedNetworks
  - Should be clarified in commonalities. Since the last comment is older than a month, we need to revive the thread.
- [API Design Guideline] "id" could be more descriptive in payload · Issue #42 · camaraproject/DedicatedNetworks
  - Current API spec seem to be inline with commonalities, i.e. no requirement on property naming. Concluded understanding to be confirmed with commonalities. AP Thorsten
- [Accesses API] POST operation is synchronous - may be there are use cases for async. · Issue #40 · camaraproject/DedicatedNetworks
- [Accesses API] x-device Header clarifications · Issue #39 · camaraproject/DedicatedNetworks
  - To be brough to commonalities: (A) can we continue using GET with a header and (B) is there a benefit of harmonizing using of device object in header. Two approaches: Either create individual headers for each device object property (as done in simple edge discovery) or serialize the device object (as done in Dedicated Networks)
- dedicated-network-accesses.yaml missing device lifecycle · Issue #21 · camaraproject/DedicatedNetworks
- Application Developers use cases · Issue #20 · camaraproject/DedicatedNetworks

Minutes

There will be another breakout in two weeks (6th Oct).

%%{init: {
  "theme": "neutral",
  "themeVariables": {
    "fontSize": "17px",
    "fontFamily": "Segoe UI, Roboto, Arial"
  }
}}%%

flowchart TB
    %% Classi
    classDef api fill:#E8F4FF,stroke:#2B88D8,stroke-width:2,rx:8;
    classDef infra fill:#F5F5F7,stroke:#8A8A8A,stroke-width:1.5,rx:10;
    classDef comp fill:#FFFFFF,stroke:#2B88D8,stroke-width:1.5,rx:8;
    classDef device fill:#ECFDF5,stroke:#10B981,stroke-width:1.5,rx:8;

    %% Titolo
    subgraph T["Dedicated Networks"]
    direction TB

    %% Sezione Architettura
    subgraph A["Architecture & Sequence"]
    direction LR

    %% Colonna sinistra: Consumer + Device/UE
    subgraph Consumer["API Consumer"]
        C["Portal / Backend"]:::comp
        %% Scegli l'icona del device qui sotto:
        %% Opzioni consigliate: 🤖 (IoT/UE generico), 📱 (smartphone), 🚗 (veicolo), 🏭 (asset industriale), 🛰️ (terminal sat)
        D["Device<br/>Uses Reserved Connectivity"]:::device
    end

    %% Colonna centrale: CAMARA APIs
    subgraph Exposure["CAMARA APIs"]
        P["Profiles API<br/>dedicated-network-profiles"]:::api
        N["Dedicated Network API<br/>dedicated-network"]:::api
        X["Accesses API<br/>dedicated-network-accesses"]:::api
    end

    %% Colonna destra: CSP
    subgraph Network_CSP["Network Provider"]
    end

    %% Collegamenti con etichette
    C -.-|"0️⃣ Complete Prerequisites<br>(Not in scope)"| Network_CSP
    C -->|1️⃣ Choose Dedicated Network Profile<br/>API: Profiles| P
    C -->|2️⃣ Create Dedicated Network<br/>API: Dedicated Network| N
    C -->|3️⃣ Create Device Accesses<br/>API: Accesses| X

    P --> Network_CSP
    N --> Network_CSP
    X --> Network_CSP

    %% Step 4: Device verso CSP
    D -->|4️⃣ Allowed devices use reserved connectivity| Network_CSP

    end
end

%% Ingrandisci ulteriormente le icone (solo testo/emoji del nodo)
style C font-size:22px;
style D font-size:24px;
style P font-size:20px;
style N font-size:20px;
style X font-size:20px;
style Network_CSP font-size:20px;

Agenda 1

Comments

Action items

Add Mermaid illustration for API description to minutes.

Hubert, Create PR on [Accesses API] Improve error handling when access is requested at incorrect time · Issue #46 · camaraproject/DedicatedNetworks

Thorsten, Open an Issue or a discussion in commonalities on [API Design Guideline] "id" could be more descriptive in payload · Issue #42 · camaraproject/DedicatedNetworks

Thorsten, Open an Issue or a discussion in commonalities on [Accesses API] x-device Header clarifications · Issue #39 · camaraproject/DedicatedNetworks

2025-09-22 Dedicated Networks Minutes

Community Attendees:

Community Attendees:

LF Staff:

Agenda

Minutes

Action items