Information dump method and apparatus, storage medium, and program product

Abstract

The present application relates to the field of fault diagnosis, and provides an information dump method and apparatus, a storage medium, and a program product. The method comprises: acquiring content in one or more virtual memory area segments within an address space of a process that is abnormally terminated; on the basis of the content in the one or more virtual memory area segments, obtaining a secure dump file for pinpointing a cause of the abnormal termination of the process, the secure dump file comprising content obtained by compressing and / or encrypting the content in at least one of the one or more virtual memory area segments. Compressing content in at least one virtual memory area segment reduces secure dump file size, enables compatibility with memory-constrained devices, and achieves broader applicability; while encrypting the content in the at least one virtual memory area segment improves information security, making the method suitable for devices with stringent information security requirements.

Description

An information dumping method, apparatus, storage medium, and program product Technical Field

[0001] This application relates to the field of fault diagnosis, and in particular to an information dumping method, apparatus, storage medium and program product. Background Technology

[0002] Some known fault diagnosis techniques save information such as the process's memory state, register state, and call stack at the time of the failure when a process terminates or crashes abnormally. Fault diagnosis technicians can then use this information to debug and locate the cause of the abnormal process termination or crash.

[0003] For example, core dump (Coredump) is a widely used general-purpose troubleshooting (design for X, DFX) technique in Linux systems, primarily used to locate unexpected process crashes. This technique is widely used in server, embedded device, and container system environments. When a process terminates abnormally, this core dump method can save the process's memory state, register state, and call stack at the time of the failure into a core dump file (also called a core file). Subsequently, troubleshooting technicians can use debugging tools to parse this core dump file, obtain key information about the process at the time of the abnormal termination, and determine the cause of the abnormal process termination.

[0004] However, the known fault diagnosis methods have certain application limitations. For example, they are not suitable for some devices with small memory space, or for some devices with high information security requirements. Summary of the Invention

[0005] This application provides an information dumping method, apparatus, storage medium, and program product, with the aim of enabling fault diagnosis technology to have better universality.

[0006] In a first aspect, this application provides an information dumping method. The steps of the method can be executed by an information dumping device, or the method can be executed by a component (such as a chip, chip system, etc.) configured in the information dumping device, or it can be implemented by a logic module or software capable of realizing all or part of the functions of the information dumping device. This application does not limit the scope of the method.

[0007] As an example and not a limitation, in the vehicle field, an information dumping device can be a vehicle, an in-vehicle device, or an in-vehicle system; in other fields besides the vehicle field, an information dumping device can be other smart terminals or systems mounted on other smart terminals.

[0008] For example, the method includes: obtaining the contents of one or more virtual memory regions in the address space of a target process, the target process being a process that has abnormally terminated on the information dumping device; obtaining a security dump file based on the contents of the one or more virtual memory regions; wherein the security dump file includes compressed and / or encrypted contents of at least one of the one or more virtual memory regions, the security dump file being used to locate the cause of the abnormal termination of the target process.

[0009] Based on the above technical solution, by compressing the contents of at least one virtual memory region of the target process, the size of the generated security dump file used to locate the cause of the abnormal termination of the target process can be reduced, which can be adapted to devices with small memory space and has good universality; by encrypting the contents of at least one virtual memory region of the target process, information security can be improved, which can be adapted to devices with high information security requirements.

[0010] In conjunction with the first aspect, in some possible implementations, obtaining the contents of one or more virtual memory regions in the address space of the target process includes: obtaining attribute information corresponding to a first virtual memory region in the address space of the target process, wherein the first virtual memory region is any virtual memory region in the address space of the target process; and obtaining the contents of the first virtual memory region when the attribute information satisfies the target conditions.

[0011] By obtaining attribute information of one or more virtual memory regions of the target process, the contents of virtual memory regions that meet the target conditions are dumped into a safe dump file. This reduces the size of the generated safe dump file used to locate the cause of the abnormal termination of the target process, making it suitable for devices with limited memory space and having good universality. In addition, by excluding some content that is not related to the cause of the abnormal termination of the target process, the efficiency of fault diagnosis can be improved.

[0012] In conjunction with the first aspect, in some possible implementations, the attribute information is used to indicate whether write permission and / or the corresponding physical memory are available, and the target condition includes: having write permission, and / or the corresponding physical memory being greater than zero; wherein, the target condition is used to determine whether the content of the first virtual memory region segment includes target content, and the target content is related to the reason for the abnormal termination of the target process.

[0013] By using attribute information to indicate write permissions and / or the presence of physical memory, the contents of virtual memory segments containing actual data can be dumped. In other words, content unrelated to the cause of the target process's abnormal termination can be filtered out, effectively filtering out content that may be related to the cause of the target process's abnormal termination, reducing unnecessary data storage and processing, and improving resource utilization efficiency.

[0014] In conjunction with the first aspect, in some possible implementations, the attribute information is used to indicate the size of the content in the first virtual memory region segment, and the target condition includes: the size of the content in the first virtual memory region segment is greater than or equal to a first threshold.

[0015] By limiting the size of the contents dumped to the safe dump file, the contents of virtual memory regions containing a large amount of content can be dumped to the safe dump file for further processing; the contents of virtual memory regions containing a small amount of content can be processed using currently known dumping methods (such as kernel dumping methods), without needing to further process the contents of all virtual memory regions of the target process. This not only improves data processing efficiency but also reduces resource waste.

[0016] In conjunction with the first aspect, in some possible implementations, the method further includes: when the attribute information does not meet the target condition, but the first virtual memory region is configured to require dumping, obtaining the contents of the first virtual memory region.

[0017] Even if the attribute information does not meet the target conditions, the contents of the virtual memory region segment configured to be dumped can still be dumped. This can flexibly adapt to actual needs, ensure that critical data is not missed due to condition limitations, and improve the comprehensiveness of fault diagnosis.

[0018] In conjunction with the first aspect, in some possible implementations, obtaining a security dump file based on the content in the one or more virtual memory regions includes: compressing the content in the one or more virtual memory regions to obtain target compressed content; obtaining the security dump file based on the target compressed content, wherein the security dump file includes the target compressed content.

[0019] Compressing the contents of one or more virtual memory regions in the address space of the target process can reduce storage space usage, improve data transmission and storage efficiency, further reduce the memory space requirements of the device, and has good universality.

[0020] In conjunction with the first aspect, in some possible implementations, compressing the content in the one or more virtual memory regions includes: compressing the content of a second virtual memory region based on a first compression parameter, the first compression parameter indicating whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed; wherein, the second virtual memory region is any one of the one or more virtual memory regions.

[0021] By controlling the compression process using compression parameters, it is possible to flexibly adapt to different storage and performance requirements, thereby improving the flexibility and adaptability of the compression process.

[0022] In conjunction with the first aspect, in some possible implementations, the method further includes: obtaining a second compression parameter, which indicates whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed, the second compression parameter being different from the first compression parameter; and updating the first compression parameter to the second compression parameter.

[0023] By updating the compression parameters for a specific virtual memory region, the compression strategy can be dynamically adjusted to adapt to different environments and changing needs, offering high flexibility and versatility.

[0024] In conjunction with the first aspect, in some possible implementations, obtaining a security dump file based on the content in the one or more virtual memory regions includes: encrypting the content in the one or more virtual memory regions to obtain target encrypted content; obtaining the security dump file based on the target encrypted content, wherein the security dump file includes the target encrypted content.

[0025] Encrypting the contents of one or more virtual memory regions in the address space of the target process can effectively protect sensitive data, prevent information leakage, and improve information security.

[0026] In conjunction with the first aspect, in some possible implementations, encrypting the content in the one or more virtual memory regions includes: encrypting the content of the second virtual memory region based on a first encryption parameter, the first encryption parameter being used to indicate whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted; wherein the second virtual memory region is any one of the one or more virtual memory regions.

[0027] By using encryption parameters to control the encryption process, encryption strategies can be flexibly selected to adapt to different security needs.

[0028] In conjunction with the first aspect, in some possible implementations, the method further includes: obtaining a second encryption parameter, which indicates whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted, the second encryption parameter being different from the first encryption parameter; and updating the first encryption parameter to the second encryption parameter.

[0029] By updating the encryption parameters for a specific virtual memory region, the encryption strategy can be dynamically adjusted to adapt to different security needs and environmental changes, exhibiting high flexibility and versatility.

[0030] In conjunction with the first aspect, in some possible implementations, the method also includes compressing the security dump file.

[0031] Compressing the security dump file can further reduce the storage space occupied, thereby further reducing the memory space requirements of the device, and has good universality.

[0032] In conjunction with the first aspect, in some possible implementations, the security dump file is compressed, including: compressing the security dump file based on a third compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed.

[0033] By using compression parameters to control the compression process of secure dump files, different storage and performance requirements can be flexibly adapted.

[0034] In conjunction with the first aspect, in some possible implementations, the method further includes: obtaining a fourth compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed, the fourth compression parameter being different from the third compression parameter; and updating the fourth compression parameter to the third compression parameter.

[0035] By updating the compression parameters for secure dump files, the compression strategy can be dynamically adjusted to adapt to different environments and changing needs, offering high flexibility and versatility.

[0036] In conjunction with the first aspect, in some possible implementations, the method also includes encrypting the secure dump file.

[0037] Encrypting secure dump files can further protect sensitive information within the files, prevent unauthorized access, and enhance information security.

[0038] In conjunction with the first aspect, in some possible implementations, the security dump file is encrypted, including: encrypting the security dump file based on a third encryption parameter, which indicates whether the security dump file needs to be encrypted, and / or, based on which encryption algorithm the security dump file is encrypted.

[0039] By using encryption parameters to control the encryption process of securely dumped files, encryption strategies can be flexibly selected to adapt to different security needs.

[0040] In conjunction with the first aspect, in some possible implementations, the method further includes: obtaining a fourth encryption parameter, which indicates whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted, the fourth encryption parameter being different from the third encryption parameter; and updating the third encryption parameter to the fourth encryption parameter.

[0041] By updating the encryption parameters for secure dump files, the encryption strategy can be dynamically adjusted to adapt to different security needs and environmental changes, exhibiting high flexibility and versatility.

[0042] Secondly, this application provides an information dumping method. The steps of the method can be executed by a cloud server, or the method can be executed by a component (such as a chip, chip system, etc.) configured in the cloud server, or it can be implemented by a logic module or software capable of implementing all or part of the functions of the cloud server. This application does not limit the scope of the method.

[0043] For example, the method includes: receiving a target file from an information dumping device; wherein the target file is associated with a security dump file used to locate the cause of the abnormal termination of the target process, the security dump file including compressed and / or encrypted content of at least one virtual memory region segment in one or more virtual memory region segments in the address space of the target process, the target process being the process that has abnormally terminated on the information dumping device.

[0044] Based on the above technical solution, the cloud server receives the target file from the information dumping device, enabling centralized management and analysis of fault diagnosis data in the cloud, thereby improving the efficiency and response speed of fault diagnosis.

[0045] Thirdly, this application provides an information dumping method. The steps of the method can be executed by an information dumping device, or the method can be executed by a component (such as a chip, chip system, etc.) configured in the information dumping device, or it can be implemented by a logic module or software capable of realizing all or part of the functions of the information dumping device. This application does not limit the scope of the method.

[0046] As an example and not a limitation, in the field of vehicles, an information dumping device can be an in-vehicle device or an in-vehicle system.

