A cross-platform docking configuration method, device and equipment for engineering machinery vehicle data

Abstract

The present invention discloses a cross-platform docking configuration method, device and equipment for engineering machinery vehicle data, comprising: in response to a user's access selection of a target three-party vehicle networking system, each three-party protocol field under a target three-party protocol supported by the target three-party vehicle networking system and each own protocol field under an own protocol supported by the own vehicle networking system are displayed in association; in response to the target three-party protocol field and the target own protocol field selected by the user, a mapping pairing group consisting of the target three-party protocol field and the target own protocol field is established; in response to a conversion formula configured by the user for the mapping pairing group selection, the conversion formula is added to the matching mapping pairing group; in response to a configuration completion instruction of the user, each mapping pairing group is uploaded to the own vehicle networking system, so that the own vehicle networking system can access the engineering machinery vehicle data obtained from the target three-party vehicle networking system, without the need for a large amount of development work, thereby reducing the docking configuration cost and maintenance difficulty.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and in particular to a cross-platform docking configuration method, device and equipment for engineering machinery vehicle data. Background Art

[0002] As more and more construction machinery begins to introduce Internet of Vehicles systems, the demand for connecting different Internet of Vehicles systems is gradually increasing. Among them, the Internet of Vehicles system includes the host, telematics box (on-board T-BOX), application software and background system. The connection of Internet of Vehicles systems can include the connection between the new version of the Internet of Vehicles system and the old version of the Internet of Vehicles system of the same developer, as well as the connection between the Internet of Vehicles systems of different developers.

[0003] At present, due to the differences between vehicle-mounted T-BOXs from different developers or the same developer, the data protocols followed by different Internet of Vehicles systems are different. Therefore, a large number of logical judgments are usually embedded in the back-end code to convert the data transmitted by the third-party Internet of Vehicles system.

[0004] However, pre-embedding a large number of logical judgments in the back-end code requires a lot of development work, which makes it impossible to connect to multiple Internet of Vehicles systems developed by different developers in a short period of time, and makes subsequent maintenance difficult. Secondly, when connecting to multiple third-party Internet of Vehicles systems, version upgrades are often performed frequently due to modifications to the third-party Internet of Vehicles systems, resulting in a high degree of coupling between the Internet of Vehicles systems, which in turn affects the smoothness of the Internet of Vehicles systems. Summary of the invention

[0005] The present invention provides a method, device and equipment for cross-platform docking configuration of engineering machinery vehicle data, which solves the problem that the existing hard-coded development method requires a lot of development work, resulting in a long construction period and difficult maintenance. The cross-platform docking configuration of engineering machinery vehicle data can be dynamically performed without the need for development work, thereby shortening the construction period, reducing the cross-platform docking cost of engineering machinery vehicle data and the subsequent maintenance difficulty.

[0006] In a first aspect, an embodiment of the present invention provides a cross-platform docking configuration method for engineering machinery vehicle data, which is executed by a front-end page adapted to the own vehicle networking system, and the method includes: in response to a user's access selection of a target three-party vehicle networking system, obtaining from the own vehicle networking system each three-party protocol field under a target three-party protocol supported by the target three-party vehicle networking system, and each own protocol field under the own protocol supported by the own vehicle networking system; displaying each three-party protocol field under the target three-party protocol and the own protocol field under the own protocol in association; in response to the target three-party protocol field and the target own protocol field selected by the user under at least one pairing selection, establishing a mapping pairing group consisting of at least one group of target three-party protocol fields and target own protocol fields; in response to a user selecting a conversion formula configured for at least one group of mapping pairing groups, adding the conversion formula to the matching mapping pairing group; in response to a configuration completion instruction of the user, uploading each established mapping pairing group as a protocol mapping configuration of the target three-party vehicle networking system to the own vehicle networking system, so that the own vehicle networking system can access the engineering machinery vehicle data obtained from the target three-party vehicle networking system according to the protocol mapping configuration.

[0007] Optionally, after the three-party protocol fields under the target three-party protocol and the own protocol fields under the own protocol are displayed in association, it also includes: after the protocol type of the target three-party protocol is displayed to the user, in response to the data receiving frequency configured by the user for the target three-party protocol, constructing data frequency modulation information; in response to the user's configuration completion instruction, uploading the established mapping pairing groups as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own Internet of Vehicles system, further including: in response to the user's configuration completion instruction, uploading the established mapping pairing groups and the data frequency modulation information together as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own Internet of Vehicles system.

