About
Lessons Learnt
WP2: Platform Architecture and Verticals
Architectural Flexibility vs. Integration Scope
While initially aimed for a single 6G-PATH architecture supporting all use cases, we discovered that a “one-size-fits-all” approach is not always necessary or efficient. Some use cases can remain decoupled without value loss.
- Action: Refine architecture based on integration feedback to balance universality with selective integration.
Incremental Support for Emerging Technologies
B5G exploration showed incremental 6G transition is more realistic than full immediate adoption, with varying technology compatibility levels.
- Action: Refine the integration roadmap alongside architecture design to align ambitions with technical readiness.
Prioritization of Use Cases
Not all use cases demand full integration into the core architecture.
- Action: Prioritize B5G integration for high-value UCs; allow independent development for specialized applications.
Cross-partner Integration Complexity
6G ecosystems have varying technical maturity levels and integration capabilities, creating bottlenecks in integration.
- Action: Implement staged, TRL-based integration plan to bridge maturity gaps.
AI Integration Misalignment
Despite progress, integrating AI into 6G platforms still faces challenges such as limited portability, fragmented toolchains, and uneven data availability across partners.
- Action: Systematically evaluate AI feasibility, reliability, and scalability requirements for specific platform functions.
WP3: 6G-PATH Experimentation Environment
Iterative Release Process
The development team has adopted an incremental approach base on intermediate releases (CI/CD) to support, dynamically, the integration into the seven testbeds.
- Action: To deliver in smaller steps instead of big-bang releases.
Clear Baseline Documentation
6G-PATH repositories include instructions for the deployment the usage and the extension of the component.
- Action: Ensuring clarity, transparency, and reproducibility in collaborative development.
Modular Architecture
The 6G-PATH platform has been split into different modules to ensure its maintainability and avoid blocking issues.
- Action: To separate experimentation and exposure functions separated; keep backend logic and user interface separated; define clear APIs between backend and frontend.
Reusability | Standard Recommendations Adoption | Sustained Activity
Continuous updated and improvements to support the integration into the seven testbeds.
- Action: ITU TR 103.761 has been adopted and work initiated in ICT 17 project has been continued throughout several SNS projects.
WP4: Verticals Experiments
Stakeholder Engagement and Road-map
Some UCs struggled with community and stakeholder engagement, limiting feedback and KVI collection.
- Action: A clear and realistic roadmap of activities per UC to align technical readiness with pilot execution.
Measurement and Validation
KPI/KVI collection proved valuable, but the application of WP6 methodology requires refinement.
- Action: Further collaboration between WP6 and WP4 is required in most UCs.
Execution and Scalability
Many solutions worked in small-scale setups but revealed challenges when scaling to multi-device or multi-user environments.
- Action: Lab tests must scale the testing to better prepare for large scale T&P.
Value and Impact for End-users
Pilots confirmed that B5G/6G-enabled solutions improve efficiency, safety, and user satisfaction across domains but validation in real operational settings is required to build trust.
- Action: T&P must be implemented in real operational settings when possible.
WP5: Cascade Funding and Training to Third Parties
From Feasibility Assessment to a Technical Eligibility Check
Difficult to assess use of the feedback in the final proposal; effort allocated better used in another evaluation scenario.
- Action: Introduce a Technical Eligibility Check to ensure only proposals that are ‘technically feasible’ are evaluated.
Expanding the Evaluation Process to Include Internal Evaluators
Evaluation of some OC#1 proposals could have benefited from a closer knowledge of the 6G-PATH infrastructure/capacity.
- Action: Include internal 6G-PATH evaluators to complement two external evaluators.
Improving Documentation
Some documents could have benefited from further simplification.
- Action: Improve documentation, including adding further elements to maximise a more heterogenous participation.
WP6: 6G Trials and Pilots Validation and Evaluation
KVI Interpretation Varies by Stakeholder and Context
Participants interpreted KVIs differently depending on use case and background.
- Action: Adapt language and survey framing to sector-specific realities.
Recruitment Diversity Affects Data Quality
Some verticals had imbalanced stakeholder groups which can lead to data bias.
- Action: Improve outreach strategy for harder-to-reach populations.
KVI Survey Instruments Need Iterative Refinement
Some questions were too abstract, overlapping, or required domain knowledge.
- Action: Simplify language, avoid jargon, and test for comprehension before wide deployment.
Cross-vertical Comparability is Challenging
Use cases had different contexts and baselines, which made comparisons of KVI scores difficult.
- Action: Standardize questionnaires Use contextual notes or disaggregated reporting for heatmaps and summaries.
Timing and Context Influence Responses
Users responded differently based on trial setup, time of day, or even recent app/system performance.
- Action: Standardize data collection protocols and note contextual factors during analysis.
WP7: Dissemination, Commercialisation and Standardisation
Dissemination Focus and Audience
Contextualising the technical outputs to reach non-specialist stakeholders (industry, policymakers, public).
- Action: Develop a unified dissemination strategy with clear audiences.
Ongoing Communication Keeps Momentum
Regular updates via newsletters, blogs, and posts keep stakeholders informed and invested in progress.
- Action: Develop a content calendar for continuous communications that reinforce the project’s value and developments.
Standardisation Alignment Challenge
Misalignment of project timelines with ongoing standardisation cycles limits the level of consortium influence.
- Action: Proactively engage with standardisation bodies and engage in pre-standardisation activities early.
Commercialisation & IP Exploitation Strategy
Resource disparities between the smaller and larger organisations and IP ownership issues hinder commercialisation opportunities.
- Action: Establish an exploitation board to map commercial pathways for technologies, apps, and use cases.
Ecosystem Engagement with Third Parties
Stronger collaboration with owners of use cases and testbeds is needed, leveraging their communication channels and participating in the exhibitions and events they attend.
- Action: Increase the engagement in third-party stakeholders through joint activities in targeted events.