File transmission auditing method in call, terminal, server and electronic equipment

Abstract

The embodiment of the invention discloses a file transmission auditing method in a call, a terminal, a server and electronic equipment, and relates to the technical field of communication, and the method comprises the following steps: a first terminal preloads an applet through a first VoNR + media interface and establishes a call channel with a second terminal; and the content sharing service server creates corresponding first and second terminal / media surface data channels. The first terminal sends the shared content to the server, the server analyzes the shared content and requests the auditing module for auditing, if the auditing fails, forwarding is stopped, the first terminal is notified, if the auditing succeeds, the media interface is called to send the content to the second terminal, or the server calls the media interface to send the content to the second terminal, and then the auditing module conducts auditing; and if the audit fails, triggering a withdrawing mechanism to enable the second terminal to delete the file. According to the embodiment of the invention, the real-time transmission and intelligent auditing of the file in the call process are realized, the application does not need to be switched, the call continuity is ensured, and the user experience and the auditing efficiency are improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for verifying file transfers during a call, a terminal, a server, and an electronic device. Background Technology

[0002] In existing communication solutions, if different terminals are in a call, file transfer and verification typically rely on third-party applications. For example, many communication solutions are based on HTTP / HTTPS protocols, using third-party applications to handle file transfer and verification through client-server interaction. The client constructs an HTTP / HTTPS POST request, encapsulates the file data in multipart / form-data format, and sends it to the server. Upon receiving the request, the server parses it, extracts the file data, and performs preprocessing as needed to complete the file upload. Then, the server checks the file content and implements appropriate verification logic based on the file type. After verification, the file is further processed according to different business requirements.

[0003] It can be seen that existing file transfer verification solutions during calls rely on third-party applications. Users need to switch to this third-party application to transfer files during a call, resulting in a lack of synchronous interaction between the call and file transfer. Furthermore, this leads to complex procedures and a poor user experience. Additionally, because third-party applications rely on their own security mechanisms, there are security vulnerabilities and data leakage risks in the file encryption and real-time verification processes, and they lack the ability to promptly intercept non-compliant files.

[0004] The above indicates that the existing file transfer verification scheme during calls is no longer suitable for the technical requirements of China Mobile's new 5G call platform and urgently needs to be improved. Summary of the Invention

[0005] This application addresses some of the shortcomings mentioned in the background art by providing a method for reviewing file transfers during a call, a terminal, a server, and an electronic device.

[0006] The embodiments of this application are implemented using the following technical solutions: According to one aspect of the embodiments of this application, an IMS-based... The DC's in-call file transfer review method, based on multiple terminals, servers, and a VoNR+ media plane, includes: a first terminal preloads a mini-program through a first VoNR+ media plane and initiates a call, establishing a call channel with a second terminal; a content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel; the first terminal sends shared content to the content sharing service server through the first terminal / media plane data channel; the content sharing service server parses the shared content and requests review from the content review module; if the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result; if the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, or: the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel; the content review module reviews the shared content and notifies the content sharing service server of the review result; or: if the review fails, the content sharing service server triggers an non-compliant file recall mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0007] According to at least one specific embodiment of the present application, the first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel. The process further includes: the first terminal initiating a call to the second terminal and establishing a mini-program control channel to request the download of a mini-program; the first VoNR+ media plane acquiring the mini-program and responding to the first terminal with a request to download the mini-program through the mini-program control channel; and the first terminal requesting the download of the mini-program from the first VoNR+ media plane through the mini-program control channel. The guiding mini-program involves the first VoNR+ media plane generating a corresponding mini-program list and transmitting response data back to the first terminal via the guiding mini-program control channel. The first terminal obtains the automatically loaded mini-program from the mini-program list and sends a request to the first VoNR+ media plane to download the automatically loaded mini-program via the guiding mini-program control channel. The second terminal accepts the call request from the first terminal, establishes a corresponding call channel, and the first terminal updates the call interface. The first terminal runs the guiding mini-program and sends a command from the guiding mini-program control channel to request the download of a content sharing mini-program from the first VoNR+ media plane to its local machine and run the content sharing mini-program.

[0008] According to at least one specific implementation of the embodiments of this application, it further includes: the content sharing applet initiating a re-INVITE renegotiation; the content sharing service server creating a data channel, the data channel including an end-to-end data channel for transmitting control messages, and: a first terminal / media plane data channel and a second terminal / media plane data channel, the first and second terminal / media plane data channels being used to transmit data messages; the first terminal initiating a call to the second terminal, establishing a guide applet control channel to request the download of the guide applet, further including: establishing a dedicated media data channel, the dedicated media data channel being used to provide specific enhanced services.

[0009] According to at least one specific embodiment of the present application, the second terminal accepts the call request of the first terminal and establishes a corresponding call channel. The first terminal updates the call interface, specifically: the first terminal updates the call interface during the call, selects the content sharing menu in the call interface, and the guide applet running on the first terminal downloads the content sharing applet from the first VoNR+ media plane to the local machine according to the content sharing menu and runs it in the local applet runtime environment.

[0010] According to at least one specific embodiment of the present application, the first terminal sends shared content to the content sharing service server through the first terminal / media plane data channel. The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The process further includes: the content sharing service server obtaining the shared content and requesting review from the content review module; the content review module completing the review and notifying the content sharing service server; if the content review module fails to review the shared content, the content sharing service server terminates data forwarding and notifies the first terminal that the review is complete; the first terminal, according to a preset operation strategy, may or may not present the review result from the shared content.

[0011] According to at least one specific embodiment of the present application, the content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result, or: the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. This further includes: the content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The shared content is sent to the second terminal; the content sharing service server parses the content sharing stream to obtain the corresponding photos / videos, requests review from the content review module, the content review module reviews the shared content, and notifies the content sharing service server of the review result; if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the first VoNR+ media plane recognizes the non-compliant file withdrawal mechanism, and sends a non-compliant file withdrawal request to the second terminal; the second terminal sends a successful withdrawal receipt to the first VoNR+ media plane and deletes the local file; the content sharing service server notifies the first terminal of the file review failure result.

[0012] According to at least one specific implementation of the embodiments of this application, the method further includes: after the first terminal receives the receipt from the second terminal, it requests the second terminal to withdraw the shared content; the second terminal receives the request to withdraw the shared content, sends a withdrawal success receipt to the first terminal, the second terminal deletes the local file, and the first terminal deletes the local sending record.

[0013] According to another aspect of the embodiments of this application, a method for reviewing file transfers during a call based on IMS DC is provided, applied to a first terminal, comprising: the first terminal preloads a mini-program through a first VoNR+ media plane and initiates a call to establish a call channel with a second terminal; the first terminal requests the first VoNR+ media plane to download a content sharing mini-program through a mini-program control channel; the first terminal initiates a re-INVITE renegotiation with the second terminal through the content sharing mini-program, and sends shared content to the first VoNR+ media plane through a first terminal / media plane data channel, wherein the first terminal / media plane data channel is created by a content sharing service server; the first terminal obtains the review result of the shared content from the content review module, and according to a preset operation strategy, the first terminal either presents or does not present the file review result, or withdraws the shared content through the first terminal / media plane data channel.