[0008] In the second aspect, an embodiment of the present invention provides a cross-platform docking method for construction machinery vehicle data, which is executed by one's own vehicle networking system, and the method includes: receiving construction machinery vehicle data to be connected provided by the target three-party vehicle networking system, and obtaining each mapping pairing group in the locally stored protocol mapping configuration corresponding to the target three-party vehicle networking system; wherein the protocol mapping configuration is generated by configuring the cross-platform docking configuration method for construction machinery vehicle data; according to the mapping relationship between the three-party protocol field in the target three-party vehicle networking system defined in each mapping pairing group and the one's own protocol field in the one's own vehicle networking system, the construction machinery vehicle data to be connected is converted into data adapted to one's own vehicle networking system.

[0009] Optionally, according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system, including: according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, and the conversion formula, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system.

[0010] Optionally, according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, and the conversion formula, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system, including: according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, determining the engineering machinery vehicle data to be processed corresponding to the engineering machinery vehicle data to be connected; according to the conversion formula configured in each mapping pairing group, converting the engineering machinery vehicle data to be processed into data adapted to the own vehicle networking system.

[0011] Optionally, receiving the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system includes: obtaining data frequency modulation information in a locally stored protocol mapping configuration corresponding to the target third-party Internet of Vehicles system; and receiving the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system according to a data receiving frequency defined in the data frequency modulation information and corresponding to the target third-party protocol supported by the target third-party Internet of Vehicles system.

[0012] In a third aspect, an embodiment of the present invention further provides a cross-platform docking configuration device for engineering machinery vehicle data, which is executed by a front-end page adapted to the own vehicle networking system, and the device includes: a protocol field acquisition module, which is used to respond to the user's access selection of the target three-party vehicle networking system, and obtain from the own vehicle networking system each three-party protocol field under the target three-party protocol supported by the target three-party vehicle networking system, and each own protocol field under the own protocol supported by the own vehicle networking system; an association display module, which is used to associate and display each three-party protocol field under the target three-party protocol and the own protocol field under the own protocol; a mapping pairing group establishment module, which is used to respond to the user's selection of the target three-party vehicle networking system. The target three-party protocol field and the target own-party protocol field selected under at least one pairing selection are used to establish a mapping pairing group consisting of at least one group of target three-party protocol fields and target own-party protocol fields; a conversion formula adding module is used to respond to the conversion formula selected and configured by the user for at least one group of mapping pairing groups, and add the conversion formula to the matching mapping pairing group; a protocol mapping configuration module is used to respond to the user's configuration completion instruction, and upload the established mapping pairing groups as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own-party Internet of Vehicles system, so that the own-party Internet of Vehicles system can access the engineering machinery vehicle data obtained from the target three-party Internet of Vehicles system according to the protocol mapping configuration.

[0013] In the fourth aspect, an embodiment of the present invention also provides a cross-platform docking device for construction machinery vehicle data, which is executed by the own vehicle networking system, and the device includes: a mapping pairing group acquisition module, which is used to receive the construction machinery vehicle data to be connected provided by the target three-party vehicle networking system, and obtain each mapping pairing group in the locally stored protocol mapping configuration corresponding to the target three-party vehicle networking system; wherein the protocol mapping configuration is generated by the cross-platform docking configuration method for construction machinery vehicle data; a data docking module, which is used to convert the construction machinery vehicle data to be connected into data adapted to the own vehicle networking system according to the mapping relationship between the three-party protocol field in the target three-party vehicle networking system defined in each mapping pairing group and the own protocol field in the own vehicle networking system.

[0014] In a fifth aspect, an embodiment of the present invention further provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the cross-platform docking configuration method for engineering machinery vehicle data, or the cross-platform docking method for engineering machinery vehicle data provided in any embodiment of the present invention.

[0015] In a sixth aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer instructions, which are used to enable a processor to implement a cross-platform docking configuration method for engineering machinery vehicle data or a cross-platform docking method for engineering machinery vehicle data provided in any embodiment of the present invention when executed.

[0016] The technical solution of the present invention performs cross-platform docking configuration of engineering machinery vehicle data through a front-end page adapted to the own vehicle networking system, and can dynamically perform cross-platform docking configuration of engineering machinery vehicle data without the need for development work, thereby shortening the construction period and reducing the difficulty of subsequent maintenance. Specifically, since the technical solution of the present invention is executed by a front-end page adapted to the own vehicle networking system, no code development work is required. Therefore, when a new third-party vehicle networking system needs to be connected or a third-party vehicle networking system that has been connected needs to be modified, only the protocol mapping configuration needs to be added or modified, which greatly reduces the difficulty of maintenance, avoids excessive coupling of the vehicle networking system, and ensures the smoothness of the vehicle networking system.

[0017] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 It is a flowchart of a cross-platform docking configuration method for engineering machinery vehicle data provided according to the first embodiment of the present invention.

