Internet of Vehicles data development system, method, electronic equipment and vehicle

Abstract

The present invention relates to a vehicle network data development system, method, electronic device and vehicle. The development platform layer is used to respond to the arrangement operation of the draggable module through the visual interface, select the target draggable module from the draggable modules and connect it, and configure the module parameters for the target draggable module to form an application script; the core engine layer is used to obtain the vehicle network data and / or preset test data corresponding to the data input source of the target draggable module of the application script from the data access layer according to the application script as the target vehicle network data, and call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, simulate the application script and the target vehicle network data to obtain the simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer. The application developed based on vehicle network data by the present invention meets the requirements.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking data development, and in particular to a vehicle networking data development system, method, electronic equipment and vehicle. Background Art

[0002] With the continuous development of Internet of Vehicles (IoV) technology, the degree of intelligence of automobiles is becoming higher and higher, and the amount of IoV data generated by the whole vehicle is also increasing. These IoV data often come from different disciplines, such as power, battery, chassis and thermal management. At the same time, as vehicles support 4G and 5G capabilities, the amount of vehicle data uploaded to the cloud is also increasing. Various manufacturers are exploring the value of these IoV data, and cloud R&D personnel are collecting the needs of various disciplines and developing dedicated applications.

[0003] In related technologies, application development involves multiple stages. For example, a data mining application needs to go through multiple stages such as demand analysis, database design, UI (User Interface) design, software development, testing and verification, and service deployment and release. Different stages usually require the participation of different personnel. For example, demand analysis requires the participation of business personnel affiliated with the data business, and software development and testing and verification require the participation of cloud R&D personnel. However, since Internet of Vehicles data comes from different professional and technical expertise, it is often accompanied by the problem that cloud R&D personnel do not understand the business and data business personnel do not understand cloud technology, resulting in the application developed based on Internet of Vehicles data not meeting the requirements. Summary of the Invention

[0004] One of the purposes of the present invention is to provide a vehicle network data development system to solve the problem in the prior art that vehicle network data comes from different professions and technical expertise, and is often accompanied by cloud-based R&D personnel not understanding the business and data business personnel not understanding cloud technology, resulting in applications developed based on vehicle network data not meeting the requirements; the second purpose is to provide a vehicle network data development method; the third purpose is to provide an electronic device; and the fourth purpose is to provide a vehicle.

[0005] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0006] A vehicle networking data development system includes at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. The vehicle networking data development system provides a draggable module for encapsulating and generating vehicle networking functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services, wherein:

[0007] The development platform layer is configured to provide a visual interface, and in response to an arrangement operation on the draggable modules through the visual interface, select a target draggable module from the draggable modules and connect it, and configure module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source;

[0008] The core engine layer is used to obtain the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script from the data access layer as the target Internet of Vehicles data according to the application script, so as to call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

[0009] A method for developing Internet of Vehicles (IoV) data is applied to an IoV data development system. The IoV data development system includes at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. The IoV data development system provides a draggable module that encapsulates IoV functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services. The method includes:

[0010] providing a visual interface, and in response to an arrangement operation on the draggable modules through the visual interface, selecting a target draggable module from the draggable modules and connecting the module, configuring module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source;

[0011] According to the application script, the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script are obtained from the data access layer as the target Internet of Vehicles data, so as to call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

[0012] Beneficial effects of the present invention:

[0013] In an embodiment of the present invention, the Internet of Vehicles data development system may include at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. In addition, the Internet of Vehicles data development system may provide professionals with draggable modules generated based on the Internet of Vehicles functional encapsulation involved in the application development process. The third-party service access layer provides atomic access entry services for simulation test related services. In the process of developing applications, the development platform layer may be used to provide a visual interface. In response to the orchestration operation of the draggable modules by relevant personnel through the visual interface, a target draggable module may be selected from the draggable modules and connected, and module parameters may be configured for the target draggable module to form an application script. The target draggable module has a corresponding data input source. The core engine layer is used to obtain the application script from the data access layer according to the application script. The Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the program script are used as the target Internet of Vehicles data, and the corresponding simulation test related services are called through the atomic access entry service provided by the third-party service access layer. The application script and the target Internet of Vehicles data are simulated and tested to obtain the simulation test results, and the simulation test results are pushed to the functional application layer to display the simulation test results through the functional application layer. During the development of the application, relevant personnel can select the draggable module related to the needs and connect it, and the draggable module has also set the corresponding input data source. Based on the input data source, the corresponding Internet of Vehicles data can be obtained to automatically perform simulation tests. Therefore, relevant personnel do not need to understand the business, and do not need to understand cloud technology, so that the application developed based on the Internet of Vehicles data meets the needs.

