Call recording data processing method and device, electronic equipment and storage medium

Abstract

The application provides a call recording data processing method and device, electronic equipment and storage medium; the method comprises the following steps: a first terminal device sends a storage evidence request to a second terminal device participating in a call; in the case of receiving a first confirmation instruction, in response to a confirmation operation for call recording, a recording request is sent to the second terminal device; in the case of receiving a second confirmation instruction, the call is recorded, and the second terminal device synchronously records; in the case of ending the call, a first call recording data recorded by the first terminal device is subjected to hash calculation, a first hash value is obtained, the second terminal device synchronously records second call recording data, and a second hash value is obtained; the first hash value and the second hash value are compared; in the case of the first hash value being the same as the second hash value, a storage evidence certificate of the first call recording data is stored. Through the application, the security of call recording data can be improved.

Description

Technical Field

[0001] This application relates to audio technology, and more particularly to a method, apparatus, electronic device, and storage medium for processing call recording data. Background Technology

[0002] With the development of instant messaging technology, the application of electronic evidence storage for multimedia data is becoming increasingly widespread. Existing evidence storage solutions typically employ a centralized server architecture or a local terminal device-independent architecture. In a centralized architecture, all parties involved in communication must centrally upload the original audio stream, and the server is responsible for data aggregation, feature extraction, and storage. This centralized data transfer mechanism increases the number of exposed points for plaintext data, compromising data confidentiality. In a local terminal device-independent architecture, data collection and processing rely solely on the initiating party's single-side terminal device, and the generated evidence file is only stored on the local terminal. This mechanism lacks a cross-validation step involving multi-terminal data, and a single-side terminal possesses the physical capability to modify the underlying local data.

[0003] In summary, the aforementioned evidence preservation mechanisms have certain limitations in data processing and transfer. Centralized data upload to the server reduces the level of physical isolation and affects data confidentiality; while unilateral storage mechanisms lack multi-party consensus, have weak anti-tampering capabilities, and make it difficult to guarantee data integrity. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing call recording data, which can improve the security of call recording data.

[0005] The technical solution of this application embodiment is implemented as follows: This application provides a method for processing call recording data, wherein a call is established between a first terminal device and a second terminal device, and the method is executed by the first terminal device; the method includes: Send a certificate storage request to the second terminal device participating in the call; Upon receiving a first confirmation instruction for the evidence storage request, in response to a confirmation operation for the call recording, a recording request is sent to the second terminal device; Upon receiving a second confirmation instruction for the recording request, the call is recorded, wherein the second terminal device records the call synchronously. When the call ends, the first call recording data recorded by the first terminal device is hashed to obtain a first hash value, wherein the second terminal device synchronously performs hash calculation on the recorded second call recording data to obtain a second hash value; The first hash value and the second hash value are sent to the server so that the server compares the first hash value and the second hash value. If the first hash value and the second hash value are the same, a certificate of evidence for the first call recording data is received and stored, wherein the certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0006] This application provides a device for processing call recording data, including: The request sending module is used to send a certificate storage request to the second terminal device participating in the call, wherein a call is established between the first terminal device and the second terminal device; The request sending module is configured to send a recording request to the second terminal device in response to a confirmation operation for the call recording, upon receiving a first confirmation instruction for the evidence storage request. A recording module is used to record a call upon receiving a second confirmation instruction for the recording request, wherein the second terminal device records the call synchronously. An encryption module is used to perform a hash calculation on the first call recording data recorded by the first terminal device to obtain a first hash value when the call ends, wherein the second terminal device synchronously performs a hash calculation on the recorded second call recording data to obtain a second hash value; An encryption module is used to send the first hash value and the second hash value to the server so that the server can compare the first hash value and the second hash value; The evidence storage module is used to receive and store evidence of the first call recording data when the first hash value and the second hash value are the same, wherein the evidence storage certificate is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0007] This application provides a method for processing call recording data, wherein a call is established between a first terminal device and a second terminal device; the method includes: Receive the evidence storage request sent by the first terminal device and forward the evidence storage request to the second terminal device; Receive a first confirmation instruction sent by the second terminal device for the evidence storage request, and send the first confirmation instruction to the first terminal device; Receive a recording request sent by the first terminal device and forward the recording request to the second terminal device; The system receives a second confirmation instruction from the second terminal device regarding the recording request, and sends the second confirmation instruction to the first terminal device so that the first terminal device records the call. The second terminal device records the call simultaneously, the first terminal device records first call recording data, and the second terminal device records second call recording data. Receive the first hash value corresponding to the first call recording data and the second hash value corresponding to the second call recording data, and compare the first hash value with the second hash value; If the first hash value and the second hash value are the same, a certificate of evidence is generated and sent to the first terminal device and the second terminal device. The certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0008] This application provides a device for processing call recording data, wherein a call is established between a first terminal device and a second terminal device; the device includes: The forwarding module is used to receive the evidence storage request sent by the first terminal device and forward the evidence storage request to the second terminal device; The forwarding module is used to receive a first confirmation instruction sent by the second terminal device for the evidence storage request, and to send the first confirmation instruction to the first terminal device. The forwarding module is used to receive a recording request sent by the first terminal device and forward the recording request to the second terminal device; The forwarding module is used to receive a second confirmation instruction for the recording request sent by the second terminal device, and send the second confirmation instruction to the first terminal device so that the first terminal device records the call, wherein the second terminal device records the call synchronously, the first terminal device records the first call recording data, and the second terminal device records the second call recording data; The comparison module is used to receive a first hash value corresponding to the first call recording data and a second hash value corresponding to the second call recording data, and compare the first hash value with the second hash value; The credential generation module is used to generate a certificate of evidence and send the certificate of evidence to the first terminal device and the second terminal device when the first hash value and the second hash value are the same. The certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0009] This application provides an electronic device, the electronic device comprising: Memory is used to store executable instructions or computer programs. The processor, when executing computer-executable instructions or computer programs stored in the memory, implements the call recording data processing method provided in the embodiments of this application.

[0010] This application provides a computer-readable storage medium storing computer-executable instructions or computer programs, which, when executed by a processor, implement the call recording data processing method provided in this application.

[0011] This application provides a computer program product, including a computer program or computer executable instructions. When the computer program or computer executable instructions are executed by a processor, they implement the call recording data processing method provided in this application.