[0047] For example, the method includes: obtaining attribute information corresponding to a first virtual memory region segment in the address space of a target process, wherein the target process is a process that has abnormally terminated on the information dumping device, and the first virtual memory region segment is any virtual memory region segment in the address space of the target process; and, if the attribute information meets the target conditions, dumping the contents of the first virtual memory region segment to a secure dump file, wherein the secure dump file is used to locate the cause of the abnormal termination of the target process.

[0048] Based on the above technical solution, by obtaining the attribute information of the virtual memory region segment of the target process, the contents of the virtual memory region segment that meets the target conditions are dumped into a safe dump file. This reduces the size of the generated safe dump file used to locate the cause of the abnormal termination of the target process, making it suitable for devices with small memory space and having good universality. In addition, it excludes some content that is not related to the cause of the abnormal termination of the target process, which can improve the efficiency of fault diagnosis.

[0049] In conjunction with the third aspect, in some possible implementations, the attribute information is used to indicate whether there is write permission and / or corresponding physical memory, and the target condition includes: having write permission, and / or, the corresponding physical memory is greater than zero; wherein, the target condition is used to determine whether the content of the first virtual memory region segment includes target content, and the target content is used to locate the reason for the abnormal termination of the target process.

[0050] By using attribute information to indicate write permissions and the presence of physical memory, the contents of virtual memory segments containing actual data can be dumped. In other words, content unrelated to the cause of the target process's abnormal termination can be filtered out, effectively filtering out content that may be related to the cause of the target process's abnormal termination, reducing unnecessary data storage and processing, and improving resource utilization efficiency.

[0051] In conjunction with the third aspect, in some possible implementations, the attribute information is used to indicate the size of the content in the first virtual memory region segment, and the target condition includes: the size of the content in the first virtual memory region segment is greater than or equal to a first threshold.

[0052] The first threshold can be pre-configured.

[0053] By limiting the size of the contents dumped to the safe dump file, the contents of virtual memory regions containing a large amount of content can be dumped to the safe dump file for further processing; the contents of virtual memory regions containing a small amount of content can be processed using currently known dumping methods (such as kernel dumping methods), without needing to further process the contents of all virtual memory regions of the target process. This not only improves data processing efficiency but also reduces resource waste.

[0054] In conjunction with the third aspect, in some possible implementations, the method further includes: if the attribute information does not meet the target condition, but the first virtual memory region segment is configured to require dumping, dumping the contents of the first virtual memory region segment to the secure dump file.

[0055] Even if the attribute information does not meet the target conditions, the contents of the virtual memory region segment configured to be dumped can still be dumped. This can flexibly adapt to actual needs, ensure that critical data is not missed due to conditional limitations, and improve the comprehensiveness of fault diagnosis.

[0056] In conjunction with the third aspect, in some possible implementations, the method further includes: compressing the contents of the first virtual memory region segment.

[0057] Compressing the contents of virtual memory regions can reduce storage space usage, improve data transmission and storage efficiency, further reduce the memory space requirements of devices, and has good versatility.

[0058] In conjunction with the third aspect, in some possible implementations, compressing the content of the first virtual memory region segment includes: compressing the content of the first virtual memory region segment based on a first compression parameter, the first compression parameter being used to indicate whether the content of the first virtual memory region segment needs to be compressed, and / or, based on which compression algorithm the content of the first virtual memory region segment is compressed.

[0059] By controlling the compression process using compression parameters, it is possible to flexibly adapt to different storage and performance requirements, thereby improving the flexibility and adaptability of the compression process.

[0060] In conjunction with the third aspect, in some possible implementations, the method further includes: obtaining a second compression parameter, which indicates whether the content of the first virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the first virtual memory region is compressed, the second compression parameter being different from the first compression parameter; and updating the first compression parameter to the second compression parameter.

[0061] By updating the compression parameters for virtual memory regions, the compression strategy can be dynamically adjusted to adapt to different environments and changing needs, exhibiting high flexibility and versatility.

[0062] In conjunction with the third aspect, in some possible implementations, the method also includes compressing the security dump file.

[0063] Compressing the security dump file can further reduce the storage space occupied, thereby further reducing the memory space requirements of the device, and has good universality.

[0064] In conjunction with the third aspect, in some possible implementations, the security dump file is compressed, including: compressing the security dump file based on a third compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed.

[0065] By using compression parameters to control the compression process of secure dump files, different storage and performance requirements can be flexibly adapted.

[0066] In conjunction with the third aspect, in some possible implementations, the method further includes: obtaining a fourth compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed, the fourth compression parameter being different from the third compression parameter; and updating the third compression parameter to the fourth compression parameter.

[0067] By updating the compression parameters for secure dump files, the compression strategy can be dynamically adjusted to adapt to different environments and changing needs, offering high flexibility and versatility.

[0068] In conjunction with the third aspect, in some possible implementations, the method further includes encrypting the contents of the first virtual memory region segment.

[0069] Encrypting the contents of virtual memory regions can effectively protect sensitive data, prevent information leakage, and improve information security.

[0070] In conjunction with the third aspect, in some possible implementations, encrypting the content in the first virtual memory region segment includes: encrypting the content in the first virtual memory region segment based on a first encryption parameter, the first encryption parameter being used to indicate whether the content in the first virtual memory region segment needs to be encrypted, and / or, based on which encryption algorithm the content in the first virtual memory region segment is encrypted.

[0071] By using encryption parameters to control the encryption process, encryption strategies can be flexibly selected to adapt to different security needs.

[0072] In conjunction with the third aspect, in some possible implementations, the method further includes: obtaining a second encryption parameter, which indicates whether the content in the first virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content in the first virtual memory region is encrypted, the second encryption parameter being different from the first encryption parameter; and updating the first encryption parameter to the second encryption parameter.

[0073] By updating the encryption parameters for virtual memory regions, encryption strategies can be dynamically adjusted to adapt to different security needs and environmental changes, exhibiting high flexibility and versatility.

[0074] In conjunction with the third aspect, in some possible implementations, the method also includes encrypting the secure dump file.

[0075] Encrypting secure dump files can further protect sensitive information within the files, prevent unauthorized access, and enhance information security.

[0076] In conjunction with the third aspect, in some possible implementations, the security dump file is encrypted, including: encrypting the security dump file based on a third encryption parameter, which indicates whether the security dump file needs to be encrypted, and / or, based on which encryption algorithm the security dump file is encrypted.

[0077] By using encryption parameters to control the encryption process of securely dumped files, encryption strategies can be flexibly selected to adapt to different security needs.

[0078] In conjunction with the third aspect, in some possible implementations, the method further includes: obtaining a fourth encryption parameter, which indicates whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted, the fourth encryption parameter being different from the third encryption parameter; and updating the third encryption parameter to the fourth encryption parameter.

[0079] By updating the encryption parameters for secure dump files, the encryption strategy can be dynamically adjusted to adapt to different security needs and environmental changes, exhibiting high flexibility and versatility.

[0080] In combination with the first and third aspects, in some possible implementations, the method further includes sending a target file associated with the security dump file to a cloud server.

[0081] Sending target files to a cloud server enables remote data backup and management, improving data availability and security.

[0082] In combination with the first and third aspects, in some possible implementations, the method also includes: deleting the security dump file and / or the target file.

[0083] By deleting secure dump files and / or target files after data transfer or processing is complete, storage space can be effectively freed up, storage costs reduced, and the exposure time of sensitive data on local storage devices decreased. This improves data security and privacy protection, helps prevent unauthorized access or data leakage, and is especially beneficial when processing dump files containing sensitive information, ensuring that data is promptly cleaned up after use.

[0084] In combination with the first and third aspects, in some possible implementations, the method further includes: receiving first information from the cloud server, the first information being used to indicate that the cloud server is a trusted device for the information dumping device.

[0085] By receiving initial information from the cloud server, indicating that the cloud server is a trusted device for the information dumping device, a trust relationship can be established between the information dumping device and the cloud server. This trust relationship contributes to the security of data transmission, preventing data from being sent to untrusted servers, thereby improving data security and integrity. By confirming the trustworthiness of the cloud server, the information dumping device can exchange data and collaborate with it with greater confidence.

[0086] In combination with the first and third aspects, in some possible implementations, the method further includes: sending a second message to the cloud server, the second message indicating that the information dumping device is a trusted device of the cloud server.

[0087] By sending a second message to the cloud server indicating that the data dump device is a trusted device of the cloud server, a two-way trust relationship can be established between the cloud server and the data dump device. This two-way authentication mechanism ensures that only authenticated devices can interact with the cloud server, thereby preventing unauthorized devices from accessing sensitive data. This measure improves the overall security of the system, enabling data to be transmitted and processed between trusted devices and reducing potential security risks.

[0088] Fourthly, this application provides an information dumping method. The steps of this method can be executed by a cloud server, or the method can be executed by a component (such as a chip, chip system, etc.) configured in the cloud server, or it can be implemented by a logic module or software capable of implementing all or part of the functions of the cloud server. This application does not limit the scope of this method.

[0089] For example, the method includes: receiving a target file from an information dumping device; wherein the target file is associated with a security dump file, the security dump file includes the contents of a virtual memory region segment in the address space of a target process that satisfies the target conditions, the target process being a process that has abnormally terminated on the information dumping device, and the security dump file being used to locate the cause of the abnormal termination of the target process.

[0090] Based on the above technical solution, the cloud server receives the target file from the information dumping device, enabling centralized management and analysis of fault diagnosis data in the cloud, thereby improving the efficiency and response speed of fault diagnosis.

[0091] In combination with the second and fourth aspects, in some possible implementations, the target file is a compressed file, and the method further includes: decompressing the target file.

[0092] By decompressing the target file in the compressed format, the original data can be recovered, which facilitates subsequent analysis and processing and improves the usability of the data.

[0093] Combining the second and fourth aspects, in some possible implementations, the target file contains encrypted content, and the method further includes: decrypting the encrypted content in the target file.

[0094] By decrypting the encrypted content in the target file, data can remain secure during transmission and can be correctly read and analyzed in the cloud, thus improving data security and availability.

[0095] In conjunction with the second and fourth aspects, in some possible implementations, the method further includes: sending first information to the information dumping device, the first information being used to instruct the cloud server to be a trusted device of the information dumping device.

[0096] Sending initial information from a cloud server to the data transfer device, indicating that the cloud server is a trusted device, enhances the data transfer device's trust in the cloud server. This trust mechanism helps the data transfer device verify the trustworthiness of the data recipient when interacting with the cloud server, thereby preventing data leakage or interception by untrusted servers. This measure improves the security of data transmission, ensuring that data is processed only in a trusted environment.

[0097] In conjunction with the second and fourth aspects, in some possible implementations, the method further includes: receiving second information from the information dumping device, the second information being used to indicate that the information dumping device is a trusted device of the cloud server.

[0098] By receiving a second message from the information dumping device, indicating that the information dumping device is a trusted device of the cloud server, a two-way trust relationship can be established between the cloud server and the information dumping device. This two-way authentication mechanism ensures that only authenticated devices can interact with the cloud server, preventing unauthorized devices from accessing or uploading data. This measure improves the overall security of the system, enabling data to be transmitted and processed between trusted devices, reducing potential security risks and the possibility of information leakage.

[0099] In conjunction with the second and fourth aspects, in some possible implementations, the method further includes: converting the security dump file into a core dump file, the core dump file having a different format from the security dump file; and storing the core dump file.

