SP7 – SCORE – SAFESPOT Core Architecture SAFESPOT ... · ATCRF Automobile Telematics Certification Reference Framework ... Reference List TCS Telephony Control ... System Core

Deliverable N. 7.4.3 – Part A Dissemination Level PU Copyright SAFESPOT

Contract N. IST-4-026963-IP

SF_D7.4.3_SCRF-Part A_v1.3.doc Page 1 of 77 SCORE

SAFESPOT INTEGRATED PROJECT - IST-4-026963-IP

DELIVERABLE

SP7 – SCORE – SAFESPOT Core Architecture

Deliverable No. (use the number indicated on technical annex)

D7.4.3

SubProject No. SP7 SubProject Title SCORE

Workpackage No. WP4 Workpackage Title Exploitation Convergence & Certification

Task No. T7.4.2 Task Title ITS Cooperating System Certification Approach

Authors (per company, if more than one company provide it together)

Main Authors:

A. Plaza, F.J. Nuñez, J. Baños (AT4 wireless)

Status (F: final; D: draft; RD: revised draft): F

Version No: 1.3

File Name: SF_D7.4.3_SCRF-Part A_v1.3

Planned Date of submission according to TA: 25/05/2007

Issue Date: 01/12/2009

Project start date and duration 01 February 2006, 48 Months

SAFESPOT Certification Reference Framework – Part A




Revision Log

Version Date Reason Name and Company

1.0 2007-05-25 First Release A. Plaza, F J. Nuñez, J. Baños (AT4 wireless)

1.1 2008-04-24 Final Version after Peer Review

A. Plaza, F J. Nuñez, J. Baños (AT4 wireless)

1.2 2008-10-29 EU reviewers comments included


1.3 2009-12-01 EU reviewers from 3rd review meeting included





Abbreviation List

AP Access Point

ASD Application Specific Device

ATCRF Automobile Telematics Certification Reference Framework

A2DP Advanced Audio Distribution Profile

AT Attention

ATCRF Automobile Telematics Certification Reference Framework

ATL Authorized Test Laboratory

ATS Abstract Test Suite

ATSO Automobile Telematic Stakeholders Organization (ATSO)

AVDTP A/V Distribution Transport Profile

AVRCP A/V Remote Control Profile

BB Base Band

BIP Basic Image Profile

BNEP Bluetooth Network Encapsulation Protocol

BPP Basic Printing Profile

BQA Bluetooth Qualification Administrator

BQB Bluetooth Qualification Body

BQE Bluetooth Qualification Expert

BQRB Bluetooth Qualification Review Board

BQTF Bluetooth Qualification Test Facility

BRTF Bluetooth Recognized Test Facility

BS Base Station

BSS Basic Service Set

BTAB Bluetooth Qualification Review Board

C2C – CC Car to Car Communication Consortium

C2I Car to Infrastructure

CA Certification Authority

CB Certification Bodies

CCTV Closed Circuit Television

CE Consumer Electronics

CEN Commitee European of Normalization

CPS Common Part Sub-Layer

CRB Certification Review Board

CSMA-CA Carrier Sense Multiple Access with Collision Avoidance

CTP Cordless Telephony Profile




CTT Conformance Test Tool

CVIS Co-operative Vehicle-Infrastructure Systems (IP project, IST 027 293)

CWG Certification Working Group

D2G Designed To Guidelines

DECT Digital Enhanced Cordless Telecommunications

DLNA Digital Living Network Alliance

DMC Digital Media Controller

DMD Digital Media Downloader

DMP Digital Media Player

DMPr Digital Media

DMR Digital Media Renderer

DMS Digital Media Server

DMU Digital Media Uploader

DoC Declaration of Compliance

DS Direct Sequence

DSRC Dedicated Short Range Communications

DSSS Direct Sequence Spread Spectrum

DUN Dial-Up Networking

EAP Extensible Authentication Protocol

EC European Commission

ECMA European Computer Manufacturers Association

ECN Engineering Changes Notes

EEC European Economic Community

EFCD Enhanced Floating Car Data

EFTA European Free Trade Association

EITSFA European Intelligent Transport Systems Framework Architecture

EMC Electromagnetic Compatibility

ESA Electronic Sub Assemblie

ETSI European Telecommunications Standards Institute

FDD Frequency Division Duplex

FFD Full Function Device

FSD Full Set of Data

FSS Fixed Satellite Service

FTP File Transfer Protocol

GAVDP Generic A/V Distribution Profile Specification

GPRS Global Personnel Recovery System

GPS Global Positioning System




GSM Global System for Mobile

GST Global System for Telematics (IP project)

HCI Host Controller Interface

HCRP Hardcopy Cable Replacement Profile

HFP Hands-Free Profile

HID Human Interface Device

HLCMP High Level Certification Master Plans

HND Home Network Device

HSP Headset Profile

IBSS Independent Basic Service Set

ICP Intercom Profile

ICS Implementation Conformance Statement

ICV Independent Certification Vendor

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IP Internet Protocol

ISA Industry Standard Architecture

ISM Industrial, Scientific and Medical

ISO International Organization for Standardization

ITL Independent Test Lab

ITS Intelligent Transportation Systems

ITU International Telecommunication Union

IUT Implementation Under Test

L2CAP Logical Link Control and Adaptation Protocol

LOS Line of Sight

MAC Medium Access Control

MBOA Multiband OFDM Alliance’s

MES Mobile Earth Stations

MHD Mobile handheld Device

MIB Management Information Base

MIU Media Interoperability Unit

M-NCF Mobile Network Connectivity Function

MSD Minimum Set of Incident

NDA Non-Disclosure Agreement

NFC Near Field Communication

OBEX Object Exchange Protocol




OFDMA Orthogonal Frequency Division Multiplexing

OPP Object Push Profile

OSI Open System Interconnection

PAN Personal Area Network

PCT Protocol Conformance Tester

PICS Protocol Implementation Conformance Statement

PDA Personal Digital Assistant

PHY Physical Layer

PIXIT Protocol Implementation eXtra Information for Testing

PRD Program Reference Document

PSAP Public Safety Answering Point

PTS Profile Tuning Suit

QDL Qualified Designed List

QLI Qualification List Interface

QPL Bluetooth Qualified Product List

RCT RadioConformance Tester

RF Radio Frecuencia

RFD Reduced Function Device

ROMES Receive Only Mobile Earth Stations

SC Safety Channel

SCORE SAFESPOT CORE architecture

SDAP Service Discovery Application Profile

SDP Service Discovery Protocol

SIG Special Interest Group

SIM Subscriber Identity Module

SLA Service Level Agreement

SLS System Level Specification

SMA Safety Margin Assistance

SoA State of Art

SOAP Simple Object Access Protocol

SP Sub Project

SPP Serial Port Profile

SS Subscriber Station

STU Separate Technical Unit

SUT System Under Test

SYNC Synchronization Profile

TCA Telematics Certification Authority




TCAB Telematics Certification Advisory Board

TCAP Transaction Capabilities Application Part

TCMT TC Mapping Table

TCRL Test Case Reference List

TCS Telephony Control Specification

TDD Time Division Duplex

TETRA Terrestrial Trunked Radio

TFC Technical Construction File

TIB Telematic Inspection Bodies

TP Test Purpose

TPEG Transport Protocol Expert Group

TPG Test Plan Generator

TS Test Site

TSS Test Suite Structure

TTCN-3 Testing and Test Control Notation

TTL Telematic Test Laboratory

TWG Technical Working Group

UML Unified Modelling Language

UMTS Universal Mobile Telecommunications System

UPL Upper Layer Protocol

UWB Ultra Wide Band

V2I Vehicle to Infrastructure

V2V Vehicle to Vehicle

VANET Vehicle Ad Hoc Network

VDP Video Distribution Profile

VGU VANET Golden Unit

VUT VANET module Under Test

WAVE Wireless Access in Vehicular Environments

WCS Web Certification System

WFA Wi-Fi Alliance

WFDCL WiMAX Forum Designated Certification Laboratory

WiMAX Worldwide Interoperability for Microwave Access

WLAN Wireless Local Area Network

WP Work Package

WPA Wi-Fi Protected Access

WPAN Wireless Access in Vehicular Environments

WPS Wi-Fi Protected




ZCP ZigBee Compliant Platform

ZID ZigBee ID




Table of contents Revision Log ............................................................................................................................................2 Abbreviation List......................................................................................................................................3 Table of contents ......................................................................................................................................9 List of Figures ........................................................................................................................................10 EXECUTIVE SUMMARY ....................................................................................................................11 1. Introduction ....................................................................................................................................12 2. Basic concepts ................................................................................................................................13 3. Relevant certification approaches worldwide.................................................................................15

3.1. Bluetooth certification.........................................................................................................15 3.1.1. Bluetooth technology......................................................................................................15 3.1.2. Certification scheme .......................................................................................................18

3.2. WiMAX certification ..........................................................................................................25 3.2.1. WiMAX technology .......................................................................................................25 3.2.2. Certification scheme .......................................................................................................27

3.3. Wi-Fi certification ...............................................................................................................32 3.3.1. Wi-Fi technology............................................................................................................32 3.3.2. Certification scheme .......................................................................................................34

3.4. DLNA certification..............................................................................................................39 3.4.1. DLNA technology ..........................................................................................................39 3.4.2. DLNA Certification scheme ...........................................................................................43

3.5. ZigBee certification.............................................................................................................46 3.5.1. ZigBee technology..........................................................................................................46 3.5.2. ZigBee Certification scheme ..........................................................................................50

3.6. UWB certification ...............................................................................................................53 3.6.1. UWB technology ............................................................................................................53 3.6.2. WiMedia-UWB Certification scheme ............................................................................55

4. The GST-CERTECS certification approach: ATCRF....................................................................58 4.1. Introduction to GST architecture.........................................................................................58

4.1.1. GST High Level Architecture.........................................................................................58 4.1.2. GST technology basics ...................................................................................................59 4.1.3. GST Reference models and protocol stacks ...................................................................60

4.2. Certification scheme (ATCRF) ...........................................................................................62 4.2.1. GST Certification main players ......................................................................................63 4.2.2. Detailed certification process..........................................................................................65 4.2.3. Product Classes...............................................................................................................65 4.2.4. Conformity Assessment Modules...................................................................................66 4.2.5. Certification Steps ..........................................................................................................67

5. Automotive Regulatory Procedure .................................................................................................69 5.1. EC Directives ......................................................................................................................70 5.2. EMC Directives...................................................................................................................71 5.3. Automotive EMC Directives Applicability .........................................................................72 5.4. e-marking ............................................................................................................................74

6. Conclusions ....................................................................................................................................76 7. References ......................................................................................................................................77




List of Figures Figure 1.Elaborating a SAFESPOT certification process ..............................................................12 Figure 2.Access to the market for Bluetooth Products...................................................................16 Figure 3. Bluetooth Communication Topologies .............................................................................17 Figure 4. Bluetooth Protocol Stack and Profiles..............................................................................17 Figure 5. Bluetooth Qualification Process for PRD 1.0 ..................................................................21 Figure 6. Detailed Bluetooth Qualification Process for PRD 1.0 ..................................................22 Figure 7. Bluetooth Qualification Process for PRD 2.0 ..................................................................23 Figure 8. Detailed Bluetooth Qualification Process for PRD 2.0 ..................................................24 Figure 9. WiMAX (802.16) Reference Model...................................................................................26 Figure 10. WiMAX Certification Testing Stakeholders ...................................................................28 Figure 11. WiMAX Certification Testing Overall Process ..............................................................30 Figure 12. WiMAX Forum Certification Testing Process ...............................................................31 Figure 13. Vehicular Environment using IEEE 802.11p.................................................................33 Figure 14. Wi-Fi Protocol Stack .........................................................................................................34 Figure 15. Wi-Fi Certification Process ..............................................................................................37 Figure 16. CE, PC-Internet, Mobile and CE Domains ....................................................................39 Figure 17. DLNA Functional Components and Technologies.......................................................40 Figure 18. DLNA Device Classes......................................................................................................42 Figure 19. DLNA Protocol Stack........................................................................................................42 Figure 20. DLNA Certification Process.............................................................................................45 Figure 21. DLNA Certification Evolution...........................................................................................46 Figure 22. ZigBee Alliance Applications...........................................................................................47 Figure 23. ZigBee Topologies............................................................................................................49 Figure 24. ZigBee Certification Process...........................................................................................52 Figure 25. Automobile Telematic System ........................................................................................58 Figure 26. eCall Reference Model ....................................................................................................60 Figure 27. V2V Reference Model ......................................................................................................61 Figure 28. EFCD Reference Model...................................................................................................62 Figure 29. ATCRF Organizational Model .........................................................................................65 Figure 30. Tests and Inspection Plans .............................................................................................68 Figure 31. Certification Process ........................................................................................................69




EXECUTIVE SUMMARY The main objective of SP7 SAFESPOT Core Architecture (SCORE) is the definition of a System Core Architecture to be used as a reference across Europe for both the development of new ITS safety services and the development of applications increasing the ITS traffic efficiency. The main activities of SCORE are:

− The specification of a high level architecture, that will consider all possible applications (safety and traffic efficiency) and technologies coming from SAFESPOT, C2C-C (Car to Car Communication) Consortium and other relevant European research projects.

− The detailed specification of SAFESPOT reference system architecture, with particular focus on local area vehicle-vehicle-infrastructure network (based on C2C-C technology and protocols) as communication infrastructure.

− The definition of architectural guidelines to design and develop vehicle and road side infrastructure platforms (contribution to other SPs (Sub Project)).

− The definition of certification areas and associated certification modules as elements of validation for the SPs contributing to the implementation of the SAFESPOT reference system architecture.

