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

Abstract

The invention relates to a terminal communication method, device and system, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: when a demand for sending file data to a second terminal exists, if the second terminal does not support an IP multimedia subsystem IMS independent data channel, sending target data to a media function MF / media resource function MRF through an application data channel ADC established with a home terminal network, the MF / MRF sends the target data to a data channel application server, 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 generating the hyperlink from the file data. By adopting the method, the communication interaction between the conventional terminal and the standalone DC terminal can be realized.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a terminal communication method, apparatus, system, computer device, computer-readable storage medium, and computer program product. Background Art

[0002] In the general trend of 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 remarkable progress in this field, has basically established the network element architecture of IMS standalone DC sessions, constructed the corresponding basic processes, and at the same time formulated a series of detailed standard specifications, laying a foundation for the development of communication based on IMS standalone DC.

[0003] However, it cannot be ignored that there are a large number of conventional terminals in the existing communication environment that do not support standalone DC. In actual communication scenarios, the interoperability problem between these conventional terminals and terminals that support standalone DC has not been properly solved, and there is still a lack of practical and effective interoperability solutions. For example, when a terminal that supports standalone DC expects to send a file to a conventional terminal using the DC channel, due to the non-support of standalone DC by the conventional terminal, the file cannot be directly received through the standalone DC channel, which seriously hinders the smooth communication interaction 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

[0004] Based on this, in view of the above technical problems, it is necessary to provide a terminal communication method, apparatus, system, computer device, computer-readable storage medium, and computer program product that can enable communication between a conventional terminal and a terminal that supports standalone DC.

[0005] In a first aspect, the present application provides a terminal communication system, which includes a first terminal, a second terminal, a media function (MF) / media resource function (MRF), and a data channel application server. The first terminal supports an IP multimedia subsystem (IMS) independent data channel, and the second terminal does not support the IMS independent data channel. Among them,

[0006] The first terminal is configured to, when there is a need to send file data to the second terminal, send target data to the MF / MRF through an application data channel (ADC) established with its own network. The target data includes the file data and the identification information of the second terminal.

[0007] The MF / MRF is configured to forward the target data to the data channel application server.

[0008] The data channel application server is configured 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.

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

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

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

[0012] The IMS application server is configured to forward the signaling to the peer network. The signaling is used to instruct the peer network to negotiate with the second terminal and feedback response information for the signaling. The response information only carries boot data channel (BDC) information.

[0013] The IMS application server is further configured to forward the response information fed back by the peer network to the IMS core network.

[0014] The IMS core network is further configured to add ADC information to the response information and send the response information with the added ADC information to the first terminal. The response information with the added ADC information is used to indicate that the establishment of the ADC between the first terminal and its own network is completed.

[0015] In a second aspect, the present application further provides a terminal communication method, which is applied to a first terminal. The method includes:

[0016] 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 Function (MF) / Media Resource Function (MRF) through the Application Data Channel (ADC) established with the local network, so as to forward the target data to the data channel application server through the MF / MRF.

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

[0018] In one embodiment, the step of, if the second terminal does not support the IMS independent data channel, sending the target data to the MF / MRF through the ADC established with the local network includes:

[0019] Sending an ADC establishment request to the IMS core network, where the ADC establishment request carries a first identifier for indicating an end-to-end ADC.

[0020] Receiving response information sent by the IMS core network, where the response information carries a second identifier for indicating an ADC from the end to the platform.

[0021] In response to the response information, sending the target data to the MF / MRF through the ADC established with the local network.

[0022] In a third aspect, the present application further provides a terminal communication method applied to a data channel application server, and the method includes:

[0023] Receiving target data sent by the MF / MRF, where the target data is data sent by a first terminal to the MF / MRF through the Application Data Channel (ADC) established with the local network when the second terminal does not support the IMS independent data channel, and the target data includes file data and the identification information of the second terminal.

[0024] Generating a hyperlink based on the file data and sending the hyperlink to the second terminal based on the identification information of the second terminal.

[0025] In a fourth aspect, the present application further provides a terminal communication method applied to a second terminal that does not support the IP Multimedia Subsystem (IMS) independent data channel, and the method includes:

[0026] Receive a hyperlink sent by a data channel application server, where the hyperlink is generated based on file data, and the file data is carried in target data forwarded by a media function MF / media resource function MRF to the data channel application server. The target data is sent by a first terminal to the MF / MRF through an application data channel ADC established with its own network. The target data includes the file data and identification information of the second terminal, and the first terminal supports an IMS independent data channel;

[0027] Obtain the file data from the data channel application server based on the hyperlink.

