Method and system for mapping SOMEIP message header and bus message ID and vehicle

Abstract

The invention discloses a mapping method and system of an SOMEIP message header and a bus message ID and a vehicle. The mapping method of the SOMEIP message header and the bus message ID comprises the following steps: obtaining a field of an SOMEIP message corresponding to a format of a bus message; according to the field of the SOMEIP message corresponding to the format of the bus message, establishing a mapping relationship between the bus message and the SOMEIP message; and according to the mapping relationship, mapping the bus message ID to the variable field of the SOMEIP message header. By the adoption of the method and device, a mapping table of the bus message ID and the SOME / IP message header does not need to be maintained any more, the version change of the mapping table does not need to be paid attention to, rapid analysis of the bus message ID and the SOME / IP message header can be completed, the corresponding bus message ID and the corresponding SOME / IP message can be found rapidly even though visual inspection is conducted, the version maintenance workload can be reduced, and the analysis efficiency of the message or the message is improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicles, and in particular, to a mapping method, system and vehicle for SOMEIP message headers and bus message IDs. Background Art

[0002] With the continuous progress of automotive technology, vehicles are no longer simply used as a means of transportation. Especially with the development of intelligence and comfort, functions such as audio-visual entertainment, cameras, and radars are installed in vehicles. The CAN / LIN bus can no longer meet this type of high-load communication. Therefore, in-vehicle Ethernet is used. However, in order to minimize the controller development cost and material cost as much as possible for the whole vehicle, some domain controllers include both CAN / LIN protocols and SOME / IP protocols (Ethernet protocols), and are routed to each channel through ID mapping by the underlying software or application software of the domain controller.

[0003] Currently, the mapping relationships between SOME / IP message headers and CAN / LIN IDs are all placed in a single table, and there is only a mapping relationship between them. It is impossible to identify the CAN / LIN ID from the SOME / IP message header or the message header from the CAN / LIN ID. As a result, developers or testers usually can only view the mapping table to parse the corresponding CAN / LIN message or SOME / IP message, and the parsing efficiency is low. Summary of the Invention

[0004] Based on this, in order to solve the above technical problems, it is necessary to provide a mapping method, system and vehicle for SOMEIP message headers and bus message IDs. The bus message ID (such as CAN / LIN message ID) directly has a mapping relationship with the SOMEIP message header, and can be directly parsed through the code generation database of the conversion relationship. At the same time, when some designers and testers do not have the database, they can also directly find the corresponding data through the message ID or SOME / IP message header, rather than searching through the mapping table. That is, it is no longer necessary to maintain the mapping table between the bus message ID and the SOME / IP message header, nor to pay attention to the changes in the mapping table version, and the rapid parsing of the bus message ID and the SOME / IP message header can be completed. Even by visual inspection, the corresponding bus message ID and SOME / IP message can be quickly found, which helps to reduce the workload of version maintenance and improve the parsing efficiency of messages or messages.

[0005] In a first aspect, a mapping method for SOMEIP message headers and bus message IDs is provided, including:

[0006] Obtain the fields of the SOMEIP message corresponding to the format of the bus message;

[0007] Establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0008] According to the mapping relationship, map the bus message ID to the variable field of the SOMEIP message header.

[0009] In some examples, the establishing the mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message includes:

[0010] If the bus message is a standard frame, establish the mapping relationship between the bus message and the SOMEIP message according to a predefined standard frame mapping template;

[0011] If the bus message is an extended frame, establish the mapping relationship between the bus message and the SOMEIP message according to a predefined extended frame mapping template.

[0012] In some examples, the standard frame includes a CAN standard frame and a LIN data frame.

[0013] In some examples, the fields of the SOMEIP message corresponding to the format of the bus message include: ServiceID, Event, Frame Type, Length, ClientID, SessionID, Protocol, Interface Version, MessageType, Return Code, and Payload, where the Frame Type is used to indicate the frame type of the bus message, and the frame type includes a CAN standard frame, a LIN data frame, and the extended frame.

[0014] In some examples, if it is a standard frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Reserved and the bus message ID.