[0100] Core dump files are typically in a standardized format, suitable for a variety of analysis tools and platforms. Converting security dump files to this format makes the file format compatible with existing debugging and analysis tools, enabling fault diagnosis technicians to analyze and diagnose faults using familiar tools and processes, thereby accelerating the fault diagnosis process.

[0101] In conjunction with aspects one through four, in some possible implementations, the object file being associated with the secure dump file includes: the object file including security parameters and / or compression parameters, the security parameters being associated with parameters used to encrypt the secure dump file, and the compression parameters being associated with parameters used to compress the secure dump file.

[0102] By including security parameters and / or compression parameters related to the secure dump file in the target file, data encryption and / or compression can be properly handled in the cloud environment, which can improve data security, transmission efficiency, and the effectiveness of data management.

[0103] In conjunction with aspects one through four, in some possible implementations, the security parameter is pre-stored, or the security parameter is determined through negotiation with the cloud server; and / or, the compression parameter is pre-stored, or the compression parameter is determined through negotiation with the cloud server.

[0104] By pre-storing or negotiating security and / or compression parameters, appropriate strategies can be used for data processing in the cloud environment, improving data security, transmission efficiency, and the effectiveness of data management.

[0105] Fifthly, this application provides an information dumping apparatus, which includes execution steps for performing the first aspect and any possible implementation thereof, or includes execution steps for performing the third aspect and any possible implementation thereof. The apparatus includes corresponding modules for performing the above-described methods. The modules included in the apparatus can be implemented in software and / or hardware.

[0106] Sixthly, this application provides an information dumping device, which includes a processor. The processor is coupled to a memory and can be used to execute a program in the memory to implement the execution steps in the first aspect and any possible implementation of the first aspect, or to implement the execution steps in the third aspect and any possible implementation of the third aspect.

[0107] Optionally, the information dumping device may also include a memory.

[0108] Optionally, the information dumping device also includes a communication interface, and the processor is coupled to the communication interface.

[0109] Seventhly, this application provides a vehicle that includes the information storage device described in the fifth or sixth aspect above.

[0110] Eighthly, this application provides a cloud server, which includes execution steps for performing the second aspect and any possible implementation of the second aspect, or includes execution steps for performing the fourth aspect and any possible implementation of the fourth aspect. The cloud server includes corresponding modules for performing the above methods. The modules included in the cloud server can be implemented by software and / or hardware.

[0111] Ninthly, this application provides a cloud server including a processor. The processor is coupled to a memory and can be used to execute a program in the memory to implement the execution steps in any of the possible implementations of the second and second aspects above, or to implement the execution steps in any of the possible implementations of the fourth aspect above.

[0112] Optionally, the cloud server also includes storage.

[0113] Optionally, the cloud server also includes a communication interface, with the processor coupled to the communication interface.

[0114] In a tenth aspect, this application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in the first aspect and any possible implementation of the first aspect, or for supporting the implementation of the functions involved in the second aspect and any possible implementation of the second aspect, or for supporting the implementation of the functions involved in the third aspect and any possible implementation of the third aspect, or for supporting the implementation of the functions involved in the fourth aspect and any possible implementation of the fourth aspect, for example, receiving or processing data and / or instruction information involved in the above methods.

[0115] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0116] The chip system can consist of chips or include chips and other discrete components.

[0117] Eleventhly, this application provides a computer-readable storage medium storing a program (also referred to as code or instructions) that, when executed by a processor, causes the method in the first aspect and any possible implementation thereof to be executed, or causes the method in the second aspect and any possible implementation thereof to be executed, or causes the method in the third aspect and any possible implementation thereof to be executed, or causes the method in the fourth aspect and any possible implementation thereof to be executed.

[0118] In a twelfth aspect, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when executed, causes the method in the first aspect and any possible implementation thereof to be executed, or causes the method in the second aspect and any possible implementation thereof to be executed, or causes the method in the third aspect and any possible implementation thereof to be executed, or causes the method in the fourth aspect and any possible implementation thereof to be executed.

[0119] It should be understood that the fifth to twelfth aspects of this application correspond to the technical solutions of the first to fourth aspects of this application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0120] Figure 1 is a flowchart illustrating the core dump method;

[0121] Figure 2 is a schematic flowchart of an information dumping method provided in an embodiment of this application;

[0122] Figure 3 is a schematic diagram of a secure dump file provided in an embodiment of this application;

[0123] Figure 4 is a schematic diagram of a secure dump file encryption part provided in an embodiment of this application;

[0124] Figure 5 is a schematic diagram of a secure dump file compression section provided in an embodiment of this application;

[0125] Figure 6 is a schematic diagram of a secure dump file encryption and compression part provided in an embodiment of this application;

[0126] Figure 7 is a schematic diagram of an information dumping device establishing a trust relationship with a cloud server;

[0127] Figure 8 is a schematic diagram of various implementation methods for configuring one or more processes on an information dumping device according to embodiments of this application;

[0128] Figure 9 is a comparative diagram showing different processes configured with different dump methods;

[0129] Figure 10 is a schematic diagram of a system architecture applicable to the information dumping method provided in the embodiments of this application;

[0130] Figure 11 is a schematic diagram of another system architecture applicable to the information dumping method provided in the embodiments of this application;

[0131] Figure 12 is another schematic flowchart of the information dumping method provided in the embodiments of this application;

[0132] Figure 13 is a schematic block diagram of the device provided in an embodiment of this application;

[0133] Figure 14 is another schematic block diagram of the device provided in the embodiments of this application. Detailed Implementation

[0134] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0135] First, in this application, the terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, an apparatus, system, product or device that includes a series of modules, units or units is not necessarily limited to those modules, units or units that are explicitly listed, but may include other modules, units or units that are not explicitly listed or that are inherent to such apparatus, system, product or device.

[0136] Second, in this application, the words "exemplarily" and "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design that is described as "exemplarily" 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 words such as "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0137] Third, in this application, "when," "under the circumstances," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

[0138] Fourth, in this application, the terms "first" and "second" are used to distinguish identical or similar items with essentially the same function and effect. For example, the terms "first encryption parameter," "second encryption parameter," "third encryption parameter," and "fourth encryption parameter" are used to distinguish different encryption parameters, and the terms "first compression parameter," "second compression parameter," "third compression parameter," and "fourth compression parameter" are used to distinguish different compression parameters, without limiting their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0139] Fifth, in this application, "preset" can be understood as predefined, defined, pre-defined, stored, pre-stored, pre-negotiated, or pre-configured, etc.

[0140] Sixth, in this application, "at least one (kind, type)" refers to one (kind, type) or multiple (kinds, types). "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the preceding and following related objects, but it does not exclude the possibility of indicating an "and" relationship. The specific meaning can be understood in conjunction with the context.

[0141] Seventh, in this application, information C is used to determine information D, including both determining information D based solely on information C and determining it based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, in the case where information D is determined based on information E, and information E is determined based on information C.

[0142] To facilitate understanding of the embodiments of this application, some technical terms or vocabulary involved in this application will be briefly explained below.

[0143] 1. Process: A process is the basic unit by which the operating system allocates resources (such as memory, central processing unit (CPU) time, etc.) and schedules tasks. It can be understood that an application can correspond to one or more processes.

[0144] Processes can include system processes (or kernel processes) and user processes.

[0145] System processes are processes started and managed by the operating system, typically used to execute core operating system functions and background services. System processes usually run in kernel space and have higher privileges and priority.

[0146] User processes are processes started and run by ordinary users in the operating system, and are typically used to execute user applications and tasks.

[0147] In this application, all processes other than those specifically designated as system processes can be understood as user processes.

[0148] 2. Process address space: This refers to the range of memory that a process can access during its execution. Each process has its own independent address space, which prevents memory interference between processes.

[0149] 3. Virtual memory area (VMA) segments: These are contiguous memory regions within a process's address space. Each virtual memory area segment has specific attributes and uses, and the operating system manages process memory usage through these segments.

[0150] 4. Core Dump File: Also known simply as the core file, this is a file generated by the operating system when a program terminates abnormally. This file contains the memory contents of the program at the time of the crash. The main purpose of a core dump file is to assist developers and system administrators in troubleshooting and debugging.

[0151] 5. Registering a callback: This refers to passing a function (called a callback function) to another function or system in programming so that the callback function can be invoked when a specific event occurs. A callback function is a developer-defined function that can be called when a specific event or condition occurs.

[0152] 6. Configuration file: This is a file used to store settings and parameters for software applications, operating systems, or other system components. Configuration files are usually in text format and allow developers or administrators to adjust the behavior and characteristics of a program without modifying its source code.

[0153] 7. Compression algorithm: An algorithm used to reduce data size by removing redundant information or encoding data in a more efficient way, so as to reduce storage space or transmission time.

[0154] 8. Encryption algorithm: An algorithm used to protect data security by converting plaintext data into ciphertext, making it difficult to understand and use without authorization.

[0155] 9. Segmentation violation (SIGSEGV) signal: Also known as the segmentation fault signal, this signal can be used to indicate an error that occurs when a program attempts to access an unauthorized memory region.

[0156] Currently, some known fault diagnosis methods save information such as the process's memory state, register state, and call stack at the time of the fault when the process terminates or crashes abnormally. Fault diagnosis technicians can then use this information to debug and locate the cause of the abnormal process termination or crash.

[0157] For example, kernel dumping is a widely used general troubleshooting technique in Linux systems, primarily used to locate unexpected process crashes. This technique is widely used in server, embedded device, and container system environments.

[0158] Figure 1 shows a schematic diagram of the core dump method.

[0159] As shown in Figure 1, when a process terminates abnormally, the operating system's kernel can execute a first kernel dump process and a second kernel dump process to save information such as the process's memory state, register state, and call stack at the time of the failure (i.e., key information related to determining the cause of the abnormal process termination, referred to as key information for ease of description) to a kernel file. Subsequently, troubleshooting technicians can use debugging tools to parse this kernel dump file to obtain the key information at the time of the process abnormality, thereby determining the cause of the abnormal process termination.

[0160] The first core dump process includes: generating a signal (e.g., SIGSEGV signal) and sending it to the process that terminated abnormally (for ease of description, the process that terminated abnormally will be referred to as the target process). After receiving the signal, the target process can enter the signal handling process. In this signal handling process, the kernel mode of the operating system can check some configurations related to the core dump of the target process, such as checking the resource limitations of the target process or checking the path of the core file that generated the target process.

[0161] The second core dump process includes: the operating system's kernel mode can generate the core dump file of the target process based on the key information of the target process, according to the path specified in the configuration for generating the core file of the target process.

[0162] However, the known fault diagnosis methods have certain application limitations. On the one hand, for some devices with limited memory, if a process terminates or crashes abnormally, the core file generated for that process may be very large, requiring a lot of storage space and affecting the normal operation of other processes. On the other hand, the generated core file contains a large amount of sensitive information such as registers used by user processes and memory usage, making it easy to intercept and exploit by malicious attackers, posing a risk to information security.

[0163] To address the aforementioned technical problems, this application provides an information dumping method. By compressing the contents of at least one virtual memory region of a process that has terminated abnormally, the size of the generated security dump file used to locate the cause of the abnormal termination of the target process can be reduced, making it suitable for devices with limited memory space and possessing good universality. And / or, by encrypting the contents of at least one virtual memory region of a process that has terminated abnormally, information security can be improved, making it suitable for devices with high information security requirements.

[0164] The following will describe in detail, with reference to the accompanying drawings, an information dumping method provided in the embodiments of this application.

[0165] Figure 2 is a schematic flowchart of an information dumping method provided in an embodiment of this application.