The present deliverable focuses on this last topic: the definition of a certification reference framework for SAFESPOT. Safety applications enabled by the C2C and C2I (Car to Infrastructure) wireless communication networks require the certification that the proposed services and products implementations are conforming to strict quality requirements (reliability, dependability, security, full interoperability, performance, EMC, etc.).

The certification is the retained way to check this conformance against the SAFESPOT certification reference framework derived from GST and enhanced / extended by SAFESPOT. The SAFESPOT Certification will define a framework to fulfil this procedure. The certification procedure will collect the most appropriate concepts and approaches from other certification procedures worldwide (GST-CERTECS, DLNA, Wi-Fi, Bluetooth, WiMAX and so on).

The Deliverable D.7.4.3 named “SAFESPOT Certification Reference Framework” has been divided in two complementary parts:

− Part A (this document). This part contains an introduction to the most relevant certification programs worldwide for different technologies. It includes an overview of the certification programs for Bluetooth, Wi-Fi, WiMAX, DLNA (Digital Living Network Alliance), ZigBee, WiMedia-UWB and GST-CERTECS. Moreover, regulatory certification focused on automotive environment is also described.

− Part B. This part will include the actual definition of the SAFESPOT Certification Reference Framework describing the elements to be under certification, the main stakeholders involved in the certification, the certification process, etc.




1. Introduction This document intends to provide an introduction to the most relevant certification programs worldwide for different technologies. It includes an overview of the certification programs for Bluetooth, Wi-Fi, WiMAX, DLNA, ZigBee, WiMedia-UWB intending to cover the most important technologies used both in vehicles (SAFESPROBE subproject) and in infrastructure (INFRASENS subproject). Moreover, an overview of automotive certification program is shown through GST-CERTECS and European regulatory directives.

The goal is to elaborate a proper certification procedure to SAFESPOT using previous experiences and capturing the most appropriate concepts and thoughts. As well, these certification programs for different technologies worldwide have been described for a better understanding of how a certification scheme behaves.

This description includes:

− Brief introduction to the technology and main applications.

− Main players (stakeholders) involved in the certification scheme.

− Elements under certification.

− Detailed description of the certification process.

Figure 1.Elaborating a SAFESPOT certification proce ss




2. Basic concepts For the purposes of the present document, the following definitions and concepts apply:

Accreditation: The act of granting credit or recognition.

Accreditation body: An organization that assesses the qualifications and capabilities of certifiers (certification bodies) to operate independently and reliable. It verifies their competence and controls their operation. The accreditation body shall accredit independent entities (certification bodies, test houses, etc.) in accordance with standards and procedures (e.g., ISO 17025).

Certify: To state something officially, usually in writing, especially that something is true or correct.

Certification: Confirmation that some fact or statement is true. It can be also defined as the procedure through which an official designation is obtained often involving standardized testing.

Certification body: A third party that assesses and certifies with respect to standards. It is an impartial organization possessing the necessary competence to operate a certification program.

Test Laboratory: An organization that carries out conformance and/or interoperability testing. This can be a third party, a user organization, a telecommunications administration or recognized private operating agency, or an identifiable part of a supplier organization.

Self-certification: An official statement that you make about yourself.

Testing: The execution of tests with the intent of providing that the system and application under test does or does not perform according to the requirements specification.

Conformance testing: Testing the extent to which an IUT is a conforming implementation. Conformance Testing checks whether an implementation is implemented correctly with respect to the requirements stated in the relevant standard or specification. The purpose of Conformance testing is to determine to what extent a single implementation of a particular standard conforms to the individual requirements of that standard.

Interoperability testing: Activity of proving that end-to-end functionality between (at least) two communicating systems is as required by the base standard(s) on which those systems are based.

Plugfest: It refers to events where engineers get together to test the interoperability of their implementations between each other.

Standardization: The process needed to produce Standards.

Standardization body: It is any entity whose primary activities are developing, coordinating, promulgating, revising, amending, reissuing, interpreting, or otherwise maintaining standards that address the interests of a wide base of users outside the standards development organization.




Standards: They are produced by many organizations (or groups of cooperating entities), some for internal usage only, others for use by groups of people, groups of companies, or an entire industry. They form interest groups, that obtain mutual gains in a coordinated action if they ensure a "group-wide" uniformity in a measure (for comparative evaluations), or in a technical reference level of quality or attainment.




3. Relevant certification approaches worldwide In this section, some relevant and existing certification schemes for other technologies worldwide are described for a better understanding of how a certification scheme must work. This description includes a brief introduction to the technology, main applications, main players involved in the certification scheme and a detailed description of the certification process.

The following technologies have been selected:

− Bluetooth.

− WiMAX.

− Wi-Fi.

− DLNA.

− ZigBee

− WiMedia-UWB

3.1. Bluetooth certification

3.1.1. Bluetooth technology

3.1.1.1. Main applications and main players

Bluetooth1 wireless technology is a very popular wireless technology due the fact that it is a powerful ad-hoc networking technology for short ranges.

The Bluetooth SIG (Special Interest Group) is comprised of more than 8,000 member companies and a small staff. The main tasks for the Bluetooth SIG are to publish Bluetooth specifications, administer the qualification program and protect the Bluetooth trademarks. Bluetooth wireless technology is the simple choice for convenient, wire-free, short-range communication between devices.

Bluetooth technology is being used primarily as a replacement of cables between electronic devices, as in Wireless Personal Area Networks (WPANs), or for connecting the components of a computer system (hubs, printers, keyboards, etc).

The most important Bluetooth wireless technology applications are:

− Communication devices: mobile units, cordless and wall phones, etc.

− Computing devices: laptops, keyboards, mouse, printers, scanners, etc.

1 Bluetooth, the Bluetooth Figure Mark, and the Bluetooth Combination Mark are registered trademarks owned by Bluetooth SIG, Inc.




− Consumer devices: digital cameras, palms, PDAs (Personal Digital Assistant), headsets, watches, radios, MP3 players, etc.

− Commercial and industrial devices: sensors, robots, etc.

As part of the membership agreement, Bluetooth SIG members get the rights to incorporate Bluetooth wireless technology into products, use the technology to offer goods and services or simply rebranding a product with Bluetooth technology provided they complete the qualification process. As with any other radio technology, products must conform to local regulations.

Figure 2.Access to the market for Bluetooth Product s

3.1.1.2. Bluetooth wireless technology basics Bluetooth wireless technology operates in the unlicensed 2.4 GHz ISM (Industrial Scientific Medical) band. The frequency band is 2400-2835 MHz. Bluetooth devices share 79 channels of 1 MHz within the 2.4 GHz band and have a typical range between 10 to 100 meters.

Bluetooth wireless technology provides a short-range radio link capable of transmitting simultaneously voice and data (up to 3 Mbps).

3.1.1.3. Bluetooth communication topologies

Bluetooth wireless enabled electronic devices connect and communicate wirelessly through short-range, ad hoc networks known as “piconets”. Each device can simultaneously communicate with up to seven other devices within a single piconet. Piconets are established dynamically and each device can also belong to several piconets simultaneously setting a “scatternet”.




Master

Slave 1

Slave 2 Master Slave 1

Piconet - A Piconet - B

Master

Slave 1

Slave 2 Master Slave 1

Piconet - A Piconet - B

Slave 2Piconet

Master

Slave 1 Slave 2Piconet

Master

Slave 1

Figure 3. Bluetooth Communication Topologies

3.1.1.4. Bluetooth protocol stack and profiles

The Bluetooth protocol stack and profiles are described in the figure below.

Figure 4. Bluetooth Protocol Stack and Profiles 2

The Bluetooth specification defines “usage models”. Usage models describe different kind of scenarios for Bluetooth wireless technology. Some examples are: serial port emulation, headset, dial-up networking, file transfer, fax, etc. 2 The acronym explanation is included in Abbreviation List Section.




Each usage model is accompanied by a “profile”. Then, a profile defines a set of protocols and protocol features to support a particular usage model.

3.1.2. Certification scheme

3.1.2.1. Bluetooth certification players Qualification is a necessary pre-condition of the intellectual property license for the Bluetooth wireless technology. A Bluetooth device is “qualified” if it is compliant with the Bluetooth specifications and demonstrates interoperability with other Bluetooth devices. To demonstrate compliance with the Bluetooth specifications, a set of test specifications were developed. The documents needed for the Bluetooth Qualification process are described in the table below.

The first stage of Bluetooth Qualification was defined in the PRD 1.0 (Program Reference Document) [4].

The Test Case Reference List (TCRL) lists and uniquely identifies all Bluetooth Test Cases, their categories, the available and active dates and mandatory test equipment (if applicable). The technical contents of the TCRL are drafted by the Bluetooth SIG from time to time and released to the BQRB. TCRL updates occur when necessary on a quarterly release cycle.

During year 2006, the Bluetooth SIG updated its Qualification Process towards a new one: the PRD 2.0 (Current policy for Bluetooth product Qualification, effective 1 August, 2006). This new Qualification program added the following new elements:

− New Qualification Enforcement Program.

− Automated Test Plan Generator.

− New member Qualification Listing interface.

− Interoperability program enhancements.

− Profile Tuning Suite.

For the Bluetooth Qualification Program (1.0 and/or 2.0), the different players involved are described in the table below.

Documents needed for Bluetooth Qualification

Bluetooth specifications (core specification & profiles) + errata.

Program Reference Document (PRD).

Test specifications (ATS, TTCN, BB (BaseBand) test specs) and

errata.

PICS & PIXIT

TCRL (Test Case Reference List) + addendum

TCMT (Test Case Mapping Table).

DoC (Declaration of Compliance).




Player Description Applies to

Bluetooth SIG

The main tasks for the Bluetooth SIG are to publish Bluetooth specifications, administer the qualification program, protect the Bluetooth trademarks and evangelize Bluetooth wireless technology.

PRD 1.0 PRD 2.0

Bluetooth Qualification Review Board (BQRB)

A committee from the Bluetooth SIG which is in charge of the specification of the manner in which manufacturers\vendors must go about complying with the Bluetooth specifications before they are allowed to Bluetooth-brand their products and sell them.

PRD 1.0 PRD 2.0

Bluetooth Qualification Administrator (BQA)

It is the interface between the BQRB and the members of Bluetooth SIG

PRD 1.0 PRD 2.0

Bluetooth Qualification test Facility (BQTF)

It is a recognized test laboratory by the Bluetooth SIG. This organization provides testing services for Bluetooth SIG members.

PRD 1.0

Bluetooth Qualification Review Board (BTAB)

It consists of BQBs, BQTF Representatives and the BQA. The BTAB provides information and recommendations to the BQRB and advises and improves the Qualification Program.

PRD 1.0

Bluetooth Qualification Body (BQB)

It is an individual recognized by the Bluetooth SIG to perform the assessment and listing of all PRD 1.0 compliant products. The use of the BQB was mandatory.

PRD 1.0

Bluetooth Qualification Expert (BQE)

It is an individual recognized by the Bluetooth SIG to perform the assessment for qualification of all PRD 2.0 compliant products. The use of the BQE is optional although recommended by the Bluetooth SIG. Designs qualifications assessed by BQEs are not in the random audit pool

PRD 2.0

Bluetooth Recognized Test Facility (BRTF)

It is a recognized test laboratory by the Bluetooth SIG. BRTF is authorized to perform testing only in behalf of their own company.

PRD 2.0

Bluetooth Member

It is the Bluetooth SIG Member willing to obtain the Bluetooth Qualification for its device

PRD 1.0 PRD 2.0

3.1.2.2. Bluetooth qualification process

Bluetooth qualification can be defined as the process by which a Member fully demonstrates that their Bluetooth design is compliant with the requirements of the Program Reference Document. This process includes a blend of Member declarations and product testing performed by the Member or an accredited laboratory (BQTF/BRTF).

Bluetooth Qualification is limited to the following product types:

− Bluetooth End Product.




− Bluetooth Controller Subsystem Product.

− Bluetooth Host Subsystem Product.

− Bluetooth Profile Subsystem Product.

− Bluetooth Component Product3.

− Bluetooth Test Equipment.

− Bluetooth Development Tool.

For the qualification process, test requirements are classified in four categories: A, B, C and D.

Test Case Category Equipment Requirements Evidence Requirements

Category A

Validated and commercially available test equipment

approved by the Bluetooth SIG as specified in the TCRL

Cat A tests in the areas RF, BB, LM and HCI, shall be performed and

documented in a test report issued by a BQTF or BRTF. Cat A tests in all other areas can be performed by the Member

Category B Member defined test setup that meets test requirements defined

in test specifications Test setup, execution and results

Category C Member defined test setup that meets test requirements defined

in test specifications

Declaration of tests performed and test results, no other evidence required

Category D Optional tests – Member defined No evidence requirements

The main players involved in the Bluetooth Qualification process are described in the next figure.

3 If one qualified component is combined into a Bluetooth system, testing related to the functionality implemented by the component may not need to be performed.




Figure 5. Bluetooth Qualification Process for PRD 1 .0

The member shall execute a QDL (Qualified Design List) listing detailing the identity of the design and the scope of the listing.

The listing information is defined by the Bluetooth SIG and includes the necessary design and qualification information to determine whether all of the Bluetooth Qualification Requirements have been satisfied. This shall include the PICS statement information that is used to determine the qualification testing requirements. In addition it may include but is not limited to the following:

− Member name.

− Qualified design ID.

− Product type.

− Hardware and software versions.

− All applicable Bluetooth Specification versions.

− Applied PRD, TCRL, TCRL addenda and Test Case Waivers.

− Assessment Date.

− Listing date.

− Product contact persons.

The Bluetooth SIG defines the procedure for the Qualified Design Listing.

