SNS JU 2026 Front-End Module Grant: HORIZON-JU-SNS-2026-FEM-STREAM-B-02

SNS JU 2026 Front-End Module Grant: HORIZON-JU-SNS-2026-FEM-STREAM-B-02

Europe’s path to 6G leadership is moving from roadmap planning into implementation, and this call is one of the few opportunities to get directly into that transition. The Smart Networks and Services Joint Undertaking (SNS JU) opened its seventh call in 2026 for a single topic, HORIZON-JU-SNS-2026-FEM-STREAM-B-02, focused on the microelectronic Front-End Module (FEM) and the FR3 frequency domain. On 26 May 2026, the call opened for submission. The official submission deadline is 3 September 2026 at 17:00 CET.

The current call page states that this is a single-stage RIA and sets out an indicative budget of EUR 14 million for the FEM topic. It also links to the EU Funding and Tenders Portal for official submission records and states that all relevant information is available there. The same SNS JU call framework appears in the amended sns_ri_wp2026_amended-fem_2calls_final.pdf, which includes topic structure, budget lines, and general conditions.

Key details at a glance

What this opportunity is actually funding

The FEM call is not a broad, general telecom grant; it is a highly specific microelectronics RIA. The call text describes FEM as a “key building block of an advanced 6G radio system,” and frames it as the hardware layer that determines competitiveness and market readiness for future systems. The goal is to push European capability on front-end architecture at the frequencies expected to matter for 6G development, especially upper FR3 and practical deployment constraints.

The call context appears in two sources. On the SNS JU page, it is presented as part of the “7th Call for Proposals” in the 2026 work programme. The amended work-programme document gives the technical context: this is a workplan-level objective aimed at microelectronics, RF, and advanced packaging integration, and at building practical designs that can bridge innovation with near-industrial pathways. The call is also connected to broader EU-level goals around digital leadership, supply chain resilience, and strategic autonomy.

A practical consequence of this focus is that proposals will be judged on whether they can produce reusable, implementable FEM outcomes with a pathway to ecosystem integration. The same document repeatedly notes that the topic is expected to support FR3 hardware progress, frequency-sharing realities in Europe, and commercialization-facing development steps toward chips and subsystems. This means the call is not just science for science’s sake. It is designed to test whether a consortium can move from promising design concepts into implementation maturity with strong EU industry relevance.

Because the program is single-stage, teams should expect competition among fully formed consortia rather than a phased pre-proposal funnel. In other words, this is one consolidated submit-and-evaluate pathway, so your proposal package must already carry the technical, commercial, and collaboration weight on day one.

Who this call is for (and who it is not for)

The most important fit test is consortium shape. This call is for organisations able to operate at the intersection of hardware innovation, telecom standards, and demonstrable implementation. Suitable participants typically include:

• microelectronics firms, RF designers, RF packaging specialists,
• network/antenna system integrators,
• software and digital calibration teams that can turn data and measurements into operational control,
• industrial research actors who can map design outputs into pilot-line transfer paths,
• universities and applied research groups with a clear role in the development chain.

The official conditions make it clear that the call is a technical collaboration call with strict partnership expectations. A “minimum participation of SNS JU member” condition applies: at least half of the budget for this FEM topic must be implemented by the SNS JU member (other than the Union) and its constituent or affiliated entities. The call text ties this condition directly to continuity of IKOP generation and long-term collaboration stability.

Another major condition is the IKOP indicator. For this topic the amended work programme sets an indicative 3.6% IKOP level as the project-budget minimum to be met and evaluated. In practical terms this means the proposal must show credible in-kind non-public financing contributions and concrete ecosystem participation from members of the relevant consortium. The call requires a dedicated IKOP table in Part B of the application form, and missing mandatory fields can invalidate eligibility.

For topic-specific international participation, the 2026 document states that some actions are under Article 22(5) restrictions for the protection of EU strategic interests. In that context, this FEM topic includes legal participation boundaries to Member States, Associated Countries, OECD and Mercosur countries (for this section of the doc, India is not included under that same phrase used for this topic set). If you are unsure whether your legal entity qualifies, treat this as a blocking prerequisite rather than a late-stage concern: it is part of admissibility.

The same topic conditions also cover high-risk supplier controls. Entities assessed as high-risk suppliers of mobile network communication equipment are excluded under those restrictions. Proposals linked to controlled entities may be blocked if they fail clearance conditions.

