ecall GOST 33464 MSD数据结构分析 —— 根据ASN.1语法

        GOST 33464中对MSD数据(minimum set of data)的结构规定是用ASN.1语法描述的。下面以version2版本为例分析MSD数据结构,并给出一种可能的实际数据结构示例。

        首先是GOST 33464: 2015附录C.3, C.5中的描述:

序号参数名参数类型及范围
1 IDINTEGER
(1...255)
2 Message IdentifierINTEGER
(1...255)
3ControlAutomatic ActivationBOOLEAN
4Test CallBOOLEAN
5Position Can Be TrustedBOOLEAN
6Vehicle TypeENUM
7VINSTRING(17)
8Vehicle Propulsion Storage TypeGasoline Tank PresentBOOLEAN
9Diesel Tank PresentBOOLEAN
10Compressed Natural GasBOOLEAN
11Liquid Propane GasBOOLEAN
12Electric Energy StorageBOOLEAN
13Hydrogen StorageBOOLEAN
14 Time StampINTEGER
(0..2^32
-1)
15Vehicle LocationPosition LatitudeINTEGER
(-2^31...2^31
-1)
16Position LongitudeINTEGER
(-2^
31...2^31-1)
17 Vehicle DirectionINTEGER
(0...255)
18Recent Vehicle Location N1Latitude DeltaINTEGER
(-512...511)
19Longitude DeltaINTEGER
(-512...511)
20Recent Vehicle Location N2Latitude DeltaINTEGER
(-512...511)
21Longitude DeltaINTEGER
(-512...511)
22 Number Of PassengersINTEGER
(0...255)
23Optional Additional DataoidRELATIVE
OID
24dataOCTET
STRING
MSDASN1Module_V2
DEFINITIONS
AUTOMATIC TAGS ::=
BEGIN
-- MSD specification version
CurrentId::= INTEGER (2)
-- ECallMessage is an upper level data element
-- It supports one message type only (msd)
-- Elements:
-- id: MSD data format, set to 1
-- msd: minimum set of data transmitted from IVDS side, except for ID
ECallMessage ::= SEQUENCE {
msdVersion INTEGER(0…255),
msd OCTET STRING (CONTAINING MSDMessage)
}
-- Message sent from IVDS side (ID is excluded)
-- Elements:
-- msdStructure: main MSD structure
-- optionalAdditionalData: additional data
-- May be extended at this level in future versions
MSDMessage ::= SEQUENCE {
msdStructure MSDStructure,
optionalAdditionalData AdditionalData OPTIONAL,
...
}
-- Main MSD structure without any additional data
-- Elements:
-- messageldentifier: message identifier
-- control: see ControlType
-- vehicleldentificationNumber: see VIN
-- vehiclePropulsionStorageType: see VehiclePropulsionStorageType
-- timestamp: time stamp
-- vehicleLocation: see VehicleLocation
-- vehicleDirection: vehicle direction