Together with execution of the listing the Member shall file the following declarations and documents with Bluetooth SIG:

− PICS.




− Test Plan.

− Test Declaration.

− Test Reports for those tests made on the product.

− Declaration of Compliance.

− Supplier Declaration of Conformity.

From the list of items above, only the ICS shall be made publicly available with the QDL.

When a Bluetooth device has successfully completed the Bluetooth qualification process, then it is identified and published in the Bluetooth Qualified Product List (QPL) for products qualified under PRD1.0 and in the Bluetooth Qualified Designs List (QLI) for designs qualified under PRD 2.0.

The main steps of the qualification process based on PRD 1.0 are described in Figure 6.

Figure 6. Detailed Bluetooth Qualification Process for PRD 1.0

The QPL/QDL is a unique recognised list of Bluetooth products that have passed successfully the Bluetooth Qualification Process.

Bluetooth End Products and Components shall be identifiable by a corresponding QPL/QDL entry.

In 2006, the PRD was updated to PRD 2.0. Aspects that differentiate PRD 2.0 from PRD 1.0 are:

− Members can, at their option, perform the listing and assessment on their own instead of using a Bluetooth Qualification Body (BQB).




− Much of the testing can be performed by the Member on its own providing they have the testing tools to perform the required testing.

− Bluetooth SIG is providing Members a new set of tools such as the TPG (Test Plan Generator), QLI (Qualification List Interface) and PTS4 (Profile Tuning Suite).

The main players for Bluetooth Qualification process based on PRD 2.0 are described in the figure below.

Figure 7. Bluetooth Qualification Process for PRD 2 .0

A transitional period was set where PRD 1.0 and PRD 2.0 rules coexisted. The main steps of the PRD 2.0 Qualification process are described in the figure below:

4 According to PRD v2.0, the “long term” plan is to perform the interoperability testing against a software tool called Profile Tuning Suite (PTS) that it has been implemented by the Bluetooth SIG.




Figure 8. Detailed Bluetooth Qualification Process for PRD 2.0

At the end of this process, members sign the DoC (Declaration of Compliance) and SDoC (Supplier Declaration of Conformity). The DoC is a written statement of the Member pertaining to product compliance with the Bluetooth Specifications; and the SDoC (Supplier Declaration of Conformity) is a declaration issued by the Member on the Assessment Date indicating that the product qualification process up to and including the assessment has been satisfied.




3.2. WiMAX certification

3.2.1. WiMAX technology

3.2.1.1. Main applications and main players WiMAX technology is providing fixed, nomadic, portable and mobile wireless broadband connectivity. WiMAX is enabling the delivery of last mile wireless broadband access and has become an alternative to DSL and cable.

It is expected that WiMAX modules will be embedded into CE (Consumer Electronics), voice and data devices, including notebooks, PDAs, Mobile PCs, games consoles, MP3 players, cellular phones and smart phones, CCTV cameras, in-vehicle subscriber stations, etc.

The key WiMAX strengths are:

− Superior performance: thanks to OFDMA technique that gives WiMAX a performance edge in delivering IP data services.

− Flexibility: allowing service providers to support many use cases and usage models for fixed and mobile access.

− All-IP based network architecture: including support for IPv6 and IMS enabling a quick adoption and inter-working with 3G and other technologies.

− Lower deployment costs: driven by a standards-based approach, cost-effective infrastructure, mass adoption of low-cost subscriber units, etc.

WiMAX technology is based on IEEE 802.16 standards:

− IEEE 802.16-2004 for Fixed WiMAX.

− IEEE 802.16e-2005 for Mobile WiMAX.

The IEEE standards govern the physical and MAC layers of the radio network but higher layers (IP, applications) are being specified by other standardization bodies such as IETF (Internet Engineering Task Force).




Figure 9. WiMAX (802.16) Reference Model

WiMAX Forum is an industry-led, non-profit corporation formed to help promote and certify the compatibility and interoperability of broadband wireless products based on WiMAX technology.

3.2.1.2. WiMAX technology basics WiMAX aims to provide wireless data over long distances, in a variety of different ways, from point to point links to full mobile cellular type access. This enables a user, for example, to browse the Internet on a laptop computer without physically connecting the laptop to a socket in a wall. The WiMAX Forum describes WiMAX as "a standards-based technology enabling the delivery of last mile wireless broadband access as an alternative to cable and DSL."

WiMAX will provide fixed, nomadic, portable and mobile wireless broadband connectivity without the need for direct line-of-sight with a base station.

There are two different WiMAX networks:

− Fixed WiMAX networks with devices compliant to IEEE 802.16-2004 standard. They use Orthogonal Frequency Division Multiplexing (OFDM) and support fixed and nomadic access in Line of Sight (LOS) and Non Line of Sight (NLOS) environments.

− Mobile WiMAX networks with devices compliant to IEEE 802.16e-2005 standard. Optimized for dynamic mobile radio channels, this flavour of WiMAX provides support for handoffs and roaming. It uses Scalable Orthogonal Frequency Division Multiplexing Access (SOFDMA). Service providers that deploy 802.16e can also use the network to provide fixed service.

The two flavours of WiMAX technology will coexist and will address a growing demand for wireless broadband access in the fixed and mobile markets.

WiMAX allows for flexible spectrum usage using FDD (Frequency Division Duplex) and TDD (Time Division Duplex) configurations. Both cases use a

Services Specific Convergente Sub-Layer (CS)

MAC Common Part Sub-Layer (MAC CPS)

Physical Layer (PHY)

MAC SAP

PHY SAP

SAP = Services Access Point




burst transmission format with framing mechanisms that support adaptive burst profiling in which transmission parameters, including the modulation and coding schemes may be adjusted individually to each SS (Subscriber Station) on a frame-by-frame basis. The FDD case supports full-duplex SS/MSs as well as half-duplex SS/MSs.

3.2.1.3. WiMAX communication topologies In WiMAX there are two different roles: a BS (Base Station) and a SS/MS (Subscriber Station/Mobile Station) . A BS is a generalized equipment set providing connectivity, management, and control of the subscriber station/mobile station (SS/MS). A SS/MS is a generalized equipment set providing connectivity between subscriber equipment and a base station (BS).

Today, WiMAX Forum is also defining the architecture framework of WiMAX networks to interwork with other existing networks.


3.2.2.1. WiMAX certification players

By means of certification, operators, service providers and end users can buy WiMAX equipment with confidence that multi-vendor interoperability is highly assured.

WiMAX Forum Certified™ devices will reduce uncertainties for all parties in the access network value chain, from technology providers to service providers to end users.

For network operators, equipment and component manufacturers, and ultimately, for subscribers, products that are WiMAX Forum Certified™ will deliver wireless broadband access with a range of interoperable components.

The WiMAX Forum launched in the middle of 2005 a certification program. The purpose of the WiMAX certification program is to assure compliance to IEEE 802.16-2004 and IEEE 802.16e-2005 standards and multivendor interoperability.

The different stakeholders relevant for WiMAX certification testing are described in the next figure.




Figure 10. WiMAX Certification Testing Stakeholders

WiMAX certification integrates conformance and interoperability requirements extracted and set by the WiMAX Forum Certification Working Group (CWG) and the WiMAX Technical Working Group (TWG). Both Working Groups are responsible for managing the conformance and interoperability testing and the certification process. The CWG is also responsible for the study, identification and selection of test equipment to be used for WiMAX conformance and interoperability testing.

WiMAX certification testing must be performed by a WiMAX Forum Designated Certification Laboratory (WFDCL). The WFDCL is in charge of conducting WiMAX certification testing including protocol conformance, radio conformance and interoperability testing.

Today certification applies to stand-alone WiMAX devices (i.e., base stations, subscriber stations and mobile stations). The certification program is currently developing the certification process for vendor’s sub-systems, including ICs and radio cards.

3.2.2.2. WiMAX certification process

A member seeking WiMAX certification for a device shall contact with a WFDCL for evaluation, testing, and certification services. The whole process is carried out through “WiMAXCert”, web tool developed, for on-line registration and tracking of certification projects, for fixed and mobile WiMAX devices.

The WiMAX certification process consists of three phases (pre-testing, testing and post-testing), composed of the following steps:

1. Pre-testing phase:

− Registration of Certification Projects: The applicant will register its WiMAX device seeking certification, filling out several forms for providing necessary data about the company, the product, the Test




Laboratory chosen, preferred dates for certification testing and, optionally, additional services.

− Quotations: The applicant will receive automatically through “WiMAXCert” a services quotation from the WFDCL indicating all the services and associated fees applicable, according to the registration previously carried out.

− Testing Requirements: “WiMAXCert” features a structured means for the vendor to provide all the technical information necessary for conducting the applicable Certification Testing (i.e., PICS, PIXIT, device configuration/test interface details).

− Acceptance/Test Slot Reservation: The vendor and the WFDCL chosen will discuss off-line the specific dates for performing the testing and other details. Once they agree on all the terms, the WFDCL will formally accept the Certification Project and confirm the Test Slot Reservation.

− Test Plan: “WiMAXCert” will automatically generate the test plan applicable to the product seeking WiMAX Certification based on the PICS provided by the vendor and the Certification Profiles implemented by the product.

− The applicant can perform some self-testing before the submission to the WFDCL for certification but the certification testing has to be done by the WFDCL.

2. Testing phase:

− WFDCL performs protocol and radio conformance testing.

− Interoperability testing is executed by the WFDCL only after the vendor’s product has passed both protocol and radio conformance testing (see Figure x). WiMAX devices have to prove interoperability with a minimum of three different vendor’s WiMAX devices. For the execution of interoperability testing, the device under test is tested against a set of pre-selected WiMAX devices (BS and SS) from different vendors.

− Test Results: While the testing is being performed, the WFDCL will be responsible for keeping the project updated in “WiMAXCert” with all the test results obtained, so that their customer can easily track the progress of the project.

3. Post-testing phase:

− Registration of Certified Products in the WiMAX Certified Product Registry: After the WFDCL notifies the successful completion of the Certification Testing to a device, the device will be included in the WiMAX Certified Product Registry through “WiMAXCert” and the corresponding Certification Certificate will be generated and granted to the vendor.




− Test Reports delivery to the vendor. Test reports, containing the results for conformance and interoperability testing performed, will be delivered to the vendor through “WiMAXCert”.

A graphical description is shown in Figure 11.

Figure 11. WiMAX Certification Testing Overall Proc ess

The documents used during the testing process are:

− PICS (Protocol Implementation Conformance Statement). It is a technical specification that has to be filled by the WiMAX Forum member (the “Applicant”) before the submission of the WiMAX device to the WFDCL. In this document the vendor specifies which features the device supports.

− TSS&TP (Test Suite Structure and Test Purposes). It is a technical document that includes the Test Purposes. Test Purposes are descriptions of well-defined test objectives focusing on one or some standard requirements.

− ATS (Abstract Test Suite). It is a collection of detailed test descriptions according to the Test Purposes described in the TSS&TP document.

− PIXIT (Protocol Implementation eXtra Information for Testing). It is a document where vendor describes in detail the steps to configure properly the submitted device.

The test tools for WiMAX testing are:

− For protocol testing, a PCT (Protocol Conformance Tester) is needed. Protocol Conformance Testers have been validated by the WiMAX Forum. Test Purposes corresponding to protocol conformance testing




must be executed according to the implementation established in the ATS, using a WiMAX Forum validated Protocol Conformance Tester and in a WFDCL.

− For radio conformance testing, a RCT (Radio Conformance Tester) is needed. Radio Conformance Testers have been validated by the WiMAX Forum.

Figure 12. WiMAX Forum Certification Testing Proces s

3.2.2.3. WiMAX certification evolution

The WiMAX Certification testing started in the early stages with only one WFDCL named “Lead Lab” which acted as a reference test laboratory. As the certification demand grew, other WFDCLs become available worldwide and the first laboratory, the “Lead Lab”, acted as a reference test laboratory.

WiMAX testing requirements are defined in certification profiles.

Fixed WiMAX currently supports five certification profiles, which define classes of products that interoperate with each other on the basis of spectrum band, channelization and duplexing mode. To date, five certification profiles have been defined in the 3.5 GHz band—where both TDD and FDD mechanisms can be used—and the 5.8 GHz TDD band. New certification profiles will be added in response to demand from vendors and operators.

Other important concept for WiMAX certification is “certification wave”. At the early stages of the WiMAX certification, the whole set of test requirements were not required to grant certification. A “certification wave” is a specific subset of testing requirements that will be used for certification for a certain period of time.

WiMAX Forum CWG defines the certification wave contents. Certification Wave 1.0 is focusing on mandatory features. Other certification waves will include more features. Each new wave will include more test cases but maintaining backwards compatibility.




3.3. Wi-Fi certification

3.3.1. Wi-Fi technology

Wi-Fi is a wireless technology that is an accepted standard for WLANs (Wireless Local Area Networks). Wi-Fi technology was created to provide fast, secure and reliable wireless connectivity. It allows connecting computers to each other; to connect to the Internet and to wired networks (e.g., Ethernet).

Wi-Fi is based on IEEE (Institute of Electrical and Electronic Engineers) 802.11 standards.

The Wi-Fi Alliance is a global, non-profit organization with the goal of driving the adoption of a single worldwide-accepted standard for high-speed wireless local area networking. The Wi-Fi Alliance develops test specifications and monitors and performs rigorous testing and Wi-Fi certification of wireless devices according to IEEE 802.11 standards.

3.3.1.1. Main applications and main players Wi-Fi enables notebook computers, consumer electronic devices, cellular phones and mobile computing devices to easily connect to the internet, as well as to each other and to existing networks.