[0020] Figure 2 It is a flow chart of a cross-platform docking method for engineering machinery vehicle data provided according to the second embodiment of the present invention.

[0021] Figure 3 It is a structural schematic diagram of a cross-platform docking configuration device for engineering machinery vehicle data provided according to Embodiment 3 of the present invention.

[0022] Figure 4 It is a structural schematic diagram of a cross-platform docking device for engineering machinery vehicle data provided according to a fourth embodiment of the present invention.

[0023] Figure 5 It is a schematic diagram of the structure of an electronic device provided by Embodiment 5 of the present invention.

[0024] Reference numerals: electronic device 10 ; processor 11 ; read-only memory (ROM) 12 ; random access memory (RAM) 13 ; bus 14 ; input / output (I / O) interface 15 ; input unit 16 ; output unit 17 ; storage unit 18 ; communication unit 19 . DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] Embodiment 1

[0028] Figure 1 It is a flow chart of a cross-platform docking configuration method for engineering machinery vehicle data provided according to the first embodiment of the present invention. This embodiment can be applicable to the situation of cross-platform docking of engineering machinery vehicle data. The method can be executed by a cross-platform docking configuration device for engineering machinery vehicle data. The cross-platform docking configuration device for engineering machinery vehicle data can be implemented in the form of hardware and / or software. The cross-platform docking configuration device for engineering machinery vehicle data can be configured in an electronic device such as a computer.

[0029] like Figure 1 As shown, a cross-platform docking configuration method for engineering machinery vehicle data disclosed in this embodiment is executed by a front-end page adapted to the vehicle networking system of the own party, and the method includes S110-S150.

[0030] S110. In response to the user's access selection of the target third-party Internet of Vehicles system, obtaining from the own Internet of Vehicles system the various third-party protocol fields under the target third-party protocol supported by the target third-party Internet of Vehicles system and the various own protocol fields under the own protocol supported by the own Internet of Vehicles system.

[0031] In this embodiment, the target three-party Internet of Vehicles system and the own Internet of Vehicles system can be different versions of Internet of Vehicles systems developed by the same developer, or different Internet of Vehicles systems developed by different developers. The target three-party protocol can be the data assembly specification followed by the vehicle-mounted T-BOX configured in the target three-party Internet of Vehicles system, and the own three-party protocol can be the data assembly specification followed by the vehicle-mounted T-BOX configured in the own Internet of Vehicles system. The three-party protocol field is used to standardize the names of the target vehicle data collected by the target three-party Internet of Vehicles system, and the own protocol field is used to standardize the names of the own vehicle data collected by the own Internet of Vehicles system.

[0032] In this step, specifically, in response to the user's access selection of the target third-party Internet of Vehicles system on the access configuration page, after obtaining the target third-party protocol supported by the target third-party Internet of Vehicles system and the own protocol supported by the own Internet of Vehicles system through the own Internet of Vehicles system, the three-party protocol fields under the target three-party protocol and the own protocol fields under the own protocol can be obtained. In actual applications, users can choose to access one or more target third-party Internet of Vehicles systems on the access configuration page. The protocols supported by the Internet of Vehicles system can be jointly identified according to the protocol type and protocol version.

[0033] S120, the three-party agreement fields under the target three-party agreement and the own-party agreement fields under the own-party agreement are associated and displayed.

[0034] In this step, specifically, each tripartite agreement field under the target tripartite agreement and each own-party agreement field under the own-party agreement can be displayed to the user at the same time. Then, after displaying the data type of the own-party agreement field, the receiving frequency information can be constructed in response to the data receiving frequency configured by the user for the data type. Among them, the data type of the own-party agreement field can be multiple, such as a fault data type, an operating condition data type (such as vehicle speed), and a fixed parameter data type (such as a vehicle identification number).

[0035] Optionally, after the three-party agreement fields under the target three-party agreement and the own-party agreement fields under the own-party agreement are displayed in association, it also includes: after the protocol type of the target three-party agreement is displayed to the user, data frequency modulation information is constructed in response to the data receiving frequency configured by the user for the target three-party agreement.

[0036] Specifically, after displaying the protocol type of the target three-party protocol to the user, the data receiving frequency configured by the user for the target three-party protocol according to the protocol type can be obtained, and data frequency modulation information can be set for the target three-party protocol according to the data receiving frequency. Among them, the data frequency modulation information can be used to reflect the frequency at which the own vehicle networking system receives the engineering machinery vehicle data sent by the target three-party vehicle networking system that supports the target three-party protocol. The frequency at which the own vehicle networking system receives the engineering machinery vehicle data sent by the target three-party vehicle networking system can be different from the frequency at which the target three-party vehicle networking system sends the engineering machinery vehicle data.