[0028] In a fifth aspect, the present application further provides a terminal communication device applied to a first terminal. The device includes:

[0029] A sending module, configured to, when there is a need to send file data to a second terminal, if the second terminal does not support an IMS independent data channel, send target data to a media function MF / media resource function MRF through an application data channel ADC established with its own network, so as to forward the target data to a data channel application server through the MF / MRF,

[0030] The target data includes the file data and identification information of the second terminal, and 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.

[0031] In one embodiment, the sending module is specifically configured to:

[0032] Send an ADC establishment request to an IMS core network, where the ADC establishment request carries a first identifier, and the first identifier is used to indicate an end-to-end ADC;

[0033] Receive response information sent by the IMS core network, where the response information carries a second identifier, and the second identifier is used to indicate an end-to-platform ADC;

[0034] In response to the response information, send target data to the MF / MRF through an ADC established with its own network.

[0035] In a sixth aspect, the present application further provides a terminal communication device applied to a data channel application server. The device includes:

[0036] A receiving module, configured to receive target data sent by a media function (MF) / media resource function (MRF), where the target data is data sent by a first terminal to the MF / MRF through an application data channel (ADC) established with its own network when a second terminal does not support an IMS independent data channel, and the target data includes file data and identification information of the second terminal;

[0037] A sending module, configured 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.

[0038] In a seventh aspect, the present application further provides a terminal communication device applied to a second terminal that does not support an IP multimedia subsystem (IMS) independent data channel. The device includes:

[0039] A receiving module, configured to receive a hyperlink sent by a data channel application server, where the hyperlink is generated based on file data, and the file data is carried in target data forwarded by an MF / media resource function (MRF) to the data channel application server. The target data is sent by a first terminal to the MF / MRF through an application data channel (ADC) established with its own network, and the target data includes the file data and identification information of the second terminal, and the first terminal supports an IMS independent data channel;

[0040] An obtaining module, configured to obtain the file data from the data channel application server based on the hyperlink.

[0041] In an eighth aspect, the present application further provides a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the terminal communication method according to any one of the above.

[0042] In a ninth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the terminal communication method according to any one of the above.

[0043] In a tenth aspect, the present application further provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the terminal communication method according to any one of the above.

[0044] The above terminal communication method, device, system, computer device, computer-readable storage medium, and computer program product, in a terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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 method, device, system, computer device, computer-readable storage medium, and computer program product provided by the embodiments of the present application successfully break the communication barrier between the conventional terminal and the standalone DC terminal, effectively realizing the communication interaction between the two, providing a strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promoting the efficient development of communication technology in a complex terminal environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for the description of the embodiments of the present application or related technologies. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other related drawings can also be obtained based on these drawings.

[0046] Figure 1 It is a schematic structural diagram of a terminal communication system in an embodiment;

[0047] Figure 2 It is a schematic diagram of signaling interaction of a terminal communication method in an embodiment;

[0048] Figure 3 It is a schematic flowchart of a terminal communication method in another embodiment;

[0049] Figure 4 It is a schematic flowchart of step 302 in another embodiment;

[0050] Figure 5 It is a schematic flowchart of a terminal communication method in another embodiment;

[0051] Figure 6 It is a schematic flowchart of a terminal communication method in another embodiment;

[0052] Figure 7 It is a block diagram of the structure of a terminal communication device in an embodiment;

[0053] Figure 8 It is a structural block diagram of a terminal communication device in another embodiment;

[0054] Figure 9 It is a structural block diagram of a terminal communication device in another embodiment;

[0055] Figure 10 It is an internal structure diagram of a computer device in one embodiment. Detailed implementation manners

[0056] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0057] In order to understand the embodiments of the present application more clearly, before introducing the embodiments of the present application, the nouns involved will be explained first:

[0058] IMS (IP Multimedia Subsystem): It is a form of multimedia service based on an IP network. It uses SIP as the call control protocol, realizes the separation of call control and service control, and enhances the multimedia support ability. It aims to provide terminal customers with newer and more diverse multimedia service experiences through the IP network. Among them, SIP (Session Initiation Protocol): It is a multimedia communication protocol formulated 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, and has characteristics such as flexibility, easy implementation, and easy expansion.

[0059] DC (Data Channel): IMS DC is an extension of the IMS multimedia telephone service, allowing any content to be transmitted between two endpoints supporting the data channel during an ongoing active session.

[0060] IMS standalone DC: It refers to the 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 the BDC (Batch Data Communication, Bootstrapping Data Channel), and then transmits application data and real-time interactive dynamic service data through the ADC (Application Data Center, Application Data Channel).

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

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