Wi-Fi was initially a technology found predominantly in laptops, PC cards, access points and wireless routers. This has changed rapidly, with an increasing number of phones, PDAs, printers, and all types of mobile and stationary devices now available with embedded Wi-Fi connectivity.

Wi-Fi Alliance certification has evolved to meet the specific requirements introduced by these new devices and the applications they are supporting.

3.3.1.2. Wi-Fi technology basics Wi-Fi devices use radio technologies based on IEEE 802.11 standards to provide secure, reliable and fast wireless connectivity. Except for 802.11a radio devices, which operate at 5 GHz frequency band, Wi-Fi devices primarily use the 2.4 GHz frequency band, which is standardized and unlicensed by international agreement, although the exact frequency allocations and maximum permitted power vary in different parts of the world.

Wi-Fi is mainly based on the following IEEE (Institute of Electrical and Electronic Engineers) standards:

− IEEE 802.11 b. It uses DSSS (Direct Sequence Spread Spectrum) to transmit information. It operates in the 2.4 GHz band and can reach a maximum data rate of 11 Mbps.

− IEEE 802.11 a. It uses OFDM (Orthogonal Frequency Division Multiplexing) as scheme to transmit information. It operates in the 5 GHz band and can reach a maximum data rate of 54 Mbps.




− IEEE 802.11 g. It also uses OFDM scheme to transmit information and has a maximum data rate of 54 Mbps but this standard operates in the 2.4 GHz band.

Channel numbers are standardized by frequency throughout the world, so authorized frequencies can be identified by channel numbers.

The maximum number of available channels for Wi-Fi enabled devices is:

− 13 for Europe.

− 11 for North America. Only channels 1, 6, and 11 are recommended for 802.11b/g to minimize interference from adjacent channels.

− 14 for Japan.

Another IEEE standard currently in the definition process is the IEEE 802.11n which will provide better range, coverage, bandwidth and performance than IEEE 802.11a/b/g.

As for vehicular environment, IEEE 802.11p specification is still under development and it is currently a draft version. This technology will operate in the 5.9 GHz band and it is based on DSRC (Dedicated Short Range Communications) which is specified in IEEE 1609.1 to IEEE 1609.4. This standard will allow enhancement V2V and V2I communications. Nevertheless, because this technology is a draft, the certification procedure for IEEE 802.11p is not yet available.

Figure 13. Vehicular Environment using IEEE 802.11p

3.3.1.3. Wi-Fi communication topologies Wi-Fi networks are composed of just two major components: an access point, wireless router or gateway that acts as the base station for the wireless network and radios clients (also named “stations”) that exchange information with the base station.

There are two possible modes of operation for a Wi-Fi network:

V2V (IEEE 802.11p)

V2I (IEEE 802.11p)




− Infrastructure mode (with a base station). It provides infrastructure access to mobile users. It covers a fixed area. Also known as BSS (Basic Service Set) mode.

− Ad-hoc mode (without base station). It allows two or more devices to communicate with each other directly instead of through a base station. Also known as IBSS (Independent Basic Service Set) mode.

There are many different ways to set up a wireless network using Wi-Fi enabled devices. When setting up a network, you can choose to have an entirely wireless network or one that is a combination of wireless and wired equipment. It is usually simpler and less expensive to have an entirely wireless network when starting from scratch and building a small home or home office network. But if you already have a network, it makes sense to add wireless components to create a combined wireless/wired network.

Wi-Fi network range and performance depend on a variety of factors including the type of Wi-Fi radio used, special antennas in place and the layout in the network environment.

3.3.1.4. Wi-Fi protocol stack IEEE standards define the PHY and MAC layers for IEEE 802.11 compliant devices. The standards define a single MAC that interacts with different PHY layers.

IEEE 802.11 MAC layer provides functionality to allow reliable data delivery for the upper layers over the wireless PHY media. Data delivery is based on an asynchronous, best effort, connectionless delivery of MAC layer data. MAC layer always manages mobility and roaming.

Figure 14. Wi-Fi Protocol Stack


3.3.2.1. Wi-Fi certification players With the aim of enhancing the user experience for mobile wireless devices, the Wi-Fi Alliance's testing and certification program ensures the interoperability of WLAN products based on the IEEE 802.11 specification.

Since the introduction of the Wi-Fi Alliance's certification program in March 2000, over 3,000 products have been designated as Wi-Fi CERTIFIED™. The Wi-Fi CERTIFIED™ logo is the guarantee that a product has met rigorous interoperability testing requirements to ensure multi-vendor interoperability.




The WFA is in charge of defining the operational processes and procedures to grant certificates and the quality principles under which the Wi-Fi Alliance Authorized Test Laboratories (ATLs) operate.

Therefore, there are three main stakeholders involved in the Wi-Fi certification process:

− The WFA member that applies for testing. It is the “Applicant”5.

− The ATL, which is in charge of performing the tests according to the WFA test plans and other obligations.

− The WFA. It is the “Certification Body” and grants the Wi-Fi logo.

To use the Wi-Fi Logo, a product must be Wi-Fi CERTIFIED. WFA grants the Wi-Fi certification based on testing results. In order to obtain the certification, a product must pass all WFA Test Plans in a WFA Authorized Test Laboratory. The WFA Authorized Laboratory must run WFA Test Plans on a validated WFA Test Bed.

The Wi-Fi Alliance certification programs include interoperability testing for devices according to IEEE 802.11a, IEEE 802.11b and IEEE 802.11g. This testing measures interoperability in terms of: application level connection (e.g., using ping command) and application level transfer rate (throughput).

The Wi-Fi Alliance certification testing applies to:

− Client devices (also named “Stations” (STA)). Some examples of Stations are: PC cards, Mini PCI modules and embedded radios, USB adapters, PCI and ISA bus adapters, compact flash and other small client-formats.

− Access Points (AP).

− Application Specific Devices (ASD). They are devices that implement IEEE 802.11 standards but are neither Stations nor Access Points. The main difference is that these devices are specific for a concrete functionality. One example could be a PDA (a Personal Digital Assistant) or a printer.

The Wi-Fi Alliance produces and updates continuously certification test plans to be used in the certification programs. Currently, the following test plan is mandatory:

− Wi-Fi 802.11 with WPA2™6, WPA and WEP System Interoperability Test Plan with ASD Test Engine for IEEE 802.11a, b & g Devices.

Other test plans that are optional:

− WMM™7 System Interoperability Test Plan with Test Engine.

− WMM Power Save System Interoperability Test Plan.

− Wi-Fi WPS™8Test Plan.

5 To certify a product the applicant must be a member of WFA. 6 WPA stands for Wi-Fi Protected Access. WPA is a trademark of the Wi-Fi Alliance 7 WMM stands for Wi-Fi Multimedia. WMM is a trademark of the Wi-Fi Alliance.




The ATLs must be qualified before executing certification testing associated to a test plan.

3.3.2.2. Wi-Fi certification process

All progress updates and transactions during the certification process are conducted through the WFA Certification System (web based tool). The main steps are:

1. The WFA member requesting testing completes an on-line application on the Certification System and selects an ATL where to perform the Wi-Fi testing according to the WFA test plans.

2. The Certification System sends to the ATL a notification of the WFA member ATL selection and request for a test schedule.

3. The ATL uses the Certification System to accept or reject the member’s request.

4. The member schedules a test date with the selected ATL’s testing facilities using a method specified by the ATL.

5. The ATL updates the information of the Certification System with the equipment test date.

6. The ATL makes financial arrangements with the member.

7. The member may re-schedule, cancel or use the scheduled time for consulting or pre-certification subject to the ATL’s established procedures for such changes.

8. The member sends the equipment samples to be tested to the ATL.

9. The ATL performs testing per the Wi-Fi Alliance test plans and the ATL issues and records test results on the Certification System.

10. If the results are successful, the device obtains the Wi-Fi CERTIFIED™ logo and it is published in the WFA web page (www.wi-fi.org).

This process is summarized in Figure 12.

8 WPS stands for Wi-Fi Protected Setup. WPS is a trademark of the Wi-Fi Alliance.




Figure 15. Wi-Fi Certification Process

Other documents to be used during the certification process are:

− Project Handling procedures

− Testing Procedures

− Operator notes

− Data sheets

− Test Reports

− Test Plans

− Module Policy

− Certification Transference Policy

− Test Lab Procedures Manual

− ECN (Engineering Changes Notes)

− NDA’s (Non-Disclosure Agreement) and confidentiality Agreements

− Samples storing conditions.

− Logo usage conditions.

3.3.2.3. Wi-Fi certification evolution

The Wi-Fi Alliance certification testing started with one test laboratory (located in the USA) in the early stages of the certification process. When the




certification demand grew, the addition of new certification test labs was required to help meet that demand.

Certification initially only focused on PHY and MAC functionality (i.e., IEEE 801.11b) to ensure basic connectivity and interoperability.

The certification programs evolved to include:

− Security: Wi-Fi Protected Access (WPA) and Wi-Fi Protected Access 2 (WPA2), with Extensible Authentication Protocol (EAP) and Extended EAP for authentication.

− Increased throughput: IEEE 802.11g and IEEE 802.11a.

− QoS: Wi-Fi Multimedia (WMM).

− Power conservation: WMM Power Save.

− Simplified network setup supporting advanced security features (Wi-Fi Protected Setup™).

Wi-Fi Alliance certification programs are continuously evolving to meeting the specific requirements introduced by new devices and the applications they support.




3.4. DLNA certification

3.4.1. DLNA technology

The Digital Living Network Alliance (DLNA™9) is a cross-industry organization of leading consumer electronics, computing industry and mobile device companies. They share a vision of a wired and wireless interoperable network of Personal Computers (PC), Consumer Electronics (CE) and mobile devices in the home enabling a seamless environment for sharing and growing new digital media and content services.

DLNA is focused on delivering interoperability guidelines based on open industry standards to complete the cross industry digital convergence.

The goals of DLNA initiative are:

− To design guidelines for interoperable products

− To develop liaisons with other industry standards bodies

− To develop and execute compliance testing and certification programs

3.4.1.1. Main application and main players Consumers are acquiring, viewing and managing an increasing amount of digital media contents on devices in the CE, mobile and PC domains (see Figure 16).

Users want to enjoy this content easily and conveniently, regardless of the source, across different devices and locations in the home.

The DLNA vision is a wired and wireless interoperable network where digital content such as photos, music and videos can be seamlessly shared through personal computers (PCs), consumer electronics (CE) and mobile devices in and beyond the home.

Figure 16. CE, PC-Internet, Mobile and CE Domains 9 DLNA is a trademark of the Digital Living Network Alliance.




3.4.1.2. DLNA technology basics In order to deliver on digital interoperability in the home, DLNA has published a common set of interoperability design guidelines. The DLNA interoperability design guidelines specify the interoperable building blocks that are available to build platforms and software infrastructure. DLNA has focused on interoperability between networked entertainment and media devices for personal media uses involving imaging, audio and video. The specific components and technologies covered by the DLNA interoperability guidelines are listed in Figure 17.

UPnP and other IP securitymechanisms

UPnP v 1.0

Media Format and Transport Model

UPnP Architecture and Technology

IP, Wired and WirelessEthernet Media and QoS

mechanisms

Technology

UPnP ForumAuthenticationn and

Authorization

IETFMedia Management,

Distribution and Control

IETF and othersMedia Formats and Streaming Protocols

UPnP ForumDevice and Service

Discovery and Control

IETF, Wi-Fi Alliance, IEEE, Bluetooth SIG

Networking and Connectivity

Main SIG and Industry Fora

FunctionalComponents

UPnP and other IP securitymechanisms

UPnP v 1.0

Media Format and Transport Model

UPnP Architecture and Technology

IP, Wired and WirelessEthernet Media and QoS

mechanisms

Technology

UPnP ForumAuthenticationn and

Authorization

IETFMedia Management,

Distribution and Control

IETF and othersMedia Formats and Streaming Protocols

UPnP ForumDevice and Service

Discovery and Control

IETF, Wi-Fi Alliance, IEEE, Bluetooth SIG

Networking and Connectivity

Main SIG and Industry Fora

FunctionalComponents

Figure 17. DLNA Functional Components and Technolog ies

Technologies are based on standards from standards bodies, SIGs (Special Interest Groups) and industry fora.

DLNA published the first version of its “Home Networked Device Interoperability Guidelines” in year 2004 that defined two different roles DMP (Digital Media Player) and DMS (Digital Media Server).

During 2006, DLNA published a new version (1.5) including new device classes (e.g., mobile devices, printers, etc.), new media transports protocols, new media formats, etc.

3.4.1.3. DLNA communication topologies DLNA interoperability design guidelines define a total of twelve device classes in three device categories.

The Home Network Device (HND) category is made up of five Device Classes that share system usages in the home network with the same media format and network connectivity requirements.

The HND category includes:

− Digital Media Server (DMS) devices provide media acquisition, recording, storage, and sourcing capabilities.




− Digital Media Player (DMP) devices find content exposed by a DMS to provide playback and rendering capabilities.

− Digital Media Renderer (DMR) devices play content they receive after being setup by another network entity.

− Digital Media Controller (DMC) devices find content exposed by a DMS and match it to the rendering capabilities of a DMR.

− Digital Media Printer (DMPr) devices provide printing services to the DLNA home network.

Other category is the Mobile Handheld Device (MHD) category which consists of five device classes that share the same system usages as the HND Device Category, but have different requirements for network connectivity. There are five device classes:

− Mobile Digital Media Server (M-DMS) devices expose and distribute content.

− Mobile Digital Media Player (M-DMP) devices find content exposed by a M-DMS and play the content locally on the M-DMP.

− Mobile Digital Media Uploader (M-DMU) devices send contents to an M-DMS with upload functionality.

− Mobile Digital Media Downloader (M-DMD) devices find and download content exposed by an M-DMS and play the content locally on the M-DMD after download.

