Test run authenticity determination method and device, vehicle and electronic equipment

Abstract

The invention relates to a test run authenticity determination method and device, a vehicle and electronic equipment, relates to the technical field of vehicles, and is used for improving the accuracy of test run authenticity verification, and the method comprises the steps: obtaining test run voice data and test run operation data of a user; determining the authenticity of the test run based on the first time related to the target function in the test run voice data and the second time related to the target function in the test run operation data; wherein the target function is any function which can be realized by the vehicle. Therefore, through dual verification of the test run voice data and the test run operation data, the authenticity of the test run is more accurate.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicles, in particular to a test driving authenticity determination method and device, a vehicle and an electronic device. BACKGROUND

[0002] Currently, in order to realize store-side multi-lead test driving, expand brand awareness and obtain business opportunities, the host factory often provides test driving incentives to the store side. However, when there are not enough test driving customers in the store, or when a customer directly places an order, some stores will fake test driving records to obtain more test driving incentives. For example, when there is actually no customer, a product expert randomly enters a customer information and drives around a circle to fake the completion of test driving; even worse, only the customer information is entered and the test driving process is falsely completed without starting the vehicle. Such behavior not only wastes the operating expenses of the host factory, but also seriously affects the evaluation and improvement of service quality.

[0003] To solve the above problems, the related technology discloses a way of marking employees in advance to distinguish whether the driver seat is an employee or a customer, and in the case of a customer in the driver seat, the test driving mode is started. Another related technology discloses an identity verification by obtaining a test driving verification code of the user to determine that the current vehicle is a test driving vehicle. As can be seen, the related technology mostly verifies whether the customer is currently in the test driving vehicle by marking the employee in advance or using the verification code. However, there is an obvious loophole in the judgment logic that only the first person getting on the vehicle is an employee and the person getting off the vehicle is a customer. The product expert can completely fake the appearance of customer test driving through simple getting on and off the vehicle, and it is difficult to ensure the true identity of the subsequent driver. If the management and use of the verification code are not strictly regulated, the store personnel can easily use or reuse the verification code, so that even if the customer does not actually participate in the test driving, the customer can pass the verification code verification link, and it is impossible to fundamentally eliminate the false test driving behavior. In addition, the related technology focuses on whether the customer is in the vehicle, and does not judge the process of test driving, thereby affecting the judgment of test driving authenticity. SUMMARY

[0004] The purpose of the present application is to provide a test driving authenticity determination method, device, vehicle and electronic device for improving the accuracy of test driving authenticity verification.

[0005] To achieve the above purpose, the technical solutions adopted by the embodiments of the present application are as follows:

[0006] In a first aspect, the embodiments of the present application provide a test driving authenticity determination method, which comprises: obtaining test driving voice data and test driving operation data of a user; determining the authenticity of test driving based on a first time related to a target function in the test driving voice data and a second time related to the target function in the test driving operation data; wherein the target function is any function that the vehicle can implement.

[0007] According to the above technical means, through double verification of the first time related to the target function in the test drive voice data and the second time related to the target function in the test drive operation data, the explanation and experience can be accurately associated from the dynamic interaction level, abnormal situations such as having operation without explanation or having explanation without operation in false test drive can be quickly identified, and the accuracy of test drive authenticity evaluation can be significantly improved.

[0008] In a possible implementation, based on the first time related to the target function in the test drive voice data and the second time related to the target function in the test drive operation data, the authenticity of the test drive is determined, including: obtaining login information of the user on the vehicle; identity verification is performed on the user based on the login information; in the case that the user is verified as a customer, the authenticity of the test drive is determined based on the first time and the second time.

[0009] According to the above technical means, the user can be accurately identified as a real customer through identity verification based on the login information. On this basis, the authenticity of the test drive can be further judged by combining the analysis of the first time and the second time, so as to form double verification from the user identity to the test drive behavior, and provide a more comprehensive and reliable basis for ensuring the authenticity of the test drive scene and process.

[0010] In a possible implementation, based on the first time and the second time, the authenticity of the test drive is determined, including: determining the time difference between the first time and the second time; in the case that the time difference is less than or equal to a preset time threshold, determining that the authenticity of the test drive is real test drive.

[0011] According to the above technical means, by determining the time difference between the first time and the second time, and then comparing the time difference with the preset time threshold, the real test drive process can be accurately identified, and the test drive behavior conforming to the conventional process can be effectively distinguished from the operation in the non-real scene, thereby providing a reliable judgment basis for ensuring the authenticity of the test drive data.

[0012] In a possible implementation, identity verification is performed on the user based on the login information, including: determining whether the vehicle logs in a target account based on the login information; the target account is an account issued to the user in the test drive reservation link; in the case that the vehicle logs in the target account, the user is determined as a customer.