-- recentVehicleLocationNl: displacement from current vehicle location
-- see VehicleLocationDelta
-- recentVehicleLocationN2: displacement from
-- recentVehicleLocationN1 see VehicleLocationDelta
-- numberOfPassengers: minimum known number
-- of fastened safety belts
MSDStructure ::= SEQUENCE {
messageIdentifier INTEGER(0 ... 255),
control ControlType,
vehicleIdentificationNumber VIN,
vehiclePropulsionStorageType VehiclePropulsionStorageType,
timestamp INTEGER(0 ... 4294967295),
vehicleLocation VehicleLocation,
vehicleDirection INTEGER(0 ... 255),
recentVehicleLocationN1 VehicleLocationDelta OPTIONAL,
recentVehicleLocationN2 VehicleLocationDelta OPTIONAL,
numberOfPassengers INTEGER(0 ... 255) OPTIONAL,
...
}
-- ControlType includes the following elements:
-- automaticActivation: true, false
-- testCall: true, false
-- positionCanBeTrusted: true, false
-- vehicleType: see VehicleType
ControlType ::= SEQUENCE {
automaticActivation BOOLEAN,
testCall BOOLEAN,
positionCanBeTrusted BOOLEAN,
vehicleType VehicleType
}
-- Vehicle type definition
VehicleType ::= ENUMERATED{
passengerVehicleClassM1 (1),
busesAndCoachesClassM2 (2),
busesAndCoachesClassM3 (3),
lightCommercialVehiclesClassN1 (4),
heavyDutyVehiclesClassN2 (5),
heavyDutyVehiclesClassN3 (6),
motorcyclesClassL1e (7),
motorcyclesClassL2e (8),
motorcyclesClassL3e (9),
motorcyclesClassL4e (10),
motorcyclesClassL5e (11),
motorcyclesClassL6e (12),
motorcyclesClassL7e (13),
...
}
-- Vehicle Identification Number (VIN)
VIN::= SEQUENCE{
isowmi PrintableString (SIZE(3))
(FROM("A".."H"|"J".."N"|"P"|"R".."Z"|"0".."9")),
isovds PrintableString (SIZE(6))
(FROM("A".."H"|"J".."N"|"P"|"R".."Z"|"0".."9")),
isovisModelyear PrintableString (SIZE(l))
(FROM("A".."H"|"J".."N"|"P"|"R".."Z"|"0".."9")),
isovisSeqPlant PrintableString (SIZE(7))
(FROM("A".."H"|"J".."N"|"P"|"R".."Z"|"0".."9")),
}
-- VehiclePropulsionStorageType:
-- Fuel (energy source) type used for vehicle
VehiclePropulsionStorageType ::= SEQUENCE {
gasolineTankPresent BOOLEAN DEFAULT FALSE,
dieselTankPresent BOOLEAN DEFAULT FALSE,
compressedNaturalGas BOOLEAN DEFAULT FALSE,
liquidPropaneGas BOOLEAN DEFAULT FALSE,
electricEnergyStorage BOOLEAN DEFAULT FALSE,
hydrogenStorage BOOLEAN DEFAULT FALSE,
otherStorage BOOLEAN DEFAULT FALSE,
...
}
-- VehicleLocation:
-- Current vehicle location
-- Elements:
-- Latitude – 32 bits (4 octets) allocated
-- Longitude – 32 bits (4 octets) allocated
VehicleLocation ::= SEQUENCE {
positionLatitude INTEGER (-2147483648..2147483647),
positionLongitude INTEGER (-2147483648..2147483647)
}
-- VehicleLocationDelta:
-- Vehicle location before an RTA event was detected
VehicleLocationDelta ::= SEQUENCE {
latitudeDelta INTEGER (-512..511),
longitudeDelta INTEGER (-512..511)
}
-- AdditionalData:
-- Any additional data encoded as a separate definition
-- Elements:
-- oid: object identifier defining data format and purpose
-- data: additional data in the format
-- defined by oid
AdditionalData ::= SEQUENCE {
oid RELATIVE-OID,
data OCTET STRING
}
END

        在分析MSD数据结构之前,首先需要了解一些基本的ASN.1语法规则,可参考文档《ASN.1编码规则详解(最全最经典)》中2.2节,2.3节,2.4节,2.6节,2.8节,2.9节,2.10节中的2.10.2(重要!),以及其他读者认为有必要提前阅读的章节。

        其次,还需要了解编码规则。GOST 33464中规定的MSD数据是按UPER编码的,可参考文档《ASN.1编码规则详解(最全最经典)》中的3.3节。特别需要阅读的是,涉及到MSD的相关数据类型的编码说明(在3.3.6节中),如BOOLEAN型、INTEGER型、ENUMERATED型、RELATIVE-OID型、字符串与日期型、SEQUENCE型等。


举例:

SEQUENCE类型

        首先,如果有 COMPONENTS OF 语句,则由相应的类型进行替换。
        如果 SEQUENCE 类型是可扩展的,则在编码的头部加上一个比特的 bit-field,如果SEQUENCE 的取值中有属于扩展附加部分的成员,则该比特等于 1,否则等于 0。如果 SEQUENCE 的定义中在扩展根部( extension root)有"n"个成员被置为OPTIONAL 或 DEFAULT,则在编码头部再添加"n"个比特的 bit-field,该 bit-field从第一个 bit 开始,依次指示被标记为 OPTIONAL 或 DEFAULT 的成员是否出现。如果为 1,则该成员出现,否则没有出现。如果“ n”小于 64K,则这个 bit-field 应该直接添到码流中。如果"n"大于等于 64K, 按照前面提到的处理方法把“ n”个bit 的 bit-field 分段并添加到域序列中,前面的长度字段 L 就作为一个有约束的整数编码,而约束的上限和下限都等于 n。
 


        接下来就可以具体分析GOST 33465 附录C.5中对MSD数据的具体规定了。

        注意:关于OID的分析需要参考文档ISO/IEC 8825-2的第33章节。(这块还没仔细看,待补充...)

        分析完后,一种可能的MSD数据结构为(不说是一定,是因为按照ASN.1描述,部分指示位、数据位有可能不存在。此处只列举一种可能性供读者参考):

序号ByteBit所属域含义 备注
107协议版本  如为GOST 33464协议,则必须设置为:0x02
26  
35  
44  
53  
62  
71  
80  
917MSD数据内容长度  表示从第2个字节之后(即从该字节之后)的数据长度
106  
115  
124  
133  
142  
151  
160  
1727 Extension of MSDMessage0:Absent    1:Present 
186 optionalAdditionalData0:Absent    1:Present
195 Extension of MSDStructure Present?0:Absent    1:Present
204 recentVehicleLocationN10:Absent    1:Present
213 recentVehicleLocationN20:Absent    1:Present
222 numberOfPassengers0:Absent    1:Present
231Message IdentifierMessage Identifier bit7 Msg ID是否仅包含8 bits,待确认
240Message Identifier bit6 
2537Message Identifier bit5 
266Message Identifier bit4 
275Message Identifier bit3 
284Message Identifier bit2 
293Message Identifier bit1 
302Message Identifier bit0 
311ControlAutomatic Activation  
320Test Call  
3347Position Can Be Trusted  
346Vehicle TypeVehicleType Enum value from 前导(Preamble)bit,当值在根部分时,该bit为0,否则为1.
355Vehicle Type- passenger vehicle (Category M1)
- buses (Category M2)
- buses (Category M3)
- light trucks (Category N1)
- cargo vehicles (Category N2)
- cargo vehicles (Category N3)
- motor cycles (Category L1e)
- motor cycles (Category L2e)
- motor cycles (Category L3e)
- motor cycles (Category L4e)
- motor cycles (Category L5e)
- motor cycles (Category L6e)
- motor cycles (Category L7e)
- ……
枚举类型值(可扩展类型)
364
373
382
391VINVIN[0] 1)每6 bits表示1位VIN码。
2)VIN码的编码不是ASIC II码。编码值对应关系见“VIN码编码值对照表”。
400 
4157 
426 
435 
444 
453VIN[1]  
462  
471  
480  
4967  
506  
515VIN[2]  
524  
533  
542  
551  
560  
5777VIN[3]  
586  
595  
604  
613  
622  
631VIN[4]  
640  
6587  
666  
675  
684  
693VIN[5]  
702  
711  
720  
7397  
746  
755VIN[6]  
764  
773  
782  
791  
800  
81107VIN[7]  
826  
835  
844  
853  
862  
871VIN[8]  
880  
89117  
906  
915  
924  
933VIN[9]  
942  
951  
960  
97127  
986  
995VIN[10]  
1004  
1013  
1022  
1031  
1040  
105137VIN[11]  
1066  
1075  
1084  
1093  
1102  
1111VIN[12]  
1120  
113147  
1146  
1155  
1164  
1173VIN[13]  
1182  
1191  
1200  
121157  
1226  
1235VIN[14]  
1244  
1253  
1262  
1271  
1280  
129167VIN[15]  
1306  
1315  
1324  
1333  
1342  
1351VIN[16]  
1360  
137177  
1386  
1395  
1404  
1413Vehicle Propulsion Storage TypeExtension of Vehicle Propulsion Storage Type Present?0:Absent    1:Present 
1422Gasoline Tank Present?0:Absent    1:Present1)每个bit表示后面对应的指示位是否存在

