Terminal communication method, apparatus and system, computer device, and readable storage medium

Abstract

The present application relates to a terminal communication method, apparatus and system, a computer device, a computer-readable storage medium, and a computer program product. The method comprises: when there is a requirement to send file data to a second terminal, if the second terminal does not support an IP multimedia subsystem (IMS) standalone data channel, sending target data to a media processing function entity by means of an application data channel (ADC) established with a local network, so as to forward the target data to a data channel application server by means of the media processing function entity, wherein the media processing function entity comprises at least one of a media function (MF) and a media resource function (MRF), the target data comprises the file data and identification information of the second terminal, and the target data is used for instructing the data channel application server to send a hyperlink to the second terminal after the hyperlink is generated from the file data.

Description

Terminal communication methods, devices, systems, computer equipment, and readable storage media

[0001] Related applications

[0002] This application claims priority to Chinese patent application filed on March 26, 2025, with application number 2025103663508, entitled "Terminal Communication Method, Apparatus, System, Computer Equipment and Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a terminal communication method, apparatus, system, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0004] With the continuous evolution of communication technologies, communication based on IMS standalone DC (IP Multimedia Subsystem Standalone Data Channel) has become a key direction for the future development of IMSDC (IP Multimedia Subsystem Data Channel) sessions. Currently, the 3GPP (3rd Generation Partnership Project) quasi-organization has made significant progress in this field, having basically established the network element architecture for IMS standalone DC sessions and constructed corresponding basic processes. Simultaneously, it has formulated a series of detailed standards and specifications, laying the foundation for the development of communication based on IMS standalone DC.

[0005] However, it cannot be ignored that a large number of conventional terminals in traditional communication environments do not support standalone DC. In actual communication scenarios, the interoperability problem between these conventional terminals and terminals supporting standalone DC has not yet been properly resolved, and there is still a lack of practical and effective interoperability solutions. For example, when a terminal supporting standalone DC wants to send a file to a conventional terminal using the DC channel, the conventional terminal cannot directly receive the file through the standalone DC channel because it does not support standalone DC. This severely hinders smooth communication between the two types of terminals and limits the application and popularization of IMS standalone DC technology in a wider range of communication scenarios. Summary of the Invention

[0006] This application provides a terminal communication method, apparatus, system, computer equipment, computer-readable storage medium, and computer program product for terminal communication.

[0007] In a first aspect, this application provides a terminal communication system, which includes a first terminal, a second terminal, a media processing function entity, and a data channel application server. The first terminal supports the IP Multimedia Subsystem (IMS) independent data channel, while the second terminal does not support the IMS independent data channel. The media processing function entity includes at least one of Media Function (MF) and Media Resource Function (MRF).

[0008] The first terminal is used to send target data to the media processing function entity through the application data channel (ADC) established with the local network when there is a need to send file data to the second terminal. The target data includes the file data and the identification information of the second terminal.

[0009] The media processing function entity is used to forward the target data to the data channel application server;

[0010] The data channel application server is used to generate hyperlinks based on the file data and send the hyperlinks to the second terminal based on the identification information of the second terminal.

[0011] The second terminal is used to obtain the file data from the data channel application server based on the hyperlink.

[0012] In one embodiment, the terminal communication system further includes an IMS core network and an IMS application server.

[0013] The IMS core network is used to send signaling for establishing an ADC to the IMS application server based on the ADC establishment request sent by the first terminal.

[0014] The IMS application server is used to forward the signaling to the peer network. The signaling is used to instruct the peer network to negotiate with the second terminal and to provide feedback on the response information in response to the signaling. The response information only carries the bootstrap data channel (BDC) information.

[0015] The IMS application server is also used to forward the response information fed back by the peer network to the IMS core network;

[0016] The IMS core network is also used to add ADC information to the response information and send the response information with added ADC information to the first terminal. The response information with added ADC information is used to indicate that the ADC connection between the first terminal and the local network is complete.

[0017] In one embodiment, before the first terminal sends the target data to the media processing function entity through the application data channel ADC established with the local network, it is also used to encrypt the file data to obtain encrypted file data; the target data also includes the decryption key corresponding to the encrypted file data;

[0018] After the second terminal obtains the encrypted file data from the data channel application server based on the hyperlink, it decrypts the encrypted file data based on the decryption key to obtain the file data.

[0019] Secondly, this application also provides a terminal communication method applied to a first terminal, the method comprising:

[0020] When there is a need to send file data to a second terminal, if the second terminal does not support the IP Multimedia Subsystem (IMS) independent data channel, the target data is sent to the media processing function entity through the application data channel (ADC) established with the local network, so that the target data is forwarded to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0021] The target data includes the file data and the identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

[0022] In one embodiment, if the second terminal does not support the IMS independent data channel, then sending the target data to the media processing function entity through the ADC established with the local network includes:

[0023] Send an ADC establishment request to the IMS core network. The ADC establishment request carries a first identifier, which is used to indicate the end-to-end ADC.

[0024] Receive response information sent by the IMS core network, the response information carrying a second identifier, the second identifier being used to indicate the end-to-platform ADC;

[0025] In response to the response information, target data is sent to the media processing function entity via the ADC established with the local network.

[0026] In one embodiment, before sending the target data to the media processing function entity via the application data channel ADC established with the local network, the method further includes:

[0027] The file data is encrypted to obtain encrypted file data;

[0028] The target data also includes a decryption key corresponding to the encrypted file data. The decryption key is used by the second terminal to decrypt the encrypted file data after obtaining it from the data channel application server via the hyperlink, in order to obtain the file data.

[0029] Thirdly, this application also provides a terminal communication method applied to a data channel application server, the method comprising:

[0030] The system receives target data sent by a media processing function entity. The target data is data sent by the first terminal to the media processing function entity through the application data channel (ADC) established with the local network when the second terminal does not support the IMS independent data channel. The target data includes file data and the identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0031] A hyperlink is generated based on the file data, and the hyperlink is sent to the second terminal based on the identification information of the second terminal.

