Vehicle model-based knowledge graph display method and device, and computer device

Abstract

The application discloses a vehicle type-based knowledge graph display method and device and a computer device, and belongs to the technical field of vehicles. Through the technical scheme provided by the embodiment of the application, the terminal displays a first knowledge graph to show the association relationship between a target service platform and multiple vehicle types, and displays a second knowledge graph through operation on the first knowledge graph; the second knowledge graph can show the association relationship between the target service platform and the function system of the corresponding vehicle type, and compared with the first knowledge graph, the relationship between the platform and the vehicle type is more deeply displayed. Operation is performed on the second knowledge graph, a third knowledge graph is further displayed, the association relationship between the service and the service data is visualized through the third knowledge graph, which helps technical personnel quickly obtain information and improves the efficiency of the technical personnel in maintaining and iteratively updating the vehicle type.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, apparatus, and computer device for displaying a knowledge graph based on vehicle models. Background Technology

[0002] With the development of vehicle technology, the number of functional systems provided in vehicles is increasing. A functional system refers to the set of components required by a vehicle to perform a specific function. In order to make full use of the multiple functional systems in a particular vehicle model, vehicle manufacturers often build a cloud service platform to interact with multiple functional systems for data exchange.

[0003] In related technologies, cloud service platforms often adopt SOA (Service-Oriented Architecture). SOA independently provides multiple services, and different services are applied to different functional systems, thereby enabling multiple functional systems in the vehicle to achieve their corresponding functions.

[0004] However, for technicians, the service data between the services provided by the cloud service platform and the functional systems is in a black box. Technicians cannot know the relationship between services and service data, which reduces the efficiency of technicians in maintaining and updating vehicle models. Summary of the Invention

[0005] This application provides a method, apparatus, and computer device for displaying a knowledge graph based on vehicle models. This allows for the visualization of services and service data provided by a cloud service platform, thereby improving the efficiency of technicians in maintaining and iteratively updating vehicle models. The technical solution is as follows:

[0006] On the one hand, a knowledge graph display method based on vehicle model is provided, the method comprising:

[0007] Display a first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the association between the target service platform node and the multiple vehicle model nodes.

[0008] In response to a click operation on any vehicle model node in the first knowledge graph, a second knowledge graph under the vehicle model node is displayed. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association relationship between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node, and the entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node.

[0009] In response to a click operation on any service node in the second knowledge graph, a third knowledge graph under the service node is displayed. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association relationship between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system.

[0010] In one possible implementation, after displaying the third knowledge graph under any service node in the second knowledge graph in response to a click operation, the method further includes:

[0011] In response to a click operation on a service node in the third knowledge graph, a seventh knowledge graph under the service node is displayed. The seventh knowledge graph includes the service node and multiple interface nodes, and is used to display the association relationship between the service node and the multiple interface nodes.

[0012] In one possible implementation, before displaying the first knowledge graph, the method further includes:

[0013] The service platform selection interface displays multiple candidate service platforms;

[0014] The display of the first knowledge graph includes:

[0015] When the target service platform is selected from the plurality of candidate service platforms, the first knowledge graph of the target service platform is displayed.

[0016] On the one hand, a knowledge graph display device based on vehicle models is provided, the device comprising:

[0017] The first knowledge graph display module is used to display the first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the association relationship between the target service platform node and the multiple vehicle model nodes.

[0018] The second knowledge graph display module is used to respond to a click operation on any vehicle model node in the first knowledge graph and display the second knowledge graph under the vehicle model node. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association relationship between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node, and the entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node.

[0019] The third knowledge graph display module is used to respond to a click operation on any service node in the second knowledge graph and display the third knowledge graph under the service node. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association relationship between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system.

[0020] In one possible implementation, the second knowledge graph display module is configured to, in response to a click operation on any vehicle model node in the first knowledge graph, acquire the plurality of functional system nodes under the vehicle model node, the plurality of service nodes under the target service platform node, and the association data between the plurality of functional system nodes and the plurality of service nodes; based on the association data between the plurality of functional system nodes and the plurality of service nodes, add connections between the plurality of functional system nodes and the plurality of service nodes to generate the second knowledge graph; and display the second knowledge graph.

[0021] In one possible implementation, the second knowledge graph display module is configured to, in response to a click operation on any vehicle model node in the first knowledge graph, display a knowledge graph selection pop-up window for the vehicle model node. The knowledge graph selection pop-up window displays multiple types of knowledge graphs under the vehicle model node, and the different types of knowledge graphs are used to demonstrate the association relationships between different types of nodes under the vehicle model node. When the second knowledge graph is selected among the multiple types of knowledge graphs, the second knowledge graph is displayed.

[0022] In one possible implementation, the device further includes:

[0023] The fourth knowledge graph display module is used to display the fourth knowledge graph when the fourth knowledge graph among the multiple types of knowledge graphs is selected. The fourth knowledge graph includes multiple manufacturer nodes and multiple component nodes. The fourth knowledge graph is used to display the association relationship between the multiple manufacturer nodes and the multiple component nodes. The entity corresponding to the component node is the component used by the vehicle model corresponding to the vehicle model node.

[0024] In one possible implementation, the device further includes any of the following:

[0025] A switching module is used to switch the second knowledge graph to the first knowledge graph in response to a click operation on the return control, where a return control is displayed in the second knowledge graph.

[0026] An export module is used to export the second knowledge graph as an image in response to a click operation on the export control, where an export control is displayed in the second knowledge graph.

[0027] A zoom-in module is used to display a zoom-in control in the second knowledge graph, and to zoom in on the second knowledge graph in response to a click operation on the zoom-in control.

[0028] In one possible implementation, the device further includes:

[0029] The fifth knowledge graph display module is used to respond to a click operation on any functional system node in the second knowledge graph and display the fifth knowledge graph under the functional system node. The fifth knowledge graph includes the functional system node and multiple component nodes. The fifth knowledge graph is used to display the association relationship between the functional system node and the multiple component nodes. The entity corresponding to the component node is a component in the functional system corresponding to the functional system node.

[0030] In one possible implementation, the device further includes:

[0031] The sixth knowledge graph display module is used to display the sixth knowledge graph under the service node in response to a drag operation on any service node in the second knowledge graph. The sixth knowledge graph includes the service node and multiple associated service nodes. The sixth knowledge graph is used to display the association relationship between the service node and the multiple associated service nodes. The entity corresponding to the associated service node is a service associated with the entity corresponding to the service node.

[0032] In one possible implementation, the device further includes:

[0033] The attribute display pop-up module is used to display an attribute display pop-up in response to a click operation on any service data node in the third knowledge graph. The attribute display pop-up displays at least one of the following: data type, data format, data flow direction, and data value range of the service data corresponding to the service data node.

[0034] In one possible implementation, the device further includes:

[0035] The seventh knowledge graph display module is used to display the seventh knowledge graph under the service node in response to the click operation of the service node in the third knowledge graph. The seventh knowledge graph includes the service node and multiple interface nodes, and is used to display the association relationship between the service node and the multiple interface nodes.

[0036] In one possible implementation, the device further includes:

[0037] The service platform selection interface display module is used to display the service platform selection interface, which displays multiple candidate service platforms.

[0038] The first knowledge graph display module is used to display the first knowledge graph of the target service platform when the target service platform is selected among the plurality of candidate service platforms.

[0039] On one hand, a computer device is provided, the computer device including one or more processors and one or more memories, the one or more memories storing at least one computer program, the computer program being loaded and executed by the one or more processors to implement the vehicle model-based knowledge graph display method.

[0040] On the one hand, a computer-readable storage medium is provided, wherein at least one computer program is stored in the computer-readable storage medium, the computer program being loaded and executed by a processor to implement the vehicle-type-based knowledge graph display method.