[0013] According to the above technical means, by means of the login information, the account login state in the vehicle can be more accurately verified, the login situation of the target account can be clearly identified, and the product expert and customer identity can be accurately distinguished, thereby effectively reducing the interference of the non-customer group on the authenticity of the test drive data, providing a more reliable basis for the judgment of the test drive authenticity, and improving the accuracy and credibility of the overall verification process.

[0014] In a possible implementation, the test drive authenticity determination method further includes: in a case where it is determined that the test drive is a real test drive, determining a test drive experience degree of the user.

[0015] According to the technical means described above, by determining the test drive experience degree of the user, accurate basis can be provided for subsequent optimization of user experience, and specific reference can be provided for improvement of service ability of product experts, so as to help form a service improvement closed loop with user experience as the core.

[0016] In a possible implementation, the test drive experience degree of the user is determined by: determining an explanation completeness degree of the target function based on a voice explanation segment of the target function by the test drive explanation personnel involved in the test drive voice data; and determining the test drive experience degree based on the explanation completeness degree.

[0017] According to the technical means described above, the explanation completeness degree is determined based on the voice explanation segment of the target function by the explanation personnel in the test drive voice data, and then the test drive experience degree is determined based on the explanation completeness degree, so that the quality of professional explanation can be directly associated with user experience, the evaluation of the test drive experience degree can more accurately reflect the influence of explanation service on user experience, and a clear direction is provided for targeted improvement of explanation completeness and optimization of service process, thereby effectively enhancing user test drive experience.

[0018] In a possible implementation, the test drive experience degree is determined based on the explanation completeness degree, including: determining an experience completeness degree of the target function by the user based on test drive operation data of the target function by the user; and determining the test drive experience degree based on the experience completeness degree and the explanation completeness degree.

[0019] According to the technical means described above, the experience completeness degree is determined based on the test drive operation data of the target function by the user, and then the test drive experience degree is determined in combination with the explanation completeness degree, so that the test drive process can be comprehensively measured from two dimensions of actual operation by the user and professional explanation by the expert, accurate capture of real experience by the user is ensured, and the influence of professional service quality is also taken into account, so that the test drive experience degree is more objective and comprehensive, and reliable basis is provided for evaluation of test drive effect and optimization of service.

[0020] In a possible implementation, the test drive experience degree is determined based on the experience completeness degree and the explanation completeness degree, including: determining a test drive experience degree of the target function based on the experience completeness degree and the explanation completeness degree; and determining the test drive experience degree of the user based on the test drive experience degree of the target function and the test drive experience degrees of other functions in the vehicle except the target function.

[0021] According to the above technical means, the influence of actual operation and professional explanation on single function experience can be determined through experience completeness and explanation completeness, and then the test driving experience degree of the target function can be determined more accurately; on this basis, the overall test driving experience degree of the user is determined in combination with the test driving experience degrees of other functions, the experience of all functions of the vehicle can be overall arranged, and the real test driving feelings of the user can be comprehensively and accurately reflected, so as to determine the test driving experience of the user and improve the test driving service quality.

[0022] In a second aspect, the embodiments of the present application provide a test driving authenticity determination device, comprising: an acquisition module and a determination module; the acquisition module is used to acquire test driving voice data and test driving operation data of a user; the determination module is used to determine the authenticity of test driving based on a first time related to a target function in the test driving voice data and a second time related to the target function in the test driving operation data; and the target function is any function that can be realized by a vehicle.

[0023] In a possible implementation, the determination module is specifically configured to acquire login information of the user on the vehicle; perform identity verification on the user based on the login information; and in a case where the user is verified as a customer, determine the authenticity of test driving based on the first time and the second time.

[0024] In a possible implementation, the determination module is specifically configured to determine a time difference between the first time and the second time; and in a case where the time difference is less than or equal to a preset time threshold, determine that the test driving is real test driving.

[0025] In a possible implementation, the determination module is specifically configured to determine whether the vehicle logs in a target account based on the login information; the target account is an account issued to the user in a test driving reservation link; and in a case where the vehicle logs in the target account, determine that the user is a customer.

[0026] In a possible implementation, the determination module is further configured to, in a case where it is determined that the test driving is real test driving, determine a test driving experience degree of the user.

[0027] In a possible implementation, the determination module is specifically configured to determine an explanation completeness of the target function based on a voice explanation segment of the target function by a test driving explanation personnel involved in the test driving voice data; and determine the test driving experience degree based on the explanation completeness.

[0028] In a possible implementation, the determination module is specifically configured to determine an experience completeness of the target function by the user based on the test driving operation data of the target function by the user; and determine the test driving experience degree based on the experience completeness and the explanation completeness.

[0029] In a possible implementation, the determining module is specifically configured to determine the test driving experience degree of the target function based on the experience completeness and the explanation completeness; and determine the test driving experience degree of the user based on the test driving experience degree of the target function and the test driving experience degrees of other functions in the vehicle except the target function.