[0037] The advantage of such a setting is that by setting different data frequency modulation information for different target three-party protocols, it avoids the situation where the target three-party Internet of Vehicles system has a high transmission frequency and completely relies on the transmission frequency of the target three-party Internet of Vehicles system to receive all data, causing data redundancy and thus affecting the business performance of the own platform. The own platform may be a platform equipped with the own Internet of Vehicles system.

[0038] S130. In response to the target three-party agreement field and the target own-party agreement field selected by the user in at least one pairing selection, establish a mapping pairing group consisting of at least one group of target three-party agreement fields and target own-party agreement fields.

[0039] In this step, specifically, after the three-party agreement fields under the target three-party agreement and the own-party agreement fields under the own-party agreement are displayed in association, the target own-party agreement fields selected by the user and the target three-party agreement fields paired with the target own-party agreement fields can be obtained. Then, a mapping pairing group can be established based on at least one set of paired target three-party agreement fields and target own-party agreement fields.

[0040] S140 . In response to the user selecting a configured transformation formula for at least one mapping pairing group, add the transformation formula to the matching mapping pairing group.

[0041] In this embodiment, there may be multiple conversion formulas, such as a formula for unit conversion, a formula for offset conversion, a formula for enumeration type conversion, and a formula for base conversion.

[0042] In this step, specifically, multiple conversion formulas can be constructed based on each tripartite agreement field and each own-party agreement field, and each conversion formula and each mapping pairing group can be displayed to the user. Then, based on the conversion formula selected and configured by the user for at least one mapping pairing group, the conversion formula can be added to the matching mapping pairing group.

[0043] S150. In response to the user's configuration completion instruction, the established mapping pairing groups are uploaded to the own vehicle networking system as the protocol mapping configuration of the target third-party vehicle networking system, so that the own vehicle networking system can access the construction machinery vehicle data obtained from the target third-party vehicle networking system according to the protocol mapping configuration.

[0044] In this step, specifically, after receiving the configuration completion instruction from the user, each established mapping pairing group can be directly uploaded to the own vehicle networking system as the protocol mapping configuration of the target three-party vehicle networking system. Alternatively, in response to the configuration completion instruction from the user, each established mapping pairing group and the data frequency modulation information can be uploaded to the own vehicle networking system as the protocol mapping configuration of the target three-party vehicle networking system. Alternatively, in response to the configuration completion instruction from the user, each established mapping pairing group and the frequency reception information corresponding to each mapping pairing group can be uploaded to the own vehicle networking system as the protocol mapping configuration of the target three-party vehicle networking system. Optionally, the protocol mapping configuration can be jointly identified according to the vehicle type, protocol type and protocol version of the own vehicle.

[0045] The technical solution of this embodiment is to obtain, from the own vehicle networking system, each three-party protocol field under the target three-party protocol supported by the target three-party vehicle networking system and each own protocol field under the own protocol supported by the own vehicle networking system in response to the user's access selection of the target three-party vehicle networking system; associate and display each three-party protocol field under the target three-party protocol and the own protocol field under the own protocol; establish a mapping pairing group consisting of at least one group of target three-party protocol fields and target own protocol fields in response to the target three-party protocol field and the target own protocol field selected by the user under at least one pairing selection; and select a mapping pairing group configured by the user for at least one group of mapping pairing groups. The conversion formula is added to the matching mapping pairing group; in response to the user's configuration completion instruction, the established mapping pairing groups are uploaded to the own vehicle networking system as the protocol mapping configuration of the target third-party vehicle networking system, so that the own vehicle networking system can access the construction machinery vehicle data obtained from the target third-party vehicle networking system according to the protocol mapping configuration. The technical means solves the problem that the existing hard-coded development method requires a lot of development work, resulting in a long construction period and difficult maintenance. The cross-platform docking configuration of the construction machinery vehicle data can be dynamically performed without the need for development work, shortening the construction period, reducing the cross-platform docking cost of the construction machinery vehicle data and the subsequent maintenance difficulty.

[0046] Embodiment 2

[0047] Figure 2It is a flow chart of a cross-platform docking method for engineering machinery vehicle data provided according to the second embodiment of the present invention. This embodiment can be applicable to the situation of cross-platform docking of engineering machinery vehicle data. The method can be executed by a cross-platform docking device for engineering machinery vehicle data. The cross-platform docking device for engineering machinery vehicle data can be implemented in the form of hardware and / or software. The cross-platform docking device for engineering machinery vehicle data can be configured in an electronic device such as a computer.