[0014] According to at least one specific embodiment of the present application, the first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The first terminal requests the first VoNR+ media plane to download a content-sharing mini-program through a guide mini-program control channel. This further includes: the first terminal initiating a call to the second terminal and establishing a guide mini-program control channel to request the download of a guide mini-program; the first terminal receiving a response from the first VoNR+ media plane requesting the download of a corresponding mini-program list from the first VoNR+ media plane through the guide mini-program control channel; the first terminal downloading the preloaded mini-program according to the mini-program list, initiating a call to the second terminal, and establishing a call channel with the second terminal; the first terminal updating the call interface during the call, selecting a content-sharing menu in the call interface, and sending a request through the guide mini-program control channel; the guide mini-program running on the first terminal downloading the content-sharing mini-program from the first VoNR+ media plane to its local machine according to the content-sharing menu and running it in the local mini-program runtime environment; the first terminal sending a file through the content-sharing mini-program and requesting content sharing from the second terminal through the first terminal / media plane data channel.

[0015] According to at least one specific implementation of the embodiments of this application, it further includes: a first terminal obtaining an audit result from a content sharing service server, wherein the audit result is an audit result sent by a content audit module; or: the first terminal receiving a receipt from a second terminal and requesting the second terminal to withdraw the shared content; the first terminal receiving a withdrawal success receipt from the second terminal and deleting the local sending record.

[0016] According to another aspect of the embodiments of this application, a method for reviewing file transfers during a call based on IMS DC is provided, applied to a second terminal, comprising: in response to a call from a first terminal, the second terminal establishing a call channel with the first terminal; obtaining a re-INVITE renegotiation initiated by the first terminal, and the second terminal requesting a content sharing applet to download from a second VoNR+ media plane; if the content review module passes the review, the second terminal obtaining the corresponding content sharing through the second terminal / media plane data channel, or: the second terminal obtaining a request to withdraw non-compliant files sent by the first VoNR+ media plane.

[0017] According to at least one specific implementation of the embodiments of this application, if the content review module passes the review, the second terminal obtains the corresponding content sharing through the second terminal / media plane data channel. Specifically, if the content review module passes the review, the second terminal obtains the content sharing through the second terminal / media plane data channel. The content sharing is a content sharing service server calling the interface of the first VoNR+media plane and sending it to the second terminal through the second terminal / media plane data channel.

[0018] According to at least one specific implementation of the embodiments of this application, the second terminal obtaining the request to withdraw a non-compliant file sent by the first VoNR+ media plane further includes: the second terminal receiving a successful withdrawal receipt of the non-compliant file sent by the first VoNR+ media plane and deleting the local file; or: the second terminal sending a receipt to the first terminal, receiving a request to withdraw shared content from the first terminal; the second terminal sending a successful withdrawal receipt to the first terminal and deleting the local file.

[0019] According to at least one specific implementation of the embodiments of this application, it further includes: the second terminal sending content sharing to the second VoNR+ media plane through the second terminal / media plane data channel; the content sharing service server reviewing the content sharing; associating the first and second terminal / media plane data channels; and forwarding the content sharing to the first terminal through the first terminal / media plane data channel.

[0020] According to another aspect of the embodiments of this application, a method for reviewing file transfers during a call based on IMS DC is provided, applied to a content sharing service server, comprising: the content sharing service server creating a first terminal / media plane data channel and a second terminal / media plane data channel, and obtaining sharing content sent by the first terminal; the content sharing service server parsing the sharing content, requesting review from a content review module, and if the review fails, the content sharing service server terminating data forwarding and notifying the first terminal of the review result; if the review succeeds, the content sharing service server calling the first VoNR+media plane to send the sharing content to the second terminal through the second terminal / media plane data channel, or: the content sharing service server calling the interface of the first VoNR+media plane to send the sharing content to the second terminal through the second terminal / media plane data channel, the content review module reviewing the sharing content and notifying the content sharing service server of the review result, or: if the review fails, the content sharing service server triggers a non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0021] According to at least one specific implementation of the embodiments of this application, the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. Further, the content sharing service server obtains the shared content, requests review from the content review module, the content review module completes the review and notifies the content sharing service server. If the content review module fails to review the shared content, the content sharing service server terminates data forwarding and notifies the first terminal that the review is complete.

[0022] According to at least one specific embodiment of the present application, the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. This further includes: the content sharing service server calling the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel; the content sharing service server parsing the content sharing bitstream to obtain the corresponding photos / videos, requesting review from the content review module; the content review module reviewing the shared content and notifying the content sharing service server of the review result; if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the first VoNR+ media plane identifies the non-compliant file withdrawal mechanism, sends a non-compliant file withdrawal request to the second terminal; and the content sharing service server notifies the first terminal of the file review failure result.

[0023] According to another aspect of the embodiments of this application, a call file transfer review system based on IMS DC is provided to implement the call file transfer review method based on IMS DC, including: a terminal / media plane data channel construction module, in which a first terminal preloads a mini-program through a first VoNR+ media plane and initiates a call to establish a call channel with a second terminal, and a content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel; and a shared content review before sending module, in which the first terminal sends shared content to the content sharing service server through the first terminal / media plane data channel, the content sharing service server parses the shared content, requests review from the content review module, and if the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review is successful, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel; or: the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, and the content review module reviews the shared content and notifies the content sharing service server of the review result; or: if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0024] According to another aspect of the embodiments of this application, an electronic device is provided, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method.

[0025] The effective technical effects of the embodiments in this application are: This application embodiment enables real-time file transfer and review during calls on different terminals without requiring users to switch to third-party applications. This avoids call interruptions caused by file transfer and review, improving the user's call experience. Integrating file transfer and review functions into calls on different terminals shortens file review time and improves efficiency. It also enhances the interactivity and real-time nature of the call and file transfer processes. Furthermore, it is more discreet for users, as there will be no unpleasant experience of file transfer interfering with the call once the file review is successful.

[0026] This application combines different terminals, VoNR+ media planes, and content sharing service servers, enabling file transfer and review to be seamlessly integrated with other functions such as call processes and video conferencing. Unlike existing technologies, it eliminates the need to switch between different application software across different applications or platforms, avoiding the adverse effects of cumbersome file operations and complex review processes. It achieves efficient multi-terminal, server-side, and VoNR+ media plane multi-terminal and multi-service collaborative operation.

[0027] This application embodiment can adopt different review methods for shared content according to the size of the file. For smaller files (such as profile pictures, etc.), a review-before-sending method is adopted, while for larger files (such as large pictures or video files), a sending-before-review method is adopted. This can flexibly treat files with different characteristics and provide different review methods, thereby improving the efficiency of file review.