2)设置为(二进制):
111 1111
1431Diesel Tank Present?0:Absent    1:Present
1440Compressed Natural Gas Present?0:Absent    1:Present
145187Liquid Propane Gas Present?0:Absent    1:Present
1466Electric Energy Storage Present?0:Absent    1:Present
1475Hydrogen Storage Present?0:Absent    1:Present
1484Other Storage Present?0:Absent    1:Present
1493Gasoline Tank0:Absent    1:Present 
1502Diesel Tank0:Absent    1:Present 
1511Compressed Natural Gas0:Absent    1:Present 
1520Liquid Propane Gas0:Absent    1:Present 
153197Electric Energy Storage0:Absent    1:Present 
1546Hydrogen Storage0:Absent    1:Present 
1555Other Storage0:Absent    1:Present 
1564time Stamptime Stamp bit31 1)time stamp值为从1970年1月1日开始,到RTA发生是的秒数。

2)如果时间超出合理范围,测试仪器会将time stamp清零显示。
1573time Stamp bit30 
1582time Stamp bit29 
1591time Stamp bit28 
1600time Stamp bit27 
161207time Stamp bit26 
1626time Stamp bit25 
1635time Stamp bit24 
1644time Stamp bit23 
1653time Stamp bit22 
1662time Stamp bit21 
1671time Stamp bit20 
1680time Stamp bit19 
169217time Stamp bit18 
1706time Stamp bit17 
1715time Stamp bit16 
1724time Stamp bit15 
1733time Stamp bit14 
1742time Stamp bit13 
1751time Stamp bit12 
1760time Stamp bit11 
177227time Stamp bit10 
1786time Stamp bit9 
1795time Stamp bit8 
1804time Stamp bit7 
1813time Stamp bit6 
1822time Stamp bit5 
1831time Stamp bit4 
1840time Stamp bit3 
185237time Stamp bit2 
1866time Stamp bit1 
1875time Stamp bit0 
1884Vehicle LocationPosition LatitudePosition Latitude bit311)Position计算时有偏移量,偏移量为:-2147483648

2)注意前面有Position Can be Trusted位

3)计算算法参考GOST 33464协议
1893Position Latitude bit30
1902Position Latitude bit29
1911Position Latitude bit28
1920Position Latitude bit27
193247Position Latitude bit26
1946Position Latitude bit25
1955Position Latitude bit24
1964Position Latitude bit23
1973Position Latitude bit22
1982Position Latitude bit21
1991Position Latitude bit20
2000Position Latitude bit19
201257Position Latitude bit18
2026Position Latitude bit17
2035Position Latitude bit16
2044Position Latitude bit15
2053Position Latitude bit14
2062Position Latitude bit13
2071Position Latitude bit12
2080Position Latitude bit11
209267Position Latitude bit10
2106Position Latitude bit9
2115Position Latitude bit8
2124Position Latitude bit7
2133Position Latitude bit6
2142Position Latitude bit5
2151Position Latitude bit4
2160Position Latitude bit3
217277Position Latitude bit2
2186Position Latitude bit1
2195Position Latitude bit0
2204Position LongitudePosition Longitude bit 311)Position计算时有偏移量,偏移量为:-2147483648

2)注意前面有Position Can be Trusted位