[0048] like Figure 2 As shown, a cross-platform docking method for engineering machinery vehicle data disclosed in this embodiment is executed by the vehicle networking system of the own party, and the method includes S210-S220.

[0049] S210, receiving the data of the engineering machinery vehicle to be connected provided by the target third-party vehicle networking system, and obtaining each mapping pairing group in the locally stored protocol mapping configuration corresponding to the target third-party vehicle networking system.

[0050] Among them, the protocol mapping configuration is generated by implementing the cross-platform docking configuration method of the engineering machinery vehicle data in the first embodiment. The engineering machinery vehicle data to be connected can be constructed based on the target vehicle data obtained by the target three-party vehicle networking system and the target three-party protocol. For example, assuming that the target vehicle data is the actual vehicle speed collected by the target three-party vehicle networking system, the engineering machinery vehicle data to be connected can be constructed based on the actual vehicle speed and the speed name and speed unit pre-defined in the target three-party protocol.

[0051] In this step, specifically, after the username and password are verified, the data of the engineering machinery vehicle to be connected provided by the target third-party Internet of Vehicles system can be obtained according to the Internet of Vehicles system name, Internet of Vehicles system access address, Internet of Vehicles system access method and delay processing information entered by the user in the access configuration page. Among them, there can be many ways to access the Internet of Vehicles system, such as Hypertext Transfer Protocol (HTTP), Transmission Control Protocol (TCP), Message Queuing Telemetry Transport (MQTT), etc. The delay processing information can be used to reflect whether the user needs his own Internet of Vehicles system to start delay processing. Optionally, when it is detected that part of the data of the engineering machinery vehicle to be connected is missing, the missing part can be automatically completed.

[0052] Then, according to the vehicle type, protocol type and protocol version, the protocol mapping configuration corresponding to the target three-party Internet of Vehicles system stored locally can be obtained, and further mapping pairing groups for processing the data of the engineering machinery vehicle to be connected can be obtained.

[0053] Optionally, receiving the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system includes: obtaining data frequency modulation information in a locally stored protocol mapping configuration corresponding to the target third-party Internet of Vehicles system; and receiving the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system according to a data receiving frequency defined in the data frequency modulation information and corresponding to the target third-party protocol supported by the target third-party Internet of Vehicles system.

[0054] Optionally, frequency reception information corresponding to each mapping configuration group can be obtained in the locally stored protocol mapping configuration corresponding to the target third-party Internet of Vehicles system; and the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system can be received according to the reception frequencies of different types of data defined in the frequency reception information.

[0055] It is worth noting that when receiving the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system according to the data frequency modulation information or frequency receiving information, the data of engineering machinery vehicles to be connected provided by the target third-party Internet of Vehicles system can be merged. For example, assuming that the target third-party Internet of Vehicles system sends the data of engineering machinery vehicles to be connected every 5 seconds, and the frequency of receiving the data of engineering machinery vehicles to be connected by the own Internet of Vehicles system is every 20 seconds, and the time when the target third-party Internet of Vehicles system first sends the data of engineering machinery vehicles to be connected is 0 seconds at a certain time and minute of a certain day, then only the data of engineering machinery vehicles to be connected sent by the target third-party Internet of Vehicles system at the 20th second at a certain time and minute of a certain day can be received, that is, the data of engineering machinery vehicles to be connected sent by the target third-party Internet of Vehicles system at the 5th and 10th seconds at a certain time and minute of a certain day can be refused.

[0056] S220. According to the mapping relationship between the three-party protocol field in the target three-party Internet of Vehicles system and the own protocol field in the own Internet of Vehicles system defined in each mapping pairing group, convert the data of the engineering machinery vehicle to be connected into data adapted to the own Internet of Vehicles system.

[0057] In this step, specifically, it can be determined whether there is a conversion formula in each mapping pairing group. If so, the data of the engineering machinery vehicle to be connected can be converted into data adapted to the own vehicle networking system according to the mapping relationship between the three-party protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, as well as the conversion formula. If not, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system only according to the mapping relationship between the three-party protocol fields in the target three-party vehicle networking system defined in each mapping pairing group and the own protocol fields in the own vehicle networking system.

[0058] Optionally, according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, and the conversion formula, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system, including: according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, determining the engineering machinery vehicle data to be processed corresponding to the engineering machinery vehicle data to be connected; according to the conversion formula configured in each mapping pairing group, converting the engineering machinery vehicle data to be processed into data adapted to the own vehicle networking system.

[0059] Specifically, after determining the engineering machinery vehicle data to be processed corresponding to the engineering machinery vehicle data to be connected based on the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, the engineering machinery vehicle data to be processed can be converted into data adapted to the own vehicle networking system according to the conversion formula configured in each mapping pairing group.

