Message conversion method and device and message receiving method and device

Abstract

The invention discloses a message conversion method and device and a message receiving method and device. The method comprises the following steps: acquiring a first original message of a first vehicle; a first message is generated according to the first original message and sent, the first message is related to the features of the first vehicle and contained in a first conversion message, the first conversion message comprises a first effective signal and a first invalid signal, the first effective signal corresponds to the features of the first vehicle, and the first invalid signal corresponds to the features of the first vehicle; the first invalid signals are signals corresponding to other vehicles except the first vehicle with different features from the features of the first vehicle, and at least one first signal in the first valid signals belongs to the first message. By implementing the application, the message supporting the characteristics of different vehicles can be provided, and the realization of cross-vehicle multiplexing is facilitated.

Description

A message conversion and receiving method and device Technical Field

[0001] The present application relates to the field of vehicle-mounted communications, and in particular to a message conversion and receiving method and device. Background Art

[0002] As vehicles evolve from signal-oriented architecture to service-oriented architecture (SOA), hybrid networking using both Ethernet and in-vehicle wired signal buses is common. Key vehicle functions are provided as services via Ethernet to local or cross-domain applications. Given the current SOA architecture's limitations in functional safety, performance, and hardware cost, signal-based communication via the in-vehicle wired signal bus is also employed.

[0003] However, in the current hybrid networking scenario, although the conversion of Ethernet messages to wired messages can be achieved, the message conversion method makes it difficult to achieve cross-vehicle reuse.

[0004] Summary of the Invention

[0005] The present application discloses a message conversion and receiving method and device, which can provide a message with a fixed format and supporting features of different vehicles, which is conducive to cross-vehicle reuse.

[0006] In a first aspect, the present application provides a message conversion method, which is applied to a conversion device, and the method includes: obtaining a first original message of a first vehicle; generating a first message based on the first original message, wherein the first message is related to the characteristics of the first vehicle, and the first message is included in a first conversion message; sending the first message; wherein the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal, the first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles other than the first vehicle, and the characteristics of other vehicles other than the first vehicle are different from the characteristics of the first vehicle, and at least one first signal in the first valid signals is associated with the first message.

[0007] The conversion device can be deployed on the vehicle integrated unit or domain controller of the first vehicle, for example. The conversion device can be a component in the vehicle integrated unit or a component in the domain controller. The component can be, for example, at least one of a chip, an integrated circuit, etc.

[0008] For example, the characteristic of the first vehicle may include at least one of the following: the model of the first vehicle, configuration information of the first vehicle, manufacturer of the first vehicle, and component information within the first vehicle. Here, the configuration information of the first vehicle may include software configuration and / or hardware configuration. For example, the hardware configuration of the first vehicle may be classified into three types: basic configuration, intermediate configuration, and advanced configuration. The component information within the first vehicle may include information related to a device that receives the first converted message.

[0009] The multiple signals in the first conversion message are a maximum set of signals corresponding to characteristics of multiple vehicles. For example, the multiple signals in the first conversion message may be pre-obtained by the conversion device from at least one original equipment manufacturer (OEM). Furthermore, the conversion device may also obtain from the OEM a correspondence between the characteristics of the first vehicle and the at least one first signal.

[0010] For example, the first valid signal can be understood as a signal that can be used by the first vehicle or a signal that the first vehicle needs to use, and the first invalid signal can be understood as a signal that cannot be used by the first vehicle or a signal that the first vehicle does not use, but the first invalid signal can be used by other vehicles except the first vehicle.

[0011] Here, at least one first signal in the first valid signal is associated with the first message, which means that at least one first signal in the first valid signal belongs to the first message, that is, the at least one first signal is included in the first message.

[0012] In the above method, the original message of the first vehicle is converted into a first message based on the characteristics of the first vehicle. The first message is included in a first conversion message. The first conversion message includes not only a first valid signal corresponding to the characteristics of the first vehicle, but also a first invalid signal corresponding to the characteristics of other vehicles except the first vehicle. In addition, part or all of the first valid signal belongs to the first message, which is conducive to the full quantization and platformization of the first conversion message. The output format of the first conversion message containing valid signals and invalid signals can support the reuse of vehicles with different characteristics.

[0013] Optionally, sending the first message includes: the first message is the first conversion message, and the first message is sent to the first control device of the first vehicle; or, the first message is sent to the target device of the first vehicle, and a communication protocol stack is deployed on the target device.

[0014] Here, when the first message is the first conversion message, it means that each signal in the first valid signal belongs to the first message. In other words, all signals in the first valid signal belong to the first message. Correspondingly, when the first message is not the first conversion message, it means that some signals in the first valid signal belong to the first message.

[0015] Exemplarily, the communication protocol stack may be a controller area network (CAN) protocol stack, a local interconnect network (LIN) protocol stack, a FlexRay protocol stack, or another in-vehicle wired signal type protocol stack.

[0016] In this implementation, the conversion device can send the first message to different targets based on whether the first message is a first conversion message. For example, if the first message is a first conversion message, the first message is received by the first control device of the first vehicle; if the first message is not a first conversion message, the first message is received by the target device in the first vehicle where the communication protocol stack is deployed. This supports different application scenarios and improves the applicability of the message conversion method.

[0017] Optionally, when sending the first message to the target device, the first conversion message also includes a first wired message, which is obtained through signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

[0018] Here, "at least one second signal in the first valid signal is associated with the first wired message" means that the at least one second signal in the first valid signal belongs to the first wired message, that is, the at least one second signal is included in the first wired message. In other words, when the first message is sent to the target device, part of the first valid signal comes from the first message, and part comes from the first wired message.

[0019] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0020] SOME / IP-based services refer to service components that are presented to the outside world through SOME / IP. These services can be, for example, atomic services, composite services, or application services. SOME / IP-based services can be understood as native services within SOA.

[0021] For example, if the SOME / IP-based service is a body domain service, vehicle components within the body domain, such as wipers and rearview mirrors, can be directly adjusted through the SOME / IP-based service; if the SOME / IP-based service is a cockpit domain service, vehicle components within the cockpit domain, such as seats and cameras, can be directly adjusted through the SOME / IP-based service.

[0022] Services based on in-vehicle wired signals refer to the service-oriented nature of in-vehicle wired signals. This abstracts hardware resources such as sensors, actuators, and legacy electronic control units (ECUs) so they can interact with the outside world through APIs. Legacy ECUs can include microcontroller units (MCUs), electronic stability program (ESP) controllers, electric power steering (EPS) controllers, battery management systems (BMSs), or other ECUs.

[0023] For example, the ESP controller is connected to the in-vehicle network through the in-vehicle bus. The ESP controller itself has control functions, and the ESP signal sent by the ESP controller is abstracted as an API to achieve interaction with the outside world.

[0024] Exemplarily, when the type of the first original message includes an in-vehicle wired signal, the first original message includes at least one of at least one CAN message, at least one LIN message, and at least one FlexRay message.

[0025] By implementing the above implementation, signal translation in different scenarios can be completed for different types of original messages to output a unified message with a fixed format, thereby shielding the differences between multiple different input signal sources.

[0026] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0027] The first API message and the second API message correspond to the same service; or,

[0028] The first API message and the second API message correspond to different services.

[0029] Exemplarily, the first API message and the second API message corresponding to the same service can be understood as: the first API message and the second API message both correspond to service 1, wherein the type of service 1 is a service based on SOME / IP or a service based on an in-vehicle wired signal.

[0030] Exemplarily, the first API message and the second API message correspond to different services, which may be: the service corresponding to the first API message and the service corresponding to the second API message are two services of different types or two different services of the same type.

[0031] For example, the first API message corresponds to service 1, and the second API message corresponds to service 2. If service 1 is a service after the ESP signal is abstracted, and service 2 is a service after the EPS signal is abstracted, then service 1 and service 2 are two different services of the same type; if service 1 is a native service in the vehicle body domain, and service 2 is a service after the ESP signal is abstracted, then service 1 and service 2 are two services of different types.

[0032] By implementing the above implementation, API messages from different services or the same service can be converted, completing signal escape in different scenarios and improving the applicability of the message conversion method.

[0033] Optionally, obtaining the first original message of the first vehicle includes: receiving the first API message from a second control device of the first vehicle; and receiving the second API message from a third control device of the first vehicle.

[0034] Exemplarily, the conversion device, the second control device and the third control device may all be deployed on the same domain controller or the same vehicle integration unit.

[0035] Exemplarily, the conversion device is deployed on a domain controller or a vehicle integrated unit, and the second control device and the third control device are deployed on the same domain controller or the same vehicle integrated unit, but the domain controller or vehicle integrated unit where the conversion device is located is different from the domain controller or vehicle integrated unit where the second control device is located.

[0036] Exemplarily, the conversion device, the second control device and the third control device are respectively deployed on different domain controllers and / or vehicle integrated units.

[0037] By implementing the above implementation, the conversion device can obtain the first original message from different message sources.

[0038] Optionally, obtaining the first original message of the first vehicle includes: receiving the first original message from a fourth control device of the first vehicle.

[0039] Exemplarily, the fourth control device and the conversion device can be deployed on the same domain controller or the same vehicle integration unit of the first vehicle, or can be deployed on different domain controllers or different vehicle integration units of the first vehicle.

[0040] By implementing the above implementation, the conversion device can obtain the first original message from the same message source.

[0041] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0042] Exemplarily, the correspondence between at least one first signal and at least one API parameter may be: one first signal corresponds to one API parameter, multiple first signals correspond to one API parameter, one first signal corresponds to multiple API parameters or other correspondences, which are not specifically limited here.

[0043] It can be seen that the correspondence between the signal in the first valid signal and the API parameter in the first original message is diverse.

[0044] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0045] Mapping based on similarity between the physical meanings of states; and

[0046] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0047] Exemplarily, "a first signal includes at least one first state" means that the first signal can be represented by a field, a binary value, or other means. Different preset values ​​of the first signal can represent multiple first states, but the first signal can only take one of the multiple preset values ​​at any given moment to represent a single first state. Accordingly, "a first API parameter includes at least one second state" can also refer to the description regarding the first signal including at least one first state, and is not further elaborated here.

[0048] For example, at least one first state of the first signal includes state 1, state 2 and state 3, wherein when the first signal takes the first preset value, it represents state 1; when the first signal takes the second preset value, it represents state 2; when the first signal takes the third preset value, it represents state 3.

[0049] By implementing the above implementation method, different mapping rules can be used to quickly achieve the correspondence between at least one first state of the first signal in the first valid signal and at least one second state of the first API parameter in the first original message, which is conducive to improving the efficiency of signal escape.

[0050] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0051] Optionally, the conversion device is deployed in any one of the following components of the first vehicle:

[0052] Vehicle integrated unit VIU;

[0053] Vehicle domain controller (VDC);

[0054] Cockpit Domain Controller (CDC); or

[0055] Mobile Data Center MDC.

[0056] For example, if multiple logical functions of the aforementioned VDC, MDC, and CDC are integrated, the conversion device can also be deployed on a domain controller that integrates multiple logical functions. For example, if the MDC and CDC are integrated, the conversion device can be deployed on a domain controller that provides both autonomous driving control functions and cockpit control functions.

[0057] It can be seen that the deployment of the conversion device on the first vehicle is relatively flexible and can meet the message conversion needs in various scenarios.

[0058] Optionally, the method also includes: obtaining a second original message of the second vehicle; generating a second message based on the second original message, the second message is related to the characteristics of the second vehicle, and the second message is included in a second conversion message; sending the second message; wherein the second conversion message includes the multiple signals, the multiple signals include a second valid signal and a second invalid signal, the second valid signal corresponds to the characteristics of the second vehicle, the second invalid signal is a signal corresponding to the characteristics of other vehicles other than the second vehicle, the characteristics of other vehicles other than the second vehicle are different from the characteristics of the second vehicle, at least one signal in the second valid signals is associated with the second message, the first valid signal and the second valid signal have at least one different signal, and the first invalid signal and the second invalid signal have at least one different signal.