[0028] This application also provides a multi-layered recall mechanism based on file transfer and review, ensuring that inappropriate content can be quickly and accurately recalled at any stage of data transmission should a potential problem be discovered, providing controllability for file transfer during calls. Compared to existing file transfer and review technologies that rely on third-party applications, this technology achieves full-process tracking and control of file review in multi-stage, multi-platform data flow, thereby reducing the complexity of file and data management and avoiding potential risks caused by improper review during file transfer. Attached Figure Description

[0029] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application.

[0030] Figure 2 This is a flowchart of Implementation Example 1 (multiple terminals).

[0031] Figure 3 This is a flowchart of the method in Embodiment 2 (first terminal).

[0032] Figure 4 This is a flowchart of the method in Example 3 (Second Terminal).

[0033] Figure 5 This is a flowchart of the method in Example 4 (server side).

[0034] Figure 6 This is a sequence diagram of the file transfer verification method during a call.

[0035] Figure 7 This is a diagram of the content review process architecture.

[0036] Figure 8 This is an architecture diagram of a file transfer verification system during a phone call.

[0037] Figure 9 This is a schematic diagram of the electronic device. Detailed Implementation

[0038] The present application / disclosure will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application / disclosure and are not intended to limit the scope of the present application / disclosure. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present application / disclosure are shown in the accompanying drawings, not the entire structure.

[0039] like Figure 1 As shown, Figure 1 A possible system architecture 100 is shown. It should be noted that the figures are merely examples of system architectures that can be applied to the embodiments of this application, to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.

[0040] The system architecture 100 of this application embodiment includes a first terminal, a second terminal, a VoNR+ media plane, and a content sharing service server. The VoNR+ media plane is based on the VoNR+ platform, which is the core system for implementing 5G New Voice (VoNR+) functionality. It can provide ultra-high-definition voice and video calls, as well as a series of real-time interactive enhanced services based on the enhanced 5G network. The VoNR+ media plane is a Media Resource Function Processor (MRFP) responsible for the unified and intelligent processing of all media streams, providing powerful media processing capabilities, including but not limited to transcoding, copying, and forwarding of audio and video streams, as well as complex video synthesis and rendering, such as overlaying AR effects, virtual backgrounds, real-time subtitles, etc. Through communication and interaction with the first and second terminals, the VoNR+ platform (media plane) can establish high-quality calls for the first and second terminals and empower them with rich enhanced experiences.

[0041] Users can use the first and second terminals to interact with the content sharing service server via VoNR+ media plane to implement an in-call file transfer verification method based on IMS DC. Various general-purpose or dedicated applications can be installed on the first and second terminals. The terminals are not limited to the first and second terminals shown in the diagram; more terminal devices can collaborate with the content sharing service server through VoNR+ media plane or by establishing a call channel to implement the in-call file transfer verification method based on IMS DC, and perform storage, retrieval, and mutual communication. The first and second terminals can be existing mobile phones, tablets, etc., and the content sharing service server can be a server providing various cloud services, storage, management, and content sharing.

[0042] It should be noted that the in-call file transfer verification method based on IMS DC provided in this application is completed by the first and second terminals in cooperation with the VoNR+ media plane and the content sharing service server. In one possible embodiment, in order to implement the in-call file transfer verification method based on IMS DC, the first and second terminals send a request to the content sharing service server through the VoNR+ media plane. The content sharing service server receives the request from the first and second terminals through the VoNR+ media plane, and sends a corresponding response message based on the rules of communication interaction and file verification, combined with the actual environment, working conditions and scenarios of the first and second terminals.

[0043] It should be understood that the number of first and second terminals, VoNR+ media plane, and content sharing service servers in System Architecture 100 is merely illustrative. In other application scenarios, any number of terminals, servers, electronic devices, network platforms, and servers can be used depending on implementation needs.

[0044]

[0045] In the above Chinese-English explanation, the Content Sharing Service Server is one of the service components of the New Call Service Control Unit (AS), which can also be understood as the Content Sharing Service AS being the service control unit of the Content Sharing Module.

[0046] In this application embodiment, the file transfer and verification method during IMS DC calls belongs to the 5G VoNR+ system. By utilizing the dedicated data channel (IMS DC) in the IMS network, it achieves secure and real-time file transfer during multimedia calls and integrates a file verification mechanism to ensure the compliance and security of transmitted content. It supports the simultaneous transmission of various file types (images, videos, etc.) during calls. This application embodiment has a wide range of applications; various telecom operators and telecom equipment suppliers can integrate the data channel of this application embodiment to deploy corresponding in-call file transfer and verification systems, realizing secure file transfer and compliance verification functions during calls.

[0047] The main application scenario of this application is a method for file transfer and review during calls based on the IP Multimedia Subsystem Data Channel (IMS DC). In this main application scenario, the flexibility of the IMS architecture, the efficient data transmission capability of DC, and deep integration with intelligent review strategies are utilized to achieve real-time file exchange and real-time, accurate, and dynamic intelligent review functions during calls. In the main application scenario of this application, a dynamically generated mini-program is embedded in the call interface based on IMS data channel technology. A hierarchical ADC channel is dynamically created by loading a re-INVITE renegotiation mechanism based on the SIP protocol through the dynamic mini-program. This achieves separation of control messages and data messages, realizes end-to-end content transmission control, and verifies file compliance in real time during transmission. Combined with a security mechanism of manual review, this enables timely interception or withdrawal of illegal content.

[0048] The technical solutions involved in this application have been applied to 5G new voice communication platforms and related products and services. Currently, 5G new voice communication services have been successfully piloted in multiple provinces. Related services were demonstrated and tested during the 2023 Hangzhou Asian Games and the 2024 Spring Festival, with an initial user base of 10 million. It will subsequently be expanded nationwide as a key strategic business. This application's embodiments can be quickly adapted to multiple telecom operators through modular porting, thereby accelerating the deployment of 5G new voice communication services.

[0049] This application embodiment is an important technical component of the 5G New Calling Service Management Platform project and a core part of 5G new calling service construction. The 5G New Calling Service Management Platform project aims to construct a network-service separation, open and agile, manageable and controllable platform based on the relevant requirements for 5G new calling operation and management. It promotes open and unified platform construction, enables product system operation, strengthens provincial and specialized network collaboration for rapid incubation of innovative application models, ensures decoupling of core network basic calling functions and media value-added service capabilities, meets the needs of rapid iteration and launch of new calling services, and leverages IP cultural content to empower content through product system operation, expand user scale, and promote capability interoperability and integration to create innovative and distinctive applications based on the open ecosystem of 5G new calling capabilities. The project involves the division of labor in building the new calling service management platform, media capability platform, and APP system, and upgrading the existing industry calling platform. It provides various necessary system capabilities such as user management, service management, content management, and capability aggregation operation for both toC and toB new calling services, facilitating the rapid development of new calling services. The main application scenario of this application embodiment can be used as the core management platform for new call services. It has the ability to handle the surge in user volume and usage in the early stage of the service, as well as the large amount of big data and high concurrency processing. As an essential component of new call services, it has strong foresight and sustainability.