[0041] On one hand, a computer program product or computer program is provided, which includes program code stored in a computer-readable storage medium. The processor of a computer device reads the program code from the computer-readable storage medium and executes the program code, causing the computer device to execute the above-described vehicle model-based knowledge graph display method.

[0042] The technical solution provided in this application allows the terminal to display the relationships between a target service platform and multiple vehicle models by showing a first knowledge graph. Operations on the first knowledge graph trigger the display of a second knowledge graph, which displays the relationships between the target service platform and the functional systems of the corresponding vehicle models. Compared to the first knowledge graph, the second knowledge graph provides a deeper understanding of the relationship between the platform and the vehicle models. Operations on the second knowledge graph can further trigger the display of a third knowledge graph, which visualizes the relationships between services and service data. This helps technicians quickly obtain information and improves the efficiency of vehicle model maintenance and iterative updates. Furthermore, the three knowledge graphs display the relationships between related entities at different levels, allowing technicians to efficiently search for relevant information. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1 This is a schematic diagram of the implementation environment of a vehicle model-based knowledge graph display method provided in an embodiment of this application;

[0045] Figure 2 This is a flowchart of a knowledge graph display method based on vehicle model provided in an embodiment of this application;

[0046] Figure 3 This is a flowchart of a knowledge graph display method based on vehicle model provided in an embodiment of this application;

[0047] Figure 4 This is a schematic diagram of an interface provided in an embodiment of this application;

[0048] Figure 5 This is a schematic diagram of a first knowledge graph provided in an embodiment of this application;

[0049] Figure 6 This is a schematic diagram of a second knowledge graph provided in an embodiment of this application;

[0050] Figure 7 This is a schematic diagram of a knowledge graph selection pop-up window provided in an embodiment of this application;

[0051] Figure 8 This is a schematic diagram of a fourth knowledge graph provided in an embodiment of this application;

[0052] Figure 9 This is a schematic diagram of a fifth knowledge graph provided in an embodiment of this application;

[0053] Figure 10 This is a schematic diagram of a sixth knowledge graph provided in an embodiment of this application;

[0054] Figure 11 This is a schematic diagram of a third knowledge graph provided in an embodiment of this application;

[0055] Figure 12 This is a schematic diagram of another third knowledge graph provided in an embodiment of this application;

[0056] Figure 13 This is a schematic diagram of an attribute display pop-up window provided in an embodiment of this application;

[0057] Figure 14This is a schematic diagram of a seventh knowledge graph provided in an embodiment of this application;

[0058] Figure 15 This is a schematic diagram of the structure of a vehicle-based knowledge graph display device provided in an embodiment of this application;

[0059] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0061] In this application, the terms "first," "second," etc., are used to distinguish identical or similar items with essentially the same function. It should be understood that there is no logical or temporal dependency between "first," "second," and "nth," nor is there any limitation on the quantity or execution order. In addition, "multiple" in this application refers to two or more.

[0062] Cloud computing refers to a delivery and usage model for IT (Internet Technology) infrastructure, meaning obtaining necessary resources through a network in an on-demand and easily scalable manner. In a broader sense, cloud computing also refers to a service delivery and usage model, meaning obtaining necessary services through a network in an on-demand and easily scalable manner. These services can be IT and software-related, internet-related, or other services. Cloud computing is a product of the development and integration of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing.

[0063] With the development of the internet, real-time data streams, and the diversification of connected devices, as well as the demands for search services, social networks, mobile commerce, and open collaboration, cloud computing has rapidly developed. Unlike previous parallel distributed computing, cloud computing will fundamentally revolutionize the entire internet model and enterprise management model.

[0064] Knowledge graphs are structured semantic knowledge bases used to rapidly describe concepts and their relationships in the physical world. By effectively processing, handling, and integrating complex document data, knowledge graphs transform it into simple, clear "entity-relationship-entity" triples, ultimately aggregating vast amounts of knowledge to achieve rapid knowledge response and reasoning. In other words, knowledge graphs can display the relationships between entities.

[0065] Entity: An entity refers to a distinguishable and independently existing thing, such as a person, a city, a plant, a product, etc. Everything in the world is composed of concrete things, which are entities. Entities are the most basic elements in a knowledge graph, and different entities have different relationships.

[0066] SOA: Service-Oriented Architecture (SOA) is a software architecture design model and methodology. In a broad sense, SOA refers to a new enterprise application architecture and enterprise IT infrastructure that enables interconnection between discrete systems across applications, departments, enterprises, and even industries. In a narrower sense, SOA refers to a software architecture that allows for the distributed deployment, composition, and use of loosely coupled, coarse-grained application components over a network, based on requirements. The service layer is the foundation of SOA and can be directly invoked by applications, effectively controlling human dependencies in system interactions with software agents.

[0067] Service Platform: A service platform is a cloud service platform provided by a service provider, offering a variety of services to vehicles. For example, it can provide navigation and self-diagnosis services. A service platform is the result of the coupling of multiple service components, each providing different services.

[0068] It should be noted that the information (including but not limited to information of the vehicle terminal, user personal information, etc.), data (including but not limited to data used for analysis, data stored, data displayed, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0069] Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle-based knowledge graph display method provided in this application embodiment. See also... Figure 1 The implementation environment may include terminal 110 and server 140.

[0070] Terminal 110 is connected to server 140 via a wireless or wired network. Optionally, terminal 110 can be a vehicle-mounted terminal, smartphone, tablet, laptop, desktop computer, etc., but is not limited to these. Terminal 110 has applications installed and running that support knowledge graph generation and display.

[0071] Server 140 is a standalone physical server, or a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms.

[0072] Those skilled in the art will understand that the number of terminals described above can be more or less. For example, there may be only one terminal, or there may be dozens or hundreds of terminals, or even more, in which case other terminals may also be included in the above implementation environment. This application does not limit the number of terminals or the type of device in its embodiments.

[0073] After introducing the implementation environment of the embodiments of this application, the application scenarios of the embodiments of this application will be described below in conjunction with the above implementation environment. In the following description, the terminal is the terminal 110 in the above implementation environment, and the server is the server 140 in the above implementation environment.

[0074] The technical solution provided in this application can be applied to scenarios involving the visualization of vehicle services and service data. For example, a server provides multiple services for a specific vehicle model, and each service requires different attributes of the service data. Understanding the correspondence between services and service data is fundamental for technicians to perform maintenance and iterative updates. These attributes include the data type, data format, and data flow of the service data. Using the technical solution provided in this application, a knowledge graph can be used to display the relationships between the platform and vehicle models, between functional systems and services, and between services and service data. This helps technicians flexibly view the correspondence between vehicle models and the server at different levels, enabling visualization of these relationships, facilitating technical personnel's review, and improving the efficiency of vehicle maintenance and iterative updates.

[0075] It should be noted that the above description uses the technical solution provided in the embodiments of this application to demonstrate the association between a server and a vehicle model at different levels. In other possible application scenarios, the technical solution provided in the embodiments of this application can also demonstrate the association between a server and multiple vehicle models, and the embodiments of this application do not limit this.

[0076] After introducing the implementation environment and application scenarios of the embodiments of this application, the technical solutions provided by the embodiments of this application are described below. (See also...) Figure 2 Taking the terminal as the executing entity as an example, the method includes the following steps.

[0077] 202. The terminal displays a first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the relationship between the target service platform node and the multiple vehicle model nodes.

[0078] In this framework, the entity corresponding to the target service platform node is the target service platform itself, which is the selected service platform. The entities corresponding to multiple vehicle model nodes are multiple vehicle models, and there is a one-to-one correspondence between the vehicle model nodes and the vehicle models; all of these vehicle models are provided with services by the target service platform. The first knowledge graph displays the association between the target service platform node and the multiple vehicle model nodes, that is, it displays the association between the target service platform and the multiple vehicle models. Technical personnel can intuitively understand this association through this first knowledge graph.