[0032] Fourthly, this application also provides a terminal communication method applied to a second terminal, the second terminal not supporting the IP Multimedia Subsystem (IMS) independent data channel, the method comprising:

[0033] The system receives a hyperlink sent by a data channel application server. The hyperlink is generated based on file data, which is carried in target data forwarded by a media processing function entity to the data channel application server. The target data is sent by a first terminal to the media processing function entity through an application data channel (ADC) established with its local network. The target data includes the file data and the identification information of the second terminal. The first terminal supports IMS independent data channels. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0034] The file data is obtained from the data channel application server based on the hyperlink.

[0035] In one embodiment, the target data further includes a decryption key corresponding to the encrypted file data; the encrypted file data is obtained by the first terminal encrypting the file data; after receiving the hyperlink sent by the data channel application server, the method further includes:

[0036] After obtaining the encrypted file data from the data channel application server via the hyperlink, the encrypted file data is decrypted using the decryption key to obtain the file data.

[0037] Fifthly, this application also provides a terminal communication device for use in a first terminal, the device comprising:

[0038] The sending module is used to send target data to the media processing function entity through the application data channel ADC established with the local network when there is a need to send file data to the second terminal. If the second terminal does not support the IP Multimedia Subsystem IMS independent data channel, the target data is sent to the media processing function entity to forward the target data to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function MF and media resource function MRF.

[0039] The target data includes the file data and the identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

[0040] In one embodiment, the sending module is specifically used for:

[0041] Send an ADC establishment request to the IMS core network. The ADC establishment request carries a first identifier, which is used to indicate the end-to-end ADC.

[0042] Receive response information sent by the IMS core network, the response information carrying a second identifier, the second identifier being used to indicate the end-to-platform ADC;

[0043] In response to the response information, target data is sent to the media processing function entity via the ADC established with the local network.

[0044] Sixthly, this application also provides a terminal communication device applied to a data channel application server, the device comprising:

[0045] A receiving module is used to receive target data sent by a media processing function entity. The target data is data sent by the first terminal to the media processing function entity through an application data channel (ADC) established with the local network when the second terminal does not support an IMS independent data channel. The target data includes file data and identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0046] The sending module is used to generate a hyperlink based on the file data and send the hyperlink to the second terminal based on the identification information of the second terminal.

[0047] Seventhly, this application also provides a terminal communication device for a second terminal, the second terminal not supporting the IP Multimedia Subsystem (IMS) independent data channel, the device comprising:

[0048] A receiving module is used to receive a hyperlink sent by a data channel application server. The hyperlink is generated based on file data, which is carried in target data forwarded by a media processing function entity to the data channel application server. The target data is sent by a first terminal to the media processing function entity through an application data channel (ADC) established with its local network. The target data includes the file data and the identification information of the second terminal. The first terminal supports an IMS independent data channel. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0049] The acquisition module is used to acquire the file data from the data channel application server based on the hyperlink.

[0050] Eighthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement any of the above-mentioned terminal communication methods.

[0051] Ninthly, this application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the above-mentioned terminal communication methods.

[0052] In a tenth aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the above-mentioned terminal communication methods. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0054] Figure 1 is a schematic diagram of the structure of a terminal communication system in one embodiment of this application;

[0055] Figure 2 is a schematic diagram of signaling interaction of a terminal communication method in one embodiment of this application;

[0056] Figure 3 is a flowchart illustrating a terminal communication method in another embodiment of this application;

[0057] Figure 4 is a flowchart of step 302 in another embodiment of this application;

[0058] Figure 5 is a flowchart illustrating a terminal communication method in another embodiment of this application;

[0059] Figure 6 is a flowchart illustrating a terminal communication method in another embodiment of this application;

[0060] Figure 7 is a structural block diagram of a terminal communication device in one embodiment of this application;

[0061] Figure 8 is a structural block diagram of a terminal communication device in another embodiment of this application;

[0062] Figure 9 is a structural block diagram of a terminal communication device in another embodiment of this application;

[0063] Figure 10 is an internal structural diagram of a computer device in one embodiment of this application. Detailed Implementation

[0064] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0065] To better understand the embodiments of this application, the following explanations of terms will be provided before introducing the embodiments:

[0066] IMS (IP Multimedia Subsystem) is a multimedia service based on IP networks. It uses SIP as the call control protocol, separating call control from service control and enhancing multimedia support capabilities. It aims to provide end-users with a more novel and diverse multimedia service experience through IP networks. SIP (Session Initiation Protocol) is a multimedia communication protocol developed by the IETF (Internet Engineering Task Force). It is a text-based application layer control protocol used to create, modify, and release sessions of one or more participants, featuring flexibility, ease of implementation, and scalability.

[0067] DC (Data Channel): IMSDC is an extension of the IMS multimedia telephony service that allows arbitrary content to be transmitted between two endpoints that support a data channel during an ongoing active session.

[0068] IMS standalone DC: Refers to an IMS data channel independent of the IMS voice and video channels. The establishment of an IMS standalone DC session can be independent of the establishment of an IMS voice or video session. The terminal obtains the application list and downloads applications through BDC (Batch Data Communication), and then transmits application data and real-time interactive dynamic business data through ADC (Application Data Channel).

[0069] A standalone DC terminal refers to a terminal device that supports IMS standalone DC in a specific communication system, while a regular terminal refers to a terminal device that does not support IMS standalone DC in a specific communication system.

[0070] MF (Media Function) / MRF (Media Resource Function) is mainly responsible for handling media-related functions, such as the transmission, processing, and conversion of media streams, as well as the allocation and management of media resources, in order to support the development of various multimedia services.

[0071] The IMS core network, also known as IMS Core (IP Multimedia Subsystem Core), is the core component of IMS, a multimedia service control architecture based on IP networks. It is responsible for handling various signaling, session control, user authentication and authorization functions, and provides core support for multimedia services.

