Data structure of MSD Version3 and data storage adaptation method

Abstract

The invention discloses an MSD Version3 data storage adaptation method, which comprises the following steps of: establishing a state machine on a service layer, and performing corresponding dialing, connection, connection, hanging up and / or callback processing aiming at different call states; an MSD data structure is reconstructed on a protocol layer, enumeration upgrading and attribute upgrading are carried out on multiple data fields, new expression creation is completed, and an MSD Version3 data structure is obtained; after the data are coded until the packing is completed, the data are sent to a PSAP end along with a voice communication channel; and after data transmission is completed, the comprehensive test instrument performs code decoding through a protocol EN 15722 to determine the data condition of the vehicle when the telephone is called out during emergency rescue of the vehicle. The invention belongs to the technical field of communication, and particularly provides an MSD Version3 data structure and a data storage adaptation method, which are used for meeting the European standard requirements of domestic vehicle exits.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and specifically relates to a data structure of MSDVersion3 and a data storage adaptation method. Background Art

[0002] In the prior art, in order to enable rescuers to obtain accident information in a timely manner, an on-board emergency call (eCall) system can be integrated into the car. In this way, when the car sends a traffic accident, the on-board eCall device can notify the rescuers of the minimum set of data (MSD) used to reflect the accident information. Specifically, when a car has a traffic accident, the on-board eCall device can automatically initiate an emergency call to establish a voice communication link from the car to the emergency rescue center through a wireless network and a public switched telephone network / general switched telephone network (PSTN / GSTN).

[0003] The current protocols for docking with European standard vehicles are all MSDVersion2. The existing V2 structure cannot meet the European standard requirements for future domestic vehicle exports. Summary of the invention

[0004] In view of the above situation, in order to overcome the defects of the prior art, the present invention provides a data structure of MSDVersion3 and a data storage adaptation method for meeting the European standard requirements for the export of domestically produced vehicles.

[0005] The technical solutions adopted in this application are as follows:

[0006] This solution provides a data structure of MSDVersion3, including:

[0007] MSD data may include the current time and the current location of the vehicle and / or user (e.g., global positioning system (GPS) coordinates of the vehicle and / or user). In addition, the MSD may also include vehicle system information, such as airbag deployment, braking information, speed information, and / or collision sensor information collected at the vehicle when an accident occurs.

[0008] As a further elaboration of the scheme, this scheme provides an MSDVersion3 data storage adaptation method, which is applied to the public safety answering center PSAP end, and the method includes:

[0009] S1: First, build a state machine at the business layer to perform corresponding dialing, connecting, answering, hanging up and / or callback processing for different call states, and handle the hang-up generated after the connecting and answering state machines in callback mode;

[0010] S2: Secondly, at the MSD protocol layer, the MSD data structure needs to be reconstructed, multiple data fields need to be enumerated and upgraded, and new expressions need to be created. This expression is the data structure expression of the new MSD Version3.

[0011] S3: After the MSD Version 3 data is encoded into a packet, it is sent to the PSAP along with the voice call channel;

[0012] S4: After the MSD Version3 data is sent, the comprehensive tester is used to simulate the connection and receive the MSD data. The comprehensive tester will decode the MSD Version3 through the protocol EN 15722 and display the data to determine the data status of the vehicle when the call is made during emergency rescue, so as to achieve the rescue purpose.

[0013] Furthermore, in S1, the overseas callback solution is 60 minutes, during which the PSAP is allowed to call back the local module device and the call can be automatically answered.

[0014] Furthermore, in S2, the data structure expression of MSD Version 3 is encoded in ASN.1 encoding format to generate ASN.1 encoding code and corresponding structure code oriented to MSD Version 3 structure, which are reserved for backup.

[0015] Furthermore, the reconstructing of the MSD data structure in S2 specifically includes:

[0016] Rewrite the ASN file, upgrade the structure in the expression from V2 to V3, and make modifications according to the protocol EN 15722. Specifically, modify the "vehicle direction threshold", change the data type of the N1\N2 longitude and latitude change value to non-pointer, modify the number of members on the vehicle, modify the vehicle type name and add 14-23 enumeration declarations.

[0017] Furthermore, the process of encoding the MSD Version 3 data in S3 into a package includes:

[0018] The state machine in the business layer is in the "dial" state, which is accompanied by the sending of MSD. According to the requirements of the European standard protocol EN15722, the MSD data should be the latest data when "dialing", so the data collection of the current time will be carried out when "dialing", and the current vehicle positioning data, timestamp, DELTA V and other related data will be collected and filled into the ASN.1 structure code for ASN.1PER encoding, in which the encoding order is encoded layer by layer from the internal structure to the external structure;

