SKELETON · Web viewEssential patents IPRs essential or potentially essential to the present...

SKELETON

ETSI TS 103 568 V1.1.1_0.0.1 (2018-02)

17

ETSI TS 103 568 V1.1.1_0.0.1 (2018-02)

RX-requirements for Automotive

and Surveillance Radar Equipment

<

TECHNICAL SPECIFICATION

Reference

DTS/ERM-TGSRR-79

Keywords

Measurement, RECEIVER, SRD

ETSI

650 Route des Lucioles

F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la

Sous-préfecture de Grasse (06) N° 7803/88

Important notice

The present document can be downloaded from:http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx.

If you find errors in the present document, please send your comment to one of the following services:https://portal.etsi.org/People/CommiteeSupportStaff.aspx

Copyright Notification

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.

The content of the PDF version shall not be modified without the written authorization of ETSI.

The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI yyyy.

All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.3GPPTM and LTE™ are trademarks of ETSI registered for the benefit of its Members andof the 3GPP Organizational Partners.oneM2M logo is protected for the benefit of its Members.GSM® and the GSM logo are trademarks registered and owned by the GSM Association.

Contents

Intellectual Property Rights4

Foreword4

Modal verbs terminology4

Executive summary4

Introduction4

1Scope5

2References5

2.1Normative references5

2.2Informative references5

3Definitions, symbols and abbreviations5

3.1Definitions5

3.2Symbols5

3.3Abbreviations5

4User defined clause(s) from here onwards6

4.1User defined subdivisions of clause(s) from here onwards6

Annex A (normative or informative):Title of annex7

Annex (informative):Bibliography8

Annex (informative):Change History9

History10

Intellectual Property Rights

Essential patents

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Trademarks

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

Foreword

This Technical Specification (TS) has been produced by ETSI Technical Committee {ETSI Technical Committee|ETSI Project|} ().

Modal verbs terminology

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

Executive summary

To be prepared

Introduction

To be prepared

1Scope

The present document …

2References2.1Normative references

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference.

NOTE:While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.

The following referenced documents are necessary for the application of the present document.

[1]

2.2Informative references

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

NOTE:While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.

The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.

[i.1]

3Definitions, symbols and abbreviations3.1Definitions

For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:

3.2Symbols

For the purposes of the present document, the [following] symbols [given in ... and the following] apply:

3.3Abbreviations

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

4Requirements; Use-Case

Open points / for discussion

Some radar sensors need a Doppler reflector. They have no simple RCS formula.

Some sensors may report blindness error in Receiver empty test.

Values needs to be checked and approved for each EN could be differentComment by Mahler Michael (C/AGT): Important action for all TG SRR membersEN 301 091-1EN 301 091-2EN 301 091-3EN 302 858EN 3021 264EN 303 360EN 302 288

followed by: usability for testing (e.g. distance values), realizable test methods

For F: permitted or occupied bandwidth shall be used (for remote band)

For the for adjacent-band a fixed value from the edge could be used (instead of F)

Evaluation of ground reflections: they could influence tests in larger distances

Points why TG SRR EUT are not comparable with maritime/avionic radars (not for the EN but for argumentation on EC level)Comment by Mahler Michael (C/AGT): See discussion on new informal annex in EN 303 396

4.1General

Note: also explains why test signals and test output points are not generally available. EUT is presented as “black-box”.

Only typical EUT output information could be used, like warning light flag, detection list of object, track list of objects, …

This is necessary because on RE-D the EUT needs to work as intended (no specific test software)

To be discussed

Add: Manufacturer to declare RF input power for RF 1dB compression point.

Add Manufacturer to declare RF input power for LF clipping point

or shall a test be prepared? Or no need?Comment by Mahler Michael (C/AGT): Based on discussions more likely that a test would be necessary

4.2Applications under 301 091-14.2.1 Automotive radar use-case

Classification of radars under 301 091-1 [i.X]Comment by Mahler Michael (C/AGT): Reference to EN or ECC/EC regulation?

Use-Case

Object (worst case)

Max. measurable distance

Ultra Short Range Radar (USRR)

< 20m

Short Range Radar (SRR)

< 50m

Mid Range Radar (MRR)

< 100m

Long Range Radar (LRR)

< 250m

Super Long Range Radar (SLRR)

> 250m

4.2.2 Other ground based vehicular radar use-case

Use-Case

Object (worst case)


4.3Applications under 301 091-2


Use-Case

Object (worst case)


4.4Applications under 301 091-3


Use-Case

Object (worst case)


4.5Applications under 302 264

Classification of radars under 302 264 [i.X]Comment by Mahler Michael (C/AGT): Reference to EN or ECC/EC regulation?

Use-Case

Object (worst case)