[0050] Example 1: like Figure 2 The method for verifying file transfers during a call based on IMS DC, as shown, is based on multiple terminals, servers, and the VoNR+ media plane, including: In step S1, the first terminal preloads the mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The content sharing service server creates a data channel between the first terminal and the media plane and a data channel between the second terminal and the media plane.

[0051] Step S2: The first terminal sends shared content to the content sharing service server through the first terminal / media plane data channel. The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, or: Step S3: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0052] Steps S1 to S3 construct an IMS DC-based method for reviewing file transfers during calls. This method involves different terminals, a VoNR+ media plane, a content sharing service server, and a content moderation module working collaboratively. It enables secure file sharing and features flexible and configurable review and distribution strategies. Content to be reviewed can be reviewed before or after distribution, achieving effective security control over file transfers during calls. The technical solution provided in steps S1 to S3 integrates the content review function into the communication network layer, avoiding reliance on the terminal's own review function or third-party software, as is the case with existing technologies. Through the collaboration of the content sharing service server and the content moderation module, the network possesses the ability to proactively identify and process inappropriate content.

[0053] Step S1 establishes a data channel between the first and second terminals / media planes through the content sharing service server, forming a communication link between the server and the communication terminal and providing the foundation for communication interaction. Step S2 implements a "review before delivery" review mode based on the communication interaction foundation provided in Step S1. After receiving content transmitted from the first terminal via the first VoNR+ media plane, forwarding is paused, and the review module is actively requested to review it. Only after the review is passed will the content sharing service server call the instruction to send the shared content to the second terminal. The review before delivery mode prevents non-compliant shared content from reaching the second terminal.

[0054] Step S3 implements a "send first, review later" review mode based on the communication interaction provided in step S1. The shared content is delivered first, and the content review module still reviews it during the delivery process. If the review fails, the content sharing business server will trigger a withdrawal mechanism to notify the second terminal to delete the local file, thus realizing in-process and post-process remedies.

[0055] The two different review modes are determined by the file size. Smaller files (such as profile pictures) are reviewed before submission, while larger files (such as large images or video files) are submitted first and then reviewed. By tailoring different review modes to the specific content being shared, the system flexibly handles files with different characteristics, improving the efficiency of file review and preventing users from experiencing a negative impact due to the perceived need for file review.

[0056] Preferably, in step S1, the first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel, further including: In step S11, the first terminal initiates a call to the second terminal to establish a control channel for the bootloader and request the download of the bootloader. In this step, to ensure high-performance data transmission from end to end, network slicing technology is used to provide logically isolated network resources for the bootloader control channel.

[0057] Step S12: The first VoNR+ media plane acquires the guide applet and replies to the first terminal with a response to download the guide applet through the guide applet control channel.

[0058] In step S13, the first terminal requests to download the guide mini-program from the first VoNR+ media plane through the guide mini-program control channel. The first VoNR+ media plane generates a corresponding mini-program list and sends the response data back to the first terminal through the guide mini-program control channel. In this step, the first terminal requests to download the mini-program list from the first VoNR+ media plane through the guide mini-program control channel. The first VoNR+ media plane dynamically generates a personalized mini-program list based on real-time user attribute analysis, network status monitoring, and dynamic service policies, using real-time data stream processing technology, and sends the response data back to the first terminal through the guide mini-program control channel.

[0059] In step S14, the first terminal obtains the autoloaded mini-program from the mini-program list and sends a request to the first VoNR+ media plane to download the autoloaded mini-program through the mini-program guidance control channel. In this step, the first terminal determines and obtains the mini-program with the autoload attribute based on the mini-program list, and then requests and downloads the autoloaded mini-program from the first VoNR+ media plane through the mini-program guidance control channel. Autoload is a pre-loading function of the VoNR+ media plane. It can automatically download and execute the core enhanced service mini-programs in advance during the waiting stage before the call between the first and second terminals is connected, ensuring that all enhanced service functions can be "instantly activated" as soon as the communication connection between the first and second terminals is established, providing users with an experience of extremely fast loading of enhanced services.

[0060] In step S15, the second terminal accepts the call request from the first terminal, the called party answers the phone, a corresponding call channel is established, the first terminal updates the call interface, and the user of the first terminal uses the updated call interface to select the content sharing menu during the call.

[0061] During this process, the first terminal updates the call interface during the call, selects the content sharing menu in the call interface, and the guide applet running on the first terminal downloads the content sharing applet from the first VoNR+ media plane to the local machine according to the content sharing menu and runs it in the local applet runtime environment.

[0062] Step S16: The first terminal runs the guide applet and sends a command from the guide applet control channel to request the download of the content sharing applet from the first VoNR+ media plane to the local machine and run the content sharing applet.

[0063] In step S17, the content sharing mini-program initiates a re-INVITE renegotiation. The content sharing service server creates a data channel, which includes an end-to-end data channel for transmitting control messages, and a first terminal / media plane data channel and a second terminal / media plane data channel. The first and second terminal / media plane data channels are used to transmit data packets. In this step, the content sharing service server creates the data channel based on the type field of the label. The label is a key parameter carried in the re-INVITE message, used to precisely tell the network what type of channel needs to be created. The type field indicates the purpose of the channel; type="control" indicates a channel for transmitting control signaling, and type="video_stream" indicates a channel for transmitting video data.

[0064] Step S18: The first terminal initiates a call to the second terminal to establish a guide applet control channel and request the download of the guide applet. The step also includes: establishing a dedicated media data channel, which is used to provide specific enhanced services.

[0065] Steps S11 to S18 are further optimizations of step S1. In the optimized technical solutions provided in steps S11 to S18, an end-to-end data channel and a data channel between the first and second terminals / media plane are established by automatically loading the mini-program and using the re-INVITE renegotiation mechanism of the content sharing mini-program. This provides business logic (mini-program), control and review (content sharing business server), and media processing (under VoNR+ media plane), realizing data interaction and file sharing between the first and second terminals, and providing a communication channel and content sharing foundation for subsequent file review.

[0066] Preferably, in step S2, the first terminal sends sharing content to the content sharing service server through the first terminal / media plane data channel. The content sharing service server parses the sharing content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the sharing content to the second terminal through the second terminal / media plane data channel, further including: The content sharing service server obtains the shared content, requests review from the content review module, and the content review module completes the review and notifies the content sharing service server. If the content moderation module fails to review the shared content, the content sharing service server will terminate data forwarding and notify the first terminal that the review is complete. The first terminal may or may not display the review results from the shared content based on the preset operation strategy.

[0067] Step S2 employs a "review before release" review strategy. The content sharing service server receives the shared content from the first terminal, parses the bitstream of the shared content to obtain files such as photos and videos, and then requests review from the content review module. The content review module completes the security review and notifies the content sharing service server. If the content review module fails the review, it terminates data forwarding and notifies the first terminal of the review result. The first terminal's mini-program then decides whether to present the content to the user based on its operational strategy.

[0068] If the content review module approves the content, the content sharing service server calls the interface of the first VoNR+ media plane and sends the photos / videos to the second terminal through the ADC2 channel according to the custom assembly format of the mini-program.