[0059] Exemplarily, signal 1 is one of the above-mentioned multiple signals, wherein signal 1 belongs to the first valid signal and signal 1 belongs to the second invalid signal.

[0060] As can be seen, when the conversion device is deployed on different vehicles, the conversion messages contain the same signals, manifested by the same signal names and number. For example, the first conversion message includes N signals, and the second conversion message also includes these N signals. When used on different vehicles, the N signals can be identified based on the vehicle's characteristics, with the signals corresponding to that vehicle being considered valid signals and those not corresponding to that vehicle being considered invalid signals. This provides a unified, fixed-format conversion message to different receiving ends, enabling cross-vehicle reuse.

[0061] In second aspect, the present application provides a message receiving method, the method comprising: receiving a first converted message, the first converted message comprising a first message, the first message being generated based on a first original message of a first vehicle, the first message being related to the characteristics of the first vehicle; wherein, the first converted message comprises multiple signals, the multiple signals comprising a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristics of the first vehicle, the first invalid signal being a signal corresponding to the characteristics of vehicles other than the first vehicle, the characteristics of vehicles other than the first vehicle being different from the characteristics of the first vehicle, and at least one first signal in the first valid signals being associated with the first message.

[0062] The method can be applied to a first control device, which can be deployed on a vehicle integrated unit or a domain controller of a first vehicle. The first control device can be a component in the vehicle integrated unit or a component in the domain controller. For example, the component can be at least one of a chip, an integrated circuit, etc.

[0063] Here, information about the characteristics of the first vehicle, multiple signals in the first conversion message, the first valid signal, the first invalid signal, the association of at least one first signal in the first valid signal with the first message, etc. can be referred to the description of the corresponding content of the first aspect above, and will not be repeated here.

[0064] In the above method, the first conversion message obtained includes not only the first valid signal corresponding to the characteristics of the first vehicle, but also the first invalid signal corresponding to the characteristics of other vehicles except the first vehicle. In this way, the first conversion message has the characteristics of full quantization and platformization. The output format of the first conversion message containing valid signals and invalid signals can support the reuse of vehicles with different characteristics.

[0065] Optionally, the receiving of the first conversion message includes: the first message is the first conversion message, and the first conversion message is received from the conversion device of the first vehicle; or, the first conversion message is received from the target device of the first vehicle, and a communication protocol stack is deployed on the target device.

[0066] Here, the domain controller or vehicle integration unit where the conversion device is located is different from the domain controller or vehicle integration unit where the first control device is located, and the domain controller or vehicle integration unit where the target device is located is different from the domain controller or vehicle integration unit where the first control device is located. The domain controller or vehicle integration unit where the conversion device is located is also different from the domain controller or vehicle integration unit where the target device is located.

[0067] By implementing the above implementation, the first converted message can be obtained from different sending ends in different scenarios. For example, when the first message is a first converted message, the first converted message is received from the conversion device of the first vehicle; when the first message is not a first converted message, the first converted message is received from the target device in the first vehicle that is equipped with a communication protocol stack.

[0068] The technical effects of any feature in any possible implementation of the second aspect below can refer to the description of the technical effects of the corresponding features of the first aspect above, and will not be repeated here.

[0069] Optionally, when receiving the first conversion message from the target device, the first conversion message also includes a first wired message, which is obtained by signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

[0070] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0071] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0072] The first API message and the second API message correspond to the same service; or,

[0073] The first API message and the second API message correspond to different services.

[0074] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0075] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0076] Mapping based on similarity between the physical meanings of states; and

[0077] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0078] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0079] In a third aspect, the present application provides a message conversion method, the method comprising: receiving a first message, the first message being generated based on a first original message of a first vehicle, the first message being associated with a characteristic of the first vehicle; obtaining a first conversion message based on a first wired message and the first message, wherein the first wired message is obtained through signal routing reorganization based on a wired signal in the first vehicle, and the first wired message is related to the characteristic of the first vehicle; the first conversion message comprises a plurality of signals, the plurality of signals comprising a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristic of the first vehicle, the first invalid signal being a signal corresponding to the characteristic of other vehicles other than the first vehicle, the characteristics of other vehicles other than the first vehicle being different from the characteristics of the first vehicle, at least one first signal in the first valid signal being associated with the first message, and at least one second signal in the first valid signal being associated with the first wired message; and sending the first conversion message to a first control device of the first vehicle.

[0080] The method can be applied to a target device deployed with a communication protocol stack. The target device can be deployed on a domain controller or a whole vehicle integrated unit of a first vehicle. The target device can be, for example, a component in the whole vehicle integrated unit or a component in the domain controller. The component can be, for example, at least one of a chip, an integrated circuit, etc.

[0081] The communication protocol stack may be, for example, a CAN protocol stack, a LIN protocol stack, a FlexRay protocol stack, or another in-vehicle wired signal type protocol stack.

[0082] Exemplarily, receiving the first message specifically includes: receiving the first message from a conversion device of the first vehicle, wherein the first message is obtained by the conversion device based on a first original message of the first vehicle.

[0083] Here, the multiple signals in the first conversion message are the maximum set of signals corresponding to the characteristics of multiple vehicles. For example, the multiple signals in the first conversion message may be pre-obtained by the target device from at least one original equipment manufacturer (OEM). Furthermore, the conversion device may also obtain from the OEM the correspondence between the characteristics of the first vehicle and the at least one second signal.

[0084] In the above method, the target device can combine the first message and the first wired message obtained by signal routing reorganization to output a conversion message with a fixed format, which not only shields the differences between multiple different input signal sources, but also realizes the full quantization and platformization of the output conversion message, which is conducive to cross-vehicle reuse.

[0085] The technical effects of any feature in any possible implementation of the third aspect below can refer to the description of the technical effects of the corresponding features of the first aspect above, and will not be repeated here.

[0086] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0087] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0088] The first API message and the second API message correspond to the same service; or,

[0089] The first API message and the second API message correspond to different services.

[0090] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0091] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0092] Mapping based on similarity between the physical meanings of states; and

[0093] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0094] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0095] In a fourth aspect, the present application provides a message conversion device, which is a conversion device or is included in the conversion device, and the device includes: an acquisition unit for acquiring a first original message of a first vehicle; a processing unit for generating a first message based on the first original message, the first message is related to the characteristics of the first vehicle, and the first message is included in a first conversion message; a sending unit for sending the first message; wherein the first conversion message includes multiple signals, the multiple signals include a first valid signal and a first invalid signal, the first valid signal corresponds to the characteristics of the first vehicle, the first invalid signal is a signal corresponding to the characteristics of other vehicles other than the first vehicle, the characteristics of other vehicles other than the first vehicle are different from the characteristics of the first vehicle, and at least one first signal in the first valid signals is associated with the first message.

[0096] Optionally, the sending unit is specifically used to: send the first message, which is the first conversion message, to the first control device of the first vehicle; or send the first message to the target device of the first vehicle, on which a communication protocol stack is deployed.

[0097] Optionally, when sending the first message to the target device, the first conversion message also includes a first wired message, which is obtained through signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

[0098] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0099] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0100] The first API message and the second API message correspond to the same service; or,

[0101] The first API message and the second API message correspond to different services.

[0102] Optionally, the acquisition unit is specifically used to: receive the first API message from the second control device of the first vehicle; and receive the second API message from the third control device of the first vehicle.

[0103] Optionally, the acquiring unit is specifically configured to: receive the first original message from a fourth control device of the first vehicle.

[0104] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0105] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0106] Mapping based on similarity between the physical meanings of states; and

[0107] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0108] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0109] Optionally, the conversion device is deployed in any one of the following components of the first vehicle:

[0110] Vehicle integrated unit VIU;

[0111] Vehicle domain controller (VDC);

[0112] Cockpit Domain Controller (CDC); or

[0113] Mobile Data Center MDC.

[0114] Optionally, the acquisition unit is also used to: acquire a second original message of the second vehicle; the processing unit is also used to generate a second message based on the second original message, the second message is related to the characteristics of the second vehicle, and the second message is included in a second conversion message; the sending unit is also used to send the second message; wherein, the second conversion message includes the multiple signals, the multiple signals include a second valid signal and a second invalid signal, the second valid signal corresponds to the characteristics of the second vehicle, the second invalid signal is a signal corresponding to the characteristics of other vehicles other than the second vehicle, the characteristics of other vehicles other than the second vehicle are different from the characteristics of the second vehicle, at least one signal in the second valid signals is associated with the second message, the first valid signal and the second valid signal have at least one different signal, and the first invalid signal and the second invalid signal have at least one different signal.

[0115] In the fifth aspect, the present application provides a message receiving device, which includes: a receiving unit for receiving a first converted message, the first converted message including a first message, the first message being generated based on a first original message of a first vehicle, and the first message being related to the characteristics of the first vehicle; wherein, the first converted message includes multiple signals, the multiple signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristics of the first vehicle, the first invalid signal being a signal corresponding to the characteristics of vehicles other than the first vehicle, the characteristics of vehicles other than the first vehicle being different from the characteristics of the first vehicle, and at least one first signal in the first valid signals is associated with the first message.

[0116] Optionally, the receiving unit is specifically used to: the first message is the first conversion message, and the first conversion message is received from the conversion device of the first vehicle; or, the first conversion message is received from the target device of the first vehicle, and a communication protocol stack is deployed on the target device.

[0117] Optionally, when receiving the first conversion message from the target device, the first conversion message also includes a first wired message, which is obtained by signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

[0118] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0119] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0120] The first API message and the second API message correspond to the same service; or,

[0121] The first API message and the second API message correspond to different services.

[0122] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0123] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0124] Mapping based on similarity between the physical meanings of states; and

[0125] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0126] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0127] In a sixth aspect, the present application provides a message conversion device, which includes: a receiving unit for receiving a first message, wherein the first message is generated based on a first original message of a first vehicle, and the first message is associated with the characteristics of the first vehicle; a processing unit for obtaining a first conversion message based on a first wired message and the first message, wherein the first wired message is obtained through signal routing reorganization based on a wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle; the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal, the first valid signal corresponds to the characteristics of the first vehicle, the first invalid signal is a signal corresponding to the characteristics of other vehicles other than the first vehicle, and the characteristics of other vehicles other than the first vehicle are different from the characteristics of the first vehicle, at least one first signal in the first valid signal is associated with the first message, and at least one second signal in the first valid signal is associated with the first wired message; a sending unit for sending the first conversion message to a first control device of the first vehicle.

[0128] Optionally, the first original message includes at least one message, the type of the first original message includes at least one of an application programming interface API message and an in-vehicle wired signal, and the API message includes at least one of the following types: an API message corresponding to a service based on an extensible service-oriented middleware SOME / IP running on IP; and an API message corresponding to a service based on an in-vehicle wired signal.

[0129] Optionally, the first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions:

[0130] The first API message and the second API message correspond to the same service; or,

[0131] The first API message and the second API message correspond to different services.

[0132] Optionally, the type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0133] Optionally, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0134] Mapping based on similarity between the physical meanings of states; and

[0135] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0136] Optionally, the type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

[0137] In a seventh aspect, the present application provides a chip comprising at least one processor and a communication interface, wherein the communication interface is configured to provide information input and / or output to the at least one processor. The chip is configured to implement the method of the first aspect or any possible embodiment of the first aspect, or the method of the second aspect or any possible embodiment of the second aspect, or the method of the third aspect or any possible embodiment of the third aspect.