[0072] The IMS application server, also known as IMS AS (IP Multimedia Subsystem Application Server IP), is an application layer entity located in the IMS network. It is mainly responsible for providing various value-added services and application logic. It controls and manages multimedia sessions by interacting with the IMS Core, providing users with a rich variety of multimedia application services.

[0073] DCSF (Data Channel Selection Function) is responsible for determining the channel control strategy used for data transmission in a communication system. Based on factors such as network conditions and user needs, it selects a suitable data channel for data transmission to optimize data transmission performance and efficiency.

[0074] DC Application Server (Data Channel Application Server), also known as IMS Data Channel Application Server, is a server in the IMS network architecture responsible for handling business logic based on data channels.

[0075] In an exemplary embodiment, as shown in FIG1, a terminal communication system is provided, which includes a first terminal 102, a second terminal 104, a media processing function entity 106, and a data channel application server 108. The first terminal supports the IP Multimedia Subsystem (IMS) independent data channel, while the second terminal does not support the IMS independent data channel.

[0076] The first terminal 102 is used to send target data to the media processing function entity 106 through the application data channel ADC established with the local network when there is a need to send file data to the second terminal 104. The target data includes file data and identification information of the second terminal 104.

[0077] Media processing function entity 106 is used to forward target data to data channel application server 108;

[0078] The data channel application server 108 is used to generate hyperlinks based on file data and send the hyperlinks to the second terminal 104 based on the identification information of the second terminal.

[0079] The second terminal 104 is used to obtain file data from the data channel application server 108 via a hyperlink.

[0080] In this embodiment, the first terminal is a standalone DC terminal that supports IMS standalone DC, and the second terminal is a conventional terminal that does not support IMS standalone DC. When the first terminal 102 needs to send file data to the second terminal 104, the first terminal 102 first confirms that it has established an ADC with its local network. This ADC is an adaptive data channel established under the IMS network architecture to meet specific data transmission requirements.

[0081] The first terminal 102 organizes and encapsulates the file data to be sent, and adds the identification information of the second terminal 104 to the data to be sent. This identification information can be a unique identifier for the second terminal 104 in the communication network, such as IMSI (International Mobile Subscriber Identity) or other similar encoded information that can be used to accurately locate the terminal.

[0082] Subsequently, the first terminal 102 sends target data containing file data and the identification information of the second terminal 104 to the media processing function entity 106 via the established ADC. During the transmission process, the first terminal 102 follows the ADC's data transmission protocol to ensure the integrity and accuracy of the data, while also performing necessary encryption processing to ensure the security of the data during transmission.

[0083] In some embodiments, before the first terminal 102 sends the target data to the media processing function entity through the application data channel ADC established with the local network, it is further configured to: encrypt the file data to obtain encrypted file data; the target data also includes a decryption key corresponding to the encrypted file data, which is used by the second terminal to decrypt the encrypted file data after obtaining it from the data channel application server via a hyperlink to obtain the file data.

[0084] After receiving the target data sent by the first terminal 102, the media processing function entity 106 performs preliminary parsing and verification of the data. Verification includes checking whether the data format meets system requirements, verifying data integrity, and checking the legitimacy of the source. If the verification passes, the media processing function entity 106 forwards the target data to the data channel application server 108 according to the system's preset routing rules and data forwarding strategy. During the forwarding process, the media processing function entity 106 ensures reliable data transmission by employing appropriate caching and retransmission mechanisms to prevent data loss or corruption.

[0085] After receiving the target data forwarded by the media processing function entity 106, the data center application server 108 extracts the file data from the target data. Based on the characteristics and attributes of the file data, the data center application server 108 generates a corresponding hyperlink. This hyperlink is a network address identifier that can be used to access and retrieve file data. Its generation algorithm ensures the uniqueness and validity of the hyperlink. In this embodiment, the hyperlink generation algorithm is not specifically limited.

[0086] The data center application server 108 extracts the identification information of the second terminal 104 from the target data and determines the communication address of the second terminal 104 based on this identification information. For example, if the second terminal 104 is a mobile terminal, the data center application server 108 can query the corresponding mobile phone number or SMS access address based on its IMSI information. Then, the data center application server 108 sends the generated hyperlink to the second terminal 104 through a suitable communication method, such as an SMS gateway or other message push platform. When sending the hyperlink, the data center application server 108 ensures the accuracy of the hyperlink information and can log the sending process for subsequent querying and tracing.

[0087] After receiving a hyperlink from the data center application server 108, the user of the second terminal 104 can trigger a file retrieval operation by clicking the hyperlink. For example, the second terminal 104 can initiate a file data retrieval request to the data center application server 108 based on the network address pointed to by the hyperlink. During the request process, the second terminal 104 follows the file access protocols supported by the data center application server 108, such as HTTP (Hypertext Transfer Protocol) or FTP (File Transfer Protocol). After receiving the file retrieval request from the second terminal 104, the data center application server 108 verifies the legality of the request and the validity of the hyperlink. If the verification is successful, the data center application server 108 can send the stored file data to the second terminal 104 in chunks or as a whole, according to the requirements of the request protocol.

[0088] During the process of receiving file data, the second terminal 104 can also display the download progress of the file in real time and perform integrity verification on the received data. Once the file data reception is complete and the verification is successful, the second terminal 104 stores the file in a designated local storage location, completing the file data acquisition process.

[0089] The terminal communication system provided in this application embodiment, in a terminal communication scenario where the second terminal is a conventional terminal that does not support IMS standalone DC, while the first terminal is a standalone DC terminal that supports IMS standalone DC, forwards the file data to be sent to the data channel application server through the media processing function entity. Subsequently, the data channel application server generates a corresponding hyperlink based on the received file data and sends the hyperlink to the second terminal. After receiving the hyperlink, the second terminal can obtain the file data from the data channel application server based on the hyperlink. That is, the terminal communication system provided in this application embodiment successfully breaks down the communication barrier between conventional terminals and standalone DC terminals, effectively realizing communication interaction between the two, providing strong solution support for the further promotion and application of IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0090] In an exemplary embodiment, the terminal communication system may further include an IMS core network and an IMS application server, wherein:

[0091] The IMS core network is used to send signaling for establishing an ADC to the IMS application server based on the ADC establishment request sent by the first terminal.

[0092] The IMS application server is used to forward signaling to the peer network. This signaling is used to instruct the peer network to negotiate with the second terminal and to provide feedback on the response information to the signaling. The response information only carries the bootstrap data channel (BDC) information.

[0093] The IMS application server is also used to forward response information from the peer network to the IMS core network;

[0094] The IMS core network is also used to add ADC information to the response information and send the response information with added ADC information to the first terminal. The response information with added ADC information is used to indicate that the first terminal has completed the ADC connection with the local network.

[0095] In this embodiment, after the first terminal 102 obtains the application list and downloads the application through the BDC, it can send an ADC establishment request to the IMS core network in response to a trigger for a specific application. After receiving the ADC establishment request, the IMS core network generates signaling (e.g., INVITE signaling) for establishing the ADC based on the request content. This signaling includes relevant information of the first terminal 102, the characteristic parameters of the requested ADC, and key data such as the session identifier associated with this communication.

[0096] The IMS core network sends the generated signaling to the IMS application server. The IMS application server is responsible for forwarding this signaling to the peer network, which instructs the peer network to negotiate with the second terminal 104. Since the second terminal 104 is a conventional terminal that does not support the IMS independent data channel, the response information sent back to the IMS application server after completing the negotiation only carries the bootstrap data channel (BDC) information. After receiving the response information, the IMS application server forwards it to the IMS core network.

[0097] After receiving the response containing only BDC information forwarded by the IMS application server, the IMS core network adds ADC information related to the local network of the first terminal 102 to the response information. This information includes the specific parameters of the ADC allocated to the first terminal 102 by the local network, such as channel bandwidth, data transmission format, access key, etc., as well as an identifier indicating that the established ADC is an end-to-platform ADC. After adding the information, the IMS core network sends a response message with the added ADC information to the first terminal 102, which indicates that the ADC connection between the first terminal 102 and the local network is complete.

[0098] In this way, the first terminal 102 can send the file data to be sent to the second terminal 104 to the media processing function entity through the ADC established with the local network, so that the media processing function entity can forward the file data to the data channel application server 108, the data channel application server 108 can generate a hyperlink and send the hyperlink to the second terminal 104, and then the second terminal 104 can obtain the file data from the data channel application server 108 based on the hyperlink.

[0099] To enable those skilled in the art to better understand the embodiments of this application, the embodiments of this application are described below through specific examples.

[0100] Referring to the signaling interaction diagram shown in Figure 2, UE-A is a standalone DC terminal, and UE-B is a conventional terminal. The communication process between UE-A and UE-B includes steps 0 to 24, wherein:

[0101] In step 0, the BDC is pre-configured to be established only between User Equipment A (UE-A) and the Media Processing Function Entity. UE-A determines whether User Equipment B (UE-B) or the network supports the data channel based on responses received from the network or other relevant entities. If the response lacks information indicating support for the data channel or contains an explicit indication of non-support, UE-A can determine that UE-B or the network does not support the data channel, providing a basis for subsequent operations. UE-A can obtain an application list and download applications based on the BDC established between the Media Processing Function Entities.

[0102] Step 1: UE-A needs to transfer files, so it initiates a request to establish an Adaptive Data Channel (ADC) for file transfer. UE-A will organize a request message containing file transfer-related information (such as file size, format, etc.) and its own identifier, and send the request to the IMS Core (IMS core network) to establish an Application Data Channel (ADC), indicating that it wishes to establish a channel for data transmission.

[0103] Step 2: After receiving the request from UE-A, the IMS Core, as a key hub in the network, forwards the request to the IMS AS.

[0104] Steps 3-4: After receiving the request, IMS AS will further route the request to DCSF according to the system configuration and logic.

[0105] Steps 5-6: After receiving the request, DCSF comprehensively considers factors such as network status, user permissions, and resource availability to determine a suitable control strategy for transmitting the file to the ADC. DCSF then issues this control strategy to IMS AS so that IMS AS can perform subsequent operations based on the strategy.

[0106] Step 7: After receiving the control policy issued by DCSF, IMS AS requests the media processing function entity for the media resources required to establish the file transfer ADC, such as specific bandwidth resources, storage resources, etc., to ensure that the data channel can operate normally and meet the requirements of file transfer.

[0107] Step 8: After requesting media resources from the media processing function entity, the IMS AS replies to the DCSF with a control policy instruction, informing the DCSF of the progress of the media resource request, the request result, and the execution status of the control policy.

[0108] Step 9: After receiving the reply from IMS AS, DCSF responds to the relevant event notifications. For example, this reply could provide feedback on state changes and resource allocation during the entire resource request and control policy execution process, ensuring information synchronization between entities in the system.

[0109] Step 10: The IMS AS sends an INVITE signaling message to the IMS Core to establish an ADC. The INVITE signaling message is an important signaling message in SIP (Session Initiation Protocol) used to initiate a session request. Here, the INVITE signaling message informs the IMS Core that an ADC session for file transfer needs to be established.

[0110] Step 11: After receiving the INVITE signaling from the IMS AS, the IMS Core forwards it to the peer network (i.e., the network where UE-B is located), attempts to establish a connection with the peer network and informs the other party that it wants to establish an ADC-related session, in preparation for subsequent negotiations with UE-B.

[0111] Step 12: After receiving the INVITE signaling from the IMS Core, the peer network negotiates with the called terminal (UE-B) to discuss various parameters and conditions for establishing an ADC session, such as supported data formats and transmission rates.