[0015] In some examples, if it is an extended frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Priority, EDP, DP, and SourceID.

[0016] In a second aspect, a mapping system between the SOMEIP message header and the bus message ID is provided, including:

[0017] An acquisition module, configured to obtain the fields of the SOMEIP message corresponding to the format of the bus message;

[0018] A creation module, configured to establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0019] A mapping module, configured to map the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship.

[0020] In a third aspect, a vehicle is provided, including: a mapping system for the SOMEIP message header and the bus message ID according to the second aspect described above.

[0021] In a fourth aspect, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the mapping method for the SOMEIP message header and the bus message ID in the first aspect and any possible implementation manner of the first aspect are implemented.

[0022] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the steps of the mapping method for the SOMEIP message header and the bus message ID in the first aspect and any possible implementation manner of the first aspect are implemented.

[0023] In a sixth aspect, a computer program product is provided, on which a computer program is stored. When the program is executed by a processor, the steps of the mapping method for the SOMEIP message header and the bus message ID in the first aspect and any possible implementation manner of the first aspect are implemented.

[0024] By adopting the embodiments of the present application, the fields of the SOMEIP message corresponding to the format of the bus message are obtained, a mapping relationship between the bus message and the SOMEIP message is established according to the fields of the SOMEIP message corresponding to the format of the bus message, and the bus message ID is mapped to the variable field of the SOMEIP message header according to the mapping relationship. The bus message ID (such as CAN / LIN message ID) has a direct mapping relationship with the SOMEIP message header, and can be directly parsed through the code generation database of the conversion relationship. At the same time, when some designers and testers do not have a database, the corresponding data can also be directly found through the message ID or SOME / IP message header, instead of searching through the mapping table, that is: there is no need to maintain the mapping table of the bus message ID and the SOME / IP message header, nor to pay attention to the changes in the mapping table version, and the rapid parsing of the bus message ID and the SOME / IP message header can be completed. Even by visual inspection, the corresponding bus message ID and SOME / IP message can be quickly found, which helps to reduce the workload of version maintenance and improve the parsing efficiency of the message or message. Description of the Drawings

[0025] Other features, objects, and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments read in conjunction with the accompanying drawings:

[0026] Figure 1 It is a flowchart of a mapping method between a SOMEIP message header and a bus message ID provided by an embodiment of the present application;

[0027] Figure 2 It is a schematic diagram of the mapping relationship of a standard frame in the mapping method between a SOMEIP message header and a bus message ID provided by an embodiment of the present application;

[0028] Figure 3 It is a schematic diagram of the mapping relationship of an extended frame in the mapping method between a SOMEIP message header and a bus message ID provided by an embodiment of the present application;

[0029] Figure 4 It is a structural block diagram of a mapping system between a SOMEIP message header and a bus message ID provided by an embodiment of the present application;

[0030] Figure 5 It is a structural block diagram of a computer device provided by an embodiment of the present application. Detailed Embodiments

[0031] The present application will be further described in detail below in conjunction with embodiments and the accompanying drawings. It can be understood that the specific embodiments described herein are only used to explain the related application and do not limit the application. Additionally, it should be noted that for ease of description, only parts related to the application are shown in the drawings.

[0032] It should be noted that, without conflict, the embodiments and features of the embodiments in the present application can be combined with each other. The present application will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0033] The mapping method, system, and vehicle between a SOMEIP message header and a bus message ID according to an embodiment of the present application are described in detail below with reference to the accompanying drawings.

[0034] Figure 1 It is a flowchart of a mapping method between a SOMEIP message header and a bus message ID according to an embodiment of the present application. As Figure 1 shown, the mapping method between a SOMEIP message header and a bus message ID according to an embodiment of the present application includes the following steps:

[0035] S101: Obtain the fields of the SOMEIP message corresponding to the format of the bus message.

[0036] S102: Establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message.

[0037] In an embodiment of the present application, the step of establishing a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message includes: if the bus message is a standard frame, establish a mapping relationship between the bus message and the SOMEIP message according to a predefined standard frame mapping template; if the bus message is an extended frame, establish a mapping relationship between the bus message and the SOMEIP message according to a predefined extended frame mapping template.