[0138] In an eighth aspect, the present application provides a vehicle comprising at least one of a first device, a second device, and a third device, wherein the first device is used to implement the method of the above-mentioned first aspect or any possible implementation of the first aspect, the second device is used to implement the method of the above-mentioned second aspect or any possible implementation of the second aspect, and the fourth device is used to implement the method of the above-mentioned third aspect or any possible implementation of the third aspect.

[0139] Illustratively, the first device may be a device of any possible implementation manner of the fourth aspect or the chip of the seventh aspect, the second device may be a device of any possible implementation manner of the fifth aspect or the chip of the seventh aspect, and the third device may be a device of any possible implementation manner of the sixth aspect or the chip of the seventh aspect.

[0140] In a ninth aspect, the present application provides a computer-readable storage medium comprising computer instructions, which, when executed by a processor, implement the method of the first aspect or any possible implementation of the first aspect, or implement the method of the second aspect or any possible implementation of the second aspect, or implement the method of the third aspect or any possible implementation of the third aspect.

[0141] In the tenth aspect, the present application provides a computer program product, which, when executed by a processor, implements the method in the above-mentioned first aspect or any possible embodiment of the first aspect, or implements the method in the above-mentioned second aspect or any possible embodiment of the second aspect, or implements the method in the above-mentioned third aspect or any possible embodiment of the third aspect.

[0142] Exemplarily, the computer program product may be a software installation package. BRIEF DESCRIPTION OF THE DRAWINGS

[0143] FIG1 is a schematic diagram of the architecture of an in-vehicle communication system provided in an embodiment of the present application;

[0144] FIG2 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0145] FIG3 is a flow chart of a message conversion method provided in an embodiment of the present application;

[0146] FIG4A is a schematic diagram of a state mapping provided by an embodiment of the present application;

[0147] FIG4B is a schematic diagram of mapping another state provided in an embodiment of the present application;

[0148] FIG4C is a schematic diagram of mapping another state provided in an embodiment of the present application;

[0149] FIG5 is a schematic diagram of mapping another state provided in an embodiment of the present application;

[0150] FIG6 is a flowchart of another message conversion method provided in an embodiment of the present application;

[0151] FIG7 is a schematic diagram of a scene inside a first vehicle provided in an embodiment of the present application;

[0152] FIG8A is a schematic structural diagram of a conversion device provided in an embodiment of the present application;

[0153] FIG8B is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0154] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0155] It should be noted that the prefixes such as "first" and "second" used in this application are only for distinguishing different description objects, and do not have any limiting effect on the position, order, priority, quantity or content of the described objects. For example, if the described object is a "field", then the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields", and "first" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the described object is a "level", then the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of described objects is not limited by the prefix and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the described object is a "device," then the "first device" and the "second device" can be the same device, the same type of device, or different types of devices. For another example, if the described object is "information," then the "first information" and the "second information" can be information of the same content or information of different contents. In short, the use of prefixes to distinguish the described objects in the embodiments of this application does not constitute a limitation on the described objects. For the description of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0156] It should be noted that the descriptions used in the embodiments of the present application, such as "at least one of a1, a2, ..., and an" and the like, include any one of a1, a2, ..., and an existing alone, and any combination of any multiple of a1, a2, ..., and an, each of which can exist alone. For example, the description "at least one of a, b, and c" includes a alone, b alone, c alone, a combination of a and b, a combination of a and c, a combination of b and c, or a combination of ab and c.

[0157] To facilitate understanding, the following first introduces relevant terms that may be involved in the embodiments of this application.

[0158] (1) CAN bus

[0159] The controller area network (CAN) bus is a shared two-wire serial communication bus that can use twisted pair cables or optical cables to transmit signals. It can be used in automotive power systems, chassis, and body electronics.

[0160] (2) LIN bus

[0161] The local interconnect network (LIN) bus is a low-cost serial communication bus used to control distributed electronic systems in automobiles. It is suitable for communication scenarios where bandwidth, performance, or fault tolerance are not critical, primarily serving as a supplement to the CAN bus. The LIN bus differs from the CAN bus primarily in its single-master, multiple-slave architecture (slave nodes only send information when the master requests it), its use of a single signal line for transmission, and its lighter-weight processing protocol stack.

[0162] (3)FlexRay bus

[0163] The FlexRay bus is a bus standard that offers deterministic timing, distributed clock synchronization, and fault tolerance. Its primary advantage is its higher bandwidth compared to the CAN bus, but at a higher cost. It is therefore well-suited for vehicle drive-by-wire systems (such as suspension control, gear shifting, braking, and steering).

[0164] (4) SOME / IP protocol

[0165] Scalable service-oriented middleware over IP (SOME / IP) is the core communication protocol for implementing automotive service-oriented architecture (SOA). SOME / IP is used for the transmission of control messages and application data in automotive Ethernet networks. SOME / IP resides in the application layer of the Open Systems Interconnection Reference Model (OSI).

[0166] The SOME / IP protocol's communication mechanism considers the needs of the receiver. For example, the electronic control unit only sends a request when it needs data. This differs from traditional bus communication mechanisms, such as in-vehicle networks based on the CAN bus, where data transmission depends on the sender's transmission cycle or the sender's detection of a signal change. Therefore, the SOME / IP protocol can effectively reduce bus load.

[0167] The technical solution in this application will be described below with reference to the accompanying drawings.

[0168] Referring to Figure 1, which is a schematic diagram of the architecture of an in-vehicle communication system provided in an embodiment of the present application, the system includes at least one domain controller (DC) and at least one vehicle integrated unit (VIU).

[0169] The vehicle integration unit (VIU) manages the electronic control units (ECUs) within its area. The VIU provides close access to the corresponding sensors, actuators, or ECUs, enabling power supply, electronic fuses, I / O port isolation, and other functions. The VIU also possesses some or all of the functions of a gateway, such as protocol conversion, protocol encapsulation and forwarding, and data format conversion. When the VIU integrates the functions of the ECUs within certain vehicle components, it also provides electronic control capabilities for controlling those components.

[0170] Each functional domain in the vehicle can have an independent domain controller. The domain controller can be understood as a general term for a system that includes domain master hardware, operating system, algorithm and application software. In Figure 1, at least one DC includes a vehicle domain controller (VDC), a mobile data center (MDC) and a cockpit domain controller (CDC). Among them, the VDC is used to provide services for vehicle parts in the body domain and vehicle parts in the chassis domain, the MDC is used to provide services for vehicle parts that realize autonomous driving functions, and the CDC is used to provide services for vehicle parts in the cockpit domain. In some possible embodiments, the MDC can also be called an advanced driving assistance system domain controller (ADAS DC) or an automatic drive domain controller (AD DC).

[0171] Here, the in-vehicle communication system shown in Figure 1 adopts a hybrid networking, that is, a combination of Ethernet and an in-vehicle wired signal bus for networking. Among them, Ethernet is used to realize service-oriented communication, and the in-vehicle wired signal bus is used to realize signal-oriented communication. In other words, the main functions in the vehicle are provided to local applications or cross-domain applications in the form of services through Ethernet, which can achieve the decoupling of software and hardware and the flexible deployment of functions to a certain extent; individual domain controllers in the vehicle (such as domain controllers with high safety requirements for the power chassis) realize signal-based communication through the in-vehicle wired signal bus. Exemplarily, the in-vehicle wired signal bus includes at least one of the above-mentioned CAN bus, LIN bus and FlexRay bus.

[0172] In FIG1 , VIUs communicate with each other via at least one of Ethernet and an in-vehicle wired signal bus. For example, VIU1 can communicate with other VIUs in FIG1 via Ethernet, and VIU1 and VIU2 can also communicate via the in-vehicle wired signal bus. For another example, VIU2 and VIU3 can communicate via Ethernet.

[0173] In Figure 1 , communication between DCs and between DCs and VIUs can occur via at least one of Ethernet and an in-vehicle wired signal bus. For example, communication between the VDC and VIU1 can occur via either Ethernet or an in-vehicle wired signal bus. Another example is communication between the MDC and VIU1 via Ethernet, while communication between the VDC and MDC can occur via an in-vehicle wired signal bus.

[0174] In some possible embodiments, the in-vehicle communication system shown in FIG1 further includes a telematics box (TBOX), which can communicate with the above-mentioned vehicle integration unit and / or domain controller via a CAN bus, for example, to transmit information or instructions, including vehicle status information, key status information, control instructions, etc.

[0175] The three domain controllers shown in Figure 1 are just examples. In some possible embodiments, the logical functions of multiple components of the aforementioned VDC, MDC, and CDC can be integrated. For example, the MDC and CDC can be integrated to obtain a domain controller that can provide both autonomous driving control and cockpit control functions. In another example, the VDC and CDC can be integrated to obtain a domain controller that can provide both body control and cockpit control functions. In another example, the VDC and MDC can be integrated to obtain a domain controller that can provide both body control and autonomous driving control functions.

[0176] The vehicle communication system shown in Figure 1 can be applied to autonomous driving vehicles, traditional vehicles or new energy vehicles, etc., where traditional vehicles refer to fuel vehicles, such as gasoline vehicles, diesel vehicles, etc., and new energy vehicles can be, for example, electric vehicles (EV), hybrid electric vehicles (HEV), extended-range electric vehicles (range extended EV), plug-in hybrid vehicles (plug-in HEV), fuel cell vehicles or other new energy vehicles, etc., and are not specifically limited here.

[0177] It should be noted that Figure 1 is merely an exemplary architecture diagram and does not limit the communication connections between network elements to the form shown in Figure 1, nor does it limit the number of network elements included in the system shown in Figure 1. Although not shown in Figure 1, Figure 1 may also include other functional entities in addition to the functional entities shown in Figure 1. In addition, the methods provided in the embodiments of the present application can be applied to the communication system shown in Figure 1. Of course, the methods provided in the embodiments of the present application can also be applied to other communication systems, and the embodiments of the present application are not limited in this regard.

[0178] See Figure 2, which is a schematic diagram of a communication system provided in an embodiment of the application. In Figure 2, the system is used to convert messages in an in-vehicle network. The system includes a conversion device, at least one message source, and a target receiving device. The conversion device, at least one message source, and the target receiving device are deployed in the same vehicle. The at least one message source can communicate with the conversion device via Ethernet and / or an in-vehicle wired signal bus, and the target receiving device communicates with the conversion device via the in-vehicle wired signal bus.

[0179] Among them, the conversion device can be deployed on any vehicle integrated unit or any domain controller of the vehicle. The conversion device can be a component in the vehicle integrated unit or a component in the domain controller. For example, the component can be at least one of a chip, an integrated circuit, etc.

[0180] The target receiving end can be deployed on the aforementioned vehicle integration unit, domain controller, or TBOX. Here, when the target receiving end is deployed on the vehicle integration unit or domain controller, the target receiving end and the conversion device are deployed on different vehicle integration units or domain controllers. In Figure 2, the target receiving end can be a first control device, which can be a component in any of the vehicle integration unit, domain controller, and TBOX. For example, the component can be at least one of a chip, an integrated circuit, etc.

[0181] At least one message source is also deployed on at least one of the vehicle integration unit and domain controller. One or more of the at least one message source can be deployed on the same vehicle integration unit or domain controller as the conversion device, or on a different vehicle integration unit or domain controller. In Figure 2 , the at least one message source includes a second control device and a third control device. The second control device or the third control device can be a component in either the vehicle integration unit or the domain controller, such as a chip or integrated circuit.

[0182] Exemplarily, the conversion device is deployed on VIU1 in FIG. 1 , the first control device is deployed on VDC in FIG. 1 , the second control device is deployed on VIU4 in FIG. 1 , and the third control device is deployed on MDC in FIG. 1 .