[0112] Step 13: Since the peer terminal (UE-B) does not support standalone data channel (DC), the 200 OK message sent back to the IMS Core does not carry ADC-related information, only BDC information. 200 OK is a SIP protocol response message indicating successful processing of a request. This means that although the peer network and terminal received and processed the INVITE signaling, they can only provide BDC-related information because they do not support standalone DC.

[0113] Step 14: After receiving the 200 OK message from the peer network, IMS Core forwards it to IMS AS.

[0114] Steps 15-16: During the communication process, relevant events may occur. The DCSF sends an event control notification to the IMS AS, conveying the event-related information. After receiving the event control notification, the IMS AS replies with an acknowledgment message to the DCSF, indicating that it has received the notification and is aware of the relevant event.

[0115] Step 17: After receiving the 200 OK message forwarded by the IMS Core, the IMS AS adds ADC-related information to its reply 200 OK message. For example, the ADC-related information may include ADC-related parameters and status that have been negotiated with the local network. The IMS Core further returns a 200 OK message with the added ADC-related information to the UE-A. This message indicates that the ADC negotiation between the UE-A and the local network has been completed, and the UE-A can use this information to perform subsequent file transfer operations.

[0116] Step 18: After receiving the 200 OK response from the called network, UE-A sends another 200 OK response to the network, containing information about the BDC and the established ADC, indicating that it is ready to conduct data communication. The network establishes a Quality of Service (QoS) flow for the data channel based on previous settings and negotiations, ensuring that data is transmitted in the channel according to predetermined quality standards.

[0117] Step 19: The network sends a 200 OK response to UE-A to confirm that both BDC and ADC have been successfully established and that DC QoS flow is ready.

[0118] Step 20: UE-A sends an ACK message to finally confirm the network's 200 OK acknowledgment. At this point, the communication channel is established and both parties can begin data transmission.

[0119] Step 21: UE-A sends the file data that needs to be transmitted to UE-B to the media processing function entity through the established ADC.

[0120] Step 22: After receiving the file data, the DC Application Server generates a corresponding hyperlink, which can be used to access and download the file data.

[0121] Step 23: The DC Application Server sends the generated hyperlink to the regular terminal UE-B via SMS.

[0122] Step 24: After UE-B receives the short message containing the hyperlink, the user can click the hyperlink to download the corresponding file data from the data center application server, completing the entire communication process.

[0123] The terminal communication system provided in this application, when a standalone DC terminal attempts to send a file to a regular terminal, negotiates with the network via SIP signaling to obtain information that the peer terminal does not support standalone DC. The standalone DC terminal then generates a hyperlink to the file and sends the hyperlink to the peer terminal via SMS. The peer regular terminal can then successfully download the file by clicking the received hyperlink. This solution supports file sending and receiving between standalone DC terminals and regular terminals, effectively solving the problem of interoperability between them and providing effective support for the further promotion and implementation of standalone DC communication.

[0124] In one embodiment, as shown in FIG3, a terminal communication method is provided. This embodiment illustrates the method by applying it to a terminal (referred to as the first terminal in the following embodiment for clarity). In this embodiment, the method includes the following steps:

[0125] Step 302: When there is a need to send file data to the second terminal, if the second terminal does not support the IP Multimedia Subsystem (IMS) independent data channel, the target data is sent to the media processing function entity through the application data channel (ADC) established with the local network, so that the target data is forwarded to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0126] The target data includes file data and identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

[0127] In this embodiment, the first terminal is a standalone DC terminal, and the second terminal is a conventional terminal. When the first terminal needs to send file data to the second terminal, the first terminal can negotiate with the SIP signaling system to obtain information that the second terminal does not support standalone DC (the specific negotiation process can be referred to the relevant description in the foregoing embodiments, and will not be repeated here in this embodiment). Then, the first terminal sends target data containing the file data to be transmitted and the identification information of the second terminal to the media processing function entity through the ADC established with the local network. The media processing function entity then forwards the target data to the data channel application server. The data channel application server generates a hyperlink corresponding to the target data and sends the hyperlink to the second terminal, allowing the second terminal to obtain the file data from the data channel application server through the hyperlink. The specific process can be referred to the relevant description in the foregoing embodiments, and will not be repeated here in this embodiment.

[0128] The terminal communication method provided in this application, in a terminal communication scenario where the second terminal is a conventional terminal that does not support IMS standalone DC, while the first terminal is a standalone DC terminal that supports IMS standalone DC, forwards the file data to be sent to the data channel application server through the media processing function entity. Subsequently, the data channel application server generates a corresponding hyperlink based on the received file data and sends the hyperlink to the second terminal. After receiving the hyperlink, the second terminal can obtain the file data from the data channel application server based on the hyperlink. That is, the terminal communication method provided in this application successfully breaks down the communication barrier between conventional terminals and standalone DC terminals, effectively realizing communication interaction between the two, providing strong solution support for the further promotion and application of IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0129] In an exemplary embodiment, referring to FIG4, in step 302, if the second terminal does not support the IMS independent data channel, then sending the target data to the media processing function entity through the ADC established with the local network may include the following steps 402 to 406, wherein:

[0130] Step 403: Send an ADC establishment request to the IMS core network. The ADC establishment request carries a first identifier, which is used to indicate the end-to-end ADC.

[0131] Step 404: Receive response information sent by the IMS core network. The response information carries a second identifier, which is used to indicate the ADC from the end to the platform.

[0132] Step 406: In response to the response information, send the target data to the media processing function entity through the ADC established with the local network.