[0079] 204. In response to a click operation on any vehicle model node in the first knowledge graph, the terminal displays a second knowledge graph under the vehicle model node. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node, and the entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node.

[0080] In this context, the second knowledge graph under the vehicle model node refers to a knowledge graph subordinate to that vehicle model node; in other words, the second knowledge graph is a knowledge graph at the next lower level than that vehicle model node. Service nodes correspond to entities that are services provided by the target service platform, such as navigation services, multimedia playback services, and vehicle detection services. Functional systems refer to the set of hardware required in a vehicle to achieve a specific function; for example, the navigation function depends on a navigation system. The second knowledge graph describes the relationships between these multiple service nodes and multiple functional system nodes, that is, it describes the relationships between the various services provided by the target service platform and the various functional systems of the vehicle model. In other words, the second knowledge graph demonstrates the correspondence between the services provided by the target service platform and the functional systems of the vehicle model.

[0081] 206. In response to a click operation on any service node in the second knowledge graph, the terminal displays a third knowledge graph under the service node. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system.

[0082] Service data refers to data generated when a service is invoked. For example, invoking a navigation service generates navigation data, which may include vehicle location data. In some embodiments, the attributes of service data include data type, data format, and data flow direction.

[0083] The technical solution provided in this application allows the terminal to display the relationships between a target service platform and multiple vehicle models by showing a first knowledge graph. Operations on the first knowledge graph trigger the display of a second knowledge graph, which displays the relationships between the target service platform and the functional systems of the corresponding vehicle models. Compared to the first knowledge graph, the second knowledge graph provides a deeper understanding of the relationship between the platform and the vehicle models. Operations on the second knowledge graph can further trigger the display of a third knowledge graph, which visualizes the relationships between services and service data. This helps technicians quickly obtain information and improves the efficiency of vehicle model maintenance and iterative updates. Furthermore, the three knowledge graphs display the relationships between related entities at different levels, allowing technicians to efficiently search for relevant information.

[0084] Steps 202-206 above are a brief description of the technical solutions provided in the embodiments of this application. The technical solutions provided in the embodiments of this application will be described in more detail below with reference to some examples. See [link to relevant documentation]. Figure 3 Taking the terminal as the executing entity as an example, the method includes the following steps.

[0085] 302. The terminal displays a service platform selection interface, which shows multiple candidate service platforms.

[0086] The service platform selection interface is used to choose different service platforms for viewing. For example, vehicle manufacturers may build their own service platform to provide services for different vehicle models, or they may directly cooperate with third-party service platforms to use their services. In some embodiments, vehicle manufacturers may cooperate with multiple third-party service platforms, leveraging the advantages of different third-party service platforms to improve the performance of their vehicles. These multiple candidate service platforms are essentially multiple third-party service platforms, and the service platform selection interface allows users to choose the target service platform from these candidate platforms to view the desired relationships.

[0087] In one possible implementation, in response to a viewing operation of the service platform selection interface, the terminal displays the service platform selection interface, which shows icons of multiple candidate service platforms. Each candidate service platform icon is a selection control; clicking on an icon selects the corresponding candidate service platform.

[0088] In this implementation, the terminal can intuitively display multiple candidate service platforms through the service platform selection interface. Technicians can also quickly find out which candidate service platforms are available by viewing the service platform selection interface, thus improving the efficiency of human-computer interaction.

[0089] For example, the terminal displays a function selection interface, which includes a service platform selection control. In response to a click on this control, the terminal displays the service platform selection interface, where the icons of multiple candidate service platforms are displayed in a tiled format. See, for example... Figure 4 The terminal displays a function selection interface 400, which includes a service platform selection control 401. In response to a click on the service platform selection control 401, the terminal obtains the corresponding interface display data, including interface elements and their arrangement. Based on this display data, the terminal displays a service platform selection interface 402, which includes icons 403-406 for multiple candidate service platforms.

[0090] In some embodiments, in addition to the service platform selection control, the function selection interface may also display other function controls, such as vehicle production plan viewing control, vehicle R&D plan viewing control, and vehicle component procurement plan viewing control. This application embodiment does not limit this.

[0091] It should be noted that step 302 above is an optional step. The terminal can either execute step 302 above or directly execute step 304 below. This application embodiment does not limit this.

[0092] 304. When the target service platform is selected among the multiple candidate service platforms, the terminal displays the first knowledge graph of the target service platform. The first knowledge graph includes the target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the relationship between the target service platform node and the multiple vehicle model nodes.

[0093] In this system, the entity corresponding to the target service platform node is the target service platform, which is the selected service platform. The entities corresponding to multiple vehicle model nodes are multiple vehicle models, and there is a one-to-one correspondence between the vehicle model nodes and the vehicle models; all of these vehicle models are provided with services by the target service platform. The first knowledge graph displays the association between the target service platform node and the multiple vehicle model nodes, that is, it displays the association between the target service platform and the multiple vehicle models. Technical personnel can intuitively understand this association through the first knowledge graph. In some embodiments, the first knowledge graph includes two types of nodes: target service platform nodes and vehicle model nodes. These two types of nodes are connected by lines to indicate an association. For example, if there is a connection between a target service platform node and a vehicle model node, it indicates that there is an association between the target service platform node and that vehicle model node, meaning that the target service platform provides services to the vehicle model corresponding to that vehicle model node.

[0094] In one possible implementation, when the target service platform is selected from among multiple candidate service platforms, the terminal obtains multiple vehicle models that are associated with the target service platform. The terminal generates a target service platform node corresponding to the target service platform and multiple vehicle model nodes corresponding to the multiple vehicle models, wherein the name of the target service platform node is the name of the target service platform, and the name of the vehicle model node is the name of the corresponding vehicle model. Based on the association between the target service platform and the multiple vehicle models, the terminal adds connections between the target service platform node and the multiple vehicle model nodes to obtain the first knowledge graph, and the terminal displays the first knowledge graph. The association between the service platform and the vehicle models is pre-stored in the cloud for the terminal to access at any time. Here, the cloud refers to the target service platform or a data server maintained by the vehicle manufacturer; this embodiment does not limit this.

[0095] In this implementation, the terminal can generate the first knowledge graph based on the target service platform after selecting the target service platform, without having to generate the first knowledge graph in advance, thus reducing the storage space occupied. At the same time, the first knowledge graph generated in real time also has greater flexibility.

[0096] For example, when the target service platform is selected from multiple candidate service platforms, the terminal sends a request to the server to obtain associated vehicle models. This request carries the identifier of the target service platform, and the server is a data server built by the car manufacturer. The server receives the request and retrieves the identifier of the target service platform from it. Based on the identifier, the server queries and obtains multiple vehicle models that are associated with the target service platform. The server sends these multiple vehicle models to the terminal, which then retrieves them. The terminal generates a target service platform node corresponding to the target service platform and multiple vehicle model nodes corresponding to the multiple vehicle models. Based on the association between the target service platform and the multiple vehicle models, connections are added between the target service platform node and the multiple vehicle model nodes to obtain the first knowledge graph. The terminal displays this first knowledge graph. For example, see [link to relevant documentation]. Figure 5 The terminal displays a first knowledge graph 500, which includes a target service platform node 501 and multiple vehicle model nodes 502-505. In some embodiments, the target service platform node is located at the center of the first knowledge graph, and the multiple vehicle model nodes surround the target service platform node.