[0183] In Figure 2, the conversion device obtains the original message from at least one message source. Since the target receiving end does not support the communication protocol corresponding to the original message, the conversion device converts the original message according to the characteristics of the vehicle. For example, a conversion message can be obtained and sent to the target receiving end, wherein the target receiving end supports the communication protocol corresponding to the conversion message. The type of the original message can be, for example, an application programming interface API message, and the type of the conversion message can be an in-vehicle wired signal. The conversion message can be any of a CAN message, a LIN message, and a FlexRay message. The format of the conversion message can support application on a variety of different vehicles. For details of the conversion message, please refer to the relevant description of the following method embodiment, which will not be repeated here.

[0184] See Figure 3, which is a flow chart of a message conversion method provided in an embodiment of the present application, which is applied to a conversion device. The conversion device may be, for example, the conversion device shown in Figure 2. The method includes but is not limited to the following steps:

[0185] S301: Obtain a first original message of a first vehicle.

[0186] The first original message includes at least one message, and a type of the first original message includes at least one of an application programming interface (API) message and an in-vehicle wired signal.

[0187] Furthermore, the API message includes at least one of the following types: an API message corresponding to a service based on SOME / IP and an API message corresponding to a service based on an in-vehicle wired signal. Here, the in-vehicle wired signal includes at least one of a CAN signal, a LIN signal, a FlexRay signal, and the like.

[0188] Exemplarily, when the type of the first original message includes an in-vehicle wired signal, the first original message includes at least one of at least one CAN message, at least one LIN message, and at least one FlexRay message.

[0189] SOME / IP-based services refer to service components that are presented to the outside world through SOME / IP. These services can be, for example, atomic services, composite services, or application services. SOME / IP-based services can be understood as native services within SOA.

[0190] For example, if the SOME / IP-based service is a body domain service, vehicle components within the body domain, such as wipers and rearview mirrors, can be directly adjusted through the SOME / IP-based service; if the SOME / IP-based service is a cockpit domain service, vehicle components within the cockpit domain, such as seats and cameras, can be directly adjusted through the SOME / IP-based service.

[0191] Services based on in-vehicle wired signals refer to turning in-vehicle wired signals into services, that is, abstracting hardware resources such as sensors, actuators, and legacy electronic control units (legacy ECUs) to interact with the outside world through APIs.

[0192] For example, an electronic stability program (ESP) controller is connected to the in-vehicle network through an in-vehicle bus. The ESP controller itself has a control function, but the ESP signal sent by the ESP controller can be abstracted as an API to achieve interaction with the outside world.

[0193] In one implementation, when the type of the first original message is an API message, if the first original message includes a first API message and a second API message, the first API message and the second API message may correspond to the same service or different services, which is not specifically limited here.

[0194] For example, the first API message and the second API message may correspond to the same service: the first API message and the second API message both correspond to service 1, wherein the type of service 1 is a service based on SOME / IP or a service based on an in-vehicle wired signal.

[0195] For example, the first API message and the second API message may correspond to different services: the first API message corresponds to service 1, and the second API message corresponds to service 2, where service 1 and service 2 may be two services of different types, for example, the type of service 1 is a service based on SOME / IP and the type of service 2 is a service based on in-vehicle wired signals; service 1 and service 2 may also be two different services of the same type, for example, the type of service 1 and the type of service 2 are both services based on in-vehicle wired signals.

[0196] Furthermore, in this case (i.e., the type of the first original message is an API message, and the first original message includes the first API message and the second API message), the way in which the conversion device obtains the first original message may be, for example, way 1 or way 2:

[0197] Method 1: Obtain the first original message from two different message sources

[0198] Specifically, obtaining the first original message includes: receiving a first API message from a second control device of the first vehicle and receiving a second API message from a third control device of the first vehicle.

[0199] The deployment of the conversion device, the second device control and the third control device on the first vehicle includes the following situations:

[0200] Case 1: The conversion device, the second control device and the third control device are all deployed on the same domain controller or the same vehicle integration unit.

[0201] Case 2: The conversion device is deployed on a domain controller or a vehicle integrated unit, and the second control device and the third control device are deployed on the same domain controller or the same vehicle integrated unit, but the domain controller or vehicle integrated unit where the conversion device is located is different from the domain controller or vehicle integrated unit where the second control device is located.

[0202] For example, the conversion device is deployed on the domain controller 1 or the vehicle integration unit 1, and the second control device and the third control device are both deployed on the domain controller 2 or the vehicle integration unit 2.

[0203] Case 3: The conversion device, the second control device and the third control device are respectively deployed on different domain controllers and / or vehicle integration units.

[0204] For example, the conversion device is deployed on the domain controller 1 or the vehicle integration unit 1, the second control device is deployed on the domain controller 2 or the vehicle integration unit 2, and the third control device is deployed on the domain controller 3 or the vehicle integration unit 3.

[0205] Method 2: Get the first original message from a message source

[0206] Specifically, obtaining the first original message includes: receiving a first API message and a second API message from a fourth control device of the first vehicle.

[0207] Among them, the fourth control device and the conversion device can be deployed on the same domain controller or the same vehicle integration unit of the first vehicle, or they can be deployed on different domain controllers or different vehicle integration units in the first vehicle. For example, the conversion device is deployed on domain controller 1 or vehicle integration unit 1, and the fourth control device is deployed on domain controller 2 or vehicle integration unit 2.

[0208] In one implementation, when the type of the first original message is an in-vehicle wired signal, the first original message includes at least one of the following:

[0209] At least one CAN message;

[0210] At least one LIN message; and

[0211] At least one FlexRay message.

[0212] Illustratively, the at least one CAN message is obtained by the conversion device from a conventional ECU connected via a CAN bus, the at least one LIN message is obtained by the conversion device from a conventional ECU connected via a LIN bus, and the at least one FlexRay message is obtained by the conversion device from a conventional ECU connected via a FlexRay bus. It is understood that the first original message may be obtained by the conversion device from at least one message source.

[0213] In another implementation, the type of the first original message includes an API message and an in-vehicle wired signal. In this case, the specific content of the first original message can be referred to the above-mentioned description that the type of the first original message is an API message and the type of the first original message is an in-vehicle wired signal, which will not be repeated here.

[0214] S302: Convert the first original message into a first message based on the characteristics of the first vehicle.

[0215] The first vehicle's characteristics include at least one of the following: the first vehicle's model, configuration information, manufacturer, and component information. For example, the first vehicle's configuration information may be software configuration and / or hardware configuration. For example, the first vehicle's hardware configuration may be classified into three types: basic configuration, intermediate configuration, and advanced configuration. Here, the user can perceive the configuration information of the first vehicle.

[0216] Among them, the first message is included in the first conversion message, and the first conversion message includes multiple signals, which include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal in the first valid signal is associated with the first message.

[0217] Here, at least one first signal in the first valid signals is associated with the first message, which can be understood as: at least one first signal in the first valid signals belongs to the first message.

[0218] Here, the multiple signals in the first conversion message are the maximum set of signals corresponding to the characteristics of multiple vehicles.

[0219] Exemplarily, the multiple signals in the first conversion message may be obtained in advance by the conversion device from at least one original equipment manufacturer (OEM).

[0220] Because the first valid signal corresponds to a characteristic of the first vehicle, at least one first signal in the first valid signal corresponds to a characteristic of the first vehicle. For example, the correspondence between at least one first signal in the first valid signal and the characteristic of the first vehicle may be pre-acquired by the conversion device from the OEM. In some possible embodiments, the conversion device may also determine, based on information sent by the OEM, that the first invalid signal does not correspond to a characteristic of the first vehicle, and that the first invalid signal corresponds to a vehicle other than the first vehicle (e.g., vehicle 2).

[0221] Here, the first invalid signal in the first conversion message is marked as a default value or a default mark in the form of a pre-embedded code, so as to indicate that the first vehicle does not use the first invalid signal.

[0222] That is to say, the first valid signal is a signal that can be used by the first vehicle or a signal that the first vehicle needs to use, and the first invalid signal is a signal that cannot be used by the first vehicle or a signal that the first vehicle does not use, but the first invalid signal can be used by other vehicles other than the first vehicle. From this, it can be seen that the format of the first conversion message can support application on different vehicles.

[0223] It can be understood that the type of the first message is the same as the type of the first conversion message. The type of the first conversion message is related to the communication protocol supported by the first control device in the first vehicle. Here, the first control device is the recipient of the first conversion message. The first control device and the conversion device are deployed on different domain controllers or different vehicle integration units. For example, the conversion device is deployed on domain controller A or vehicle integration unit B, and the first control device is deployed on domain controller C or vehicle integration unit D. In addition, the first control device and the message source end of the first original message are also deployed on different domain controllers or different vehicle integration units.

[0224] For example, if the first control device only supports the CAN communication protocol, the type of the first converted message is specifically CAN, and the type of the first message is also CAN; if the first control device only supports the LIN communication protocol, the type of the first converted message is specifically LIN, and the type of the first message is also LIN; if the first control device only supports the FlexRay communication protocol, the type of the first converted message is specifically FlexRay, and the type of the first message is also FlexRay. In some possible embodiments, if the first control device supports at least one of the CAN communication protocol, the LIN communication protocol, and the FlexRay communication protocol, the type of the first converted message can be determined based on the actual needs of the first control device.

[0225] In one implementation, when the type of the first original message includes an application programming interface API message, at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

[0226] Here, the correspondence between at least one first signal in the first valid signal and at least one API parameter in the first original message includes at least one of the following situations:

[0227] A first signal in the first valid signal corresponds to an API parameter in the first original message;

[0228] A first signal in the first valid signal corresponds to a plurality of API parameters in the first original message; and

[0229] The multiple first signals in the first valid signal correspond to an API parameter in the first original message.

[0230] Exemplarily, when the first original message includes multiple API parameters, these multiple API parameters may come from the same API message in the first original message, or from different API messages in the first original message. Accordingly, these multiple API parameters may belong to the same service or to different services. When these multiple API parameters belong to different services, the scheduling period of the application software module (software component, SWC) where these multiple different services are located is the same as the scheduling period of the conversion device, for example, updated every 10 milliseconds, thereby preventing duplicate data or aging data from existing in the first message.

[0231] Here, the correspondence between the at least one first signal and the at least one API parameter can be pre-set by a user based on experience, or can be learned by an artificial intelligence algorithm through training, and is not specifically limited here. The following describes the correspondence between the at least one first signal and the at least one API parameter based on the first conversion message being a CAN message.

[0232] The following are some examples to illustrate the correspondence between a first signal and an API parameter:

[0233] For example, the first signal (CAN signal) “VIU_HighBeamIndReq” corresponds to the API parameter “HighBeamIndicatorReq”, wherein both the CAN signal “VIU_HighBeamIndReq” and the “HighBeamIndicatorReq” parameter are used to indicate a request for a high beam function indicator light.

[0234] For example, the first signal (CAN signal) "VIU_BMS_FaultLevel" corresponds to the API parameter "HvBattFltSt", where "VIU_BMS_FaultLevel" is used to indicate the fault level of the battery management system (BMS) on the VIU, and the "HvBattFltSt" parameter is used to indicate the high-voltage battery fault status.

[0235] For example, the first signal (CAN signal) "VIU_EPS_FaultState" corresponds to the API parameter "EPS_FltIncn", where "VIU_EPS_FaultState" is used to indicate the fault state of the electric power steering (EPS) system on the VIU, and the "EPS_FltIncn" parameter is used to indicate the fault indication of the EPS.