[0069] Step S2 employs a "review before sending" review strategy, which enables proactive review and defense. The risks of shared content are eliminated through review at the sending end (first terminal), ensuring that non-compliant content cannot reach the recipient (second terminal). The content sharing service server is responsible for parsing the shared content and submitting it to the content review module. The content review module is responsible for reviewing the content and returning the results. The content sharing service server then takes corresponding actions based on the review results of the content review module, nipping any potential non-compliance in the bud.

[0070] Preferably, in step S3, the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. This further includes: Step S31: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel.

[0071] In step S32, the content sharing service server parses the content sharing bitstream to obtain the corresponding photos / videos, requests review from the content review module, reviews the shared content, and notifies the content sharing service server of the review result.

[0072] Step S33: If the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism. The first VoNR+ media surface identifies the non-compliant file withdrawal mechanism and sends a non-compliant file withdrawal request to the second terminal.

[0073] In step S34, the second terminal sends a successful receipt to the first VoNR+ media plane to withdraw the non-compliant document and deletes the local file.

[0074] Step S35: The content sharing service server notifies the first terminal of the file review failure result.

[0075] In step S36, after receiving the receipt from the second terminal, the first terminal requests the second terminal to withdraw the shared content.

[0076] In step S37, the second terminal receives the request to withdraw the shared content, sends a successful withdrawal receipt to the first terminal, the second terminal deletes the local file, and the first terminal deletes the local sending record.

[0077] The "review before release" review model provided in steps S31 to S37 can be summarized as follows: If the shared content is compliant, the content sharing service server calls the interface of the first VoNR+ media plane and sends the photos / videos to the second terminal through the second terminal / media plane data channel, according to the format uniformly stipulated by the network. If the shared content is non-compliant, then: The content sharing service server parses the bitstream to obtain photos / videos and requests review from the content review module. Once the content review module completes the review, it notifies the content sharing service server of the review result.

[0078] If the review fails, the content sharing service server will trigger the non-compliant file withdrawal mechanism to the first VoNR+ media plane, and the first VoNR+ media plane will send a non-compliant file withdrawal request to terminal B.

[0079] The second terminal sends a successful receipt to the first VONR+ media interface confirming the withdrawal of non-compliant documents and deletes the local files.

[0080] The content sharing service AS notifies the first terminal of the result of the file review failure.

[0081] Steps S31 to S37 are further optimizations of the "post-submission review" method in step S3. They trace and clean up non-compliant shared content that has already been forwarded. While ensuring a smooth call process, they provide a function for post-event review of shared content, achieving a balance between user experience and compliance review. They conduct silent review while prioritizing the immediacy of content sharing and user experience, and provide a mechanism for withdrawing non-compliant content sharing. While the vast majority of compliant content is distributed quickly, a few non-compliant contents can be remedied afterward.

[0082] Example 2: like Figure 3As shown, this application provides a method for reviewing file transfers during a call based on IMS DC for a first terminal. The difference from Embodiment 1 is that Embodiment 1 includes multiple implementing entities such as a first terminal, a second terminal, and a content sharing service server, while Embodiment 2 only describes the technical solution using the first terminal as the main entity. The method steps include: Step T1-1: The first terminal preloads the mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The first terminal requests the first VoNR+ media plane to download the content sharing mini-program through the guide mini-program control channel.

[0083] Step T1-2: The first terminal initiates a re-INVITE renegotiation with the second terminal through the content sharing applet, and sends the shared content to the first VoNR+ media plane through the first terminal / media plane data channel. The first terminal / media plane data channel is created by the content sharing service server.

[0084] Step T1-3: The first terminal obtains the review result of the shared content from the content review module. According to the preset operation strategy, the first terminal may or may not display the review result from the file, or: withdraw the shared content through the first terminal / media data channel.

[0085] Preferably, in step T1-1, the first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The first terminal requests the first VoNR+ media plane to download a content-sharing mini-program through the guiding mini-program control channel, further including: In step T1-11, the first terminal initiates a call to the second terminal to establish a control channel for the guide applet and request to download the guide applet.

[0086] T1-12, the first terminal receives a response from the first VoNR+ media plane to obtain the guide applet, and requests the first VoNR+ media plane to download the corresponding applet list through the guide applet control channel.

[0087] T1-13, the first terminal downloads a pre-loaded mini-program according to the mini-program list, initiates a call to the second terminal, and establishes a call channel with the second terminal.

[0088] T1-14, the first terminal updates the call interface during the call, selects the content sharing menu in the call interface, and sends a request through the guide applet control channel. The guide applet running on the first terminal downloads the content sharing applet from the first VoNR+ media plane to the local machine according to the content sharing menu and runs it in the local applet runtime environment.

[0089] T1-15, the first terminal sends a file through the content sharing applet and requests content sharing from the second terminal through the first terminal / media plane data channel.

[0090] Step T1-16: The first terminal obtains the review result from the content sharing service server. The review result is the review result sent by the content review module, or: the first terminal receives the receipt from the second terminal and requests the second terminal to withdraw the shared content. In step T1-17, the first terminal receives a successful withdrawal receipt from the second terminal and deletes the local transmission record.

[0091] Steps T1-1 to T1-3 (including steps T1-11 to T1-17) are essentially the same as those of steps S1 to S3, and the repeated content will not be repeated. However, it is worth noting that although the technical solutions provided in steps T1-1 to T1-3 only describe the first terminal and the second terminal, this does not mean that there is a limitation on the number of terminals or servers in this application embodiment. This specific embodiment uses the first and second terminals as examples to illustrate the technical solution only for the purpose of ease of understanding and convenience, and does not imply any limitation on the number of terminals.

[0092] Example 3: like Figure 4 As shown, this application embodiment provides a method for reviewing file transfers during a call based on IMS DC using a second terminal. The difference from Embodiments 1 and 2 is that this specific implementation is based on a second terminal, using the second terminal as the implementing entity. Embodiment 1 includes multiple implementing entities such as a first terminal, a second terminal, and a content sharing service server; Embodiment 2's implementing entity only includes the first terminal; while this embodiment's implementing entity only includes the second terminal. The specific method steps are as follows: In step T2-1, in response to the call from the first terminal, the second terminal establishes a call channel with the first terminal.

[0093] In step T2-2, the first terminal initiates a re-INVITE renegotiation, and the second terminal requests the download of the content sharing applet from the second VoNR+ media plane.

[0094] In step T2-3, if the content review module approves the content, the second terminal obtains the content sharing through the second terminal / media plane data channel, or the second terminal obtains the non-compliant file withdrawal request sent by the first VoNR+media plane.

[0095] Preferably, in step T2-3, if the content review module approves the content, the second terminal obtains the corresponding content sharing through the second terminal / media plane data channel. Specifically, if the content review module approves the content, the second terminal obtains the content sharing through the second terminal / media plane data channel. The content sharing is achieved by the content sharing service server calling the interface of the first VoNR+media plane and sending it to the second terminal through the second terminal / media plane data channel.