[0030] In a third aspect, the present application provides a vehicle comprising the test driving authenticity determining apparatus of the second aspect.

[0031] In a fourth aspect, the present application provides an electronic device comprising a processor and a memory; the memory stores instructions executable by the processor. The processor is configured to execute the instructions, so that the electronic device implements the method of the first aspect.

[0032] It should be noted that the technical effects brought by any one of the implementation manners of the second aspect to the fourth aspect can refer to the technical effects brought by the corresponding implementation manners in the first aspect, which will not be repeated here.

[0033] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0034] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the specification, serve to explain the principles of the present application, and do not constitute an improper limitation on the present application.

[0035] Figure 1 is a flowchart of a test driving authenticity determining method according to an exemplary embodiment;

[0036] Figure 2 is a flowchart of another test driving authenticity determining method according to an exemplary embodiment;

[0037] Figure 3 is a flowchart of another test driving authenticity determining method according to an exemplary embodiment;

[0038] Figure 4 is a flowchart of another test driving authenticity determining method according to an exemplary embodiment;

[0039] Figure 5 is a flowchart of another test driving authenticity determining method according to an exemplary embodiment;

[0040] Figure 6 is a flowchart of another test driving authenticity determining method according to an exemplary embodiment;

[0041] Figure 7is a flow chart of still another test drive authenticity determination method according to an exemplary embodiment;

[0042] Figure 8 is a flow chart of still another test drive authenticity determination method according to an exemplary embodiment;

[0043] Figure 9 is a flow chart of still another test drive authenticity determination method according to an exemplary embodiment;

[0044] Figure 10 is a flow chart of still another test drive authenticity determination method according to an exemplary embodiment;

[0045] Figure 11 is a flow chart of still another test drive authenticity determination method according to an exemplary embodiment;

[0046] Figure 12 is a block diagram of a test drive authenticity determination apparatus according to an exemplary embodiment;

[0047] Figure 13 is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0048] In order to make the skilled in the art better understand the technical solutions of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings.

[0049] It should be noted that the terms "first", "second", and the like in the description and claims of the present application and the above drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0050] In the embodiments of the present application, the terms "comprise", "contain" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, article or device. Without more limitations, the element defined by the sentence "comprises a" does not exclude the presence of another identical element in the process, article or device comprising the element.

[0051] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0052] For ease of understanding, the method for determining the authenticity of test runs provided in this application will be described in detail below with reference to the accompanying drawings.

[0053] In some embodiments, the execution entity of the test run authenticity determination method provided in this application can be a test run authenticity determination device. For example, the test run authenticity determination device can be any device or equipment capable of determining test run authenticity, such as a server cluster composed of multiple servers, a single server, a computer, or a processor or processing chip in a server or computer. This application does not limit this.

[0054] As a feasible approach, the test vehicle authenticity verification device is connected to the vehicle and can obtain test vehicle voice data and test vehicle operation data from the vehicle.

[0055] It should be noted that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0056] like Figure 1 As shown, the method for determining the authenticity of a test drive includes the following steps:

[0057] S101. Obtain the user's test drive voice data and test drive operation data.

[0058] Among them, test drive voice data refers to the recordings with a timeline collected during the test drive, and test drive operation data refers to the embedded data collected during the test drive, including the user's operation time and the corresponding target function.

[0059] As a feasible implementation method, recordings (test drive voice data) and embedded data (test drive operation data) can be automatically obtained from the vehicle after the test drive duration is greater than or equal to the preset time, or the vehicle travel distance is equal to the preset distance threshold.

[0060] When the test drive duration reaches or exceeds the preset time, it means that the user has completed a period of test drive. At this time, the test drive voice data and test drive operation data can reflect the authenticity of the test drive well, and the possibility of significant changes in the subsequent process is small.

[0061] As another feasible approach, after the test drive is completed, the recording (test drive voice data) and embedded data (test drive operation data) can be automatically obtained from the vehicle.

[0062] Acquiring data after the test drive ensures that the collected information is complete, comprehensively covering the explanations and operations during the test drive, providing a complete data foundation for subsequent authenticity assessment.

[0063] As a feasible approach, explicit consent from the customer must be obtained before collecting test drive voice data (recordings) and test drive operation data (user operation data points) at the start of the test drive.

[0064] For example, after the test drive begins, a pop-up window appears on the vehicle's infotainment system: "To ensure the quality of your test drive, this service will record the entire process and monitor your operation data in the vehicle. Do you agree?" It also displays "Agree" and "Disagree" buttons. After the user clicks "Agree," the vehicle automatically starts recording audio and recording the user's operation data. During the test drive, the vehicle automatically uploads the audio recordings (test drive voice data) and the data points (test drive operation data).