[0236] The following is a specific example to illustrate that a first signal corresponds to multiple API parameters: for example, the first signal (CAN signal) "VIU_BMS_ACChrgSt" corresponds to API parameter 1 "EMS_PortConnectStatus" and API parameter 2 "EMS_ChargeSt", where the "VIU_BMS_ACChrgSt" signal is used to indicate the AC charging status of the BMS on the VIU, the "EMS_PortConnectStatus" parameter is used to indicate the interface connection status of the engine management system (EMS), and the "EMS_ChargeSt" parameter is used to indicate the charging status of the EMS.

[0237] In some possible embodiments, the first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, and the first API parameter includes at least one second state, wherein a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions:

[0238] Mapping based on similarity between the physical meanings of states; and

[0239] The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, wherein the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

[0240] Here, the first signal including at least one first state means that the first signal can be represented by a field, a binary value, or other means. The first signal can represent multiple first states by taking different preset values, but the first signal can only take one of the multiple preset values ​​at any given moment to represent one first state. Accordingly, the first API parameter including at least one second state can also refer to the description of the first signal including at least one first state, and is not further described here.

[0241] For example, at least one first state of the first signal includes state 1, state 2 and state 3, wherein when the first signal takes the first preset value, it represents state 1; when the first signal takes the second preset value, it represents state 2; when the first signal takes the third preset value, it represents state 3.

[0242] Exemplarily, the mapping relationship between the at least one first state and the at least one second state may be pre-configured by the user on the conversion device based on the mapping rules, or may be learned by an artificial intelligence algorithm through training, which is not specifically limited here.

[0243] The following examples illustrate the mapping based on the similarity between the physical meanings of states:

[0244] Example 1: Take the correspondence between the above-mentioned "VIU_HighBeamIndReq" signal and the "HighBeamIndicatorReq" parameter as an example, that is, the first signal is "VIU_HighBeamIndReq" and the first API parameter is the "HighBeamIndicatorReq" parameter.

[0245] Refer to FIG4A, which is a state mapping diagram provided by an embodiment of the present application. In FIG4A, at least one first state of the "VIU_HighBeamIndReq" signal includes the Initial state indicated by 0x0, the OFF state indicated by 0x0, the AHB OFF, HiBeam ON (high beam automatic control system off, high beam on) state indicated by 0x2, the AHB ON, HiBeam OFF (high beam automatic control system on, high beam off) state indicated by 0x3, the AHB ON, HiBeam OFF (high beam automatic control system on, high beam off) state indicated by 0x4, and the AHB ON, HiBeam ON (high beam automatic control system on, high beam off) state indicated by 0x5. ON (high beam automatic control system is on, high beam is on) state and Reserved state indicated by 0x5-0x7; at least one second state of the "HighBeamIndicatorReq" parameter includes OFF state indicated by 0x0, AutoOFF, HighBeamON (automatic mode is off, high beam is on) state indicated by 0x1, AutoON, HighBeamON (automatic mode is on, high beam is on) state indicated by 0x2, AutoON, HighBeamOFF (automatic mode is on, high beam is on) state indicated by 0xFE, 0x3 indicating Initial state and Invalid state indicated by 0xFF.

[0246] Based on the similarity between the physical meanings of the states of both parties shown in Figure 4A, it can be seen that "0x0: Initial" in at least one first state corresponds to "0xFE: Initial" in at least one second state, "0x1: OFF" in at least one first state corresponds to "0x0: OFF" in at least one second state, "0x2: AHB OFF, HiBeam ON" in at least one first state corresponds to "0x1: AutoOFF, HighBeamON" in at least one second state, "0x3: AHB ON, HiBeam OFF" in at least one first state corresponds to "0x3: AutoON, HighBeamOFF" in at least one second state, "0x4: AHB ON, HiBeam ON" in at least one first state corresponds to "0x2: AutoON, HighBeamON" in at least one second state, and "0x5-0x7: Reserved" in at least one first state corresponds to "0xFF: Invalid" in at least one second state.

[0247] Example 2: Taking the correspondence between the above-mentioned “VIU_EPS_FaultState” signal and the “EPS_FltIncn” parameter as an example, the first signal is “VIU_EPS_FaultState” and the first API parameter is the “EPS_FltIncn” parameter.

[0248] Referring to FIG4B , FIG4B is a schematic diagram of a state mapping provided by an embodiment of the present application. In FIG4B , at least one first state of the "VIU_EPS_FaultState" signal includes a no failure state (indicated by 0x0), a slight failure state (indicated by 0x1), a critical failure state (indicated by 0x2), a fatal failure state (indicated by 0x3), and a reserved state (indicated by 0x4); and at least one second state of the "EPS_FltIncn" parameter includes a normal state (indicated by 0x0), a yellow lamp request state (indicated by 0x1), and a red lamp request state (indicated by 0x2).

[0249] It can be seen that the fault level classification granularity of the "EPS_FltIncn" parameter shown in Figure 4B is coarser than the fault level classification granularity of the "VIU_EPS_FaultState" CAN signal, and that "0x0:normal" in at least one second state corresponds to "0x0:no failure" in at least one first state, "0x1:yellow lamp request" in at least one second state corresponds to "0x1:slight failure" in at least one first state, and "0x2:red lamp request" in at least one second state can simultaneously correspond to "0x2:critical failure" and "0x3:fatal failure" in at least one first state. It can be understood that when the fault level classification granularity of the bus signal (as output) is finer than the fault level classification granularity of the API parameter (as input), the original information of the API parameter is not lost.

[0250] Exemplarily, if the first original message includes the API parameter "EPS_FltIncn", and the value of the API parameter "EPS_FltIncn" is 0x2 indicating a red lamp request, since "0x2: red lamp request" in Figure 4B corresponds to "0x2: critical failure" and "0x3: fatal failure", the first conversion message includes a "VIU_EPS_FaultState" signal, and the value of the "VIU_EPS_FaultState" signal is 0x2 indicating a critical failure state or 0x3 indicating a fatal failure state, which is not specifically limited here.

[0251] Example 3: Taking the correspondence between the above-mentioned "VIU_BMS_ACChrgSt" signal and the "EMS_PortConnectStatus" parameter and the "EMS_ChargeSt" parameter as an example, that is, the first signal is "VIU_BMS_ACChrgSt", and the first API parameter includes the "EMS_PortConnectStatus" parameter and the "EMS_ChargeSt" parameter.

[0252] Refer to Figure 4C, which is a mapping diagram of a state provided by an embodiment of the present application. In Figure 4C, it is necessary to select a suitable state from multiple second states of two different API parameters for mapping, wherein at least one first state of the "VIU_BMS_ACChrgSt" signal includes the off (unplugged) state indicated by 0x0, the init (initialization) state indicated by 0x1, the standby (standby) state indicated by 0x2, the charging (charging) state indicated by 0x3, the chg_end (charging termination) state indicated by 0x4, the preheat (preheating) state indicated by 0x5, the fault (charging abnormal termination) state indicated by 0x6 and the reserved (reserved) state indicated by 0x7-0xF; at least one second state includes multiple second states of EMS_PortConnectStatus (API parameter 1) and multiple second states of EMS_ChargeSt (API parameter 2), wherein the multiple second states of API parameter 1 include 0 indicating The API parameter 2 includes the init (initial value) state indicated by 1, the unplug (unconnected) state indicated by 1, the semilink (semi-connected) state indicated by 2, the plugin (connected) state indicated by 3, the abnormal (abnormal) state indicated by 4, and the invalid (invalid value) state indicated by 0XFF. The multiple second states of the API parameter 2 include the un_charge (uncharged) state indicated by 0x0, the charging (charging) state indicated by 0x1, the full_of_charge (full) state indicated by 0x2, the charge_end (charging termination) state indicated by 0x3, the heating (battery pack heating) state indicated by 0x4, the keep_warm (battery pack keeping warm) state indicated by 0x5, the abnormal (abnormal) state indicated by 0x6, the derating (derating charging) state indicated by 0x7, and the invalid (invalid) state indicated by 0xFF.

[0253] Based on the similarity between the physical meanings of the states of both parties shown in FIG4C , it can be seen that “0x0:off” of the “VIU_BMS_ACChrgSt” signal corresponds to “1:unplug” of API parameter 1, “0x1:init” of the “VIU_BMS_ACChrgSt” signal corresponds to “0:init” of API parameter 1, “0x2:standby” of the “VIU_BMS_ACChrgSt” signal corresponds to “0x0:un_charge” of API parameter 2, and “0x1:init” of the “VIU_BMS_ACChrgSt” signal corresponds to “0:init” of API parameter 1. "0x3:charging" corresponds to "0x1:charging" of API parameter 2, "0x4:chg_end" of the "VIU_BMS_ACChrgSt" signal corresponds to "0x3:charge_end" of API parameter 2, "0x5:preheat" of the "VIU_BMS_ACChrgSt" signal corresponds to "0x4:heating" of API parameter 2, and "0x6:fault" of the "VIU_BMS_ACChrgSt" signal corresponds to "0x6:abnormal" of API parameter 2.

[0254] Exemplarily, if the first original message includes API parameter 1 "EMS_PortConnectStatus", and the value of API parameter 1 "EMS_PortConnectStatus" is 1 indicating the unplug (unconnected) state, since "1:unplug" in Figure 4C corresponds to "0x0:off", the first conversion message includes the "VIU_BMS_ACChrgSt" signal, and the value of the "VIU_BMS_ACChrgSt" signal is 0x0 indicating the off (unplugged) state.

[0255] Exemplarily, if the first original message includes API parameter 1 "EPS_FltIncn" and API parameter 2 "EMS_ChargeSt", and the value of "EPS_FltIncn" is 3 indicating the plugin (connected) state and the value of "EMS_ChargeSt" is 0x4 indicating the heating (battery pack heating) state, since "3:plugin" in Figure 4C has no mapped state and "0x4:heating" corresponds to "0x5:preheat", the first conversion message includes the "VIU_BMS_ACChrgSt" signal, and the value of the "VIU_BMS_ACChrgSt" signal is 0x5 indicating the preheat (preheating) state.

[0256] The following example illustrates the mapping of states based on a preset ratio:

[0257] In one implementation, the number of the at least one second state is greater than the number of the at least one first state, that is, the granularity of the fault level division of the first API parameter is finer than the granularity of the fault level division of the first signal, then the preset ratio is obtained based on the number of the at least one first state and the number of the at least one second state, including: the preset ratio is the ratio of the number of the at least one first state to the number of the at least one second state.

[0258] It can be understood that mapping based on a preset ratio indicates that at least one first state of the first signal and at least one second state of the first API parameter can be quantified, for example, both can be quantifications of fault levels.

[0259] For example, the above-mentioned “VIU_BMS_FaultLevel” signal corresponds to the “HvBattFltSt” parameter, that is, the first signal is “VIU_BMS_FaultLevel”, and the first API parameter is the “HvBattFltSt” parameter.

[0260] Refer to Figure 5, which is a mapping diagram of another state provided by an embodiment of the present application. In Figure 5, at least one first state of the "VIU_BMS_FaultLevel" signal includes a normal state indicated by 0x0, a level 1 state indicated by 0x1, a level 2 state indicated by 0x2, a level 3 state indicated by 0x3, a level 4 state indicated by 0x4, a level 5 state indicated by 0x5, a level 6 state indicated by 0x6, and a reserved state indicated by 0x7-0xF; at least one second state of the "HvBattFltSt" parameter includes a no_fault state indicated by 0 The fault_level 1 status indicated by 1, the fault_level 2 status indicated by 2, the fault_level 3 status indicated by 3, the fault_level 4 status indicated by 4, the fault_level 5 status indicated by 5, the fault_level 6 status indicated by 6, the fault_level 7 status indicated by 7, the fault_level 8 status indicated by 8, and the invalid status indicated by 0xFF.