[0166] The method 200 shown in Figure 2 may include steps 210 and 220. The following provides a detailed description of each step in the method 200.

[0167] The steps of method 200 can be executed by an information dumping device, or the steps of method 200 can be executed by a component (such as a chip, chip system, etc.) configured in the information dumping device, or they can be implemented by a logic module or software capable of implementing all or part of the functions of the information dumping device. This application does not limit this.

[0168] As an example and not a limitation, in the vehicle field, an information dumping device can be a vehicle, an in-vehicle device, or an in-vehicle system; in other fields besides the vehicle field, an information dumping device can be other smart terminals or systems mounted on other smart terminals.

[0169] The following describes steps 210 and 220 in detail, using the information transfer device as the execution subject.

[0170] In step 210, the contents of one or more virtual memory regions in the address space of the target process are obtained. The target process is the process that has terminated abnormally on the information dump device.

[0171] It is understood that fault diagnosis technicians can configure one or more processes on the information dumping device so that, in the event of abnormal termination, these processes can trigger the information dumping method provided in this application. Detailed descriptions are provided below and will not be repeated here.

[0172] When a process of one or more processes configured on the information dumping device to be applicable to the information dumping method provided in this application terminates abnormally, the information dumping device can obtain the contents of one or more virtual memory regions in the address space of the target process, so that subsequent fault diagnosis technicians can locate the cause of the abnormal termination of the target process based on the contents of the one or more virtual memory regions.

[0173] In step 220, a security dump file is obtained based on the contents of the one or more virtual memory regions. The security dump file includes the contents of at least one of the one or more virtual memory regions that have been compressed and / or encrypted.

[0174] The following describes several possible implementation methods for step 220.

[0175] In one possible implementation, obtaining a security dump file based on the content of the one or more virtual memory regions includes: compressing the content of the one or more virtual memory regions to obtain target compressed content; and obtaining the security dump file based on the target compressed content, wherein the security dump file includes the target compressed content.

[0176] Example 1: After obtaining the contents of one or more virtual memory regions in the address space of the target process, the information dumping device can compress the contents of at least one of the one or more virtual memory regions and save the compressed contents to a secure dump file.

[0177] Compressing the contents of one or more virtual memory regions in the address space of the target process can reduce storage space usage, improve data transmission and storage efficiency, further reduce the memory space requirements of the device, and has good universality.

[0178] Optionally, compressing the content in the one or more virtual memory regions includes: compressing the content of the second virtual memory region based on a first compression parameter, the first compression parameter indicating whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed; wherein, the second virtual memory region is any one of the one or more virtual memory regions.

[0179] Understandably, each virtual memory region segment of each process can be configured with corresponding compression parameters. The information dumping device can decide whether to compress the contents of the second virtual memory region segment and which compression algorithm to use based on the compression parameters corresponding to each virtual memory region segment of each process.

[0180] By controlling the compression process using compression parameters, it is possible to flexibly adapt to different storage and performance requirements, thereby improving the flexibility and adaptability of the compression process.

[0181] Optionally, the method 200 further includes: obtaining a second compression parameter, which indicates whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed, the second compression parameter being different from the first compression parameter; and updating the first compression parameter to the second compression parameter.

[0182] Understandably, each virtual memory region of each process can be configured with corresponding compression parameters, and these parameters can be updated according to actual needs. By updating the compression parameters for a specific virtual memory region, the compression strategy can be dynamically adjusted to adapt to different environments and changing requirements, offering high flexibility and versatility.

[0183] In one possible second implementation, obtaining a security dump file based on the content in the one or more virtual memory regions includes: encrypting the content in the one or more virtual memory regions to obtain target encrypted content; obtaining the security dump file based on the target encrypted content, wherein the security dump file includes the target encrypted content.

[0184] Example 2: After obtaining the contents of one or more virtual memory regions in the address space of the target process, the information dumping device can encrypt the contents of at least one of the one or more virtual memory regions and save the encrypted contents to a secure dump file.

[0185] Encrypting the contents of one or more virtual memory regions in the address space of the target process can effectively protect sensitive data, prevent information leakage, and improve information security.

[0186] Optionally, encrypting the content in the one or more virtual memory regions includes: encrypting the content of the second virtual memory region based on a first encryption parameter, the first encryption parameter indicating whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted; wherein, the second virtual memory region is any one of the one or more virtual memory regions.

[0187] Understandably, each virtual memory region segment of each process can be configured with corresponding encryption parameters. The information dumping device can decide whether to encrypt the contents of the second virtual memory region segment and which compression algorithm to use to encrypt the contents of the second virtual memory region segment based on the encryption parameters corresponding to each virtual memory region segment of each process.

[0188] By using encryption parameters to control the encryption process, encryption strategies can be flexibly selected to adapt to different security needs.

[0189] Optionally, the method 200 further includes: obtaining a second encryption parameter, which is used to indicate whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted, the second encryption parameter being different from the first encryption parameter; and updating the first encryption parameter to the second encryption parameter.

[0190] Understandably, each virtual memory region of each process can be configured with corresponding encryption parameters, and these parameters can be updated according to actual needs. By updating the encryption parameters for a specific virtual memory region, the encryption strategy can be dynamically adjusted to adapt to different security requirements and environmental changes, offering high flexibility and versatility.

[0191] In one possible implementation, a security dump file is obtained based on the content of the one or more virtual memory regions, including: encrypting and compressing the content of the one or more virtual memory regions to obtain compressed target encrypted content; and obtaining the security dump file based on the compressed target encrypted content, wherein the security dump file includes the compressed target encrypted content.

[0192] Example 3: After obtaining the contents of one or more virtual memory regions in the address space of the target process, the information dumping device can compress and encrypt the contents of at least one of the one or more virtual memory regions, and save the compressed and encrypted contents to a secure dump file.

[0193] Encrypting and compressing the contents of one or more virtual memory regions in the address space of the target process can effectively protect sensitive data, prevent information leakage, and improve information security. On the other hand, it can reduce storage space occupation, improve data transmission and storage efficiency, reduce the memory space requirements of the device, and has good universality.

[0194] Figure 3 is a schematic diagram of a secure dump file provided in an embodiment of this application.

[0195] As shown in Figure 3, the security dump file may include the compressed content of m (m is an integer greater than or equal to 1) virtual memory regions in one or more virtual memory regions in the address space of the target process (i.e., the target compressed content mentioned in Implementation Method 1 below step 220), and may also include overall compressed segment information, such as including but not limited to the number of compressed parts (i.e., the number of virtual memory regions corresponding to the compressed parts, i.e., m), the offset of each compressed part (i.e., the position information of each compressed part), etc.; and / or, the security dump file may include the encrypted content of n (n is an integer greater than or equal to 1) virtual memory regions in one or more virtual memory regions in the address space of the target process (i.e., the target encrypted content mentioned in Implementation Method 2 below step 220), and may also include overall encrypted segment information, such as including but not limited to the number of encrypted parts (i.e., the number of virtual memory regions corresponding to the encrypted parts, i.e. n), the offset of each encrypted part (i.e., the position information of each encrypted part), etc.

[0196] It is understandable that, in Example 1 above, the secure dump file generated by the information dumping device may include the compressed content of the m virtual memory regions and the overall compressed segment information, as shown in Figure 3; in Example 2 above, the secure dump file generated by the information dumping device may include the encrypted content of the n virtual memory regions and the overall encrypted segment information, as shown in Figure 3; in Example 2 above, the secure dump file generated by the information dumping device may include the compressed content of the m virtual memory regions and the overall compressed segment information, as shown in Figure 3, and the encrypted content of the n virtual memory regions and the overall encrypted segment information.

[0197] The following sections, with reference to Figures 4 to 6, provide a detailed explanation of the composition of each encrypted part after encryption, the composition of each compressed part after compression, and the composition of each encrypted and compressed part after encryption and compression.

[0198] Figure 4 is a schematic diagram of the encrypted part of the secure dump file provided in an embodiment of this application.

[0199] As shown in Figure 4, the encrypted part (e.g., encrypted part 1) may include, but is not limited to, the current segment information, encryption parameters, and ciphertext (i.e., the actual encrypted data other than the current segment information and encryption parameters). The current segment information may include, but is not limited to, the length of the encrypted part (i.e., the length of the entire encrypted part 1) and the length of the ciphertext; the encryption parameters may include, but are not limited to, the encryption algorithm used.

[0200] Figure 5 is a schematic diagram of a secure dump file compression section provided in an embodiment of this application.

[0201] As shown in Figure 5, the compressed portion (e.g., compressed portion 1) may include, but is not limited to, the current segment information, compression parameters, and compressed content (i.e., the actual compressed data excluding the current segment information and compression parameters). The current segment information may include, but is not limited to, the length of the compressed portion (i.e., the length of the entire compressed portion 1) and the length of the compressed content; the compression parameters may include, but are not limited to, the compression algorithm used.

[0202] Figure 6 is a schematic diagram of the secure dump file encryption and compression part provided in an embodiment of this application.

[0203] As shown in Figure 6, the part that is both encrypted and compressed (e.g., compressed part x & encrypted part y) may include, but is not limited to, the current segment information, encryption parameters, compression parameters, and the compressed ciphertext. The current segment information may include, but is not limited to, the length of the encrypted and compressed part (i.e., the length of the entire compressed part x & encrypted part y), the ciphertext length, and the length of the compressed ciphertext; the encryption parameters may include, but are not limited to, the encryption algorithm used; and the compression parameters may include, but are not limited to, the compression algorithm used.

[0204] By compressing the contents of at least one virtual memory region of the target process, the size of the generated security dump file used to locate the cause of the abnormal termination of the target process can be reduced, making it suitable for devices with small memory space and having good universality; by encrypting the contents of at least one virtual memory region of the target process, information security can be improved, making it suitable for devices with high information security requirements.

[0205] Optionally, if each virtual memory region in the address space of the target process is configured to be unencrypted and uncompressed, the file generated by the information dumping device for the target process to locate the cause of the abnormal termination of the target process can be a kernel dump file.

[0206] In one possible implementation, obtaining the contents of one or more virtual memory regions in the address space of the target process includes: obtaining attribute information corresponding to a first virtual memory region in the address space of the target process, wherein the first virtual memory region is any virtual memory region in the address space of the target process; and obtaining the contents of the first virtual memory region if the attribute information satisfies the target conditions.

[0207] For example, the information dumping device can obtain the attribute information of any virtual memory region segment in the address space of the target process (for ease of description, any virtual memory region segment in the address space of the target process is referred to as the first virtual memory region segment), and can obtain the content in the first virtual memory region segment if the attribute information of the first virtual memory region segment meets the target conditions.

[0208] By obtaining attribute information of one or more virtual memory regions of the target process, the contents of virtual memory regions that meet the target conditions are dumped into a safe dump file. This reduces the size of the generated safe dump file used to locate the cause of the abnormal termination of the target process, making it suitable for devices with limited memory space and having good universality. In addition, by excluding some content that is not related to the cause of the abnormal termination of the target process, the efficiency of fault diagnosis can be improved.

[0209] In one possible implementation, the attribute information is used to indicate whether write permission and / or corresponding physical memory are available, and the target condition includes: having write permission, and / or, the corresponding physical memory being greater than zero; wherein, the target condition is used to determine whether the content of the first virtual memory region segment includes target content, and the target content is related to the reason for the abnormal termination of the target process.