[0096] For example, the second terminal receiving the non-compliant document retraction request sent by the first VoNR+ media plane further includes: Step T2-31: The second terminal receives the successful retraction receipt of the non-compliant file sent from the first VoNR+ media plane, and deletes the local file, or: Step T2-32: The second terminal sends a receipt to the first terminal and receives a request from the first terminal to withdraw the shared content. Step T2-33: The second terminal sends a successful withdrawal receipt to the first terminal and deletes the local file.

[0097] Preferably, based on steps T2-1 to T2-3, the following may also be included: In step T2-4, the second terminal sends content sharing to the second VoNR+ media plane through the second terminal / media plane data channel. The content sharing service server reviews the content sharing and associates the first and second terminal / media plane data channels. The content sharing is then forwarded to the first terminal through the first terminal / media plane data channel.

[0098] In the technical solutions provided in steps T2-1 to T2-4, the second terminal, as the main implementer of the equipment, collaborates with the VoNR+ media plane and the first terminal through operations such as establishing channels, responding to renegotiation, and receiving / withdrawing content to jointly implement the method for verifying file transfers during a call. By cooperating with other main implementers of the equipment, the second terminal can respond to network commands, process end-to-end requests, and initiate service requests. The technical solutions provided in steps T2-1 to T2-4 are similar to those in embodiments one and two; repeated content will not be elaborated upon. However, it is worth noting that although only the first and second terminals are described in the technical solutions provided in steps T2-1 to T2-4, this does not imply a limitation on the number of terminals or servers in this application embodiment. This specific embodiment uses the first and second terminals as examples to illustrate the technical solutions only for ease of understanding and convenience, and does not imply any explicit or implicit limitation on the number of terminals.

[0099] Example 4: like Figure 5As shown, this application embodiment provides a method for reviewing file transfers during a call applied to a content sharing service server. The difference between this embodiment and other embodiments is that this embodiment uses a content sharing service server as the implementation subject and describes the embodiment from the perspective of the content sharing service server. The method steps include: Step V1: The content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel to obtain the sharing content sent by the first terminal.

[0100] Step V2: The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, or: Step V3: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0101] Preferably, in step V3, the content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. This further includes: Step V31: The content sharing service server obtains the shared content, requests review from the content review module, and the content review module completes the review and notifies the content sharing service server. In step V32, if the content review module fails to review the shared content, the content sharing service server terminates data forwarding and notifies the first terminal that the review is complete.

[0102] Step V33: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel; Step V34: The content sharing service server parses the content sharing bitstream to obtain the corresponding photos / videos, requests review from the content review module, reviews the shared content, and notifies the content sharing service server of the review result. Step V35: If the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism. The first VoNR+ media surface identifies the non-compliant file withdrawal mechanism and sends a non-compliant file withdrawal request to the second terminal. Step V36: The content sharing service server notifies the first terminal of the file review failure result.

[0103] The optimization technical solutions provided in steps V31 to V36 involve communication and interaction between the content sharing business server and the content review module, as well as the content review and withdrawal mechanism. In the specific review process, the review methods of "review before release" and "release before review" are also adopted.

[0104] In this embodiment, the content sharing service server acts as the execution entity. It dynamically selects and executes two strategies: "review before release" and "release before review." It also collaborates with the content review module, the first and second VoNR+ media surfaces, and the first and second terminals to achieve intelligent review and flexible configuration processing of the shared content.

[0105] In the "review before distribution" mode, the content sharing server waits for the review module's review result before instructing the first VoNR+ media plane to distribute the content. This mode is suitable for application scenarios with high compliance requirements. In the "distribute before review" mode, the content sharing server and VoNR+ media plane collaborate asynchronously. While initiating the distribution instruction, it simultaneously sends review requests to the content review module, allowing content distribution and review to be processed in parallel. This prioritizes a smooth user experience while providing a post-event retraction mechanism to ensure the compliance of shared content. Through these dual review modes, the content sharing server achieves an optimal balance between review procedures and transmission efficiency, meeting the differentiated needs of various application scenarios. It provides both preventative (review before distribution) and post-event retrospective retraction capabilities, ensuring the communication system's high efficiency, flexibility, security, and reliability.

[0106] However, it is worth noting that although the technical solutions provided in steps V1 to V3 (including steps V31 to V36) only describe one shared service server and two terminals (the first and second terminals), this does not mean that there is a limitation on the number of terminals or servers in this application embodiment. This specific embodiment uses a shared service server as an example to illustrate the technical solution only for the purpose of ease of understanding and convenience, and does not imply any limitation on the number of terminals.

[0107] like Figure 6 As shown, Figure 6 This includes the timing relationship between the first and second terminals, the content sharing service server, and the first and second VoNR+ media planes, through... Figure 6 It can be seen that the communication and interaction process between different terminals, servers and VoNR+ media plane will Figure 6 By combining this embodiment with Embodiments 1 and 4, the full picture of the technical solution of this application can be clearly seen. Figure 6 In the diagram, BDC0 is the control channel for the bootstrap mini-program (default / basic data channel, used for signaling, initial sessions, and low-priority data), BDC100 is the enhanced / dedicated data channel, used for high-priority data, high-quality media streams, or supplementary services, ADC1 is the first terminal / media plane data channel, and ADC2 is the second terminal / media plane data channel.

[0108] like Figure 7 The content review process shown involves the content sharing service server sending the file content to be reviewed to the data acquisition module. The data acquisition module then obtains the file content corresponding to the content review request. For video files, it calls the video stream frame capture interface to output image / video frames.

[0109] The region identification module uses computer vision technology to perform semantic segmentation on image / video frames. It uses a convolutional neural network architecture to identify whether a region is a concentrated area of ​​sensitive elements. If so, the file content is sent to the violation location module; otherwise, the process returns to the region identification module for retry or is marked as unrecognizable.

[0110] The violation location module uses a violation type probability matrix, including sub-items such as political sensitivity, pornography index, and violent tendency, to score each attention area for violation. Based on a preset threshold, it filters out target violation areas and sends the violation image dataset to the result generation module for result determination.

[0111] The results generation module calls visual feature, text feature, and spatiotemporal feature extraction interfaces to extract features of the violation area. A multi-level classifier is used, including primary classification for coarse-grained filtering, secondary classification for fine-grained identification, and a final decision method for violation determination, ultimately outputting the review result. If the review passes: the machine review result is returned to the content sharing business server; if the review fails: the content of the file to be reviewed is sent to the human review module.

[0112] Manually review image / video content and notify the content sharing server of the review results.

[0113] like Figure 8As shown, this application embodiment, based on the IMS DC-based in-call file transfer verification method, also provides a corresponding IMS DC-based in-call file transfer verification system, used to implement the IMS DC-based in-call file transfer verification method described in any one of the embodiments of this application, including: The terminal / media plane data channel construction module establishes a call channel with the second terminal by preloading a mini-program through the first VoNR+ media plane and initiating a call. The content sharing service server creates the first terminal / media plane data channel and the second terminal / media plane data channel. The content sharing module requires a pre-review before delivery. The first terminal sends the shared content to the content sharing service server via the first terminal / media plane data channel. The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+media plane to send the shared content to the second terminal via the second terminal / media plane data channel, or: The content sharing module involves sending and reviewing content first. The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