3)计算算法参考GOST 33464协议
2213Position Longitude bit 30
2222Position Longitude bit 29
2231Position Longitude bit 28
2240Position Longitude bit 27
225287Position Longitude bit 26
2266Position Longitude bit 25
2275Position Longitude bit 24
2284Position Longitude bit 23
2293Position Longitude bit 22
2302Position Longitude bit 21
2311Position Longitude bit 20
2320Position Longitude bit 19
233297Position Longitude bit 18
2346Position Longitude bit 17
2355Position Longitude bit 16
2364Position Longitude bit 15
2373Position Longitude bit 14
2382Position Longitude bit 13
2391Position Longitude bit 12
2400Position Longitude bit 11
241307Position Longitude bit 10
2426Position Longitude bit 9
2435Position Longitude bit 8
2444Position Longitude bit 7
2453Position Longitude bit 6
2462Position Longitude bit 5
2471Position Longitude bit 4
2480Position Longitude bit 3
249317Position Longitude bit 2
2506Position Longitude bit 1
2515Position Longitude bit 0
2524Vehicle DirectionVehicle Direction bit7 1)GOST 33464中规定分辨率为2°,但测试仪器没有进行分辨率的处理。
2533Vehicle Direction bit6 
2542Vehicle Direction bit5 
2551Vehicle Direction bit4 
2560Vehicle Direction bit3 
257327Vehicle Direction bit2 
2586Vehicle Direction bit1 
2595Vehicle Direction bit0 
2604recentVehicleLocationN1LatitudeRecent Vehicle Location N1 Lat bit91)偏移量:-512
2)注意前面有recentVehicleLocationN1标志位
2613Recent Vehicle Location N1 Lat bit8
2622Recent Vehicle Location N1 Lat bit7
2631Recent Vehicle Location N1 Lat bit6
2640Recent Vehicle Location N1 Lat bit5
265337Recent Vehicle Location N1 Lat bit4
2666Recent Vehicle Location N1 Lat bit3
2675Recent Vehicle Location N1 Lat bit2
2684Recent Vehicle Location N1 Lat bit1
2693Recent Vehicle Location N1 Lat bit0
2702LongitudeRecent Vehicle Location N1 Long bit9
2711Recent Vehicle Location N1 Long bit8
2720Recent Vehicle Location N1 Long bit7
273347Recent Vehicle Location N1 Long bit6
2746Recent Vehicle Location N1 Long bit5
2755Recent Vehicle Location N1 Long bit4
2764Recent Vehicle Location N1 Long bit3
2773Recent Vehicle Location N1 Long bit2
2782Recent Vehicle Location N1 Long bit1
2791Recent Vehicle Location N1 Long bit0
2800recentVehicleLocationN2LatitudeRecent Vehicle Location N2 Lat bit91)偏移量:-512
2)注意前面有recentVehicleLocationN2标志位
281357Recent Vehicle Location N2 Lat bit8
2826Recent Vehicle Location N2 Lat bit7
2835Recent Vehicle Location N2 Lat bit6
2844Recent Vehicle Location N2 Lat bit5
2853Recent Vehicle Location N2 Lat bit4
2862Recent Vehicle Location N2 Lat bit3
2871Recent Vehicle Location N2 Lat bit2
2880Recent Vehicle Location N2 Lat bit1
289367Recent Vehicle Location N2 Lat bit0
2906LongitudeRecent Vehicle Location N2 Long bit9
2915Recent Vehicle Location N2 Long bit8
2924Recent Vehicle Location N2 Long bit7
2933Recent Vehicle Location N2 Long bit6
2942Recent Vehicle Location N2 Long bit5
2951Recent Vehicle Location N2 Long bit4
2960Recent Vehicle Location N2 Long bit3
297377Recent Vehicle Location N2 Long bit2
2986Recent Vehicle Location N2 Long bit1
2995Recent Vehicle Location N2 Long bit0
3004Number of passengersNumber of passeners bit7 1)注意前面有numberOfPassengers标志位
3013Number of passengers bit6 
3022Number of passeners bit5 
3031Number of passeners bit4 
3040Number of passengers bit3 
305387Number of passeners bit2 
3066Number of passeners bit1 
3075Number of passengers bit0 
3084    
3093    
3102    
3111    
3120    

        更详细的分析过程待有时间补充。


        文中列举的参考文档下载链接为:

链接:https://pan.baidu.com/s/1ETGxVC0G3LTF9YS9Ub6uLA 
提取码:0q5i 


 

  • 22
    点赞
  • 18
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
Contents Contents .............................................................................................................................. 3 1 Introduction .................................................................................................................. 6 1.1 About eCall / ERA GLONASS ................................................................................................................. 7 1.2 eCall definitions .................................................................................................................................... 7 2 IVS system and eCall conformity ................................................................................. 8 2.1 eCall AT interface summary .................................................................................................................. 9 2.2 Table of timings (eCall Release 2 and 3) .............................................................................................. 10 3 eCall control through AT interface ............................................................................ 11 3.1 AT+UECALLSTAT ................................................................................................................................ 12 3.1.1 Read configuration: AT+UECALLSTAT? ....................................................................................... 12 3.1.2 Force the configuration in cache: AT+UECALLSTAT=0/1/2 ........................................................... 13 3.1.3 Restore configuration in cache: AT+UECALLSTAT=3 .................................................................... 13 3.2 AT+UECALLTYPE ................................................................................................................................ 14 3.3 AT+CECALL ........................................................................................................................................ 16 3.4 AT+UDCONF=90 ................................................................................................................................ 17 3.4.1 eCall test number: AT+UDCONF=90,1[,<ToN>,<number>] ......................................................... 17 3.4.2 eCall reconfiguration number: AT+UDCONF=90,2[,<ToN>,<number>] ....................................... 17 3.4.3 eCall T3242 duration: AT+UDCONF=90,11,<timer_duration> ..................................................... 17 3.4.4 eCall T3243 duration: AT+UDCONF=90,12,<timer_duration> ..................................................... 17 3.5 AT+UECALLDATA ............................................................................................................................... 18 3.5.1 Activation: AT+UECALLDATA=1,<push/pull mode>,<MSD data> ................................................ 18 3.5.2 In-band Modem status events: +UUECALLDATA: <urc_id> .......................................................... 18 3.5.3 MSD update: AT+UECALLDATA=2,<update mode>,<MSD data> ............................................... 19 3.5.4 Examples ..................................................................................................................................... 19 3.6 AT+UECALLVOICE .............................................................................................................................. 20 3.6.1 Internal voice control ................................................................................................................... 21 3.6.2 Configurable internal HLAP timers (eCall Release 4) ..................................................................... 23 4 eCall examples ............................................................................................................ 25 4.1 eCall session dynamic view: end-to-end In-band signaling .................................................................. 25 4.1.1 MSD transfer in push mode ......................................................................................................... 25 4.1.2 MSD update in TX idling mode .................................................................................................... 26 4.2 eCall control examples ........................................................................................................................ 27 4.2.1 Simple MSD transfer in push mode ............................................................................................. 27 4.2.2 MSD update on PULL request, with transmitter reset and microphone control ............................ 28 4.2.3 Answer to PSAP callback ............................................................................................................. 29 4.3 eCall configuration examples .............................................................................................................. 30 4.3.1 eCall initiation (eCall Release 2 vs 3) ............................................................................................ 30 4.3.2 eCall-only mode with an eCall-enabled USIM .............................................................................. 31 eCall / ERA GLONASS - Application Note UBX-13001924 - R09 Contents Page 4 of 62 4.3.3 Force the eCall-only mode with a not eCall-enabled USIM .......................................................... 32 4.3.4 Force the eCall without registration restrictions with a not eCall-enabled USIM ........................... 32 5 ERA-GLONASS additional features and use cases .................................................... 33 5.1 MSD transfer by SMS .......................................................................................................................... 33 5.1.1 MSD SMS transmission in PDU mode .......................................................................................... 33 5.2 SIM/eUICC profile switch .................................................................................................................... 35 5.2.1 Example of management of eCall transaction with temporary eUICC swap to emergency profile 35 6 eCall / ERA GLONASS In-band Modem simulation system ...................................... 37 6.1 PSAP simulator ................................................................................................................................... 37 6.1.1 Software & hardware requirements ............................................................................................. 37 6.2 IVS system .......................................................................................................................................... 38 6.2.1 Software & hardware requirements ............................................................................................. 38 6.3 m-center software .............................................................................................................................. 38 6.3.1 IVS simulator ............................................................................................................................... 39 6.3.2 PSAP simulator ............................................................................................................................ 43 6.4 eCall / ERA GLONASS system setup .................................................................................................... 45 6.4.1 PSAP simulator connecting with the PSAP GSM modem .............................................................. 45 6.4.2 Starting the PSAP simulator ......................................................................................................... 45 6.4.3 IVS simulator connecting with the IVS GSM modem .................................................................... 45 6.4.4 Starting the IVS simulator ............................................................................................................ 45 6.4.5 IVS In-band Modem setup without IVS simulator ......................................................................... 47 6.5 Running the eCall simulation .............................................................................................................. 47 6.5.1 eCall simulation example (without IVS simulator) ......................................................................... 47 6.5.2 Callback example ........................................................................................................................ 49 Appendix .......................................................................................................................... 50 A List of Acronyms ......................................................................................................... 50 B PAN European eCall IVS test list ................................................................................ 51 B.1 NAD Protocol ...................................................................................................................................... 51 B.2 In-band modem conformance ............................................................................................................ 51 B.3 High-level application protocol ........................................................................................................... 52 C ERA-GLONASS IVS test list ......................................................................................... 54 C.1 IVS functional and data transfer protocols test methods ..................................................................... 54 C.1.1 IVS tests in regard to functional requirements ............................................................................. 54 C.1.2 IVS tests in regard to requirements of data exchange protocols ................................................... 54 C.2 IVS tests for compliance with the established requirements for electromagnetic compatibility and resistance to climatic and mechanical loads ................................................................................................... 55 C.2.1 IVS tests for compliance with the established requirements for electromagnetic compatibility ..... 55 C.2.2 IVS tests for compliance with the established requirements for resistance to climatic loads .......... 55 C.2.3 IVS tests for compliance with the established requirements for resistance to mechanical loads .... 56 C.3 IVS tests for conformity to quality requirements for loudspeaker communication in vehicle cabin ....... 56 eCall / ERA GLONASS - Application Note UBX-13001924 - R09 Contents Page 5 of 62 C.4 IVS tests for conformity to accident detection requirements .............................................................. 56 C.5 IVS tests for wireless communication modules .................................................................................... 57 C.5.1 IVS tests in regard to implementation of GSM modem functions ................................................. 57 C.5.2 IVS tests in regard to implementation of UMTS modem functions ............................................... 57 C.5.3 IVS tests in regard to implementation of in-band modem functions ............................................. 58 C.6 IVS tests for navigation modules ......................................................................................................... 58 D eCall flag ..................................................................................................................... 59 Related documents .......................................................................................................... 60 Revision history ................................................................................................................ 61 Contact .............................................................................................................................. 62
在机器学习和模式识别中,f1_score, precision, recall, average precision(AP),以及区域下的面积(AUC)是常用于评估二分类模型的性能指标。 f1_score是综合评估模型精确率和召回率的指标,它的计算公式为:f1_score=2*(precision*recall)/(precision+recall)。f1_score可以用来评估模型在不同阈值下的表现,它的取值范围是0到1,数值越高表示模型表现越好。 precision(精确率)是指模型预测为正例中真正为正例的比例,计算公式为:precision=TP/(TP+FP)。precision的值越高,表示模型的误报率较低,即模型判断为正例的样本中真正为正例的概率越大。 recall(召回率)是指模型预测为正例的样本中真正为正例的比例,计算公式为:recall=TP/(TP+FN)。recall的值越高,表示模型的漏报率较低,即模型能够更好地捕捉到真正为正例的样本。 average precision(AP)是用于评估模型在不同阈值下的精度-召回率曲线(Precision-Recall Curve)下的面积大小。AP的取值范围是0到1,数值越高表示模型分类的准确度越高。 AUC(Area Under Curve)是用于评估模型在不同阈值下的真正例率(True Positive Rate)和假正例率(False Positive Rate)之间的关系。AUC的取值范围是0到1,数值越接近1表示模型的分类准确度越高。 综上所述,f1_score, precision, recall, AP和AUC是常用于评估二分类模型性能的指标,可以用来衡量模型的分类准确度、误报率和漏报率。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 3
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值