[0210] Understandably, if a virtual memory segment lacks write permissions, the operating system cannot write information such as the target process's memory state, register state, and call stack to that segment during its execution. Therefore, the virtual memory segment will not contain information about the target process's memory state, register state, and call stack at the time of its abnormal termination; in other words, it lacks content helpful in locating the cause of the process's abnormal termination. Thus, if a virtual memory segment lacks write permissions, its contents can be left unaccessed; conversely, if a virtual memory segment has write permissions, its contents can be accessed.

[0211] It's also understandable that if a virtual memory segment lacks corresponding physical memory, the operating system cannot write information such as the target process's memory state, register state, and call stack to that virtual memory segment during its execution. Therefore, this virtual memory segment will not contain information such as the target process's memory state, register state, and call stack at the time of its abnormal termination; in other words, it lacks content helpful in locating the cause of the process's abnormal termination. Therefore, if a virtual memory segment lacks corresponding physical memory, its contents do not need to be retrieved; if a virtual memory segment has corresponding physical memory, its contents can be retrieved.

[0212] Example A: This attribute information indicates whether write permission is available, and the target condition includes: having write permission. Thus, if write permission is available for the first virtual memory region, the data dumping device can retrieve the contents of the first virtual memory region.

[0213] Example B: This attribute information indicates whether there is corresponding physical memory, and the target condition includes: the corresponding physical memory is greater than zero. Thus, if the physical memory corresponding to the first virtual memory region is greater than zero, the information dumping device can retrieve the contents of the first virtual memory region.

[0214] Example C: This attribute information indicates whether write permission is available and the corresponding physical memory. The target conditions include: having write permission and the corresponding physical memory being greater than zero. Thus, if write permission is available for the first virtual memory region and the physical memory corresponding to the first virtual memory region is greater than zero, the information dumping device can retrieve the contents of the first virtual memory region.

[0215] By using attribute information to indicate write permissions and / or the presence of physical memory, the contents of virtual memory segments containing actual data can be dumped. In other words, content unrelated to the cause of the target process's abnormal termination can be filtered out, effectively filtering out content that may be related to the cause of the target process's abnormal termination, reducing unnecessary data storage and processing, and improving resource utilization efficiency.

[0216] In another possible implementation, the attribute information is used to indicate the size of the content in the first virtual memory region segment, and the target condition includes: the size of the content in the first virtual memory region segment is greater than or equal to a first threshold.

[0217] The first threshold can be preset, and this application does not limit the specific value of the first threshold.

[0218] For example, if the size of the content in the first virtual memory region is greater than or equal to the first threshold, the information dumping device can obtain the content in the first virtual memory region.

[0219] By limiting the size of the contents dumped to the safe dump file, the contents of virtual memory regions containing a large amount of content can be dumped to the safe dump file for further processing; the contents of virtual memory regions containing a small amount of content can be processed using currently known dumping methods (such as kernel dumping methods), without needing to further process the contents of all virtual memory regions of the target process. This not only improves data processing efficiency but also reduces resource waste.

[0220] Optionally, the method 200 further includes: if the attribute information does not meet the target condition, but the first virtual memory region segment is configured to need to be dumped, obtaining the content in the first virtual memory region segment.

[0221] Understandably, for each process, each virtual memory segment corresponding to that process can be individually configured to determine whether the contents of that virtual memory segment need to be dumped. When a virtual memory segment is configured to require dumping, regardless of whether the attribute information of that virtual memory segment meets the target conditions, the information dumping device can obtain the contents of that virtual memory segment and dump them to a secure dump file.

[0222] In other words, even if the attribute information does not meet the target conditions, the contents of the virtual memory region segment configured to be dumped can still be dumped. This can flexibly adapt to actual needs, ensure that critical data is not missed due to conditional limitations, and improve the comprehensiveness of fault diagnosis.

[0223] In one possible implementation, method 200 further includes compressing the secure dump file.

[0224] It is understandable that after obtaining the security dump file through steps 210 and 220, the information dumping device can further compress the security dump file. This further reduces storage space usage, thereby lowering the memory requirements of the device and demonstrating good versatility.

[0225] Optionally, compressing the security dump file includes: compressing the security dump file based on a third compression parameter, the third compression parameter being used to indicate whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed.

[0226] Understandably, each process's security dump file can be configured with corresponding compression parameters. The information dumping device can decide whether to compress the security dump file of a process and which compression algorithm to use based on the compression parameters corresponding to the security dump file of each process.

[0227] By using compression parameters to control the compression process of secure dump files, different storage and performance requirements can be flexibly adapted.

[0228] Optionally, the method 200 further includes: obtaining a fourth compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed, the fourth compression parameter being different from the third compression parameter; and updating the fourth compression parameter to the third compression parameter.

[0229] Understandably, each process's security dump file can be configured with corresponding compression parameters, and these parameters can be updated according to actual needs. By updating the compression parameters for the security dump file, the compression strategy can be dynamically adjusted to adapt to different environments and changing requirements, offering high flexibility and versatility.

[0230] In one possible implementation, method 200 further includes encrypting the secure dump file.

[0231] It is understandable that after obtaining the secure dump file through steps 210 and 220, the information dumping device can further encrypt the secure dump file. This further protects sensitive information within the file, prevents unauthorized access, and enhances information security.

[0232] Optionally, encrypting the security dump file includes: encrypting the security dump file based on a third encryption parameter, the third encryption parameter being used to indicate whether the security dump file needs to be encrypted, and / or, based on which encryption algorithm the security dump file is encrypted.

[0233] Understandably, each process's security dump file can be configured with corresponding encryption parameters. The information dumping device can decide whether to encrypt the security dump file of a process and which encryption algorithm to use based on the encryption parameters corresponding to the security dump file of each process.

[0234] By using encryption parameters to control the encryption process of securely dumped files, encryption strategies can be flexibly selected to adapt to different security needs.

[0235] Optionally, the method 200 further includes: obtaining a fourth encryption parameter, which indicates whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted, the fourth encryption parameter being different from the third encryption parameter; and updating the third encryption parameter to the fourth encryption parameter.

[0236] Understandably, each process's security dump file can be configured with corresponding encryption parameters, and these parameters can be updated according to actual needs. By updating the encryption parameters for the security dump file, the encryption strategy can be dynamically adjusted to adapt to different security requirements and environmental changes, exhibiting high flexibility and versatility.

[0237] In one possible implementation, method 200 further includes compressing and encrypting the secure dump file.

[0238] It is understandable that after obtaining the secure dump file through steps 210 and 220, the information dumping device can further encrypt and compress the secure dump file. This, on the one hand, can further effectively protect sensitive data, prevent information leakage, and improve information security; on the other hand, it can further reduce storage space usage, improve data transmission and storage efficiency, reduce the memory space requirements of the device, and has good versatility.

[0239] In one possible implementation, the method 200 further includes sending a target file associated with the security dump file to a cloud server. Accordingly, the cloud server can receive the target file from the information dump device.

[0240] As an example, the target file is related to the security dump file, which can be understood as the target file being the security dump file.

[0241] In another example, after obtaining a secure dump file and further processing it to obtain a target file, the information dumping device can send the target file to a cloud server.

[0242] Optionally, the information dumping device may further process the secure dump file, including but not limited to one or more of the following: encryption, compression, or format conversion.

[0243] Example D: The target file is the core file obtained after format conversion of the security dump file. In other words, the information dump device can convert the security dump file into a core file.

[0244] Example E: The target file includes security parameters related to the parameters used to encrypt the secure dump file. In other words, the target file is the file obtained after encrypting the secure dump file. These security parameters may be pre-stored or determined through negotiation with a cloud server; this application does not impose any limitations on this.

[0245] Example F: The target file includes compression parameters related to the parameters used to compress the security dump file. In other words, the target file is the file obtained by compressing the security dump file. These compression parameters may be pre-stored or determined through negotiation with a cloud server; this application does not impose any limitations on this.

[0246] Example G: The target file includes security parameters and compression parameters. In other words, the target file is the result of encrypting and compressing the security dump file.

[0247] Example H: The target file is the core file obtained by converting the format of the security dump file, and then encrypting the core file.

[0248] Example I: The target file is the core file obtained by converting the format of the security dump file, and then compressing the core file.

[0249] Example J is a target file obtained by converting the format of the security dump file to obtain the core file, and then encrypting and compressing the core file.

[0250] It is understandable that, in the case that the target file is a compressed file, the cloud server can also decompress the target file based on preset compression parameters or compression parameters determined in consultation with the information storage device.

[0251] It is also understandable that, if there is encrypted content in the target file, the cloud server can decompress the encrypted content in the target file based on preset encryption parameters or encryption parameters determined through negotiation with the information dumping device.

[0252] It is also understood that after the cloud server receives the secure dump file from the information dump device, or after the cloud server receives the encrypted and / or compressed secure dump file from the information dump device and processes it accordingly to obtain the secure dump file, the cloud server can convert the secure dump file into a core dump file and store the core dump file.

[0253] Core dump files are typically in a standardized format, suitable for a variety of analysis tools and platforms. Converting security dump files to this format makes the file format compatible with existing debugging and analysis tools, enabling fault diagnosis technicians to analyze and diagnose faults using familiar tools and processes, thereby accelerating the fault diagnosis process.

[0254] Optionally, the method 200 further includes: deleting the security dump file and / or the target file.

[0255] As an example, after the target file is sent to a cloud server, the information dump device can delete the secure dump file.

[0256] In another example, after the target file is sent to a cloud server, the information dumping device can delete the target file.

[0257] In another example, after the target file is sent to the cloud server, the information dump device can delete both the security dump file and the target file.

[0258] By deleting secure dump files and / or target files after data transfer or processing is complete, storage space can be effectively freed up, storage costs reduced, and the exposure time of sensitive data on local storage devices decreased. This improves data security and privacy protection, helps prevent unauthorized access or data leakage, and is especially beneficial when processing dump files containing sensitive information, ensuring that data is promptly cleaned up after use.

[0259] In one possible implementation, the method 200 further includes: receiving first information from the cloud server, the first information indicating that the cloud server is a trusted device for the information dumping device. Accordingly, the cloud server sends the first information to the information dumping device.

[0260] Sending initial information from a cloud server to the data transfer device, indicating that the cloud server is a trusted device, enhances the data transfer device's trust in the cloud server. This trust mechanism helps the data transfer device verify the trustworthiness of the data recipient when interacting with the cloud server, thereby preventing data leakage or interception by untrusted servers. This measure improves the security of data transmission, ensuring that data is processed only in a trusted environment.

[0261] In one possible implementation, the method 200 further includes: sending second information to the cloud server, the second information indicating that the information dumping device is a trusted device of the cloud server. Accordingly, the cloud server receives the second information from the information dumping device.

[0262] By receiving a second message from the information dumping device, indicating that the information dumping device is a trusted device of the cloud server, a two-way trust relationship can be established between the cloud server and the information dumping device. This two-way authentication mechanism ensures that only authenticated devices can interact with the cloud server, preventing unauthorized devices from accessing or uploading data. This measure improves the overall security of the system, enabling data to be transmitted and processed between trusted devices, reducing potential security risks and the possibility of information leakage.

[0263] Figure 7 is a schematic diagram of an information dumping device establishing a trust relationship with a cloud server.

[0264] As shown in Figure 7, the information dumping device can pre-store the information dumping device's certificate (hereinafter referred to as the information dumping device certificate for ease of description) (not shown in Figure 7), the cloud server's certificate (hereinafter referred to as the cloud certificate for ease of description), the cloud server's public key (hereinafter referred to as the cloud public key for ease of description), and the information dumping device's pre-set private key. Correspondingly, the cloud server can pre-store the cloud certificate (not shown in Figure 7), the information dumping device's certificate and public key (hereinafter referred to as the information dumping device public key for ease of description), and the cloud server's pre-set private key.