[0114] like Figure 9 As shown, this application embodiment, in addition to providing a method and system for reviewing file transfers during a call based on IMS DC, also provides corresponding electronic devices and storage media: An electronic device includes: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the method described in any specific embodiment.

[0115] A computer-readable storage medium stores a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of the method described in any specific embodiment of the present application.

[0116] Explanation of reference numerals in the attached drawings: Electronic device 500, External device 514, Processor 516, Bus 518, Network adapter 520, I / O interface 522, Display device 524, Memory 528, RAM 530, Cache 532, Storage system 534, Program / Utility 540, Program module 542.

[0117] Figure 9The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this application. Typically, this electronic device could be a device within an electronic product based on the call file transfer verification method described above. The electronic device 500 is represented as a general-purpose computing device. Components of the electronic device 500 may include, but are not limited to: one or more processing units or processors 516, a memory 528, and a bus 518 connecting different system components (including the memory 528 and the processor 516). The bus 518 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus. The electronic device 500 typically includes various computer system readable media. These media can be any available media accessible to the electronic device 500, including volatile and non-volatile media, removable and non-removable media. Memory 528 may include computer system readable media in the form of volatile memory, such as RAM 530 and / or cache 532. Electronic device 500 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 534 may be used to read and write non-removable, non-volatile magnetic media (not shown in the figure, commonly referred to as "hard disk drives"). Although not shown in the figure, storage system 534 may provide disk drives for reading and writing to removable non-volatile disks (e.g., floppy disks, portable hard disks, hot-swappable storage media) and optical disk drives for reading and writing to removable non-volatile optical disks (e.g., CD-ROMs, DVD-ROMs, or other optical media). In these cases, each drive may be connected to bus 518 via one or more data media interfaces. Memory 528 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of various specific embodiments of the present application. A program / utility 540 having a set (at least one) of program modules 542 may be stored, for example, in memory 528. Such program modules 542 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 542 typically perform the functions and / or methods described in the embodiments of this application.Electronic device 500 can also communicate with one or more external devices 514 (e.g., keyboard, pointing device, display device 524, etc.), and with one or more devices that enable a user to interact with electronic device 500, and / or with any device that enables electronic device 500 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed through I / O interface 522. Furthermore, electronic device 500 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 520. Network adapter 520 communicates with other modules of electronic device 500 via bus 518. It should be understood that, although not shown in the figures, those skilled in the art can use other hardware and / or software modules in conjunction with electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems. Processor 516 executes various functional applications and data processing by running programs stored in memory 528, such as implementing the methods provided in any one or more embodiments of this application.

[0118] In the description of the embodiments of this application, the reference to terms such as "an embodiment," "example," "specific example," etc., means that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the embodiments of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0119] Furthermore, the technical solutions of the various implementation methods in this application can be combined with each other, but only if they are based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the embodiments of this application.

[0120] All features disclosed in the embodiments of this application, or all steps in the disclosed methods or processes, may be combined in any way, except for mutually exclusive features and / or steps. Any feature disclosed in the specification of the embodiments of this application, unless specifically stated otherwise, may be replaced by other equivalent or similar alternative features. That is, unless specifically stated otherwise, each feature is merely one example of a series of equivalent or similar features. Throughout the specification, the same reference numerals indicate the same elements.