[0261] In Figure 5, it can be seen that the number of at least one second state of the "HvBattFltSt" parameter is greater than the number of at least one first state of the "VIU_BMS_FaultLevel" signal, that is, the fault level division granularity of the "HvBattFltSt" parameter is finer than the fault level division granularity of the "VIU_BMS_FaultLevel" signal. In order to ensure that the original information of the "HvBattFltSt" parameter is not lost, so that each fault level of the "HvBattFltSt" parameter can correspond to a fault level of the "VIU_BMS_FaultLevel" signal, mapping can be performed based on a preset ratio. In Figure 5, assuming that the fault severity from "fault_level1" to "fault_level8" and the fault severity from "level1" to "level6" are both increasing step by step, the preset ratio can be the ratio of the number of at least one first state to the number of at least one second state, that is, In this case, the mapping process between the 8 fault levels of the "HvBattFltSt" parameter and the 6 fault levels of the "VIU_BMS_FaultLevel" signal can be referred to as shown in the following Table 1.

[0262] Refer to Table 1, which is a table showing the correspondence between the fault level of the "HvBattFltSt" parameter and the fault level of the "VIU_BMS_FaultLevel" signal. Specifically, Table 1 shows the correspondence between the fault level as input (i.e., the fault level of the API parameter "HvBattFltSt"), the level value multiplied by the preset ratio, the level conversion value, and the fault level as output (i.e., the fault level of the CAN signal "VIU_BMS_FaultLevel"), where the preset ratio is Taking the correspondence of "1-0.75-1-1" in Table 1 as an example, it shows that when the input fault level is fault level 1 of "HvBattFltSt", the level value after multiplying by the preset ratio is 0.75, and 0.75 is rounded off to obtain a level conversion value of 1. That is, the fault level 1 of the "HvBattFltSt" parameter corresponds to the fault level 1 of the "VIU_BMS_FaultLevel" signal. It can be understood that the other correspondences in Table 1 can refer to the description of the correspondence of "1-0.75-1-1", which will not be repeated here.

[0263] Table 1

[0264]

[0265] The calculation method of the grade conversion value in Table 1 takes "rounding off" as an example, but the calculation method of the grade conversion value is not limited to rounding off. In some possible embodiments, if the grade value after multiplying by the preset ratio is a non-integer value, the grade conversion value can be obtained by rounding up.

[0266] It can be understood that the above Table 1 is only used as an example to reflect the correspondence between the fault level as input, the level value multiplied by the preset ratio, the level conversion value and the fault level as output. In actual applications, the text content and storage method of the correspondence can also be in other forms, which are not specifically limited here.

[0267] Therefore, based on the mapping based on the preset ratio shown in Table 1, it can be known that the "0:no_fault" of the "HvBattFltSt" parameter corresponds to the "0x0:normal" of the "VIU_BMS_FaultLevel" signal, the "1:fault_level1" of the "HvBattFltSt" parameter corresponds to the "0x1:level1" of the "VIU_BMS_FaultLevel" signal, the "2:fault_level2" parameter of the "HvBattFltSt" parameter corresponds to the "0x2:level2" of the "VIU_BMS_FaultLevel" signal, the "3:fault_level3" of the HvBattFltSt parameter corresponds to the "0x2:level2" of the "VIU_BMS_FaultLevel" signal, and the "4:fault_level5" of the HvBattFltSt parameter corresponds to the "0x2:level5" of the "VIU_BMS_FaultLevel" signal. "t_level4" of the "VIU_BMS_FaultLevel" signal corresponds to "0x2:level2", "5:fault_level5" of the "HvBattFltSt" parameter corresponds to "0x4:level4" of the "VIU_BMS_FaultLevel" signal, "6:fault_level6" of the "HvBattFltSt" parameter corresponds to "0x5:level5" of the "VIU_BMS_FaultLevel" signal, "7:fault_level7" of the "HvBattFltSt" parameter corresponds to "0x5:level5" of the "VIU_BMS_FaultLevel" signal, and "8:fault_level8" of the "HvBattFltSt" parameter corresponds to "0x6:level6" of the "VIU_BMS_FaultLevel" signal.

[0268] In some possible embodiments, the number of the at least one second state may be less than the number of the at least one first state, that is, the range granularity of the second state of the first API parameter is coarser than the quantization granularity of the first state of the first signal. In this case, the preset ratio is still the ratio of the number of the at least one second state to the number of the at least one first state. It will be understood that when the range granularity of the second state of the first API parameter is the same as the quantization granularity of the first state of the first signal, the preset ratio is 1.

[0269] S303: Send a first message.

[0270] In one implementation, sending the first message includes: when the first message is a first conversion message, sending the first message to the first control device.

[0271] Here, the first message is a first conversion message, which means that each signal in the first valid signal belongs to the first message. Each signal in the first valid signal has a corresponding API parameter in the first original message. In other words, each signal in the first valid signal is obtained by mapping based on the corresponding API parameter in the first original message.

[0272] In one implementation, sending the first message includes sending the first message to a target device in the first vehicle, where the target device is equipped with a communication protocol stack. In this case, after receiving the first message, the target device then sends the first converted message to the first control device. For details regarding this embodiment, please refer to the description related to FIG. 6 below and will not be repeated here.

[0273] Furthermore, when the first message is sent to the target device of the first vehicle, the first converted message also includes a first wired message, wherein the first wired message is obtained through signal routing reorganization based on the wired signal in the first vehicle, the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

[0274] Here, at least one second signal in the first valid signal is associated with the first wired message, which means that at least one second signal in the first valid signal belongs to the first wired message. It can be seen that in this case, part of the first valid signal comes from the first message, and part of the signal comes from the first wired message. In other words, the first valid signal is obtained in two ways. Specifically, the signal from the first message in the first valid signal is obtained by mapping and converting based on the corresponding API parameters, and the signal from the first wired message in the first valid signal is obtained by signal routing and reorganization of the in-vehicle wired signal.

[0275] It is understandable that the type of the first wired message is the same as the type of the first converted message. Detailed descriptions of the first message type being the same as the type of the first converted message in S302 are available and will not be repeated here.

[0276] It can be seen that by implementing the embodiments of the present application, different types of original messages can be provided with a unified or fixed message format according to the communication protocol supported by the target receiving end. This not only shields the differences between multiple different input signal sources, but also realizes the full quantization and platformization of the output messages, which is conducive to the reuse of messages across vehicles.

[0277] In some possible embodiments, the above-mentioned message conversion method can be applicable to different vehicles, such as a first vehicle and a second vehicle, wherein the characteristics of the first vehicle are different from those of the second vehicle, for example, the model of the first vehicle is different from that of the second vehicle.

[0278] The following specifically describes how the message conversion method provided in the embodiments of the present application can achieve cross-vehicle reuse:

[0279] When the conversion device is deployed on the first vehicle, the conversion device obtains the first original message of the first vehicle, generates a first message based on the first original message, the first message is related to the characteristics of the first vehicle, and the first message is included in the first conversion message; sends the first message; wherein, the first conversion message includes N signals (N is an integer greater than 1), and the N signals include a first valid signal and a first invalid signal, the first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle, the characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle, and at least one first signal in the first valid signals is associated with the first message.

[0280] When the conversion device is deployed on the second vehicle, the conversion device obtains the original message of the second vehicle, generates a second message based on the second original message, the second message is related to the characteristics of the second vehicle, and the second message is included in the second conversion message; sends the second message; wherein, the second conversion message includes the above-mentioned N signals, the N signals include a second valid signal and a second invalid signal, the second valid signal corresponds to the characteristics of the second vehicle, the second invalid signal is a signal corresponding to the characteristics of other vehicles except the second vehicle, the characteristics of other vehicles except the second vehicle are different from the characteristics of the second vehicle, at least one signal in the second valid signal is associated with the second message, there is at least one different signal between the first valid signal and the second valid signal, and there is at least one different signal between the first invalid signal and the second invalid signal.

[0281] Exemplarily, signal 1 is one of the N signals mentioned above, wherein signal 1 is a first valid signal and signal 1 is a second invalid signal.

[0282] As can be seen, when the conversion device is deployed on different vehicles, the conversion message contains the same signals, manifested by the same signal names and number. For example, the first conversion message includes N signals, and the second conversion message also includes these N signals. When used on different vehicles, the N signals corresponding to the vehicle's characteristics can be designated as valid signals for that vehicle, while signals not used by that vehicle can be designated as invalid signals for that vehicle. This provides a unified conversion message format for different receiving ends, enabling cross-vehicle reuse.

[0283] See Figure 6, which is a flow chart of another message conversion method provided by an embodiment of the present application. The method is applied to a communication system consisting of a conversion device, a target device, and a first control device. The conversion device, the target device, and the first control device are deployed on a first vehicle; the conversion device and the target device are located on the same domain controller or the same vehicle integration unit; the conversion device and the first control device are located on different domain controllers or different vehicle integration units; and a communication protocol stack is deployed on the target device. The method includes but is not limited to the following steps:

[0284] S601: The conversion device sends a first message to the target device.

[0285] The first message is generated by the conversion device based on the first original message of the first vehicle, and the first message is related to the characteristics of the first vehicle. This step can be specifically referred to the description of S301 and S302 in the embodiment of Figure 3, and will not be repeated here.

[0286] Correspondingly, the target device receives the first message sent by the conversion device.

[0287] S602: The target device obtains a first converted message according to the first wired message and the first message.

[0288] The first conversion message includes multiple signals, including a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of vehicles other than the first vehicle, and the characteristics of the vehicles other than the first vehicle are different from the characteristics of the first vehicle. At least one first signal in the first valid signal is associated with the first message, and at least one second signal in the first valid signal is associated with the first wired message, and the first wired message is related to the characteristics of the first vehicle. For the description of the first message and the first wired message, please refer to the relevant description of the corresponding content in Figure 3, and will not be repeated here.

[0289] Here, the multiple signals in the first conversion message are the maximum set of signals corresponding to the characteristics of multiple vehicles. For example, the multiple signals in the first conversion message may be pre-obtained by the target device from at least one original equipment manufacturer (OEM). In some possible embodiments, the target device may also obtain the correspondence between each vehicle characteristic and the vehicle's valid signals from the OEM.

[0290] Here, the first wired message can be obtained by the target device through signal routing reorganization of the in-vehicle wired signal in the first vehicle based on the characteristics of the first vehicle. The first wired message can be a CAN message, a LIN message, a FlexRay message, or other in-vehicle wired signal type message.

[0291] Here, the type of the first message, the type of the first wired message, and the type of the first converted message are the same, and the type of the first message, the type of the first wired message, and the type of the first converted message are related to the communication protocol supported by the first control device. For example, if the first control device only supports the CAN communication protocol, the type of the first message is CAN, the type of the first wired message is also CAN, and the type of the first converted message is also CAN.

[0292] Exemplarily, the process for acquiring the first wired message may be as follows: assuming that the first valid signal includes signal 1, signal 2, signal 3, and signal 4, wherein signal 1 and signal 2 belong to the first message, but the first message does not include signal 3 and signal 4. The target device may acquire signal 3 and signal 4 by signal routing reorganization. Specifically, the target device acquires CAN message 1 via the CAN bus to which it is connected, and acquires LIN message 1 via the LIN bus to which it is connected. CAN message 1 includes signal 3, and LIN message 1 includes signal 4. The target device performs signal routing reorganization on CAN message 1 and LIN message 1 to acquire the first wired message, wherein the first wired message includes signal 3 and signal 4. Furthermore, the target device acquires a first converted message based on the first message and the first wired message. The target device may acquire signal 1 and signal 2 from the first message, and acquire signal 3 and signal 4 from the first wired message.