In short, this is not a “whoever has a good idea” opportunity. It is for organizations that can satisfy both technical excellence and eligibility architecture at once.

Why this call matters for applicants building technology roadmaps

If your group is pursuing 6G hardware, this opportunity matters because it sits exactly where standards, hardware manufacturability, and commercialization intersect. The topic text frames FEM as an enabling component for advanced use cases and mass-market competitiveness, while the broader SNS JU call rationale references spectrum and deployment strategy constraints in FR3.

From a team perspective, the benefits of being in this call are:

1. Access to EU-level R&I funding for a constrained but high-impact topic.
2. Alignment with EU strategic priorities on digital sovereignty. Even if the grant size is not huge in mega-program terms, the visibility and network value is significant.
3. Pressure-tested collaboration opportunity. The call design forces industry-academia-consortium cooperation across RF, microelectronics, packaging, and exploitation tracks.
4. A path into European pilot ecosystems. While the call wording highlights links to Chips JU and broader ecosystems, this means applicants should position their work for transfer, not only prototype publication.

It is also useful to set realistic expectations. EUR 14 million is the topic budget, not automatically one grant size. Realistic wins usually involve teams that can justify a focused, staged technical delivery with clearly partitioned work packages and measurable outputs.

Application process: practical sequence that avoids common pitfalls

The SNS JU page and FAQ show this is one of the calls managed via the EU portal process, with SNS-specific reference documents and FAQ support. For teams already comfortable with Horizon Europe flows, the task is mostly about call-specific compliance.

Use this practical sequence:

1) Confirm admissibility before team design is frozen

Before opening the proposal outline, verify all legal and ownership constraints. A proposal that is ineligible on submit due to restricted participation or missing required member participation shares is usually not salvageable within the review window. Confirm:

• whether each legal entity is eligible by country class,
• whether any beneficiary falls under prohibited high-risk constraints,
• whether affiliate/subcontractor links trigger additional controls.

2) Build an admissibility-first work package split

Because this is a single-stage RIA, your package needs to be coherent from the first draft. Build the proposal with these layers:

• Core technology: concrete FEM architecture, target frequency bands, interference and sharing strategy, packaging and system integration plan.
• Implementation confidence: who delivers which physical design, who owns which integration test, who manages validation.
• IP and commercialization pathway: how results are retained in eligible countries as required by security-relevant provisions.
• Ecosystem transfer: evidence that work can connect to European pilots and future standards/industrial paths.

3) Prepare the IKOP and SNS J U member participation map early

The amendments explicitly require a Part B IKOP compliance table and minimum participation percentages. For this topic, the admissibility language is strict and operational, not decorative. Do not wait until the end of drafting to reconstruct this section.

4) Use the Part B budget and narrative constraints correctly

The same SNS documents mention that the call follows Horizon Europe participation rules with topic exceptions. Budget tables are often where teams fail consistency checks. Keep the RIA budget consistent across cost tables, narrative work package splits, and expected partner contributions. If your consortium contains a mix of for-profit and non-profit participants, verify in-kind and reimbursement assumptions for each role.

5) Verify page limit and format before final submission

The call document states a 70-page full proposal limit for RIAs and CSAs under these streams. It is easy to exceed this limit with annex-heavy writing. A trimmed, evidence-rich draft with direct references is easier to evaluate than a long concept-only submission.

6) Submit with margin before 3 September 2026

Submission deadline is single-cutoff and tied to Brussels local time. Use local time conversion at least one day before the deadline.

Required materials and evaluation cues you should plan for

You should deliver all mandatory data requested in SNS portal forms, but content quality also matters. For this topic, evaluators look for technical realism and consortium quality in equal measure.

Include these core materials:

• Call condition compliance matrix mapped directly to the official FEM topic document,
• Technical concept with clear FR3 architecture logic, spectrum assumptions, and risk plan,
• Partner capability matrix showing why each partner is necessary and how budget shares link to the 50% SNS JU member implementation requirement,
• Consortium governance and decision flow, especially for in-kind contribution tracking,
• SME contribution plan that is believable (the topic targets around 20%),
• Security and access controls if restricted participation rules apply,
• Intellectual property management, including ownership and transfer conditions.

An often-overlooked clue in this call is that the topic language repeatedly references standardization interfaces and ecosystem readiness. So include references to how your concept can interact with open standards pathways and test platforms, not only internal lab outputs.

What a strong FEM proposal usually demonstrates (without adding unsupported claims)