[0012] The embodiments of this application have the following beneficial effects: The system sends a storage request and a recording request to the second terminal device from the first terminal device, and after receiving the first confirmation instruction and the second confirmation instruction respectively, triggers simultaneous local recording on both ends. This ensures that both parties are fully informed during the recording process, guaranteeing their right to know and ensuring that recording is conducted with their authorization. The first and second terminal devices simultaneously record call data and store it independently. They perform hash calculations on the call data separately, and only send the calculated first and second hash values ​​to the server for comparison. This ensures that the original call recording data is stored only on the local terminal, preventing sensitive communication data from circulating over the network and improving data confidentiality. Transmitting lightweight hash values ​​to the server instead of large amounts of call recording data significantly reduces network bandwidth consumption during the storage process and saves server storage space. The server, independent of the terminal, performs a consistency comparison of the generated first and second hash values. If the hash values ​​are found to be identical, a storage certificate is generated, allowing the terminal device to receive and store the certificate. The hash value comparison confirms that the call recording data collected by both terminals is consistent and has not been unilaterally modified. This mechanism, which verifies data through third-party hash consensus, significantly enhances the objectivity, authenticity, and credibility of the final generated electronic evidence. Attached Figure Description

[0013] Figure 1 This is a schematic diagram illustrating the application mode of the call recording data processing method provided in the embodiments of this application; Figure 2A This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application; Figure 2B This is a schematic diagram of the server structure provided in an embodiment of this application; Figure 3A This is a first flowchart illustrating the method for processing call recording data provided in an embodiment of this application; Figure 3B This is a second flowchart illustrating the method for processing call recording data provided in the embodiments of this application; Figure 4 This is a schematic diagram of the third process of the call recording data processing method provided in the embodiments of this application.

[0014] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0017] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0018] It should be noted that all call recording data involved in this application was obtained with the user's knowledge and consent, and subsequent processing of the call recording data was carried out within the scope authorized by the user after acquisition. The acquisition and processing of call recording data strictly comply with legal requirements and personal information processing rules.

[0019] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0022] 1) Electronic Evidence Preservation: A data processing mechanism in computer or network communication systems for collecting, solidifying, and storing electronic data generated in specific business scenarios. It typically uses specific acquisition interfaces to obtain target data (such as audio streams, text, system logs, etc.) and combines timestamps, identity identifiers, and cryptographic algorithms (such as digital signatures and hash operations) to convert electronic data into structured records with fixed states (i.e., evidence preservation certificates).

[0023] 2) Advanced Encryption Standard (AES): A symmetric block cipher algorithm used in computer data security. The AES algorithm divides raw plaintext data of arbitrary length into fixed-length (typically 128 bits) blocks and performs a fixed number of rounds (e.g., 10, 12, or 14 rounds) of matrix transformation logic on each block, depending on the length of the selected key (typically 128, 192, or 256 bits). This transformation includes byte substitution, row shifting, column obfuscation, and round key addition. The same digital key is used for both encryption and decryption.

[0024] 3) Secure Hash Algorithm (SHA): A family of cryptographic hash algorithms used to perform data compression and mapping operations. Secure hash functions include specific branches such as SHA-1, SHA-256, and SHA-512. In secure hash function technology, the original file content cannot be deduced from the hash value.

[0025] With the development of mobile internet and instant messaging technologies, electronic evidence storage of multimedia communication data is widely used in business processes such as fact-fixing. Current electronic data storage technologies mainly employ either a centralized processing architecture with a central node or an independent execution architecture with local terminal devices. In a centralized processing architecture, the original audio multimedia data streams from communication participants typically need to be aggregated, feature-extracted, and stored via a unified server. In a local terminal-independent execution architecture, the generation and processing of multimedia data primarily rely on the physical device of a single initiating end, and the recorded call data is stored only at the initiating end. In real-world complex communication applications, the aforementioned data flow and processing mechanisms suffer from low visibility of the stored data, and the cross-consensus verification mechanism for multi-terminal data has limitations, resulting in low confidentiality during the original data flow process and making it difficult to prevent tampering.

[0026] This application provides a method for processing call recording data, a device for processing call recording data, an electronic device, a computer-readable storage medium, and a computer program product, which can improve the security of call recording data.

[0027] The following describes exemplary applications of the electronic devices provided in the embodiments of this application. These electronic devices can be implemented as terminal devices, such as laptops, tablets, desktop computers, set-top boxes, smart TVs, in-vehicle terminals, virtual reality (VR) devices, augmented reality (AR) devices, and other various types of terminals, or as servers. The following will describe exemplary applications of the electronic devices when implemented as terminal devices.

[0028] See Figure 1 , Figure 1 This is a schematic diagram of the application mode of the call recording data processing method provided in the embodiments of this application; the terminal device (exemplarily shown as the first terminal device 400-1 and the second terminal device 400-2) is connected to the server 200 through the network 300, and the database 500 stores the evidence storage certificate. The network 300 can be a wide area network or a local area network, or a combination of the two.

[0029] The first terminal device 400-1 is used by the first user, and the second terminal device 400-2 is used by the second user. The first terminal device 400-1 sends a request to the server 200 via network 300. The server 200 forwards the request to the second terminal device 400-2. If both requests are confirmed, the first terminal device 400-1 and the second terminal device 400-2 simultaneously record the call, obtaining call recording data. At the end of the call, the first terminal device 400-1 and the second terminal device 400-2 perform hash calculations on their respective recorded call data to obtain hash values, and send the hash values ​​to the server 200. The server 200 compares the hash values ​​sent by the two terminal devices and, if the hash values ​​are the same, returns the corresponding evidence to the terminal devices.

[0030] See Figure 2A , Figure 2A This is a schematic diagram of the structure of the terminal device provided in the embodiments of this application. The terminal device 400 can be... Figure 1 Terminal device 400-1 or terminal device 400-2, Figure 2A The terminal device 400 shown includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the terminal device 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2A The general labeled all buses as Bus System 440.

[0031] Processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0032] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0033] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0034] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0035] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0036] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks; The network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc. Presentation module 453 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 associated with user interface 430 (e.g., a display screen, a speaker, etc.). The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0037] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2A A processing device 455 for call recording data stored in memory 450 is shown. This device can be software in the form of programs and plug-ins, including the following software modules: a request sending module 4551, a recording module 4552, an encryption module 4553, and a certificate storage module 4554. These modules are logically linked and can therefore be arbitrarily combined or further separated according to their implemented functions. Figure 2AFor ease of explanation, all the above modules are shown at once, and the functions of each module will be explained below.

[0038] See Figure 2B , Figure 2B This is a schematic diagram of the structure of the server provided in the embodiments of this application. The server can be... Figure 1 Server 200, Figure 2B The server 200 shown includes at least one processor 210, memory 250, and at least one network interface 220. The various components of server 200 are coupled together via a bus system 240. It is understood that the bus system 240 is used to implement communication between these components. In addition to a data bus, the bus system 240 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2B The general labeled all buses as Bus System 240.

[0039] Processor 210 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0040] The memory 250 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 250 may optionally include one or more storage devices physically located away from the processor 210.

[0041] The memory 250 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 250 described in this application embodiment is intended to include any suitable type of memory.