[0265] As an example, and not a limitation, the private key of the data dumping device and the private key of the cloud can be stored in their respective secure environments. For example, in the case of a vehicle as the data dumping device, the private key of the data dumping device (i.e., the vehicle-side private key) can be stored in the vehicle's trusted execution environment (TEE) to prevent key leakage. Similarly, the private key of the cloud server can be stored in the cloud hardware security module (HSM).

[0266] The following is a brief description of the process by which the information dumping device establishes a trust relationship (i.e., communication negotiation) with the cloud server.

[0267] The cloud server can encrypt the cloud certificate using its private key and the public key of the information storage device to obtain first information, and then send this first information to the information storage device. Upon receiving the first information from the cloud server, the information storage device can decrypt it using its private key and the cloud public key to obtain the target cloud certificate. Furthermore, the information storage device can compare this target cloud certificate with pre-stored cloud certificates on its device. That is, the information storage device can verify the signature legitimacy of the target cloud certificate level by level using the pre-installed root certificate store of the cloud server to confirm the legitimacy of the cloud server's identity, i.e., whether the cloud server is a trusted device of the information storage device. Thus, a one-way trust relationship (i.e., a one-way communication channel) is established between the information storage device and the cloud server.

[0268] Without loss of generality, the information dumping device can encrypt its certificate using its private key and the cloud's public key to obtain second information, which it then sends to the cloud server. Upon receiving the second information from the information dumping device, the cloud server can decrypt it using the cloud's private key and the information dumping device's public key to obtain the target information dumping device certificate. Furthermore, the cloud server can compare this target information dumping device certificate with pre-stored information dumping device certificates on the cloud server. That is, the cloud server can verify the signature legitimacy of the target information dumping device certificate level by level using a pre-installed root certificate store for information dumping devices, thereby confirming the legitimacy of the information dumping device's identity and whether it is a trusted device of the cloud server. This establishes a one-way trust relationship between the cloud server and the information dumping device (i.e., a one-way communication channel between the cloud server and the information dumping device).

[0269] In this way, a two-way trust relationship (i.e., a two-way communication channel) between the information dumping device and the cloud server is established.

[0270] Understandably, the information dumping device can use its private key and the cloud's public key to perform shared key calculation based on a key negotiation cryptographic algorithm, obtaining a shared symmetric key. Without loss of generality, the cloud server can use its private key and the information dumping device's public key to calculate the shared key using the same key negotiation algorithm, obtaining a shared symmetric key that is identical to the shared key obtained by the information dumping device. In this way, the information dumping device can subsequently use this shared symmetric key to encrypt a file (e.g., a secure dump file or a target file) and send it to the cloud server. Correspondingly, upon receiving the encrypted file (e.g., an encrypted secure dump file or a target file) from the information dumping device, the cloud server can use the same shared symmetric key to decrypt the file, thereby ensuring the confidentiality, security, and integrity of the information in the file.

[0271] Optionally, the information dumping device and the cloud server can periodically update their respective certificates and private keys, thereby enabling the sharing of symmetric keys and controlling the scope of key leakage to ensure the confidentiality and security of historical conversations.

[0272] As described in step 210, a fault diagnosis technician can configure one or more processes on the information dumping device so that, in the event of abnormal termination, these processes can trigger the initiation of the information dumping method provided in this application. The following detailed description, in conjunction with the accompanying drawings, illustrates the configuration of one or more processes on the information dumping device.

[0273] Figure 8 is a schematic diagram of various implementation methods for configuring one or more processes on an information dumping device according to embodiments of this application.

[0274] As shown in Figure 8, the information transfer device may be equipped with a secure transfer system for implementing the information transfer method provided in the embodiments of this application.

[0275] One implementation method is that the secure dump system is configured via a configuration file.

[0276] In scenarios where the information dumping method provided in this application is commercially available, a secure dumping system can be provided to customers, along with a configuration file for configuring or managing the secure dumping system. In other words, the secure dumping system can be configured via a configuration file. This allows customers to configure user processes on the information dumping device based on the configuration file, such as configuring whether dumping is required and which dumping method to use. For example, user process 1 can be configured with the information dumping method provided in this application; user process 2 can be configured with the configuration of currently known core dumping methods; and user process 3 can be configured without either the information dumping method provided in this application or the configuration of currently known core dumping methods.

[0277] The configuration for configuring the information dumping method provided in this application for user process 1 may include, but is not limited to: configuring parameters such as whether dumping is required, whether compression is required or which compression algorithm is used, and whether encryption is required or which encryption algorithm is used for each virtual memory region segment in the address space of the user process; or configuring parameters such as whether encryption is required or which encryption algorithm is used for the security dump file generated by user process 1, and whether compression is required or which compression algorithm is used.

[0278] In this implementation, the relevant configuration parameters can be updated using either method 1 or method 2, as shown in Figure 8. Method 1 and method 2 will be explained below.

[0279] Method 1: Customers can set any process-related parameter through the configuration file provided by the security dump system. The security dump system can register callbacks so that when the customer modifies the parameters in the configuration file, the corresponding callback function is directly called to notify the security dump system of the modified parameters, so that the modified parameters take effect.

[0280] Method 2: When the customer uses the security dump system, the information dump device can enable a security dump module process (which is a system process) in user mode. This security dump module process can monitor the modification of the configuration file. After the configuration file is modified, the security dump module process can call the user interface provided by the security dump system to notify the security dump system of the modified parameters so that the modified parameters of the customer take effect.

[0281] Another implementation is that the secure dump system is configured through a secure dump repository.

[0282] In this context, the security dump library can be a dynamic shared object (DLL). A DLL is a shared library file that is loaded at runtime and can be used to share code and data among multiple programs. DLLs allow programs to dynamically load and link the necessary libraries at runtime, improving resource utilization and program flexibility.

[0283] In scenarios where the information dumping method provided in this application is commercially available, a secure dumping system can be provided to customers, along with a secure dumping library for configuring or managing the system. In other words, the secure dumping system can be configured through this library. This allows customers to configure user processes on the information dumping device based on the library, such as whether dumping is required and which dumping method to use. For a detailed description of configuring any user process, please refer to the above description of configuration via configuration files; for brevity, it will not be repeated here.

[0284] Method 3: As shown in Figure 8, customers can set any process-related parameters through the security dump library provided by the security dump system. Customers can also directly notify the security dump system of the modified parameters by calling the interface in the security dump library so that the modified parameters take effect, thereby updating the configuration parameters.

[0285] Figure 9 is a comparative diagram showing different processes configured with different dump methods.

[0286] As shown in Figure 9, user process 1 is configured with the relevant configuration of the information dumping method provided in this application. In the event of abnormal termination of user process 1, the security dumping system will generate a security dump file for locating the cause of abnormal termination of user process 1 based on the relevant configuration of user process 1.

[0287] User process 2 is configured with the relevant configurations of the currently known core dump method. In the event of abnormal termination of user process 2, the core dump system will generate a core dump file based on the relevant configurations of user process 2, and the information dump device can be used to locate the cause of abnormal termination of user process 2.

[0288] User process 3 is neither configured with the information dumping method provided in this application nor with the currently known core dumping method. Therefore, in the event of abnormal termination of user process 3, user process 3 will exit directly, and the information dumping device will not generate files for fault diagnosis, that is, it will not generate files for locating the cause of abnormal termination of user process 3.

[0289] Figure 10 is a schematic diagram of a system architecture applicable to the information dumping method provided in the embodiments of this application.

[0290] As shown in Figure 10, the system architecture applicable to the information dumping method provided in this application embodiment may include an information dumping device. The operating system of the information dumping device may include user mode and kernel mode, with at least one user process running in user mode. A secure dumping system may be deployed on the information dumping device; for example, the secure dumping system may be deployed in the kernel mode of the operating system of the information dumping device. A secure dumping module may also be deployed on the information dumping device; for example, the secure dumping module may be deployed in the user mode of the operating system of the information dumping device.

[0291] The security dump module can be used to configure the security dump system and user processes in response to customer operations. Based on the user's configuration of the user process and the security dump system, the security dump system can automatically identify the target content of the abnormally terminated user process (i.e., the target process) and perform segmented encryption and / or compression based on the relevant configuration. Specifically, it encrypts the target content in virtual memory regions configured to be encrypted and compresses the target content in virtual memory regions configured to be compressed, thereby generating a file used to locate the cause of the abnormal termination of the user process, such as a security dump file or a kernel file (not shown in Figure 10).

[0292] As mentioned in the following description of Figure 6 above, when each virtual memory region in the target process's address space is configured to be unencrypted and uncompressed, the file generated by the information dumping device for the target process to locate the cause of the abnormal termination of the target process can be a kernel dump file. This application does not limit this.

[0293] It is understandable that if any user process configured with the information dumping method provided in this application terminates abnormally on the information dumping device, the information dumping device may be triggered to first execute the first core dumping process, and then generate a file based on the relevant configuration of the security dumping system to locate the cause of the abnormal termination of the user process. A detailed description can be found in the relevant description in method 200 above, and for brevity, it will not be repeated here. A detailed description of the first core dumping process can be found in the relevant explanation in Figure 1, and for brevity, it will not be repeated here.

[0294] Figure 11 is a schematic diagram of another system architecture applicable to the information dumping method provided in the embodiments of this application.

[0295] As shown in Figure 11, the system architecture applicable to the information dumping method provided in this application embodiment may include an information dumping device and a cloud server (abbreviated as cloud in the figure). The operating system of the information dumping device may include user mode and kernel mode. At least one user process can run in user mode. A secure dumping system and a secure dumping module may be deployed on the information dumping device. A secure dumping module may also be deployed on the cloud server.

[0296] For a description of the secure dumping system and secure dumping module on the information dumping device, please refer to the relevant explanation in Figure 10. For brevity, it will not be repeated here. Furthermore, the secure dumping module on the information dumping device in Figure 11 differs from the secure dumping module on the information dumping device in Figure 10 in that it can also interact with the secure dumping module on the cloud server, including but not limited to one or more of the following: negotiating communication with the secure dumping module on the cloud server, or sending target files to the secure dumping module on the cloud server. For a description of negotiating communication with the secure dumping module on the cloud server and sending target files to the secure dumping module on the cloud server, please refer to the relevant description in Method 200 above. For brevity, it will not be repeated here.

[0297] The security dump module on the cloud server can also be used to process the target dump file, including but not limited to one or more of the following: decrypting the target file, decompressing the target file, decrypting the contents of the target file, decompressing the contents of the target file, and converting the target file into a core dump file. For a description of the cloud server, please refer to the relevant description in Method 200 above; for brevity, it will not be repeated here.

[0298] The information transfer method provided in this application will be further illustrated below with reference to Figure 12, taking a vehicle as an example.

[0299] Figure 12 is another schematic flowchart of the information dumping method provided in the embodiments of this application.

[0300] In step 1201, the vehicle-side security dump module and the cloud-based security dump module communicate and negotiate.

[0301] The vehicle-side secure data dump module and the cloud-based secure storage module negotiate keys using their respective certificates, public keys, and private keys, following a common cryptographic protocol. Once the negotiation is successful, the vehicle and cloud terminals can communicate securely and encrypted through a trusted communication channel.