[0060] The technical solution of this embodiment is to receive the engineering machinery vehicle data to be connected provided by the target three-party Internet of Vehicles system, and obtain each mapping pairing group in the protocol mapping configuration corresponding to the target three-party Internet of Vehicles system stored locally; wherein the protocol mapping configuration is generated by implementing the cross-platform docking configuration method for engineering machinery vehicle data in one; according to the mapping relationship between the three-party protocol field in the target three-party Internet of Vehicles system and the own protocol field in the own Internet of Vehicles system defined in each mapping pairing group, a technical means is used to convert the engineering machinery vehicle data to be connected into data adapted to the own Internet of Vehicles system, which solves the problem that the existing hard-coded development method requires a lot of development work, resulting in a long construction period and difficult maintenance, and improves the docking efficiency of engineering machinery vehicle data.

[0061] Embodiment 3

[0062] Figure 3 It is a structural diagram of a cross-platform docking configuration device for engineering machinery vehicle data provided according to Example 3 of the present invention. This embodiment can be applied to the situation where front-end configuration is performed to achieve cross-platform docking of engineering machinery vehicle data. The cross-platform docking configuration device for engineering machinery vehicle data can be implemented in the form of hardware and / or software and can be configured in an electronic device.

[0063] like Figure 3As shown, the cross-platform docking configuration device for engineering machinery vehicle data disclosed in this embodiment is executed by a front-end page adapted to the own vehicle networking system, and the device includes: a protocol field acquisition module 31, which is used to respond to the user's access selection of the target three-party vehicle networking system, and obtain from the own vehicle networking system each three-party protocol field under the target three-party protocol supported by the target three-party vehicle networking system, and each own protocol field under the own protocol supported by the own vehicle networking system; an association display module 32, which is used to associate and display each three-party protocol field under the target three-party protocol and the own protocol field under the own protocol; a mapping pairing group establishment module 33, which is used to respond to the user's selection of access to at least one of the three-party vehicle networking systems; The target three-party protocol field and the target own-party protocol field selected under the second pairing selection are used to establish a mapping pairing group consisting of at least one group of target three-party protocol fields and target own-party protocol fields; a conversion formula adding module 34 is used to respond to the conversion formula selected and configured by the user for at least one group of mapping pairing groups, and add the conversion formula to the matching mapping pairing group; a protocol mapping configuration module 35 is used to respond to the user's configuration completion instruction, and upload the established mapping pairing groups as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own-party Internet of Vehicles system, so that the own-party Internet of Vehicles system can access the engineering machinery vehicle data obtained from the target three-party Internet of Vehicles system according to the protocol mapping configuration.

[0064] The technical solution in this embodiment, through the mutual cooperation of the protocol field acquisition module 31, the association display module 32, the mapping pairing group establishment module 33, the conversion formula addition module 34 and the protocol mapping configuration module 35, solves the problem that the existing hard-coded development method requires a lot of development work, resulting in a long construction period and difficult maintenance. It can dynamically perform cross-platform docking configuration of engineering machinery vehicle data without the need for development work, shortening the construction period, reducing the cross-platform docking cost of engineering machinery vehicle data and the subsequent maintenance difficulty.

[0065] Optionally, the device further includes a data frequency modulation module, which is used to construct data frequency modulation information in response to a data receiving frequency configured by the user for the target three-party protocol after displaying the protocol type of the target three-party protocol to the user.

[0066] Optionally, the protocol mapping configuration module 35 is specifically used to: in response to the user's configuration completion instruction, upload the established mapping pairing groups and data frequency modulation information as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own Internet of Vehicles system.

[0067] The cross-platform docking configuration device for engineering machinery vehicle data provided in the embodiment of the present invention can execute the cross-platform docking configuration method for engineering machinery vehicle data provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. For the contents not described in detail in this embodiment, please refer to the description in any method embodiment of this application.

[0068] Embodiment 4

[0069] Figure 4 It is a structural schematic diagram of a cross-platform docking device for engineering machinery vehicle data provided according to Example 4 of the present invention. This embodiment can be applied to the situation of cross-platform docking of engineering machinery vehicle data. The cross-platform docking device for engineering machinery vehicle data can be implemented in the form of hardware and / or software, and can be configured in an electronic device such as a computer.

[0070] like Figure 4 As shown, the cross-platform docking device for engineering machinery vehicle data disclosed in this embodiment is executed by the own vehicle networking system, and the device includes: a mapping pairing group acquisition module 41, which is used to receive the engineering machinery vehicle data to be connected provided by the target three-party vehicle networking system, and obtain each mapping pairing group in the protocol mapping configuration corresponding to the target three-party vehicle networking system stored locally; wherein the protocol mapping configuration is generated by the cross-platform docking configuration method for engineering machinery vehicle data; a data docking module 42, which is used to convert the engineering machinery vehicle data to be connected into data adapted to the own vehicle networking system according to the mapping relationship between the three-party protocol field in the target three-party vehicle networking system defined in each mapping pairing group and the own protocol field in the own vehicle networking system.