[0097] It should be noted that the above description is based on the example of the terminal generating the first knowledge graph. In other possible implementations, the first knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0098] In some embodiments, the first knowledge graph, in addition to displaying the association between the target service platform node and multiple vehicle model nodes, can also display the association between the multiple vehicle model nodes. That is, in the first knowledge graph, there are also connections between the multiple vehicle model nodes, which clearly show the association between them. In some embodiments, to distinguish between the connections between the target service platform node and the vehicle model nodes, and between the connections between vehicle model nodes, the terminal can use different colors to display the connections. For example, the connection between the target service platform node and the vehicle model nodes is black, and the connection between the vehicle model nodes is red. The association between vehicle model nodes includes the generational relationship between the vehicle models corresponding to the vehicle model nodes. For example, vehicle model A is the predecessor of vehicle model B. This is reflected in the first knowledge graph, where there is a connection between the vehicle model node corresponding to vehicle model A and the vehicle model node corresponding to vehicle model B. In some embodiments, the connections between vehicle model nodes are directed line segments. The direction of the directed line segments can intuitively show the generational relationship between the vehicle models corresponding to the vehicle model nodes, improving the efficiency of human-computer interaction.

[0099] Optionally, after the terminal displays the first knowledge graph, the terminal can also perform any of the following steps.

[0100] In one possible implementation, the first knowledge graph displays an export control, and in response to a click operation on the export control, the terminal exports the first knowledge graph as an image.

[0101] In this implementation, an export control is provided on the first knowledge graph, which can be quickly exported as an image for storage and sharing, thus improving the efficiency of human-computer interaction.

[0102] For example, see Figure 5 The first knowledge graph 500 displays an export control 506. In response to clicking the export control 506, the terminal displays an image export pop-up window, which includes a storage location selection area and a confirmation control. When an image storage location is selected through the storage location selection area, in response to clicking the confirmation control, the terminal exports the first knowledge graph as an image. In some embodiments, the image export pop-up window further includes at least one of an export image preview area and an export image naming area, wherein the export image preview area is used to preview the first knowledge graph, and the naming area is used to name the exported image.

[0103] In one possible implementation, the first knowledge graph displays a zoom-in control, and in response to a click on the zoom-in control, the terminal zooms in on the first knowledge graph. In some embodiments, the graphics in the first knowledge graph are all vector graphics, thereby ensuring that the first knowledge graph still has high clarity after zooming in.

[0104] In this implementation, a zoom control is provided on the first knowledge graph, which allows for quick zooming in of the first knowledge graph to facilitate more detailed observation of its local areas, thereby improving the efficiency of human-computer interaction.

[0105] For example, see Figure 5 The first knowledge graph 500 displays a zoom control 507. In response to a click operation on the zoom control 507, the terminal zooms in on the first knowledge graph 500.

[0106] In one possible implementation, in response to a long-press operation on any vehicle model node in the first knowledge graph, the terminal displays a pop-up window introducing the vehicle model corresponding to that node. This pop-up window displays descriptive text about the vehicle model, such as its design time, number of iterations, and designer. Alternatively, in response to a long-press operation on a target service platform node, the terminal displays a pop-up window introducing the target service platform. This pop-up window displays descriptive text about the target platform, such as its operator, establishment date, and the types of services it provides.

[0107] In this implementation, a function is provided on the first knowledge graph to long-press a node to view more information, which enriches the information content of the first knowledge graph and provides convenience for technicians to use the first knowledge graph.

[0108] Optionally, in addition to selecting the target service platform through the service platform selection interface as described in step 302, the terminal can also select the target service platform and display the first knowledge graph in the following ways.

[0109] In one possible implementation, the terminal displays an initial knowledge graph, which includes multiple candidate service platform nodes and multiple candidate vehicle model nodes. This initial knowledge graph is used to demonstrate the relationships between the multiple candidate service platform nodes and the multiple candidate vehicle model nodes, wherein the entity corresponding to each candidate service platform node is a candidate service platform, and the entity corresponding to each candidate vehicle model node is a candidate vehicle model. In response to a click operation on a target service platform node among the multiple candidate service platform nodes, the terminal displays the first knowledge graph of that target service platform, where clicking on the target service platform node indicates that the target service platform has been selected from the multiple candidate service platforms.

[0110] In this implementation, the terminal can display an initial knowledge graph, which graphically shows the relationship between multiple candidate service platforms and multiple candidate vehicle models, providing technicians with richer information. Technicians can also use this initial graph to select the correspondence between the target service platform and vehicle model they want to view further, thus improving the efficiency of human-computer interaction.

[0111] 306. In response to a click operation on any vehicle model node in the first knowledge graph, the terminal displays a second knowledge graph under the vehicle model node. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node, and the entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node.

[0112] In this context, the second knowledge graph under the vehicle model node refers to a knowledge graph subordinate to that vehicle model node; in other words, the second knowledge graph is a knowledge graph at the next lower level than that vehicle model node. Service nodes correspond to entities that are services provided by the target service platform, such as navigation services, multimedia playback services, and vehicle detection services. Functional systems refer to the set of hardware required in a vehicle to achieve a specific function; for example, the implementation of navigation depends on a navigation system. The second knowledge graph describes the relationships between these multiple service nodes and multiple functional system nodes, that is, it describes the relationships between the various services provided by the target service platform and the various functional systems of the vehicle model. In other words, the second knowledge graph displays the correspondence between the services provided by the target service platform and the functional systems of the vehicle model. By viewing the second knowledge graph, technicians can know which functional system the services provided by the target service platform are applied to, reducing the difficulty for technicians to query the correspondence between services and functional systems and improving the efficiency of human-computer interaction. In some embodiments, the method of viewing other knowledge graphs by clicking on nodes is also called drill-down.

[0113] In one possible implementation, in response to a click operation on any vehicle model node in the first knowledge graph, the terminal acquires the plurality of functional system nodes under that vehicle model node, the plurality of service nodes under the target service platform node, and the association data between the plurality of functional system nodes and the plurality of service nodes. Based on the association data between the plurality of functional system nodes and the plurality of service nodes, the terminal adds connections between the plurality of functional system nodes and the plurality of service nodes to generate the second knowledge graph. The terminal displays the second knowledge graph.

[0114] In this implementation, the terminal can generate a second knowledge graph based on the selected vehicle model node, without having to generate the second knowledge graph in advance, thus reducing the storage space occupied. At the same time, the real-time generated second knowledge graph also has greater flexibility.

[0115] For example, in response to a click on any vehicle model node in the first knowledge graph, the terminal sends a function system retrieval request to the server. This request carries the vehicle model corresponding to the vehicle model node. The server is a data server built by the car manufacturer. The server receives the function system retrieval request and retrieves the vehicle model corresponding to the vehicle model node and the identifier of the target service platform from the request. The server queries based on the vehicle model to obtain multiple function systems for that vehicle model. The server queries based on the identifier of the target service platform to obtain multiple services provided by the target service platform. The server queries based on the multiple function systems and services to obtain association data between the multiple function systems and services. This association data represents the correspondence between function systems and services. The server sends the multiple function systems, services, and association data to the terminal, which receives them. The terminal generates multiple function system nodes corresponding to each of the multiple function systems and multiple service nodes corresponding to each of the multiple services. Based on the association data, the terminal adds connections between the multiple function system nodes and service nodes to obtain the second knowledge graph. The terminal displays the second knowledge graph. For example, see Figure 6 The terminal displays a second knowledge graph 600, which includes multiple service nodes 601-603 and multiple functional system nodes 604-606.

[0116] It should be noted that the above description is based on the example of the terminal generating the second knowledge graph. In other possible implementations, the second knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0117] In some embodiments, the second knowledge graph, in addition to displaying the relationships between service nodes and functional system nodes, can also display the relationships between the multiple service nodes and the multiple functional system nodes. The relationships between the multiple service nodes refer to the dependencies between the services corresponding to the service nodes. For example, if there is a connection between service node C and service node D, it means that the service corresponding to service node C depends on the service corresponding to service node D, and vice versa. Correspondingly, the relationships between the multiple functional system nodes refer to the physical connectivity of the functional systems corresponding to the multiple functional system nodes. For example, the electrical connection between the positioning functional system and the communication functional system.