5RX-tests5.1 General requirements

Manufacturer shall declare “EUT output update rate”.

Manufacturer shall declare “the typical output of the sensor”, like target tracking list, warning flag,….. (list needs to be defined and specified definition section)

Manufacturer shall choose one of the use-case / categories the radar device

5.2RX-test procedure

The RX-test procedure for surveillance radar application covered by this document is split into three parts

1. Receiver empty test (clause 6)

2. Receiver Sensitivity test (clause 7)

3. Receiver Blocking test (clause 8)

For each test the wanted performance criteria is specified as percentage of positive detections of given number of EUT output update rates (radar cycles)

6Receiver empty test6.1 Description

Text

6.2 Wanted performance criteria6.2.1 General

The wanted performance criteria shall be fulfilled with least over 1000 EUT output update rate

6.2.2Requirements

Class

Given target

Given interferer

Criterion

USRR

None *

None

No object with constant D,v properties < 5 % of all radar cycles

SRR

None *

None


MRR

None *

None


LRR

None *

None


Super LRR

None *

None


7Receiver sensitivity test7.1 Description of the principal

Text to explain and to compare with “traditional” RX-requirements

Comment by Mahler Michael (C/AGT):


Test time = 1000 * EUT output update rate

Target positioned in main beam direction

7.2.2Requirements

ClassComment by Mahler Michael (C/AGT): To add more tables (based on clause 4) or all in one table with separations

Given target

Given interferer

Criterion

USRR

RCS = -10dBsm @ 10mComment by Mahler Michael (C/AGT): There must be a link from clause 4 (kind of object) to the given RCS justification Annex

None

95 % probability of detection (Note)

SRR

RCS = 0dBsm @ 20m

None


MRR

RCS = 10dBsm @ 50m

None


LRR

RCS = 10dBsm @ 150m

None


Super LRRComment by Mahler Michael (C/AGT): Super LRR could be more a scenario for 091-2

RCS = -10dBsm @ 500m

None


Note: How many “EUT output update rates“ show the given target at the given distance with an accuracy of up to +/- 5%.

Discussion point: If such long measuring distances are not possible within a certified test environment, then scaled down distances and scaled down RCS, or target simulators can be used.

7.3 Conformance test

Situation:

A EN (later) shall be clear and shall not provide options also for the conformance tests.

In this TS we can propose “free-space” test within a camber or OAS or we propose test with a target simulator.

The EN later needs to only one clear reference or includes only one solution.

Other option for the EN: we add requirements e.g. for USRR chamber test. For LRR target simulator test.

Open: what shall we do if a sensors need “moving” objects / Doppler info target simulator only?

Other options?

8Receiver Blocking test8.1 Description of the principal

Text to explain and to compare with “traditional” RX-requirements

Text, Note: the current explanation on the EN could be reused


Test time = 1000 * EUT output update rate

Target positioned in main beam direction

The interference signal source is positioned within the 3dB beam width at the operating center frequency of the RX boresight.

8.2.2Requirements for in-band interferer

ClassComment by Mahler Michael (C/AGT): To add more tables (based on clause 4) or all in one table with separations

Given target

Given interferer

Criterion

USRR

RCS = -10dBsm @ 10mComment by Mahler Michael (C/AGT): There must be a link from clause 4 (kind of object) to the given RCS justification Annex

55mV/m @ FMCWComment by Mahler Michael (C/AGT): Description with in Annex


SRR

RCS = 0dBsm @ 20m

55mV/m @ FMCW


MRR

RCS = 10dBsm @ 50m

55mV/m @ FMCW


LRR

RCS = 10dBsm @ 150m

55mV/m @ FMCW


Super LRRComment by Mahler Michael (C/AGT): Scenario for 091-2


55mV/m @ FMCW


Note: How many “EUT output update rates” show the given target at the given distance with an accuracy of up to +/- 5%.

Discussion point: If such long measuring distances are not possible within a certified test environment, then scaled down distances and scaled down RCS, or target simulators can be used.

Further test details:

Check for given interferer parameters whether declared RF 1dB compression point is reached.

Check for given interferer parameters whether declared LF clipping point is reached.

8.2.3Requirements for adjacent-band interferer

Class

Given target

Given interferer

Criterion

USRR

RCS = -10dBsm @ 10m

173 mV/m @ f = fc ± F


SRR

RCS = 0dBsm @ 20m

173 mV/m @ f = fc ± F


MRR

RCS = 10dBsm @ 50m

173 mV/m @ f = fc ± F


LRR

RCS = 10dBsm @ 150m

173 mV/m @ f = fc ± F


Super LRRComment by Mahler Michael (C/AGT): For 091-2


173 mV/m @ f = fc ± F