[0293] In some possible embodiments, both Signal 3 and Signal 4 may be included in LIN message 1. In this case, the signal routing reorganization operation may be performed only on LIN message 1 to obtain the first wired message. Of course, Signal 3 and Signal 4 may also be included in messages of other in-vehicle wired signal types, which are not specifically limited here.

[0294] S603: The target device sends a first conversion message to the first control device.

[0295] S604: The first control device receives the first conversion message.

[0296] As can be seen, in implementing the embodiments of the present application, the conversion device can be used only to convert the original message of the API message type based on the characteristics of the first vehicle to obtain a first message, and then send the first message to a target device deployed with a communication protocol stack. The target device can combine the first message and the first wired message obtained based on signal routing reorganization to output a communication message with a unified format. This not only shields the differences between multiple different input signal sources, but also achieves full quantization and platformization of the output message, which is conducive to cross-vehicle message reuse.

[0297] Refer to Figure 7, which is a schematic diagram of a scene in a first vehicle provided in an embodiment of the present application. Figure 7 shows the information transmission process between domain controller 1, domain controller 2, domain controller 3 and vehicle integration unit 1. For example, in Figure 7, the conversion device in the above embodiment is deployed on the vehicle integration unit 1, the message source end in the above embodiment can be deployed on at least one of the domain controller 1, domain controller 2 and vehicle integration unit 1, and the first control device in the above embodiment can be deployed on the domain controller 3. For example, the first control device can be a microcontroller unit (MCU) in Figure 7.

[0298] Figure 7 shows three signal sources that can be used as input, namely signal source 1, signal source 2 and signal source 3, where signal source 1 is the API message corresponding to the native service, signal source 2 is a wired message generated based on the in-vehicle wired signal (sent by the Legacy ECU hanging below), and signal source 3 is the API message corresponding to the service based on the in-vehicle wired signal (i.e., the Legacy ECU service). As can be seen from Figure 7, any one of the domain controller 1, domain controller 2 and vehicle integration unit 1 can provide at least one of these three signal sources. The communication paths corresponding to different signal sources may be different, and the communication paths may include, for example, at least one of the paths running the CAN protocol, the paths running SOME / IP, and the paths running CAN overETH.

[0299] Taking the vehicle integration unit 1 in Figure 7 as an example, the internal architecture of the vehicle integration unit 1 is specifically described: the bottom layer is the microcontroller abstraction layer (MCAL), above which the CAN protocol stack, SOME / IP, and TCP / IP protocol stacks are deployed. Above the protocol stack is the protocol data unit router (PduR) layer, above which the runtime environment (RTE) layer is located. Above the RTE layer is the application layer where the legacy ECU services, conversion devices, and native services are located. The internal architecture of domain controllers 1, 2, and 3 in Figure 7 can be referred to the relevant description of the vehicle integration unit 1 and will not be repeated here.

[0300] In one implementation, the signal sources (or message sources) acquired by the conversion device come from different message source ends.

[0301] For example, the API message 1 provided by the LegacyECU service or native service on domain controller 1 is transmitted to the conversion device in the vehicle integration unit 1 via SOME / IP, and the API message 2 provided by the native service or LegacyECU service on domain controller 2 is transmitted to the conversion device in the vehicle integration unit 1 via SOME / IP. The conversion device converts the API message 1 and the API message 2 to obtain a first message, and when the first message is a first converted message, it sends the first message to the MCU in the domain controller 3 via the CAN bus. The message conversion process can refer to the description of Figure 3 above. In some possible embodiments, if the first message is not the first converted message, the conversion device can also send the first message to the lower-layer device. Here, the lower-layer device can be, for example, the device where the CAN protocol stack is located.

[0302] For another example, API message 1 provided by the LegacyECU service on domain controller 1 is transmitted via SOME / IP to the conversion device in vehicle integration unit 1. API message 2 provided by the native service on domain controller 1 is also transmitted via SOME / IP to the conversion device in vehicle integration unit 1. Accordingly, the conversion device converts API message 1 and API message 2 to obtain a first message. If the first message is a first converted message, the first message is sent via the CAN bus to the MCU in domain controller 3. In some possible embodiments, if the first message is not a first converted message, the conversion device may also send the first message to a lower-layer device.

[0303] For another example, API message 1 provided by the LegacyECU service on vehicle integration unit 1 is transmitted to the conversion device, and API message 2 provided by the native service on vehicle integration unit 1 is transmitted to the conversion device. Accordingly, the conversion device converts API message 1 and API message 2 to obtain a first message. If the first message is a first converted message, the first message is sent to the MCU in domain controller 3 via the CAN bus. In some possible embodiments, if the first message is not a first converted message, the conversion device may also send the first message to a lower-layer device.

[0304] In one implementation, the signal sources (or message sources) acquired by the conversion device come from the same message source end.

[0305] For example, API message 1 provided by the LegacyECU service on domain controller 1 is transmitted via SOME / IP to a conversion device in vehicle integration unit 1. API message 2 provided by the LegacyECU service on domain controller 1 is also transmitted via SOME / IP to a conversion device in vehicle integration unit 1. Accordingly, the conversion device converts API message 1 and API message 2 to obtain a first message. If the first message is a first converted message, the first message is sent via the CAN bus to the MCU in domain controller 3. In some possible embodiments, if the first message is not a first converted message, the conversion device may also send the first message to a lower-layer device.

[0306] In some possible embodiments, in FIG7 , if a lower-layer device in the vehicle integrated unit 1 (e.g., a device where the CAN protocol stack is located) receives a first message sent by the application layer, the lower-layer device may also receive at least one signal source. The lower-layer device may first reorganize the at least one signal source through signal routing to obtain a first wired message, then obtain a first conversion message based on the first message and the first wired message, and send the first conversion message to the MCU in the domain controller 3 through the CAN bus, wherein the at least one signal source includes at least one of the following wired messages:

[0307] At least one wired message transmitted by the LegacyECUs connected to the domain controller 1 via the CAN bus;

[0308] At least one wired message transmitted by the Legacy ECUs connected to or above the domain controller 2 via the CAN bus or CAN over ETH; and

[0309] The LegacyECUs mounted above and below the vehicle integration unit 1 transmit at least one wired message via the CAN bus.

[0310] 8A is a schematic diagram of a conversion device according to an embodiment of the present application, wherein the conversion device 30 includes an acquisition unit 310, a processing unit 312, and a sending unit 314. The conversion device 30 can be implemented by hardware, software, or a combination of hardware and software.

[0311] Among them, the acquisition unit 310 is used to obtain the first original message of the first vehicle; the processing unit 312 is used to generate a first message based on the first original message, the first message is related to the characteristics of the first vehicle, and the first message is included in the first conversion message; the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of the other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal in the first valid signal is associated with the first message; the sending unit 314 is used to send the first message.

[0312] The conversion device 30 may be used to implement the method described in the embodiment of Figure 3. In the embodiment of Figure 3, the acquisition unit 310 may be used to execute S301, and the processing unit 312 and the sending unit 314 may be used to execute S302.

[0313] 8B is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, wherein the communication device 40 includes a receiving unit 410. The communication device 40 can be implemented by hardware, software, or a combination of hardware and software.

[0314] In one implementation, the communication device 40 may be the first control device in the embodiment of FIG6 . The receiving unit 410 is configured to receive a first converted message, the first converted message including a first message, the first message being generated based on a first original message of a first vehicle, the first message being associated with a characteristic of the first vehicle; wherein the first converted message includes a plurality of signals, the plurality of signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristic of the first vehicle, the first invalid signal being a signal corresponding to a characteristic of a vehicle other than the first vehicle, the characteristics of the vehicle other than the first vehicle being different from the characteristics of the first vehicle, and at least one of the first valid signals being associated with the first message.

[0315] In this case, the communication device 40 may be used to execute the method on the first control device side in the embodiment of FIG. 6 , and the receiving unit 410 may be used to execute S604 in the embodiment of FIG. 6 .

[0316] In another implementation, the communication device 40 further includes a processing unit 412 and a sending unit 414. In this case, the receiving unit 410 is configured to receive a first message, the first message being generated based on a first original message of a first vehicle and being associated with a characteristic of the first vehicle; the processing unit 412 is configured to obtain a first converted message based on the first wired message and the first message, wherein the first wired message is obtained by signal routing reorganization based on wired signals within the first vehicle and is associated with the characteristic of the first vehicle; the first converted message includes multiple signals, the multiple signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristic of the first vehicle, the first invalid signal being a signal corresponding to the characteristic of a vehicle other than the first vehicle, the characteristic of the vehicle other than the first vehicle being different from the characteristic of the first vehicle, at least one first signal in the first valid signal being associated with the first message, and at least one second signal in the first valid signal being associated with the first wired message; and the sending unit 414 is configured to send the first converted message to a first control device of the first vehicle.

[0317] In this case, the communication device 40 may be used to execute the method on the target device side in the embodiment of FIG. 6 . Specifically, the receiving unit 410 may be used to execute S601 , the processing unit 412 may be used to execute S602 , and the sending unit 414 may be used to execute S603 .

[0318] It should be understood that the division of the various units in the above devices (such as the device shown in Figure 8A or Figure 8B) is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the various units of the device, where the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by software called by the processor, and the rest by hardware circuits.

[0319] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the processor loads a configuration document to implement the process of hardware circuit configuration, which can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0320] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0321] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0322] Referring to Figure 9 , which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application, as shown in Figure 9 , the communication device 50 includes a processor 501 , a communication interface 502 , a memory 503 , and a bus 504 . The processor 501 , the memory 503 , and the communication interface 502 communicate with each other via the bus 504 .

[0323] It should be understood that the present application does not limit the number of processors and memories in the communication device 50 .

[0324] In one implementation, the communication device 50 may be a vehicle, or the communication device 50 may be a device within the vehicle. The device may be, for example, a vehicle integrated unit or a domain controller, where the domain controller may be, for example, a VDC, an MDC, or a CDC, etc. The communication device 50 may also be a component within the above-mentioned device, and the component may be, for example, at least one of a chip, an integrated circuit, etc.

[0325] Bus 504 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG9 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 504 may include a path for transmitting information between various components of communication device 50 (e.g., memory 503, processor 501, and communication interface 502).

[0326] The processor 501 can refer to the relevant description of the processor in the above embodiment, which will not be repeated here.

[0327] Memory 503 provides storage space for data such as the operating system and computer programs. Memory 503 can be one or a combination of random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM). Memory 503 can exist independently or be integrated within processor 501.

[0328] The communication interface 502 can be used to provide information input or output for the processor 501. Alternatively, the communication interface 502 can be used to receive data transmitted externally and / or transmit data externally. It can be a wired link interface such as an Ethernet cable, or a wireless link interface (such as Wi-Fi, Bluetooth, general wireless transmission, etc.). Alternatively, the communication interface 502 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) or a receiver coupled to the interface.

[0329] The processor 501 in the communication device 50 is used to read the computer program stored in the memory 503 to execute the aforementioned method, such as the method described in FIG. 3 or FIG. 6 .

[0330] In one possible design, the communication device 50 may be one or more modules in an execution body for executing the method shown in FIG. 3 , and the processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0331] Acquire a first original message of the first vehicle by the acquisition unit 310;

[0332] A first message is generated based on the first original message, the first message being associated with a characteristic of the first vehicle and being included in a first converted message; the first converted message comprising a plurality of signals, the plurality of signals comprising a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristic of the first vehicle, the first invalid signal being a signal corresponding to a characteristic of a vehicle other than the first vehicle, the characteristics of the vehicle other than the first vehicle being different from the characteristics of the first vehicle, and at least one first signal among the first valid signals being associated with the first message;