− Mobile Digital Media Controller (M-DMC) devices find contents exposed by an M-DMS and match it to the rendering capabilities of a DMR, setting up connections between the server and renderer.

The last category is the Home Infrastructure Device (HID) that includes two device classes:

− Mobile Network Connectivity Function (M-NCF) devices provide a bridge function between the MHD and the HND.

− Media Interoperability Unit (MIU) devices provide content transformation between required media formats for the HND and the MHD device categories.

All these device classes are summarized in the next figure:




Figure 18. DLNA Device Classes

3.4.1.4. DLNA protocol stack and roles

DLNA interoperability guidelines specify the following protocol stack for DLNA compliant devices.

Figure 19. DLNA Protocol Stack

Home Network Devices

Digital Media Server (DMS)

Digital Media Player (DMP)

Digital Media Renderer (DMR)

Digital Media Controller (DMC)

Digital Media Printer (DMP)

Mobile Handheld Devices

Mobile Digital Media Server (M-DMS)

Mobile Digital Media Player (M-DMP)

Mobile Digital Media Downloader (M-

DMD)

Mobile Digital Media Uploader (M-DMU)

Mobile Digital Media Controller (M-DMC)

Home Infrastracture Devices

Mobile Interoperability Unit

(MIU)

Mobile Network Connectivity

Function (M-NCF)




3.4.2. DLNA Certification scheme

3.4.2.1. DLNA certification players Products designed to the DLNA Interoperability Guidelines are granted use of the DLNA CERTIFIED Logo after passing all DLNA certification and testing requirements.

DLNA launched a certification program according to DLNA Interoperability Guidelines version 1.0 in 2005. The goal of this certification program is validating interoperability between devices designed to be compliant to the DLNA Interoperability Guidelines. If a Member Company’s product passes certification testing, a licensing agreement is signed issuing the DLNA CERTIFIED Logo to the certified product enabling consumers to identify it as DLNA compliant.

The main stakeholders of DLNA certification are:

− DLNA Compliance and Certification Committee: Its mission is to specify and maintain processes, policies and test resources for DLNA members to design, verify and promote device compliance with DLNA Interoperability Guidelines. Therefore, it is in charge of the definition of the Certification and Logo Program.

− Test Laboratories. They are named ICV (Independent Certification Vendor). They perform DLNA certification testing.

− The DLNA Member seeking for certification.

The DLNA certification testing comprises conformance and interoperability testing. As described before, DLNA certification testing verifies that the device correctly implements DLNA design guidelines and demonstrates correct interoperability with other DLNA devices.

All DLNA features, functions and features and capabilities in the device must be passed in order for the device to be certified.

Before submission to certification, DLNA devices seeking for certification must own the following certification prerequisites:

− UPnP™10 certification.

− Wi-Fi Alliance certification for devices equipped with IEEE 802.11 a/b/g.

Conformance testing for DLNA certification testing includes:

− Media distribution and control

− Device discovery and control

− Media Transport

− Media Formats

− Network Protocols 10 UPnP stands for Universal Plug and Play.




− Network Topologies

Interoperability testing for DLNA certification consists of demonstrating correct interoperability with other three DLNA devices (named “Reference Devices”). Interoperability testing checks the following functionalities:

− Discover devices using control points

− Stream content, from Media Servers to Media Players

− AutoIP/DHCP connectivity

− Play capability

− Stop capability

− Pause/Resume capability

− Trick modes (seek forward and seek backward)

DLNA also provides its members a conformance test tool named CTT (Conformance Test Tool) which can be used by the Member for self-testing before submission to the ICV.

Interoperability testing checks the following functionalities:

− Discover devices using control points.

− Stream content, from Media Servers to Media Players.

− AutoIP/DHCP connectivity.

− Play capability.

− Stop capability.

− Pause/Resume capability.

− Trick modes (seek forward and seek backward).

DLNA also provides to its members a conformance test tool named CTT (Conformance Test Tool) which can be used by the Member for self-testing before submission to the ICV.

3.4.2.2. DLNA certification process All progress updates and transactions during the certification process are conducted through the WCS (Web Certification System). This web-based tool tracks all the certification process.

The DLNA certification process is described in the figure below.




Figure 20. DLNA Certification Process

The main steps in the DLNA certification process are:

1. The Applicant seeking for DLNA certification must be a DLNA member.

2. The Applicant must design and implement its device according to the DLNA Interoperability Guidelines.

3. The Applicant requests formal testing and completes an on-line application on the WCS. The Applicant selects an ICV where to perform the DLNA certification testing.

4. The WCS sends to the ICV a notification of the DLNA member ICV selection and request for a test schedule.

5. The ICV uses the WCS to accept or reject the Applicant’s request.

6. The Applicant schedules a test date with the selected ICV testing facilities using a method specified by the ICV.

7. The ICV makes financial arrangements with the Applicant.

8. The Applicant may re-schedule, cancel or use the scheduled time for certification subject to the ICV’s established procedures for such changes.

9. The Applicant sends to the ICV the equipment samples to be tested.

10. The ICV performs conformance and interoperability testing according to the DLNA Test Plans (these test plans are produced by the DLNA Compliance and Certification Committee based on the DLNA Interoperability Guidelines)

11. The ICV issues and records test results on the WCS.

12. A dispute form may be submitted to the DLNA Certification Administrator if the tests fail.