[0118] In one possible implementation, in response to a click operation on any vehicle model node in the first knowledge graph, the terminal displays a knowledge graph selection pop-up window for that vehicle model node. This pop-up window displays multiple types of knowledge graphs under that vehicle model node, with different types of knowledge graphs used to demonstrate the relationships between different types of nodes under that vehicle model node. If the second knowledge graph is selected from among these multiple types of knowledge graphs, the terminal displays that second knowledge graph.

[0119] In this implementation, clicking on the vehicle model node displays a knowledge graph selection pop-up. Through the knowledge graph selection pop-up, users can select multiple types of knowledge graphs under the vehicle model node. Different types of knowledge graphs can reflect the correspondence between different levels of nodes under that vehicle model node, enriching the display format of the knowledge graph, providing technicians with more types of knowledge graphs, and improving the degree of data visualization.

[0120] For example, see Figure 5 , Figure 6 and Figure 7 In response to a click on any vehicle model node 502 in the first knowledge graph 500, the terminal displays a knowledge graph selection pop-up window 700 for that vehicle model node 502. This pop-up window 700 displays multiple knowledge graphs 701-704 under that vehicle model node. In response to a click on the second knowledge graph 702 within the multiple knowledge graphs 701-704, the terminal displays the second knowledge graph 600.

[0121] Optionally, based on the above implementation, when the fourth knowledge graph among the multiple knowledge graphs is selected, the terminal displays the fourth knowledge graph, which includes multiple manufacturer nodes and multiple component nodes. The fourth knowledge graph is used to display the association between the multiple manufacturer nodes and the multiple component nodes, and the entity corresponding to the component node is the component used by the vehicle model corresponding to the vehicle model node.

[0122] The concept of components here differs from the previously described functional systems. A functional system comprises multiple components; that is, a collection of multiple components constitutes a functional system. The fourth knowledge graph illustrates the relationships between components and manufacturers, specifically which manufacturer supplies the components in the vehicle. In some embodiments, a component may be jointly produced by multiple manufacturers. In this fourth knowledge graph, a component node may be associated with multiple manufacturer nodes. Conversely, a manufacturer may also produce multiple components simultaneously, thus a manufacturer node may be associated with multiple component nodes.

[0123] For example, in response to a click on any vehicle model node in the first knowledge graph, the terminal displays a knowledge graph selection pop-up window for that vehicle model node. In response to a click on the fourth knowledge graph in the knowledge graph selection pop-up window, the terminal displays the fourth knowledge graph. For example, see... Figure 7 and Figure 8 In response to a click operation on the fourth knowledge graph 704 among the multiple knowledge graphs 701-704, the terminal displays the fourth knowledge graph 800, which includes multiple manufacturer nodes 801-804 and multiple component nodes 805-808.

[0124] Optionally, after displaying the second knowledge graph, the terminal can also perform any of the following steps.

[0125] In one possible implementation, the second knowledge graph displays a return control, and in response to a click operation on the return control, the terminal switches the second knowledge graph to the first knowledge graph.

[0126] In this implementation, a return control is provided in the second knowledge graph. By clicking the return control, users can quickly return to the first knowledge graph for display. This helps technicians to trace back the first knowledge graph and select other nodes on the first knowledge graph for viewing, thus improving the efficiency of human-computer interaction.

[0127] For example, see Figure 5 and Figure 6 The second knowledge graph displays a return control 607. In response to a click on the return control 607, the terminal switches the second knowledge graph 600 to the first knowledge graph 500.

[0128] In one possible implementation, the second knowledge graph displays an export control, and in response to a click operation on the export control, the terminal exports the second knowledge graph as an image.

[0129] In this implementation, an export control is provided on the second knowledge graph, which can be quickly exported as an image for storage and sharing, thus improving the efficiency of human-computer interaction.

[0130] For example, see Figure 6The second knowledge graph 600 displays an export control 608. In response to clicking the export control 608, the terminal displays an image export pop-up window, which includes a storage location selection area and a confirmation control. When a storage location for the image is selected through the storage location selection area, in response to clicking the confirmation control, the terminal exports the second knowledge graph as an image. In some embodiments, the image export pop-up window further includes at least one of an export image preview area and an export image naming area, wherein the export image preview area is used to preview the second knowledge graph, and the naming area is used to name the exported image.

[0131] In one possible implementation, the second knowledge graph displays a zoom-in control, and in response to a click operation on the zoom-in control, the terminal zooms in on the second knowledge graph.

[0132] In this implementation, a zoom control is provided on the second knowledge graph, which allows for quick zooming in of the second knowledge graph to facilitate more detailed observation of its local areas, thereby improving the efficiency of human-computer interaction.

[0133] For example, see Figure 6 The second knowledge graph 600 displays a zoom control 609. In response to a click on the zoom control 609, the terminal zooms in on the second knowledge graph 600. In some embodiments, in addition to zooming in on the second knowledge graph as a whole via the zoom control, the terminal can also zoom in on a specific part of the second knowledge graph. This application embodiment does not limit this.

[0134] Optionally, after step 306, the terminal can execute the following steps 308, 310 or 312, which is not limited in this embodiment.

[0135] 308. In response to a click operation on any functional system node in the second knowledge graph, the terminal displays a fifth knowledge graph under the functional system node. The fifth knowledge graph includes the functional system node and multiple component nodes. The fifth knowledge graph is used to display the association relationship between the functional system node and the multiple component nodes. The entity corresponding to the component node is a component in the functional system corresponding to the functional system node.

[0136] The fifth knowledge graph under a functional system node refers to a knowledge graph that belongs to that functional system node; in other words, it is a knowledge graph at the next lower level of that functional system node. The fifth knowledge graph illustrates the component composition of the functional system.

[0137] In one possible implementation, in response to a click operation on any functional system node in the second knowledge graph, the terminal obtains multiple components in the functional system corresponding to that functional system node. Based on these multiple components, the terminal generates multiple component nodes, and adds connections between these component nodes and the functional system node to obtain the fifth knowledge graph. The terminal then displays the fifth knowledge graph.

[0138] In this implementation, the terminal can generate the fifth knowledge graph based on the selected functional system node, without having to generate the fifth knowledge graph in advance, thus reducing the storage space occupied. At the same time, the real-time generated fifth knowledge graph also has greater flexibility.

[0139] For example, in response to a click on any functional system node in the second knowledge graph, the terminal sends a component retrieval request to the server. This request carries the functional system corresponding to the functional system node. The server is a data server built by an automotive manufacturer. The server receives the component retrieval request and retrieves the functional system corresponding to the functional system node from it. The server queries based on this functional system to obtain multiple components within it. The server sends these components to the terminal, which receives them. The terminal generates multiple component nodes corresponding to these components and adds connections between the functional system node and the component nodes to obtain the fifth knowledge graph. The terminal then displays the fifth knowledge graph. For example, see [link to relevant documentation]. Figure 9 The terminal displays the fifth knowledge graph 900, which includes a functional system node 901 and multiple component nodes 902-906.

[0140] It should be noted that the above description is based on the example of the fifth knowledge graph being generated by the terminal. In other possible implementations, the fifth knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0141] 310. In response to a drag operation on any service node in the second knowledge graph, the terminal displays a sixth knowledge graph under the service node. The sixth knowledge graph includes the service node and multiple associated service nodes. The sixth knowledge graph is used to display the association between the service node and the multiple associated service nodes. The entity corresponding to the associated service node is a service associated with the entity corresponding to the service node.