[0042] In some embodiments, memory 250 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0043] Operating system 251 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks; The network communication module 252 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc. In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2B A processing device 255 for call recording data stored in memory 250 is shown. This device can be software in the form of programs and plug-ins, including the following software modules: a forwarding module 2551, a comparison module 2552, and a credential generation module 2553. These modules are logically linked and can therefore be arbitrarily combined or further separated according to their implemented functions. Figure 2B For ease of explanation, all the above modules are shown at once, and the functions of each module will be explained below.

[0044] The method for processing call recording data provided in this application will be described in conjunction with exemplary applications and implementations of the terminal devices or servers provided in the embodiments of this application.

[0045] The following describes the method for processing call recording data provided in the embodiments of this application. As mentioned above, the electronic device implementing the method for processing call recording data in the embodiments of this application can be a terminal device or a server, or a combination of both. Therefore, the executing entity of each step will not be described again below.

[0046] See Figure 3A , Figure 3A This is a flowchart illustrating the method for processing call recording data provided in this application embodiment, which will be combined with... Figure 3A The steps shown are explained. Figure 3A The entity responsible for executing the steps is Figure 1 Terminal device 400-1 or terminal device 400-2.

[0047] In step 301, a certificate storage request is sent to the second terminal device participating in the call.

[0048] For example, a call is established between a first terminal device and a second terminal device, the method of which is executed by the first terminal device. Both the first and second terminal devices have a first application installed for the call and a second application installed for recording. For example, the first application is an instant messaging application, and the second application is a recording application. The call can be conducted via voice message, voice call, or video call. The first terminal device is used by a first user, and the second terminal device is used by a second user. A data preservation request is a specific network interaction command or data message designed to trigger the data solidification and preservation process. The second application on the second terminal device displays a confirmation control for the data preservation request as a floating window in the call interface of the first application. The data preservation request is forwarded to the second terminal device through the server.

[0049] In step 302, upon receiving a first confirmation instruction for the evidence storage request, a recording request is sent to the second terminal device in response to the confirmation operation for the call recording.

[0050] For example, the confirmation instruction for the evidence storage request indicates that the second user has authorized the evidence storage of this call. Upon receiving the confirmation instruction for the evidence storage request, the first user then confirms whether to start recording through a secondary confirmation operation, and the first terminal device sends a recording request. The recording request is a specific electronic control signaling used to trigger multi-terminal synchronous multimedia acquisition logic during the call. The recording request is forwarded to the second terminal device through the server.

[0051] In step 303, upon receiving a second confirmation instruction for the recording request, the call is recorded.

[0052] Here, the second terminal device records audio synchronously.

[0053] For example, a second application on both the first and second terminal devices simultaneously starts recording. The entire recording process takes place locally on the terminal device, without transmitting any raw audio data to the server. The original file is stored only on the user's own terminal device, and the server never accesses any raw data, fundamentally eliminating the risk of privacy leaks. Recording is achieved through the following methods: the second application calls the underlying background audio playback interface to loop through silent audio files; the background audio playback status is continuously monitored in real time, and a replay command is triggered when the single playback of a silent audio file is detected to have ended; playing silent audio files ensures that the second application runs stably in the background of the terminal device for a preset time and will not be automatically closed by the terminal device. The underlying audio acquisition interface is called to obtain the global audio output data stream of the terminal operating system, thus obtaining the call recording data. During the recording process, the Network Time Protocol (NTP) is used to accurately synchronize the time of the first and second terminal devices.

[0054] In step 304, when the call ends, the first call recording data recorded by the first terminal device is hashed to obtain a first hash value.

[0055] Here, the second terminal device synchronously performs hash calculation on the recorded second call recording data to obtain the second hash value.

[0056] For example, a 256-bit hash calculation using the Secure Hash Algorithm (SHA) is performed on the recorded original audio file to generate a unique hash fingerprint (hash value) of the original audio file.

[0057] In some embodiments, after step 304, the first call recording data is encrypted to obtain a first encrypted file, wherein the second terminal device synchronously encrypts the second call recording data to obtain a second encrypted file, and the first and second encrypted files are prohibited from being modified.

[0058] For example, the encryption algorithm could be AES-256, which uses fixed-length 128-bit data blocks and a 256-bit key. During encryption, the algorithm performs multiple rounds of iterative transformations on the original call recording data. Each round of transformations (except the last) consists of four specific mathematical and logical state matrix transformation steps: byte substitution, row shifting, column mixing, and round key addition. The encryption key is randomly generated and stored locally on the terminal device.

[0059] In step 305, the first hash value and the second hash value are sent to the server so that the server can compare the first hash value and the second hash value.

[0060] For example, the first and second terminal devices respectively combine the first and second hash values, along with the globally unique session ID of the current call, the identity identifier of each terminal device, and the timestamp. The first terminal device generates a first data packet, and the second terminal device generates a second data packet. A secure encrypted transmission protocol (such as HTTPS or TLS 1.3) is invoked to send the first and second data packets to the server via the network. Upon receiving the network request from the terminal device, the server parses the data packets. Using the globally unique session ID as the primary key, the server performs addressing and matching, extracting the first and second hash values ​​belonging to the same real-time call session into the same comparison queue in memory. A logical comparator is invoked to perform bit-by-bit or string-level matching operations on the first and second hash values.

[0061] If the first hash value and the second hash value are determined to be identical, the server determines that the original multimedia data recorded locally by both ends of the communication is physically symmetrical and has not been unilaterally tampered with. In this case, the server triggers a certificate release instruction, packaging the same hash value (i.e., the core certificate feature code) and related business metadata to generate a certificate of evidence. If the first hash value and the second hash value are determined to be different, the server determines that at least one party's original recording data has been lost, damaged, or tampered with. In this case, the server automatically triggers an anomaly blocking mechanism, refusing to generate a valid certificate of evidence for the call, and sends feedback information containing an anomaly error code to both the first and second terminal devices.

[0062] In step 306, if the first hash value and the second hash value are the same, the certificate of authenticity for the first call recording data is received and stored.

[0063] Here, the evidence certificate is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0064] In some embodiments, the document containing the evidence is a file that cannot be modified, and the format of the file that cannot be modified may be PDF. The evidence is stored on the blockchain. The evidence includes: evidence number, evidence generation time, recording time period of the call recording data, identity information of the parties involved in the call, device information of the first terminal device, device information of the second terminal device, first electronic signature of the first user using the first terminal device, second electronic signature of the second user using the second terminal device, and blockchain evidence identifier.