13. Testing results are reviewed by the DLNA Certification Administrator. If the test results are successful, the device obtains the DLNA CERTIFIED logo and it is published in the DLNA web page (http://certification.dlna.org/products/).

3.4.2.3. DLNA certification evolution DLNA holds regularly interoperability events named “Plugfests”. DLNA considers Plugfests an opportunity for vendors to test with devices from other vendors allowing them to gain experience and debug their prototype devices under development before submission for formal certification testing.

Figure 21. DLNA Certification Evolution

For a smooth implementation of the certification process, DLNA followed the steps described in the figure above. Before the establishment of a formal certification and logo program, DLNA established a D2G (Design To Guidelines) Program. This was a pre-certification program where both prototypes and commercial products were tested with participating devices in Plugfest events. Those devices passing all the tests defined by the D2G program were allowed to claim “Designed to DLNA guidelines” but not eligible for DLNA CERTIFIED logo and certification marketing.

The last step was the establishment of the certification and logo program. The certification testing must be performed in the ICVs. Initially, one laboratory was recognized and to meet the certification demand later more test laboratories were recognized.

3.5. ZigBee certification

3.5.1. ZigBee technology

ZigBee technology is a low data rate, low power consumption, low cost; wireless networking protocol targeted towards automation and remote control applications. IEEE 802.15.4 committee started working on a low data rate standard a short while later. Then the ZigBee Alliance and the IEEE decided to join forces and ZigBee is the commercial name for this technology.




The ZigBee Alliance has been set up as an association of companies working together to enable reliable, cost-effective, low-power, wirelessly networked, monitoring and control products based on an open global standard.

The relationship between IEEE 802.15.4 and ZigBee is similar to that between IEEE 802.11 and the Wi-Fi Alliance. The ZigBee 1.0 specification was ratified on December 14, 2004 and is available to members of the ZigBee Alliance. Most recently, the ZigBee 2007 specification was posted on October 30, 2007. The first ZigBee Application Profile, Home Automation, was announced November 2, 2007.

3.5.1.1. Main applications and main players ZigBee has been developed to meet the growing demand for capable wireless networking between numerous low-power devices. In industry ZigBee is being used for next generation automated manufacturing, with small transmitters in every device on the floor, allowing for communication between devices to a central computer. This new level of communication permits finely-tuned remote monitoring and manipulation. In the consumer market ZigBee is being explored for everything from linking low-power household devices such as smoke alarms to a central housing control unit, to centralized light controls.

Figure 22. ZigBee Alliance Applications

3.5.1.2. ZigBee technology basics




The focus of network applications under the IEEE 802.15.4 / ZigBee standard include the features of low power consumption, needed for only two major modes (Tx/Rx or Sleep), high density of nodes per network, low costs and simple implementation.

These features are enabled by the following characteristics:

− 2.4GHz and 868/915 MHz dual PHY modes. This represents three license-free bands: 2.4-2.4835 GHz, 868-870 MHz and 902-928 MHz. The number of channels allotted to each frequency band is fixed at sixteen (numbered 11-26), one (numbered 0) and ten (numbered 1-10) respectively. The higher frequency band is applicable worldwide, and the lower band in the areas of North America, Europe, Australia and New Zealand.

− Low power consumption, with battery life ranging from months to years. Considering the number of devices with remotes in use at present, it is easy to see that more numbers of batteries need to be provisioned every so often, entailing regular (as well as timely), recurring expenditure. In the ZigBee standard, longer battery life is achievable by either of two means: continuous network connection and slow but sure battery drain, or intermittent connection and even slower battery drain.

− Maximum data rates allowed for each of these frequency bands are fixed as 250 kbps @2.4 GHz, 40 kbps @ 915 MHz, and 20 kbps @868 MHz.

− High throughput and low latency for low duty-cycle applications (<0.1%).

− Channel access using Carrier Sense Multiple Access with Collision Avoidance (CSMA - CA)

− Addressing space of up to 64 bit IEEE address devices, 65,535 networks

− 50m typical range

− Fully reliable “hand-shaked” data transfer protocol.

− Different topologies as illustrated below: star, peer-to-peer, mesh

3.5.1.3. ZigBee communication topologies A ZigBee system consists of three different ZigBee types that operate in any self-organizing application network. These devices have 64-bit IEEE addresses, with option to enable shorter addresses to reduce packet size, and work in either of two addressing modes – star and peer-to-peer.

− The ZigBee coordinator node: There is one, and only one, ZigBee coordinator in each network to act as the router to other networks, and can be likened to the root of a (network) tree. It is designed to store information about the network.




− The full function device FFD: The FFD is an intermediary router transmitting data from other devices. It needs lesser memory than the ZigBee coordinator node, and entails lesser manufacturing costs. It can operate in all topologies and can act as a coordinator.

− The reduced function device RFD: This device is just capable of talking in the network; it cannot relay data from other devices. Requiring even less memory, (no flash, very little ROM and RAM), an RFD will thus be cheaper than an FFD. This device talks only to a network coordinator and can be implemented very simply in star topology.

ZigBee supports three topologies: star topology, peer-to-peer topology and cluster tree.

Figure 23. ZigBee Topologies

3.5.1.4. ZigBee protocol stack IEEE and ZigBee Alliance have been working closely to specify the entire protocol stack. IEEE 802.15.4 focuses on the specification of the lower two layers of the protocol (physical and data link layer). On the other hand, ZigBee Alliance aims to provide the upper layers of the protocol stack (from network to the application layer) for interoperable data networking, security services and a range of wireless home and building control solutions, provide interoperability compliance testing, marketing of the standard, advanced engineering for the evolution of the standard. This will assure consumers to buy products from different manufacturers with confidence that the products will work together.

The ZigBee protocol stack is described in the figure below.




3.5.2. ZigBee Certification scheme

3.5.2.1. ZigBee certification players Achieving interoperability of end ZigBee products is a key objective of the ZigBee Alliance by means of a certification program defined in ‘ZigBee Alliance Certification and Testing Policy’ document [17].

This certification program assurances both interoperability of ZigBee products with those from other vendors who implement around public application profiles and successful co-existence of manufacturer specific applications profile-based solutions. The ZigBee Certified Product Logo may be applied to a product after a ZigBee Alliance member company successfully completes the ZigBee Certification Program for end products. Only end products may bear the ZigBee Alliance Certified Product Logo.

To submit a product for certification or compliance testing and to be granted certification and compliance status, a company must be a member of the ZigBee Alliance. As a member, a company has the rights to use the ZigBee Alliance logo on certified end products.

ZigBee certification is applied over ZigBee platform and ZigBee products. ZigBee compliant platform testing is described in applicable to manufacturers of semiconductors and software, module makers and system integrators through the ZigBee Compliant Platform (ZCP) Test Program. This testing iombines IEEE 802.15.4 physical and MAC layer interoperability with the ZigBee Alliance stack profile testing through a “Golder platform”. This “Golder Platform” is established as reference point for ongoing platform certification by approved test service providers, and each test service provider must have




one instance of each golden platform. The certification program identifies a procedure for selecting a candidate golden platform.

ZigBee product must be built on ZigBee Compliant Platform and must use a Public or Manufacturer Specific Application Profile, ZigBee Alliance specifies two test program for each type of profile.The ZigBee Manufacturer Specific Profile Test Program is based on interoperability testing in a network of reference devices in order to determine the level of coexistence of the product within a ZigBee network.

Next figure illustrates how the test programs map to the ZigBee Alliance Stack and Application Profile types.

Finally, manufacturers are not able to self-certify. They are however encouraged to conduct pre-testing and to attend ZigFests. Both of these activities are beneficial in ensuring proper implementation of the specifications prior to submission for formal compliance testing. Test plans are available to ZigBee Alliance members for both compliance testing and ZigFests.

A ZigFest is an interoperability event where manufacturers gather together to showcase their products and network with other wireless technology professionals. Several test cases and runs will be facilitated with different pairings of manufacturers. The participant’s identities will be confidential and only known to the other parties at the event. The ZigBee Alliance provides a summary report of the ZigFest after most events.

3.5.2.2. ZigBee certification process The ZigBee Alliance will grant ZigBee certification through the procedure illustrated in next figure.

ZigBee Compliant Platform

ZigBee Manufactures Specific Profile

ZigBee Public Profile

ZigBee APP Layer

ZigBee NWK Layer

802.15.4 Compliant PHY and MAC

ZigBee APP Layer

ZigBee NWK Layer


Manufacturer Specific

Application Profile

ZigBee APP Layer

ZigBee NWK Layer


Public Application Profile




Figure 24. ZigBee Certification Process

The main steps in the ZigBee certification process are:

1. A manufacturer applies for ZigBee Alliance certification.

2. Manufacturer registers device for certification and receive a ZigBee ID number (ZID) and information regarding test programs and test service providers.

3. The member company submits the product(s) to their choice of ZigBee designated test providers

4. The ZigBee Alliance Certification Body receives notification from the test provider upon successful completion of certification test. This notification process does not include test results or confidential vendor information, only a general ‘pass’ statement. The vendor is automatically notified.

5. The company provides the appropriate paperwork to the Certification Body, as defined during the initial application process.

6. The ZigBee Management Firm confirms the membership status as "member in good standing" with all dues and fees paid for the Member or Adopter member.

7. The ZigBee Alliance receives the lab test results, conducts a review within 5 business days, approves the cost and provides logo usage rights to the submitter company.




8. A ZigBee Compliant Platform (ZCP) is used for the final product.

9. ZigBee Alliance registers the certified products via its web site.

Finally, this program also takes into account the possibility of a re-certification process as long as products have been modified. Depending on the nature of the changes, the test services provider will determine whether the entire certification retest must be carried out, or only a part of it.

3.6. UWB certification

3.6.1. UWB technology

Ultra-Wideband (UWB) technology based on the WiMedia standard brings the convenience and mobility of wireless communications to high-speed interconnects in devices throughout the digital home and office. Designed for low-power, short-range, wireless personal area networks (WPANs), UWB is the leading technology for freeing people from wires, enabling wireless connection of multiple devices for transmission of video, audio and other high-bandwidth data.

3.6.1.1. Main applications and main players Ultra Wideband (UWB) is a wireless technology for transmitting digital data at very high rates over a wide spectrum of frequency bands using very low power. UWB is ideally suited for wireless communications, particularly short-range and high-speed data transmissions for wireless personal area network (WPAN) applications.

Owing to its characteristics, one of the main application areas for UWB is short-range very high-speed wireless communication links, as part of what is usually referred to as Wireless Personal Area Networks (WPAN). Next table summarizes how UWB applications are being used in different market segments.

Application Consumer Computer Mobile Automotive Medical Industrial Transmission of high-definition

AV (audio-video)

AV equipment PC, AV equipment

Mobile phones/MIDs/PDAs

In-car entertainment - -

Replacement of wired USB 2.0

peripherical connections

AV equipment Webcam, mouse, etc.

Mobile phones/MIDs/PDAs

In-car entertainment - -

Ultra-low power data

transmission - - - -

Wireless Body Area Network

Sensor networks




3.6.1.2. UWB technology basics UWB is presented as the big capacity alternative to short range communications and it’s being standardizing in three different groups in the IEEE. IEEE 802.15.3a includes two proposals to UWB: The proposal of the OFDM, the Multiband OFDM Alliance’s (MBOA) and the proposal of direct sequence (Direct Sequence, DS). In the case of the IEEE 802.15.4a, the DS proposal was approved for low information ratios. Moreover, it’s being discussed the incorporation of the UWB as a physical layer for the Bluetooth, in the case of the IEEE 802.15.1.

UWB specify transfer rates in gross of 11, 22 Mbps for the connectivity of the audio devices and 33, 44 and 55Mbps for the multimedia connections. The maximum theorist rate is 1Gbps and is superior to Wi-Fi when penetrating walls and physical barriers in short distances.

The frequency spectrum used goes from 3.1 GHz to 10.6 GHz: (declared not licensed BANDA by the FCC) using multiple accesses OFDM with modulations QPSK/BPSK or DS-UWB (Motorola).

3.6.1.3. WiMedia-UWB Standardization The UWB standardization process is being long and complex. It started with the formation of the group IEEE 802.15.3a. Previously, the IEEE had led the study of certain work groups to enable the construction of a standard based in the new guidelines of the FCC about the spectrum for the UWB.

At first, there were presented 21 standardization propositions. But these were reduced to two of them: one based on OFDM Multiband, proposed by Texas Instruments Inc., and a second proposal based in the direct sequence technology (DS), led by Freescale and the UWB Forum. The lack of agreement between the two tendencies, practically irreconcilable, took the process to a dead line.

Some supporters of the OFDM Multiband decided to continue working apart from the standardization process of the IEEE not to delay even more the launch to the market of at least one kind of product destined to meet the demand for WPAN. This group was called at first Multiband OFDM Alliance (MBOA), which renamed itself as WiMedia Alliance. It is structure is similar to the WiFi Alliance’s, which is the organization that test, certify and guarantee the inter operability of the products arisen for this technology.

WiMedia Alliance kept on pursuing the standardization for the UWB, in spite of the blockade of the IEEE work group, encouraging this process in alternative bodies (ECMA, ISO and ETSI). This measure provoked the cancellation of the IEEE 802.15.3a group without an agreement for the standard in January 2006. Meanwhile, the processes were completed for the other agencies in 2007.

During this period of time, the techniques specifications have remained stables. That’s why there have arisen massive consume products totally certificated with inter operability guaranteed. At this point, WiMedia is posing




new specifications about the layer of the WiNet protocol adaptation and Bluetooth. Other changes are related to retouching designed to answer new international regulations, to get flexible spectral features and the coexistence of the OFDM Multiband.

3.6.1.4. WiMedia-UWB protocol stack WiMedia Alliance has the backing of the Universal Serial Bus-Implementers Forum (USB-IF) for Certified Wireless USBTM11 (WUSB), and the Bluetooth Special Interest Group (SIG) which will integrate the WiMedia UWB technology into future versions of Bluetooth. The IEEE 1394 Trade Association has also selected the WiMedia platform for the new generation of wireless FireWire. See Errore. L'origine riferimento non è stata trovata. below. DLNA™12 (Digital Living Network Alliance) is also an affiliate organization of the WiMedia Alliance.

3.6.2. WiMedia-UWB Certification scheme

3.6.2.1. WiMedia-UWB certification players The WiMedia specifications define a distributed Medium Access Control (MAC) sublayer, an Ultra-wideband (UWB) radio Physical layer (PHY), and Upper Layer Protocols (UPLs). To complement those specifications and to enable measurement of compliance to specifications and interoperability between real implementations, WiMedia has instituted the Compliance and Interoperability Policy (CIP). Its purpose is to provide the rules, guidelines, and policies WiMedia members must follow to certify their commercial implementations or to register PHY implementations. The WiMedia Certification Review Board (CRB) is in charge of maintaining, administering and enforcing this CPI. 11 Certified Wireless USB is a trademark of the USB-IF. 12 DLNA is a trademark of the Digital Living Network Alliance.




The WiMedia certification testing applies to two types of possible implementations: PHY layer and WiMedia Platform. WiMedia certification testing covers both conformance and interoperability requirements as Table shows. In case of WiMedia Platform testing, the implementation must be based on a WiMedia Certified PHY.

Implementation Conformance Interoperability

PHY layer Based on PHY test specifications -

WiMedia Platform Based on Platform Test Specifications

Once an implementation has successfully passed its certification testing, it is a candidate to become a Certified PHY or WiMedia Certified Radio Platform (WCRP) respectively. Moreover, each type of WiMedia implementation requires specific testing before it is added to the Integrator’s List which is the official list of WiMedia Certified Implementations.

A member who wants to get certification for its implementations has the following options:

- Participate in WiMedia hosted Certification Events for compliance and interoperability testing held independently or in conjunction with other industry events.

- Contract the testing services of an Independent Test Lab (ITL) which is a WiMedia-select third-party laboratory authorized for certification testing.

Finally, there is an expiration on all PHY Certifications and Platform Certifications issued. This expiration policy is intended to address incremental releases to Medium Access Control (MAC) and PHY compliance and interoperability test specifications as well as unforeseen interoperability difficulties which become evident after deployment to the field.

3.6.2.2. WiMedia-UWB certification process In order to be a WiMedia Certified Implementation, the following conditions must be met:

- The applicant must be a current WiMedia Member.

- The implementation shall have been submitted for WiMedia certification testing in accordance with the official WiMedia Compliance and Interoperability Test Specs approved by the WiMedia Board of Directors and administered by the CRB.

- The implementation shall have shown to have successfully passed all required compliance and interoperability tests which are in effect for a current WiMedia Final Deliverable, as performed by WiMedia or its subcontractors or agents.




- The implementation must be intended for commercial use and sale, and be intended for volume production.

The main steps in the WiMedia-UWB certification process are:

1. The applicant submits a list of mandatory and optional features to be tested at a given event at least one week prior to the event. In cases where testing is performed by an ITL, the one week advanced submission time may be waived.

2. After the test event the PICS is archived and a Certification folder is established for the implementation.

3. When the member applies for Certification the archivist supplies the list of mandatory / optional features to be reviewed.

4. When the CRB accepts the member’s application, the list of PICS is made a part of the Integrator’s List information after any embargo time specified by the member’s application.

5. Product documentation that describes the implementation, including versions of the component parts is submitted by the member at the time the member arrives at the testing event or ITL.

6. Product documentation is archived after testing and is made available to the CRB only if it needs to review an issue relating to the implementation being Certified. The information is added to the Certification folder established for the implementation.

7. Instructions describing the steps necessary to cause the implementation under test to perform required functions are to be submitted at the time the member arrives at the testing event or ITL.

8. Operational instructions are archived after testing and added to the Certification archive folder established for the implementation.

9. A high-quality digital image of the implementation is archived after the event and is available to the CRB only if the CRB requires it when reviewing an issue relating to the implementation being Certified.

10. The summary of the test results are archived.

11. The summary of the test results are passed to the CRB upon application by the member for Certification.

12. Details of the testing of the implementation are archived after the event and are available to the CRB only if the CRB requires it when reviewing an issue relating to the implementation being Certified.

13. Members may apply to the CRB for Certification after the test event is complete. The application is archived.

14. The information in the application is included in the Integrator’s List data if the implementation meets all the requirements for Certification.




4. The GST-CERTECS certification approach: ATCRF

4.1. Introduction to GST architecture

4.1.1. GST High Level Architecture

GST architecture is based on distributed telematics systems using an heterogeneous communication network. This implies that GST is a complex distributed system interconnecting information processing systems and exchanging information over different kinds of networks with different communication media, different security levels, different data features and using heterogeneous wireless networks.

An overview of the system envisioned by GST is shown in the figure below.

Figure 25. Automobile Telematic System

The complexity of the GST architecture including the convergence of fixed and mobile requires an inspection methodology and tools to verify interoperability of network elements. The inspection methodology applies to the following interfaces:

− eCall interface: eCall interface is described in the RESCUE subproject. The interface consists of Vehicle to PSAP data and voice communication.

− Vehicle to Vehicle (V2V) and Vehicle to Infrastructure (V2I) interfaces: V2V and V2I interfaces are also described in the RESCUE subproject. The interface consists of Vehicle to Vehicle and Vehicle to Infrastructure data communication.

− EFCD interface: EFCD interface is described in the EFCD subproject.

− Safety channel (SC) interface: part of the Safety Channel subproject this defines architecture and a set of specifications which allow for the




aggregation and transmission of high priority and safe messages to in-vehicle Client Systems as defined by GST.

4.1.2. GST technology basics

4.1.2.1 eCall interface The eCall is a pan-European in-vehicle emergency call service intended to reduce the rescue services´ response time by generating an emergency call to the emergency number 112 after an accident or similar distress situation.

The emergency call, automatically generated by vehicle sensors or manually by vehicle occupants, carries both voice and data directly to the nearest emergency service, normally the PSAP (Public Safety Answering Point). Together with the voice connection a set of MSD (Minimum Set of incident Data) is transmitted which includes accurate information on the location of the accident site. Alternatively the terminal may send a larger set of data, the FSD or full set of data. The FSD is sent to a service centre, which is able to forward the data set to the selected PSAP. The automatic triggering of the call together with the location information are the key features to achieve the system objective: reduce the response time.

4.1.2.2. Vehicle to Vehicle (V2V) and Vehicle to In frastructure (V2I) interface The main foreseen road safety warning messages applications involving vehicle-to-vehicle and vehicle to infrastructure communications are: the virtual triangle, the blue wave, accident warning, immobilized vehicle, emergency break, low visibility, low friction and ghost driver.

To support the first two applications the underlying foreseen protocol stack is based on WLAN (Wireless Local Area Network) technology. The specified standards foreseen for this application are known as WAVE (Wireless Access in Vehicular Environments).

4.1.2.3. Enhanced Floating Car Data (EFCD)

EFCD (Enhaced Floating Car Data) sub-project of GST defined the followings goals:

− Generation of safety relevant content by using various in-car sensors linked to the in-vehicle platforms.

− Provision of enhanced event detection and quality measurement to improve data quality.

This technology provides an innovative transport layer for traffic and travel information. Collecting road and traffic information from floating sensors, i.e., sensors in moving vehicles, may allow a better management of the traffic and




the possibility to send safety related information to moving vehicles based on the information collected and processed. Information that may be collected includes: speed of the vehicle; presence of fog in the area; snow conditions, etc.

EFCD subproject goal is, in a long-term perspective, to increase the number of floating car sensors and to collect safety relevant content. The objective can only be achieved through the generation of FCD-data with high quality at reduced cost. The necessary technological developments need to be part of an open EFCD system framework, where different service concepts can coexist and complement each other towards comprehensive coverage and penetration.

4.1.2.4. Safety Channel (SC) Safety Channel is a set of protocols and interfaces which fulfill the requirements of a bearer independent, real time, high priority message channel.

These messages will give a vehicle’s driver early warning and safety information. The messages will not rely on a specific transmission bearer and allow for a full range of safety related services in urban areas and the secondary level road network.

4.1.3. GST Reference models and protocol stacks

4.1.3.1. eCall Reference Model and protocol stack

RESCUE GST subproject is working on this specification for the eCall over a cellular network together with other components of the complete emergency call that involve vehicle-to-vehicle communications. To transmit the minimum set of incident data on the cellular network there are several options. The solution proposed in RESCUE is the use of USSD (Unstructured Supplementary Service Data) a GSM/GPRS/UMTS supplementary service.

Figure 26. eCall Reference Model




The proposed protocol stack to harmonize the system is presented in Fig. x. TCAP (Transaction Capabilities Application Part) enables reliable end to end communication between TCU and PSAP.

4.1.3.2. Vehicle to Vehicle Reference Model and pro tocol stack

WAVE is defined as the operation mode used by IEEE 802.11 devices in the ITS (Intelligent Transportation Systems) communication band. The purpose of this set of specifications is to provide short-range wireless communications among information sources, and roadside infrastructure including forwarding stations and radio mobile units.

The technology used to convey the warning messages is TPEG (Transport Protocol Experts Group).

Figure 27. V2V Reference Model

4.1.3.3. EFCD Reference Model and protocol stack

For the floating car data application designed to support the collecting of road and traffic information there are two alternatives foreseen. One is based on the use of packet switched cellular networks, such as GPRS which is widely deployed across Europe; and the other is via a vehicle to road infrastructure communication based on WLAN type of communications using the WAVE protocol stack.

The Services Centre collecting the information must be able to interface both with the road infrastructure and the cellular packed switched network. Web Services using SOAP (Simple Object Access Protocol) protocol have been selected. SOAP is a protocol for exchanging messages over a network. SOAP has some advantages: it is platform and language independent; it uses XML to send and receive messages; it is usually conveyed over HTTP which eliminates firewall problems; and it is a protocol for exchanging information in a decentralized and distributed environment.




Figure 28. EFCD Reference Model

4.2. Certification scheme (ATCRF)

The Certification step is judged necessary to guarantee to the end users of automobiles that the proposed telematics open systems and services not only will preserve their current level of safety, but will be also contributing to enhance it by the deployment of secure, reliable adding value services acting passively or actively in critical situations in which people or their properties are in danger.

The ATCRF (Automobile Telematics Certification Reference Framework) is the major Certification building block designed to guide the automobile telematics Certification through the definition of economical, organisational, technical and data models to be used for an efficient European Certification of telematics components, systems and services to be deployed by the automobile industry.

ATCRF provides an initial Certification reference framework necessary for the building of the European Certification organisation and all its technical support.

The initial ATCRF includes:

− The description of the Certification operational Process to guide its actors.

− A description of the reference implementations or standards against which the proposed implementations under test shall be tested for conformance.

− A specification of all the requirements (SLA: Service Level Agreement) agreed between the service end users and service providers of all the services which are the target of the inspection and Certification Process.

− A specification of the system (SLS: System Level Specification) which is supposed to satisfy the SLAs of all supported services.




− The formal description of the elements which have to be inspected or to be tested as well as the description of test programmes, test cases, test suites.

4.2.1. GST Certification main players

The CERTECS Certification scheme involves various Entities with specific responsibilities. The table below describes those entities.

Player Description

Automotive Certification Stakeholders Organisation (ATSO)

The ATSO will be an organization constituted of members representing the various interests of the automobile telematics stakeholders. This organization will include some working groups in charge of achieving a permanent survey of all evolutions which may impact the existing ATCRF. This organization will have the mission to develop and update the ATCRF and submit it to the TCA for being used as a reference framework for the Certification of telematics Products/services.

Telematics Certification Advisory Board (TCAB)

The management of the Certification Process is supervised by the Telematics Certification Advisory Board (TCAB). TCAB is a forum of all the directly contributing entities (full members). Other parties may observe the ongoing activities since they might be interested in the Certification Process.

Telematics Certification Authority (TCA)

It establishes the policies and practices of the Certification scheme.

Certification Bodies (CB)

CBs are competent and qualified, accredited bodies that provide part or the whole Certification services to the Applicant seeking for Product Certification. They are responsible for checking and approving test or Inspection plans, reviewing test or inspection reports, as well as checking Technical Documentation against requirements. It has 2 Roles :

• CB Project Manager • CB Scope Manager

Telematic Test Laboratories (TTL)

TTLs are competent and qualified, accredited bodies designated by the TCA, conducting tests of telematics Products within its accreditation scope. For this purpose, it needs qualified personnel, required test platforms and test systems. They will be of course very related to their specialisation. Test plans are generated and executed by TTLs while Inspection plans are by TIBs. Test plans and Inspection plans are a subset of the HLMCP (High Level Certification Master Plan). TTLs generate test reports for Applicants and for CBs. TTLs have 3 Roles:

• TTL Test Laboratory Manager • TTL Test Operation Manager • TTL Scope Manager

Telematic Inspection Bodies (TIB)

TIBs are competent and qualified, accredited bodies designated by the TCA, conducting inspections of telematics Products within its accreditation scope. TIBs generate inspection reports for Applicants and inspection results for CBs. It has 2 Roles:




• TIB Inspector • TIB Scope Manager

Applicant

Applicants could be car manufacturer, service provider, device supplier (hardware and software) seeking for Certification of its Product. Applicants have 2 Roles:

• Applicants Applicant • Applicants Potential Applicant

Furthermore a number of parties may be involved in the GST Certification scheme:

− Accreditation Body: It is an authoritative body that gives formal recognition that a CB, TIB, or TTL is competent to carry out specific tasks. The proof is furnished by inspecting/auditing the body’s competence. It should be mentioned that, as long as no formal accreditation procedure for telematics exists TCA may instead designate the CB, TIB, or TTLs.

− Third Party organizations: They are test and consultancy organizations fully or partially involved in specific Certification elements.

− Automobile & Telematics Industry: non-regulatory companies or groups.

− Regulatory Bodies: national or international bodies who regulate local or regional markets.

The main players and relationships are described in the figure.




Figure 29. ATCRF Organizational Model

4.2.2. Detailed certification process

The ATCRF approach transfers existing certification schemes and practices into the telematics service area. One of the main differences is that the certification scheme relies on the superordinated Telematics Certification Authority (TCA) who gives the right, to Applicants applying for certification of its telematics Product(s), to use the CERTECS Mark, C-Mark.

After all the data and information is collected through the various stages and modules and paths, a number of CBs will issue certificates (within their scope and for the services contracted) if the evaluation of test and inspection results performed by TTLs and/or TIBs, documented in the Test and/or Inspection Report, is successful. On completion of all the certifications, the TCA will grant the Applicant the right to use the C-Mark logo.

4.2.3. Product Classes

Telematics Products have been classified into four classes (see table below) according to the impacts of a service failure on the vehicle occupants and on the vehicle itself.

− Class I: Imperceptible.

− Class IIa: Down graded functionality.




− Class IIb: Serious disruption.

− Class III: Safety affecting.

All services having a direct impact either on the active safety (avoiding an accident) of vehicle occupants or on the passive safety (reducing an accident impacts) will be classified as class III services.

Therefore this classification can be simplified to:

− Safety affecting Products (Class III).

− Non-safety affecting Products (Class I, Class IIa and Class IIb).

Product Classes Scopes of certification (Examples)

III

Safety affecting:

A disruption of the service may have some

serious safety impact for the user, without being

safety critical.

Accident assistance (eCall Service)

Road Hazard Warning

Medical emergency assistance

IIb

Serious disruption:

A disruption of the service may have some

serious cost impact for the user.

IIa

Down graded functionality:

A disruption of the service may have some limited

cost impact for the user.

Navigation

Traffic Info

EFCD

I

Imperceptible:

A disruption of the service does not have any

perceptible safety or cost impact to the user.

Infotainement

eCommerce

mCommerce

A list of typical telematics Products which are supposed to ask for Certification is established by the TCA in consultation with all the stakeholders of the market represented in the Automotive Certification Stakeholders Organisation (ATSO).

It is the TCA which defines the features and the Product families and therefore the scopes of GST certification for each type of Product.

A “typical telematics Product” is described in terms of features which are usually offered by the Product and by related standards. Interpretations on the Product type are done by the TCA, and then are published for information for the laboratories which will use it for determining which tests are to be performed.

4.2.4. Conformity Assessment Modules

Strictly following the established European approach for CE-marking (Council Decision 93/465/EEC) for all conformity assessments two life cycle phases are distinguished: Design and Production. The assessment is subdivided into modules, which comprise a limited number of different procedures applicable




to the Product classes. The modules can be combined to each other in a variety of ways.

Module A: Internal testing and control of productio n or by competent bodies

The Applicant controls the design and production phases. Its Technical file provides evidence of conformity. It draws up a declaration of conformity, which contains all relevant information to identify standards or specifications, the explanation why the Product is categorized into Classes I, IIa or IIb, as well as the Applicant and the Product. The Applicant delivers the conformity declaration to the CB for registration. The CB is not actively involved. This means it does not examine the Technical file and does not issue a Certificate.

Module B: Examination of design.

Module B is of main interest for the Certification Scheme. The need to examine design proposals is essential and the prerequisite for Module D to the Certification Process. Design examination usually takes place on the basis of the Technical file.

Module D: Production quality assurance.

Covers the production phase and follows Module B. It derives from the quality assurance standard EN ISO 9001, with the intervention of an accredited body responsible for approving and controlling the quality system for production, final product inspection and testing set up by the manufacturer.

Telematics Products of main interest for the GST Certification scheme were Class III Products and modules applicable to this Product class are Modules B and D. This first classification approach is based on the security criterion which is not sufficient; therefore a more detailed approach may be developed in the future.

The conformity assessment is therefore subdivided into modules which comprise a limited number of different procedures applicable to the Product Classes:

− Two life cycle phases: Design and Production

− Class III -> Modules B and D.

4.2.5. Certification Steps

This section describes the defined GST certification process. The process concentrates on Module B, Examination of Design of the Process. Test and inspection plans and their relationship in the certification process are described in the figure below.




Figure 30. Tests and Inspection Plans

The steps in the certification process are:

1. The TCA will receive a Certification request, including a summary of the Technical File from the Applicant.

2. The TCA analyses the Applicant’s request to characterize and classify the Product(s) to be certified. Following the results of this initial analysis, the TCA will generate the HLCMP (High Level Certification Master Plans) according to the ATCRF and the nature of the request. In view of the Product(s)’ attributes the complexity of the concerned implementation and its class, the TCA provides the Applicant a list of approved TTLs, TIBs and CBs. This will include the manufacturers own TTL if its accredited scope corresponds to the scope of activity defined in the HLCMP.

3. The Applicant gets in contact with the CBs, TIBs, and/or TTLs that are recognised for the scope of the work.

4. Before the contracts with the TTL(s) and the TIB(s) can be concluded, Test Plans/ Inspection Plans must be agreed between the selected and involved CB and the TTLs/TIBs. Their contents are derived from the applied standards (SLA, SLS, reference implementation, international standard, or guide line). The Test Plan/Inspection Plan can be either directly submitted by the CB or a proposal from the TTL/TIB approved by the CB.

5. This information exchange allows all parties to estimate test/inspection efforts, costs and duration and to conclude a contract between the Applicant and the TTL and the Applicant and the TTL/TIB about the various steps to be followed and the documents and implementations to be provided.

6. Following the agreed Test Plans/Inspection Plans, the tests inspections are executed by the TTLs and TIBs.

7. After tests/inspections executions, each TTL/TIB will provide the results to the selected and responsible CB. The CB evaluates them for conformity with




the applied standards (SLA, SLS, international standards, reference implementations) and test/inspection procedures. Simultaneously the Applicant receives the comprehensive test/inspection report from the TTLs/TIBs.

8. When all tasks of the TCA’s HLCMP are fulfilled and when all the data and reports collected during the various stages of the certification Process are completed, the CB(s) evaluate(s) the test and inspection results and issues a/several Type Examination Certificate to the Applicant. Simultaneously the Evaluation Report(s) and Certificate(s) is/are provided to the TCA.

The whole certification process is graphically described in the following figure:

Figure 31. Certification Process

5. Automotive Regulatory Procedure

Directive 70/156/EEC defines "vehicles" as follows: "any motor vehicle intended for use on the road, being complete or incomplete, having at least 4 wheels and a maximum design speed exceeding 25 km/h, and its trailers, with the exception of vehicles which run on rails and of agricultural and forestry tractors and all mobile machinery." This includes passenger cars, trucks, vans, coaches, caravans and motor caravans (RV). Motorcycles are covered by the frame directive 92/61/EEC. "Components", in the sense of the directive, are electrical and electronic sub-assemblies intended to be part of a vehicle,




together with any associated connections and wiring, which perform specialized functions.

The EU commission recognized shortcomings in the European Automotive EMC Directive 95/54/EC2 almost as soon as it was released as it contained conflicts with other international standards. It was considered by most automotive Original Equipment Manufacturers (OEMs) as being inadequate as a basic standard for automotive products primarily due to lack of conducted transient testing in the directive. Another area of concern expressed by aftermarket equipment suppliers was the status of aftermarket products with "CE" approval to the generic EMC directive (89/336/EEC) and telecommunication products type approved to the R&TTE directive (1999/5/EC) that have no control function in the vehicle. The current status of these products in 95/54/EC is that after October 2002 these have to be "e"-marked for vehicle use.

5.1. EC Directives

The European Parliament has enacted a series of measures intended to put the Single Market into practice through a set of Directives. Some of these Directives have been aimed at removing barriers of a purely customs/excise nature, others have concentrated on transport arrangements to ensure the free movement of goods, while a series of Directives, produced under the heading of `New Approach Directives' and promoted by the three European Standards Organisations (CEN, CENELEC and ETSI) together with both the European Commission and EFTA (European Free Trade Association), are intended to provide controls on product design, with the principal objective being to provide a `level playing field' for product safety requirements across the European Community.

The directives cover a very wide range of product areas such as machinery, electromagnetic compatibility (EMC), personal protective equipment, medical devices, gas appliances and commercial explosives, among others. Concerning to automotive products and particularly on telematics products, the most relevant EC Directives are:

− Council Directive 89/336/EEC: Electromagnetic Compatibility and its new version 2004/108/EC.

− Council Directive 1999/5/EC: Radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity.

− Council Directive 95/54/EC on EMC in automotive and its new version 2004/104/EC.

− Council Directive 95/46/EC: Protection of individuals with regard to the processing of personal data and on the free movement of such data.

− Council Directive 2000/53: Principles on human machine interface, HMI.




− Council Directive 93/465/EEC: Modules for conformity assessment and rules for CE marking.

− Council Directive 2004/52/EC: Interoperability of electronic road toll systems in the Community.

5.2. EMC Directives

A new Automotive EMC Directive (2004/104/EC) was published. The European Commission published the Directive 2004/104/EC on 13th November 2004 followed by 2005/49/EC, 2005/83/EC and the new adoption directive 2006/28/EC on 6th March 2006 concerning the EMC of motor vehicles and their electrical and electronic components, which forms part of European legislation for automotive type approval.

This Directive, adopted by 2005/49/EC, 2005/83/EC and 2006/28/EC replaces the previous automotive EMC directive 95/54/EC, which was based on 72/245/EEC, a directive handling only the on the suppression of electrical noise from spark-ignition engines.

e-marking will not be required under the new Directive for non-immunity related aftermarket accessories, but manufacturers will need to self-certify compliance with the requirements for emissions and conducted transients and obtain a certificate from the automotive authorities certifying that their products are not related to immunity and do not need type approval. The time schedule of these Directives is:

− With effect from 01. July 2006 the current Directive 2006/28/EC (2004/104/EC) will be applied.

− With effect from 01. July 2006 the previous Directive 95/54/EC cannot be applied any longer for new approvals.

− With effect from 01. January 2009 all devices have to comply with the Directive 2006/28/EC (2004/104/EC).

Next table illustrates a comparison of EMC-requirements between the old (95/54/EC) and new directive (2004/104/EC).

Directive 95/54/EC Directive 2006/28/EC (2004/104/EC)

Electromagnetic radiation measurements: - Broadband/Narrowband - Frequency range: 30 ~ 1000 MHz

Electromagnetic radiation measurements: - Broadband/Narrowband - Frequency range: 30 ~ 1000 MHz

Immunity to electromagnetic radiation - Frequency range: 20 to 1000 MHz - AM 80%, 1 KHz - Different test methods

Immunity to electromagnetic radiation - Frequency range: 20 to 2000 MHz - AM 80%, 1 KHz up to 800 MHz. PM

from 800 to 2000 MHz - Different test methods

Immunity against disturbances conducted along supply lines (ISO test pulses 1 ~ 4)

Emission of conducted disturbances along supply lines




The new directive is a significant improvement over the old directive. It is both clearer in the requirements and test levels. In using international automotive test standards it brings the test methods for the EU directive in-line with the test configurations used by most automotive OEMs. In the future translating the results from "e"-mark testing to an OEM specification will be much more straightforward.

5.3. Automotive EMC Directives Applicability

The Automotive EMC Directive requires manufacturers to gain type approval for all vehicles and electronic sub assemblies (ESAs), components and separate technical units (STUs) to be used in vehicles. Certain types of equipment are exempt from certain tests. This means that any device, or a part of the vehicle (whether it is an original part or an after market part) needs to be approved before it can be sold. Moreover, some ESAs, sold as aftermarket equipment and intended for installation in motor vehicles, need no type approval according to the Directive 2006/28/EC (2004/104/EC) if they are not related to immunity-related functions.

Products that are not permanently wired to the vehicle harness and can be removed without specialist tools, or are technically restricted to operation while the vehicle is stationary, will no longer have to prove compliance to the Automotive EMC directive once 2004/104/EC comes into effect. Such products can be CE marked (if necessary) and obtain a Declaration of Conformity via the generic EMC directive (89/336/EEC) processes; this includes self-certification and technical construction file (TCF) routes to compliance.

This change to the automotive EMC directive provides a method for some suppliers to reduce their testing by self certifying products (CE marking) based on "use of known good circuits" and TCF. However, there may be a commercial imperative to retain "e"-marking on some products to maintain credibility in the automotive marketplace. There could also still be the dictated requirement from aftermarket product retailers, forcing "e"-mark testing on the product by otherwise threatening to remove from their sales portfolio. It is highly unlikely that automotive OEMs will approve products for fit to their vehicles (e.g., at franchised dealerships), even as aftermarket items, if "e"-mark certification is not obtained as a minimum.

Additionally, the vehicle manufacturer is required to make a statement on the requirements for installation of RF transmitters in their vehicles following R&TTE directive as part of their application for approval certification to 2004/104/EC. Some of these directives are defined by ETSI in EN 301 489-X and are shown in next table.

Directive Equipments

EN 301 489-01 v1.6.1 Common technical requirements




EN 301 489-02 v1.3.1 Radio paging equipment

EN 301 489-03 v1.4.1 Short-Range Devices (SRD) operating on frequencies between 9 kHz and 40 GHz

EN 301 489-04 v1.3.1 Fixed radio links and ancillary equipment and services

EN 301 489-05 v1.3.1 Private land Mobile Radio (PMR) and ancillary equipment (speech and non-speech)

EN 301 489-06 v1.2.1 Digital Enhanced Cordless Telecommunications (DECT) equipment

EN 301 489-07 v1.3.1 Mobile and portable radio and ancillary equipment of digital cellular radio telecommunications systems (GSM and DCS)

EN 301 489-08 v1.2.1 GSM base stations

EN 301 489-09 v1.3.1 Wireless microphones, similar Radio Frequency (RF) audio link equipment, cordless audio and in-ear monitoring devices

EN 301 489-10 v1.3.1 First (CT1 and CT1+) and Second Generation Cordless Telephone (CT2) equipment

EN 301 489-11 v1.3.1 Terrestrial sound broadcasting service transmitters

EN 301 489-12 v1.2.1 Very Small Aperture Terminal, Satellite Interactive Earth Stations operated in the frequency ranges between 4 GHz and 30 GHz in the Fixed Satellite Service (FSS)

EN 301 489-13 v1.2.1 Citizens' Band (CB) radio and ancillary equipment (speech and non-speech)

EN 301 489-14 v1.2.1 Analogue and digital terrestrial TV broadcasting service transmitters

EN 301 489-15 v1.2.1 Commercially available amateur radio equipment

EN 301 489-16 v1.2.1 Analogue cellular radio communications equipment, mobile and portable

EN 301 489-17 v1.2.1 2,4 GHz wideband transmission systems and 5 GHz high performance RLAN equipment

EN 301 489-18 v1.3.1 Radio equipment and services; Part 18: Specific conditions for Terrestrial Trunked Radio (TETRA) equipment

EN 301 489-19 v1.2.1 Receive Only Mobile Earth Stations (ROMES) operating in the 1,5 GHz band providing data communication

EN 301 489-20 v1.2.1 Mobile Earth Stations (MES) used in the Mobile Satellite Services (MSS)

EN 301 489-22 v1.3.1 Ground-based VHF aeronautical mobile and fixed radio equipment

EN 301 489-23 v1.2.1 IMT-2000 CDMA Direct Spread (UTRA) Base Station (BS) radio, repeater and ancillary equipment

EN 301 489-24 v1.3.1 IMT-2000 CDMA Direct Spread (UTRA) for Mobile and portable (UE) radio and ancillary equipment

EN 301 489-25 v2.3.2 CDMA 1x Spread Spectrum Mobile Stations and ancillary equipment

EN 301 489-26 v2.3.2 CDMA 1x spread spectrum base stations, repeaters and ancillary equipment

EN 301 489-27 v1.1.1 Ultra Low Power Active Medical Implants (ULP-AMI) and related peripheral devices (ULP-AMI-P)

EN 301 489-28 v1.1.1 Wireless digital video links

EN 301 489-31 v1.1.1 Radio equipment in the 9 to 315 kHz band for Ultra Low Power Active Medical Implants (ULP-AMI) and related peripheral devices (ULP-AMI-P)




EN 301 489-32 v1.1.1 Ground and Wall-Probing Radar applications

5.4. e-marking

The 2004/104/EC Directive has a different approval mark from the CE mark directives. Instead of the CE logo, products approved to this Directive should carry the ‘e’ mark. This mark consists of a rectangle surrounding the letter 'e' followed by the distinguishing number or letters of the Member State which has granted type-approval.

The marking must also include, in the vicinity of the rectangle, the four-digit sequential number, referred to as 'base approval number', preceded by two figures indicating the sequence number assigned to the most recent major technical amendment to Directive 72/245/EEC on the date EEC component type-approval was granted. (The test house or Technical Service will advise the manufacturer of this number during the approval process.)

If an electrical or electronic system has been approved as part of a whole vehicle test then that system does not require "e" marking. The same system sold as a spare part will also not require "e" marking. It is, however, recommended that the packaging bears the "e" mark. Next table contrasts the processes of compliance between the Automotive (e-marking) and EMC Directives (CE marking). The major difference between e-marking and CE marking is the route to approval. For CE marking, manufacturer self-declaration is the norm, whereas the only route to compliance with the Automotive Directive is formal type approval. Each of the EU member states ( Austria, Belgium, Denmark, Finland, France, Germany, Greece, Island, Ireland, Italy, Liechtenstein, Luxemburg, Holland, Norway, Portugal, Spain, Sweden, United Kingdom, Cyprus, Czech Republic, Estonia, Hungary, Latonia, Lithuania, Malta, Poland, Slovakia, Slovenia) has a national body responsible for issuing type approval certificates

e-marking (2004/104/EC) CE-marking (89/336/EEC)

EMC limits and test methods all defined in legislation 2004/104/EC

Select appropriate EMCcriterion, identify applicableEMC standards, decide on route to compliance.

Develop compliant product. Develop compliant product.

Submit product for formal type approval. Submit TFC, submit for third-party testing.

Apply e-mark and sell. Conformity, apply CE mark, and sell.

Compliance with the EMC Directive usually involves selecting and applying standards from the ever-growing, ever-changing list published in the Official Journal of the European Communities. For the Automotive Directive, the process is simplified (in principle) because the directive contains within it all the test methods and limits necessary for compliance.

Manufacturers and their representatives should note, however, that 2004/104/EC compliance does not absolve them from compliance with other




applicable European legislation. For example, a product that can be fitted in a vehicle or used at home must comply with both the Automotive and EMC Directives. If a product contains a radio transmitter, it must also comply with the R&TTE Directive (as section above described), and so on. In all cases, a product must be safe when used as intended and should not impair a driver's ability to properly control the vehicle.




6. Conclusions This deliverable has described some relevant certification programs worldwide extracting the most appropriate concepts and approaches which could be applicable for the proper definition of the SAFEPOT certification reference framework. It is clear that to define the certification scheme for SAFESPOT it is important to review existing schemes and to understand the processes, the stakeholders involved, and the main decisions that have to be taken before defining an appropriate certification scheme.

The complete definition of the scheme needs a more complete definition of the architecture (which is currently in the process of definition). Therefore, the deliverable has been divided in two parts. The first part, the Part A, that includes a review of existing schemes and the key elements; and the Part B (to be delivered later) that will include the actual definition of the scheme for SAFESPOT.




7. References [1] ETSI ETS 300 406, V1: (1995-04). “Methods for Testing and

Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology”.

[2] ISO/IEC 17025: 2000. “General Requirements for the Competence of Calibration and Testing Laboratories”.

[3] Bluetooth Core Specification version 2.0. Owner: Bluetooth SIG.

[4] Bluetooth Qualification Program version 1.0. Owner: Bluetooth SIG.

[5] Bluetooth Qualification Program version 2.0. Owner: Bluetooth SIG.

[6] IEEE Std. 802.11: 1999. (ISO/IEC 8802-11: 1999) “IEEE Standards for Information Technology - Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Network - Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications”.

[7] IEEE Std. 802.16: 2004. “IEEE Standard for Local and metropolitan area networks Part 16: Air Interface for Fixed Broadband Wireless Access Systems”.

[8] “The WiMAX Forum Certified Program for Fixed WiMAX”. January 2007. Prepared by Senza Fili Consulting on behalf of the WiMAX Forum.

[9] “What WiMAX Forum Certified will bring to 802.16”. WiMAX whitepaper. Available at www.wimaxforum.org.

[10] Wi-Fi Alliance. “Authorized Test Laboratory Procedures Manual”. Version 2.0. October 2006.

[11] “Wi-Fi CERTIFIED makes it Wi-Fi. An Overview of the Wi-Fi Alliance Approach to Certification”. Wi-Fi Alliance White Paper. Available at www.wi-fi.org

[12] “DLNA Overview and Vision Whitepaper 2006”. Digital Living Network Alliance whitepaper. Available at www.dlna.org.

[13] “Digital Living Network Alliance Certification Process”. Version: 1.0 September 22, 2005.

[14] Incisor Magazine. June 2007.

[15] CERTECS Deliverable 4.1. “Certification Process Implementation”. Version 1.0

[16] CERTECS Deliverable 7.4. “ATCRF Initial Version”. Version 1.0.

[17] “ZigBee Alliance Certification and Testing Policy”, ZigBee Alliance, revision 18