IEEE Journal on Selected Areas in Communications (ieee-journal-on-selected-areas-in-communications)
Journal positioning
IEEE Journal on Selected Areas in Communications (JSAC) publishes high-impact work at
the systems and networks frontier of communications, organized largely around
topical special issues defined by current calls for papers — next-generation
wireless, networking, security, optical and quantum communication, and
machine-learning-for-communications, among others. Unlike a broad-scope transaction,
JSAC's fit is set by the active call: a paper must match a specific issue's theme and
clear a bar of impact and timeliness, not merely be technically correct. Routine,
incremental results — even sound ones — that do not advance a call's frontier are a
poor fit. This skill is a fit / venue-selection / re-framing tool. It does not
replace the journal's current official author guidelines or any call's specific
instructions. Before submitting, re-check the live JSAC author information and the
target call for papers.
When to trigger
- The author names JSAC for a communications/networking manuscript and wants to check
fit against an active or upcoming special-issue call.
- A result must be re-framed to foreground its impact and timeliness for a particular
call's frontier theme.
- The author is choosing between JSAC (call-driven, topical) and a broad-scope
transaction (
ieee-transactions-on-communications / ieee-transactions-on-wireless-communications).
- The author needs the call-matching logic and desk-reject heuristics specific to a
special-issue venue.
Scope & topic fit
- Next-generation wireless and cellular systems, integrated sensing and communication,
non-terrestrial and massive-connectivity architectures — when matching a live call.
- Network architecture, protocols, virtualization, edge/cloud, and network management
at the systems frontier.
- Security, privacy, and trust in communication systems and networks, including
physical-layer and cross-layer security.
- Machine-learning-for-communications and communications-for-AI, where the advance is
a communications-systems contribution, not generic ML.
- Optical, quantum, molecular, and emerging communication paradigms when aligned with
a dedicated issue; route strictly by the call's stated scope and timeline.
Method & evidence bar
- The contribution must be high-impact and timely for the targeted call — a frontier
advance, not a routine increment; the call's aims-and-scope text is the rubric.
- Technical rigor still applies: analysis, simulation, and where appropriate testbed
or prototype evidence, with correct, current baselines under realistic models.
- Claims of advancing the frontier must be substantiated against the most recent
relevant work, including very recent preprints and standards activity where the
topic is fast-moving.
- System-level and cross-layer evaluation is often expected; isolated PHY tweaks
rarely match a systems-and-networks call.
- Reproducibility and clear assumptions matter as in any IEEE communications venue;
impact claims must be evidence-backed, not aspirational.
Structure & house style
- IEEE format; submissions go to a specific special issue (or, where offered, an
ongoing series) — match the manuscript to the call and re-check current article
types, limits, and deadlines on the live call page.
- The introduction must connect the work to the call's theme and articulate why it
advances that frontier now.
- Figures and evaluation should be system-level and comparative; include architecture
diagrams and end-to-end performance, not only link-level curves.
- Hard submission deadlines and guest-editor handling are typical for special issues;
confirm the timeline before preparing the manuscript.
Official-submission checklist
- Before giving submission-ready advice, read
../../resources/source-basis.md and
../../resources/official-source-map.md; start from the IEEE Author Center anchors,
then cite the current JSAC page and the specific call for papers you checked.
- Search the live site for "IEEE JSAC call for papers" and confirm the active issue,
its scope, and its submission deadline.
- Re-check article types, length/overlength policy, the IEEE template, and any
issue-specific requirements.
- Confirm reproducibility/simulation-code expectations and overlap/dual-submission
policy with sibling journals.
- Re-check ORCID, competing-interests, funding, author-contribution, and AI-use
disclosure requirements, and IEEE open-access options.
- If the live official instructions conflict with this skill, the official
instructions win.
Pre-submission self-check
Common desk-reject triggers
- Out-of-scope for every active call, or submitted after the issue deadline.
- Technically sound but routine/incremental work that does not advance the call's frontier.
- A narrow PHY-layer tweak submitted to a systems-and-networks call with no system-level contribution.
- Generic machine-learning applied to a communications dataset with no communications-systems advance.
- Impact claimed but not benchmarked against the latest relevant work in a fast-moving topic.
Re-routing decision
- Broad-scope general communications result, no matching call →
ieee-transactions-on-communications.
- Wireless-specific PHY/MAC, MIMO, channel work →
ieee-transactions-on-wireless-communications.
- Fundamental-limit/capacity theorem →
ieee-transactions-on-information-theory.
- Signal-processing method with analysis as the core →
ieee-transactions-on-signal-processing.
- Broad tutorial/survey of a communications frontier →
proceedings-of-the-ieee.
Output format
[Fit] High / Medium / Low (one-line reason)
[Target] IEEE Journal on Selected Areas in Communications
[Active call] <matched special-issue theme, or "none — re-route">
[Topic tags] <2–3 closest communications/networking subtopics>
[Impact + timeliness] <why this advances the call's frontier now>
[Top risk] <the single most likely reason for rejection>
[Deadline check] <call submission window confirmed?>
[Official items to re-check] <call scope+deadline / article type / length / disclosures>
[Re-route suggestion] <if no call matches, a better-matched venue>
Source: brycewang-stanford/Awesome-Journal-Skills → Engineering-Technology-Journal-Skills/skills/ieee-journal-on-selected-areas-in-communications/SKILL.md
1---2name: ieee-journal-on-selected-areas-in-communications3description: Use when targeting IEEE Journal on Selected Areas in Communications (JSAC) or deciding whether a communications-and-networking manuscript fits this venue. Encodes the journal's call-driven fit, the high-impact-and-topical bar, the route-by-active-call logic, house style, official-submission re-check, and desk-reject heuristics.4---5
6
7# IEEE Journal on Selected Areas in Communications (ieee-journal-on-selected-areas-in-communications)
8
9## Journal positioning
10
11IEEE Journal on Selected Areas in Communications (JSAC) publishes high-impact work at
12the systems and networks frontier of communications, organized largely around
13**topical special issues defined by current calls for papers** — next-generation
14wireless, networking, security, optical and quantum communication, and
15machine-learning-for-communications, among others. Unlike a broad-scope transaction,
16JSAC's fit is set by the active call: a paper must match a specific issue's theme and
17clear a bar of impact and timeliness, not merely be technically correct. Routine,
18incremental results — even sound ones — that do not advance a call's frontier are a
19poor fit. This skill is a **fit / venue-selection / re-framing** tool. It does not
20replace the journal's current official author guidelines or any call's specific
21instructions. Before submitting, re-check the live JSAC author information and the
22target call for papers.
23
24## When to trigger
25
26- The author names JSAC for a communications/networking manuscript and wants to check
27 fit against an active or upcoming special-issue call.
28- A result must be re-framed to foreground its impact and timeliness for a particular
29 call's frontier theme.
30- The author is choosing between JSAC (call-driven, topical) and a broad-scope
31 transaction (`ieee-transactions-on-communications` / `ieee-transactions-on-wireless-communications`).
32- The author needs the call-matching logic and desk-reject heuristics specific to a
33 special-issue venue.
34
35## Scope & topic fit
36
37- Next-generation wireless and cellular systems, integrated sensing and communication,
38 non-terrestrial and massive-connectivity architectures — when matching a live call.
39- Network architecture, protocols, virtualization, edge/cloud, and network management
40 at the systems frontier.
41- Security, privacy, and trust in communication systems and networks, including
42 physical-layer and cross-layer security.
43- Machine-learning-for-communications and communications-for-AI, where the advance is
44 a communications-systems contribution, not generic ML.
45- Optical, quantum, molecular, and emerging communication paradigms when aligned with
46 a dedicated issue; route strictly by the call's stated scope and timeline.
47
48## Method & evidence bar
49
50- The contribution must be **high-impact and timely for the targeted call** — a frontier
51 advance, not a routine increment; the call's aims-and-scope text is the rubric.
52- Technical rigor still applies: analysis, simulation, and where appropriate testbed
53 or prototype evidence, with correct, current baselines under realistic models.
54- Claims of advancing the frontier must be substantiated against the most recent
55 relevant work, including very recent preprints and standards activity where the
56 topic is fast-moving.
57- System-level and cross-layer evaluation is often expected; isolated PHY tweaks
58 rarely match a systems-and-networks call.
59- Reproducibility and clear assumptions matter as in any IEEE communications venue;
60 impact claims must be evidence-backed, not aspirational.
61
62## Structure & house style
63
64- IEEE format; submissions go to a specific special issue (or, where offered, an
65 ongoing series) — match the manuscript to the call and re-check current article
66 types, limits, and deadlines on the live call page.
67- The introduction must connect the work to the call's theme and articulate why it
68 advances that frontier now.
69- Figures and evaluation should be system-level and comparative; include architecture
70 diagrams and end-to-end performance, not only link-level curves.
71- Hard submission deadlines and guest-editor handling are typical for special issues;
72 confirm the timeline before preparing the manuscript.
73
74## Official-submission checklist
75
76- Before giving submission-ready advice, read `../../resources/source-basis.md` and
77 `../../resources/official-source-map.md`; start from the IEEE Author Center anchors,
78 then cite the current JSAC page and the specific call for papers you checked.
79- Search the live site for "IEEE JSAC call for papers" and confirm the active issue,
80 its scope, and its submission deadline.
81- Re-check article types, length/overlength policy, the IEEE template, and any
82 issue-specific requirements.
83- Confirm reproducibility/simulation-code expectations and overlap/dual-submission
84 policy with sibling journals.
85- Re-check ORCID, competing-interests, funding, author-contribution, and AI-use
86 disclosure requirements, and IEEE open-access options.
87- If the live official instructions conflict with this skill, the official
88 instructions win.
89
90## Pre-submission self-check
91
92- [ ] The manuscript matches a specific active call's theme, scope, and timeline.
93- [ ] The contribution is framed as a high-impact, timely frontier advance, not a routine increment.
94- [ ] Frontier claims are substantiated against the most recent relevant work, including recent preprints/standards.
95- [ ] Evaluation is system-level/cross-layer where the call expects it, with matched, current baselines.
96- [ ] The JSAC (call-driven) vs. broad-transaction choice is deliberate and justified.
97- [ ] Article type, length, and the call's deadline are confirmed on the live page.
98
99## Common desk-reject triggers
100
101- Out-of-scope for every active call, or submitted after the issue deadline.
102- Technically sound but routine/incremental work that does not advance the call's frontier.
103- A narrow PHY-layer tweak submitted to a systems-and-networks call with no system-level contribution.
104- Generic machine-learning applied to a communications dataset with no communications-systems advance.
105- Impact claimed but not benchmarked against the latest relevant work in a fast-moving topic.
106
107## Re-routing decision
108
109- Broad-scope general communications result, no matching call → `ieee-transactions-on-communications`.
110- Wireless-specific PHY/MAC, MIMO, channel work → `ieee-transactions-on-wireless-communications`.
111- Fundamental-limit/capacity theorem → `ieee-transactions-on-information-theory`.
112- Signal-processing method with analysis as the core → `ieee-transactions-on-signal-processing`.
113- Broad tutorial/survey of a communications frontier → `proceedings-of-the-ieee`.
114
115## Output format
116
117```text
118[Fit] High / Medium / Low (one-line reason)
119[Target] IEEE Journal on Selected Areas in Communications
120[Active call] <matched special-issue theme, or "none — re-route">
121[Topic tags] <2–3 closest communications/networking subtopics>
122[Impact + timeliness] <why this advances the call's frontier now>
123[Top risk] <the single most likely reason for rejection>
124[Deadline check] <call submission window confirmed?>
125[Official items to re-check] <call scope+deadline / article type / length / disclosures>
126[Re-route suggestion] <if no call matches, a better-matched venue>
127```
128
129---
130
131**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Engineering-Technology-Journal-Skills/skills/ieee-journal-on-selected-areas-in-communications/SKILL.md`