Working group

Working Group 2 shall develop the overall architecture and address cross (OSI) layer issues. In particular this includes:

• ITS Architecture

• Communications Architecture

• Cross Layer Issues

• Separation of Service Provision from Medium provision

• Methodology is to use different viewpoints or perspectives, e.g. user, standardization, network, security, operation, implementation

Working Group 3 shall develop ETSI deliverables for the data transport and network protocol layers and management of these layers.

In particular this includes:

• Development of a network architecture which covers existing and future wireless and wired technologies and various application services for any kind of ITS users, including vehicle drivers and passengers, railway users, pedestrians, bicyclists and other; 
• Harmonization of the network architecture with the overall ITS system and protocol architecture;
  Development of novel networking protocols for ITS, such as ad hoc and multi-hop routing protocols, reliable transport protocols over multi-hop routing, and others; 
• Integration of dedicated ITS network protocols and transport protocols with the Internet protocol suite and IP mobility extensions; 
• Work out solutions for internetworking between access networks; 
• Ensuring that the networking and data transport protocols and algorithms 

o Are efficient, scalable and reliable; 
o Protect the user's privacy and ensure security;  

Working Group 4 shall encompass ITS standardization on OSI model layers 1 and 2 including the management of these layers. WG 4 may have subgroups for each of the core subject areas.

Core subject areas currently identified are:

• ERM Liaison/participation with regard to ERM scoped issues. WG 4 is the responsible group inside TC ITS for the development of ETSI system reference documents for ITS 
• 5 GHz 
• 60 GHz 
• Infra-red CEN RTTT DSRC 
• ISO CALM (21212 and 21213) 2G / 3G

WG 4 may have joint meetings with TC ERM TG37 and liaise on media related subjects to TC ERM TG37 directly. 

Working Group 5 shall be responsible for:

• Conducting studies leading to deliverables on Security; 
• Assuring ITS solutions conform to regulatory requirements for privacy, data protection, lawful interception and data retention; 
• Management and co-ordination of the development of security specifications for ITS communication and data; 
• Investigation of security services and mechanisms required for providing ITS services over the Internet; 
• Development of security analyses of candidate protocols and network elements to be used within the ITS framework to implement capabilities e.g., EMTEL aspects, IPv6 migration, keying strategies and methods; 
• Tracking ongoing worldwide security activities of interest to ITS (notably in ISO TC204)

Working Group 5 shall undertake activities including, but not restricted to:

• Determine and document the objectives and priorities for ITS security taking into account the needs and aspirations of users, operators, regulators and manufacturers (primarily building a secure Service Capability invocation and protection model). 
• Accommodate, as far as is practicable, any regional regulatory requirements in security objectives. This includes regional regulatory requirements that are related to the processing of personal data and privacy. 
• Ensure that a threat analysis for ITS is conducted and maintained as the feature set being standardised grows. 
• Detail the security requirements for ITS to include, but not necessarily be limited to, security requirements for services, user access to services, billing and accounting, operations and maintenance, and fraud control. 
• Detail the security requirements for the physical elements of ITS deployments to include, but not necessarily be limited to, security requirements for the access network, the core network and its interfaces to legacy networks and terminals. 
• Define a security architecture for ITS which will satisfy the security requirements and align with the ITS system architecture. 
• Produce specifications for: 

 o All the elements in the security architecture. 
 o Operations and management of the security elements.
   o Any cryptographic algorithms needed for the security elements. 

• Ensure the availability of any cryptographic algorithms which need to be part of the common specifications (via SAGE for example). 
• Define how the specifications for the security elements are to be integrated into the access network, core network, terminal, O&M and other relevant specifications produced for ITS, and to assist with that integration. Detail the requirements for lawful interception in ITS, and produce all specifications needed to meet those requirements. This work shall be performed in conjunction with TC LI to ensure handover capabilities exist sufficient to support the intercepted material. 
• Produce a time and milestones plan for the introduction of the various elements of the security architecture which is in line with the development of other relevant elements of ITS. 
• Produce guidelines on the use of the ITS security elements, including any requirements for operator specific algorithms. 
• Produce guidelines on the limitations of ITS security, and of the implications of not activating the security elements that are provided.

In addition, security services and mechanisms for providing services over the Internet will continue to be investigated. It is important to realize that security for open networks and for interoperability is challenging. 

Preparation of a first draft business plan - Review the task list ( N08) provided by the CEN-CLC Cybersecurity Coordination Group (CSCG) and asses how these tasks could be taken up in the upcoming TC 13 work

The WG considers national and international standards for adoption in the domain of management system standards including supporting control sets covering information and cyber security. Where not being developed by other SDO's, the WG may develop CEN/CENELEC publications in this domain.

Security evaluation and assessment

Cybersecurity services

The present document specifies the structure of the Network Service Descriptor (NSD) file archive and the naming conventions for the different files it contains, fulfilling the requirements specified in ETSI GS NFV-IFA 014 [1] for an NSD file structure.

With the advent and rise of AI there is a risk that machine-to-machine decisions will be made with black-box inputs determined without input transparency to humans. In order to enable ethics-based AI, individuals will require the means to influence and determine the values, rules and inputs that guide the development of personalized algorithms and Artificial Intelligence. They will need an agent that can negotiate their individual rights and agency in a system of shared social norms, ethics and human rights that also foresee and helps the individual mitigate ethical implications of data processing. This approach will enable individuals to safely organize and share their personal information at a machine-readable level and enable a personalized AI to act as a proxy for machine-to-machine decisions. A key goal for the creation of this standard is to educate government and commercial actors why it is in their best interests to create the mechanisms for individuals to train Personal AI Agents to move beyond asymmetry and harmonize personal data usage for the future.

Standard: P7006 - Standard for Personal Data Artificial Intelligence (AI) Agent

Description: This standard describes the technical elements required to create and grant access to a personalized Artificial Intelligence (AI) that will comprise inputs, learning, ethics, rules and values controlled by individuals.

Development Status: Under development

Experiential Networked Intelligence (ENI)- Terminology for Main Concepts in ENI

Experiential Networked Intelligence (ENI); Proof of Concepts Framework