[0333] The first message is sent by the sending unit 314 .

[0334] In one possible design, the communication device 50 may be one or more modules in an execution entity (e.g., a first control device) that executes the method shown in FIG6 , and the processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0335] A first conversion message is received through the receiving unit 410, the first conversion message including a first message, the first message being generated based on the first original message of the first vehicle, and the first message being related to the characteristics of the first vehicle; wherein the first conversion message includes multiple signals, the multiple signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristics of the first vehicle, the first invalid signal being a signal corresponding to the characteristics of vehicles other than the first vehicle, the characteristics of the vehicles other than the first vehicle being different from the characteristics of the first vehicle, and at least one first signal in the first valid signals is associated with the first message.

[0336] In one possible design, the communication device 50 may be one or more modules in an execution subject (e.g., a target device) that executes the method shown in FIG. 6 , and the processor 501 may be configured to read one or more computer programs stored in a memory to perform the following operations:

[0337] receiving, by the receiving unit 410, a first message generated based on a first original message of a first vehicle, the first message being associated with a feature of the first vehicle;

[0338] A first converted message is obtained based on the first wired message and the first message, wherein the first wired message is obtained by signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is associated with the characteristics of the first vehicle; the first converted message includes a plurality of signals, the plurality of signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristics of the first vehicle, the first invalid signal being a signal corresponding to the characteristics of a vehicle other than the first vehicle, the characteristics of the vehicle other than the first vehicle being different from the characteristics of the first vehicle, at least one first signal in the first valid signals being associated with the first message, and at least one second signal in the first valid signals being associated with the first wired message;

[0339] The first conversion message is sent to the first control device of the first vehicle via the sending unit 414 .

[0340] In the embodiments described above, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. In addition, in the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0341] It should be noted that, those skilled in the art can see that all or part of the steps in the various methods of the above embodiments can be completed by a program to instruct relevant hardware. The program can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0342] The technical solution of the present application may essentially or contribute to the part or all or part of the technical solution in the form of a software product. The computer program product is stored in a storage medium and includes a number of instructions for enabling a device (which may be a personal computer, a server, or a network device, a robot, a single-chip microcomputer, a chip, a robot, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.

Claims

1. A message conversion method, characterized in that: Applied to a conversion device, the method comprises: Obtaining a first original message of a first vehicle; generating a first message according to the first original message, wherein the first message is related to a feature of the first vehicle, and the first message is included in a first converted message; sending the first message; Among them, the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal among the first valid signals is associated with the first message.

2. The method according to claim 1, characterized in that The sending the first message includes: The first message is the first converted message, and the first message is sent to the first control device of the first vehicle; or The first message is sent to a target device of the first vehicle, where a communication protocol stack is deployed.

3. The method according to claim 2, characterized in that When the first message is sent to the target device, the first converted message also includes a first wired message, which is obtained by signal routing reorganization based on the wired signal in the first vehicle, and the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

4. The method according to any one of claims 1 to 3, characterized in that The first original message includes at least one message, and a type of the first original message includes at least one of an application programming interface (API) message and an in-vehicle wired signal. The API message includes at least one of the following types: API messages corresponding to services based on the scalable service-oriented middleware SOME / IP running on IP; and API messages corresponding to services based on in-vehicle wired signals.

5. The method according to claim 4, characterized in that The first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions: The first API message and the second API message correspond to the same service; or, The first API message and the second API message correspond to different services.

6. The method according to claim 5, characterized in that The obtaining of the first original message of the first vehicle includes: receiving the first API message from a second control device of the first vehicle; The second API message is received from a third control device of the first vehicle.

7. The method according to any one of claims 1 to 5, characterized in that The obtaining of the first original message of the first vehicle includes: The first original message is received from a fourth control device of the first vehicle.

8. The method according to any one of claims 1 to 7, characterized in that The type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

9. The method according to claim 8, characterized in that The first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions: Mapping is performed based on the similarity between the physical meanings of states; and The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

10. The method according to any one of claims 1 to 9, characterized in that The type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

11. The method according to any one of claims 1 to 10, characterized in that The conversion device is disposed in any one of the following components of the first vehicle: Vehicle integrated unit VIU; Vehicle domain controller (VDC); Cockpit Domain Controller (CDC); or Mobile Data Center MDC.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: Obtaining a second original message of a second vehicle; generating a second message according to the second original message, wherein the second message is related to characteristics of the second vehicle, and the second message is included in a second converted message; sending the second message; The second conversion message includes the multiple signals, and the multiple signals include a second valid signal and a second invalid signal. The second valid signal corresponds to the characteristics of the second vehicle, and the second invalid signal is a signal corresponding to the characteristics of other vehicles except the second vehicle. The characteristics of the other vehicles except the second vehicle are different from the characteristics of the second vehicle. At least one signal in the second valid signals is associated with the second message. There is at least one different signal between the first valid signal and the second valid signal, and there is at least one different signal between the first invalid signal and the second invalid signal.

13. A message receiving method, characterized in that: The method comprises: receiving a first converted message, the first converted message including a first message, the first message being generated based on a first original message of a first vehicle, the first message being related to a characteristic of the first vehicle; Among them, the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal among the first valid signals is associated with the first message.

14. The method according to claim 13, characterized in that The receiving of the first conversion message includes: The first message is the first conversion message, and the first conversion message is received from the conversion device of the first vehicle; or, The first converted message is received from a target device of the first vehicle, where a communication protocol stack is deployed.

15. The method according to claim 14, characterized in that In the case of receiving the first converted message from the target device, the first converted message also includes a first wired message, which is obtained by signal routing reorganization based on the wired signal in the first vehicle, the first wired message is related to the characteristics of the first vehicle, and at least one second signal in the first valid signal is associated with the first wired message.

16. The method according to any one of claims 13 to 15, characterized in that: The first original message includes at least one message, and a type of the first original message includes at least one of an application programming interface (API) message and an in-vehicle wired signal. The API message includes at least one of the following types: API messages corresponding to services based on the scalable service-oriented middleware SOME / IP running on IP; and API messages corresponding to services based on in-vehicle wired signals.

17. The method according to claim 16, characterized in that The first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions: The first API message and the second API message correspond to the same service; or, The first API message and the second API message correspond to different services.

18. The method according to any one of claims 13 to 17, characterized in that: The type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

19. The method according to claim 18, characterized in that The first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions: Mapping is performed based on the similarity between the physical meanings of states; and The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

20. The method according to any one of claims 13 to 19, characterized in that: The type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

21. A message conversion method, characterized in that: The method comprises: receiving a first message, the first message being generated based on a first original message of a first vehicle, the first message being associated with a characteristic of the first vehicle; Obtaining a first converted message based on a first wired message and the first message, wherein the first wired message is obtained by signal routing reorganization based on a wired signal within the first vehicle, and the first wired message is associated with a characteristic of the first vehicle; the first converted message includes a plurality of signals, the plurality of signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristic of the first vehicle, the first invalid signal being a signal corresponding to a characteristic of a vehicle other than the first vehicle, the characteristics of the vehicle other than the first vehicle being different from the characteristics of the first vehicle, at least one first signal among the first valid signals being associated with the first message, and at least one second signal among the first valid signals being associated with the first wired message; The first conversion message is sent to a first control device of the first vehicle.

22. The method according to claim 21, characterized in that The first original message includes at least one message, and a type of the first original message includes at least one of an application programming interface (API) message and an in-vehicle wired signal. The API message includes at least one of the following types: API messages corresponding to services based on the scalable service-oriented middleware SOME / IP running on IP; and API messages corresponding to services based on in-vehicle wired signals.

23. The method according to claim 22, characterized in that The first original message includes a first API message and a second API message, and the first API message and the second API message meet any one of the following conditions: The first API message and the second API message correspond to the same service; or, The first API message and the second API message correspond to different services.

24. The method according to any one of claims 21 to 23, characterized in that The type of the first original message includes an application programming interface API message, and at least one first signal in the first valid signal corresponds to at least one API parameter in the first original message.

25. The method according to claim 24, characterized in that The first signal in the first valid signal includes at least one first state, the first API parameter in the first original message corresponds to the first signal, the first API parameter includes at least one second state, and a mapping rule between the at least one first state and the at least one second state satisfies at least one of the following conditions: Mapping is performed based on the similarity between the physical meanings of states; and The number of the at least one first state is different from the number of the at least one second state, and the mapping is performed based on a preset ratio, where the preset ratio is obtained according to the number of the at least one first state and the number of the at least one second state.

26. The method according to any one of claims 21 to 25, characterized in that The type of the first conversion message is an in-vehicle wired signal, and the first conversion message is any one of a controller area network (CAN) message, a local interconnect network (LIN) message, and a FlexRay message.

27. A message conversion device, characterized in that: The device comprises: an acquiring unit, configured to acquire a first original message of a first vehicle; a processing unit, configured to generate a first message based on the first original message, wherein the first message is related to a feature of the first vehicle, and the first message is included in a first converted message; a sending unit, configured to send the first message; Among them, the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal among the first valid signals is associated with the first message.

28. A message receiving device, characterized in that: The device comprises: a receiving unit, configured to receive a first converted message, the first converted message including a first message, the first message being generated based on a first original message of a first vehicle, the first message being related to a feature of the first vehicle; Among them, the first conversion message includes multiple signals, and the multiple signals include a first valid signal and a first invalid signal. The first valid signal corresponds to the characteristics of the first vehicle, and the first invalid signal is a signal corresponding to the characteristics of other vehicles except the first vehicle. The characteristics of other vehicles except the first vehicle are different from the characteristics of the first vehicle. At least one first signal among the first valid signals is associated with the first message.

29. A message conversion device, characterized in that: The device comprises: A receiving unit, configured to receive a first message, where the first message is generated based on a first original message of a first vehicle, and the first message is associated with a feature of the first vehicle; a processing unit configured to obtain a first converted message based on a first wired message and the first message, wherein the first wired message is obtained by signal routing reorganization based on wired signals within the first vehicle, and the first wired message is associated with characteristics of the first vehicle; the first converted message includes a plurality of signals, the plurality of signals including a first valid signal and a first invalid signal, the first valid signal corresponding to the characteristics of the first vehicle, the first invalid signal being a signal corresponding to characteristics of a vehicle other than the first vehicle, the characteristics of the vehicle other than the first vehicle being different from the characteristics of the first vehicle, at least one first signal among the first valid signals being associated with the first message, and at least one second signal among the first valid signals being associated with the first wired message; A sending unit is used to send the first conversion message to the first control device of the first vehicle.

30. A chip, characterized in that: The chip includes at least one processor and a communication interface; The communication interface is used to receive and / or send data, and / or, the communication interface is used to provide input and / or output for the processor; the at least one processor is used to implement the method according to any one of claims 1-12, or to implement the method according to any one of claims 13-20, or to implement the method according to any one of claims 21-26.

31. A vehicle, characterized in that: The vehicle includes at least one of a first device, a second device, and a third device, wherein the first device is used to execute the method according to any one of claims 1 to 12, the second device is used to execute the method according to any one of claims 13 to 20, and the third device is used to execute the method according to any one of claims 21 to 26.

32. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program instructions, and the program instructions are used to implement the method according to any one of claims 1 to 12, or to implement the method according to any one of claims 13 to 20, or to implement the method according to any one of claims 21 to 26.

33. A computer program product, which, when running on a processor, causes an apparatus to perform the method according to any one of claims 1 to 12, or causes an apparatus to perform the method according to any one of claims 13 to 20, or causes an apparatus to perform the method according to any one of claims 21 to 26.

Images