[0065] For example, the server calls a pre-defined third-party Certificate Authority (CA) interface to verify the identity authorization status of the first user using the first terminal device and the second user using the second terminal device, and obtains the first electronic signature corresponding to the first user and the second electronic signature corresponding to the second user (e.g., digital signature data generated based on an asymmetric encryption algorithm). The electronic signatures are then bound to the data packets sent by the terminal devices. The data packets, the obtained electronic signatures, and the verified hash value of the audio recording file are packaged and sent to a pre-defined blockchain network node for broadcast and consensus calculation via a smart contract call interface. Once the notarized transaction is successfully packaged into a block on the blockchain, the server receives a blockchain notarization identifier returned by the blockchain network. This identifier includes the block height, timestamp, and a globally unique transaction hash value. The server then calls a document rendering engine to write all data fields and the blockchain notarization identifier into a pre-defined structured notarization document template; executes a format conversion instruction to render and encapsulate the template into a digitally tamper-proof locked, unmodifiable file (such as PDF format), and marks the current system time as the notarization certificate generation time.

[0066] In some embodiments, after step 306, the first call recording data is processed by speech-to-text conversion to obtain the recording text; keywords are extracted from the recording text to obtain topic keywords; and solutions corresponding to the call topics are retrieved based on the topic keywords.

[0067] In some embodiments, keyword extraction is performed on the recorded text to obtain topic keywords, which is achieved as follows: the recorded text is segmented to obtain multiple first segments; the multiple first segments are filtered according to part-of-speech tagging to obtain multiple second segments, wherein the filtering includes deleting modal particles, deleting conjunctions, and deleting noisy text; the multiple second segments are mapped to semantic feature vectors, and the word frequency of each second segment in the recorded text is calculated based on the semantic feature vectors; the inverse document frequency of each second segment is calculated based on a preset global corpus; the inverse document frequency is multiplied by the word frequency to obtain the weight value of the second segment; and the preset number of second segments with the largest weight values ​​are selected as topic keywords.

[0068] For example, Term Frequency (TF) is used to characterize how frequently a valid word appears in a text. TF is calculated as the ratio of the absolute number of times a word appears in the current text to the total number of words in the current text after word segmentation. A higher TF value indicates that the word is mentioned more frequently in the current recording.

[0069] For example, Inverse Document Frequency (IDF) is used to characterize the prevalence and discriminative power (i.e., information entropy) of a word in a global corpus. It is calculated using the following formula:

[0070] Here, IDF is the inverse document frequency, M is the total number of texts in the global corpus, and N is the number of texts containing the specific word in the global corpus. The denominator is N+1 to prevent the solution from being impossible if the denominator is 0. For example, if there are M texts in the global corpus, N means that the specific word appears in N texts in the global corpus. Multiplying the inverse document frequency by the term frequency yields the weight value, which is also known as the term frequency-inverse document frequency (TF-IDF).

[0071] In some embodiments, retrieving solutions corresponding to a call topic based on topic keywords is achieved in the following ways: performing feature extraction processing on the topic keywords to obtain a retrieval feature vector; performing string matching on preset solutions in a preset database based on the topic keywords to obtain multiple candidate solutions; performing feature extraction processing on each candidate solution to obtain a solution feature vector; calculating the cosine similarity between each solution feature vector and the retrieval feature vector; and selecting the candidate solution with the largest cosine similarity as the solution corresponding to the call topic.

[0072] For example, a preset feature embedding model is invoked to perform text feature transformation on the extracted topic keywords, generating a multi-dimensional retrieval feature vector; the topic keywords are used as query terms, and string matching logic is executed in a preset business strategy database to extract records containing or partially matching topic keywords, generating a candidate set containing multiple candidate solutions; a preset neural network model is invoked to perform feature extraction on the description text or attribute fields of each candidate solution in the candidate set, generating a solution feature vector corresponding to each candidate solution; the cosine similarity value between each solution feature vector and the retrieval feature vector is calculated; the candidate solutions are sorted in descending order of cosine similarity value, and the candidate solution with the largest cosine similarity value is selected as the target solution to be sent to the current call topic.

[0073] In some embodiments, this application also provides a method for processing call recording data, wherein a call is established between a first terminal device and a second terminal device; Reference Figure 3B , Figure 3B This is a flowchart illustrating the method for processing call recording data provided in this application embodiment, which will be combined with... Figure 3B The steps shown are explained. The executing entity is... Figure 1 Server 200 in the middle.

[0074] In step 311, the evidence storage request sent by the first terminal device is received and forwarded to the second terminal device.

[0075] In step 312, a first confirmation instruction for the evidence storage request sent by the second terminal device is received, and the first confirmation instruction is sent to the first terminal device.

[0076] In step 313, a recording request sent by the first terminal device is received, and the recording request is forwarded to the second terminal device.

[0077] In step 314, a second confirmation instruction for the recording request is received from the second terminal device, and the second confirmation instruction is sent to the first terminal device so that the first terminal device records the call.

[0078] Here, the second terminal device records audio synchronously, the first terminal device records the first call recording data, and the second terminal device records the second call recording data.

[0079] In step 315, the first hash value corresponding to the first call recording data and the second hash value corresponding to the second call recording data are received, and the first hash value and the second hash value are compared.

[0080] In step 316, if the first hash value and the second hash value are the same, a certificate of evidence is generated and sent to the first terminal device and the second terminal device.

[0081] Here, the evidence certificate is used to indicate that the first call recording data and the second call recording data are the same and have not been modified. The principles of steps 311 to 316 can be referred to steps 301 to 306 above, and will not be repeated here.

[0082] In this embodiment, the first terminal device sends a storage request and a recording request to the second terminal device, and after obtaining the first confirmation instruction and the second confirmation instruction respectively, triggers simultaneous local recording on both ends, realizing recording operation with both parties fully informed. This ensures the right to know of the call participants and guarantees that recording is conducted with the authorization of both parties. The first and second terminal devices simultaneously record call recording data and store it independently. They perform hash calculations on the call recording data separately, and only send the calculated first and second hash values ​​to the server for comparison. This ensures that the original call recording data is stored only on the local terminal, avoiding the flow of sensitive communication data over the network and improving data confidentiality. Transmitting lightweight hash values ​​to the server instead of large-capacity call recording data significantly reduces network bandwidth consumption during the storage process and saves server storage space. The server, independent of the terminal, performs a consistency comparison of the separately generated first and second hash values. If the hash values ​​from both ends are found to be identical, a certificate of evidence is generated, allowing the terminal device to receive and store the certificate. Hash value comparison confirms that the call recording data collected by both terminals is consistent and has not been unilaterally modified. This mechanism, verified through third-party hash consensus, significantly enhances the objectivity and credibility of the final electronic certificate of evidence.

[0083] The following will describe an exemplary application of the call recording data processing method of this application in a practical application scenario.