[0063] The IMS core network, also known as IMS Core (IP Multimedia Subsystem Core), IMS is a multimedia service control architecture based on the IP network. IMS Core is its core part, responsible for processing various signaling, session control, user authentication and authorization, etc., and providing core support for multimedia services.

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

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

[0066] The DC Application Server (Data Channel Application Server), namely the IMS data channel application server, is a server in the IMS network architecture responsible for processing service logics related to the data channel.

[0067] In an exemplary embodiment, as Figure 1 shown, a terminal communication system is provided. The terminal communication system includes a first terminal 102, a second terminal 104, a media function MF / media resource function MRF 106, and a data channel application server 108. The first terminal supports an IP multimedia subsystem IMS independent data channel, and the second terminal does not support the IMS independent data channel. Among them,

[0068] The first terminal 102 is configured to, when there is a need to send file data to the second terminal 104, send target data to the MF / MRF 106 through an application data channel ADC established with its local network. The target data includes file data and the identification information of the second terminal 104.

[0069] The MF / MRF 106 is configured to forward the target data to the data channel application server 108.

[0070] The data channel application server 108 is configured to generate a hyperlink based on the file data and send the hyperlink to the second terminal 104 based on the identification information of the second terminal.

[0071] The second terminal 104 is configured to obtain the file data from the data channel application server 108 based on the hyperlink.

[0072] In the embodiment of the present application, 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 has a need 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.

[0073] The first terminal 102 sorts and encapsulates the file data to be sent and adds the identification information of the second terminal 104 to the sent data. The identification information may be the unique identification code of the second terminal 104 in the communication network, such as IMSI (International Mobile Subscriber Identity) or other similar coding information that can be used to accurately locate the terminal.

[0074] Subsequently, the first terminal 102 sends the target data containing the file data and the identification information of the second terminal 104 to the MF / MRF 106 through the established ADC. During the sending process, the first terminal 102 follows the data transmission protocol of the ADC to ensure the integrity and accuracy of the data, and at the same time performs necessary encryption processing on the data to ensure the security of the data during transmission.

[0075] After receiving the target data sent by the first terminal 102, the MF / MRF 106 performs preliminary parsing and verification on the data. The verification content includes whether the data format conforms to the system requirements, the integrity check of the data, and the source legality check, etc. If the verification passes, the MF / MRF 106 forwards the target data to the data channel application server 108 according to the routing rules and data forwarding policies preset by the system. During the forwarding process, the MF / MRF 106 ensures the reliable transmission of the data, and adopts appropriate caching and retransmission mechanisms to prevent data loss or damage.

[0076] After receiving the target data forwarded by the MF / MRF 106, the data center application server 108 extracts the file data from the target data. The data center application server 108 generates a corresponding hyperlink based on the characteristics and attributes of the file data. The hyperlink is a network address identifier that can be used to access and obtain the file data, and its generation algorithm ensures the uniqueness and validity of the hyperlink. In the embodiments of the present application, the generation algorithm of the hyperlink is not specifically limited.

[0077] 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 according to the 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 according to its IMSI information. Furthermore, the data center application server 108 sends the generated hyperlink to the second terminal 104 through a suitable communication method, such as a SMS gateway or other message push platforms. When sending the hyperlink, the data center application server 108 ensures the accuracy of the hyperlink information and can record the sending process for subsequent query and traceability.

[0078] After the second terminal 104 receives the hyperlink sent by the data center application server 108, the user can trigger the file acquisition operation of the terminal by clicking on the hyperlink. Exemplarily, the second terminal 104 can initiate a file data acquisition request to the data center application server 108 according to the network address pointed to by the hyperlink. During the request process, the second terminal 104 follows the file access protocol supported by the data center application server 108, such as the HTTP (Hypertext Transfer Protocol) or FTP (File Transfer Protocol). After receiving the file acquisition request from the second terminal 104, the data center application server 108 verifies the legitimacy of the request and the validity of the hyperlink. If the verification passes, 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.

[0079] During the process of receiving the 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. When the file data reception is completed and the verification is correct, the second terminal 104 stores the file at a specified storage location locally, completing the process of acquiring the file data.

[0080] In the terminal communication system provided by the embodiments of the present application, in a terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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, by adopting the terminal communication system provided by the embodiments of the present application, the communication barrier between the conventional terminal and the standalone DC terminal is successfully broken, and the communication interaction between the two is effectively realized, providing a strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promoting the efficient development of communication technology in a complex terminal environment.

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