· F= permitted operating bandwidth.Comment by Mahler Michael (C/AGT): Or real operating BW

8.2.4Requirements for remote band interferer

Class

Given target

Given interferer

Criterion

USRR

RCS=-10dBsm @ 10m

173 mV/m @ f = fc ± 10 × F


SRR

RCS=0dBsm @ 20m

173 mV/m @ f = fc ± 10 × F


MRR

RCS=10dBsm @ 50m

173 mV/m @ f = fc ± 10 × F


LRR

RCS=10dBsm @ 150m

173 mV/m @ f = fc ± 10 × F


Super LRR

RCS=-10dBsm @ 500m

173 mV/m @ f = fc ± 10 × F



F= permitted operating bandwidth .Comment by Mahler Michael (C/AGT): Or real operating BW

8.3 Conformance test

See comments in clause 7.3

Annex A (normative or informative):Interferer SignalComment by Mahler Michael (C/AGT): Is interferer specific of the use-case, justification necessary why FMCW or CW

FMCW Interferer for in-band interferer testsComment by Mahler Michael (C/AGT): Additional to check outcome STF 494 “Interferer” investigation for (T)LPR within 7xGHz range

Comments:

•Modulated interferer signal does not give constant interference. To get stable results a long measurement time might be needed.

•Action: Interferer FMCW details to be defined.

•55mV/m is equal to an 10dBm (e.i.r.p) interferer in 10m distance

CW interferer for

Comment:

Interferer: CW as current EN version

173mV/m is equal to an 20dBm (e.i.r.p) interferer in 10m distance

F= permitted operating bandwidth.

Annex B (informative):Radar target reflectorsB.1General remarks

In radar measurements power is transmitted towards a target and the reflected power is received. The received power depends – among others – on the radar cross section σ of the target:

P_Rx σ

The radar cross section σ in turn depends on several parameters:

· Frequency of radar signal

· Target material

· Target shape

· Target size

· Target motion

For a target in a real world traffic scenario, like a vehicle or a pedestrian, the material, shape and size vary with the incident angle so that the radar cross section varies as well:

Figure X.1: Exemplary radar cross section of a vehicle at 24 GHz [T. Schipper et al.].

Figure X.2: Exemplary radar cross section of a pedestrian at 77 GHz [EC Joint Resarch Center].

For stable radar test results a target reflector with less variability in radar cross section is prefered.

This annex in the following describes three different classes of such target reflectors.

Corner reflector RCS / dBsm

Corner reflector dimension / mm @ 76 GHz

Spherical reflector dimensions

(diameter in mm)

-40

4,4

11.4

-30

7,5

-20

14

-10

24

0

42

10

78

If such long measuring distances are not possible, then scaled down distances and respectively corrected RCS, for example:

Distance scaling factor

RCS correction

0,5

-12 dB

0,1

-40 dB

B.2Direct target reflectors

By using well conducting metal as material and by limiting the complexity of the geometric shape and by avoiding motion, reflectors can be realized for which the reflection behavior is simple enough to be analytically computed.

Examples are:

By adding motion to a direct target reflector the occurring Doppler effect causes the reflected power to be shifted in frequency (fC + fD):

fD = 2 vr /

Motion towards the radar sensor gives a positive frequency shift while motion away from the radar sensor gives a negative frequency shift.

An example of such a reflector is a rotating fan.

B.3Delay line target reflectors

To realize a target reflector at a distance larger than the size of a test lab, a wound-up waveguide can be used as shown in Fig. X.3.

Short

Horn antenna

Wave- guide

Wound-up waveguide

Figure X.3: Schematic diagram of a delay line target reflector with wound-up waveguide.

The effective length is equal to the waveguide length multiplied by the ratio of speed of light in free space and phase velocity in the waveguide.

B.4Electronic target reflectors

Using analogue electronic components like amplifiers and phase shifters, then the radar cross section and Doppler frequency shift can be adjusted (see for example Fig. X.4).

Horn antenna

Phase shifter

Figure X.4: Schematic diagram of an analogue electronic target reflector.

Using digital electronic components like ADCs, DACs and processors, then the target reflector properties can be adjusted in a very general way (see for example Fig. X.5).

Down converter

Horn antenna

~

Up converter

ADC

DAC

Fast digital signal processor

LO

Figure X.5: Schematic diagram of a digital electronic target reflector.

Annex C (normative or informative):Target Simulator

Annex D (normative or informative):Detailed test setup

Annex E (normative or informative):Rx processing stages in EUT and interference evaluation

Component

Output signal