A strong submission typically demonstrates four things:

1. Clear technical edge with execution discipline. The project should explain exactly how the FEM design reduces uncertainty in FR3 operation and real-world coexistence.
2. A realistic exploitation route. Reviewers need to see how outputs become hardware artifacts, pilot validation points, and transfer steps.
3. A coalition that can sustain momentum. The consortium architecture should show long-term joint activity and concrete 6G-IA participation.
4. Compliance-ready operations. Eligibility details are not a footnote. They determine admissibility and can disqualify high-quality science if incomplete.

Because this is a call under a strategic programme, proposals that are only exploratory and do not show deployment alignment tend to score poorly. The same applies if teams over-index on “future research curiosity” without showing measurable output.

Common mistakes I repeatedly see in SNS-style calls

1. Waiting until final weeks to handle IKOP compliance. The mandatory table is a hard condition. Leaving it to late editing causes structural mistakes and missing values.
2. Assuming all EU-eligible entities are automatically unrestricted. The FEM topic includes topic-specific participation boundaries and security conditions. Not every partner should be treated identically.
3. Overly broad technical scope. FEM is narrow. If your narrative drifts into general 6G claims, it loses focus.
4. No industrial transfer anchor. The topic repeatedly references commercialization and pilot-line readiness. A technically elegant design without transfer logic looks weak in this call.
5. Relying on one lead institution for every dependency. The 6G-IA participation threshold and workload split require balanced project ownership.
6. Treating page limits as optional. A proposal over the limit can be rejected before full evaluation if it violates formatting constraints.

A useful way to audit your draft is to run a pre-submission checklist against the official FAQ and call PDF. Anything not explicitly linked to a required section in those documents should be removed or moved.

FAQ for applicants

Is the amount fixed?

No. The call publishes a topic-level budget envelope of EUR 14 million. Individual award size depends on evaluation, competition, and portfolio fit.

Is this call still open?

As of 2026-06-03, yes. The SNS JU current call page indicates the 7th call opened on 26 May 2026 and closes on 3 September 2026 at 17:00 CET.

What kind of action is this?

Single-stage Research and Innovation Action under Stream B.

Is a consortium mandatory?

In practice, yes. The conditions and budget share thresholds indicate this is a multi-actor action where industry participation is structurally required.

Is there an explicit SME expectation?

The SNS conditions note a programme-level target of 20% SME participation.

Can non-EU participants join?

The topic applies participation restrictions to specific country groups depending on article-22(5) conditions. The call language for this topic identifies Member States, Associated Countries, OECD, and Mercosur as eligible classes for this participation regime.

What is the expected technical output?

Focus is on microelectronic FEM design and demonstrable progress toward advanced 6G front-end capabilities with practical integration orientation.

Official links and what to monitor next

Use this set as your primary source stack:

• SNS JU Current Call for Proposals: https://smart-networks.europa.eu/current-call-for-proposals/
• SNS JU FAQ for calls: https://smart-networks.europa.eu/faq-call-6-frequently-asked-questions/
• Amended SNS 2026 R&I Work Programme (FEM section): https://smart-networks.europa.eu/wp-content/uploads/2026/04/sns_ri_wp2026_amended-fem_2calls_final.pdf
• SNS JU 7th Call Info Day (for context and partner networking): https://smart-networks.europa.eu/event/sns-ju-7th-call-for-proposals-info-day-brokerage-event/
• EU Funding & Tenders Portal topic view: https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/HORIZON-JU-SNS-2026-FEM-STREAM-B-02
• SNS brokerage platform: https://sns-brokerage.eu/

If you are submitting through this window, treat these as your working set. Pull the EU portal topic page for final administrative fields just before submission, because submission forms can be updated even after the call page is published.

Final preparation checklist before submit

• Confirm legal entity admissibility against topic participation restrictions.
• Complete the mandatory Part B IKOP declaration and compliance table.
• Show clear budget allocation consistent with the 50% SNS JU member implementation threshold.
• Align technical narrative to FR3 FEM outcomes and deployment constraints.
• Include security- and confidentiality-related ownership handling where required.
• Keep proposal length within the RIA page limits.
• Submit before the 3 September 2026 17:00 CET cutoff.

The FEM call is most likely to reward teams that are technically precise and administratively disciplined. If your organization is already at the intersection of hardware design, telecom standardization, and industrial transfer, this is one of the first 2026 calls where your readiness can be converted into funding discussion, not just scientific discussion.