[0014] In an embodiment of the present invention, the draggable module of the Internet of Vehicles data development system is generated by professionals based on the Internet of Vehicles function package involved in the application development process. The relevant personnel select the corresponding draggable module according to the development requirements to connect, configure module parameters, etc., to realize the development of the application. It can be seen that the relevant personnel do not need to use code to realize the development of the application. Therefore, the Internet of Vehicles data development system is a zero-code modular system. Although the zero-code platform in the related art provides basic functional modules such as tables and charts, it does not provide preset business logic and end-to-end solutions for vertical fields (such as the Internet of Vehicles). For example, it does not provide the draggable module generated based on the Internet of Vehicles function package involved in the application development process in the embodiment of the present invention. Therefore, relevant personnel can only piece together complex requirements from scratch based on basic functional modules, and need to go deep into various development stages of the application. Even if the development of the application can be completed in the end, and there is no need to use code, the development efficiency is low. In addition, if the relevant personnel do not have a thorough understanding of the various development stages of the application, then the application developed based on the Internet of Vehicles data may not meet the requirements. The embodiment of the present invention provides draggable modules. Relevant personnel can independently and quickly complete the logical construction and deployment of the application by dragging and arranging the draggable modules, breaking the communication and understanding costs caused by different technical expertise in the original division of labor model, reducing cross-team collaboration (for example, the need for data engineers + vehicle-side engineers, etc.), and a single person can complete the entire development process.

[0015] In addition, the data access layer, third-party service access layer, core engine layer, development platform layer, and functional application layer of the Internet of Vehicles data development system in the embodiment of the present invention are isolated from each other, that is, they can independently complete their own functions. Therefore, the system stability is enhanced, and overall fault isolation is achieved. The crash of a single application will not affect the main framework and other services of the Internet of Vehicles data development system. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A schematic diagram of the structure of a vehicle networking data development method provided in an embodiment of the present invention;

[0017] Figure 2 This is a logic block diagram of a vehicle networking data development system provided in an embodiment of the present invention;

[0018] Figure 3 A flowchart of an application development process provided in an embodiment of the present invention;

[0019] Figure 4 This is a timing diagram of operation signals of an application provided in an embodiment of the present invention;

[0020] Figure 5A flowchart of a method for developing Internet of Vehicles data provided in an embodiment of the present invention;

[0021] Figure 6 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0022] The following describes the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the various details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.

[0023] Reference Figure 1 , shows a schematic diagram of the structure of an Internet of Vehicles data development system provided in an embodiment of the present invention. The core business layer of the Internet of Vehicles data development system includes at least a data access layer 101, a third-party service access layer 102, a core engine layer 103, a development platform layer 104, and a functional application layer 105. The Internet of Vehicles data development system provides draggable modules, which are used to encapsulate and generate Internet of Vehicles functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services, wherein:

[0024] The development platform layer is configured to provide a visual interface, and in response to an arrangement operation on the draggable modules through the visual interface, select a target draggable module from the draggable modules and connect it, and configure module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source;

[0025] The core engine layer is used to obtain the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script from the data access layer as the target Internet of Vehicles data according to the application script, so as to call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

[0026] In the IoV data development system, draggable modules can be provided. There can be one, but typically multiple, draggable modules. These modules are modularly encapsulated, specialized functions for automotive bus data. These specialized functions may include, but are not limited to, signal parsing, timing analysis, vehicle state machine logic, CAN (Controller Area Network) signal parsing, and battery life calculation. Specifically, these specialized functions are also referred to as IoV functions. These functions are involved in the development phases of automotive applications, including requirements analysis, database design, UI design, software development, testing and verification, and / or service deployment and release.

[0027] Each draggable module has a corresponding data input source. Based on this data input source, the IoV data corresponding to the IoV function corresponding to the draggable module can be obtained. For example, if temperature data is required, the CAN interface signal should be obtained. This eliminates the need for personnel to deeply understand which IoV data is required to use a specific function. In some embodiments, personnel can set the data input source for IoV data themselves.

[0028] In the embodiment of the present invention, the core business layer of the Internet of Vehicles data development system includes a data access layer, a third-party service access layer, a core engine layer, a development platform layer and a functional application layer. Figure 2 , a logical block diagram of a connected vehicle data development system provided in an embodiment of the present invention. The data access layer may include a multi-protocol data module, a data preprocessing module, a real-time data stream access module, and a vehicle basic data module. It is primarily responsible for connecting to multi-source vehicle-side data and implementing standardized data parsing and preprocessing. The third-party service access layer may include vehicle-side toolchain services, R&D toolchain services, message push services, and ecosystem interface services. It is primarily responsible for connecting the enterprise's toolchain with third-party systems, achieving ecological integration. The core engine layer may include a logic operation engine, a data rule processing engine, an automated process engine, a dynamic execution engine, a custom module execution engine, a third-party service scheduling engine, modular management services, and log management and tracking. It is primarily responsible for providing capabilities such as logical operations, data rule cleansing, module management, process resource scheduling, and independent operation of upper-layer applications. The development platform layer includes a visual orchestration module, a modular warehouse module, a simulation testing module, and a deployment and release module. It is primarily responsible for providing a visual development environment, supporting dragging and dropping of draggable modules, logical orchestration, and property setting. The functional application layer is primarily responsible for orchestrating and combining applications for different scenarios.