[0133] In this embodiment, when a first terminal needs to transfer file data to a second terminal, it sends an ADC establishment request to the IMS core network. When sending the ADC establishment request, the first terminal carries a first identifier in the request message. This first identifier is a special mark or code used to explicitly indicate that the request is associated with an end-to-end ADC. For example, the first identifier can be a string with a specific format, containing relevant identification information for the first and second terminals, as well as a specific marker for the end-to-end communication mode. For example, the first identifier can be designed in the form of "E2E-ADC-[Source Terminal ID]-[Target Terminal ID]", where "E2E-DC" indicates an end-to-end ADC request, and the following source terminal ID and target terminal ID are used to uniquely identify the two ends of the communication.

[0134] After receiving the ADC establishment request sent by the first terminal, the IMS core network executes the SIP signaling negotiation process and obtains the response information fed back by the IMS core network. This SIP signaling negotiation process can refer to steps 2 to 20 of the aforementioned embodiments, and will not be repeated here in this embodiment.

[0135] The first terminal receives a response message from the IMS core network carrying a second identifier. This second identifier is used to indicate the end-to-platform ADC, and can be in the format of "E2P-ADC-[Network Platform Identifier]-[Channel Parameters]", where "E2P-ADC" indicates the end-to-platform ADC, "Network Platform Identifier" identifies the serving network platform, and "Channel Parameters" covers ADC-related parameters such as bandwidth and transmission protocol.

[0136] The first terminal parses the received response information, confirms its legitimacy and compliance with expectations, and then responds by sending the target data to the media processing function entity through the ADC already established with the local network. The target data can be various types of file data, such as text, images, and videos. Before sending, the first terminal encapsulates the data, adding header information such as data type and length. Simultaneously, based on the ADC characteristics and network requirements, it selects an appropriate transmission protocol (such as TCP (Transmission Control Protocol) or UDP (User Datagram Protocol)) and method to ensure the reliability and efficiency of data transmission.

[0137] In one embodiment, as shown in Figure 5, a terminal communication method is provided. This embodiment illustrates the application of this method to a data channel application server. In this embodiment, the method includes the following steps 502 to 504, wherein:

[0138] Step 502: Receive target data sent by the media processing function entity. The target data is data sent by the first terminal to the media processing function entity through the application data channel (ADC) established with the local network when the second terminal does not support the IMS independent data channel. The target data includes file data and the identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0139] Step 504: Generate a hyperlink based on the file data and send the hyperlink to the second terminal based on the identification information of the second terminal.

[0140] In this embodiment, the target data is data sent by the first terminal and forwarded to the data channel application server by the media processing function entity. It includes file data to be sent to the second terminal and the identification information of the second terminal. The process of the first terminal sending the target data to the media processing function entity can be referred to the relevant description in the foregoing embodiments, and will not be repeated here in this embodiment.

[0141] After the data channel application server obtains file data from the target data, it first processes the file data for storage, storing the file data in a designated storage space. For example, it may categorize and store the data according to information such as file type and time. Then, based on the stored file location information, it generates a corresponding hyperlink. For example, if the file data is stored in the server's " / files / contract / 20250325 / " directory and the file name is "important_contract.docx", the hyperlink generated by the data channel application server could be "http: / / dc-server / files / contract / 20250325 / important_contract.docx".

[0142] The data channel application server obtains the identification information of the second terminal from the target data and determines the method of sending the hyperlink to the second terminal based on the identification information. If the identification information of the second terminal is a mobile phone number and the communication system supports SMS notification function, the data channel application server can send an SMS containing the hyperlink to the second terminal through the SMS gateway. If the second terminal supports instant messaging applications and has corresponding account information in the IMS core network, the data channel application server can also send the hyperlink to the corresponding instant messaging account of the second terminal through the instant messaging interface.

[0143] After receiving a text message or instant messaging message containing a hyperlink, the user clicks the hyperlink. If the second terminal device has an application installed that supports opening that file type, the device will automatically invoke that application and request the file data from the data channel application server via the network, completing the file reception process.

[0144] The terminal communication method provided in this application, in a terminal communication scenario where the second terminal is a conventional terminal that does not support IMS standalone DC, while the first terminal is a standalone DC terminal that supports IMS standalone DC, forwards the file data to be sent to the data channel application server through the media processing function entity. Subsequently, the data channel application server generates a corresponding hyperlink based on the received file data and sends the hyperlink to the second terminal. After receiving the hyperlink, the second terminal can obtain the file data from the data channel application server based on the hyperlink. That is, the terminal communication method provided in this application successfully breaks down the communication barrier between conventional terminals and standalone DC terminals, effectively realizing communication interaction between the two, providing strong solution support for the further promotion and application of IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0145] In one embodiment, as shown in FIG6, a terminal communication method is provided. This embodiment illustrates the application of this method to a terminal (referred to as a second terminal in the following embodiment for clarity). In this embodiment, the method includes the following steps 602 to 604, wherein:

[0146] Step 602: Receive a hyperlink sent by the data channel application server. The hyperlink is generated based on file data. The file data is carried in the target data forwarded by the media processing function entity to the data channel application server. The target data is sent by the first terminal to the media processing function entity through the application data channel ADC established with the local network. The target data includes file data and the identification information of the second terminal. The first terminal supports the IMS independent data channel. The media processing function entity includes at least one of media function MF and media resource function MRF.

[0147] Step 604: Obtain file data from the data channel application server via a hyperlink.

[0148] In this embodiment, the hyperlink is generated by the data channel application server based on the file data sent by the first terminal. The process of the data channel application server obtaining the file data and sending the hyperlink to the second terminal can be referred to the relevant description in the foregoing embodiments, and will not be repeated here in this embodiment.

[0149] For example, if the data channel application server sends a hyperlink to a second terminal through the SMS gateway, the SMS application on the second terminal will receive an SMS message containing the hyperlink. After receiving the SMS message, the SMS application will display the complete message content to the user, with the hyperlink appearing as a clickable element.

[0150] Alternatively, when the second terminal supports instant messaging applications and has corresponding account information in the IMS core network, the data channel application server sends the hyperlink to the second terminal's instant messaging account via the instant messaging interface. For example, in commonly used instant messaging software, the second terminal user receives a message from the system notification account containing the aforementioned hyperlink. The instant messaging software displays the message in rich text format, and the hyperlink can be directly clicked.

