Skip to content
16th International Conference on Intelligent Transport Systems Telecommunications 15 to 17 October 2023 · Lisbon, Portugal Conference record
ITST 2023 Transport communications Plan your visit

Demonstrations

Put the system on the table

The demo session was the part of the programme where a claim had to be shown rather than described.

2 Pages for a demo abstract

Demo session

01

What the session was for

A conference paper can hide a fragile system. A demonstration cannot. The demo session gave research projects, startups and established companies a place to show a working prototype and let other specialists look at it directly.

The scope matched the main call. A demo could address any part of transport communications: a radio link, a positioning method, a network service, a cooperative application or a test tool that makes another result possible.

The session was not a trade fair. The point was technical exchange, and the best work was the kind that made another researcher ask a harder question.

Who could submit. Research projects, startups and industry teams were all invited to send an abstract describing a working prototype within the scope of the call.
What counted. A demonstration had to go beyond a slide. The abstract needed to explain what the system does, what is new and what a visitor would see.
02

The route from abstract to floor

Submissions were made through the conference system and limited to two pages in the conference template. Review used the same two tests as the main call: scientific merit and novelty.

Accepted demos were given a two minute pitch in a dedicated session. That short window forced teams to state the problem, the intervention and the evidence without the usual buildup.

The call directed abstracts that were accepted and then presented to IEEE Xplore, with EI indexing. A best demo award recognised merit, novelty and the quality of the pitch.

What reviewers could judge from an abstract

Whether the problem is real, whether the system is genuinely working, whether the advance is clear and whether the team can explain it without the hardware in front of them.

What the two minute pitch had to cover

The transport problem, the communications method, the state of the prototype and the result that can already be shown. A longer history of the project is usually less useful than one clear measurement.

Why presentation was part of publication

The publication route named in the call applied to accepted and presented abstracts. A demo listed in the programme but not shown on the floor would not meet that condition.

How the demo differed from a poster

A poster explains a result and invites discussion. A demo runs. The audience expects to see input, output and failure modes, not only a diagram of them.

03

Demo dates

  • 1 June 2023Demo abstract submission
  • 1 July 2023Notification of acceptance
  • 22 July 2023Camera ready version due
  • 27 July 2023Author registration and payment due
Separate from the paper. A demo abstract did not require a full paper, and a full paper did not guarantee a demo place. Each route had its own review.

Teams that also submitted a paper could use the demo to show the implementation behind the result, but the abstract still had to stand on its own.

04

What a good demo made visible

A visitor should be able to answer four questions within a few minutes: what is moving, what is communicating, what changes when the link works, and what happens when it fails.

That last question matters most in transport. A system that only performs under ideal radio conditions is a laboratory result. A system that degrades in a way an operator can understand is closer to something deployable.

The edition put demonstrations alongside papers for exactly that reason. The conversation between the two is where a research community tests its own confidence.

Reference shelf

External sites are listed for context and are not controlled by the conference record.