[0082] The IMS core network is configured to send a signaling for establishing an ADC to the IMS application server based on the ADC establishment request sent by the first terminal;

[0083] The IMS application server is used to forward signaling to the peer network. The signaling is used to instruct the peer network to negotiate with the second terminal and feedback response information for the signaling. Only the Boot Data Channel (BDC) information is carried in the response information.

[0084] The IMS application server is also used to forward the response information feedback by the peer network to the IMS core network.

[0085] The IMS core network is also used to add ADC information to the response information, and send the response information with the added ADC information to the first terminal. The response information with the added ADC information is used to indicate that the ADC establishment between the first terminal and its local network is completed.

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

[0087] The IMS core network sends the generated signaling to the IMS application server. The IMS application server is responsible for forwarding the signaling to the peer network, and the signaling is used to instruct 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, only the Boot Data Channel (BDC) information is carried in the response information feedback by the peer network to the IMS application server after the negotiation is completed. After receiving the response information, the IMS application server forwards it to the IMS core network.

[0088] 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. These information include specific parameters of the ADC allocated by the local network for the first terminal 102, such as channel bandwidth, data transmission format, access key, etc., and an identifier indicating that the established ADC is an end-to-platform ADC. After adding, the IMS core network sends the response information with the added ADC information to the first terminal 102, and the response information is used to indicate that the ADC establishment between the first terminal 102 and its local network is completed.

[0089] In this way, subsequently, the first terminal 102 can send the file data to be sent to the second terminal 104 to the MF / MRF through the ADC established with the local network, so that the MF / MRF forwards the file data to the data channel application server 108. The data channel application server 108 generates a hyperlink and sends the hyperlink to the second terminal 104. Furthermore, the second terminal 104 can obtain the file data from the data channel application server 108 based on the hyperlink.

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

[0091] Referring to Figure 2 the signaling interaction diagram shown, 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, where:

[0092] In step 0, it is preset that the BDC is only established between the user equipment A (UE-A) and the MF / MRF. UE-A determines whether the user equipment B (UE-B) or the network supports the data channel according to the response received from the network or other relevant entities. If the relevant information indicating support for the data channel is missing in the response or there is an explicit indication of non-support, UE-A can determine that UE-B or the network does not support the data channel, which provides a basic judgment for subsequent operations. UE-A can obtain the application list and download applications based on the BDC established between the MF / MRF.

[0093] Step 1: UE-A has a need for file transfer, 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, etc., and send a request to establish an application data channel (ADC) to the IMS Core (IMS core network), indicating its hope to establish a channel for data transmission.

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

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

[0096] Steps 5-6: After receiving the request, the DCSF determines the control strategy suitable for the ADC of this file transfer by comprehensively considering various factors such as network status, user permissions, and resource availability. The DCSF sends this control strategy to the IMS AS so that the IMS AS can perform subsequent operations according to this strategy.

[0097] Step 7: After receiving the control policy sent by the DCSF, the IMS AS requests the MF / MRF 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.

[0098] Step 8: After requesting the media resources from the MF / MRF, the IMS AS replies to the DCSF with a control policy indication, informing the DCSF of information such as the progress of the media resource request, the request result, and the execution status of the control policy.

[0099] Step 9: After receiving the reply from the IMS AS, the DCSF makes a reply to the relevant event notification. Exemplarily, this reply can provide feedback on the status changes and resource allocation during the entire resource request and control policy execution process, ensuring information synchronization among entities in the system.

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

[0101] Step 11: After receiving the INVITE signaling sent by 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 an ADC-related session is to be established, preparing for subsequent negotiation with UE-B.

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

[0103] Step 13: Since the peer terminal (UE-B) does not support the standalone data channel (standalone DC), the ADC-related information is not carried in the 200OK message replied to the IMS Core, and only the BDC information is carried. 200OK is a response message in the SIP protocol indicating that the request has been successfully processed. Here, it shows that although the peer network and terminal received and processed the INVITE signaling, due to the lack of support for standalone DC, only BDC-related information can be provided.

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

[0105] Steps 15-16: During the communication process, a related event may occur. DCSF sends an event control notification to IMS AS to convey the event-related information. After receiving the event control notification, IMS AS replies with confirmation information to DCSF, indicating that it has received the notification and is aware of the related event.

[0106] Step 17: After receiving the 200OK message forwarded by the IMS Core, the IMS AS adds ADC related information to the replied 200OK message. For example, the ADC related information may include information such as ADC related parameters and status that have been negotiated by the local network. The IMS Core further returns the 200OK message with the ADC related information added to UE-A, indicating through this message that the ADC negotiation between UE-A and the local network has been completed, and UE-A can perform subsequent file transfer operations based on this information.