[0065] As a feasible approach, a complete test drive process includes both a test drive and a test ride.

[0066] For example, such as Figure 2 As shown, the test drive process includes: after the product expert (i.e. the test drive presenter, referred to as such below) sits in the driver's seat, the product expert logs into the vehicle's infotainment system account; after successful login, the product expert explains the vehicle's key features to the customer; after the explanation, the product expert drives the test drive vehicle to let the customer experience the vehicle's performance.

[0067] For example, such as Figure 3 As shown, the test drive process includes: the customer sits in the driver's seat and logs into their authorized target account; after successful login, the vehicle automatically broadcasts the first preset text via voice (e.g., welcome Mr. / Ms. XX to test drive the XX model, wish you a pleasant test drive); when the customer gets out of the car at the end of the test drive, the vehicle automatically broadcasts the second preset text via voice (e.g. thank you for testing the X model, wish you a pleasant driving experience).

[0068] Optionally, at the start of the test drive, a product expert can guide the customer to sit in the driver's seat and log in to their target account. If the customer is a new account holder, they can follow the vehicle's system prompts to complete the vehicle setup (including adjusting the seat position, setting up the head-up display, adjusting the rearview mirrors, and selecting the driving mode); if the customer is not a new account holder, a product expert will assist them in completing the relevant settings.

[0069] It should be understood that a product expert is a role that possesses in-depth professional knowledge and rich practical experience in a specific product or product line area, and can provide professional support around product value realization and user needs satisfaction.

[0070] It should be noted that the order of test drives and test rides is determined by product experts based on customer needs, and this embodiment does not impose any restrictions on this.

[0071] S102. Based on the first time of the test drive voice data involving the target function and the second time of the test drive operation data involving the target function, determine the authenticity of the test drive.

[0072] The target function is any function that the vehicle can perform.

[0073] As a feasible approach, the first mention of the target function during the test drive can be identified by the following method: performing speech recognition processing on the test drive recording with a timeline, converting the audio data into text information, and retaining the timestamp corresponding to each text segment; performing keyword matching on each text segment based on a preset target function keyword library; and extracting the timestamp corresponding to the corresponding paragraph text information when keywords related to the target function appear in the text, and using this timestamp as the first mention of the target function in the test drive voice data.

[0074] As a feasible implementation method, the second time can be the specific moment when the user actually operates the target function. It can be obtained in the following way: when an operation record consistent with the target function appears in the data, the operation time corresponding to the operation record is directly extracted. This time is the second time involving the target function in the test operation data.

[0075] It should be understood that in a real test drive, the customer's understanding of the vehicle's functions follows a natural transition from explanation to operation: the product expert first introduces the target function (corresponding to the first time), and then guides the customer to experience the operation (corresponding to the second time). In terms of time, the first time is earlier than the second time and the interval is reasonable. At the same time, this correlation is difficult to be easily faked and is the core basis for judging the authenticity of the test drive.

[0076] Therefore, the authenticity of a test drive can be verified by examining the sequence and time interval between the first and second times. Verifying the sequence of times: if the first time is later than the second time, or if the two are completely unrelated (e.g., only the first time exists without the second time, or vice versa), it can be directly identified as abnormal, and is highly likely a fake test drive. Verifying the time interval is within a preset reasonable range (which can be set according to the complexity of the explanation of different functions, such as 1-3 minutes for simple functions and 3-5 minutes for complex functions). If the interval far exceeds the reasonable range, there may be fraudulent behavior such as performing the operation first and then providing explanations, or explaining without actual operation, which may indicate a fake test drive.

[0077] During test drives, product experts often use tactics revolving around the aforementioned time relationships to fabricate results. This might include quickly operating functions without explanation (no first-time verification), verbally mentioning functions without actually operating them (no second-time verification), or deliberately falsifying records with reversed time sequences or abnormal intervals. By verifying both the first and second-time verifications, these anomalies can be accurately detected, effectively distinguishing fake test drives from genuine ones.

[0078] In some embodiments, when assessing the authenticity of a test drive, it is also necessary to first authenticate the user to confirm that the test drive is being conducted by a customer. Combined with Figure 1 ,like Figure 4 As shown, step S102 above can be specifically implemented as follows:

[0079] S401. Obtain the user's login information on the vehicle.

[0080] As a feasible approach, user login information on the vehicle can be extracted from test drive operation data.

[0081] For example, in the design of data collection points for test drive operation data, collection fields related to user login behavior are pre-set. When a user performs a login operation (such as entering an account and password, scanning a code to log in, or using facial recognition to log in) on the vehicle's central control screen, vehicle system, or related software, the system automatically records the time, login account (or anonymous identifier), login status, and other information corresponding to the operation and stores them in the test drive operation data. Subsequently, these field information can be directly extracted from the test drive operation data, which is the user's login information on the vehicle.