[0038] Among them, the standard frame includes a CAN standard frame and a LIN data frame.

[0039] In an embodiment of the present application, the fields of the SOMEIP message corresponding to the format of the bus message include: ServiceID, Event, Frame Type, Length, ClientID, Session ID, Protocol, InterfaceVersion, Message Type, Return Code, and Payload. Among them, the Frame Type is used to indicate the frame type of the bus message, and the frame type includes a CAN standard frame, a LIN data frame, and the extended frame.

[0040] As a specific example, if it is a standard frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Reserved and the bus message ID.

[0041] In another specific example, if it is an extended frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Priority, EDP, DP, and Source ID.

[0042] S103: Map the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship.

[0043] Specifically, there are standard frames (including CAN standard frames and LIN data frames) and extended frames in the CAN / LIN bus, such as Figure 2 the mapping relationship of the standard frame shown, such as Figure 3 the mapping relationship of the extended frame shown. In the embodiment of the present application, SOME / IP field messages are fully utilized to map CAN / LIN messages to SOME / IP messages, and the mapping relationship is as shown in Figure 2 and Figure 3As shown, it should be noted that: PGNx is not equivalent to the lower 2 bytes of the PGN in the J1939 message. In this article, PGNx does not distinguish between PDU1 and PDU2, and directly converts the 2 bytes occupied by the PGN in the message ID. For example, for the message 0x0CE00400x, this position is filled with 0xE004; for 0x0CF00400x, this position is filled with 0xF004.

[0044] The SOME / IP Data fields corresponding to the CAN / LIN message format are as follows:

[0045] 1. Service ID: The length is 2 bytes, and all CAN / LIN messages are filled with the fixed data 0x0000;

[0046] 2. Event: The length is 1 bit, which is the Method / Event flag bit. All CAN / LIN messages sent periodically use Event and are filled with the fixed data 0x1;

[0047] 3. Frame Type: The frame type flag bit, with a length of 2 bits, indicating the frame type of this CAN(FD) / LIN data:

[0048] 0x0: Standard CAN;

[0049] 0x1: Extended CAN;

[0050] 0x3: LIN;

[0051] 4. The following fields only appear in the standard frame:

[0052] 4.1. Reserved: The length is 1 bit. The reserved field only appears in the standard frame and is filled with 0x0;

[0053] 4.2. CAN / LIN ID: The CAN / LIN message ID, with a length of 11 bits;

[0054] 5. The following fields only appear in the CAN extended frame:

[0055] 5.1. Priority: The priority, with a length of 3 bits, mapping the priority in the J1939 message ID;

[0056] 5.2. EDP: Extended Data Page, with a length of 1 bit, mapping the EDP in the J1939 message ID. This field is filled with the fixed data 0x0;

[0057] 5.3, DP: Data Page, with a length of 1 bit, mapping the DP in the J1939 message ID. For example, for ID 18FF0627x, this position is filled with 0x0; for 0x19FF0627, this position is filled with 0x1).

[0058] 5.4, Source ID: Source address, with a length of 1 byte, mapping the source address in the J1939 message ID;

[0059] 6. Length: The length is 4 bytes, indicating the number of data bytes after the Length field;

[0060] 7. ClientID: Client ID, with a length of 2 bytes:

[0061] Standard frame: Filled with fixed data 0xFFFF;

[0062] Extended frame: The lower two bytes of the PGN in the J1939 message ID are converted;

[0063] 8. Session ID: Session ID, with a length of 2 bytes. The initial value of the Session ID is 0x0001; when the Session ID increases to 0xFFFF, the Session ID starts counting from 0x0001 again (segment differentiation);

[0064] 9. Protocol: Protocol version, with a length of 1 byte, filled with fixed data 0x01;

[0065] 10. Interface Version: Interface version, with a length of 1 byte, indicating the big data routing table version. Currently, it is V1.0 and is filled with 0x10;

[0066] 11. Message Type: SOME / IP message type, with a length of 1 byte. This specification stipulates it as 0x2;