[0107] Step 18: After receiving the 200OK response from the called network, UE-A sends a 200OK response to the network again, which contains the relevant information of BDC and the established ADC, indicating that it is ready for data communication. Based on the previous settings and negotiations, the network establishes the quality of service (QoS) flow of the data channel to ensure that the data can be transmitted in the channel according to the predetermined quality standard.

[0108] Step 19: The network sends a 200OK response to UE-A, confirming that both BDC and ADC have been successfully established and DC Qosflow is ready.

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

[0110] Step 21: UE-A sends the file data to be transmitted to UE-B to the MF / MRF through the established ADC.

[0111] 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.

[0112] Step 23: The DC Application Server sends the generated hyperlink to the conventional terminal UE-B via a short message.

[0113] 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, thus completing the entire communication process.

[0114] In the terminal communication system provided by the embodiments of the present application, when a standalone DC terminal attempts to send a file to a conventional terminal, the standalone DC terminal obtains through SIP signaling negotiation the status that the peer terminal does not support standalone DC, and then initiates negotiation with the network to generate a hyperlink of the file, and sends the hyperlink to the peer terminal through SMS. The peer conventional terminal can successfully download the file by clicking on the received hyperlink. This solution supports the sending and receiving of files between the standalone DC terminal and the conventional terminal, effectively solving the problem of non-interoperability between the standalone DC terminal and the conventional terminal, and providing an effective solution support for the further promotion and implementation of standalone DC communication.

[0115] In one embodiment, as Figure 3 shown, a terminal communication method is provided. In this embodiment, this method is exemplified by being applied to a terminal (referred to as the first terminal in the following embodiments for clear description). In this embodiment, the method includes the following steps:

[0116] Step 302, 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, send target data to a Media Function (MF) / Media Resource Function (MRF) through an Application Data Channel (ADC) established with the local network, so as to forward the target data to a data channel application server through the MF / MRF.

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

[0118] In the embodiments of the present application, the first terminal is a standalone DC terminal, and the second terminal is a conventional terminal. When the first terminal has a need to send file data to the second terminal, the first terminal can obtain through SIP signaling negotiation the status that the second terminal does not support standalone DC (the specific negotiation process can refer to the relevant description in the foregoing embodiments, and will not be elaborated herein in the embodiments of the present application). Then, the first terminal sends target data including the file data to be transmitted and the identification information of the second terminal to the MF / MRF through the ADC established with the local network, so as to forward the target data to the data channel application server through the MF / MRF. After the data channel application server generates the hyperlink corresponding to the target data, it sends the hyperlink to the second terminal. Then, the second terminal can obtain the file data from the data channel application server through the hyperlink. The specific process can refer to the relevant description in the foregoing embodiments, and will not be elaborated herein in the embodiments of the present application.

[0119] In the terminal communication method provided by the embodiment of the present application, in a terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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, by adopting the terminal communication method provided by the embodiment of the present application, the communication barrier between the conventional terminal and the standalone DC terminal is successfully broken, and the communication interaction between the two is effectively realized, providing strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promoting the efficient development of communication technology in a complex terminal environment.

[0120] In an exemplary embodiment, referring to Figure 4 as shown, in step 302, if the second terminal does not support the IMS independent data channel, sending the target data to the MF / MRF through the ADC established with the local network may include the following steps 402 to 406, where:

[0121] Step 403, sending an ADC establishment request to the IMS core network, where the ADC establishment request carries a first identifier, and the first identifier is used to indicate the end-to-end ADC;

[0122] Step 404, receiving the response information sent by the IMS core network, where the response information carries a second identifier, and the second identifier is used to indicate the ADC from the end to the platform;

[0123] Step 406, in response to the response information, sending the target data to the MF / MRF through the ADC established with the local network.

[0124] In the embodiment of the present application, when the first terminal has a need to transmit file data to the second terminal, it sends an ADC establishment request to the IMS core network. When sending this ADC establishment request, the first terminal carries a first identifier in the request message. The first identifier is a special mark or code used to clearly indicate that the request is associated with an end-to-end ADC. For example, the first identifier can be a string in a specific format that contains relevant identification information of the first terminal and the second terminal, as well as a specific mark 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" represents the end-to-end ADC request, and the subsequent source terminal ID and target terminal ID are used to uniquely identify the two ends of the communication.

[0125] After the IMS core network receives the ADC establishment request sent by the first terminal, it executes the SIP signaling negotiation process and obtains the response information fed back by the IMS core network. This SIP signaling negotiation process may refer to Steps 2 to 20 of the foregoing embodiment, and will not be elaborated herein in the embodiments of the present application.