[0121] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification of embodiments (including the corresponding claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification of embodiments (including the corresponding claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0122] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of this application, and are not intended to limit them. Although the embodiments of this application have been described in detail with reference to the foregoing specific embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing specific embodiments, or equivalent substitutions can be made to some or all of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the specific embodiments of this application.

Claims

1. A method for verifying file transfers during a call based on IMS DC, comprising multiple terminals, a server, and a VoNR+ media plane, characterized in that, include: The first terminal preloads the mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The content sharing service server creates a data channel between the first terminal and the media plane and a data channel between the second terminal and the media plane. The first terminal sends shared content to the content sharing service server through the first terminal / media plane data channel. The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, or: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

2. The method for verifying file transfers during a call based on IMS DC according to claim 1, characterized in that, The first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel, further including: The first terminal initiates a call to the second terminal, establishes a control channel for the guide applet, and requests the download of the guide applet. The first VoNR+ media plane obtains the guide applet and replies to the first terminal with a response to download the guide applet through the guide applet control channel; The first terminal requests the download of the guide mini-program from the first VoNR+ media plane through the guide mini-program control channel. The first VoNR+ media plane generates a corresponding mini-program list and sends the response data back to the first terminal through the guide mini-program control channel. The first terminal obtains the automatically loaded mini-program through the mini-program list and sends a request to the first VoNR+ media plane to download the automatically loaded mini-program through the mini-program control channel. The second terminal accepts the call request from the first terminal, establishes a corresponding call channel, and the first terminal updates the call interface. The first terminal runs the guide applet and sends a command from the guide applet control channel to request the download of the content sharing applet from the first VoNR+ media plane to the local machine and run the content sharing applet.

3. The method for verifying file transfers during a call based on IMS DC according to claim 2, characterized in that, Also includes: The content sharing mini-program initiates a re-INVITE renegotiation, and the content sharing service server creates a data channel. The data channel includes an end-to-end data channel for transmitting control messages, as well as a first terminal / media plane data channel and a second terminal / media plane data channel. The first and second terminal / media plane data channels are used to transmit data packets. The first terminal initiates a call to the second terminal to establish a guide applet control channel and request the download of the guide applet. The process also includes: establishing a dedicated media data channel, which is used to provide specific enhanced services.

4. The method for verifying file transfers during a call based on IMS DC according to claim 3, characterized in that, The second terminal accepts the call request from the first terminal, establishes a corresponding call channel, and the first terminal updates the call interface, specifically as follows: During a call, the first terminal updates the call interface and selects the content sharing menu. The guide applet running on the first terminal downloads the content sharing applet from the first VoNR+ media plane to the local device according to the content sharing menu and runs it in the local applet runtime environment.

5. The method for verifying file transfers during a call based on IMS DC according to claim 1, characterized in that, The first terminal sends sharing content to the content sharing service server through the first terminal / media plane data channel. The content sharing service server parses the sharing content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review is successful, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, further including: The content sharing service server obtains the shared content, requests review from the content review module, and the content review module completes the review and notifies the content sharing service server. If the content moderation module fails to review the shared content, the content sharing service server will terminate data forwarding and notify the first terminal that the review is complete. The first terminal may or may not display the review results from the shared content based on the preset operation strategy.

6. The method for verifying file transfers during a call based on IMS DC according to claim 1, characterized in that, The content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. Further, this includes: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel; The content sharing service server parses the content sharing bitstream to obtain the corresponding photos / videos, requests review from the content review module, and the content review module reviews the shared content and notifies the content sharing service server of the review result. If the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism. The first VoNR+ media plane identifies the non-compliant file withdrawal mechanism and sends a non-compliant file withdrawal request to the second terminal. The second terminal sends a successful receipt to the first VoNR+ media interface to retract the non-compliant document and deletes the local file; The content sharing service server notifies the first terminal of the file review failure result.

7. The method for verifying file transfers during a call based on IMS DC according to claim 6, characterized in that, Also includes: After receiving the receipt from the second terminal, the first terminal requests the second terminal to withdraw the shared content. The second terminal receives the request to withdraw the shared content, sends a successful withdrawal receipt to the first terminal, deletes the local file on the second terminal, and deletes the local sending record on the first terminal.

8. A method for verifying file transfers during a call based on IMS DC, applied to a first terminal, characterized in that, include: The first terminal preloads the mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The first terminal requests the first VoNR+ media plane to download the content sharing mini-program through the mini-program control channel. The first terminal initiates a re-INVITE renegotiation to the second terminal through the content sharing applet, and sends the shared content to the first VoNR+ media plane through the first terminal / media plane data channel. The first terminal / media plane data channel is created by the content sharing service server. The first terminal receives the review results of the shared content from the content review module. Based on the preset operation strategy, the first terminal may or may not display the review results from the document, or: withdraw the shared content through the first terminal / media data channel.

9. The method for verifying file transfer during a call based on IMS DC according to claim 8, applied to a first terminal, characterized in that, The first terminal preloads a mini-program through the first VoNR+ media plane and initiates a call to establish a call channel with the second terminal. The first terminal requests the first VoNR+ media plane to download a content-sharing mini-program through the mini-program control channel, further including: The first terminal initiates a call to the second terminal, establishes a control channel for the guide applet, and requests the download of the guide applet. The first terminal receives a response from the first VoNR+ media plane to obtain the guide applet, and requests the first VoNR+ media plane to download the corresponding applet list through the guide applet control channel; The first terminal downloads pre-loaded mini-programs according to the mini-program list, initiates a call to the second terminal, and establishes a call channel with the second terminal; During a call, the first terminal updates the call interface, selects the content sharing menu in the call interface, and sends a request through the guide mini-program control channel. The guide mini-program running on the first terminal downloads the content sharing mini-program from the first VoNR+ media plane to the local device according to the content sharing menu and runs it in the local mini-program runtime environment. The first terminal sends a file through the content sharing mini-program and requests content sharing from the second terminal through the first terminal / media plane data channel.

10. The method for verifying file transfer during a call based on IMS DC according to claim 9, characterized in that, Also includes: The first terminal obtains the review result from the content sharing service server, wherein the review result is the review result sent by the content review module, or: The first terminal receives the receipt from the second terminal and requests the second terminal to withdraw the shared content; The first terminal receives a successful withdrawal receipt from the second terminal and deletes the local sending record.

11. A method for verifying file transfers during a call based on IMS DC, applied to a second terminal, characterized in that, include: In response to a call from the first terminal, the second terminal establishes a call channel with the first terminal; The second terminal requests the download of the content sharing mini-program from the second VoNR+ media plane after receiving the re-INVITE renegotiation initiated by the first terminal. If the content review module approves the content, the second terminal obtains the corresponding content sharing through the second terminal / media plane data channel, or the second terminal obtains the non-compliant file withdrawal request sent by the first VoNR+media plane.

12. The method for verifying file transfer during a call based on IMS DC according to claim 11, characterized in that: If the content review module approves the content, the second terminal obtains the corresponding content sharing through the second terminal / media data channel, specifically: Once the content review module approves the content, the second terminal obtains the shared content through the second terminal / media plane data channel. The shared content is obtained by the content sharing service server calling the interface of the first VoNR+media plane and sending it to the second terminal through the second terminal / media plane data channel.

13. The method for verifying file transfers during a call based on IMS DC according to claim 11, characterized in that, The second terminal receives the non-compliant document retraction request sent by the first VoNR+ media plane, further including: The second terminal receives a successful receipt from the first VoNR+ media plane confirming the withdrawal of non-compliant files, and deletes the local file, or: The second terminal sends a receipt to the first terminal and receives a request from the first terminal to withdraw the shared content. The second terminal sends a successful withdrawal receipt to the first terminal and deletes the local file.

14. The method for verifying file transfers during a call based on IMS DC according to claim 11, characterized in that, Also includes: The second terminal sends content sharing to the second VoNR+ media plane through the second terminal / media plane data channel. The content sharing service server reviews the content sharing and associates the first and second terminal / media plane data channels. The content sharing is then forwarded to the first terminal through the first terminal / media plane data channel.

15. A method for reviewing file transfers during a call based on IMS DC, applied to a content sharing service server, characterized in that... include: The content sharing service server creates a first terminal / media plane data channel and a second terminal / media plane data channel to obtain the shared content sent by the first terminal; The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel, or: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

16. The method for verifying file transfers during a call based on IMS DC according to claim 15, characterized in that, The content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. Further, this includes: The content sharing service server obtains the shared content, requests review from the content review module, and the content review module completes the review and notifies the content sharing service server. If the content moderation module fails to review the shared content, the content sharing service server will terminate data forwarding and notify the first terminal that the review is complete.

17. The method for verifying file transfers during a call based on IMS DC according to claim 15, characterized in that, The content sharing service server calls the interface of the first VoNR+ media plane to send the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result. Further, this includes: The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel; The content sharing service server parses the content sharing bitstream to obtain the corresponding photos / videos, requests review from the content review module, and the content review module reviews the shared content and notifies the content sharing service server of the review result. If the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism. The first VoNR+ media plane identifies the non-compliant file withdrawal mechanism and sends a non-compliant file withdrawal request to the second terminal. The content sharing service server notifies the first terminal of the file review failure result.

18. A call-based file transfer verification system based on IMS DC, used to implement the call-based file transfer verification method based on IMS DC as described in any one of claims 1 to 17, characterized in that, include: The terminal / media plane data channel construction module establishes a call channel with the second terminal by preloading a mini-program through the first VoNR+ media plane and initiating a call. The content sharing service server creates the first terminal / media plane data channel and the second terminal / media plane data channel. The content sharing module requires a pre-review before delivery. The first terminal sends the shared content to the content sharing service server via the first terminal / media plane data channel. The content sharing service server parses the shared content and requests review from the content review module. If the review fails, the content sharing service server terminates data forwarding and notifies the first terminal of the review result. If the review succeeds, the content sharing service server calls the first VoNR+media plane to send the shared content to the second terminal via the second terminal / media plane data channel, or: The content sharing module involves sending and reviewing content first. The content sharing service server calls the interface of the first VoNR+ media plane and sends the shared content to the second terminal through the second terminal / media plane data channel. The content review module reviews the shared content and notifies the content sharing service server of the review result. Alternatively, if the review fails, the content sharing service server triggers the non-compliant file withdrawal mechanism, the second terminal deletes the local file, and the content sharing service server notifies the first terminal of the file review failure result.

19. An electronic device, characterized in that, include: The system includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 17.

Images