[0151] After seeing a message containing a hyperlink, the second terminal user can click the hyperlink to trigger the retrieval of file data. At this time, the second terminal device recognizes the specific file resource that the link points to on the data channel application server based on the hyperlink's format.

[0152] The second terminal device invokes the system's built-in network request module to generate an HTTP GET request for the file data based on the address information in the hyperlink. For example, for the hyperlink "http: / / dc-server / files / contract / 20250325 / important_contract.docx", the request header generated by the device may contain key information such as user device information and the requested file path.

[0153] After receiving a file request from the second terminal, the data channel application server locates the corresponding file data in the server's storage system based on the file path information in the request. For example, it reads the contents of the file "important_contract.docx" from the directory " / files / contract / 20250325 / ", encapsulates the read file data in an HTTP response, and returns it to the second terminal over the network. The response data may contain information such as the file's byte stream content, file type, and file size.

[0154] After receiving the HTTP response, the second terminal stores the file data according to the specified storage path. If an application that supports this file type is installed on the device, such as office software for opening Word documents, the device can be directly associated with that application so that subsequent users can directly open the file and view its contents.

[0155] The terminal communication method provided in this application, in a terminal communication scenario where the second terminal is a conventional terminal that does not support IMS standalone DC, while the first terminal is a standalone DC terminal that supports IMS standalone DC, forwards the file data to be sent to the data channel application server through the media processing function entity. Subsequently, the data channel application server generates a corresponding hyperlink based on the received file data and sends the hyperlink to the second terminal. After receiving the hyperlink, the second terminal can obtain the file data from the data channel application server based on the hyperlink. That is, the terminal communication method provided in this application successfully breaks down the communication barrier between conventional terminals and standalone DC terminals, effectively realizing communication interaction between the two, providing strong solution support for the further promotion and application of IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0156] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0157] Based on the same inventive concept, this application also provides a terminal communication device for implementing the terminal communication method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more terminal communication device embodiments provided below can be found in the limitations of the terminal communication method described above, and will not be repeated here.

[0158] In an exemplary embodiment, as shown in FIG7, a terminal communication device 700 is provided, including: a transmitting module 702, wherein:

[0159] The sending module 702 is used to send target data to the media processing function entity through the application data channel ADC established with the local network when there is a need to send file data to the second terminal. If the second terminal does not support the IP Multimedia Subsystem IMS independent data channel, the target data is sent to the media processing function entity through the application data channel ADC established with the local network. The media processing function entity forwards the target data to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function MF and media resource function MRF.

[0160] The target data includes the file data and the identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

[0161] In one embodiment, the sending module 702 is specifically used for:

[0162] Send an ADC establishment request to the IMS core network. The ADC establishment request carries a first identifier, which is used to indicate the end-to-end ADC.

[0163] Receive response information sent by the IMS core network, the response information carrying a second identifier, the second identifier being used to indicate the end-to-platform ADC;

[0164] In response to the response information, target data is sent to the media processing function entity via the ADC established with the local network.

[0165] In an exemplary embodiment, as shown in FIG8, a terminal communication device 800 is provided, including: a receiving module 802 and a transmitting module 804, wherein:

[0166] The receiving module 802 is used to receive target data sent by the media processing function entity. The target data is data sent by the first terminal to the media processing function entity through the application data channel (ADC) established with the local network when the second terminal does not support the IMS independent data channel. The target data includes file data and the identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF).

[0167] The sending module 804 is used to generate a hyperlink based on the file data and send the hyperlink to the second terminal based on the identification information of the second terminal.

[0168] In an exemplary embodiment, as shown in FIG9, a terminal communication device 900 is provided, including: a receiving module 902 and an acquiring module 904, wherein:

[0169] The receiving module 902 is used to receive a hyperlink sent by the data channel application server. The hyperlink is generated based on file data, which is carried in target data forwarded by the media processing function entity to the data channel application server. The target data is sent by the first terminal to the media processing function entity through the application data channel ADC established with the local network. The target data includes the file data and the identification information of the second terminal. The first terminal supports the IMS independent data channel. The media processing function entity includes at least one of media function MF and media resource function MRF.

[0170] The acquisition module 904 is used to acquire the file data from the data channel application server based on the hyperlink.

[0171] In the aforementioned terminal communication device, when the second terminal is a conventional terminal that does not support IMS standalone DC, while the first terminal is a standalone DC terminal that supports IMS standalone DC, the first terminal forwards the file data to be sent to the data channel application server through the media processing function entity. Subsequently, the data channel application server generates a corresponding hyperlink based on the received file data and sends the hyperlink to the second terminal. After receiving the hyperlink, the second terminal can obtain the file data from the data channel application server based on the hyperlink. The terminal communication device provided in this application successfully breaks down the communication barrier between conventional terminals and standalone DC terminals, effectively realizing communication interaction between the two, providing strong solution support for the further promotion and application of IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0172] Each module in the aforementioned terminal communication device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0173] In an exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram is shown in Figure 10. The computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used for exchanging information between the processor and external devices. The communication interface of the computer device is used for wired or wireless communication with external terminals; wireless communication can be implemented through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a terminal communication method.

[0174] Those skilled in the art will understand that the structure shown in Figure 10 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or may combine certain components, or may have different component arrangements.

[0175] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0176] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0177] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0178] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0179] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0180] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0181] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A terminal communication system, comprising a first terminal, a second terminal, a media processing function entity, and a data channel application server, wherein the first terminal supports an IP Multimedia Subsystem (IMS) independent data channel, and the second terminal does not support an IMS independent data channel; the media processing function entity comprises at least one of a Media Function (MF) and a Media Resource Function (MRF); The first terminal is used to send target data to the media processing function entity through the application data channel (ADC) established with the local network when there is a need to send file data to the second terminal. The target data includes the file data and the identification information of the second terminal. The media processing function entity is used to forward the target data to the data channel application server; The data channel application server is used to generate hyperlinks based on the file data and send the hyperlinks to the second terminal based on the identification information of the second terminal. The second terminal is used to obtain the file data from the data channel application server based on the hyperlink.