[0029] The core engine layer's logical operation engine is responsible for basic operations and advanced analysis, such as sliding window aggregation, signal interpolation, and state machine logic, and also provides an atomic orchestration module. The data rule processing engine provides various data cleansing rules and an atomic orchestration module. The automated process engine handles the corresponding automated processes in the system. The dynamic execution engine virtualizes and runs applications in the functional application layer. The custom module execution engine runs custom atomic orchestration modules. The third-party service scheduling engine calls the third-party service access layer and provides atomic orchestration modules. The modular management service is responsible for categorizing and managing all atomic orchestration modules provided by the core engine layer. Log management and tracking records operations on each terminal. The basic modules provide basic optional configurations and properties, offering different functional combinations.

[0030] Among them, the visual orchestration module of the platform development layer is responsible for implementing drag-and-drop logic flow design, supporting dragging and connecting draggable modules, dynamic parameter configuration, etc.; the modular warehouse module is responsible for classified retrieval and providing detail pages for draggable modules, such as quickly filtering draggable modules by functional labels (such as "signal analysis" and "anomaly detection"); the simulation test module is responsible for real-time debugging, data injection, result verification, etc., including virtual data (test data) input and real Internet of Vehicles data loading.

[0031] It should be noted that the modules corresponding to the core business layer of the above-mentioned Internet of Vehicles data development system are only examples. In actual applications, modules can be refined and / or merged according to actual needs to facilitate relevant personnel to develop applications more conveniently. The embodiments of the present invention do not need to be limited to this.

[0032] In some embodiments of the present invention, the simulation test related services include at least on-board R&D physical tools, R&D service systems and / or third-party ecological services, which provide vehicle-side tool chain services, R&D tool chain services and third-party ecological interface services based on the third-party service access layer. Specifically, the vehicle-side tool chain service, and on-board R&D physical tools, such as CANoe, Vector and other tool chains, CANoe, Vector can realize simulation testing of Internet of Vehicles data, and provide atomic entry services corresponding to on-board R&D physical tools; R&D tool chain services, connect various R&D service systems, such as version management, defect management and other service systems, and provide atomic entry services corresponding to R&D service systems; third-party ecological interface services, connect third-party ecological services outside the enterprise, such as external maps, and provide atomic entry services corresponding to third-party ecological services.

[0033] In an embodiment of the present invention, the development platform layer provides a visual interface for relevant personnel to implement the business logic orchestration of the application. Specifically, the development platform layer serves as a bridge for the integration of business and technology, lowering the development threshold through visual interaction. Relevant personnel can drag, connect, and configure module parameters of draggable modules according to their needs, thereby constructing the application logic flow of the application and generating a structured application script. This eliminates the need for relevant personnel to understand the underlying implementation of different IoV data protocols, service calls, and other aspects. Next, the core engine layer is responsible for converting the application script into the actual operation logic of the application. Specifically, the core engine layer parses the application script and dynamically obtains real-time IoV data (e.g., CAN signals) from the data access layer based on the data input source definition of the application script. It can also obtain preset test data (e.g., virtual CAN signals simulating extreme temperature scenarios). Then, through the atomic access portal service provided by the third-party service access layer, it calls the corresponding simulation test-related service to simulate the application script and the target IoV data to obtain simulation test results. Finally, the simulation test results can be pushed to the functional application layer, where they are displayed. Relevant personnel can then determine whether the application meets the requirements by observing the simulation test results.

[0034] In the above-mentioned Internet of Vehicles data development system, the Internet of Vehicles data development system may include at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. In addition, the Internet of Vehicles data development system may provide professionals with draggable modules generated based on the Internet of Vehicles functional encapsulation involved in the application development process. The third-party service access layer provides atomic access entry services for simulation test related services. In the process of developing applications, the development platform layer may be used to provide a visual interface. In response to the orchestration operation of the draggable modules by relevant personnel through the visual interface, the target draggable module may be selected from the draggable modules and connected, and module parameters may be configured for the target draggable module to form an application script. The target draggable module has a corresponding data input source. The core engine layer is used to obtain the data from the data access layer according to the application script. The Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script are used as the target Internet of Vehicles data, and the corresponding simulation test related services are called through the atomic access entry service provided by the third-party service access layer. The application script and the target Internet of Vehicles data are simulated and tested to obtain simulation test results, and the simulation test results are pushed to the functional application layer to display the simulation test results through the functional application layer. During the development of the application, relevant personnel can select the draggable module related to the needs and connect it, and the draggable module has also set up the corresponding input data source. Based on the input data source, the corresponding Internet of Vehicles data can be obtained to automatically perform simulation tests. Therefore, relevant personnel do not need to understand the business, and do not need to understand cloud technology, so that the application developed based on the Internet of Vehicles data meets the needs.