[0082] S402. Verify user identity based on login information.

[0083] As a feasible approach, user authentication is performed based on login information to identify the user as a customer.

[0084] For example, the login account (or anonymous identifier) ​​in the user login information is extracted from the test drive operation data, and compared with the identity information (such as mobile phone number, ID card number associated account, etc.) that the user reserved in the OEM system before the test drive. At the same time, the validity of the login status is verified (such as whether the login is successful or whether it is within the test drive period). If the account matches and the login status is valid, the user is determined to be a customer.

[0085] As another feasible approach, user authentication can be performed based on login information to identify users as fake customers.

[0086] For example, if it is determined that the user is a fake customer, the authenticity of the test drive is determined to be fake, and the user's test drive experience is zero.

[0087] Optionally, since users can choose whether to log in, if a user does not log in to the target account in the vehicle, the product expert can appeal using test drive voice data from communication with the customer.

[0088] S403. If the user is verified to be a customer, the authenticity of the test drive shall be determined based on the first and second time points.

[0089] As a feasible implementation method, after verifying that the current user is indeed a customer through user login information, the first time (explanation time) involving the target function is extracted from the test drive voice data, and the second time (operation time) involving the same target function is extracted from the test drive operation data. Then, it is verified whether the second time is later than the first time and whether the interval between the two is within a preset reasonable range. If both conditions are met, the test drive is determined to be real; otherwise, it is determined to be abnormal.

[0090] As a feasible approach, the authenticity of a test drive is determined to be a genuine test drive if the time difference is less than or equal to a preset time threshold.

[0091] As another feasible approach, if the time difference exceeds a preset time threshold, the authenticity of the test drive can be determined as a sham test drive.

[0092] In some embodiments, a user's account can also be linked to the vehicle, thereby determining whether the user is a genuine customer test driving the vehicle based on login information within the vehicle. Combined with... Figure 4 ,like Figure 5 As shown, step S402 above can be specifically implemented as follows:

[0093] S501. Determine whether the vehicle is logged into the target account based on the login information.

[0094] The target account is the account issued to the user during the test drive reservation process.