[0126] The first terminal receives the second identifier carried in the response information sent by the IMS core network. This second identifier is used to indicate the end-to-platform ADC. For example, it may be in the format of "E2P-ADC-[network platform identifier]-[channel parameter]". "E2P -ADC" represents the end-to-platform ADC, "network platform identifier" identifies the service network platform, and "channel parameter" covers ADC-related parameters such as bandwidth and transmission protocol.

[0127] After the first terminal parses the received response information and confirms that it is legal and meets the expectations, in response to the response information, it sends the target data to the MF / MRF through the ADC established with its local network. The target data may be various file data such as text, images, and videos. Before sending, the first terminal will encapsulate the data, add header information such as data type and length, and at the same time, according to the ADC characteristics and network requirements, select a suitable transmission protocol (such as TCP (Transmission Control Protocol), UDP (User Datagram Protocol)) and method to ensure the reliability and efficiency of data transmission.

[0128] In one embodiment, as Figure 5 shown, a terminal communication method is provided. In this embodiment, this method is illustrated by taking the application of this method to a data channel application server as an example. In the embodiment, this method includes the following Steps 502 to 504, where:

[0129] Step 502: Receive the target data sent by the media function MF / media resource function MRF. The target data is the data sent by the first terminal to the MF / MRF through the application data channel ADC established with its local network when the second terminal does not support the IMS independent data channel. The target data includes file data and the identifier information of the second terminal;

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

[0131] In the embodiment of the present application, the target data is sent from the first terminal and forwarded to the data channel application server via the MF / MRF. It includes the 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 MF / MRF can refer to the relevant description in the foregoing embodiment, which will not be elaborated herein in the embodiment of the present application.

[0132] After the data channel application server obtains the file data from the target data, it first performs storage processing on the file data and stores the file data in the specified storage space. For example, it is classified and stored according to information such as file type and time. Then, based on the stored file location information, a corresponding hyperlink is generated. For example, if the file data is stored in the directory " / files / contract / 20250325 / " on the server and the file name is "important_contract.docx", the hyperlink generated by the data channel application server can be "http: / / dc - server / files / contract / 20250325 / important_contract.docx".

[0133] 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 of the second terminal. If the identification information of the second terminal is a mobile phone number and the communication system supports the 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 an instant messaging application and there is 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.

[0134] After the second terminal receives the SMS or instant messaging message containing the hyperlink, the user clicks on the hyperlink. If the second terminal device has installed an application program that supports opening this file type, the device will automatically call the application program and download the file data from the data channel application server through a network request to complete the file receiving process.

[0135] The terminal communication method provided by the embodiments of the present application, in the terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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, by adopting the terminal communication method provided by the embodiments of the present application, the communication barrier between the conventional terminal and the standalone DC terminal is successfully broken, and the communication interaction between the two is effectively realized, providing a strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promoting the efficient development of communication technology in complex terminal environments.

[0136] In one embodiment, as Figure 6 shown, a terminal communication method is provided. In this embodiment, this method is exemplified by being applied to a terminal (referred to as the second terminal in the following embodiments for clear description). In the embodiment, the method includes the following steps 602 to 604, where:

[0137] Step 602, receive the hyperlink sent by the data channel application server. The hyperlink is generated based on the file data, and the file data is carried in the target data forwarded by the media function MF / media resource function MRF to the data channel application server. The target data is sent by the first terminal to the MF / MRF 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, and the first terminal supports IMS independent data channel;

[0138] Step 604, obtain the file data from the data channel application server based on the hyperlink.

[0139] In the embodiments of the present application, 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 refer to the relevant descriptions of the foregoing embodiments, and will not be elaborated herein in the embodiments of the present application.

[0140] Exemplarily, if the data channel application server sends the hyperlink to the second terminal through the SMS gateway, the SMS application of the second terminal will receive the SMS containing the hyperlink. After receiving the SMS, the SMS application will display the SMS content to the user completely, and the hyperlink part will be presented in a clickable form.

[0141] Alternatively, when the second terminal supports an instant messaging application and has corresponding account information in the IMS core network, the data channel application server sends the hyperlink to the instant messaging account of the second terminal through the instant messaging interface. For example, in a common instant messaging software, the user of the second terminal receives a message from the system notification account, which contains the above hyperlink. The instant messaging software displays the message in rich text format, and the hyperlink can be directly clicked for operation.