[0019] When the encoding reaches the outermost layer, the encoding is considered complete, and the MSD Version 3 package is also considered complete. At this time, it is sent to the PSAP end along with the voice call channel.

[0020] Furthermore, the specific encoding and decoding methods include:

[0021] Coding: ASN.1PER encoding is adopted, and the ASN1C tool is used to implement the underlying code. This code can form the underlying library file according to different compilation chain compilation environments for use by different software platforms. The data structure corresponding to the transmitted MSD data is included in the declaration file, and the input configuration is transmitted one by one. The encoding and decoding logic is included in the underlying code. The client is responsible for the encoding and transmission of MSD data.

[0022] Decoding: Decoding is implemented on the PSAP side. Encode and decode are symmetric encryption. The data transmitted by encode is decoded by the PSAP side.

[0023] The beneficial effects achieved by the present invention using the above scheme are as follows:

[0024] By enumerating and upgrading multiple data fields and upgrading their attributes, the MSD data structure is reconstructed to meet the European standards for the export of domestically produced vehicles. At the same time, the data can be used to realize the functions of vehicle emergency calls and emergency rescue. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A comparison diagram of the MSD Version 2 data structure and the MSD Version 3 data structure provided in this embodiment;

[0026] The meanings of the attached drawings are as follows:

[0027] (a) is the MSDVersion2 data structure, referred to as V2 data;

[0028] (b) is the MSDVersion3 data structure, referred to as V3 data for short. DETAILED DESCRIPTION

[0029] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0030] Example 1

[0031] This embodiment provides a data storage adaptation method of MSDVersion3, including application to a public safety answering center PSAP, the method comprising:

[0032] S1: First, build a state machine at the business layer to perform corresponding dialing, connecting, answering, hanging up and / or callback processing for different call states, and handle the hang-up generated after the connecting and answering state machines in callback mode;

[0033] Among them, the overseas callback plan is 60 minutes, during which PSAP is allowed to call back the local module device and the call can be automatically answered.

[0034] S2: Secondly, at the MSD protocol layer, the MSD data structure needs to be reconstructed, multiple data fields need to be enumerated and upgraded, and new expressions need to be created. This expression is the data structure expression of the new MSDVersion3.

[0035] The data structure expression of MSDVersion3 is encoded in ASN.1 encoding format to generate ASN.1 encoding code and corresponding structure code oriented to MSDVersion3 structure for backup.

[0036] The reconstruction of the MSD data structure specifically includes: rewriting the ASN file, upgrading the structure in the expression from V2 to V3 (such as Figure 1 As shown), the modification is made according to the protocol EN 15722, specifically, the "vehicle direction threshold" is modified, the data type of the N1\N2 longitude and latitude change value is changed to non-pointer, the number of members on the vehicle is named, the vehicle type is named, and the 14-23 enumeration declarations are supplemented.

[0037] S3: After the MSD Version 3 data is encoded into a packet, it is sent to the PSAP along with the voice call channel;

[0038] The process of encoding MSD Version3 data into a package includes:

[0039] The state machine in the business layer is in the "dial" state, which is accompanied by the sending of MSD. According to the requirements of the European standard protocol EN15722, the MSD data should be the latest data when "dialing", so the data collection of the current time will be carried out when "dialing", and the current vehicle positioning data, timestamp, DELTA V and other related data will be collected and filled into the ASN.1 structure code for ASN.1PER encoding, in which the encoding order is encoded layer by layer from the internal structure to the external structure;

[0040] When the encoding reaches the outermost layer, the encoding is considered complete, and the MSD Version 3 package is also considered complete. At this time, it is sent to the PSAP end along with the voice call channel.

[0041] S4: After the MSD Version3 data is sent, the comprehensive tester is used to simulate the connection and receive the MSD data. The comprehensive tester will decode the MSD Version3 through the protocol EN 15722 and display the data to determine the data status of the vehicle when the call is made during emergency rescue, so as to achieve the rescue purpose.

[0042] Furthermore, the specific encoding and decoding methods include:

[0043] Coding: ASN.1PER encoding is adopted, and the ASN1C tool is used to implement the underlying code. This code can form the underlying library file according to different compilation chain compilation environments for use by different software platforms. The data structure corresponding to the transmitted MSD data is included in the declaration file, and the input configuration is transmitted one by one. The encoding and decoding logic is included in the underlying code. The client is responsible for the encoding and transmission of MSD data.

[0044] Decoding: Decoding is implemented on the PSAP side. Encode and decode are symmetric encryption. The data transmitted by encode is decoded by the PSAP side.