[0142] The sixth knowledge graph under a service node refers to a knowledge graph that belongs to that service node; in other words, it is the knowledge graph at the next level below that service node. The sixth knowledge graph illustrates the relationships between the services provided by the target service platform.

[0143] In one possible implementation, in response to a drag operation on any service node in the second knowledge graph, the terminal obtains multiple associated services that have dependencies on the service corresponding to that service node. Based on these multiple associated services, the terminal generates multiple associated service nodes, and adds connections between these multiple associated service nodes and the service node to obtain the sixth knowledge graph. The terminal displays the sixth knowledge graph.

[0144] In this implementation, the terminal can generate the sixth knowledge graph based on the service node after dragging the service node, without having to generate the sixth knowledge graph in advance, thus reducing the storage space occupied. At the same time, the sixth knowledge graph generated in real time also has greater flexibility.

[0145] For example, in response to a drag operation on any service node in the second knowledge graph, the terminal sends a service retrieval request to the server. This request carries the service corresponding to the service node. The server is a data server built by an automotive manufacturer. The server receives the service retrieval request and retrieves the service corresponding to the service node from it. The server queries based on this service to obtain multiple related services that have dependencies on it. The server sends these related services to the terminal, which receives them. The terminal generates multiple related service nodes corresponding to these related services and adds connections between these service nodes to obtain the sixth knowledge graph. The terminal displays this sixth knowledge graph. For example, see [link to relevant documentation]. Figure 10 The terminal displays the sixth knowledge graph 1000, which includes service node 1001 and multiple associated service nodes 1002-1006.

[0146] It should be noted that the above description is based on the example of the sixth knowledge graph being generated by the terminal. In other possible implementations, the sixth knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0147] 312. In response to a click operation on any service node in the second knowledge graph, the terminal displays a third knowledge graph under the service node. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system.

[0148] In this context, a third knowledge graph under a service node refers to a knowledge graph subordinate to that service node; in other words, it is the knowledge graph at the next lower level of that service node. The third knowledge graph displays the relationships between services and service data. The attributes of service data include at least one of the following: data type, data format, data flow direction, and data value range. When the entity corresponding to the service data node is a data type, the third knowledge graph displays the relationship between the service and the data type; when the entity corresponding to the service data node is a data flow direction, the third knowledge graph displays the relationship between the service and the data flow direction.

[0149] In one possible implementation, in response to a click operation on any service node in the second knowledge graph, the terminal obtains multiple service data used by the service corresponding to that service node. Based on the multiple service data, the terminal generates multiple service data nodes, and adds connections between the multiple service data nodes and the service node to obtain the third knowledge graph. The terminal displays the third knowledge graph.

[0150] In this implementation, the terminal can generate a third knowledge graph based on the service node after dragging the service node, without having to generate the third knowledge graph in advance, thus reducing the storage space occupied. At the same time, the real-time generated third knowledge graph also has greater flexibility.

[0151] For example, in response to a click on any service node in the second knowledge graph, the terminal sends a service retrieval request to the server. This request carries the service corresponding to the service node. The server is a data server built by an automotive manufacturer. The server receives the service retrieval request and retrieves the service corresponding to the service node from it. The server queries based on this service to obtain multiple service data used by that service. The server sends this multiple service data to the terminal, which receives it. The terminal generates multiple service data nodes corresponding to the service data, and adds connections between these service nodes to obtain the third knowledge graph. The terminal displays the third knowledge graph. For example, see [link to relevant documentation]. Figure 11 The terminal displays a third knowledge graph 1100, which includes a service node 1101 and multiple service data nodes 1102-1106.

[0152] It should be noted that the above description is based on the example of the terminal generating the third knowledge graph. In other possible implementations, the third knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0153] Furthermore, the above explanation uses a third knowledge graph comprising service nodes and one type of service data node as an example. In other possible implementations, the third knowledge graph may include service nodes and multiple types of service data nodes. Different types of service data nodes are used to display different attributes of service data. In some embodiments, in this third knowledge graph, service nodes may be connected to first-type service data nodes, first-type service data nodes may be connected to second-type service data nodes, and second-type service data nodes may be connected to third-type service data nodes. The first-type, second-type, and third-type service data nodes are used to display different attributes of service data. For example, the entity corresponding to the first-type service data node is the data type of the service data, the entity corresponding to the second-type service data node is the data format of the service data, and the entity corresponding to the third-type service data node is the value range of the service data. The third knowledge graph displayed in this way can more comprehensively display the attributes of service data, and the data visualization effect is better. For example, see... Figure 12 The terminal displays a third knowledge graph 1200, which includes service nodes 1201, first-type service data nodes 1202, second-type service data nodes 1203, and third-type service data nodes 1204.

[0154] Optionally, after step 312 above, the terminal may also perform any of the following steps.

[0155] 314. In response to a click operation on any service data node in the third knowledge graph, the terminal displays an attribute display pop-up window, which displays at least one of the following: data type, data format, data flow direction, and data value range of the service data corresponding to the service data node.

[0156] The attribute display pop-up is used to display the attributes of the service data. The attributes of the service data include at least one of the following: data type, data format, data flow direction, and data value range.

[0157] For example, see Figure 11 and Figure 13 In response to a click operation on any service data node 1102 in the third knowledge graph 1100, the terminal displays an attribute display pop-up window 1300, which displays the attributes of the service data corresponding to the service data node 1102.

[0158] 316. In response to a click operation on the service node in the third knowledge graph, the terminal displays the seventh knowledge graph under the service node. The seventh knowledge graph includes the service node and multiple interface nodes. The seventh knowledge graph is used to display the relationship between the service node and the multiple interface nodes.

[0159] In one possible implementation, in response to a click operation on any service node in the third knowledge graph, the terminal obtains multiple interfaces for service calls corresponding to that service node. Based on these multiple interfaces, the terminal generates multiple interface nodes, and adds connections between these interface nodes and the service node to obtain the seventh knowledge graph. The terminal then displays the seventh knowledge graph.

[0160] In this implementation, the terminal can generate the seventh knowledge graph based on the selected service node, without having to generate the seventh knowledge graph in advance, thus reducing the storage space occupied. At the same time, the real-time generated seventh knowledge graph also has greater flexibility.

[0161] For example, in response to a click on any service node in the third knowledge graph, the terminal sends an interface retrieval request to the server. This request carries the service corresponding to the service node. The server is a data server built by an automotive manufacturer. The server receives the interface retrieval request and retrieves the service corresponding to the service node from it. The server queries based on this service to obtain multiple interfaces called by that service. The server sends these multiple interfaces to the terminal, which receives them. The terminal generates multiple interface nodes corresponding to these interfaces and adds connections between the service node and these interface nodes to obtain the seventh knowledge graph. The terminal displays this seventh knowledge graph. See, for example, [link to relevant documentation]. Figure 14 The terminal displays the seventh knowledge graph 1400, which includes service node 1401 and multiple interface nodes 1402-1406.

[0162] It should be noted that the above description is based on the example of the seventh knowledge graph being generated by the terminal. In other possible implementations, the seventh knowledge graph can also be generated by the server, and this application embodiment does not limit this.

[0163] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0164] The technical solution provided in this application allows the terminal to display the relationships between a target service platform and multiple vehicle models by showing a first knowledge graph. Operations on the first knowledge graph trigger the display of a second knowledge graph, which displays the relationships between the target service platform and the functional systems of the corresponding vehicle models. Compared to the first knowledge graph, the second knowledge graph provides a deeper understanding of the relationship between the platform and the vehicle models. Operations on the second knowledge graph can further trigger the display of a third knowledge graph, which visualizes the relationships between services and service data. This helps technicians quickly obtain information and improves the efficiency of vehicle model maintenance and iterative updates. Furthermore, the three knowledge graphs display the relationships between related entities at different levels, allowing technicians to efficiently search for relevant information.