[0035] In some embodiments of the present invention, the data access layer supports at least one Internet of Vehicles protocol and / or Internet of Vehicles rule;

[0036] The data access layer is used to obtain the original Internet of Vehicles signal according to the application script, parse the original Internet of Vehicles signal according to the supported Internet of Vehicles protocol and / or Internet of Vehicles rules to obtain Internet of Vehicles data, and pre-process the Internet of Vehicles data; the Internet of Vehicles data includes at least vehicle-side data and / or vehicle basic data, and the pre-processing includes at least time series alignment and / or cleaning of the Internet of Vehicles data according to preset Internet of Vehicles-specific processing logic.

[0037] In an embodiment of the present invention, the data access layer includes a multi-protocol data module, a data preprocessing module, a real-time data stream access module, and a vehicle basic data module. It is mainly responsible for connecting to multi-source vehicle-side data, realizing data standardization analysis and preprocessing, and uniformly providing Internet of Vehicles data and vehicle basic data to the core engine layer.

[0038] Specifically, the multi-protocol data module can be responsible for accessing the Internet of Vehicles protocols: CAN, CANFD (Controller Area Network Flexible Data-Rate), LIN (Local Interconnect Network), ETH (Ethernet), MQTT (Message Queuing Telemetry Transport), HTTP (Hypertext Transfer Protocol), Kafka (a distributed publish-subscribe messaging system), Modbus (Modbus Protocol), etc., while providing pre-configured templates such as Topic mapping (quickly associating MQTT / Kafka topics with vehicle-side signals) and CAN / LIN signal DBC (Database for CAN) file parsing rules; the data preprocessing module has built-in Internet of Vehicles-specific processing logic: time series alignment, signal cleaning, etc.; the real-time data stream access module is based on a platform that can support real-time data processing and batch processing, such as Apache Flink or Apache Kafka Streams, to achieve real-time collection and buffering of high-throughput data streams; the vehicle basic data module provides vehicle VIN (Vehicle Identification Number) Common vehicle basic data such as vehicle identification number (VIN) decoding, vehicle model matching, device information, software version and / or user information.

[0039] In some embodiments of the present invention, the third-party service access layer also provides atomic access entry services for communication software;

[0040] The core engine layer is used to call the communication software according to the application script through the atomic access entry service provided by the third-party service access layer, so as to push messages through the communication software.

[0041] In an embodiment of the present invention, the third-party service access layer can also provide an atomic access entry service for the communication software. Specifically, the third-party service access layer can include a message push service. The message push service connects various communication software, such as email, internal / external communication software, and provides an atomic entry service corresponding to the message push service; the core engine layer can call the corresponding communication software, such as email, through the atomic access entry service provided by the third-party service access layer according to the application script, so as to push various messages through the communication software, such as the simulation test results of the application script, or abnormal data and faults that occur during the simulation test results, etc., so as to facilitate relevant personnel or other personnel involved in the application development to understand the application, and then perform corresponding processing, thereby ensuring the development efficiency of the application.

[0042] In some embodiments of the present invention, the development platform layer is further used to perform editing operations on the application script; the editing operations at least include adding, deleting, modifying and / or publishing.

[0043] In an embodiment of the present invention, the deployment and publishing module of the development platform layer can support the full life cycle management of the application script, that is, editing operations such as adding, deleting, modifying and / or publishing can be performed. Specifically, adding refers to adding new functional modules or logical branches to the application script, thereby expanding the various capabilities of the application; deleting refers to removing redundant or invalid draggable modules in the application script, and optimizing the logic of the application script. Modification refers to adjusting the properties of the draggable module of the application script or the parameters and connection relationships corresponding to the properties, etc., to adapt to the changed requirements or achieve better application effects. Publishing refers to deploying the application script to the operating environment. By performing adaptive editing operations on the application script, relevant personnel can flexibly adjust the application script without having to redevelop the application script of the entire application, thereby ensuring the efficiency of application development.

[0044] In some embodiments of the present invention, the development platform layer is also used to display data flow; the data flow includes at least the data flow between the target draggable modules of the application script and / or the data flow between the target draggable module and the simulation test related services; the data flow has a visual identification, and the visual identification includes at least highlighting.

[0045] In an embodiment of the present invention, the simulation test module of the development platform layer can display the data flow during the simulation test of the application script. The data flow may include: the data flow between the target draggable modules, for example, the Internet of Vehicles data after cleaning at the data access layer can flow into the dynamic operation engine of the core engine layer; the data flow may also include: the data flow between the target draggable module and the simulation test related services, for example, the map provided by the third-party system of the simulation test related services flows into the platform development layer, etc.