[0071] The technical solution in this embodiment solves the problem that the existing hard-coded development method requires a lot of development work, resulting in a long construction period and difficult maintenance, through the mutual cooperation of the mapping pairing group acquisition module 41 and the data docking module 42, and improves the docking efficiency of engineering machinery vehicle data.

[0072] Optionally, the data docking module 42 includes: a data conversion unit, which is used to convert the data of the engineering machinery vehicle to be connected into data adapted to the own vehicle networking system according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, as well as the conversion formula.

[0073] Optionally, the data conversion unit is specifically used to: determine the engineering machinery vehicle data to be processed corresponding to the engineering machinery vehicle data to be connected according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system; and convert the engineering machinery vehicle data to be processed into data adapted to the own vehicle networking system according to the conversion formula configured in each mapping pairing group.

[0074] Optionally, the mapping pairing group acquisition module 41 is specifically used to: obtain data frequency modulation information in the locally stored protocol mapping configuration corresponding to the target three-party Internet of Vehicles system; receive the engineering machinery vehicle data to be connected provided by the target three-party Internet of Vehicles system according to the data receiving frequency corresponding to the target three-party protocol supported by the target three-party Internet of Vehicles system defined in the data frequency modulation information.

[0075] The cross-platform docking device for engineering machinery vehicle data provided in the embodiment of the present invention can execute the cross-platform docking method for engineering machinery vehicle data provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. For the contents not described in detail in this embodiment, please refer to the description in any method embodiment of this application.

[0076] Embodiment 5

[0077] Figure 5 A schematic structural diagram of an electronic device 10 that can be used to implement an embodiment of the present invention is shown.

[0078] like Figure 5 As shown, the electronic device 10 includes at least one processor 11, and a memory such as ROM 12, RAM 13, etc., which is communicatively connected to the at least one processor 11, wherein the memory stores a computer program that can be executed by the at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in ROM 12 or the computer program loaded from the storage unit 18 to RAM 13. In RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, ROM 12 and RAM 13 are connected to each other via a bus 14. The I / O interface 15 is also connected to the bus 14.

[0079] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0080] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as a cross-platform docking configuration method for engineering machinery vehicle data, or a cross-platform docking method for engineering machinery vehicle data.

[0081] In some embodiments, the cross-platform docking configuration method for engineering machinery vehicle data, or the cross-platform docking method for engineering machinery vehicle data can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, the cross-platform docking configuration method for engineering machinery vehicle data described above, or one or more steps of the cross-platform docking method for engineering machinery vehicle data can be executed. Alternatively, in other embodiments, the processor 11 can be configured to execute the cross-platform docking configuration method for engineering machinery vehicle data, or the cross-platform docking method for engineering machinery vehicle data, by any other appropriate means (for example, by means of firmware).

[0082] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0083] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0084] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a ROM, an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0085] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0086] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0087] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0088] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0089] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A cross-platform docking configuration method for engineering machinery vehicle data, characterized in that: The method is executed by a front-end page adapted to the vehicle networking system of the party, and includes: In response to the user's access selection of the target three-party Internet of Vehicles system, acquiring from the own Internet of Vehicles system each three-party protocol field under the target three-party protocol supported by the target three-party Internet of Vehicles system and each own protocol field under the own protocol supported by the own Internet of Vehicles system; The three-party agreement fields under the target three-party agreement and the own agreement fields under the own agreement are displayed in association; In response to the target three-party agreement field and the target own-party agreement field selected by the user under at least one pairing selection, establishing a mapping pairing group consisting of at least one set of the target three-party agreement field and the target own-party agreement field; In response to a user selecting a configured transformation formula for at least one set of mapping pair groups, adding the transformation formula to the matching mapping pair groups; In response to the user's configuration completion instruction, the established mapping pairing groups are uploaded to the own vehicle networking system as the protocol mapping configuration of the target third-party vehicle networking system, so that the own vehicle networking system can access the construction machinery vehicle data obtained from the target third-party vehicle networking system according to the protocol mapping configuration.