[0142] After seeing the message containing the hyperlink, the user of the second terminal can trigger the acquisition of file data by clicking on the hyperlink. At this time, the second terminal device identifies that the link points to a specific file resource of the data channel application server according to the format of the hyperlink.

[0143] The second terminal device calls the built-in network request module of the system and generates an HTTP GET request for the file data according to the address information in the hyperlink. For example, for the above hyperlink "http: / / dc - server / files / contract / 20250325 / important_contract.docx", the request headers generated by the device may contain key information such as user device information and the requested file path.

[0144] After receiving the file request sent by the second terminal, the data channel application server locates the corresponding file data in the server storage system according to the file path information in the request. For example, it reads the content of the "important_contract.docx" file from the " / files / contract / 20250325 / " directory and encapsulates the read file data in an HTTP response, and returns it to the second terminal through the network. The response data may include information such as the byte stream content of the file, file type, and file size.

[0145] After receiving the HTTP response, the second terminal stores the file data according to the specified storage path. If an application program that supports this file type is installed on the device, such as an office software for opening Word documents, the device can directly associate the application program so that the user can directly open the file to view the content later.

[0146] In the terminal communication method provided by the embodiments of the present application, in a terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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, by adopting the terminal communication method provided by the embodiments of the present application, the communication barrier between the conventional terminal and the standalone DC terminal is successfully broken, and the communication interaction between the two is effectively realized, providing strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promoting the efficient development of communication technology in a complex terminal environment.

[0147] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are sequentially shown according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed 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 executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0148] Based on the same inventive concept, the embodiments of the present application also provide a terminal communication device for implementing the above-mentioned terminal communication method. The solution provided by this device to solve the problem is similar to the solution described in the above method. Therefore, the specific limitations in one or more of the following embodiments of the terminal communication device can refer to the limitations on the terminal communication method in the above text and will not be repeated here.

[0149] In an exemplary embodiment, as Figure 7 shown, a terminal communication device 700 is provided, including: a sending module 702, where:

[0150] A sending module 702, configured to, when there is a need to send file data to a second terminal, if the second terminal does not support an IP Multimedia Subsystem (IMS) independent data channel, send target data to a Media Function (MF) / Media Resource Function (MRF) through an Application Data Channel (ADC) established with the local network, so as to forward the target data to a data channel application server through the MF / MRF.

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

[0152] In one embodiment, the sending module 702 is specifically configured to:

[0153] Send an ADC establishment request to an IMS core network, where the ADC establishment request carries a first identifier for indicating an end-to-end ADC;

[0154] Receive response information sent by the IMS core network, where the response information carries a second identifier for indicating an end-to-platform ADC;

[0155] In response to the response information, send the target data to the MF / MRF through the ADC established with the local network.

[0156] In an exemplary embodiment, as Figure 8 shown, a terminal communication device 800 is provided, including a receiving module 802 and a sending module 804, where:

[0157] The receiving module 802 is configured to receive target data sent by an MF / MRF, where the target data is data sent by a first terminal to the MF / MRF through an ADC established with the local network when the second terminal does not support an IMS independent data channel, and the target data includes file data and identification information of the second terminal;

[0158] The sending module 804 is configured 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.

[0159] In an exemplary embodiment, as Figure 9 shown, a terminal communication device 900 is provided, including a receiving module 902 and an obtaining module 904, where:

[0160] A receiving module 902, configured to receive a hyperlink sent by a data channel application server, where the hyperlink is generated based on file data, and the file data is carried in target data forwarded by a media function MF / media resource function MRF to the data channel application server, and the target data is sent by a first terminal to the MF / MRF through an application data channel ADC established with the local network. The target data includes the file data and identification information of a second terminal, and the first terminal supports an IMS independent data channel;

[0161] An obtaining module 904, configured to obtain the file data from the data channel application server based on the hyperlink.

[0162] In the above terminal communication device, in a terminal communication scenario, when the second terminal is a conventional terminal that does not support IMS standalone DC, and 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 MF / MRF. 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 the embodiment of the present application successfully breaks the communication barrier between the conventional terminal and the standalone DC terminal, effectively realizes the communication interaction between the two, provides a strong solution support for the further popularization and implementation of the IMS standalone DC communication technology, and promotes the efficient development of communication technology in a complex terminal environment.

[0163] Each module in the above terminal communication device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor of the computer device in hardware form or be independent of the processor, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0164] In an exemplary embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 10As shown in the figure. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an 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 to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a terminal communication method.

[0165] Those skilled in the art can understand that Figure 10 the structure shown in the figure is only a block diagram of some structures related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0166] In one embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0167] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0168] In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0169] 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 for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0170] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, a database, or other media used in the embodiments provided in the present 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), magnetoresistive 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 be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in the present application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in the present application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., without limitation.