[0165] Figure 15 This is a schematic diagram of the structure of a vehicle-based knowledge graph display device provided in an embodiment of this application. See also... Figure 15 The device includes: a first knowledge graph display module 1501, a second knowledge graph display module 1502, and a third knowledge graph display module 1503.

[0166] The first knowledge graph display module 1501 is used to display the first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the relationship between the target service platform node and the multiple vehicle model nodes.

[0167] The second knowledge graph display module 1502 is used to respond to a click operation on any vehicle model node in the first knowledge graph and display the second knowledge graph under that vehicle model node. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to show the relationship between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node, and the entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node.

[0168] The third knowledge graph display module 1503 is used to respond to a click operation on any service node in the second knowledge graph and display the third knowledge graph under the service node. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to show the relationship between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system.

[0169] In one possible implementation, the second knowledge graph display module 1502 is configured to, in response to a click operation on any vehicle model node in the first knowledge graph, acquire the plurality of functional system nodes under that vehicle model node, the plurality of service nodes under the target service platform node, and the association data between the plurality of functional system nodes and the plurality of service nodes. Based on the association data between the plurality of functional system nodes and the plurality of service nodes, connections are added between the plurality of functional system nodes and the plurality of service nodes to generate the second knowledge graph. The second knowledge graph is then displayed.

[0170] In one possible implementation, the second knowledge graph display module 1502 is configured to, in response to a click operation on any vehicle model node in the first knowledge graph, display a knowledge graph selection pop-up window for that vehicle model node. This pop-up window displays multiple types of knowledge graphs under that vehicle model node, with different types of knowledge graphs used to demonstrate the relationships between different types of nodes under that vehicle model node. When the second knowledge graph is selected among these multiple types of knowledge graphs, that second knowledge graph is displayed.

[0171] In one possible implementation, the device further includes:

[0172] The fourth knowledge graph display module is used to display the fourth knowledge graph when it is selected among the multiple knowledge graphs. The fourth knowledge graph includes multiple manufacturer nodes and multiple component nodes. The fourth knowledge graph is used to display the relationship between the multiple manufacturer nodes and the multiple component nodes. The entity corresponding to the component node is the component used by the vehicle model corresponding to the vehicle model node.

[0173] In one possible implementation, the device further includes any of the following:

[0174] The switching module is used to switch the second knowledge graph to the first knowledge graph in response to a click operation on the return control, where a return control is displayed.

[0175] The export module is used when an export control is displayed in the second knowledge graph. In response to a click operation on the export control, the second knowledge graph is exported as an image.

[0176] The zoom-in module is used to display a zoom-in control in the second knowledge graph, and to zoom in on the second knowledge graph in response to a click operation on the zoom-in control.

[0177] In one possible implementation, the device further includes:

[0178] The fifth knowledge graph display module is used to respond to a click operation on any functional system node in the second knowledge graph and display the fifth knowledge graph under the functional system node. The fifth knowledge graph includes the functional system node and multiple component nodes. The fifth knowledge graph is used to show the relationship between the functional system node and the multiple component nodes. The entity corresponding to the component node is the component in the functional system corresponding to the functional system node.

[0179] In one possible implementation, the device further includes:

[0180] The sixth knowledge graph display module is used to display the sixth knowledge graph under any service node in the second knowledge graph in response to a drag operation. The sixth knowledge graph includes the service node and multiple associated service nodes. The sixth knowledge graph is used to show the relationship between the service node and the multiple associated service nodes. The entity corresponding to the associated service node is the service associated with the entity corresponding to the service node.

[0181] In one possible implementation, the device further includes:

[0182] The attribute display pop-up module is used to display an attribute display pop-up in response to a click operation on any service data node in the third knowledge graph. The attribute display pop-up displays at least one of the following: data type, data format, data flow direction, and data value range of the service data corresponding to the service data node.

[0183] In one possible implementation, the device further includes:

[0184] The seventh knowledge graph display module is used to respond to the click operation of the service node in the third knowledge graph and display the seventh knowledge graph under the service node. The seventh knowledge graph includes the service node and multiple interface nodes. The seventh knowledge graph is used to show the relationship between the service node and the multiple interface nodes.

[0185] In one possible implementation, the device further includes:

[0186] The service platform selection interface display module is used to display the service platform selection interface, which shows multiple candidate service platforms.

[0187] The first knowledge graph display module 1501 is used to display the first knowledge graph of the target service platform when the target service platform is selected among the multiple candidate service platforms.

[0188] It should be noted that the vehicle-based knowledge graph display device provided in the above embodiments is only illustrated by the division of the above functional modules when displaying the knowledge graph. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the computer device can be divided into different functional modules to complete all or part of the functions described above. In addition, the vehicle-based knowledge graph display device and the vehicle-based knowledge graph display method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0189] The technical solution provided in this application allows the terminal to display the relationships between a target service platform and multiple vehicle models by showing a first knowledge graph. Operations on the first knowledge graph trigger the display of a second knowledge graph, which displays the relationships between the target service platform and the functional systems of the corresponding vehicle models. Compared to the first knowledge graph, the second knowledge graph provides a deeper understanding of the relationship between the platform and the vehicle models. Operations on the second knowledge graph can further trigger the display of a third knowledge graph, which visualizes the relationships between services and service data. This helps technicians quickly obtain information and improves the efficiency of vehicle model maintenance and iterative updates. Furthermore, the three knowledge graphs display the relationships between related entities at different levels, allowing technicians to efficiently search for relevant information.

[0190] This application provides a computer device for performing the above-described method. The computer device can be implemented as a terminal, and the structure of the terminal is described below.

[0191] Figure 16 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal 1600 can be: a vehicle terminal, a smartphone, a tablet computer, a laptop computer, or a desktop computer.

[0192] Typically, terminal 1600 includes one or more processors 1601 and one or more memories 1602.

[0193] Processor 1601 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1601 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1601 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1601 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1601 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0194] The memory 1602 may include one or more computer-readable storage media, which may be non-transitory. The memory 1602 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1602 are used to store at least one computer program, which is executed by the processor 1601 to implement the vehicle-type-based knowledge graph display method provided in the method embodiments of this application.

[0195] In some embodiments, the terminal 1600 may also optionally include a peripheral device interface 1603 and at least one peripheral device. The processor 1601, memory 1602, and peripheral device interface 1603 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1603 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1604, a display screen 1605, a camera assembly 1606, an audio circuit 1607, and a power supply 1608.

[0196] Peripheral interface 1603 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1601 and memory 1602. In some embodiments, processor 1601, memory 1602 and peripheral interface 1603 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1601, memory 1602 and peripheral interface 1603 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0197] The radio frequency (RF) circuit 1604 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1604 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1604 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1604 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc.

[0198] Display screen 1605 is used to display a user interface (UI). This UI may include graphics, text, icons, video, and any combination thereof. When display screen 1605 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1601 for processing. In this case, display screen 1605 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard.

[0199] The camera assembly 1606 is used to capture images or videos. Optionally, the camera assembly 1606 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal.

[0200] The audio circuit 1607 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals that are input to the processor 1601 for processing, or input to the radio frequency circuit 1604 to realize voice communication.

[0201] The power supply 1608 is used to supply power to the various components in the terminal 1600. The power supply 1608 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery.

[0202] In some embodiments, the terminal 1600 further includes one or more sensors 1609. The one or more sensors 1609 include, but are not limited to: an accelerometer 1610, a gyroscope 1611, a pressure sensor 1612, an optical sensor 1613, and a proximity sensor 1614.

[0203] Accelerometer 1610 can detect the magnitude of acceleration on the three coordinate axes of a coordinate system established with terminal 1600.