2. The method according to claim 1, characterized in that After the three-party agreement fields under the target three-party agreement and the own agreement fields under the own agreement are associated and displayed, it also includes: After presenting the protocol type of the target tripartite protocol to the user, constructing data frequency modulation information in response to the data receiving frequency configured by the user for the target tripartite protocol; In response to the user's configuration completion instruction, uploading each established mapping pairing group as the protocol mapping configuration of the target three-party Internet of Vehicles system to the own Internet of Vehicles system further includes: In response to the user's configuration completion instruction, the established mapping pairing groups and data frequency modulation information are uploaded to the own vehicle networking system as the protocol mapping configuration of the target three-party vehicle networking system.

3. A cross-platform docking method for engineering machinery vehicle data, characterized in that: The method is executed by the vehicle networking system of the own party, and includes: Receiving the engineering machinery vehicle data to be connected provided by the target third-party vehicle networking system, and obtaining each mapping pairing group in the locally stored protocol mapping configuration corresponding to the target third-party vehicle networking system; wherein the protocol mapping configuration is generated by the method configuration described in claim 1 or 2; According to the mapping relationship between the tripartite protocol field in the target tripartite vehicle networking system and the own protocol field in the own vehicle networking system defined in each mapping pairing group, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system.

4. The method according to claim 3, characterized in that According to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system, including: According to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, as well as the conversion formula, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system.

5. The method according to claim 4, characterized in that According to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system, as well as the conversion formula, the data of the engineering machinery vehicle to be connected is converted into data adapted to the own vehicle networking system, including: Determine the engineering machinery vehicle data to be processed corresponding to the engineering machinery vehicle data to be connected according to the mapping relationship between the tripartite protocol fields defined in each mapping pairing group and the own protocol fields in the own vehicle networking system; According to the conversion formula configured in each mapping pairing group, the engineering machinery vehicle data to be processed is converted into data adapted to the vehicle networking system of the own party.

6. The method according to claim 3, characterized in that Receive the engineering machinery vehicle data to be connected provided by the target third-party Internet of Vehicles system, including: Obtain data frequency modulation information from the locally stored protocol mapping configuration corresponding to the target third-party Internet of Vehicles system; According to the data receiving frequency defined in the data frequency modulation information and corresponding to the target three-party protocol supported by the target three-party Internet of Vehicles system, the data of the engineering machinery vehicle to be connected provided by the target three-party Internet of Vehicles system is received.

7. A cross-platform docking configuration device for engineering machinery vehicle data, characterized in that: The device is executed by a front-end page adapted to the vehicle networking system of the party, and the device includes: A protocol field acquisition module, configured to, in response to a user's access selection of a target three-party vehicle networking system, acquire from the own vehicle networking system various three-party protocol fields under a target three-party protocol supported by the target three-party vehicle networking system, and various own protocol fields under an own protocol supported by the own vehicle networking system; An association display module is used to associate and display the three-party agreement fields under the target three-party agreement and the own-party agreement fields under the own-party agreement; A mapping pairing group establishment module, configured to establish a mapping pairing group consisting of at least one set of target tripartite agreement fields and target own-party agreement fields in response to target tripartite agreement fields and target own-party agreement fields selected by a user under at least one pairing selection; a conversion formula adding module, configured to add the conversion formula to the matching mapping pairing group in response to a user selecting a configured conversion formula for at least one mapping pairing group; The protocol mapping configuration module is used to respond to the user's configuration completion instruction and upload the established mapping pairing groups as the protocol mapping configuration of the target third-party Internet of Vehicles system to the own Internet of Vehicles system, so that the own Internet of Vehicles system can access the engineering machinery vehicle data obtained from the target third-party Internet of Vehicles system according to the protocol mapping configuration.

8. A cross-platform docking device for engineering machinery vehicle data, characterized in that: The device is executed by the vehicle networking system of the own party, and the device includes: A mapping pairing group acquisition module, used to receive the engineering machinery vehicle data to be connected provided by the target third-party vehicle networking system, and acquire each mapping pairing group in the protocol mapping configuration corresponding to the target third-party vehicle networking system stored locally; wherein the protocol mapping configuration is generated by the method configuration described in claim 1 or 2; The data docking module is used to convert the data of the engineering machinery vehicle to be connected into data adapted to the own vehicle networking system according to the mapping relationship between the three-party protocol fields in the target three-party vehicle networking system and the own protocol fields in the own vehicle networking system defined in each mapping pairing group.

9. An electronic device, characterized in that: The electronic device comprises: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the cross-platform docking configuration method for engineering machinery vehicle data described in any one of claims 1-2, or the cross-platform docking method for engineering machinery vehicle data described in any one of claims 3-6.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, which are used to enable a processor to implement the cross-platform docking configuration method for engineering machinery vehicle data described in any one of claims 1-2, or the cross-platform docking method for engineering machinery vehicle data described in any one of claims 3-6 when executed.

Images