[0171] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, 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, it should be considered as the scope recorded in the present application.

[0172] The above-described embodiments merely represent several implementation manners of the present application. The description thereof is relatively specific and detailed, but it should not be construed as a limitation to the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A terminal communication system, characterized in that: The terminal communication system includes a first terminal, a second terminal, a media function MF / media resource function MRF and a data channel application server, the first terminal supports an IP multimedia subsystem IMS independent data channel, and the second terminal does not support an IMS independent data channel; wherein, The first terminal is configured to send target data to the MF / MRF through an application data channel ADC established with the local network when there is a need to send file data to the second terminal, wherein the target data includes the file data and identification information of the second terminal; The MF / MRF is used to forward the target data to the data channel application server; The data channel application server 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; 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, characterized in that The terminal communication system also includes an IMS core network and an IMS application server. The IMS core network is configured to send a 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, where the signaling is used to instruct the peer network to negotiate with the second terminal, and to feed back response information for the signaling, where the response information only carries the guided data channel BDC information; The IMS application server is further configured to forward the response information fed back by the peer network to the IMS core network; The IMS core network is further used to add ADC information to the response information, and send the response information with the ADC information added to the first terminal, wherein the response information with the ADC information added is used to indicate that the ADC establishment between the first terminal and the local network is completed.

3. A terminal communication method, characterized in that: Applied to a first terminal, the method includes: 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 function MF / media resource function MRF through the application data channel ADC established with the local network, so as to forward the target data to the data channel application server through the MF / MRF. The target data includes the file data and identification information of the second terminal, and 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.

4. The method according to claim 3, characterized in that If the second terminal does not support the IMS independent data channel, sending the target data to the MF / MRF through the ADC established with the local network includes: Sending an ADC establishment request to the IMS core network, where the ADC establishment request carries a first identifier, where the first identifier is used to indicate an end-to-end ADC; receiving a response message sent by the IMS core network, wherein the response message carries a second identifier, and the second identifier is used to indicate an end-to-platform ADC; In response to the response information, the target data is sent to the MF / MRF via the ADC established with the local network.

5. A terminal communication method, characterized in that: Applied to a data channel application server, the method comprises: receiving target data sent by a media function MF / media resource function MRF, wherein the target data is data sent by the first terminal to the MF / MRF through an application data channel ADC established with the local network when the second terminal does not support an IMS independent data channel, and the target data includes file data and identification information of the second terminal; 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.

6. A terminal communication method, characterized in that: Applied to a second terminal, the second terminal does not support an IP Multimedia Subsystem IMS independent data channel, the method comprising: receiving a hyperlink sent by a data channel application server, where the hyperlink is generated based on file data, where the file data is carried in target data forwarded by a media function MF / media resource function MRF to the data channel application server, where the target data is sent by a first terminal to the MF / MRF through an application data channel ADC established with a local network, where the target data includes the file data and identification information of the second terminal, and where the first terminal supports an IMS independent data channel; The file data is obtained from the data channel application server based on the hyperlink.

7. A terminal communication device, characterized in that: Applied to a first terminal, the device includes: a sending module, configured to, when there is a need to send file data to a second terminal, if the second terminal does not support an independent data channel of an IP multimedia subsystem IMS, send target data to a media function MF / media resource function MRF through an application data channel ADC established with a local network, so as to forward the target data to a data channel application server through the MF / MRF, The target data includes the file data and identification information of the second terminal, and 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.

8. A terminal communication device, characterized in that: Applied to a data channel application server, the device comprises: a receiving module, configured to receive target data sent by a media function MF / media resource function MRF, wherein the target data is data sent by the first terminal to the MF / MRF through an application data channel ADC established with the local network when the second terminal does not support an IMS independent data channel, and the target data includes file data and identification information of the second terminal; A 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.

9. A terminal communication device, characterized in that: Applied to a second terminal, the second terminal does not support an IP Multimedia Subsystem IMS independent data channel, the device includes: a receiving module, configured to receive a hyperlink sent by a data channel application server, wherein the hyperlink is generated based on file data, the file data is carried in target data forwarded by a media function MF / media resource function MRF to the data channel application server, the target data is sent by a first terminal to the MF / MRF through an application data channel ADC established with a local network, the target data includes the file data and identification information of the second terminal, and the first terminal supports an IMS independent data channel; An acquisition module is used to acquire the file data from the data channel application server based on the hyperlink.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 3 to 6 are implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 3 to 6 are implemented.

Images