[0045] Example 2

[0046] This embodiment discloses an MSD Version 3 data structure, which is constructed by the MSD Version 3 data storage adaptation method described in Embodiment 1.

[0047] Among them, the MSD Version3 data includes the current vehicle positioning data, timestamp, and DELTAV related data; the data structure expression of MSD Version3 is encoded through the ASN.1 encoding format to generate an ASN.1 encoding code guided by the MSD Version3 structure and a corresponding structure code.

[0048] refer to Figure 1 As shown, the structure in the expression is upgraded from the original V2 to the latest V3.

[0049] It should be noted that although the embodiments of the present invention have been shown and described, for ordinary technicians in this field, without departing from the purpose of the invention, structural methods and embodiments similar to the technical solution are designed without creativity and should all fall within the scope of protection of the present invention.

Claims

1. MSD Version3 data storage adaptation method, applied to the public safety answering center PSAP end, characterized in that: The method comprises: S1: First, build a state machine at the business layer to perform corresponding dialing, connecting, answering, hanging up and / or callback processing for different call states, and handle the hang-up generated after the connecting and answering state machines in callback mode; S2: Secondly, at the MSD protocol layer, the MSD data structure needs to be reconstructed, multiple data fields need to be enumerated and upgraded, and new expressions need to be created. This expression is the data structure expression of the new MSD Version3. S3: After the MSD Version 3 data is encoded into a packet, it is sent to the PSAP along with the voice call channel; S4: After the MSD Version3 data is sent, the comprehensive tester is used to simulate the connection and receive the MSD data. The comprehensive tester will decode the MSD Version3 through the protocol EN 15722 and display the data to determine the data status of the vehicle when the call is made during emergency rescue, so as to achieve the rescue purpose.

2. The MSD Version 3 data storage adaptation method according to claim 1, characterized in that: In S2, the data structure expression of MSD Version 3 is encoded in ASN.1 encoding format to generate ASN.1 encoding code and corresponding structure code oriented to MSD Version 3 structure, which are reserved for future use.

3. The MSD Version 3 data storage adaptation method according to claim 2, characterized in that: The reconstruction of the MSD data structure in S2 specifically includes: Rewrite the ASN file, upgrade the structure in the expression from MSD Version2 data to MSD Version3 data, and modify it according to the protocol EN 15722. Specifically, modify the "vehicle direction threshold", change the data type of the N1\N2 longitude and latitude change value to non-pointer, modify the number of members on the vehicle, modify the vehicle type name and add 14-23 enumeration declarations.

4. The MSD Version 3 data storage adaptation method according to claim 3, characterized in that: The process of encoding the MSDVersion3 data in S3 into a package includes: The state machine in the business layer is in the "dial" state, which is accompanied by the sending of MSD. According to the requirements of the European standard protocol EN 15722, the MSD data should be the latest data at the time of "dial", so the data collection at the current time will be performed when "dial", and the current vehicle positioning data, timestamp, DELTA V and other related data will be collected and filled into the ASN.1 structure code for ASN.1PER encoding, in which the encoding order is encoded layer by layer from the internal structure to the external structure; When the encoding reaches the outermost layer, the encoding is considered complete, and the MSD Version 3 package is also considered complete. At this time, it is sent to the PSAP end along with the voice call channel.

5. The MSD Version 3 data storage adaptation method according to claim 4, characterized in that: The specific encoding and decoding methods include: Coding: ASN.1PER encoding is adopted, and the ASN1C tool is used to implement the underlying code. This code can form the underlying library file according to different compilation chain compilation environments for use by different software platforms. The data structure corresponding to the transmitted MSD data is included in the declaration file, and the input configuration is transmitted one by one. The encoding and decoding logic is included in the underlying code. The client is responsible for the encoding and transmission of the MSD data. Decoding: Decoding is implemented on the PSAP side. Encode and decode are symmetric encryption. The data transmitted by encode is decoded by the PSAP side.

6. The MSD Version 3 data storage adaptation method according to claim 1, characterized in that: In S1, the overseas callback solution is 60 minutes, during which the PSAP is allowed to call back the local module device and the call can be automatically answered.

7. The data structure of MSD Version 3 is characterized by: The data structure is constructed by the MSD Version 3 data storage adaptation method described in any one of claims 1 to 6; MSD Version3 data includes current vehicle location data, timestamp, and DELTAV related data; The data structure expression of MSD Version3 is encoded through the ASN.1 encoding format to generate ASN.1 encoding code and corresponding structure code oriented to the MSDVersion3 structure.

Images