[0084] With the widespread adoption of mobile internet and instant messaging technologies, electronic data storage plays a crucial role in protecting communication rights and solidifying facts. Currently, the following electronic data storage technologies exist for real-time communications (such as voice calls and video conferencing): (1) Centralized cloud-based recording mode. In this mode, the evidence storage platform server acts as the central node, receiving, recording, and storing the original audio data streams of each communicating party. Subsequently, the server extracts file characteristics and performs blockchain-based evidence storage. This centralized evidence storage mode requires the original call recording data to flow through and be stored on a third-party server, causing the data to be out of the physical control of the user terminal. In communication scenarios involving trade secrets or sensitive personal information, there is a high risk of data leakage, making it difficult to meet strict data privacy protection requirements.

[0085] (2) Unilateral Local Recording Mode. The party initiating the evidence storage request performs the recording task on its local terminal device. The original audio file is stored on the initiating party's local terminal, and then the local terminal calculates the hash value and uploads it to the cloud for evidence storage. This method lacks a multi-party cross-verification mechanism for the original data. The party initiating the evidence storage has the authority and physical conditions to perform modification actions (such as editing, splicing, and truncating) on ​​the audio file locally, and such modification actions cannot be effectively traced. Therefore, the call recording data stored on the local terminal cannot objectively prove its integrity and authenticity.

[0086] (3) Speech-to-text recording tool. This tool converts audio communication into text records by calling an Automatic Speech Recognition (ASR) model. This method only performs data conversion and lacks data anti-tampering and solidification mechanisms based on cryptography or blockchain technology. The generated text data can be edited arbitrarily and does not have the objective technical constraints required for electronic evidence preservation.

[0087] In addition, existing electronic evidence storage systems or devices usually exist as independent infrastructure, which has the following drawbacks: On the one hand, there is data isolation between the evidence storage function and subsequent business applications, and there is a lack of automated semantic analysis and business routing mechanisms based on the content of call recording data, resulting in low data flow efficiency between the evidence storage stage and subsequent business processing stages; the operation process of general evidence storage platforms is lengthy (involving real-name authentication, manual uploading and application, etc.), and the high interaction costs and usage thresholds make it difficult to adapt to the high-frequency, lightweight daily communication evidence storage needs.

[0088] In summary, call recording data preservation faces risks to data privacy and cross-tampering by multiple parties. Furthermore, related technologies for call recording data preservation also have limitations in terms of business linkage mechanisms and interaction efficiency.

[0089] This application provides a method for processing call recording data, aiming to solve the technical problems in related technologies such as the lack of an effective evidence preservation mechanism for multi-party communication processes, the complexity of general platform operation procedures, and the existence of data silos between the evidence preservation module and downstream services. By collecting call recording data during the communication process, a data solidification mechanism combining local encryption, blockchain on-chain verification, and timestamp verification is adopted. Combined with an asymmetric identity verification architecture based on initiator authorization and simplified verification by participants, electronic evidence preservation certificates are generated. Simultaneously, interface linkage between the evidence preservation module and subsequent business processing is achieved based on the characteristics of the evidence preservation data. Compared with existing technologies, this method improves the integrity and multi-party neutral anti-tampering capabilities of the preserved call recording data, reduces the interaction processing nodes for evidence preservation requests, and improves the efficiency of cross-system data flow.

[0090] See Figure 4 , Figure 4 This is a flowchart illustrating the method for processing call recording data provided in this application embodiment, which will be combined with... Figure 4 The steps shown are explained. Figure 4 The entity responsible for executing the steps is Figure 1 Terminal device 400-1 or terminal device 400-2.

[0091] In step 401, a certificate storage request is sent to the second terminal device participating in the call.

[0092] For example, the execution entity is designated as the first terminal device. The first terminal device executes the command, and the first and second terminal devices communicate through a first application. Assume a first user uses the first terminal device, and a second user uses the second terminal device. Both the first and second terminal devices have a second application installed; this second application is for call recording. A data preservation request is a specific network interaction command or data message designed to trigger the data solidification and preservation process. The second application on the second terminal device displays a confirmation control for the data preservation request as a floating window in the call interface of the first application. In response to the second user's triggering of the confirmation control, the second terminal device sends a confirmation command for the data preservation request to the first terminal device.

[0093] For example: The first user is a parent, and the second user is a teacher. The first user (e.g., the parent) selects the second user (e.g., the teacher) within the second application using their first terminal device, and clicks the "Initiate Evidence-Based Call" button to send an evidence-based request to the evidence-based server. Upon receiving the request, the evidence-based server immediately sends a push notification to the second user's (e.g., the teacher's) second terminal device, clearly informing them: "A parent has initiated an evidence-based call. The call content will be recorded simultaneously and independently by both users' phones to generate evidence-based credentials," and "Clicking 'Agree' will start the call and initiate evidence-based recording; clicking 'Reject' will cancel this call."

[0094] For example: The first user is an employee of Party A, and the second user is an employee of Party B. The first user (e.g., the employee of Party A) selects the second user (e.g., the employee of Party B) to communicate with within the second application using their first terminal device, and clicks the "Initiate Evidence Preservation Call" button to send an evidence preservation request to the evidence preservation server. Upon receiving the request, the evidence preservation server immediately sends a push notification to the second user's (e.g., the employee of Party B) second terminal device, clearly informing them: "Employee X has initiated an evidence preservation call. The call content will be recorded simultaneously and independently by both parties' mobile phones to generate evidence preservation certificates," and "Clicking 'Agree' will start the call and initiate evidence preservation; clicking 'Reject' will cancel this call."

[0095] In step 402, upon receiving a confirmation instruction for the evidence storage request, a recording request is sent to the second terminal device in response to the confirmation operation for the call recording.

[0096] For example, the confirmation instruction for the evidence storage request indicates that the second user has authorized the evidence storage of this call. Upon receiving the confirmation instruction for the evidence storage request, in response to the first user's confirmation operation for the call recording, a recording request is sent to the second terminal device. The recording request is a specific electronic control signaling used to trigger multi-terminal synchronous multimedia acquisition logic during a call.

[0097] In step 403, upon receiving a confirmation instruction for the recording request, recording of the call between the first terminal device and the second terminal device begins.

[0098] For example, the confirmation instruction for the recording request indicates that the second user agrees to start recording the content of this call. The second application on both the first and second terminal devices starts recording simultaneously. The entire recording process takes place locally on the terminal devices, without transmitting any raw audio data to the server; the original file is stored only on the user's own terminal device, and the server never accesses any raw data, fundamentally eliminating the risk of privacy leaks. Specifically designed for real-time communication scenarios, it can complete the evidence preservation process while the call is in progress.

[0099] For example, during the recording process, the second application recording the call content performs white noise keep-alive processing, pre-stores a silent audio file (which can be in MP3 format) of a preset duration on the Content Delivery Network (CDN) server; upon receiving a confirmation instruction for the recording request, the second application calls the underlying background audio playback interface to loop the silent audio file; through real-time background audio playback status detection events, the playback status is continuously monitored in real time, and when the single playback of the silent audio file is detected to have ended, a replay instruction is triggered; playing the silent audio file ensures that the second application can run stably in the background of the terminal device for more than the preset duration and will not be automatically closed by the terminal device.