[0067] 12. Return Code: SOME / IP return code, indicating whether the request has been successfully processed, with a length of 1 byte. This specification stipulates it as 0x00;

[0068] 13. Payload: Payload of SOME / IP Data, the data in the CAN(FD) message, should be filled in this position.

[0069] According to the mapping method of SOMEIP message header and bus message ID according to the embodiments of the present application, obtain the fields of the SOMEIP message corresponding to the format of the bus message. According to the fields of the SOMEIP message corresponding to the format of the bus message, establish the mapping relationship between the bus message and the SOMEIP message. According to the mapping relationship, map the bus message ID to the variable field of the SOMEIP message header. The bus message ID (such as CAN / LIN message ID) has a direct mapping relationship with the SOMEIP message header and can be directly parsed through the code generation database of the conversion relationship. At the same time, in the case where some designers and testers do not have the database, the corresponding data can also be directly found through the message ID or SOME / IP message header, rather than searching through the mapping table, that is: there is no need to maintain the mapping table of the bus message ID and SOME / IP message header, nor to pay attention to the changes in the mapping table version, and the rapid parsing of the bus message ID and SOME / IP message header can be completed. Even by visual inspection, the corresponding bus message ID and SOME / IP message can be quickly found, which helps to reduce the workload of version maintenance and improve the parsing efficiency of the message or message.

[0070] Figure 4 It is a structural block diagram of a mapping system for SOMEIP message header and bus message ID according to an embodiment of the present application. As Figure 4 shown, the mapping system for SOMEIP message header and bus message ID according to the embodiments of the present application includes: an acquisition module 410, a creation module 420, and a mapping module 430, where:

[0071] The acquisition module 410 is used to obtain the fields of the SOMEIP message corresponding to the format of the bus message;

[0072] The creation module 420 is used to establish the mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0073] The mapping module 430 is used to map the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship.

[0074] The mapping system of SOMEIP message header and bus message ID according to the embodiments of the present application obtains the fields of the SOMEIP message corresponding to the format of the bus message, establishes the mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message, and maps the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship. The bus message ID (such as CAN / LIN message ID) has a direct mapping relationship with the SOMEIP message header, and can be directly parsed through the code generation database of the conversion relationship. At the same time, in the case where some designers and testers do not have the database, the corresponding data can also be directly found through the message ID or SOME / IP message header, instead of searching through the mapping table, that is: there is no need to maintain the mapping table of the bus message ID and the SOME / IP message header, nor to pay attention to the version change of the mapping table, and the rapid parsing of the bus message ID and the SOME / IP message header can be completed. Even by visual inspection, the corresponding bus message ID and SOME / IP message can be quickly found, which helps to reduce the workload of version maintenance and improve the parsing efficiency of the message or message.

[0075] For the specific limitations of the mapping system of the SOMEIP message header and the bus message ID, reference can be made to the limitations of the mapping method of the SOMEIP message header and the bus message ID in the above text, which will not be elaborated here. Each module of the above mapping system of the SOMEIP message header and the bus message ID can be implemented in whole or in part by software, hardware and their combination. The above-mentioned each module can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0076] In one embodiment, a vehicle is provided, including: a mapping system of SOMEIP message headers and bus message IDs according to any of the foregoing embodiments. The vehicle obtains the fields of the SOMEIP message corresponding to the format of the bus message, and establishes a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message. According to the mapping relationship, the bus message ID is mapped to the variable field of the SOMEIP message header. The bus message ID (such as CAN / LIN message ID) has a direct mapping relationship with the SOMEIP message header, and can be directly parsed through the code generation database of the conversion relationship. At the same time, in the case where some designers and testers do not have the database, the corresponding data can also be directly found through the message ID or SOME / IP message header, without searching through the mapping table, that is: there is no need to maintain the mapping table of the bus message ID and the SOME / IP message header, nor to pay attention to the changes in the mapping table version, and the rapid parsing of the bus message ID and the SOME / IP message header can be completed. Even by visual inspection, the corresponding bus message ID and SOME / IP message can be quickly found, which helps to reduce the workload of version maintenance and improve the parsing efficiency of the message or message.