[0046] In order to facilitate relevant personnel to view the data flow, the data flow can also be displayed in the visual interface with corresponding visual identification. For example, the data flow can be highlighted. By intuitively presenting the data flow of the application script during the simulation test process, the observability of the application during the simulation test process is improved, helping relevant personnel quickly discover logical errors or blockages.

[0047] In some embodiments of the present invention, the development platform layer is further configured to interrupt the simulation test of the application script and the target Internet of Vehicles data in response to an interrupt operation submitted through the visual interface.

[0048] In an embodiment of the present invention, during the simulation test of an application script, relevant personnel can actively trigger an interrupt operation (such as clicking a pause button displayed in the visual interface) through the visual interface provided by the development platform layer. In response to the interrupt operation, the Internet of Vehicles data development system can stop the simulation test and retain the variable values ​​of the relevant variables involved at the time of the interruption, as well as the context information of the draggable module, so that the simulation test of the application script can be continued when the relevant personnel clicks the start button displayed in the visual interface. In the above embodiment, relevant personnel are allowed to pause the simulation test of the application script when an abnormal or unexpected result occurs, and then check for problems with the application script to avoid erroneous logic from continuously consuming computing resources or generating invalid simulation test results.

[0049] In some embodiments of the present invention, the development platform layer is further used to monitor the application script and the target Internet of Vehicles data during simulation testing, so that when the specified variable meets the preset monitoring conditions, the specified variable is displayed in the visualization interface.

[0050] In an embodiment of the present invention, the simulation test module at the development platform layer provides a monitoring function. Relevant personnel can monitor designated variables in real time and set corresponding preset monitoring conditions for the designated variables. For example, if certain data during the simulation test exceeds a preset threshold, or the application status does not meet the preset state, the designated variable can be displayed in the visualization interface when the preset monitoring conditions are met, such as by highlighting, displaying with color, or through a pop-up window. By monitoring various variables during the simulation process in real time and displaying them in the visualization interface when the designated variables meet the preset monitoring conditions, the cost of manual inspections can be reduced.

[0051] In order to enable those skilled in the art to better understand the embodiments of the present invention, specific examples are used below for illustration.

[0052] Reference Figure 3 , which is a development flow chart of an application provided in an embodiment of the present invention. The process of creating a new application can be as follows, wherein the relevant personnel may be vehicle-side data developers:

[0053] S301: Vehicle-side data developers analyze new requirements, sort out the draggable modules selected according to the requirements, and sort out the logic of the requirements;

[0054] S302: The vehicle-side data developer selects a draggable module from the modular warehouse module, adds branch logic to the selected draggable module, drags and connects the draggable module, and configures module parameters for the draggable module;

[0055] S303: The vehicle-side data developer injects test data and / or selects real Internet of Vehicles data into the simulation test module for real-time debugging. After completion, functional and performance testing is performed.

[0056] S304: The vehicle-side data developer submits a deployment and release application in the deployment and release module. After approval, the application is dynamically loaded and run.

[0057] S305: The vehicle-side data developer continuously expands the scenarios and adjusts the parameters based on the monitoring dashboard, message push records, and alarm settings of the specified variables of the application script to achieve operation and maintenance monitoring and iteration of the application script.

[0058] Reference Figure 4 , is a timing diagram of operation signals of an application provided in an embodiment of the present invention. The application operation timing is as follows:

[0059] 401: The vehicle-side device uploads the original IoV signal to the data access layer, which performs data cleansing, such as protocol parsing and time series alignment. The vehicle-side device may include a T-Box (Telematics Box), an ECU (Electronic Control Unit), and onboard sensors.

[0060] 402: The dynamic runtime engine loads the application script to be run and parses the information required to run;

[0061] 403: The dynamic running engine loads the original IoV signal to the data access layer based on the information in the application script and parses it to obtain IoV data.

[0062] 404: The dynamic operation engine schedules the data rule processing engine interface to perform secondary data cleaning on the Internet of Vehicles data based on the information in the application script;

[0063] 405: Dynamically running the engine, based on the information in the application script, scheduling the logical operation rules provided by the logical operation engine to perform secondary calculations on the Internet of Vehicles data;

[0064] 406: Dynamically run the engine and perform incremental calculations based on the information in the application script;

[0065] 407: Dynamically run the engine and repeat steps 403-406 until all calculations in the application script are completed. Aggregate calculations are then performed on the final output, such as report statistics.

[0066] 408: The dynamic operation engine dispatches the atomic access entry service (interface) provided by the third-party service scheduling engine based on the information in the application script to push messages, such as email and issue management systems.

