Problem scene reproduction method, system and device of communication log and medium
By acquiring and parsing vehicle communication logs to generate test cases, the time-consuming reproduction problem caused by inaccurate user operation descriptions was solved, the problem was accurately located and efficiently reproduced, and system stability and user experience were improved.
Patent Information
- Application Number
- CN202510877921.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-27
- Publication Date
- 2025-09-23
AI Technical Summary
When reproducing occasional or difficult software problems reported by users, existing technologies have problems such as long reproduction time and low efficiency due to inaccurate user operation descriptions, and the problem is not fixed in a timely manner, which affects product stability and user experience.
By obtaining vehicle communication logs within the target time period, using configuration files to parse the logs to generate element units, and then generating test cases and sending them to the cloud server to simulate problem scenarios, accurate positioning and efficient reproduction can be achieved.
It improves problem location efficiency, shortens problem resolution cycle, reduces business losses, and improves system stability and reliability.
Smart Images
Figure CN120692151A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, system, device, and medium for reproducing problem scenarios in communication logs. Background Art
[0002] Currently, when users report occasional or complex issues, developers typically first attempt to identify the cause of the software defect from existing logs. To reproduce the problem scenario, testers often ask users about their vehicle usage and then analyze the logs based on this information to try to reproduce the software defect. This approach can help resolve some issues to a certain extent and is currently the standard process.
[0003] However, in actual operation, this process has many drawbacks. For one thing, the user in question may not be able to fully and accurately describe the operation process at the time, and may even misdescribe the operation process. This results in the test side spending a lot of time to identify and verify the accuracy of the information when analyzing logs and reproducing the problem. This makes the entire reproduction process time-consuming and cannot accurately output the use case for reproduction immediately. On the other hand, if the reproduction use case output is incorrect, occasional or difficult software defects may remain unfixed after multiple version iterations. This not only creates risks for users to use the car, but also significantly reduces the delivery quality of the test side, affecting the overall stability of the product and user experience. Summary of the Invention
[0004] The Summary of the Invention introduces a series of simplified concepts that will be further described in the Detailed Description of the Invention. The Summary of the Invention of this application is not intended to limit the key features and essential technical features of the claimed technical solution, nor is it intended to determine the scope of protection of the claimed technical solution.
[0005] In a first aspect, an embodiment of the present application provides a method for reproducing a problem scenario in a communication log, the method comprising:
[0006] If problem information of a target vehicle fed back by a user is received at a target time, obtaining a communication log of the target vehicle within a target duration, wherein the target time is within the target duration, and the target vehicle includes multiple communication entities;
[0007] calling a configuration file to parse the communication log to obtain at least one element unit, the configuration file including a parsing rule for the communication log, each element unit including a plurality of elements, each element being used to reflect historical communication information between at least two communication entities;
[0008] A corresponding test case is generated for each of the element units, and the test case is sent to a cloud server so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
[0009] In one embodiment of the present invention, the calling configuration file parses the communication log to obtain at least one element unit, including:
[0010] Using a parsing tool to call the configuration file to obtain the parsing rules;
[0011] The at least one element unit corresponding to the parsing rule is extracted from the communication log based on the parsing rule, wherein the at least one element unit includes a target timestamp, a target interface name, a target interface parameter, a target client identifier, and a target server identifier.
[0012] In one embodiment of the present invention, generating a corresponding test case for each element unit includes:
[0013] Determine the interface call time according to the target timestamp;
[0014] Generate an interface call instruction according to the target interface name and target interface parameters;
[0015] Generate a client startup instruction according to the target client identifier;
[0016] Generate a server connection instruction according to the target server identifier;
[0017] The test case is generated based on the interface call time, the interface call instruction, the client start instruction and the server connection instruction.
[0018] In one embodiment of the present invention, generating a corresponding test case for each of the element units further includes:
[0019] Obtain the time difference between two temporally adjacent element units;
[0020] After the previous test case is generated, the next test case is generated after the time difference has passed.
[0021] In one embodiment of the present invention, when running the test case, the cloud server performs the following steps:
[0022] The client startup instruction and the server connection instruction in the test case are executed in sequence and the interface call instruction is executed based on the interface call time.
[0023] In one embodiment of the present invention, the acquiring of the communication log of the target vehicle within the target duration includes:
[0024] When it is detected that the first log in the communication log does not contain the target interface name, the target client identifier and the target server identifier at the same time, the log sequence in the communication log is traversed until the first log containing the target interface name, the target client identifier and the target server identifier is found.
[0025] In one embodiment of the present invention, the architecture of the communication log is a service-oriented architecture.
[0026] In a second aspect, the present application proposes a communication log problem scenario reproduction system, the system comprising: a data acquisition module, an element extraction module and a problem reproduction module;
[0027] The data acquisition module is configured to: if problem information of a target vehicle fed back by a user is received at a target time, acquire a communication log of the target vehicle within a target time, wherein the target time is within the target time, and the target vehicle includes a plurality of communication entities;
[0028] The element extraction module is configured to: call a configuration file to parse the communication log to obtain at least one element unit, the configuration file including a parsing rule for the communication log, each element unit including a plurality of elements, each element being used to reflect historical communication information between at least two communication entities;
[0029] The problem reproduction module is configured to: generate a corresponding test case for each of the element units, and send the test case to a cloud server so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
[0030] In a third aspect, an electronic device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor is configured to implement the steps of a method for reproducing a problem scenario in a communication log as described in any one of the first aspects above when executing the computer program stored in the memory.
[0031] In a fourth aspect, the present application further proposes a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a method for reproducing a problem scenario in a communication log according to any one of the first aspects.
[0032] In summary, a method for reproducing problem scenarios in a communication log according to an embodiment of the present application, by receiving problem information of a target vehicle fed back by a user at a target time, and obtaining the communication log of the target vehicle within a target time period, can accurately locate the source of the problem, avoid blindly searching in massive logs, and improve the efficiency of problem location. Calling a configuration file to parse the communication log can convert complex log data into valuable information, providing a clear basis for subsequent analysis. Generate a corresponding test case for each of the element units, and execute it through a cloud server to reproduce the problem scenario of the target vehicle, which can highly simulate the real scenario when the problem occurs and achieve accurate reproduction of the problem. This not only helps developers to quickly and accurately understand the nature of the problem, but also greatly shortens the problem-solving cycle, reduces business losses caused by untimely problem handling, but also improves the stability and reliability of the system, and provides a strong guarantee for the efficient operation of the communication system.
[0033] The method for reproducing problem scenarios in communication logs proposed in this application, and other advantages, objectives, and features of this application will be partially reflected in the following description, and will also be understood by technical personnel in this field through research and practice of this application. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present description. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:
[0035] Figure 1 A schematic diagram of a process for reproducing a problem scenario in a communication log provided in an embodiment of the present application;
[0036] Figure 2 A schematic diagram of the structure of a communication log problem scenario reproduction system provided in an embodiment of the present application;
[0037] Figure 3 A schematic diagram of the structure of an electronic device for reproducing problem scenarios in a communication log provided in an embodiment of the present application. DETAILED DESCRIPTION
[0038] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification are described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.
[0039] In this article, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also include elements inherent to such process, method, article or equipment. In the absence of further restrictions, the elements defined by the statement "comprising a ..." do not exclude the presence of other identical elements in the process, method, article or equipment comprising the elements. The term "two or more" includes two or more than two cases.
[0040] See also Figure 1 , which is a flow chart of a method for reproducing a problem scenario in a communication log provided in an embodiment of the present application, which may specifically include:
[0041] S110: If problem information of a target vehicle fed back by a user is received at a target time, obtaining a communication log of the target vehicle within a target duration, wherein the target time is within the target duration, and the target vehicle includes multiple communication entities;
[0042] For example, after receiving user feedback at a target time, the target time is used as a time point, and a target time range is defined. Communication logs for the target vehicle are then collected within this range. For example, if a user reports a vehicle problem at 10 a.m. and the target time range is set to 1 hour before and after, communication logs for the target vehicle will be collected between 9 a.m. and 11 a.m. This allows for precise identification of the time period when the problem occurred, avoids acquiring excessive amounts of irrelevant log information, and improves troubleshooting efficiency.
[0043] S120: Call a configuration file to parse the communication log to obtain at least one element unit, wherein the configuration file includes a parsing rule for the communication log, and each element unit includes multiple elements, each element being used to reflect historical communication information between at least two communication entities;
[0044] For example, a configuration file containing parsing rules for communication logs is called. The logs are parsed according to these rules, breaking the log contents into at least one element unit. For example, a communication log records communication information between different vehicle components. Parsing this information can organize it into units containing specific elements. This helps structure complex log data and facilitates subsequent processing.
[0045] S130: Generate a corresponding test case for each element unit, and send the test case to a cloud server, so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
[0046] Exemplarily, a corresponding test case is generated for each element unit, specifically: a test case is generated based on the at least one element unit, and a test case may include multiple operations, such as starting the client, connecting to the server, and calling the interface. Moreover, there are multiple log lines in the communication log, and one log line corresponds to one element unit. Therefore, the test case can be obtained by multiple log lines, that is, multiple element units. These test cases are sent to the cloud server, and the cloud server runs the test case to simulate the problem scenario of the target vehicle. For example, the element unit records a specific instruction sent by a certain communication subject at a specific time, and the test case will be simulated according to this information to see if the problem can be reproduced. In this way, it is possible to quickly verify whether the problem can be reproduced without actually operating the vehicle, saving time and cost.
[0047] In summary, the method for reproducing problem scenarios in communication logs proposed in the embodiment of the present application, by receiving problem information of the target vehicle fed back by the user at the target time, to obtain the communication log of the target vehicle within the target time, can accurately locate the source of the problem, avoid blindly searching in massive logs, and improve the efficiency of problem location. Calling the configuration file to parse the communication log can convert complex log data into valuable information, providing a clear basis for subsequent analysis. Generate a corresponding test case for each of the element units, and execute it through the cloud server to reproduce the problem scenario of the target vehicle, which can highly simulate the real scenario when the problem occurs and achieve accurate reproduction of the problem. This not only helps developers to quickly and accurately understand the nature of the problem, but also greatly shortens the problem-solving cycle, reduces business losses caused by untimely problem handling, but also improves the stability and reliability of the system, and provides a strong guarantee for the efficient operation of the communication system.
[0048] In some examples, the calling configuration file parses the communication log to obtain at least one element unit, including:
[0049] Using a parsing tool to call the configuration file to obtain the parsing rules;
[0050] The at least one element unit corresponding to the parsing rule is extracted from the communication log based on the parsing rule, wherein the at least one element unit includes a target timestamp, a target interface name, a target interface parameter, a target client identifier, and a target server identifier.
[0051] For example, a parsing tool is used to call a configuration file and obtain pre-set parsing rules from the configuration file. Then, based on the parsing rules, element units containing key information such as the target timestamp, target interface name, target interface parameters, target client identifier, and target server identifier are extracted from the communication log.
[0052] For example, when a user reports a vehicle problem, the problem reproduction process begins. First, the cloud obtains the log path, then starts the Log_Parsing_Tool (log parsing) tool, which loads the configuration file. The configuration file defines the log parsing rules, namely [log time][interface name][interface parameters][client ID][server ID]. For example, the obtained log content is [2000:15:30:22:100]:[SetDoorOpen][1][CDC_01][BGM_02]. The parsing tool will parse this log into the following element units based on the rules in the configuration file: the target timestamp is 2000:15:30:22:100, the target interface name is SetDoorOpen (set the door open state), the target interface parameter is 1, the target client identifier is CDC_(cockpit domain controller)01, and the target server identifier is BGM (background music system)_02. Through such analysis, the originally complex log content can be converted into clear and actionable element units, providing a basis for the subsequent generation of test cases and reproduction of problem scenarios.
[0053] By extracting key elements through clear parsing rules, log content can be more accurately converted into executable test cases. For example, in the above example, the accurately extracted elements can be directly used to generate the corresponding test commands, such as launching the client CDC_01 and connecting to the server BGM_02, then calling the SetDoorOpen interface and passing in parameter 1, greatly improving the efficiency and accuracy of test engineers in reproducing the problem.
[0054] In some examples, generating a corresponding test case for each element unit includes:
[0055] Determine the interface call time according to the target timestamp;
[0056] Generate an interface call instruction according to the target interface name and target interface parameters;
[0057] Generate a client startup instruction according to the target client identifier;
[0058] Generate a server connection instruction according to the target server identifier;
[0059] The test case is generated based on the interface call time, the interface call instruction, the client start instruction and the server connection instruction.
[0060] Exemplarily, the element unit includes a target timestamp, a target interface name, target interface parameters, a target client identifier, and a target server identifier. The interface call time is determined based on the target timestamp; an interface call instruction is generated based on the target interface name and target interface parameters; a client startup instruction is generated based on the target client identifier; and a server connection instruction is generated based on the target server identifier. Finally, a test case is generated based on these instructions.
[0061] For example, the target timestamp in the element unit is "2025-06-26 10:00:00," the target interface name is "Interface A," the target interface parameter is "Parameter 123," the target client identifier is "Client 1," and the target server identifier is "Server 2." After determining the interface call time based on the timestamp, the interface call instruction "Call Interface A at 2025-06-26 10:00:00, passing in parameter 123" is generated. The client startup instruction is "Start Client 1," and the server connection instruction is "Connect to Server 2." Test cases are generated based on these instructions. The test case generation process is detailed, enabling the test cases to more accurately simulate actual communication scenarios and improve the accuracy of problem scenario reproduction.
[0062] In some examples, generating a corresponding test case for each element unit further includes:
[0063] Obtain the time difference between two temporally adjacent element units;
[0064] After the previous test case is generated, the next test case is generated after the time difference has passed.
[0065] For example, the time difference between two chronologically adjacent element units is calculated. After generating a test case for the previous element unit, the test case is generated, followed by a wait time corresponding to the time difference before generating the test case for the next element unit. This allows the generated test cases to more accurately simulate the chronological order of operations in real-world scenarios.
[0066] For example, a log contains two records: the first record indicates a door opening operation at 2000:15:30:22:100, and the second record indicates a window opening operation at 2000:15:30:22:200. The door opening operation and window opening operation correspond to two element units, respectively. We can calculate the time difference between these two element units to be 100ms.
[0067] When generating test cases, the system first generates a corresponding test case for the door opening element, simulating a vehicle door opening. After completing the door opening test case generation, it waits 100ms before generating a corresponding test case for the window opening element, simulating a vehicle window opening. This chronological generation of test cases allows for a more realistic reproduction of the time intervals and sequence of various operations in actual vehicle operation.
[0068] In some examples, when running the test case, the cloud server performs the following steps, including:
[0069] The client startup instruction and the server connection instruction in the test case are executed in sequence and the interface call instruction is executed based on the interface call time.
[0070] For example, the specific execution order for the cloud server to run the test case to reproduce the target vehicle problem scenario is as follows: executing the client startup command and server connection command in the test case in sequence, and executing the interface call command based on the interface call time. In the test case generated according to the above method, the cloud server first executes the "Start Client 1" command, then the "Connect to Server 2" command, and finally executes the "Call Interface A, Pass in Parameters 123" command at 2025-06-26 10:00:00, simulating the actual communication process. This clarifies the execution order of the test case, ensures that the test case execution conforms to the logic of actual communication, and improves the reliability of reproducing the problem scenario.
[0071] In some examples, obtaining the communication log of the target vehicle within a target duration includes:
[0072] When it is detected that the first log in the communication log does not contain the target interface name, the target client identifier and the target server identifier at the same time, the log sequence in the communication log is traversed until the first log containing the target interface name, the target client identifier and the target server identifier is found.
[0073] For example, when it is detected that the first log in the communication log does not contain the target interface name, target client identifier and target server identifier at the same time, the log sequence in the communication log is traversed until the first log containing this information is found. For example: in the acquired communication log, the first log may contain only partial information, such as only the target interface name and target client identifier, but no target server identifier. In this case, it is necessary to traverse the log sequence until the first log containing the target interface name, target client identifier and target server identifier is found. Ensure that the acquired log can accurately reflect the target communication scenario to avoid affecting the subsequent analysis and test case generation due to incomplete information in the first log.
[0074] In some examples, the architecture of the communication log is a service-oriented architecture.
[0075] For example, in the target vehicle's communication system, various communication entities communicate with each other through a service-oriented architecture, and the communication log records the communication information within this architecture. For example, different vehicle components act as service providers and service consumers, communicating through interfaces, and the communication log records information about these interface calls. Clarifying the communication log architecture facilitates better understanding and processing of communication logs, providing a clearer architectural foundation for reproducing problem scenarios.
[0076] like Figure 2 As shown, this application proposes a communication log problem scenario reproduction system, the system includes: a data acquisition module 21, an element extraction module 22 and a problem reproduction module 23;
[0077] The data acquisition module 21 is configured to: if problem information of a target vehicle fed back by a user is received at a target time, acquire the communication log of the target vehicle within a target time, wherein the target time is within the target time, and the target vehicle includes multiple communication entities;
[0078] The element extraction module 22 is configured to: call a configuration file to parse the communication log to obtain at least one element unit, the configuration file including the parsing rules of the communication log, each element unit including a plurality of elements, each element being used to reflect historical communication information between at least two communication entities;
[0079] The problem reproduction module 23 is configured to generate a corresponding test case for each of the element units, and send the test case to a cloud server so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
[0080] The effects of applying the above method in the above system can be found in the description of the above method embodiment, which will not be repeated here.
[0081] like Figure 3 As shown, an embodiment of the present application also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored on the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, the steps of a method for reproducing the problem scenario of the above-mentioned communication log are implemented.
[0082] Since the electronic device introduced in this embodiment is a device used to implement a problem scenario reproduction device of a communication log in the embodiment of this application, based on the method introduced in the embodiment of this application, technical personnel in this field can understand the specific implementation method of the electronic device of this embodiment and its various variations. Therefore, how the electronic device implements the method in the embodiment of this application will not be introduced in detail here. As long as the equipment used by technical personnel in this field to implement the method in the embodiment of this application falls within the scope of protection of this application.
[0083] In the specific implementation process, the computer program 311 can be implemented when executed by the processor Figure 1 Any implementation manner in the corresponding embodiments.
[0084] It should be noted that, in the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0085] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-readable program code.
[0086] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0087] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0088] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0089] An embodiment of the present application further provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes the process of the LDPC decoding method of the solid-state drive controller.
[0090] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).
[0091] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0092] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.
[0093] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0094] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0095] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0096] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
[0097] Although the preferred embodiments of this specification have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of this specification.
[0098] Obviously, those skilled in the art may make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if such changes and modifications fall within the scope of the claims of this specification and their equivalents, this specification is intended to include such changes and modifications.
Claims
1. A method for reproducing a problem scenario in a communication log, characterized in that: The method comprises: If problem information of a target vehicle fed back by a user is received at a target time, obtaining a communication log of the target vehicle within a target duration, wherein the target time is within the target duration, and the target vehicle includes multiple communication entities; calling a configuration file to parse the communication log to obtain at least one element unit, the configuration file including a parsing rule for the communication log, each element unit including a plurality of elements, each element being used to reflect historical communication information between at least two communication entities; A corresponding test case is generated for each of the element units, and the test case is sent to a cloud server so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
2. The method for reproducing problem scenarios in communication logs according to claim 1, characterized in that: The calling configuration file parses the communication log to obtain at least one element unit, including: Using a parsing tool to call the configuration file to obtain the parsing rules; The at least one element unit corresponding to the parsing rule is extracted from the communication log based on the parsing rule, wherein the at least one element unit includes a target timestamp, a target interface name, a target interface parameter, a target client identifier, and a target server identifier.
3. The method for reproducing problem scenarios in communication logs according to claim 1, characterized in that: Generating a corresponding test case for each element unit includes: Determine the interface call time according to the target timestamp; Generate an interface call instruction according to the target interface name and target interface parameters; Generate a client startup instruction according to the target client identifier; Generate a server connection instruction according to the target server identifier; The test case is generated based on the interface call time, the interface call instruction, the client start instruction and the server connection instruction.
4. The method for reproducing problem scenarios in communication logs according to claim 1, characterized in that: Generate a corresponding test case for each element unit, including: Obtain the time difference between two temporally adjacent element units; After the previous test case is generated, the next test case is generated after the time difference has passed.
5. The method for reproducing problem scenarios in communication logs according to claim 3, characterized in that: When running the test case, the cloud server performs the following steps: The client startup instruction and the server connection instruction in the test case are executed in sequence and the interface call instruction is executed based on the interface call time.
6. The method for reproducing problem scenarios in communication logs according to claim 3, characterized in that: The acquiring of the communication log of the target vehicle within the target duration includes: When it is detected that the first log in the communication log does not contain the target interface name, the target client identifier and the target server identifier at the same time, the log sequence in the communication log is traversed until the first log containing the target interface name, the target client identifier and the target server identifier is found.
7. The method for reproducing problem scenarios in communication logs according to claim 1, characterized in that: The architecture of the communication log is a service-oriented architecture.
8. A communication log problem scenario reproduction system, characterized by: The system includes: a data acquisition module, an element extraction module and a problem reproduction module; The data acquisition module is configured to: if problem information of a target vehicle fed back by a user is received at a target time, acquire a communication log of the target vehicle within a target time, wherein the target time is within the target time, and the target vehicle includes a plurality of communication entities; The element extraction module is configured to: call a configuration file to parse the communication log to obtain at least one element unit, the configuration file including a parsing rule for the communication log, each element unit including a plurality of elements, each element being used to reflect historical communication information between at least two communication entities; The problem reproduction module is configured to: generate a corresponding test case for each of the element units, and send the test case to a cloud server so that the cloud server runs the test case to reproduce the problem scenario of the target vehicle.
9. An electronic device comprising: A memory and a processor, wherein the processor is configured to implement the steps of a method for reproducing a problem scenario in a communication log according to any one of claims 1 to 7 when executing a computer program stored in the memory.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of a method for reproducing a problem scenario in a communication log are implemented as described in any one of claims 1 to 7.