2. The system according to claim 1, wherein, The terminal communication system also includes an IMS core network and an IMS application server. The IMS core network is used to send signaling for establishing an ADC to the IMS application server based on the ADC establishment request sent by the first terminal. The IMS application server is used to forward the signaling to the peer network. The signaling is used to instruct the peer network to negotiate with the second terminal and to provide feedback on the response information in response to the signaling. The response information only carries the bootstrap data channel (BDC) information. The IMS application server is also used to forward the response information fed back by the peer network to the IMS core network; The IMS core network is also used to add ADC information to the response information and send the response information with added ADC information to the first terminal. The response information with added ADC information is used to indicate that the ADC connection between the first terminal and the local network is complete.

3. The system according to claim 1, wherein, Before the first terminal sends the target data to the media processing function entity through the application data channel ADC established with the local network, it is also used to encrypt the file data to obtain encrypted file data; the target data also includes the decryption key corresponding to the encrypted file data; After the second terminal obtains the encrypted file data from the data channel application server based on the hyperlink, it decrypts the encrypted file data based on the decryption key to obtain the file data.

4. A terminal communication method, applied to a first terminal, the method comprising: When there is a need to send file data to a second terminal, if the second terminal does not support the IP Multimedia Subsystem (IMS) independent data channel, the target data is sent to the media processing function entity through the application data channel (ADC) established with the local network, so that the target data is forwarded to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function (MF) and media resource function (MRF). The target data includes the file data and the identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

5. The method according to claim 4, wherein, If the second terminal does not support the IMS independent data channel, then the target data is sent to the media processing function entity through the ADC established with the local network, including: Send an ADC establishment request to the IMS core network. The ADC establishment request carries a first identifier, which is used to indicate the end-to-end ADC. Receive response information sent by the IMS core network, the response information carrying a second identifier, the second identifier being used to indicate the end-to-platform ADC; In response to the response information, target data is sent to the media processing function entity via the ADC established with the local network.

6. The method according to claim 4, wherein, Before sending the target data to the media processing function entity through the application data channel ADC established with the local network, the method further includes: The file data is encrypted to obtain encrypted file data; The target data also includes a decryption key corresponding to the encrypted file data. The decryption key is used by the second terminal to decrypt the encrypted file data after obtaining it from the data channel application server via the hyperlink, in order to obtain the file data.

7. A terminal communication method applied to a data channel application server, the method comprising: The system receives target data sent by a media processing function entity. The target data is data sent by the first terminal to the media processing function entity through the application data channel (ADC) established with the local network when the second terminal does not support the IMS independent data channel. The target data includes file data and the identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF). A hyperlink is generated based on the file data, and the hyperlink is sent to the second terminal based on the identification information of the second terminal.

8. A terminal communication method applied to a second terminal, the second terminal not supporting the IP Multimedia Subsystem (IMS) independent data channel, the method comprising: The system receives a hyperlink sent by a data channel application server. The hyperlink is generated based on file data, which is carried in target data forwarded by a media processing function entity to the data channel application server. The target data is sent by a first terminal to the media processing function entity through an application data channel (ADC) established with its local network. The target data includes the file data and the identification information of the second terminal. The first terminal supports IMS independent data channels. The media processing function entity includes at least one of media function (MF) and media resource function (MRF). The file data is obtained from the data channel application server based on the hyperlink.

9. The method according to claim 8, wherein, The target data also includes a decryption key corresponding to the encrypted file data; the encrypted file data is obtained by the first terminal encrypting the file data. After receiving the hyperlink sent by the data channel application server, the method further includes: After obtaining the encrypted file data from the data channel application server via the hyperlink, the encrypted file data is decrypted using the decryption key to obtain the file data.

10. A terminal communication device, applied to a first terminal, the device comprising: The sending module is used to send target data to the media processing function entity through the application data channel ADC established with the local network when there is a need to send file data to the second terminal. If the second terminal does not support the IP Multimedia Subsystem IMS independent data channel, the target data is sent to the media processing function entity to forward the target data to the data channel application server through the media processing function entity. The media processing function entity includes at least one of media function MF and media resource function MRF. The target data includes the file data and the identification information of the second terminal. The target data is used to instruct the data channel application server to generate a hyperlink from the file data and then send the hyperlink to the second terminal.

11. A terminal communication device applied to a data channel application server, the device comprising: A receiving module is used to receive target data sent by a media processing function entity. The target data is data sent by the first terminal to the media processing function entity through an application data channel (ADC) established with the local network when the second terminal does not support an IMS independent data channel. The target data includes file data and identification information of the second terminal. The media processing function entity includes at least one of media function (MF) and media resource function (MRF). The sending module is used to generate a hyperlink based on the file data and send the hyperlink to the second terminal based on the identification information of the second terminal.

12. A terminal communication device, applied to a second terminal, the second terminal not supporting the IP Multimedia Subsystem (IMS) independent data channel, the device comprising: A receiving module is used to receive a hyperlink sent by a data channel application server. The hyperlink is generated based on file data, which is carried in target data forwarded by a media processing function entity to the data channel application server. The target data is sent by a first terminal to the media processing function entity through an application data channel (ADC) established with its local network. The target data includes the file data and the identification information of the second terminal. The first terminal supports an IMS independent data channel. The media processing function entity includes at least one of media function (MF) and media resource function (MRF). The acquisition module is used to acquire the file data from the data channel application server based on the hyperlink.

13. A computer device comprising a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method according to any one of claims 4 to 9.

14. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method according to any one of claims 4 to 9.

15. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 4 to 9.

Images