[0100] During recording, the underlying audio acquisition interface is invoked to obtain the global audio output data stream from the terminal operating system. The sources of the global audio output data stream include, but are not limited to: cellular network calls, VoIP calls, video calls, local microphone input, and audio output from other applications. The recording format is MP3, with a sampling rate of 16kHz and a bitrate of 16kbps, thus minimizing file size while meeting audio feature recognition requirements. If any terminal device involved in the call disconnects from the network, closes a second application, loses network access, or is powered off, it will not affect the recording process of other terminal devices.

[0101] In some embodiments, the Network Time Protocol (NTP) is used to accurately synchronize the time of the first terminal device and the second terminal device to ensure that the time error recorded by both parties does not exceed 100 milliseconds.

[0102] In step 404, if the call ends, the call recording data is encrypted to obtain an encrypted file, and the call recording data is hashed to obtain a hash value.

[0103] For example, the original call recording data is encrypted using the Advanced Encryption Standard (AES) 256-bit encryption algorithm. The encrypted file is stored in a restricted execution environment and storage space independently allocated to the second application, isolated from the shared resources of other applications and terminal devices. The AES-256 algorithm uses fixed-length 128-bit data blocks and a 256-bit key. During encryption, the algorithm performs multiple rounds of iterative transformation operations on the original call recording data. Each round of transformation (except the last round) consists of four specific mathematical and logical state matrix transformation steps: byte substitution, row shifting, column mixing, and round key addition. The encryption key is randomly generated and stored locally on the terminal device.

[0104] For example, the first and second terminal devices each perform a 256-bit hash calculation using the Secure Hash Algorithm (SHA) on the recorded original audio file locally, generating a unique hash fingerprint (hash value) for the original audio file. Both terminal devices record simultaneously and independently, and the integrity and authenticity of the file are proven through a cloud-based hash comparison mechanism, resulting in evidence with near-notarization validity.

[0105] In some embodiments, the terminal device calls a second application to detect the audio volume in real time during the call. If the silence lasts for more than a certain period of time, the recording is terminated and no evidence report is generated. If only mono sound is detected, it is marked as abnormal evidence. During the call, call keywords are detected, and communication content that violates laws and regulations is marked as abnormal evidence.

[0106] Recording cannot be initiated by one party; both parties' terminal devices must be online and authorized to record simultaneously before recording can begin. Each party's terminal device records independently on its local machine, and the original files are stored in the local storage space of each terminal device. If either party hangs up the phone, the recording will terminate simultaneously, and no evidence report will be generated.

[0107] In step 405, the hash value is sent to the server so that the server can compare it with the hash value generated by the terminal device participating in the call.

[0108] For example, the server is only used to perform hash value comparisons and does not store the original audio files. The first and second terminal devices upload their hash values ​​to the evidence storage server. The server compares the two hash values: if the two hash values ​​are exactly the same, it means that the content recorded by the first and second terminal devices is completely identical and has not been tampered with by either party; if the two hash values ​​are inconsistent, it means that at least one terminal device's recording process malfunctioned or the file was tampered with, and the evidence storage fails.

[0109] In step 406, the comparison results are received and stored.

[0110] For example, if the hash value comparison passes, the evidence storage server uploads the two identical hash values, the identity information of both parties in the call, the call timestamp (generation time), the user's electronic signature, and the application platform's electronic signature to the blockchain for evidence storage. The hash value, file size, duration, user ID, and other information are simultaneously uploaded to a recognized and trusted platform, integrating different evidence storage certificates to generate a unique evidence storage number. An evidence storage certificate containing all the above information is generated and simultaneously sent to both the first and second terminal devices. The server only stores the evidence storage certificate and the hash value, not any original audio data. The evidence storage certificate includes the evidence storage number, generation time, identity information of both parties in the call, data information, user's electronic signature, application platform's electronic signature, and blockchain evidence storage identifier. The evidence storage certificate file can be in an unmodifiable file format. The certificate contains a unique verification QR code, which can be scanned to verify the authenticity of the evidence storage certificate online.

[0111] In step 407, text conversion is performed based on the call recording data to obtain the recording text, and topic detection is performed on the recording text to obtain topic keywords.

[0112] For example, the original call recording data is preprocessed, including format standardization and noise reduction. An Automatic Speech Recognition (ASR) model is then used to convert the preprocessed call recording data into text, resulting in the recording text. Based on the recording text, a Natural Language Processing (NLP) model is used to perform sentence segmentation and tokenization, and part-of-speech tagging is used to filter out stop words (such as modal particles, conjunctions, and noisy text) to obtain a valid word sequence. A pre-defined word vector model (such as Word2Vec or BERT) is then used to map the valid word sequence into high-dimensional semantic feature vectors. Based on the semantic feature vectors, the term frequency (TF) of each valid word in the recording text is calculated, and the inverse document frequency (IDF) is calculated using a global evidence corpus. The TF and IDF are multiplied to obtain the TF-IDF, which is then sorted from highest to lowest according to a comprehensive weight score. The top N words are selected as topic keywords (where N is a positive integer greater than or equal to 1).

[0113] In step 408, a search is performed based on topic keywords to obtain the solution corresponding to the topic.

[0114] For example, the retrieval process is implemented through vector retrieval in the database, calling a pre-defined text embedding model (such as Word Embedding) to transform the set of topic keywords into retrieval feature vectors with multi-dimensional continuous features. The database stores solutions and their corresponding feature vectors; based on the topic keywords, exact string matching is performed on the solutions to obtain multiple candidate solutions; based on the retrieval feature vectors, the cosine similarity between the feature vectors corresponding to the candidate solutions and the retrieval feature vectors is calculated, and the candidate solution with the highest cosine similarity is selected as the solution corresponding to the topic.

[0115] For example, if the first user is the project requester (Party A) and the second user is the project contractor (Party B), and during a call between them discussing the project's technical development progress, the recorded text is analyzed to extract key terms such as "requirement change," "delayed delivery," and "increased scheduling." Based on these key terms, a search vector is generated and searched within a pre-defined enterprise business database to obtain a search solution corresponding to that keyword combination. The solution may include, but is not limited to, a standardized template for a project delay supplementary agreement, or relevant documents detailing the changed requirements.

[0116] For example: the first user is a parent, the second user is a teacher, and the conversation discusses the child's academic performance. The detected keywords are "academic performance," "subject imbalance," and "grade level." Based on these keywords, a search is performed to obtain solutions related to the topic. These solutions could be public articles, links to purchase study guides, or advertisements for tutoring classes. As another example: the first user is a parent, the second user is a teacher, and the conversation discusses the child's behavioral problems. The detected keywords are "behavioral habits" and "poor athletic ability." Based on these keywords, a search is performed to obtain solutions related to the topic. These solutions could be recommendations for outdoor activities or advertisements for sports-related tutoring classes.