[0302] For a detailed description of the communication negotiation between the vehicle-side security dump module and the cloud-side security dump module, please refer to the relevant description in Figure 7 of Method 200 above. For the sake of brevity, it will not be repeated here.

[0303] In step 1202, if at least one target process exists, the vehicle's kernel mode executes the first kernel dump process.

[0304] For a detailed description of the target process and the first core dump procedure, please refer to the relevant description in Method 200 above. For the sake of brevity, it will not be repeated here.

[0305] In step 1203, the vehicle-side safety dump system obtains the attribute information of the i-th (1≤i≤N, where N is the number of virtual memory regions included in the address space of the target process, and N is a positive integer) virtual memory region segment in the address space of the target process.

[0306] For a detailed description of the attribute information of the virtual memory region segments in the address space of the target process, please refer to the relevant description in Method 200 above. For the sake of brevity, it will not be repeated here.

[0307] In step 1204, it is determined whether the attribute information of the i-th virtual memory region segment meets the target conditions.

[0308] For a detailed description of the target conditions, please refer to the relevant description in Method 200 above. For the sake of brevity, it will not be repeated here.

[0309] In step 1205, it is determined whether the i-th virtual memory region segment is configured to require encryption.

[0310] In step 1206, the vehicle-side security dump system encrypts the contents of the i-th virtual memory region segment.

[0311] In step 1207, it is determined whether the i-th virtual memory region segment is configured to require compression.

[0312] In step 1208, the vehicle-side safety dump system compresses the contents of the i-th virtual memory region.

[0313] In step 1209, the vehicle-side secure dump system dumps the compressed and / or encrypted target content into a secure dump file.

[0314] In step 1210, is i equal to N?

[0315] In step 1211, i = i + 1.

[0316] In steps 1203 to 1211, the vehicle-side security dump system can traverse each virtual memory region segment of the target process's address space and obtain the attribute information of each virtual memory region segment. For each virtual memory region segment of the target process's address space, the vehicle-side security dump system can determine whether the attribute information of the virtual memory region segment meets the target conditions, whether the virtual memory region segment is configured to be encrypted and / or compressed, encrypt the content in the virtual memory region segment configured to be encrypted, compress the content in the virtual memory region segment configured to be compressed, and dump the encrypted and / or compressed content in the virtual memory region segment to a security dump file.

[0317] It is understood that Figure 12 is merely an example. In practical applications, the order in which the determination of whether a virtual memory region segment is configured to be encrypted or compressed is not restricted, nor is the order in which the content within the virtual memory region segment is compressed or encrypted. That is, one can first determine whether a virtual memory region segment is configured to be encrypted, and then determine whether it is configured to be compressed; or, one can first determine whether a virtual memory region segment is configured to be compressed, and then determine whether it is configured to be encrypted; or, one can simultaneously determine whether a virtual memory region segment is configured to be encrypted and whether it is configured to be compressed. Without loss of generality, one can first encrypt the content within the virtual memory region segment, and then compress it; or, one can first compress the content within the virtual memory region segment, and then encrypt it. This application does not impose any limitations on this.

[0318] In step 1212, is the security dump file configured to require compression?

[0319] In step 1213, the vehicle-side safety dump system compresses the safety dump file.

[0320] In step 1214, the security dump file is configured to require encryption.

[0321] In step 1215, the vehicle-side security dump system encrypts the security dump file.

[0322] In step 1216, the vehicle-side security dump system transmits the target file to the cloud-based security dump module.

[0323] In steps 1212 to 1216, for the security dump file, the vehicle-side security dump system can determine whether the security dump file is configured to be encrypted and / or compressed. If the security dump file is configured to be encrypted, the security dump file is encrypted. If the security dump file is configured to be compressed, the security dump file is compressed. The encrypted and / or compressed security dump file can then be transmitted to the cloud-based security dump module.

[0324] It is understood that Figure 12 is merely an example. In practical applications, the order in which the determination of whether a security dump file is configured to be encrypted or compressed is not restricted, nor is the order in which the security dump file is compressed or encrypted. That is, one can first determine whether the security dump file is configured to be encrypted, and then determine whether it is configured to be compressed; or, one can first determine whether the security dump file is configured to be compressed, and then determine whether it is configured to be encrypted; or, one can simultaneously determine whether the security dump file is configured to be encrypted and compressed. Without loss of generality, one can first encrypt the security dump file, and then compress it; or, one can first compress the security dump file, and then encrypt it. This application does not impose any limitations on this.

[0325] In step 1217, the cloud-based secure dump module decrypts and / or decompresses the target file to obtain a secure dump file.

[0326] It is understandable that if the vehicle-side security dump system encrypts the security dump file, the cloud-based security dump module can decrypt the target file, and / or, if the vehicle-side security dump system compresses the security dump file, the cloud-based security dump module can decompress the target file to obtain the security dump file.

[0327] In step 1218, the cloud-based security dump module converts the security dump file into a core file.

[0328] Understandably, if the security dump file contains encrypted content, the cloud-based security dump module can decrypt the encrypted content, and / or, if the security dump file contains compressed content, it can decompress the compressed content to obtain the target content. Furthermore, the cloud-based security dump module can perform format conversion on the target content to obtain a file conforming to the fault diagnosis protocol standard, such as a core file.

[0329] In step 1219, the cloud-based secure dump module stores the core files.

[0330] It is understood that Figure 12 is merely an example and should not impose any limitations on this application.

[0331] Based on the above technical solution, firstly, by compressing the content of at least one virtual memory region of the target process, the size of the generated security dump file used to locate the cause of the abnormal termination of the target process can be reduced, making it suitable for devices with limited memory space and possessing good universality. Secondly, by encrypting the content of at least one virtual memory region of the target process, information security can be improved, making it suitable for devices with high information security requirements. Thirdly, by obtaining the attribute information of one or more virtual memory regions of the target process, the content of the virtual memory regions that meet the target conditions is dumped into the security dump file, thereby reducing the size of the generated security dump file used to locate the cause of the abnormal termination of the target process, making it suitable for devices with limited memory space and possessing good universality. In addition, by excluding some content that is not related to the cause of the abnormal termination of the target process, the efficiency of fault diagnosis can be improved.

[0332] The information transfer method provided in this application has been described in detail above with reference to the accompanying drawings. The information transfer apparatus provided in the embodiments of this application will be described in detail below.

[0333] It should be understood that the devices shown in Figures 13 and 14 can be used to implement the functions of the information dumping device or cloud server in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the device can be the device in any of the method embodiments shown in Figure 2 or Figure 12, or it can be a component (such as a chip, chip system, processor, etc.) configured in the information dumping device or cloud server, or it can be a logic module or software capable of implementing some or all of the functions of the information dumping device or cloud server.

[0334] Figure 13 is a schematic block diagram of the device provided in an embodiment of this application.

[0335] As shown in Figure 13, the device 1300 includes an acquisition module 1310 and a processing module 1320. The device 1300 can be used to implement the function of the device in any of the method embodiments shown in Figure 2 or Figure 12.

[0336] As an example, when the device 1300 is used to implement the function of the information dumping device in the method embodiment shown in FIG2, the acquisition module 1310 can be used to acquire the contents of one or more virtual memory regions in the address space of the target process, the target process being the process that has abnormally terminated on the information dumping device; the processing module 1320 can be used to obtain a secure dump file based on the contents of the one or more virtual memory regions; wherein, the secure dump file includes the contents of at least one of the one or more virtual memory regions after compression and / or encryption, and the secure dump file is used to locate the cause of the abnormal termination of the target process.

[0337] Optionally, the acquisition module 1310 can be specifically used to: acquire attribute information corresponding to a first virtual memory region segment in the address space of the target process, wherein the first virtual memory region segment is any virtual memory region segment in the address space of the target process; and acquire the content in the first virtual memory region segment when the attribute information meets the target conditions.

[0338] Optionally, the attribute information is used to indicate whether there is write permission and / or corresponding physical memory, and the target condition includes: having write permission, and / or, the corresponding physical memory is greater than zero; wherein, the target condition is used to determine whether the content of the first virtual memory region segment includes target content, and the target content is related to the reason for the abnormal termination of the target process.

[0339] Optionally, the attribute information is used to indicate the size of the content in the first virtual memory region segment, and the target condition includes: the size of the content in the first virtual memory region segment is greater than or equal to a first threshold.

[0340] Optionally, the acquisition module 1310 can also be used to: acquire the contents of the first virtual memory region segment when the attribute information does not meet the target condition, but the first virtual memory region segment is configured to need to be dumped.

[0341] Optionally, the processing module 1320 may be specifically used to: compress the contents in one or more virtual memory regions to obtain target compressed content; and obtain the security dump file based on the target compressed content, wherein the security dump file includes the target compressed content.

[0342] Optionally, the processing module 1320 may be specifically used to: compress the contents of the second virtual memory region segment based on a first compression parameter, the first compression parameter being used to indicate whether the contents of the second virtual memory region segment need to be compressed, and / or, based on which compression algorithm the contents of the second virtual memory region segment are compressed; wherein, the second virtual memory region segment is any one of the one or more virtual memory region segments.

[0343] Optionally, the acquisition module 1310 may also be used to: acquire a second compression parameter, which indicates whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed, the second compression parameter being different from the first compression parameter; the processing module 1320 may also be used to: update the first compression parameter to the second compression parameter.

[0344] Optionally, the processing module 1320 may be specifically used to: encrypt the contents in one or more virtual memory regions to obtain target encrypted content; and obtain the security dump file based on the target encrypted content, wherein the security dump file includes the target encrypted content.

[0345] Optionally, the processing module 1320 may be specifically used to: encrypt the content of the second virtual memory region segment based on a first encryption parameter, the first encryption parameter being used to indicate whether the content of the second virtual memory region segment needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region segment is encrypted; wherein, the second virtual memory region segment is any one of the one or more virtual memory region segments.

[0346] Optionally, the acquisition module 1310 can also be used to: acquire a second encryption parameter, which indicates whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted, the second encryption parameter being different from the first encryption parameter; the processing module 1320 can also be used to: update the first encryption parameter to the second encryption parameter.

[0347] Optionally, the processing module 1320 can also be used to compress the security dump file.

[0348] Optionally, the processing module 1320 may be specifically used to: compress the security dump file based on a third compression parameter, the third compression parameter being used to indicate whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed.

[0349] Optionally, the acquisition module 1310 may also be used to: acquire a fourth compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed, the fourth compression parameter being different from the third compression parameter; the processing module 1320 may also be used to: update the fourth compression parameter to the third compression parameter.

[0350] Optionally, the processing module 1320 can also be used to encrypt the secure dump file.

[0351] Optionally, the processing module 1320 may be specifically used to: encrypt the secure dump file based on a third encryption parameter, the third encryption parameter being used to indicate whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted.

[0352] Optionally, the acquisition module 1310 can also be used to: acquire a fourth encryption parameter, which indicates whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted, the fourth encryption parameter being different from the third encryption parameter; the processing module 1320 can also be used to: update the third encryption parameter to the fourth encryption parameter.

[0353] Optionally, the processing module 1320 can also be used to: send a target file to a cloud server, the target file being associated with the security dump file.

[0354] Optionally, the object file associated with the secure dump file includes: the object file includes security parameters and / or compression parameters, the security parameters being associated with parameters used to encrypt the secure dump file, and the compression parameters being associated with parameters used to compress the secure dump file.

[0355] Optionally, the security parameter is pre-stored, or the security parameter is determined through negotiation with the cloud server; and / or, the compression parameter is pre-stored, or the compression parameter is determined through negotiation with the cloud server.