[0067] 409: The dynamic operation engine pushes the final calculation results, reports, and other information to the application function layer for display in the application.

[0068] The embodiments of the present invention target IoV data and, through an IoV data development system, implement IoV data mining and development for different functions and scenarios, as well as the development, verification, and release of scenario applications for fault alarms. This can quickly respond to different needs, mine the value of IoV data, and reduce operation and maintenance costs.

[0069] The zero-code platform in the related art has the defect of "tools without scenarios". Specifically, although the zero-code platform provides basic functional modules such as tables and charts, it does not provide pre-set business logic and end-to-end solutions for vertical fields (such as the Internet of Vehicles). For example, it does not provide the draggable module generated by the Internet of Vehicles function encapsulation involved in the application development process in the embodiment of the present invention. Therefore, relevant personnel can only piece together complex requirements from scratch based on the basic functional modules, and need to go deep into various development stages of the application. Even if the development of the application can be completed in the end and there is no need to use code, the development efficiency is low. In addition, if the relevant personnel do not have a thorough understanding of the various development stages of the application, then the application developed based on the Internet of Vehicles data may not meet the requirements.

[0070] In an embodiment of the present invention, the draggable module of the Internet of Vehicles data development system is generated by professionals based on the Internet of Vehicles function encapsulation involved in the application development process. Relevant personnel select the corresponding draggable module according to development requirements to connect, configure module parameters, etc., to realize the development of the application. It can be seen that relevant personnel do not need to use code to realize the development of the application. Therefore, the Internet of Vehicles data development system is a zero-code modular system. In addition, by providing draggable modules, the embodiment of the present invention allows relevant personnel to independently and quickly complete the logical construction and deployment of the application by dragging and arranging the draggable modules, breaking the communication and understanding costs caused by different technical expertise in the original division of labor model, reducing cross-team collaboration (for example, the need for data engineers + vehicle-side engineers, etc.), and a single person can complete the entire development process.

[0071] In addition, the data access layer, third-party service access layer, core engine layer, development platform layer, and functional application layer of the Internet of Vehicles data development system in the embodiment of the present invention are isolated from each other, that is, they can independently complete their own functions. Therefore, the system stability is enhanced, and overall fault isolation is achieved. The crash of a single application will not affect the main framework and other services of the Internet of Vehicles data development system.

[0072] Reference Figure 5 , showing a flowchart of the steps of a vehicle networking data development method provided in an embodiment of the present invention, which is applied to a vehicle networking data development system. The vehicle networking data development system includes at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. The vehicle networking data development system provides a draggable module, which is used to encapsulate and generate vehicle networking functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services. The method may include:

[0073] Step 501: providing a visual interface, in response to an arrangement operation on the draggable modules through the visual interface, selecting a target draggable module from the draggable modules and connecting the module, configuring module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source;

[0074] Step 502: According to the application script, obtain the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script from the data access layer as the target Internet of Vehicles data, call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

[0075] In some embodiments of the present invention, the simulation test related services include at least vehicle-mounted R&D physical tools, R&D service systems and / or third-party ecological services.

[0076] In some embodiments of the present invention, the data access layer supports at least one Internet of Vehicles protocol and / or Internet of Vehicles rule, and the method includes:

[0077] According to the application script, the original Internet of Vehicles signal is obtained, the original Internet of Vehicles signal is parsed according to the supported Internet of Vehicles protocol and / or Internet of Vehicles rules to obtain Internet of Vehicles data, and the Internet of Vehicles data is preprocessed; the Internet of Vehicles data includes at least vehicle-side data and / or vehicle basic data, and the preprocessing includes at least time series alignment and / or cleaning of the Internet of Vehicles data according to preset Internet of Vehicles-specific processing logic.

[0078] In some embodiments of the present invention, the third-party service access layer also provides atomic access portal services for communication software; the method includes:

[0079] According to the application script, the communication software is called through the atomic access portal service provided by the third-party service access layer to push messages through the communication software.

[0080] In some embodiments of the present invention, the method comprises:

[0081] Performing an editing operation on the application script; the editing operation at least includes adding, deleting, modifying and / or publishing.

[0082] In some embodiments of the present invention, the method comprises:

[0083] Display data flow; the data flow includes at least the data flow between the target draggable modules of the application script and / or the data flow between the target draggable module and the simulation test related services; the data flow has a visual identification, and the visual identification includes at least highlighting.

[0084] In some embodiments of the present invention, the method comprises:

[0085] In response to an interrupt operation submitted through the visual interface, the simulation test on the application script and the target Internet of Vehicles data is interrupted.

[0086] In some embodiments of the present invention, the method comprises:

[0087] Monitoring is performed during simulation testing of the application script and the target Internet of Vehicles data, so that when a specified variable meets a preset monitoring condition, the specified variable is displayed in the visualization interface.