[0117] In this embodiment, (1) recording is performed through a second application other than the first application for the call function. The background process is kept alive by playing silent audio in a loop, so that the second application continues to call the underlying audio interface to occupy the media output channel of the terminal device, thus maintaining the active status of the application in the operating system. This mechanism effectively avoids the risk of the application being automatically suspended when it is moved to the background, ensures the continuous operation of the audio acquisition thread for a long preset time, and prevents the unexpected interruption of the recording data. (2) By completing the generation, encryption and hash calculation logic of the original multimedia file in the local isolated environment of the terminal, the server only needs to receive and process the fixed-length hash digest for consistency verification, and does not receive the original call recording data. The path of the original data flow to the cloud is completely cut off from the network topology level, ensuring the privacy and security of sensitive call recording data. (3) Recording instructions are triggered synchronously by both ends, identity comparison is based on an external authoritative feature database, and physical feature detection is based on audio energy and channel status. In the early stage of recording, unilateral forged requests or call requests for non-target business scenarios are automatically identified and filtered. By using the native channel of a third-party basic communication application to establish a session and forcibly trigger the synchronous independent recording of both ends of the communication, the asymmetric characteristics of unilateral data collection are eliminated. Through the consensus mechanism of independent encryption calculation of hash values ​​by both ends and comparison of consistency, the integrity of the original data is proved without touching the plaintext; then the consistent hash value is synchronized to the third-party independent node cluster (such as blockchain) for on-chain solidification, ensuring the immutability of the call recording data. (4) High-dimensional semantic feature extraction and topic keyword detection are performed on the transcribed text of the evidenced speech using natural language processing technology. By automatically searching and calculating the matching degree between the extracted semantic feature vector and the preset database, solutions can be generated or obtained in real time and accurately, improving the automation level of the business processing process and the overall response efficiency.

[0118] The following description continues to illustrate the exemplary structure of the call recording data processing device 455 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2A As shown, the software modules in the call recording data processing device 455 stored in the memory 450 may include: a request sending module 4551, configured to send a certificate of authenticity request to a second terminal device participating in the call, wherein a call is established between the first terminal device and the second terminal device; the request sending module 4551, configured to, upon receiving a first confirmation instruction for the certificate of authenticity request, send a recording request to the second terminal device in response to a confirmation operation for the call recording; a recording module 4552, configured to, upon receiving a second confirmation instruction for the recording request, record the call, wherein the second terminal device records synchronously; and an encryption module 4553, configured to, after the call ends... In the case of a call recording, the first call recording data recorded by the first terminal device is hashed to obtain a first hash value, wherein the second terminal device synchronously performs a hash calculation on the recorded second call recording data to obtain a second hash value; the encryption module 4553 is used to send the first hash value and the second hash value to the server so that the server compares the first hash value and the second hash value; the evidence storage module 4554 is used to receive and store an evidence storage certificate of the first call recording data when the first hash value and the second hash value are the same, wherein the evidence storage certificate is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0119] In some embodiments, the evidence storage module 4554 is configured to, after receiving and storing the evidence storage certificate of the first call recording data, perform speech-to-text processing on the first call recording data to obtain the recording text; extract keywords from the recording text to obtain topic keywords; and retrieve solutions corresponding to the call topic based on the topic keywords.

[0120] In some embodiments, the evidence storage module 4554 is used to perform word segmentation on the recorded text to obtain multiple first word segments; to filter the multiple first word segments according to part-of-speech tagging to obtain multiple second word segments, wherein the filtering includes deleting modal particles, deleting conjunctions, and deleting noisy text; to map the multiple second word segments into semantic feature vectors, and to calculate the word frequency of each second word segment in the recorded text based on the semantic feature vectors; to calculate the inverse document frequency of each second word segment based on a preset global corpus; to multiply the inverse document frequency by the word frequency to obtain the weight value of the second word segment; and to select the second word segment with the largest preset number of weight values ​​as the topic keywords.

[0121] In some embodiments, the evidence storage module 4554 is used to perform feature extraction processing on the topic keywords to obtain a retrieval feature vector; perform string matching on preset solutions in a preset database based on the topic keywords to obtain multiple candidate solutions; perform feature extraction processing on each candidate solution to obtain a solution feature vector; calculate the cosine similarity between each solution feature vector and the retrieval feature vector; and select the candidate solution with the largest cosine similarity as the solution corresponding to the call topic.

[0122] In some embodiments, the encryption module 4553 is used to perform hash calculation on the first call recording data recorded by the first terminal device to obtain a first hash value, and then encrypt the first call recording data to obtain a first encrypted file. The second terminal device simultaneously encrypts the second call recording data to obtain a second encrypted file. The first encrypted file and the second encrypted file are prohibited from being modified.

[0123] In some embodiments, the file of the evidence storage certificate is a file that cannot be modified, and the evidence storage certificate is stored in the blockchain; the evidence storage certificate includes: evidence storage number, evidence storage certificate generation time, recording time period of call recording data, identity information of the parties involved in the call, device information of the first terminal device, device information of the second terminal device, first electronic signature of the first user using the first terminal device, second electronic signature of the second user using the second terminal device, and blockchain evidence storage identifier.

[0124] The following description continues to illustrate the exemplary structure of the call recording data processing device 255 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2BAs shown, the software modules in the call recording data processing device 255 stored in the memory 250 may include: a forwarding module 2551, configured to receive a certificate storage request sent by the first terminal device and forward the certificate storage request to the second terminal device, wherein a call is established between the first terminal device and the second terminal device; a forwarding module 2551, configured to receive a first confirmation instruction sent by the second terminal device for the certificate storage request and send the first confirmation instruction to the first terminal device; a forwarding module 2551, configured to receive a recording request sent by the first terminal device and forward the recording request to the second terminal device; and a forwarding module 2551, configured to receive a second confirmation instruction sent by the second terminal device for the recording request and send the second confirmation instruction to the second terminal device. A command is sent to the first terminal device to record the call, wherein the second terminal device records the call synchronously, the first terminal device records first call recording data, and the second terminal device records second call recording data; a comparison module 2552 is used to receive a first hash value corresponding to the first call recording data and a second hash value corresponding to the second call recording data, and compare the first hash value with the second hash value; a credential generation module 2553 is used to generate a certificate of evidence and send the certificate of evidence to the first terminal device and the second terminal device when the first hash value and the second hash value are the same, wherein the certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

[0125] This application provides a computer program product, which includes a computer program or computer-executable instructions stored in a computer-readable storage medium. The processor of an electronic device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the electronic device to perform the call recording data processing method described above in this application.