[0356] In another example, when the device 1300 is used to implement the function of the cloud server in any embodiment of method 200 or the method embodiment shown in FIG12, the acquisition module 1310 can be used to receive a target file from the information dump device; wherein the target file is related to a security dump file, the security dump file is used to locate the cause of the abnormal termination of the target process, the security dump file includes the content of at least one virtual memory region segment in one or more virtual memory region segments in the address space of the target process after compression and / or encryption, the target process is the process that has abnormally terminated on the information dump device.

[0357] Optionally, the object file associated with the secure dump file includes: the object file includes security parameters and / or compression parameters, the security parameters being associated with parameters used to encrypt the secure dump file, and the compression parameters being associated with parameters used to compress the secure dump file.

[0358] Optionally, the security parameter is pre-stored, or the security parameter is determined through negotiation with the cloud server; and / or, the compression parameter is pre-stored, or the compression parameter is determined through negotiation with the cloud server.

[0359] Optionally, the target file is a compressed file, and the processing module 1320 can be used to decompress the target file.

[0360] Optionally, if the target file contains encrypted content, the processing module 1320 can also be used to decrypt the encrypted content in the target file.

[0361] More detailed descriptions of the above modules can be obtained directly from the relevant descriptions in the method embodiments shown in Figure 2 or Figure 12, and will not be repeated here.

[0362] It should be understood that the module division in the embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0363] Figure 14 is another schematic block diagram of the device provided in the embodiments of this application.

[0364] The device 1400 can be a chip system, or it can be a device configured with a chip system to implement the methods described in the above-described method embodiments. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0365] As shown in FIG14, the device 1400 may include a processor 1410, which can be used to execute computer programs or instructions in memory to implement the steps performed by the information dumping device or cloud server in any of the method embodiments shown in FIG2 or FIG12.

[0366] Optionally, the device 1400 further includes a communication interface 1420. The communication interface 1420 can be used to communicate with other devices via a transmission medium, thereby enabling the device 1400 to communicate with other devices. The communication interface 1420 can be, for example, a transceiver, interface, bus, circuit, or a device capable of transmitting and receiving functions. The processor 1410 can use the communication interface 1420 to input and output data, and to implement the method described in any embodiment corresponding to FIG. 2 or FIG. 12. Specifically, the device 1400 can be used to implement the functions of an information dumping device or a cloud server in the above method embodiments.

[0367] Optionally, the device 1400 further includes at least one memory 1430 for storing program instructions and / or data. The memory 1430 is coupled to the processor 1410. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1410 may operate in conjunction with the memory 1430. The processor 1410 may execute program instructions stored in the memory 1430.

[0368] In this application, the memory 1430 may be integrated into the processor 1410, or the processor 1410 and the memory 1430 may be set up separately; this application does not limit this.

[0369] It should be understood that the coupling in the embodiments of this application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information interaction between devices, units, or modules. The processor 1410 may operate in conjunction with the memory 1430. The embodiments of this application do not limit the specific connection medium between the processor 1410, communication interface 1420, and memory 1430. In Figure 14, the processor 1410, communication interface 1420, and memory 1430 are connected via a bus 1440. The bus 1440 is represented by a thick line in Figure 14. The connection methods between other components are only illustrative and not intended to be limiting. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 14, but this does not indicate that there is only one bus or one type of bus.

[0370] This application also provides a computer program product, which includes a computer program (also known as code or instructions) that, when run, can implement the steps performed by the information dumping device or cloud server in any of the embodiments shown in FIG2 or FIG12.

[0371] This application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is run, it can implement the steps performed by the information dumping device or cloud server in any of the embodiments shown in FIG2 or FIG12.

[0372] This application provides a chip system including at least one processor for supporting the implementation of the steps performed by the information dumping device or cloud server in any of the embodiments shown in FIG2 or FIG12.

[0373] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0374] The chip system can consist of chips or include chips and other discrete components.

[0375] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0376] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0377] The terms "unit," "module," etc., used in this specification can be used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. In the embodiments of this application, "unit" and "module" have the same meaning and can be used interchangeably.

[0378] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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. In the several embodiments provided in this application, it should be understood that the disclosed apparatus, devices, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of 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 system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0379] The units described as separate components may or may not be physically separate. The 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0380] In addition, 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.

[0381] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0382] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the technology, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in 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.

[0383] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information dumping method, characterized in that, Applied to an information dumping device, the method includes: Obtain the contents of one or more virtual memory regions in the address space of the target process, wherein the target process is a process that has terminated abnormally on the information dumping device; Based on the contents of the one or more virtual memory regions, a secure dump file is obtained; The security dump file includes compressed and / or encrypted content from at least one of the one or more virtual memory regions. The security dump file is used to locate the cause of the abnormal termination of the target process.

2. The method according to claim 1, characterized in that, The step of obtaining the contents of one or more virtual memory regions in the address space of the target process includes: Obtain the attribute information corresponding to the first virtual memory region segment in the address space of the target process, wherein the first virtual memory region segment is any virtual memory region segment in the address space of the target process; If the attribute information meets the target conditions, the content in the first virtual memory region segment is obtained.

3. The method according to claim 2, characterized in that, The attribute information is used to indicate whether there is write permission and / or the corresponding physical memory, and the target conditions include: having write permission, and / or, the corresponding physical memory is greater than zero; The target condition is used to determine whether the content of the first virtual memory region segment includes target content, and the target content is used to locate the reason for the abnormal termination of the target process.

4. The method according to claim 2, characterized in that, The attribute information is used to indicate the size of the content in the first virtual memory region segment, and the target condition includes: the size of the content in the first virtual memory region segment is greater than or equal to a first threshold.

5. The method according to any one of claims 2 to 4, characterized in that, The method further includes: If the attribute information does not meet the target conditions, but the first virtual memory region is configured to need to be dumped, the contents of the first virtual memory region are obtained.

6. The method according to any one of claims 1 to 5, characterized in that, The process of obtaining a secure dump file based on the contents of the one or more virtual memory regions includes: The contents of the one or more virtual memory regions are compressed to obtain the target compressed content; The secure dump file is obtained based on the target compressed content, and the secure dump file includes the target compressed content.

7. The method according to claim 6, characterized in that, The compression of the contents in the one or more virtual memory regions includes: The content of the second virtual memory region is compressed based on the first compression parameter, which is used to indicate whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed. The second virtual memory region segment is any one of the one or more virtual memory region segments.

8. The method according to claim 7, characterized in that, The method further includes: Obtain a second compression parameter, which indicates whether the content of the second virtual memory region needs to be compressed, and / or, based on which compression algorithm the content of the second virtual memory region is compressed, and the second compression parameter is different from the first compression parameter; Update the first compression parameter to the second compression parameter.

9. The method according to any one of claims 1 to 8, characterized in that, The process of obtaining a secure dump file based on the contents of the one or more virtual memory regions includes: Encrypt the contents of one or more virtual memory regions to obtain the target encrypted content; The secure dump file is obtained based on the target encrypted content, and the secure dump file includes the target encrypted content.

10. The method according to claim 9, characterized in that, The encryption of the contents in the one or more virtual memory regions includes: The content of the second virtual memory region is encrypted based on the first encryption parameter, wherein the first encryption parameter is used to indicate whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted; The second virtual memory region segment is any one of the one or more virtual memory region segments.

11. The method according to claim 10, characterized in that, The method further includes: Obtain a second encryption parameter, which indicates whether the content of the second virtual memory region needs to be encrypted, and / or, based on which encryption algorithm the content of the second virtual memory region is encrypted, and the second encryption parameter is different from the first encryption parameter; Update the first encryption parameter to the second encryption parameter.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: The security dump file is compressed.

13. The method according to claim 12, characterized in that, The compression of the security dump file includes: The security dump file is compressed based on a third compression parameter, which indicates whether the security dump file needs to be compressed and / or, based on which compression algorithm the security dump file is compressed.

14. The method according to claim 13, characterized in that, The method further includes: Obtain a fourth compression parameter, which indicates whether the security dump file needs to be compressed, and / or, based on which compression algorithm the security dump file is compressed, the fourth compression parameter being different from the third compression parameter; Update the fourth compression parameter to the third compression parameter.

15. The method according to any one of claims 1 to 14, characterized in that, The method further includes: The secure dump file is encrypted.

16. The method according to claim 15, characterized in that, The encryption of the secure dump file includes: The secure dump file is encrypted based on a third encryption parameter, which indicates whether the secure dump file needs to be encrypted and / or, based on which encryption algorithm the secure dump file is encrypted.

17. The method according to claim 16, characterized in that, The method further includes: Obtain a fourth encryption parameter, which indicates whether the secure dump file needs to be encrypted, and / or, based on which encryption algorithm the secure dump file is encrypted, and the fourth encryption parameter is different from the third encryption parameter; Update the third encryption parameter to the fourth encryption parameter.

18. The method according to any one of claims 1 to 17, characterized in that, The method further includes: Send the target file, which is related to the security dump file, to the cloud server.

19. The method according to claim 18, characterized in that, The target file and the security dump file are related to the following: The target file includes security parameters and / or compression parameters, the security parameters being related to parameters used to encrypt the secure dump file, and the compression parameters being related to parameters used to compress the secure dump file.

20. The method according to claim 19, characterized in that, The security parameters are either pre-stored, or determined through negotiation with the cloud server; and / or, The compression parameters are either pre-stored or determined through negotiation with the cloud server.

21. An information transfer method, characterized in that, Applied to a cloud server, the method includes: Receive target files from the information dumping device; The target file is related to the security dump file, which is used to locate the cause of the abnormal termination of the target process. The security dump file includes the content of at least one virtual memory region segment in the address space of the target process after compression and / or encryption. The target process is the process that has abnormally terminated on the information dumping device.

22. The method according to claim 21, characterized in that, The target file and the security dump file are related to the following: The target file includes security parameters and / or compression parameters, the security parameters being related to parameters used to encrypt the secure dump file, and the compression parameters being related to parameters used to compress the secure dump file.

23. The method according to claim 22, characterized in that, The security parameters are either pre-stored, or determined through negotiation with the cloud server; and / or, The compression parameters are either pre-stored or determined through negotiation with the cloud server.

24. The method according to claim 22 or 23, characterized in that, The target file is a compressed file, and the method further includes: The target file is decompressed.

25. The method according to any one of claims 22 to 24, characterized in that, The target file contains encrypted content, and the method further includes: Decrypt the encrypted content in the target file.

26. An information transfer device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1 to 20.

27. An information transfer device, characterized in that, Including processor and memory, among which, The memory is used to store programs; The processor is used to invoke the program so that the device performs the method as described in any one of claims 1 to 20.

28. A cloud server, characterized in that, The cloud server includes a module for performing the method as described in any one of claims 21 to 25.

29. A cloud server, characterized in that, Including processor and memory, among which, The memory is used to store programs; The processor is used to invoke the program so that the cloud server performs the method as described in any one of claims 21 to 25.

30. A vehicle, characterized in that, The vehicle includes the information transfer device as described in claim 26 or 27.

31. A computer-readable storage medium having a program stored thereon, characterized in that, When the program is executed, it causes the method as described in any one of claims 1 to 20 to be executed, or causes the method as described in any one of claims 21 to 25 to be executed.

32. A computer program product, characterized in that, Includes a computer program that, when run, causes the method as claimed in any one of claims 1 to 20 to be performed, or causes the method as claimed in any one of claims 21 to 25 to be performed.

Images