[0204] The gyroscope sensor 1611 can detect the orientation and rotation angle of the terminal 1600. The gyroscope sensor 1611 can work in conjunction with the accelerometer sensor 1610 to collect the user's 3D movements on the terminal 1600.

[0205] The pressure sensor 1612 can be installed on the side bezel of the terminal 1600 and / or on the lower layer of the display screen 1605. When the pressure sensor 1612 is installed on the side bezel of the terminal 1600, it can detect the user's grip signal on the terminal 1600, and the processor 1601 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1612. When the pressure sensor 1612 is installed on the lower layer of the display screen 1605, the processor 1601 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1605.

[0206] An optical sensor 1613 is used to collect ambient light intensity. In one embodiment, a processor 1601 can control the display brightness of a display screen 1605 based on the ambient light intensity collected by the optical sensor 1613.

[0207] The proximity sensor 1614 is used to detect the distance between the user and the front of the terminal 1600.

[0208] Those skilled in the art will understand that Figure 12 The structure shown does not constitute a limitation on terminal 1600 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0209] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including a computer program that can be executed by a processor to complete the vehicle-type-based knowledge graph display method in the above embodiments. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, or optical data storage device, etc.

[0210] In an exemplary embodiment, a computer program product or computer program is also provided, which includes program code stored in a computer-readable storage medium. The processor of a computer device reads the program code from the computer-readable storage medium and executes the program code, causing the computer device to perform the above-described vehicle model-based knowledge graph display method.

[0211] In some embodiments, the computer program involved in the present application embodiments may be deployed and executed on a computer device, or executed on multiple computer devices located in one location, or executed on multiple computer devices distributed in multiple locations and interconnected through a communication network. Multiple computer devices distributed in multiple locations and interconnected through a communication network may constitute a blockchain system.

[0212] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0213] The above are merely optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A knowledge graph display method based on vehicle models, characterized in that, The method includes: Display a first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the association between the target service platform node and the multiple vehicle model nodes. In response to a click operation on any vehicle model node in the first knowledge graph, a second knowledge graph under the vehicle model node is displayed. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association relationship between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node. The entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node. The functional system refers to the set of hardware required in the vehicle to achieve a specific function. The second knowledge graph is the knowledge graph at the next level below the vehicle model node. In response to a click operation on any service node in the second knowledge graph, a third knowledge graph under the service node is displayed. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system. Wherein, after displaying the second knowledge graph under the vehicle model node in response to a click operation on any vehicle model node in the first knowledge graph, the method further includes any one of the following: The second knowledge graph displays a return control, and in response to a click operation on the return control, the second knowledge graph is switched to the first knowledge graph; The second knowledge graph displays an export control. In response to a click operation on the export control, the second knowledge graph is exported as an image. The second knowledge graph displays a zoom-in control, and the second knowledge graph is zoomed in in response to a click operation on the zoom-in control.

2. The method according to claim 1, characterized in that, The step of displaying the second knowledge graph under any vehicle model node in the first knowledge graph in response to a click operation includes: In response to a click operation on any vehicle model node in the first knowledge graph, the multiple functional system nodes under the vehicle model node, the multiple service nodes under the target service platform node, and the association data between the multiple functional system nodes and the multiple service nodes are obtained. Based on the association data between the multiple functional system nodes and the multiple service nodes, connections are added between the multiple functional system nodes and the multiple service nodes to generate the second knowledge graph; The second knowledge graph is displayed.

3. The method according to claim 1, characterized in that, The step of displaying the second knowledge graph under any vehicle model node in the first knowledge graph in response to a click operation includes: In response to a click operation on any vehicle model node in the first knowledge graph, a knowledge graph selection pop-up window for the vehicle model node is displayed. The knowledge graph selection pop-up window displays multiple types of knowledge graphs under the vehicle model node. Different types of knowledge graphs are used to demonstrate the relationship between different types of nodes under the vehicle model node. If the second knowledge graph is selected among the multiple types of knowledge graphs, the second knowledge graph is displayed.

4. The method according to claim 3, characterized in that, After displaying the knowledge graph selection pop-up window for the vehicle model node in response to a click operation on any vehicle model node in the first knowledge graph, the method further includes: When the fourth knowledge graph among the multiple knowledge graphs is selected, the fourth knowledge graph is displayed. The fourth knowledge graph includes multiple manufacturer nodes and multiple component nodes. The fourth knowledge graph is used to display the association relationship between the multiple manufacturer nodes and the multiple component nodes. The entity corresponding to the component node is the component used by the vehicle model corresponding to the vehicle model node.

5. The method according to claim 1, characterized in that, After responding to a click operation on any vehicle model node in the first knowledge graph and displaying the second knowledge graph under that vehicle model node, the method further includes: In response to a click operation on any functional system node in the second knowledge graph, a fifth knowledge graph under the functional system node is displayed. The fifth knowledge graph includes the functional system node and multiple component nodes. The fifth knowledge graph is used to display the association relationship between the functional system node and the multiple component nodes. The entity corresponding to the component node is a component in the functional system corresponding to the functional system node.

6. The method according to any one of claims 1-5, characterized in that, After responding to a click operation on any vehicle model node in the first knowledge graph and displaying the second knowledge graph under that vehicle model node, the method further includes: In response to a drag operation on any service node in the second knowledge graph, a sixth knowledge graph under the service node is displayed. The sixth knowledge graph includes the service node and multiple associated service nodes. The sixth knowledge graph is used to display the association relationship between the service node and the multiple associated service nodes. The entity corresponding to the associated service node is a service associated with the entity corresponding to the service node.

7. The method according to any one of claims 1-5, characterized in that, After displaying the third knowledge graph under any service node in the second knowledge graph in response to a click operation, the method further includes: In response to a click operation on any service data node in the third knowledge graph, an attribute display pop-up window is displayed, which displays at least one of the following: data type, data format, data flow direction, and data value range of the service data corresponding to the service data node.

8. A knowledge graph display device based on vehicle models, characterized in that, The device includes: The first knowledge graph display module is used to display the first knowledge graph, which includes a target service platform node and multiple vehicle model nodes. The first knowledge graph is used to display the association relationship between the target service platform node and the multiple vehicle model nodes. The second knowledge graph display module is used to respond to a click operation on any vehicle model node in the first knowledge graph and display the second knowledge graph under the vehicle model node. The second knowledge graph includes multiple service nodes and multiple functional system nodes. The second knowledge graph is used to display the association relationship between the multiple service nodes and the multiple functional system nodes. The entity corresponding to the service node is the service provided by the service platform corresponding to the target service platform node. The entity corresponding to the functional system node is the functional system of the vehicle model corresponding to the vehicle model node. The functional system refers to the set of hardware required in the vehicle to achieve a specific function. The second knowledge graph is the knowledge graph at the next level below the vehicle model node. The third knowledge graph display module is used to respond to a click operation on any service node in the second knowledge graph and display the third knowledge graph under the service node. The third knowledge graph includes the service node and multiple service data nodes. The third knowledge graph is used to display the association relationship between the service node and the multiple service data nodes. The entity corresponding to the service data node is the attribute of the service data transmitted to the corresponding functional system. A switching module is used to switch the second knowledge graph to the first knowledge graph in response to a click operation on the return control, where a return control is displayed in the second knowledge graph. An export module is used to export the second knowledge graph as an image in response to a click operation on the export control, where an export control is displayed in the second knowledge graph. A zoom-in module is used to display a zoom-in control in the second knowledge graph, and to zoom in on the second knowledge graph in response to a click operation on the zoom-in control.

9. A computer device, characterized in that, The computer device includes one or more processors and one or more memories, wherein at least one computer program is stored in the one or more memories, and the computer program is loaded and executed by the one or more processors to implement the vehicle-based knowledge graph display method as described in any one of claims 1 to 7.

Images