[0095] For example, the process of obtaining and using a target account can be as follows: Figure 6 As shown, users can book a test drive online or be guided by a product expert to complete information collection upon arrival at the store. The product expert schedules the test drive based on the vehicle the user wants to test drive. After successful scheduling, the system automatically grants the user access to the test drive vehicle to their pre-registered mobile phone number and generates a target account (which can be used as the customer's identity information). The product expert then leads the customer to the vehicle to prepare for the test drive. After the customer gets in the vehicle and logs into their target account, the marketing backend confirms the start of the test drive and sends a signal to the vehicle to inform it that the test drive has begun. The vehicle then starts recording audio and data from embedded points.

[0096] It should be understood that login information includes the target account's username, login time, login status, and corresponding vehicle identification number. By checking the vehicle's login information, it's possible to determine whether the target account has logged into that vehicle, and then, based on the authenticity and matching degree of the login records, the user's identity can be effectively verified.

[0097] S502. If the vehicle is logged into the target account, identify the user as a customer.

[0098] For example, the core information of the login account (such as account identifier, bound mobile phone number, etc.) is extracted from the login account in the vehicle login information; the extracted account information is compared with the target account information generated in the test drive reservation process. If the two match completely (including the account identifier is the same and the bound mobile phone number is the same); at the same time, the validity of the login behavior is verified (such as the login time is within the reserved test drive period and the login device is the vehicle system of the current test drive vehicle); after the above conditions are met, the user can be determined to be a customer.

[0099] By leveraging login information, the login status of accounts in vehicles can be verified more accurately, the login status of target accounts can be clearly identified, and the identities of product experts and customers can be precisely distinguished. This effectively reduces interference from non-customer groups on the authenticity of test drive data, provides a more reliable basis for determining the authenticity of test drives, and improves the accuracy and credibility of the overall verification process.

[0100] In some embodiments, the authenticity of a test drive can be assessed by analyzing the time difference between test drive voice data and test drive operation data related to the same target function. Combined with... Figure 4 ,like Figure 7 As shown, the step S403 above, "determining the authenticity of the test drive based on the first and second times," can be implemented in the following steps:

[0101] S701. Determine the time difference between the first time and the second time.

[0102] As a feasible approach, the first time involving the target function is extracted from the test drive voice data, and the second time involving the same target function is extracted from the test drive operation data. Then, both times are converted into timestamp format to unify the time calculation unit. Finally, the timestamp of the first time is subtracted from the timestamp of the second time, and the result is the time difference between the two.

[0103] S702. When the time difference is less than or equal to the preset time threshold, the authenticity of the test drive is determined to be a real test drive.

[0104] The preset time threshold represents the maximum permissible time interval between the explanation and operation of the vehicle's unified functions. The preset time threshold can be 3 minutes.

[0105] Taking function A as an example, assuming that function A was activated at 15:01:01 based on the test drive operation data, and function A was explained between 14:58:01 and 15:04:01 on the same day based on the test drive voice data, then it can be determined as a real test drive.

[0106] In some embodiments, if the authenticity of the test drive is determined to be a genuine test drive, the user's test drive experience is determined.

[0107] As a feasible implementation method, when it is determined to be a real test drive, the user's test drive experience can be determined by the basic test drive data score and the test drive experience of the vehicle's achievable functions. The scoring indicators for the test drive experience can be set independently based on the vehicle type; this application embodiment does not limit this.

[0108] For example, the basic test drive data score can be scored based on the vehicle's test drive mileage, and the test drive experience of the vehicle's achievable functions can be determined through test drive voice data and test drive operation data.

[0109] For example, as shown in Table 1, this represents the test drive experience for a certain test drive process.

[0110] Table 1 Test Drive Experience

[0111]

[0112]

[0113] As a feasible approach, user test drive experience can be determined using test drive voice data. For example... Figure 8 As shown, this can be achieved through the following steps:

[0114] S801. Based on the test drive voice data, determine the completeness of the explanation of the target function by the test drive instructor's voice explanation segments of the target function.

[0115] Among them, the audio explanation segment is used to represent the audio segment (including the text conversion content with the corresponding timestamp) in which the test drive explanation personnel introduce the target function in the test drive audio data.

[0116] Explanation completeness is used to indicate the extent to which the audio explanation segment covers the core information of the target function.

[0117] For example, a core explanation element library of the target function (such as function definition, operation method, usage scenario, advantages and features, etc.) is pre-built. After the voice explanation segments of the target function extracted from the test drive voice data are converted into text, they are matched with the core explanation element library. The proportion of the number of successfully matched elements to the total number of elements is counted. This proportion is the completeness of the explanation of the target function.

[0118] S802. Determine the test drive experience based on the completeness of the explanation.

[0119] It should be understood that scoring product experts based on the completeness of their explanations, and using this to determine the user's test drive experience, is because the completeness of the explanation directly reflects the product expert's professional mastery of the target function and the quality of their explanation service. A complete explanation not only demonstrates the product expert's familiarity with the functional details but also shows their attention to customer needs, helping customers to fully understand the vehicle's functions and improving the test drive experience. In contrast, an incomplete explanation may expose insufficient professional competence or a perfunctory service attitude, easily leading to cognitive biases in customers and thus affecting their test drive experience.

[0120] As another feasible approach, the user's test drive experience can be determined using test drive voice data and test drive operation data. For example... Figure 9 As shown, step S802 above can be specifically implemented as follows:

[0121] S901. Based on the user's test operation data of the target function, determine the completeness of the user's experience with the target function.

[0122] Among them, the completeness of the experience refers to the ratio between the number of standardized operation steps actually completed by the user for the target function during the test drive and the total number of core operation steps preset for the function.

[0123] For example, a standardized list of operation steps is preset for each target function (such as key steps like starting the function, adjusting parameters, switching modes, and turning off the function); all user operation records for the target function are extracted from the test operation data, including operation time, operation type, and operation result; the extracted operation records are compared with the preset list of steps, and the proportion of the number of operation steps completed by the user to the total number of steps is calculated; this proportion is the completeness of the user's experience with the target function, and the higher the proportion, the more comprehensive the user's experience with the target function.

[0124] S902. Determine the test drive experience level based on the completeness of the experience and the completeness of the explanation.

[0125] For example, such as Figure 10 As shown, when the vehicle is detected to be unregistered, receives a locking signal, and is unoccupied in the driver's seat, the test drive is considered to have ended. After the test drive ends, the test drive voice data and test drive operation data are automatically acquired. By analyzing the test drive voice data and test drive operation data, the completeness of the user experience and the completeness of the product expert's explanation are scored respectively, and the test drive experience is finally comprehensively evaluated.

[0126] The completeness of the experience is determined by analyzing user test drive data of the target functions, and then the completeness of the explanation is combined to determine the test drive experience score. This approach comprehensively measures the test drive process from two dimensions: actual user operation and expert explanation. It ensures accurate capture of the user's real experience while incorporating the influence of professional service quality, making the resulting test drive experience score more objective and comprehensive. This provides a reliable basis for evaluating test drive effectiveness and optimizing services.

[0127] In some embodiments, the test drive experience of each target function can be determined first, and then the overall test drive experience of the vehicle can be determined by considering the test drive experience of all achievable functions in the vehicle. For example... Figure 11 As shown, step S902 above can be specifically implemented as follows:

[0128] S1101. Based on the completeness of the experience and the completeness of the explanation, determine the test drive experience of the target function.

[0129] As a feasible approach, first assign corresponding weights to the completeness of the experience and the completeness of the explanation (the weights can be set according to the degree of influence of the two on the experience of the target function, such as each accounting for 50%). Then, the user's score on the completeness of the experience of the target function and the product expert's score on the completeness of the explanation of the function are weighted and calculated according to the set weights. The result is the test drive experience score of the target function.

[0130] This method of weighting the evaluation based on the importance of experience and explanation can reflect the difference in their impact on the target function experience, making the score more in line with the actual experience.

[0131] As another feasible approach, pre-set scoring criteria for experience completeness and explanation completeness (e.g., different scores corresponding to different completeness ratio ranges), determine the experience completeness score and explanation completeness score corresponding to the target function based on these criteria, and then add these two scores together to obtain the test drive experience score of the target function.

[0132] The system allows for direct addition based on preset scoring criteria, making it simple and intuitive to operate and providing quick results, making it suitable for scenarios with high efficiency requirements.

[0133] S1102. Determine the user's test drive experience based on the test drive experience of the target function and the test drive experience of other functions in the vehicle besides the target function.

[0134] As a feasible approach, first identify all the functions in the vehicle that need to be considered (including the target function and other functions), and assign a weight to the test drive experience of each function (determined based on the importance of the function, with important functions having higher weights); then multiply the test drive experience score of each function by its corresponding weight, and finally add all the products together to obtain the overall test drive experience score for the user.

[0135] By assigning weights to functions based on their importance, the scoring can reflect the different impacts of various functions on the user experience, making the scores more consistent with actual user experiences.

[0136] As another feasible approach, the test drive experience score of the target function can be directly added to the test drive experience scores of other functions in the vehicle besides the target function, and the result can be used as the user's test drive experience score.

[0137] It directly adds up the experience scores of each function, making the calculation convenient and providing a quick overall score. It is suitable for scenarios where the importance of each function is not differentiated too much.

[0138] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the test run authenticity determination device or electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0139] This application embodiment can, based on the above method, exemplarily divide the test run authenticity determination device or electronic device into functional modules. For example, the test run authenticity determination device or electronic device may include functional modules corresponding to each functional division, or two or more functions may be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0140] Reference Figure 12The test drive authenticity determination device 1200 includes: an acquisition module 1201 and a determination module 1202; the acquisition module 1201 is used to acquire the user's test drive voice data and test drive operation data; the determination module 1202 is used to determine the authenticity of the test drive based on a first time in the test drive voice data involving the target function and a second time in the test drive operation data involving the target function; wherein, the target function is any function that the vehicle can achieve.

