A method, device and equipment for querying vehicle information
By parsing the user's vehicle query request, the system automatically determines the query type and target vehicle, and calls the vehicle status interface to obtain data. This solves the problem of cumbersome vehicle information queries in existing technologies and achieves an efficient and convenient query process.
Patent Information
- Application Number
- CN202611377649.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-07
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, vehicle information retrieval is inefficient, requiring users to perform multiple steps and manually search for the target vehicle when associating multiple vehicles, which affects convenience and efficiency.
By parsing the user's vehicle query request, the system automatically determines the query type and target vehicle, calls the vehicle status interface to obtain vehicle status data, and generates query results, thus simplifying the query process.
It reduces the number of manual steps required by users, improves the efficiency and convenience of vehicle information retrieval, and enhances the accuracy and flexibility of target vehicle identification.
Smart Images

Figure CN123115191A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle networking technology, and in particular to a method, device and equipment for querying vehicle information. Background Technology
[0002] With the development of vehicle networking, vehicles can interact with each other through vehicle terminals, communication networks and service platforms to provide vehicle information such as location, battery level, remaining mileage, operating status and charging status.
[0003] Currently, when users query vehicle information, they need to access an application provided by the vehicle manufacturer and perform operations such as searching and selecting to obtain the vehicle information of the target vehicle. Because users need to perform multiple steps, the overall operation process is lengthy, resulting in low efficiency in vehicle information querying.
[0004] Therefore, there is an urgent need for a solution to address the aforementioned technical problems. Summary of the Invention
[0005] Based on the above problems, this application provides a vehicle information query method, device, and equipment to solve the problem of low efficiency in vehicle information query.
[0006] The embodiments of this application disclose the following technical solutions: Firstly, this application provides a vehicle information query method, comprising: parsing a vehicle query request input by a user to determine the query type and target vehicle corresponding to the vehicle query request; determining the target vehicle from at least one vehicle associated with the user; calling a vehicle status interface to obtain vehicle status data corresponding to the target vehicle; and generating a vehicle query result corresponding to the vehicle query request based on the query type and the vehicle status data.
[0007] In this embodiment, by parsing the vehicle query request input by the user, the query type and target vehicle corresponding to the query request can be determined. The target vehicle can be automatically determined from at least one vehicle associated with the user, without requiring the user to manually search for or switch vehicles. After determining the target vehicle, the vehicle status data corresponding to the target vehicle is obtained by calling the vehicle status interface, and the corresponding vehicle query results are generated based on the query type and vehicle status data. This achieves automatic vehicle information query, effectively improving the efficiency and convenience of vehicle information query.
[0008] In one possible implementation, parsing the vehicle query request input by the user to determine the query type and target vehicle corresponding to the vehicle query request includes: parsing the vehicle query request input by the user to determine the query type and first information corresponding to the vehicle query request; the first information is used to indicate the specified status of the vehicle corresponding to the vehicle query request; and based on the first information, determining the target vehicle from at least one vehicle associated with the user.
[0009] In this embodiment, the vehicle that the user expects to query can be automatically identified based on the vehicle-specific information contained in the user's query request, avoiding the need for the user to manually search for the target vehicle among multiple associated vehicles. At the same time, when the user does not explicitly specify a vehicle, the corresponding target vehicle can be determined by combining the specified vehicle status, thereby improving the accuracy and flexibility of target vehicle determination and thus improving the efficiency of vehicle information query.
[0010] In one possible implementation, determining the target vehicle from at least one vehicle associated with the user based on the first information includes: when the vehicle's specified state is a specified vehicle state, obtaining vehicle identification information from the first information; determining the target vehicle from at least one vehicle associated with the user based on the vehicle identification information; when the vehicle's specified state is an unspecified vehicle state and the user is associated with one vehicle, determining the vehicle associated with the user as the target vehicle; when the vehicle's specified state is an unspecified vehicle state and the user is associated with multiple vehicles, outputting candidate vehicle information corresponding to the multiple vehicles; and determining the target vehicle based on the user's selection of the candidate vehicle information.
[0011] In this embodiment, the target vehicle determination needs can be adapted to different numbers of vehicles and different query scenarios, improving the accuracy and flexibility of target vehicle determination, reducing the manual search process for users, and improving the efficiency of vehicle information query.
[0012] In one possible implementation, determining the target vehicle from at least one vehicle associated with the user based on the first information includes: determining a target call path from at least one call path according to the query type; the at least one call path includes at least one of a skill call path and a model context protocol service call path; calling a vehicle list interface based on the target call path to obtain at least one vehicle associated with the user; and determining the target vehicle from the obtained at least one vehicle based on the first information.
[0013] In this embodiment, a suitable vehicle information acquisition method can be selected according to different query needs, thereby improving the flexibility of vehicle information acquisition. After acquiring the user's associated vehicles, the target vehicle can be further determined from the at least one vehicle based on the first information. This allows the target vehicle determination process to combine the user's query intent with vehicle information for matching, thereby improving the accuracy and reliability of target vehicle determination.
[0014] In one possible implementation, the step of calling the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle includes: obtaining remote query capability information corresponding to the target vehicle; and, if the remote query capability information indicates that the target vehicle supports remote querying, calling the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle.
[0015] In this embodiment, the remote query capability of the target vehicle is determined before performing a vehicle status query to avoid executing invalid interface calls for vehicles that do not support remote queries. Furthermore, by obtaining vehicle status data only from target vehicles with remote query capabilities, the success rate of vehicle status data acquisition can be improved, resource consumption caused by invalid requests can be reduced, and the stability of the vehicle information query process can be enhanced.
[0016] In one possible implementation, the method further includes: generating a first prompt message when the remote query capability information indicates that the target vehicle does not support remote query; the first prompt message is used to indicate that the target vehicle does not support remote query; and outputting the first prompt message.
[0017] In this embodiment, when the target vehicle status data cannot be obtained, the user is promptly informed of the reason, preventing the user from being unable to determine the specific problem due to query failure. Furthermore, by providing the user with a prompt message indicating that the vehicle does not support remote querying, the transparency and understandability of the vehicle information query process are improved, enhancing the user experience.
[0018] In one possible implementation, generating the vehicle query result corresponding to the vehicle query request based on the query type and the vehicle status data includes: performing at least one of the following processes on the vehicle status data: field mapping, unit unification, and status semantic transformation, to obtain processed vehicle status data; determining target status data from the processed vehicle status data according to the query type; and generating the vehicle query result based on the target status data.
[0019] In this embodiment, vehicle status data in different formats is converted into a unified data representation, improving the standardization and consistency of the vehicle status data. Based on this, target status data is determined from the processed vehicle status data according to the query type, and corresponding vehicle query results are generated. This ensures that the generated query results match the user's query needs, improving the accuracy and readability of the vehicle query results and enhancing the user's experience in obtaining vehicle information.
[0020] In one possible implementation, the step of calling the vehicle status interface includes: obtaining the access credential corresponding to the user; verifying the access credential; and, if the access credential verification is successful, calling the vehicle status interface based on the access credential.
[0021] In this embodiment, before calling the vehicle status interface, it is confirmed whether the user has the corresponding vehicle information access permission. If the access credential verification is successful, the vehicle status interface is called based on the access credential, which can avoid unauthorized access to vehicle status data and improve the security and reliability of the vehicle information query process. At the same time, by calling the interface based on the access credential, effective management of vehicle information access permissions for different users can be achieved, improving the security of the vehicle status data interaction process.
[0022] Secondly, embodiments of this application provide a vehicle information query device, including: Parsing unit, calling unit, and generation unit; The parsing unit is used to parse the vehicle query request input by the user, determine the query type and target vehicle corresponding to the vehicle query request; the target vehicle is determined from at least one vehicle associated with the user; The calling unit is used to call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle. The generation unit is used to generate vehicle query results corresponding to the vehicle query request based on the query type and the vehicle status data.
[0023] Third aspect: This application provides a computer device, which includes a processor and a memory; The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the steps of the method described above according to the instructions in the program code.
[0024] Fourth aspect: Embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method described above.
[0025] Fifth aspect: This application provides a computer program product, which, when run on a computer, enables the computer to perform the steps of the method described above.
[0026] Compared with the prior art, this application has the following beneficial effects: In this embodiment, by parsing the vehicle query request input by the user, the query type and target vehicle corresponding to the query request can be determined, and the target vehicle can be automatically determined from at least one vehicle associated with the user, eliminating the need for the user to manually search for or select a vehicle to query. After determining the target vehicle, the vehicle status data corresponding to the target vehicle is obtained by calling the vehicle status interface, and the vehicle query result corresponding to the vehicle query request is generated based on the query type and vehicle status data. Since this embodiment can automatically determine the corresponding target vehicle based on the vehicle query request input by the user, automatically obtain the corresponding vehicle status data of the target vehicle, and generate query results, it reduces the manual operation steps for users in the vehicle information query process, simplifies the vehicle information query process, solves the problem of the cumbersome and inconvenient information query process in the prior art, and improves the efficiency of vehicle information query. Attached Figure Description
[0027] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the 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.
[0028] Figure 1 A schematic diagram illustrating an application scenario provided in an embodiment of this application; Figure 2 A flowchart illustrating a vehicle information query method provided in this application embodiment; Figure 3 A flowchart for determining a target vehicle is provided as an embodiment of this application; Figure 4 This is a schematic diagram of a vehicle status data acquisition process provided in an embodiment of this application; Figure 5 This is a schematic diagram of a vehicle status data processing flow provided in an embodiment of this application; Figure 6 This is a schematic diagram of an abnormal information processing flow provided in an embodiment of this application; Figure 7 A general architecture diagram of a vehicle information query method provided in an embodiment of this application; Figure 8This is a schematic diagram of the structure of a vehicle information query device provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation
[0029] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.
[0030] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0031] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.
[0032] Currently, vehicle information can be queried through applications provided by vehicle manufacturers. Users can access these applications to find associated vehicles and obtain information such as location, battery level, remaining mileage, operating status, and charging status. However, due to the limited interaction of existing vehicle information query methods, users need to perform multiple steps through the application page to complete the query. This is especially true when a user has associated multiple vehicles, requiring them to manually search for the target vehicle from among them, which affects the convenience and efficiency of vehicle information queries.
[0033] For example, when a user needs to query information such as vehicle location and battery level, the user usually needs to first open the vehicle management application, log in to the corresponding account, enter the vehicle information query page, select the target vehicle from the list of associated vehicles, and then obtain the corresponding vehicle information. When a user associates multiple vehicles, the user needs to select based on information such as vehicle name and vehicle number, which increases the operational complexity of the vehicle information query process.
[0034] However, this method has at least the following problems: Firstly, this method requires users to perform multiple page operations, resulting in a lengthy query process that fails to meet users' needs for quickly obtaining vehicle information. Secondly, when a user has associated multiple vehicles, this method requires the user to manually search for and select the target vehicle, leading to low efficiency in determining the target vehicle. Thirdly, this method relies on a fixed application interaction method, making it difficult to automatically determine the query requirements and generate corresponding vehicle query results based on the user's input information, thus affecting the level of intelligence in vehicle information querying.
[0035] Based on this, this application provides a vehicle information query method, which obtains a vehicle query request input by the user, parses the vehicle query request, determines the query type and target vehicle corresponding to the vehicle query request, and the target vehicle needs to be determined from at least one vehicle associated with the user; calls the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle; and generates the vehicle query result corresponding to the vehicle query request based on the query type and vehicle status data.
[0036] This application embodiment can automatically determine the target vehicle based on the vehicle query request entered by the user, and obtain the vehicle data corresponding to the target vehicle to generate query results. Users do not need to manually search for vehicles or perform multi-step query operations. Therefore, it simplifies the vehicle information query process, reduces the complexity of vehicle information query operations, and improves the efficiency of vehicle information query.
[0037] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0038] See Figure 1 This figure is a schematic diagram of an application scenario provided by an embodiment of this application.
[0039] The vehicle information query method provided in this application can be applied to computer devices. In some embodiments, the computer device may include, but is not limited to, mobile phones, tablets, laptops, wearable electronic devices, smartwatches, and other electronic devices. This application does not impose any special limitations on the specific form of the computer device.
[0040] In this embodiment, computer device 1101 serves as a user terminal, interacting with server 1102. The user terminal may include a chat interface, desktop assistant, voice input, or other interactive interface, used to receive vehicle query requests input by the user and display the vehicle query results to the user.
[0041] For example, computer device 1101 can respond to user input operations in a chat interface, desktop assistant, voice entry or other interactive interface, obtain the vehicle query request input by the user, and send the vehicle query request to server 1102.
[0042] After receiving the vehicle query request, server 1102 can parse the vehicle query request to determine the query type and target vehicle corresponding to the vehicle query request; call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle; and generate the vehicle query result corresponding to the vehicle query request based on the query type and the vehicle status data.
[0043] After generating the vehicle query results, the server 1102 can send the vehicle query results to the computer device 1101 so that the computer device 1101 can display the vehicle query results to the user through the corresponding interactive method.
[0044] The following describes a vehicle information query method provided by an embodiment of this application with reference to the accompanying drawings. Figure 2 The figure is a flowchart of a vehicle information query method provided in an embodiment of this application, including S201-S203.
[0045] S201. Parse the vehicle query request input by the user to determine the query type and target vehicle corresponding to the vehicle query request.
[0046] The target vehicle is determined from at least one vehicle associated with the user.
[0047] In this embodiment, the vehicle query request input by the user may include query information entered by the user through a chat interface, desktop assistant, voice entry, or other interactive interface. The query type is used to indicate the type of vehicle information the user requests to query, such as vehicle location, battery level, remaining mileage, operating status, charging status, etc.
[0048] For example, when a user enters a vehicle query request such as "How much battery does my car have left?" or "How much battery does the vehicle have left?", the query type can be determined to be a battery query, and the remaining battery information of the target vehicle can be obtained. When a user enters a vehicle query request such as "How many kilometers can my car run?" or "How far can the remaining battery support driving?", the query type can be determined to be a mileage query, and the remaining driving mileage information of the target vehicle can be obtained.
[0049] Upon receiving a vehicle query request from a user, the request can be parsed to obtain the query type and information used to determine the target vehicle. The query type indicates the type of vehicle information the user wishes to query; the information used to determine the target vehicle is used to identify the target vehicle from at least one vehicle associated with the user.
[0050] For example, since a user may be associated with one or more vehicles, when querying vehicle information, the corresponding target vehicle can be determined based on the vehicle query request entered by the user, so as to obtain the vehicle status data corresponding to the target vehicle in the future.
[0051] In one possible implementation, S201 can be achieved through steps 211 to 212.
[0052] Step 211: Parse the vehicle query request entered by the user to determine the query type and first information corresponding to the vehicle query request.
[0053] The first information is used to indicate the specified vehicle status corresponding to the vehicle query request.
[0054] In this embodiment of the application, after receiving a vehicle query request input by a user, the vehicle query request can be parsed to obtain the query type corresponding to the vehicle query request and the first information. The first information can be understood as structured information obtained after parsing the vehicle query request, used to locate the target vehicle from at least one vehicle associated with the user.
[0055] For example, the first information may include, but is not limited to, vehicle designation status, vehicle identification type, and vehicle identification information. The vehicle designation status indicates whether the vehicle query request contains information for identifying the target vehicle; the vehicle identification type indicates the identification method used by the user when designating the vehicle; and the vehicle identification information represents the specific identification content corresponding to the vehicle designated by the user.
[0056] For example, when a user's vehicle query request contains information indicating the target vehicle, the specified vehicle status corresponding to the query request can be determined as the specified vehicle status, and the corresponding vehicle identification type and vehicle identification information can be further determined. For instance, when a user enters "How much battery does Xiao Hei have?", the vehicle query request can be parsed to determine the query type as battery level query. The first information can be represented as: the specified vehicle status is the specified vehicle status, the vehicle identification type is the vehicle nickname, and the vehicle identification information is "Xiao Hei".
[0057] When a user's vehicle query request does not contain information indicating the target vehicle, the vehicle's specified status can be determined to be "unspecified vehicle status". For example, when a user enters "Where is my car?", the vehicle query request can be parsed to determine that the query type is a location query, and the first piece of information can be represented as: "Vehicle specified status is unspecified vehicle status".
[0058] By parsing the vehicle query request, the natural language information input by the user can be converted into structured information for determining the target vehicle, so that the target vehicle can be determined from at least one vehicle associated with the user based on the first information.
[0059] Step 212: Based on the first information, determine the target vehicle from at least one vehicle associated with the user.
[0060] In this embodiment of the application, after determining the first information, the target vehicle can be determined from at least one vehicle associated with the user based on the first information. The vehicle associated with the user may be a vehicle pre-bound to the user's account, or a vehicle belonging to the user determined through other means; this embodiment of the application does not specifically limit this.
[0061] See Figure 3 The figure is a flowchart of a method for determining a target vehicle according to an embodiment of this application.
[0062] In one possible implementation, a target call path can be determined from at least one call path based on the user's communication content, and at least one vehicle associated with the user can be obtained based on the target call path. The call path can be used to invoke vehicle-related services to obtain vehicle information associated with the user. The call path can include at least one of a skill call path, a Model Context Protocol (MCP) service call path, or other service call paths.
[0063] The Skill invocation path can be understood as a way of encapsulating vehicle query capabilities. When querying vehicle information through the Skill invocation path, the Skill can encapsulate the processing logic required for vehicle querying, such as vehicle information acquisition logic, parameter parsing logic, and interface call logic; or, the Skill can serve as an entry point for capability invocation, further invoking the vehicle query capabilities provided by the Model Context Protocol Server (MCP Server) to obtain the corresponding vehicle information based on the query requirements.
[0064] For example, when Skill has its own vehicle list query logic, Skill can directly execute the vehicle list query operation to obtain vehicle information associated with the user; when Skill does not directly store vehicle query logic, Skill can send a query request to the MCP Server and call the corresponding vehicle service interface through the MCP Server to obtain vehicle information.
[0065] In one possible implementation, the execution unit used to perform the aforementioned vehicle information query processing can be implemented in different software forms depending on the actual application requirements. The execution unit can be implemented using Skill, MCP Server, local scripts, microservices, Function Compute, or containerized services. Specifically, the execution unit can be used to execute relevant processing logic during the vehicle query process, such as parsing vehicle query requests, obtaining vehicle information, acquiring vehicle status data, and generating query results.
[0066] For example, the target call path can be configured according to actual query requirements. For instance, when high data security is required during vehicle information querying, a more secure call path, such as the Model Context Protocol service call path, can be selected to obtain vehicle-related data; when security requirements are lower, a skill call path can be selected to obtain vehicle information. In this embodiment, the specific selection method of the call path can be adjusted according to actual application needs.
[0067] Based on the target call path, the vehicle list interface can be called, which is used to retrieve the collection of vehicles bound to the current account.
[0068] At this point, after selecting the target call path but before calling the vehicle list interface, the user's access credentials can be obtained and verified. These credentials are used to verify whether the user has the permission to call the vehicle list interface and retrieve the corresponding vehicle list data.
[0069] For example, after obtaining the user's access credentials, the access credentials can be validated. If the access credentials are validated, the vehicle list interface can be called based on the access credentials to obtain the vehicle list data associated with the current account.
[0070] For example, access credentials can be generated or obtained based on user identity information and carried when calling the vehicle list interface, so that the vehicle server can verify the user's identity and access permissions based on the access credentials; after successful verification, the vehicle list data associated with the current account is returned.
[0071] In one possible implementation, the access credential can be a service key (SK) that the user has pre-obtained within the vehicle manufacturer's application (App). The user can configure the SK key as an access credential for the corresponding call path of the vehicle query service, so as to use it when calling the vehicle list interface or other vehicle-related service interfaces.
[0072] For example, the SK key can be stored in a Skill configuration item, a local security configuration area, or a controlled cache. When it is necessary to call the vehicle list interface, the SK key can be retrieved from the corresponding storage location, and an interface call request can be initiated to the vehicle server carrying the SK key, so that the vehicle server can perform identity authentication and permission verification based on the SK key.
[0073] Furthermore, to enhance the security of access credential storage, the caching method for access credentials can be adjusted according to actual application requirements. For example, in addition to using environment variables, local configuration files, or controlled caching to store access credentials, a system key chain, an encrypted database, or a security module can also be used to store access credentials. Specifically, the system key chain can be used for secure hosting of access credentials; the encrypted database can be used for encrypted storage of access credentials; and the security module can be used to provide secure storage and controlled access capabilities for access credentials.
[0074] It is understood that the specific form and storage method of the access credentials can be set according to actual application requirements. For example, they may include environment variables, security configurations, token information, authorization credential information, SK keys, or other information used for authentication. The storage method of the access credentials may include configuration file storage, key chain storage, encrypted database storage, security module storage, or other secure storage methods. This application embodiment does not specifically limit this.
[0075] After calling the vehicle list interface, determine whether the user has specified a vehicle, that is, make the judgment based on the vehicle specification status in the first information.
[0076] In another possible implementation, when the vehicle status specified in the first information is a specified vehicle status, the vehicle identification information in the first information can be obtained, and the target vehicle can be determined from at least one vehicle associated with the user based on the vehicle identification information.
[0077] The vehicle identification information can be structured slot information used to distinguish different vehicles, including but not limited to vehicle nickname, vehicle serial number, vehicle number, vehicle identification code, etc. This application embodiment does not specifically limit this.
[0078] For example, when a user enters "How much battery does Xiao Hei have left?", the system can match the corresponding vehicle from at least one vehicle associated with the user based on the vehicle identification information "Xiao Hei", and identify the matched vehicle as the target vehicle. When a user enters "How much battery does vehicle serial number 1234567 have left?", the system can search for a vehicle with the corresponding vehicle serial number from at least one vehicle associated with the user based on the vehicle identification information "1234567", and identify the found vehicle as the target vehicle. When a user enters "How many kilometers can the car with number A001 run?", the system can identify the corresponding vehicle from at least one vehicle associated with the user based on the vehicle number "A001", and identify that vehicle as the target vehicle.
[0079] When the vehicle status specified in the first information is "unspecified vehicle status", the target vehicle can be determined based on the number of vehicles associated with the user.
[0080] For example, when a user associates only one vehicle, that associated vehicle can be directly identified as the target vehicle. For instance, if a user enters "Where is my car?" and only associates one vehicle, that vehicle can be directly identified as the target vehicle.
[0081] When a user associates multiple vehicles, the system can retrieve candidate vehicle information for each vehicle and output the candidate vehicle information for the user to choose from; based on the user's selection of the candidate vehicle information, the target vehicle is determined.
[0082] For example, when a user enters "Where is my car?" and the user has associated multiple vehicles, the system can output the vehicle nicknames, vehicle serial numbers, or other candidate information for each vehicle. The user can then select the appropriate vehicle based on their needs, and the selected vehicle will be designated as the target vehicle.
[0083] In one possible implementation, the target vehicle determination process can also support multiple vehicle matching methods. For a vehicle query request containing vehicle identification information, the target vehicle can be determined based on the matching relationship between the vehicle identification information and the user's associated vehicle information. The target vehicle matching method can include at least one of exact matching, fuzzy matching, most recently used priority matching, or context-based default vehicle inference.
[0084] For example, when a user enters "How much battery does Xiao Hei have left?", the system can match the vehicle nickname "Xiao Hei" with the user's associated vehicle information. If a vehicle with the exact same name exists, that vehicle can be identified as the target vehicle. When the vehicle identification information entered by the user partially matches the vehicle nickname, vehicle serial number, or other information, the target vehicle can also be determined based on fuzzy matching. When the user does not explicitly specify a vehicle, the system can determine the default vehicle based on the vehicle's recent usage records, or infer the target vehicle by combining the user's historical query context.
[0085] By using the above method, the target vehicle can be determined based on the query requirements corresponding to the vehicle query request, the specified vehicle status, and the number of vehicles associated with the user, thereby improving the accuracy of target vehicle determination and reducing the user's manual vehicle search process.
[0086] S202. Call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle.
[0087] In this embodiment, after determining the target vehicle, vehicle status data corresponding to the target vehicle can be further obtained. The vehicle status data can be used to represent the current operating status of the target vehicle, and may include, but is not limited to, vehicle location information, battery level information, remaining mileage information, power on / off status information, and charging status information. This embodiment does not specifically limit these data.
[0088] Among them, the vehicle status data corresponding to the target vehicle can be obtained by calling the vehicle status interface. The vehicle status interface can be used to provide vehicle status query capabilities to the outside world to obtain real-time or historical status information of the target vehicle.
[0089] In addition, it should be noted that since the remote query capabilities of different vehicles may vary, before calling the vehicle status interface to obtain vehicle status data, it is advisable to first determine whether the target vehicle supports remote querying in order to avoid performing invalid query operations on vehicles that do not have remote query capabilities.
[0090] In one possible implementation, S202 can be achieved through steps 221-222.
[0091] Step 221: Obtain the remote query capability information corresponding to the target vehicle.
[0092] In this embodiment of the application, after determining the target vehicle, remote query capability information corresponding to the target vehicle can be obtained. This remote query capability information indicates whether the target vehicle possesses remote query capability, which represents the vehicle's ability to obtain vehicle status data via network communication without requiring local user intervention.
[0093] For example, remote query capability information can be determined based on the capability identifier corresponding to the vehicle. For instance, the vehicle service platform can pre-store capability identifiers representing vehicle capabilities. These capability identifiers can include information indicating whether the vehicle supports remote queries, such as a remote query capability field (remoteCapable). Once the capability identifier corresponding to the target vehicle is obtained, the remote query capability information corresponding to the target vehicle can be determined based on the value of the capability identifier.
[0094] It is understood that the methods for obtaining remote query capability information are not limited to the above methods. In practical applications, remote query capability information corresponding to the target vehicle can also be obtained by querying vehicle configuration parameters, reading the vehicle capability list, or calling the vehicle capability query interface. This application embodiment does not make specific limitations on this.
[0095] After obtaining the remote query capability information corresponding to the target vehicle, it can be determined whether the target vehicle supports remote query based on the remote query capability information.
[0096] Step 222: If the remote query capability information indicates that the target vehicle supports remote query, call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle.
[0097] In this embodiment of the application, when the remote query capability information indicates that the target vehicle supports remote querying, the vehicle status interface can be called to obtain the vehicle status data corresponding to the target vehicle, such as... Figure 4 As shown.
[0098] For example, when the value of the remoteCapable field is true, it can be determined that the target vehicle supports remote querying.
[0099] The vehicle status interface is used to obtain the status information of the target vehicle. The vehicle status data may include, but is not limited to, at least one of the following vehicle information: location, battery level, remaining mileage, power on / off status, and charging status.
[0100] At this point, the corresponding vehicle status data can be determined based on the query type, and the vehicle status interface can be called to obtain the vehicle status data corresponding to the target vehicle. For example, when the query type is a battery query, the vehicle status interface can be called to obtain the remaining battery information of the target vehicle; when the query type is a location query, the vehicle status interface can be called to obtain the location information of the target vehicle; and when the query type is a remaining mileage query, the vehicle status interface can be called to obtain the remaining mileage information of the target vehicle.
[0101] For example, the vehicle status interface can be called based on the vehicle identification information corresponding to the target vehicle, so that the vehicle server can determine the corresponding target vehicle based on the vehicle identification information and return the vehicle status data corresponding to the target vehicle.
[0102] In one possible implementation, after obtaining the remote query capability information corresponding to the target vehicle, when the remote query capability information indicates that the target vehicle does not support remote query, a first prompt message can be generated.
[0103] For example, when the value of the remoteCapable field is false, it can be determined that the target vehicle does not support remote querying.
[0104] The first prompt message is used to inform the user that the target vehicle currently does not have remote query capabilities. The first prompt message may include text information, voice information, image information, or other forms of prompt information, and this application embodiment does not specifically limit this.
[0105] For example, when a user enters "How much battery does my car have left?", if it is determined that the target vehicle does not support remote querying, a first prompt message can be generated to inform the user that "the current vehicle does not support remote querying", so that the user knows that the vehicle status data corresponding to the vehicle cannot be obtained remotely.
[0106] After generating the first prompt message, it can be output through the user terminal to display or play a prompt message to the user that the target vehicle does not support remote query.
[0107] For example, the first prompt information can be sent to the user terminal and displayed through the corresponding interactive interface of the user terminal, or broadcast through the voice entry, so that the user can understand the remote query capability status of the target vehicle in a timely manner.
[0108] S203. Based on the query type and the vehicle status data, generate the vehicle query result corresponding to the vehicle query request.
[0109] In one possible implementation, before generating vehicle query results based on query type and vehicle status data, the vehicle status data can be processed to ensure it meets the requirements for generating vehicle query results, such as... Figure 5 As shown.
[0110] For example, vehicle status data can be processed by at least one of the following: field mapping, unit unification, and status semantic transformation, to obtain processed vehicle status data.
[0111] The field mapping is used to convert the different field names returned by different vehicle service interfaces that represent the same vehicle status to obtain vehicle status data with a unified field format.
[0112] In this embodiment, different vehicle service interfaces may use different fields to represent the same vehicle status information in the vehicle status data returned. For example, some vehicle service interfaces may use the "power" field to represent the remaining battery power, while others may use the "batteryLevel" field; some may use the "mileageLeft" field to represent the remaining driving range, while others may use the "mileageRemaining" field. In this case, these different fields can be mapped to a unified battery power field and a unified remaining mileage field to facilitate subsequent processing based on these unified fields.
[0113] Unit unification is used to convert data from different units in vehicle status data into a unified data unit, so as to ensure that vehicle status data from different sources can be processed according to a unified standard.
[0114] For example, the remaining mileage data returned by different vehicle service interfaces may use different units of measurement such as kilometers and meters. In this case, the remaining mileage data in different units can be converted into a unified unit before querying the results.
[0115] State semantic transformation is used to convert state identifiers, state codes, or other non-natural language forms of data in vehicle state data into state description information that users can understand.
[0116] For example, when "powerOn" in the vehicle status data is a Boolean type, the corresponding data can be converted to "powered on" or "powered off" through status semantic conversion; when "charging" in the vehicle status data is a status identifier, the corresponding status can be converted to user-understandable status information such as "charging" or "not charging".
[0117] After obtaining the processed vehicle status data, the target status data can be determined from the processed vehicle status data according to the query type, and vehicle query results can be generated based on the target status data.
[0118] In one possible implementation, when generating vehicle query results based on target state data, the corresponding result generation method can be selected according to the query type, and the target state data can be converted into query results in natural language form.
[0119] For example, you can select the corresponding query result template according to the query type, and fill the target status data into the information position corresponding to the query result template to generate vehicle query results.
[0120] For example, when the query type is location query, query results containing a description of the vehicle's current location can be generated based on the target vehicle's location data; when the query type is battery level query, query results containing the remaining battery percentage and estimated remaining driving range can be generated based on the vehicle's remaining battery level data; when the query type is comprehensive status query, comprehensive status query results can be generated based on multiple target status data such as vehicle location, battery level, power on / off status, and charging status.
[0121] In another possible implementation, when an anomaly occurs during the acquisition of vehicle status data, error semantic mapping can be performed based on a preset error code, and corresponding anomaly message can be generated according to a template, such as... Figure 6 As shown.
[0122] For example, a mapping relationship between error codes and prompts can be pre-set, and the target prompt can be determined based on the error code corresponding to the exception. Error codes may include, but are not limited to, errors such as missing key, invalid key, no vehicle bound to user, vehicle not found, not supported for remote vehicle query, and service exceptions (http_4xx / http_5xx).
[0123] For example, when a missing necessary access parameter is detected, the error code can be mapped to "Please complete the vehicle service configuration first"; when an invalid access credential is detected, the error code can be mapped to "Invalid access credential, please reconfigure"; when no associated vehicle is detected under a user account, the error code can be mapped to "No vehicle bound to the current account"; when a specified vehicle is not matched, the error code can be mapped to "The specified vehicle was not found, please check the vehicle nickname or serial number"; when the target vehicle does not support remote query, the error code can be mapped to "This vehicle does not currently support remote status query"; when a service abnormality is detected, the error code can be mapped to "The service is temporarily unavailable, please try again later".
[0124] Furthermore, the prompts after the abnormal semantic mapping can share a unified natural language output interface with the normal query results, so that the vehicle query system can output natural language feedback in a unified format in both normal and abnormal query scenarios.
[0125] It is understood that the processing method of vehicle status data, query result template, and error semantic mapping method can be adjusted according to the vehicle service interface type, query requirements, and actual application scenarios. This application embodiment does not impose specific limitations on these aspects.
[0126] Through the above methods, the embodiments of this application can standardize the heterogeneous vehicle status data returned by different vehicle services and generate corresponding natural language query results in combination with the user query type; at the same time, in the event of query anomalies, corresponding prompt information can be generated through an error semantic mapping mechanism, thereby improving the accuracy, understandability and interactive experience of vehicle information query results.
[0127] It is understood that the vehicle information query method provided in this application embodiment is not limited to a specific vehicle brand or a single vehicle open platform. For other two-wheeled vehicles, connected small vehicles, or other vehicles with vehicle networking capabilities, as long as they can provide vehicle list query capabilities and vehicle status query capabilities, such as providing corresponding vehicle list interfaces and vehicle status interfaces, vehicle information query can be implemented based on the method provided in this application embodiment.
[0128] For example, different vehicle manufacturers or vehicle service platforms can provide corresponding vehicle information acquisition capabilities according to their own interface protocols. This application embodiment can obtain user-associated vehicle information and vehicle status data corresponding to the target vehicle by adapting to different vehicle service interfaces, and generate vehicle query results based on a unified vehicle information processing flow.
[0129] Since the embodiments of this application are not limited to a specific vehicle brand or a single vehicle open platform, as long as the vehicle has the corresponding vehicle information query capability, the method provided by the embodiments of this application can be applied, thus improving the universality and applicability of the vehicle information query solution.
[0130] See Figure 7 This figure is an overall architecture diagram of a vehicle information query method provided in an embodiment of this application.
[0131] like Figure 7 As shown, users can input vehicle query requests through a user terminal. The user terminal may include a chat interface, desktop assistant, voice entry, or other interactive interface. In response to the user's input vehicle query request, the system can parse the request, determine the corresponding query type, and further identify the target vehicle to be queried.
[0132] After determining the query type and target vehicle, a target call path can be determined from at least one call path based on the communication content corresponding to the vehicle query request and the actual business needs. The call path can include at least one of a skill call path and a Model Context Protocol (MCP) service call path.
[0133] Based on a defined target call path, vehicle status data corresponding to the target vehicle can be obtained. The process of obtaining vehicle status data may include steps such as verifying access credentials, retrieving a vehicle list, determining the remote query capability information corresponding to the target vehicle, and calling the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle. This vehicle status data may include information such as the target vehicle's location, battery level, remaining range, power on / off status, and charging status.
[0134] After obtaining vehicle status data, it can be processed. For example, at least one of the following processes can be performed on the vehicle status data: field mapping, unit unification, and status semantic transformation, to obtain processed vehicle status data. The target status data can then be determined from the processed vehicle status data based on the query type.
[0135] Based on the target status data, vehicle query results corresponding to the vehicle query request can be generated and displayed to the user through the user terminal's user interface.
[0136] This application also provides a vehicle information query device, see [link to relevant documentation]. Figure 8 The figure is a schematic diagram of the structure of a vehicle information query device provided in an embodiment of this application. Its specific implementation method is consistent with the implementation method and the technical effect achieved in the above-described method embodiment, and some contents will not be repeated.
[0137] A vehicle information query device 7100 includes: The parsing unit 7101, the calling unit 7102, and the generating unit 7103; The parsing unit 7101 is used to parse the vehicle query request input by the user, determine the query type and target vehicle corresponding to the vehicle query request; the target vehicle is determined from at least one vehicle associated with the user. Calling unit 7102 is used to call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle. The generation unit 7103 is used to generate vehicle query results corresponding to the vehicle query request based on the query type and vehicle status data.
[0138] In one possible implementation, the parsing unit 7101 is specifically used for: The system parses the vehicle query request entered by the user to determine the query type and first information corresponding to the vehicle query request; the first information is used to indicate the specified status of the vehicle corresponding to the vehicle query request. Based on the first information, the target vehicle is determined from at least one vehicle associated with the user.
[0139] In one possible implementation, the parsing unit 7101 is specifically used for: When the vehicle is in a specified state, obtain the vehicle identification information from the first information; Based on vehicle identification information, identify the target vehicle from at least one vehicle associated with the user; The vehicle identification information includes, but is not limited to, structured slot information such as vehicle nickname, vehicle serial number, vehicle number, and vehicle identification code used to distinguish different vehicles.
[0140] In one possible implementation, the parsing unit 7101 is specifically used for: If the vehicle's specified status is "unspecified" and the user has associated a vehicle, the vehicle associated with the user will be identified as the target vehicle. If the specified vehicle status is "unspecified" and the user has associated multiple vehicles, output the candidate vehicle information corresponding to the multiple vehicles. The target vehicle is determined based on the user's selection of candidate vehicle information.
[0141] In one possible implementation, the parsing unit 7101 is specifically used for: Based on the communication content corresponding to the vehicle query request, determine the target call path from at least one call path; Call the vehicle list interface based on the target call path to obtain at least one vehicle associated with the user; Based on the first information, the target vehicle is determined from at least one of the acquired vehicles.
[0142] The call path includes at least one of the skill call path and the model context protocol service call path, and the target call path can be configured according to actual query requirements.
[0143] In one possible implementation, unit 7102 is specifically used for: Obtain remote query capability information corresponding to the target vehicle; If the remote query capability information indicates that the target vehicle supports remote query, the vehicle status interface is called to obtain the vehicle status data corresponding to the target vehicle.
[0144] In one possible implementation, unit 7102 is specifically used for: Obtain the user's access credentials; Verify the access credentials; If the access credentials are verified, the vehicle status interface is invoked based on the access credentials.
[0145] In one possible implementation, the calling unit 7102 is also used for: If the remote query capability information indicates that the target vehicle does not support remote query, a first prompt message is generated; Output the first prompt message.
[0146] The first prompt message indicates that the target vehicle does not support remote querying.
[0147] In one possible implementation, the generating unit 7103 is specifically used for: Perform at least one of the following processes on the vehicle status data: field mapping, unit unification, and status semantic transformation, to obtain the processed vehicle status data; Based on the query type, determine the target status data from the processed vehicle status data; Based on the target status data, generate vehicle query results.
[0148] In one possible implementation, the generating unit 7103 is specifically used for: When the query type is at least one of location query, battery level query, remaining mileage query, power on / off status query, or charging status query, the corresponding target status data is determined from the processed vehicle status data. Vehicle query results are generated based on the target status data.
[0149] In summary, the device provided in this application parses the vehicle query request input by the user, determines the query type and the target vehicle, calls the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle, and further generates vehicle query results based on the query type and vehicle status data, thus realizing the process of determining the target vehicle and obtaining the corresponding vehicle information according to the vehicle query request input by the user.
[0150] Meanwhile, the device provided in this application embodiment can select the corresponding call path according to the communication content corresponding to the vehicle query request, and obtain vehicle status data through the vehicle status interface; when the target vehicle does not support remote query, it can also output corresponding prompt information to the user, thereby improving the accuracy and user experience in the vehicle information query process.
[0151] Furthermore, the apparatus provided in this application embodiment can perform field mapping, unit unification, and state semantic conversion on vehicle status data, and generate vehicle query results based on the processed vehicle status data, making the generated vehicle query results more in line with user query needs and improving the convenience of vehicle information query.
[0152] This application provides a computer device, such as... Figure 9 As shown in the figure, this figure is a schematic diagram of the structure of a computer device provided in an embodiment of this application. The computer device 8100 includes: a processor 8101 and a memory 8102; The memory 8102 is used to store program code and transfer the program code to the processor; The processor 8101 is used to execute the steps of the above method according to the instructions in the program code.
[0153] This application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above method.
[0154] This application provides a computer program product, which, when run on a computer, executes the steps of the above method.
[0155] The above is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for querying vehicle information, characterized in that, include: The user-inputted vehicle query request is parsed to determine the query type and target vehicle corresponding to the vehicle query request; The target vehicle is determined from at least one vehicle associated with the user; Call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle; Based on the query type and the vehicle status data, generate the vehicle query result corresponding to the vehicle query request.
2. The method according to claim 1, characterized in that, The step of parsing the user-input vehicle query request to determine the query type and target vehicle corresponding to the vehicle query request includes: The user-inputted vehicle query request is parsed to determine the query type and first information corresponding to the vehicle query request; the first information is used to indicate the specified status of the vehicle corresponding to the vehicle query request. Based on the first information, the target vehicle is determined from at least one vehicle associated with the user.
3. The method according to claim 2, characterized in that, The step of determining the target vehicle from at least one vehicle associated with the user based on the first information includes: When the specified vehicle status is a specified vehicle status, the vehicle identification information in the first information is obtained; The target vehicle is determined from at least one vehicle associated with the user based on the vehicle identification information; If the vehicle's specified status is "unspecified vehicle status" and the user is associated with a vehicle, the vehicle associated with the user will be identified as the target vehicle. If the specified vehicle status is "unspecified vehicle status" and the user is associated with multiple vehicles, output the candidate vehicle information corresponding to the multiple vehicles. The target vehicle is determined based on the user's selection of the candidate vehicle information.
4. The method according to claim 2, characterized in that, The step of determining the target vehicle from at least one vehicle associated with the user based on the first information includes: Based on the query type, a target call path is determined from at least one call path; the at least one call path includes at least one of a skill call path and a model context protocol service call path; Based on the target call path, the vehicle list interface is called to obtain at least one vehicle associated with the user; Based on the first information, the target vehicle is determined from the at least one vehicle acquired.
5. The method according to claim 1, characterized in that, The step of calling the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle includes: Obtain the remote query capability information corresponding to the target vehicle; When the remote query capability information indicates that the target vehicle supports remote query, the vehicle status interface is invoked to obtain the vehicle status data corresponding to the target vehicle.
6. The method according to claim 5, characterized in that, The method further includes: If the remote query capability information indicates that the target vehicle does not support remote query, a first prompt message is generated; the first prompt message is used to indicate that the target vehicle does not support remote query. Output the first prompt message.
7. The method according to any one of claims 1 to 6, characterized in that, The step of generating vehicle query results corresponding to the vehicle query request based on the query type and the vehicle status data includes: The vehicle status data is processed by at least one of the following: field mapping, unit unification, and status semantic transformation, to obtain the processed vehicle status data. Based on the query type, determine the target status data from the processed vehicle status data; Based on the target status data, the vehicle query results are generated.
8. The method according to any one of claims 1 to 6, characterized in that, The invocation of the vehicle status interface includes: Obtain the access credentials corresponding to the user; Verify the access credentials; If the access credential is successfully verified, the vehicle status interface is invoked based on the access credential.
9. A vehicle information query device, characterized in that, include: Parsing unit, calling unit, and generation unit; The parsing unit is used to parse the vehicle query request input by the user and determine the query type and target vehicle corresponding to the vehicle query request. The target vehicle is determined from at least one vehicle associated with the user; The calling unit is used to call the vehicle status interface to obtain the vehicle status data corresponding to the target vehicle. The generation unit is used to generate vehicle query results corresponding to the vehicle query request based on the query type and the vehicle status data.
10. A computer device, characterized in that, The computer device includes: a processor and a memory; The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the steps of the method as described in any one of claims 1 to 8 according to instructions in the program code.