[0126] This application provides a computer-readable storage medium storing computer-executable instructions or a computer program. When the computer-executable instructions or the computer program are executed by a processor, the processor will execute the call recording data processing method provided in this application. For example, ... Figure 3A The method for processing call recording data is shown.

[0127] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0128] In some embodiments, computer-executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

[0129] As an example, computer-executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a HyperText Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple co-located files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0130] As an example, computer-executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located at one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0131] In summary, through the embodiments of this application, the first terminal device sends a storage request and a recording request to the second terminal device, and after obtaining the first confirmation instruction and the second confirmation instruction respectively, triggers simultaneous local recording on both ends, realizing recording operations with both parties fully informed. This ensures the right to know of the call participants and guarantees that recording is conducted with the authorization of both parties. The first and second terminal devices simultaneously record call recording data and store it independently. They perform hash calculations on the call recording data separately and only send the calculated first and second hash values ​​to the server for comparison. This ensures that the original call recording data is stored only on the local terminal, avoiding the flow of sensitive communication data over the network and improving data confidentiality. Transmitting lightweight hash values ​​to the server instead of large-capacity call recording data significantly reduces network bandwidth consumption during the storage process and saves server storage space. The server, independent of the terminal, performs a consistency comparison of the separately generated first and second hash values. If the hash values ​​from both ends are found to be identical, a certificate of evidence is generated, allowing the terminal device to receive and store the certificate. Hash value comparison confirms that the call recording data collected by both terminals is consistent and has not been unilaterally modified. This mechanism, verified through third-party hash consensus, significantly enhances the objectivity and credibility of the final electronic certificate of evidence.

[0132] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for processing call recording data, characterized in that, A call is established between a first terminal device and a second terminal device, the method being executed by the first terminal device; the method includes: Send a certificate storage request to the second terminal device participating in the call; Upon receiving a first confirmation instruction for the evidence storage request, in response to a confirmation operation for the call recording, a recording request is sent to the second terminal device; Upon receiving a second confirmation instruction for the recording request, the call is recorded, wherein the second terminal device records the call synchronously. When the call ends, the first call recording data recorded by the first terminal device is hashed to obtain a first hash value, wherein the second terminal device synchronously performs hash calculation on the recorded second call recording data to obtain a second hash value; The first hash value and the second hash value are sent to the server so that the server compares the first hash value and the second hash value. If the first hash value and the second hash value are the same, a certificate of evidence for the first call recording data is received and stored, wherein the certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

2. The method according to claim 1, characterized in that, After receiving and storing the evidence of the first call recording data, the method further includes: The first call recording data is processed to convert speech to text, resulting in the recording text. Keyword extraction was performed on the audio transcript to obtain topic keywords; Based on the aforementioned topic keywords, search for solutions corresponding to the call topics.

3. The method according to claim 2, characterized in that, The keyword extraction from the recorded text to obtain topic keywords includes: The recorded text is segmented into multiple first-order words. The multiple first word segments are filtered based on part-of-speech tagging to obtain multiple second word segments, wherein the filtering includes deleting modal particles, deleting conjunctions, and deleting noisy text; The plurality of second word segments are mapped to semantic feature vectors, and the word frequency of each second word segment in the recorded text is calculated based on the semantic feature vectors. The inverse document frequency of each second word is calculated based on a preset global corpus; Multiply the inverse document frequency by the term frequency to obtain the weight value of the second word segmentation; The second word with the largest preset weight value is used as the topic keyword.

4. The method according to claim 2, characterized in that, The solution for retrieving call topics based on the topic keywords includes: The topic keywords are subjected to feature extraction processing to obtain a retrieval feature vector; Based on the topic keywords, string matching is performed on the preset solutions in the preset database to obtain multiple candidate solutions; For each candidate solution, feature extraction is performed to obtain the solution feature vector; Calculate the cosine similarity between each of the scheme feature vectors and the retrieval feature vectors; The candidate solution with the highest cosine similarity is selected as the solution corresponding to the call topic.

5. The method according to claim 1, characterized in that, After performing a hash calculation on the first call recording data recorded by the first terminal device to obtain a first hash value, the method further includes: The first call recording data is encrypted to obtain a first encrypted file, wherein the second terminal device synchronously encrypts the second call recording data to obtain a second encrypted file, and the first encrypted file and the second encrypted file are prohibited from being modified.

6. The method according to claim 1, characterized in that, The document containing the evidence is a file that cannot be modified, and the evidence is stored on the blockchain. The evidence storage certificate includes: evidence storage number, evidence storage certificate generation time, recording time period of call recording data, identity information of the parties involved in the call, device information of the first terminal device, device information of the second terminal device, first electronic signature of the first user using the first terminal device, second electronic signature of the second user using the second terminal device, and blockchain evidence storage identifier.

7. A method for processing call recording data, characterized in that, A call is established between a first terminal device and a second terminal device; the method includes: Receive the evidence storage request sent by the first terminal device and forward the evidence storage request to the second terminal device; Receive a first confirmation instruction sent by the second terminal device for the evidence storage request, and send the first confirmation instruction to the first terminal device; Receive a recording request sent by the first terminal device and forward the recording request to the second terminal device; The system receives a second confirmation instruction from the second terminal device regarding the recording request, and sends the second confirmation instruction to the first terminal device so that the first terminal device records the call. The second terminal device records the call simultaneously, the first terminal device records first call recording data, and the second terminal device records second call recording data. Receive the first hash value corresponding to the first call recording data and the second hash value corresponding to the second call recording data, and compare the first hash value with the second hash value; If the first hash value and the second hash value are the same, a certificate of evidence is generated and sent to the first terminal device and the second terminal device. The certificate of evidence is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

8. A device for processing call recording data, characterized in that, The device includes: The request sending module is used to send a certificate storage request to the second terminal device participating in the call, wherein a call is established between the first terminal device and the second terminal device; The request sending module is configured to send a recording request to the second terminal device in response to a confirmation operation for the call recording, upon receiving a first confirmation instruction for the evidence storage request. A recording module is used to record a call upon receiving a second confirmation instruction for the recording request, wherein the second terminal device records the call synchronously. An encryption module is used to perform a hash calculation on the first call recording data recorded by the first terminal device to obtain a first hash value when the call ends, wherein the second terminal device synchronously performs a hash calculation on the recorded second call recording data to obtain a second hash value; The encryption module is used to send the first hash value and the second hash value to the server so that the server can compare the first hash value and the second hash value; The evidence storage module is used to receive and store evidence of the first call recording data when the first hash value and the second hash value are the same, wherein the evidence storage certificate is used to indicate that the first call recording data and the second call recording data are the same and have not been modified.

9. An electronic device, characterized in that, The electronic device includes: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the method for processing call recording data as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer program are executed by a processor, the method for processing call recording data as described in any one of claims 1 to 7 is implemented.

Images