[0141] In one possible implementation, the determining module 1202 is specifically used to obtain the user's login information on the vehicle; to authenticate the user based on the login information; and, if the user is verified to be a customer, to determine the authenticity of the test drive based on a first time and a second time.

[0142] In one possible implementation, the determining module 1202 is specifically used to determine the time difference between the first time and the second time; if the time difference is less than or equal to a preset time threshold, the authenticity of the test run is determined to be a real test run.

[0143] In one possible implementation, module 1202 is specifically used to determine whether the vehicle is logged into the target account based on login information; the target account is the account issued to the user during the test drive reservation process; if the vehicle is logged into the target account, the user is determined to be a customer.

[0144] In one possible implementation, the determining module 1202 is further configured to determine the user's test drive experience if the test drive is determined to be a real test drive.

[0145] In one possible implementation, the determining module 1202 is specifically used to determine the completeness of the explanation of the target function based on the audio explanation segments of the test drive instructor on the target function involved in the test drive audio data; and to determine the test drive experience based on the completeness of the explanation.

[0146] In one possible implementation, the determining module 1202 is specifically used to determine the completeness of the user's experience with the target function based on the user's test operation data of the target function; and to determine the test experience level based on the completeness of the experience and the completeness of the explanation.

[0147] In one possible implementation, module 1202 is specifically used to determine the test drive experience of the target function based on the completeness of the experience and the completeness of the explanation; and to determine the user's test drive experience based on the test drive experience of the target function and the test drive experience of other functions in the vehicle besides the target function.

[0148] like Figure 13 As shown, the electronic device 1300 includes, but is not limited to, a processor 1301 and a memory 1302.

[0149] The aforementioned memory 1302 is used to store the executable instructions of the aforementioned processor 1301. It is understood that the aforementioned processor 1301 is configured to execute instructions to implement the test run authenticity determination method in the above embodiments.

[0150] It should be noted that those skilled in the art will understand that Figure 13 The electronic device structure shown does not constitute a limitation on electronic device 13000, which may include more than Figure 13 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0151] Processor 1301 is the control center of electronic device 1300. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in memory 1302, and by calling data stored in memory 1302, it performs various functions and processes data of electronic device 1300, thereby providing overall monitoring of electronic device 1300. Processor 1301 may include one or more processing units. Optionally, processor 1301 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into processor 1301.