[0088] In an embodiment of the present invention, the Internet of Vehicles data development system may include at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. In addition, the Internet of Vehicles data development system may provide professionals with draggable modules generated based on the Internet of Vehicles functional encapsulation involved in the application development process. The third-party service access layer provides atomic access entry services for simulation test related services. In the process of developing applications, the development platform layer may be used to provide a visual interface. In response to the orchestration operation of the draggable modules by relevant personnel through the visual interface, a target draggable module may be selected from the draggable modules and connected, and module parameters may be configured for the target draggable module to form an application script. The target draggable module has a corresponding data input source. The core engine layer is used to obtain the application script from the data access layer according to the application script. The Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the program script are used as the target Internet of Vehicles data, and the corresponding simulation test related services are called through the atomic access entry service provided by the third-party service access layer. The application script and the target Internet of Vehicles data are simulated and tested to obtain the simulation test results, and the simulation test results are pushed to the functional application layer to display the simulation test results through the functional application layer. During the development of the application, relevant personnel can select the draggable module related to the needs and connect it, and the draggable module has also set the corresponding input data source. Based on the input data source, the corresponding Internet of Vehicles data can be obtained to automatically perform simulation tests. Therefore, relevant personnel do not need to understand the business, and do not need to understand cloud technology, so that the application developed based on the Internet of Vehicles data meets the needs.

[0089] In an embodiment of the present invention, the draggable module of the Internet of Vehicles data development system is generated by professionals based on the Internet of Vehicles function package involved in the application development process. The relevant personnel select the corresponding draggable module according to the development requirements to connect, configure module parameters, etc., to realize the development of the application. It can be seen that the relevant personnel do not need to use code to realize the development of the application. Therefore, the Internet of Vehicles data development system is a zero-code modular system. Although the zero-code platform in the related art provides basic functional modules such as tables and charts, it does not provide preset business logic and end-to-end solutions for vertical fields (such as the Internet of Vehicles). For example, it does not provide the draggable module generated based on the Internet of Vehicles function package involved in the application development process in the embodiment of the present invention. Therefore, relevant personnel can only piece together complex requirements from scratch based on basic functional modules, and need to go deep into various development stages of the application. Even if the development of the application can be completed in the end, and there is no need to use code, the development efficiency is low. In addition, if the relevant personnel do not have a thorough understanding of the various development stages of the application, then the application developed based on the Internet of Vehicles data may not meet the requirements. The embodiment of the present invention provides draggable modules. Relevant personnel can independently and quickly complete the logical construction and deployment of the application by dragging and arranging the draggable modules, breaking the communication and understanding costs caused by different technical expertise in the original division of labor model, reducing cross-team collaboration (for example, the need for data engineers + vehicle-side engineers, etc.), and a single person can complete the entire development process.

[0090] In addition, the data access layer, third-party service access layer, core engine layer, development platform layer, and functional application layer of the Internet of Vehicles data development system in the embodiment of the present invention are isolated from each other, that is, they can independently complete their own functions. Therefore, the system stability is enhanced, and overall fault isolation is achieved. The crash of a single application will not affect the main framework and other services of the Internet of Vehicles data development system.

[0091] As for the method embodiment, since it is basically similar to the system embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the system embodiment.

[0092] It should be noted that the embodiments of the present invention may involve the use of user data. In actual applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations of the country where the user is located (for example, with the user's explicit consent, effective notification to the user, etc.).

[0093] The embodiment of the present invention further provides an electronic device, such as Figure 6 As shown, it includes a processor 601, a device interface 602, a memory

[0094] 603 and bus 604;

[0095] Memory 603, used for storing computer programs;

[0096] The processor 601 is configured to implement the above steps when executing the program stored in the memory 603 .

[0097] The bus mentioned in the terminal above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This bus can be divided into address buses, data buses, control buses, etc. For ease of illustration, the figure shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0098] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0099] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0100] The present invention also provides a storage medium, which, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute the vehicle network data development method of the aforementioned embodiment.

[0101] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0102] The algorithm and display provided herein are not inherently related to any particular computer, virtual device or other equipment. According to the above description, it is obvious that the structure required for constructing this type of device is suitable. In addition, the present invention is not directed to any specific programming language. It should be understood that various programming languages ​​can be utilized to realize the content of the present invention described herein, and the above description of specific languages ​​is for the purpose of disclosing the best mode of the present invention.

[0103] In the description provided herein, numerous specific details are described. However, it is understood that embodiments of the present invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.

[0104] Similarly, it should be understood that in order to streamline the present invention and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Accordingly, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of the invention.