[0077] In addition, the other components and functions of the vehicle according to the embodiments of the present application are known to those of ordinary skill in the art, and will not be described in detail here.

[0078] In one embodiment, a computer device is provided. Figure 5 It is a structural block diagram of the computer device provided in the embodiments of the present application. Refer to Figure 5 This computer device includes a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, it implements the embodiments of the foregoing SOMEIP message header and bus message ID mapping method. For example, it executes: obtaining the fields of the SOMEIP message corresponding to the format of the bus message;

[0079] Establishing a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0080] According to the mapping relationship, mapping the bus message ID to the variable field of the SOMEIP message header.

[0081] In the embodiments of the present application, a computer-readable storage medium is also provided. The computer-readable storage medium stores a computer program. When the processor executes the computer program, it implements the embodiments of the foregoing SOMEIP message header and bus message ID mapping method. For example, it executes: obtaining the fields of the SOMEIP message corresponding to the format of the bus message;

[0082] Establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0083] Map the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship.

[0084] An embodiment of the present application provides a computer program product, which includes instructions that, when run, cause the method described in the embodiment of the present application to be executed. For example, the following can be executed Figure 1 each step of the mapping method of the SOMEIP message header and the bus message ID shown, for example, execute: obtain the fields of the SOMEIP message corresponding to the format of the bus message;

[0085] Establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message;

[0086] Map the bus message ID to the variable field of the SOMEIP message header according to the mapping relationship.

[0087] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0088] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0089] The above embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation to the scope of the patent application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A mapping method for SOMEIP message headers and bus message IDs, characterized in that, including: obtaining fields of a SOMEIP message corresponding to the format of a bus message; establishing a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message; mapping the bus message ID to a variable field of the SOMEIP message header according to the mapping relationship.

2. The mapping method of SOMEIP message header and bus message ID according to claim 1, characterized in that, The establishing the mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message includes: if the bus message is a standard frame, establishing the mapping relationship between the bus message and the SOMEIP message according to a predefined standard frame mapping template; if the bus message is an extended frame, establishing the mapping relationship between the bus message and the SOMEIP message according to a predefined extended frame mapping template.

3. The mapping method of SOMEIP message header and bus message ID according to claim 2, characterized in that, The standard frame includes a CAN standard frame and a LIN data frame.

4. The mapping method of SOMEIP message header and bus message ID according to any one of claims 1-3, characterized in that The fields of the SOMEIP message corresponding to the format of the bus message include: ServiceID, Event, Frame Type, Length, ClientID, SessionID, Protocol, Interface Version, Message Type, Return Code, and Payload, where the Frame Type is used to indicate the frame type of the bus message, and the frame type includes a CAN standard frame, a LIN data frame, and an extended frame.

5. The mapping method of SOMEIP message header and bus message ID according to claim 4, wherein If it is a standard frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Reserved and the bus message ID.

6. The mapping method of SOMEIP message header and bus message ID according to claim 4, wherein If it is an extended frame, the fields of the SOMEIP message corresponding to the format of the bus message further include: Priority, EDP, DP, and SourceID.

7. A mapping system for SOMEIP message headers and bus message IDs, characterized in that, including: an obtaining module, configured to obtain fields of a SOMEIP message corresponding to the format of a bus message; a creating module, configured to establish a mapping relationship between the bus message and the SOMEIP message according to the fields of the SOMEIP message corresponding to the format of the bus message; a mapping module, configured to map the bus message ID to a variable field of the SOMEIP message header according to the mapping relationship.

8. A vehicle, characterized in that, including: the mapping system of the SOMEIP message header and the bus message ID according to claim 7.

9. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, implementing the mapping method of the SOMEIP message header and the bus message ID according to any one of claims 1-6.

10. A computer-readable storage medium, comprising a memory and a computer program stored on the memory and executable on a processor, characterized in that, When the program is executed by the processor, implementing the mapping method of the SOMEIP message header and the bus message ID according to any one of claims 1-6.

Images