Interference effect and impactComment by Mahler Michael (C/AGT): Discussion:Two members opposed and requested to delete the third columnThe table was proposed to give arguments e.g. for discussion with EC desk officer. Three members stated we need such arguments.Note: Chairman: if we are different from the ETSI Guide for EN the arguments needs to be written somewhere.Note by one member: we should try to avoid building standards around specific architectures. The standards should try to test important likely failure modes.TGSRR#29:After discussion: all participants agreed that such arguments are necessary Proposal is a good starting point Place (within which doc) needs to be discussedNote: figure2 out M1452.2 could be used in addition

Remarks

Rx antenna

Analogue RF signal(for each Rx channel)

t.b.d

Not suitable as interference test criterion as normally no connection point available.

RF homodyne downconverter

Analogue LF signal(for each Rx channel)

Large interference power can lead to exceeding the RF 1dB compression point. Exceeding the RF 1dB compression point can cause generation of harmonic frequencies which could be interpreted as ghost targets.

LF amplifier with bandpass characteristics

Analogue LF signal(for each Rx channel)

Large interference power can lead to exceeding the LF 1dB compression point. Exceeding the LF 1dB compression point can cause generation of harmonic frequencies which could be interpreted as ghost targets.

AD converter

Digital values(for each Rx channel)

Outliers.

Not suitable as interference test criterion as ADC values are not available at outer connector of sensor.

FFT

2D spectrum(for each Rx channel)

Increase of noise level and downgrading of S / N

Not suitable as interference test criterion as FFT spectrum normally is not available at outer connector of sensor.

Raw signal processing(detect peaks in FFT spectrum, from peaks compute target distance, …)

At the end of each radar cycle:List of raw targets, each described by distance, speed, azimuth angle, reliability

Reduced accuracy of raw target properties, loss of raw targets, generation of pseudo raw targets.

Object tracking(improve result reliability by checking plausibility, …)

At the end of each radar cycle:List of objects, each described by distance, speed, azimuth angle

Reduced accuracy of object properties, delayed generation of objects, loss of objects

Not suitable as interference test criterion here because object properties are influenced by driving situation. Given measurement setup is not a realistic driving situation.

Warning algorithm, action to vehicle brakes, …

At the end of each radar cycle:Message to the driver or to the vehicle

Wrong warning / action, delayed warning / action.

Not suitable as interference test criterion here because warning / action is influenced by driving situation. Given measurement setup is not a realistic driving situation.

Annex F (normative or informative):idea/discussions on NF measurement technique.

Discussions on NF measurement technique.

Slight variations in the procedures are possible. Eg move the target towards to the EUT and note the range at which is it detected, rather than check whether it is detected at a given range. This means that the operation of the EUT is the same for the detection test and the non-detection test.

One issue is the indication or output from the EUT. But this is the same issue for any type of Rx test.

Biggest problem identified is injecting the ENR noise signal in a radiated measurement.

A path loss calculation showed the noise source has to be at least 35 dB ENR. Commercially available noise sources are only up to 15 dB ENR.

So one question is: Is there a standard technique for a radiated NF measurement on a radar?

Summary:

TGSRR investigated the feasibility of a NF measurement, as described in https://docbox.etsi.org/ERM/ERMTGSRR/05-CONTRIBUTIONS/2017//ERMTGSRR(17)029015r1_Noise_Figure_approach_to_Rx_specifications.docx

Additional contribution/for discussion:

https://docbox.etsi.org/ERM/ERMTGSRR/05-CONTRIBUTIONS/2017/ERMTGSRR(17)029021_Probablity_of_Detection_approach_to_Rx_specifications.docx

The technique is interesting, but the problem is that it would have to be performed as a radiated rather than a conducted measurement.

It would not be easy for a test house to perform this test. It would require assembly of test equipment and there would be a difficulty of calibration.

No examples have been found of other bodies performing radiated NF measurements.

Other Notes

The value of Rx sensitivity (or similar) measurement is questionable.

It cannot be separated from a system performance measurement and is therefore not actually a Rx measurement.

Regarding the RED requirement to use the spectrum effectively and efficiently, the value of a measurement such as Rx NF is questionable. It could be argued that the manufacturer has to produce an EUT with a reasonable NF or he does not have a working product

Discussed during the meeting: “function of an “Sensor””

Annex (informative):Bibliography

Annex (informative):Change History

Date

Version

Information about changes

02/28/2018

0.0.1

Initial version based on https://docbox.etsi.org/ERM/ERMTGSRR/05-CONTRIBUTIONS/2018/ERMTGSRR(17)029016r3_Summary_RX-Requirement_discussion.docx

History

Document history

Latest changes made on 2017-07-10

ETSI

SKELETON · Web viewEssential patents IPRs essential or potentially essential to the present...

Documents

Transcript of SKELETON · Web viewEssential patents IPRs essential or potentially essential to the present...