[0105] Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively modified and installed in one or more devices different from the embodiments. The modules, units, or components in the embodiments can be combined into a single module, unit, or component, and furthermore, they can be divided into multiple sub-modules, sub-units, or sub-components. All features disclosed in this specification (including the accompanying claims, abstract, and drawings), and all processes or units of any method or device disclosed therein, can be combined in any combination, unless at least some of such features and / or processes or units are mutually exclusive. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0106] The various component embodiments of the present invention may be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will appreciate that in practice, a microprocessor or digital signal processor (DSP) may be used to implement some or all of the functions of some or all of the components of the sorting device according to the present invention. The present invention may also be implemented as an apparatus or device program for performing part or all of the methods described herein. Such a program implementing the present invention may be stored on a computer-readable medium or in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0107] It should be noted that the above embodiments illustrate rather than limit the invention, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between brackets should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising several different elements and by means of appropriately programmed computers. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.

[0108] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices, apparatuses and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0109] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

[0110] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

[0111] It should be noted that the various data-related processes in the embodiments of the present invention are all carried out in compliance with the corresponding data protection laws and policies of the country where they are located, and with the authorization given by the corresponding device owner.

Claims

1. A vehicle network data development system, characterized in that: The IoV data development system includes at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. The IoV data development system provides a draggable module, which is used to encapsulate and generate IoV functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services, wherein: The development platform layer is configured to provide a visual interface, and in response to an arrangement operation on the draggable modules through the visual interface, select a target draggable module from the draggable modules and connect it, and configure module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source; The core engine layer is used to obtain the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script from the data access layer as the target Internet of Vehicles data according to the application script, so as to call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

2. The vehicle networking data development system according to claim 1, characterized in that: The simulation test related services include at least vehicle-mounted R&D physical tools, R&D service systems and / or third-party ecological services.

3. The vehicle networking data development system according to claim 1, characterized in that: The data access layer supports at least one Internet of Vehicles protocol and / or Internet of Vehicles rule; The data access layer is used to obtain the original Internet of Vehicles signal according to the application script, parse the original Internet of Vehicles signal according to the supported Internet of Vehicles protocol and / or Internet of Vehicles rules to obtain Internet of Vehicles data, and pre-process the Internet of Vehicles data; the Internet of Vehicles data includes at least vehicle-side data and / or vehicle basic data, and the pre-processing includes at least time series alignment and / or cleaning of the Internet of Vehicles data according to preset Internet of Vehicles-specific processing logic.

4. The vehicle networking data development system according to claim 1, characterized in that: The third-party service access layer also provides atomic access entry services for communication software; The core engine layer is used to call the communication software according to the application script through the atomic access entry service provided by the third-party service access layer, so as to push messages through the communication software.

5. The vehicle networking data development system according to claim 1, characterized in that: The development platform layer is further used to perform editing operations on the application script; the editing operations at least include adding, deleting, modifying and / or publishing.

6. The vehicle networking data development system according to claim 2, characterized in that: The development platform layer is also used to display data flow; the data flow at least includes the data flow between the target draggable modules of the application script and / or the data flow between the target draggable module and the simulation test related services; the data flow has a visual identification, and the visual identification at least includes highlighting.

7. The vehicle networking data development system according to claim 1, characterized in that: The development platform layer is further configured to interrupt the simulation test of the application script and the target Internet of Vehicles data in response to an interrupt operation submitted through the visual interface.

8. The vehicle networking data development system according to claim 1, characterized in that: The development platform layer is further used to monitor the application script and the target Internet of Vehicles data during simulation testing, so as to display the specified variables in the visualization interface when the specified variables meet preset monitoring conditions.

9. A method for developing Internet of Vehicles data, characterized in that: The method is applied to a vehicle networking data development system, which includes at least a data access layer, a third-party service access layer, a core engine layer, a development platform layer, and a functional application layer. The vehicle networking data development system provides a draggable module, which is used to encapsulate and generate vehicle networking functions involved in application development. The third-party service access layer provides atomic access entry services for simulation test-related services. providing a visual interface, and in response to an arrangement operation on the draggable modules through the visual interface, selecting a target draggable module from the draggable modules and connecting the module, configuring module parameters for the target draggable module to form an application script; the target draggable module has a corresponding data input source; According to the application script, the Internet of Vehicles data and / or preset test data corresponding to the data input source of the target draggable module of the application script are obtained from the data access layer as the target Internet of Vehicles data, so as to call the corresponding simulation test related service through the atomic access entry service provided by the third-party service access layer, perform simulation testing on the application script and the target Internet of Vehicles data to obtain simulation test results, and push the simulation test results to the functional application layer to display the simulation test results through the functional application layer.

10. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to execute the instructions to implement the vehicle network data development method as claimed in claim 9.

11. A computer-readable storage medium, characterized in that When the instructions in the storage medium are executed by the processor of the mobile terminal, the mobile terminal is enabled to execute the vehicle network data development method as claimed in claim 9.

12. A vehicle, characterized in that: The vehicle includes the electronic device according to claim 10.

Images