[0152] The memory 1302 can be used to store software programs and various data. The memory 1302 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, application programs required by at least one functional module (such as a determination unit, processing unit, etc.), etc. Furthermore, the memory 1302 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0153] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 1302 including instructions, which can be executed by a processor 1301 of an electronic device 1300 to implement the test run authenticity determination method in the above embodiments.

[0154] In actual implementation, Figure 12 The functions of the acquisition module 1201 and the determination module 1202 can both be provided by Figure 13 The processor 1301 calls the computer program stored in the memory 1302 to implement the process. The specific execution process can be found in the method section of the previous embodiment, and will not be repeated here.

[0155] Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), random access memory (RAM), compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device.

[0156] In an exemplary embodiment, this application also provides a computer program product including one or more instructions, which can be executed by the processor 1301 of the electronic device 1300 to complete the test run authenticity determination method in the above embodiments.

[0157] It should be noted that when one or more instructions in the computer-readable storage medium or computer program product are executed by the processor 1301 of the electronic device 1300, they implement the various processes of the above method embodiments and achieve the same technical effect as the above method. To avoid repetition, they will not be described again here.

[0158] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0159] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0160] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0161] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0162] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0163] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope 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 determining the authenticity of a test run, characterized in that, The methods for determining the authenticity of the test run include: Acquire user test drive voice data and test drive operation data; The authenticity of the test drive is determined based on the first time the target function is involved in the test drive voice data and the second time the target function is involved in the test drive operation data; wherein, the target function is any function that the vehicle can perform.

2. The method for determining the authenticity of a test run according to claim 1, characterized in that, The determination of the authenticity of the test drive based on the first time of the test drive voice data involving the target function and the second time of the test drive operation data involving the target function includes: Obtain the user's login information on the vehicle; The user is authenticated based on the login information; If the user is verified to be a customer, the authenticity of the test drive is determined based on the first time and the second time.

3. The method for determining the authenticity of a test run according to claim 1 or 2, characterized in that, Based on the first time and the second time, the authenticity of the test drive is determined, including: Determine the time difference between the first time and the second time; If the time difference is less than or equal to a preset time threshold, the test drive is determined to be a genuine test drive.

4. The method for determining the authenticity of a test run according to claim 2, characterized in that, The process of authenticating the user based on the login information includes: Based on the login information, it is determined whether the vehicle is logged into the target account; the target account is the account issued to the user during the test drive reservation process. If the vehicle is logged into the target account, the user is identified as the customer.

5. The method for determining the authenticity of a test run according to claim 3, characterized in that, The method for determining the authenticity of the test run also includes: If the test drive is confirmed to be a genuine test drive, then the user's test drive experience level is determined.

6. The method for determining the authenticity of a test run according to claim 5, characterized in that, Determining the user's test drive experience includes: Based on the audio explanatory segments of the test drive personnel explaining the target function involved in the test drive audio data, the completeness of the explanation of the target function is determined. The test drive experience level is determined based on the completeness of the explanation.

7. The method for determining the authenticity of a test run according to claim 6, characterized in that, The determination of the test drive experience based on the completeness of the explanation includes: Based on the user's test drive operation data of the target function, determine the completeness of the user's experience with the target function; The test drive experience level is determined based on the completeness of the experience and the completeness of the explanation.

8. The method for determining the authenticity of a test run according to claim 7, characterized in that, The determination of the test drive experience level based on the completeness of the experience and the completeness of the explanation includes: Based on the completeness of the experience and the completeness of the explanation, the test drive experience of the target function is determined; The user's test drive experience is determined based on the test drive experience of the target function and the test drive experience of other functions in the vehicle besides the target function.

9. A device for determining the authenticity of a test run, characterized in that, include: Get the module and determine the module; The acquisition module is used to acquire the user's test drive voice data and test drive operation data; The determination module is used to determine the authenticity of the test drive based on a first time in the test drive voice data involving the target function and a second time in the test drive operation data involving the target function; wherein, the target function is any function that the vehicle can perform.

10. The test run authenticity determination device according to claim 9, characterized in that, include: The determining module is specifically used to obtain the user's login information on the vehicle; The user is authenticated based on the login information; if the user is verified to be a customer, the authenticity of the test drive is determined based on the first time and the second time.

11. A vehicle, characterized in that, Includes the test run authenticity determination device as described in any one of claims 9-10.

12. An electronic device, characterized in that, include: Processor and memory; The memory stores instructions that the processor can execute; When the processor is configured to execute the instructions, the electronic device implements the test vehicle authenticity determination method as described in claims 1-8.

Images