Skip to main content
Publications lead hero image abstract pattern


Publication Date


Manuscript Submission Deadline



Call for Connected Vehicles Articles

The IEEE Internet of Things Magazine (IEEE IoTM) is currently soliciting articles for its vertical area on Connected Vehicles. Vehicles, as multi-faceted IoT objects, equipped with on board sensors (radar, camera, positioning receiver) and storage, processing and communication capabilities, are revolutionizing the future of private and public transportation, by enabling green traffic management, intelligent vehicle control, safe and comfortable driving. Connected vehicles are capable of autonomously exchanging kinematics parameters, sensed data, and driving intentions to coordinate their maneuvers, and to send diagnostics and maintenance information to the cloud servers of manufacturers. Vehicles can as well provide passengers with navigation services and other traffic telematics applications, along with on-demand video streaming and online Internet access. This vertical includes but is not limited to intelligent transportation and connected aerial vehicles among others.

Articles revolving around this vertical area should discuss:

  • A high-level operational description of the proposed solution for connected vehicle service, addressing the identified need for the presented solution, the addressed vehicular application(s) and use cases:
    • What is the addressed vehicular service (e.g., road safety, entertainment, traffic efficiency)?
    • What is the addressed vehicular application and use case (e.g., platooning, cooperative sensing, cooperative maneuvering, Internet access, vulnerable road user protection)?
    • What are the building blocks lying at the core of the designed connected vehicle- based solution that will enable such a service?
    • What issues the proposed solution intends to solve or to mitigate?
    • What are the high-level expectations of achievements for the proposed solution?
  • A high-level technical description of the proposed solution, e.g., by specifying the communication, sensing, and processing capabilities needed to set up the solution on board and at the infrastructure:
    • What are the technical challenges that the proposed solution intends to face throughout the design, implementation and deployment of the connected vehicle-based solution to enable the provisioning of the considered service and support its efficient and effective operation?
    • Which technologies and capabilities are needed on board the vehicle and at the network and roadside infrastructure to realize the proposed connected-vehicle solution?
    • What is the level of vehicle automation involved in the solution?
    • What are the technical risks underlying the provisioning of the considered service as well as the feasibility and costs of implementation and deployment of its enabling solution?
  • An insightful discussion and elaboration of the novel findings:
    • Which metrics are used to evaluate if the solution is provisioned successfully? How these metrics are measured?
    • How is the outcome differing from other alternative solutions? Are the achieved gain and the necessary costs acceptable in the context of real-world connected vehicle scenarios?
    • What are the limits of the proposed solution?
  • A summary of the business case(s) for connected vehicle service operation:
    • Who are the stakeholders?
    • What role do the drivers and passengers play in the solution definition and testing?
    • What role do the automotive makers and the network operator play in the solution definition and testing?
    • What benefits were anticipated and received from the solution? How were the benefits measured?
    • Was the user experience tested?
    • Were any policy or regulatory issues encountered?
    • Were any ethical, social or legal issues encountered?
  • Lessons learned from planning, designing, prototyping, implementation, deployment and operation:
    • What were the key lessons learned?
    • Can this experience contribute to defining best practices?
    • What were the risks and rewards?

Articles could present real-world experiences with projects integrating connected vehicles or preliminary testbeds for future visions thereof. Authors should keep in mind that the intended audience consists of all the members of the IoT community. Hence, articles must be understandable by the general IoT practitioner/researcher, independent of technical or business specialty and are expected to add to the knowledge base or best practices of the IoT community. Mathematical material should be avoided; instead, references to papers containing the relevant mathematics should be provided when applicable.

In addition to the above, the IEEE IoTM general author guidelines for manuscript development and submission over manuscript central must be carefully abided by.

Note: IoTM does not have a specific template and does not require manuscripts to be submitted in any specific layout. However, authors can use the template for IEEE Transactions to get a rough estimate of the page count.