WO2018133542A1 - 文件传输方法及系统、装置、电子设备、计算机存储介质 - Google Patents

文件传输方法及系统、装置、电子设备、计算机存储介质 Download PDF

Info

Publication number
WO2018133542A1
WO2018133542A1 PCT/CN2017/113124 CN2017113124W WO2018133542A1 WO 2018133542 A1 WO2018133542 A1 WO 2018133542A1 CN 2017113124 W CN2017113124 W CN 2017113124W WO 2018133542 A1 WO2018133542 A1 WO 2018133542A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
file
http
storage server
application server
Prior art date
Application number
PCT/CN2017/113124
Other languages
English (en)
French (fr)
Inventor
卞福升
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018133542A1 publication Critical patent/WO2018133542A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the present application relates to the field of Rich Media Communication (RCS), and in particular, to an RCS-based file transmission method and system, apparatus, electronic device, and computer storage medium.
  • RCS Rich Media Communication
  • RCS defines a set of service capabilities based on IP Multimedia Subsystem (IMS) and existing mobile networks, providing mobile users with enhanced address book, content sharing, file transfer, enhanced messaging and more.
  • IMS IP Multimedia Subsystem
  • the embodiment of the present application provides a file transmission method, system, device, electronic device, and computer storage medium.
  • An embodiment of the present application provides a file transmission method, where the method includes:
  • the first storage server When the first terminal does not support the Hypertext Transfer Protocol (HTTP), the first storage server establishes a message session relay protocol (MSRP) link with the first terminal, and receives the file sent by the first terminal by using the MSRP link;
  • MSRP message session relay protocol
  • the first application server sends the storage address of the file in the first storage server to the second application server.
  • the first storage server when the first terminal does not support HTTP, the first storage server establishes an MSRP link with the first terminal, and receives the file sent by the first terminal by using the MSRP link, including:
  • the first application server receives the request message sent by the first terminal, where the request message carries the file information and the MSRP link establishment information of the first terminal;
  • the first application server returns a response message to the first terminal, where the response message carries the MSRP link establishment information of the first application server;
  • the first application server After receiving the positive confirmation message returned by the first terminal, the first application server notifies the first storage server to receive the file sent by the first terminal;
  • the first storage server establishes an MSRP link with the first terminal according to the MSRP link establishment information, and receives the file sent by the first terminal by using an MSRP link;
  • the first storage server stores the received file and notifies the first application server that the file is successfully received.
  • the first application server sends the storage address of the file in the first storage server to the second application server, including:
  • the first application server stores according to the first storage server.
  • the path of the stored file generates a corresponding HTTP link
  • the first application server encapsulates the HTTP link of the file into the instant messaging body and forwards it to the second application server.
  • the embodiment of the present application further provides a file transmission method, where the method includes:
  • the second application server When receiving the instant messaging message sent by the first application server and carrying the HTTP link, the second application server queries whether the second terminal supports HTTP;
  • the second application server sends a file acquisition notification message to the second storage server, so that the second storage server acquires the file from the first storage server by using an HTTP method.
  • the second application server sends the instant messaging message to the second terminal, so that the second terminal acquires the first storage server according to the HTTP link. Document.
  • the second application server sends a file acquisition notification message to the second storage server, so that the second storage server obtains the file from the first storage server by using an HTTP method, including:
  • the second application server sends an HTTP file acquisition notification message to the second storage server
  • the second storage server sends an HTTP acquisition request message to the first storage server
  • the second storage server receives the file sent by the first storage server
  • the second storage server stores the file and notifies the second application server that the file is successfully received.
  • the method further includes:
  • the second storage server establishes an MSRP link with the second terminal, and sends the file to the second terminal by using the MSRP link.
  • the second storage server establishes an MSRP link with the second terminal, and sends the file to the second terminal by using the MSRP link, including:
  • the second application server receives the request message sent by the second terminal, where the request message carries the text.
  • the second application server returns a response message to the second terminal, where the response message carries the MSRP link establishment information of the second application server;
  • the second application server notifies the second storage server to send the file
  • the second storage server and the second terminal establish an MSRP link according to the MSRP link establishment information, and send the file to the second terminal by using the MSRP link;
  • the second storage server After the second storage server sends the file, it notifies the second application server that the file is successfully sent.
  • An embodiment of the present application provides a file transmission method, where the method includes:
  • the first terminal When the first terminal does not support HTTP, the first terminal establishes an MSRP link with the first storage server, and the first terminal sends a file to the first storage server by using the MSRP link;
  • the first application server sends the storage address of the file in the first storage server to the second application server;
  • the second application server sends the storage address to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • the method further includes:
  • the second storage server acquires the file from the first storage server by using an HTTP method
  • the second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • the file is sent by the first terminal to a second terminal;
  • the file is sent by the first terminal to the plurality of second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first end And a plurality of second terminals.
  • the method further includes:
  • the second application server acquires terminal capability information of the second terminal.
  • the second application server acquires terminal capability information of the multiple second terminals.
  • the embodiment of the present application further provides a file transmission method, where the method includes:
  • the first terminal When the first terminal supports HTTP, the first terminal sends a file to the first storage server by using an HTTP method;
  • the second storage server acquires the file from the first storage server by using an HTTP method
  • the second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • the method further includes:
  • the first application server sends the storage address of the file in the first storage server to the second application server;
  • the second application server sends the storage address to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • the file is sent by the first terminal to a second terminal;
  • the file is sent by the first terminal to the plurality of second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first terminal and a plurality of second terminals.
  • the method further includes:
  • the second application server acquires terminal capability information of the second terminal.
  • the second application server acquires terminal capability information of the multiple second terminals.
  • the embodiment of the present application further provides a file transmission system, where the system includes: a storage server, Application server; among them,
  • the storage server is configured to: when the first terminal does not support HTTP, establish an MSRP link with the first terminal, and receive, by using the MSRP link, the file sent by the first terminal;
  • the application server is configured to send, when the second terminal supports HTTP, the storage address of the file in the storage server to the second application server.
  • the application server is configured to: when the first terminal does not support HTTP, receive a request message sent by the first terminal, where the request message carries file information and MSRP link establishment information of the first terminal; Returning a response message, the response message carrying the MSRP link establishment information of the application server; after receiving the positive confirmation message returned by the first terminal, notifying the storage server to receive the file sent by the first terminal;
  • the storage server is configured to establish an MSRP link with the first terminal according to the MSRP link establishment information, and receive the file sent by the first terminal by using an MSRP link; store the received file, and notify the application server The file was received successfully.
  • the application server is configured to generate a corresponding HTTP link according to a path of a file stored in the storage server when the second terminal supports HTTP; and encapsulate the HTTP link of the file into an instant messaging message body. Forward to the second application server.
  • An embodiment of the present application provides a file transmission system, where the system includes: a storage server and an application server;
  • the application server is configured to: when receiving the instant messaging message with the HTTP link sent by the first application server, query whether the second terminal supports HTTP; and when the second terminal does not support HTTP, send the message to the storage server. Obtaining a notification message, so that the storage server acquires the file from the first storage server by using an HTTP method; and when the second terminal supports HTTP, sending the instant messaging message to the second terminal, So that the second terminal acquires the file from the first storage server according to the HTTP link.
  • the application server is configured to send HTTP to the storage server.
  • File get notification message
  • the storage server is configured to send an HTTP acquisition request message to the first storage server, receive the file sent by the first storage server, store the file, and notify the second application server that the file is successfully received.
  • the storage server is configured to establish an MSRP link with the second terminal, and send the file to the second terminal by using the MSRP link.
  • the application server is configured to receive a request message sent by the second terminal, where the request message carries the file information and the MSRP link establishment information of the terminal, and returns a response message to the second terminal, where the response message carries the The MSRP link establishment information of the application server; receiving a positive confirmation message sent by the second terminal; notifying the storage server to send the file;
  • the storage server is configured to establish an MSRP link with the second terminal according to the MSRP link establishment information, and send a file to the second terminal by using the MSRP link. After the file is sent, the second application server is notified that the file is successfully sent.
  • the embodiment of the present application further provides a file transmission system, where the system includes: a first terminal, a first storage server, a first application server, a second terminal, and a second application server;
  • the first terminal is configured to: when the first terminal does not support HTTP, the first terminal establishes an MSRP link with the first storage server, and the first terminal sends the first terminal to the first storage server by using the MSRP link. Send File;
  • the first application server is configured to: when the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server;
  • the second application server is configured to send the storage address to the second terminal
  • the second terminal is configured to acquire the file from the first storage server by using an HTTP method according to the storage address.
  • the system further includes:
  • a second storage server configured to: when the second terminal does not support HTTP, the second storage server acquires the file from the first storage server by using an HTTP method; and the second storage server establishes with the second terminal MSRP link;
  • the second terminal is configured to acquire the file from the second storage server by using the MSRP link.
  • the file is sent by the first terminal to a second terminal;
  • the file is sent by the first terminal to the plurality of second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first terminal and a plurality of second terminals.
  • the second application server is configured to acquire terminal capability information of the second terminal, or acquire terminal capability information of the multiple second terminals.
  • the embodiment of the present application provides a file transmission system, where the system includes: a first terminal, a first storage server, a second terminal, and a second storage server;
  • the first terminal is configured to: when the first terminal supports HTTP, the first terminal sends a file to the first storage server by using an HTTP method;
  • the second storage server is configured to: when the second terminal does not support HTTP, the second storage server acquires the file from the first storage server by using an HTTP method; and establishes an MSRP link with the second terminal;
  • the second terminal is configured to acquire the file from the second storage server by using the MSRP link.
  • system further includes: a first application server and a second application server; wherein
  • the first application server is configured to: when the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server;
  • the second application server is configured to send the storage address to the second terminal
  • the second terminal is configured to acquire the file from the first storage server by using an HTTP method according to the storage address.
  • the file is sent by the first terminal to a second terminal;
  • the file is sent by the first terminal to the plurality of second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first terminal and a plurality of second terminals.
  • the second application server is configured to acquire terminal capability information of the second terminal, or acquire terminal capability information of the multiple second terminals.
  • the embodiment of the present application further provides a file transmission device, where the device includes:
  • a generating unit configured to generate an HTTP link according to a storage address of the file in the first storage server when the first terminal does not support HTTP;
  • a packaging unit configured to encapsulate the HTTP link into an instant messaging message
  • a communication unit configured to send the communication message to a second application server
  • the communication unit is configured to: when the first terminal supports HTTP, the first application server receives the instant messaging message sent by the first terminal and carries the HTTP link, and sends the instant messaging message to the second application server.
  • An embodiment of the present application provides a file transmission apparatus, where the apparatus includes:
  • a communication unit configured to receive an instant messaging message sent by the first application server and having an HTTP link
  • the query unit is configured to query whether the second terminal supports HTTP
  • the communication unit is configured to: when the second terminal does not support HTTP, send a file acquisition notification message to the second storage server, so that the second storage server acquires the information from the first storage server by using an HTTP method. a file; when the second terminal supports HTTP, the instant messaging message is sent to the second terminal, so that the second terminal is according to the The HTTP link retrieves the file from the first storage server.
  • the embodiment of the present application further provides an electronic device, where the electronic device includes a processor and a memory, where the computer stores computer program instructions, when the processor executes the computer program instructions, the processor is configured to execute The file transfer method of any of the above.
  • the embodiment of the present application further provides a computer storage medium storing a computer program configured to execute the file transfer method.
  • the first terminal in a case, when the first terminal does not support HTTP, the first terminal establishes an MSRP link with the first storage server, and the first terminal passes the MSRP link.
  • Sending a file to the first storage server when the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server; the second application server Sending the storage address to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • the first terminal when the first terminal supports HTTP, the first terminal sends a file to the first storage server by using an HTTP method; when the second terminal does not support HTTP, the second storage server uses the HTTP mode from the The first storage server acquires the file; the second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • terminals that implement the two protocols can transfer files to each other, reduce network traffic, and save resources of the storage server.
  • FIG. 1 is a schematic flowchart 1 of a file transmission method according to an embodiment of the present application.
  • FIG. 2 is a second schematic flowchart of a file transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart 3 of a file transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart 4 of a file transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart 5 of a file transmission method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart 6 of a file transmission method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram 1 of a point-to-point file transmission process defined by the specification.
  • Figure 8 is a schematic diagram 2 of the point-to-point file transmission process defined by the specification.
  • FIG. 9 is a schematic diagram 1 of a point-to-point file transmission process according to an embodiment of the present application.
  • Figure 10 is a schematic diagram 3 of the point-to-point file transmission process defined by the specification.
  • FIG. 11 is a second schematic diagram of a point file transmission process according to an embodiment of the present application.
  • Figure 12 is a schematic diagram of a point-to-multipoint file transfer process defined by the specification.
  • FIG. 13 is a schematic diagram of a point-to-multipoint file transmission process according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a flow of a chat room file transmission according to an embodiment of the present application.
  • 16 is a first structural diagram of a file transmission system according to an embodiment of the present application.
  • 17 is a second structural diagram of a file transmission system according to an embodiment of the present application.
  • FIG. 18 is a first schematic structural diagram of a file transmission apparatus according to an embodiment of the present application.
  • FIG. 19 is a second structural diagram of a file transmission apparatus according to an embodiment of the present application.
  • INVITE indicates that the calling user initiates a session request and invites other users to join a session.
  • the client verifies to the server that it has received the final response to the INVITE request.
  • BYE Indicates to terminate an already established call.
  • REGISTER Indicates that the client registers with the SIP server.
  • a capability detection message is used to detect the capabilities of the other terminal.
  • MESSAG used to send instant messages, can not keep the session, the content size is limited, generally 900 bytes.
  • UE User Equipment, responsible for initiating or receiving group chat messages, such as mobile phones, PADs, and the like.
  • IM_AS Instant Messenger Application Server, which is responsible for receiving the message submitted by the terminal and delivering it according to the address of the recipient. If the destination is the UE, it sends a chat message to the AS to which the destination belongs.
  • UE_A, UE_B, and UE_C are three UE terminals.
  • IM_AS_A, IM_AS_B, and IM_AS_C are the chat ASs to which UE_A, UE_B, and UE_C belong, respectively.
  • GC_AS_A, GC_AS_B, and IM_AS_C are the group chat AS to which UE_A, UE_B, and UE_C belong, respectively.
  • HTTP_MSRP_A, HTTP_MSRP_B, and HTTP_MSRP_C are the storage servers corresponding to the IM_AS_A, IM_AS_B, and IM_AS_C sides, and provide HTTP and MSRP services externally.
  • RCS5.0 and the previous specifications define the method of storing and forwarding RCS files.
  • the files are transmitted through the combination of SIP and MSRP, and the RCS application server (AS, Application Server) to which the sender belongs is received. After the new file is saved, store it first. Then, it is retransmitted to the RCS AS to which the pick-up party belongs through SIP and MSRP, and the RCS AS to which the receiver belongs receives the file and then forwards it to the receiver terminal.
  • AS Application Server
  • the server generates a corresponding HTTP Uniform Relocation Locator (URL, Uniform Resoure Locator), and then sends the HTTP URL to the receiver through the RCS AS, and the receiver terminal obtains the file content through the HTTP URL to the HTTP server, thereby avoiding the RCS AS. Transfer file content.
  • URL Uniform Relocation Locator
  • the intermediate core network element such as the Call Session Control Function (CSCF, Call Session Control Function), is omitted.
  • CSCF Call Session Control Function
  • the file transmission method includes:
  • Step 101 When the first terminal does not support HTTP, the first terminal establishes an MSRP link with the first storage server, and the first terminal sends a file to the first storage server by using the MSRP link.
  • the first type the file is sent by the first terminal to a second terminal;
  • the second type the file is sent by the first terminal to multiple second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first terminal and a plurality of second terminals.
  • the specific processes are:
  • the first terminal is UE_A
  • the first application server is IM_AS_A
  • the first storage server is HTTP_MSRP_A.
  • UE_A sends an INVITE message to IM_AS_A, and carries file information and terminal MSRP link establishment information through the SDP;
  • IM_AS_A UE_A returns a 200 OK response, carries the MSRP link establishment information on the IM_AS_A side;
  • UE_A receives the response message, and returns an ACK;
  • IM_AS_A notifies the HTTP_MSRP_A to receive the file;
  • UE_A and HTTP_MSRP_A establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and send it through the MSRP link.
  • File; HTTP_MSRP_A receives the storage file and then notifies the IM_AS_A file that it was successfully received.
  • the foregoing process is a specific process in which the first terminal sends a file to the first storage server through the
  • Step 102 When the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server.
  • the second terminal is UE_B
  • the second application server is IM_AS_B
  • the IM_AS_A generates a corresponding HTTP URL according to the HTTP_MSRP_A storage file path, and the HTTP URL and corresponding file information (file type, file size, file name), etc.
  • the content is encapsulated into the Message body and then forwarded to IM_AS_B.
  • IM_AS_B determines that the local UE_B supports HTTP, IM_AS_B sends the Message to the UE_B; UE_B parses the received Message message to obtain an HTTP URL; UE_B sends an HTTP GET request to the HTTP_MSRP_A server to obtain the file content; and the HTTP_MSRP_A server returns the file content to the UE_B.
  • Step 103 The second application server sends the storage address to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • the method further includes:
  • the second storage server acquires the file from the first storage server by using an HTTP method
  • the second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • IM_AS_B sends an HTTP file acquisition notification to HTTP_MSRP_B; HTTP_MSRP_B sends an HTTP GET request to HTTP_MSRP_A; HTTP_MSRP_A returns the file content; HTTP_MSRP_B file acquisition is completed, and IM_AS_B is notified; IM_AS_B sends an INVITE message to UE_B.
  • the information about the received file is included.
  • the UE_B receives the INVITE message, and the UB_B sends an INVITE message to the IM_AS_B.
  • the SDP carries the information about the received file and the MSRP link establishment information.
  • the IM_AS_B returns a 200 OK response and carries the IM_AS_B side MSRP.
  • Chain information UE_B receives the response message and returns the ACK;
  • IM_AS_B notifies the HTTP_MSRP_B to send the file;
  • UE_B and HTTP_MSRP_B establish the MSRP link MSRP_2 according to the SIP negotiation link establishment information, and receive the file content through the MSRP link; notify the IM_AS_B after the HTTP_MSRP_B file is sent. The file was sent successfully.
  • the method further includes: the second application server acquiring the terminal capability information of the second terminal; or the second application server acquiring the terminal capability information of the multiple second terminals.
  • the second application server acquires terminal capability information of the second terminal, and when the second terminal supports HTTP, performs a corresponding HTTP process; when the second terminal does not support HTTP, performs SIP+ The corresponding process of MSRP.
  • the second application server acquires terminal capability information of the plurality of second terminals, performs a corresponding HTTP process for the second terminal supporting HTTP, and performs SIP for the second terminal that does not support HTTP. +MSRP corresponding process.
  • the file transmission method includes:
  • Step 201 When the first terminal supports HTTP, the first terminal sends a file to the first storage server by using an HTTP method.
  • the first type the file is sent by the first terminal to a second terminal;
  • the second type the file is sent by the first terminal to multiple second terminals;
  • the file is sent by the first terminal to the first group, and the first group includes the first terminal and a plurality of second terminals.
  • the specific processes are:
  • the first terminal is UE_A
  • the first application server is IM_AS_A
  • the first storage server is HTTP_MSRP_A.
  • UE_A transmits the file content to HTTP_MSRP_A through an HTTP POST request
  • HTTP_MSRP_A receives, stores, and stores according to the file.
  • the location generates a corresponding HTTP URL, returns a 200 OK response, and carries the HTTP URL corresponding to the file
  • UE_A encapsulates the HTTP URL and the corresponding file information (file type, file size, file name) and the like into the Message message body, and then sends it to IM_AS_A. .
  • Step 202 When the second terminal does not support HTTP, the second storage server acquires the file from the first storage server by using an HTTP method.
  • IM_AS_A receives the Message message and forwards it to IM_AS_B; IM_AS_B parses the Message message, obtains the HTTP URL of the file, and queries the local terminal UE_B registration capability. If HTTP file transmission is not supported, IM_AS_B sends an HTTP file acquisition notification to HTTP_MSRP_B; HTTP_MSRP_B HTTP_MSRP_A sends an HTTP GET request; HTTP_MSRP_A returns the contents of the file.
  • Step 203 The second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • the HTTP_MSRP_B file is obtained, and the IM_AS_B is sent.
  • the IM_AS_B sends an INVITE message to the UE_B, including the information about the received file.
  • the IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side.
  • the UE_B receives the response message and returns an ACK.
  • the IM_AS_B notifies the HTTP_MSRP_B.
  • UE_B and HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link; after the HTTP_MSRP_B file is sent, notify the IM_AS_B that the file is successfully sent.
  • the method further includes:
  • the first application server sends the storage address of the file in the first storage server to the second application server;
  • the second application server sends the storage address to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • IM_AS_B queries the local terminal UE_B registration capability, UE_B supports HTTP file transmission, and then forwards the Message message to UE_B; UE_B parses the received Message message to obtain an HTTP URL; UE_B sends an HTTP GET request to the HTTP_MSRP_A server to obtain file content; HTTP_MSRP_A server Returns the contents of the file to UE_B.
  • the method further includes: the second application server acquiring the terminal capability information of the second terminal; or the second application server acquiring the terminal capability information of the multiple second terminals.
  • the second application server acquires terminal capability information of the second terminal, and when the second terminal supports HTTP, performs a corresponding HTTP process; when the second terminal does not support HTTP, performs SIP+ The corresponding process of MSRP.
  • the second application server obtains multiple The terminal capability information of the second terminal performs a corresponding HTTP process for the second terminal supporting HTTP, and performs a corresponding process of the SIP+MSRP for the second terminal that does not support HTTP.
  • FIG. 3 is a schematic flowchart of a file transmission method according to an embodiment of the present disclosure. The example is applied to a first application server. As shown in FIG. 3, the file transmission method includes:
  • Step 301 When the first terminal does not support HTTP, the first application server generates an HTTP link according to the storage address of the file in the first storage server; the first application server encapsulates the HTTP link into an instant messaging message, and sends the HTTP link. Give the second application server.
  • Step 302 When the first terminal supports HTTP, the first application server receives the instant messaging message sent by the first terminal and carries the HTTP link, and sends the instant messaging message to the second application server.
  • the file transmission method includes:
  • Step 401 When the second application server receives the instant messaging message sent by the first application server and carries the HTTP link, the second application server queries whether the second terminal supports HTTP.
  • Step 402 When the second terminal does not support HTTP, the second application server sends a file acquisition notification message to the second storage server, so that the second storage server obtains the first storage server by using an HTTP method. The file.
  • Step 403 When the second terminal supports HTTP, the second application server sends the instant messaging message to the second terminal, so that the second terminal is from the first storage server according to the HTTP link. Get the file in .
  • the file transfer method includes:
  • Step 501 When the first terminal does not support the Hypertext Transfer Protocol (HTTP), the first storage server establishes a message session relay protocol (MSRP) link with the first terminal, and receives, by using the MSRP link, the first terminal, file.
  • MSRP message session relay protocol
  • the first storage server when the first terminal does not support HTTP, the first storage server establishes an MSRP link with the first terminal, and receives the file sent by the first terminal by using the MSRP link, including:
  • the first application server receives the request message sent by the first terminal, where the request message carries the file information and the MSRP link establishment information of the first terminal;
  • the first application server returns a response message to the first terminal, where the response message carries the MSRP link establishment information of the first application server;
  • the first application server After receiving the positive confirmation message returned by the first terminal, the first application server notifies the first storage server to receive the file sent by the first terminal;
  • the first storage server establishes an MSRP link with the first terminal according to the MSRP link establishment information, and receives the file sent by the first terminal by using an MSRP link;
  • the first storage server stores the received file and notifies the first application server that the file is successfully received.
  • Step 502 When the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server.
  • the first application server when the second terminal supports the HTTP, sends the storage address of the file in the first storage server to the second application server, including:
  • the first application server When the second terminal supports HTTP, the first application server generates a corresponding HTTP link according to the path of the file stored in the first storage server;
  • the first application server encapsulates the HTTP link of the file into the instant messaging body Send to the second application server.
  • FIG. 6 is a schematic flowchart diagram of a file transmission method according to an embodiment of the present disclosure. As shown in FIG. 6, the file transmission method includes:
  • Step 601 When the second application server receives the instant messaging message sent by the first application server and carries the HTTP link, the second application server queries whether the second terminal supports HTTP.
  • Step 602 When the second terminal does not support HTTP, the second application server sends a file acquisition notification message to the second storage server, so that the second storage server acquires the first storage server by using an HTTP method.
  • the file The file.
  • the second application server sends a file acquisition notification message to the second storage server, so that the second storage server obtains the file from the first storage server by using an HTTP method, including:
  • the second application server sends an HTTP file acquisition notification message to the second storage server
  • the second storage server sends an HTTP acquisition request message to the first storage server
  • the second storage server receives the file sent by the first storage server
  • the second storage server stores the file and notifies the second application server that the file is successfully received.
  • the method further includes:
  • the second storage server establishes an MSRP link with the second terminal, and sends the file to the second terminal by using the MSRP link.
  • the second application server receives the request message sent by the second terminal, where the request message carries the file information and the MSRP link establishment information of the terminal;
  • the second application server returns a response message to the second terminal, where the response message carries the MSRP link establishment information of the second application server;
  • the second application server notifies the second storage server to send the file
  • the second storage server and the second terminal establish an MSRP link according to the MSRP link establishment information, and Sending a file to the second terminal by using the MSRP link;
  • the second storage server After the second storage server sends the file, it notifies the second application server that the file is successfully sent.
  • Step 603 When the second terminal supports HTTP, the second application server sends the instant messaging message to the second terminal, so that the second terminal is from the first storage server according to the HTTP link. Get the file in .
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • UE_A sends a file to UE_B.
  • UE_A supports the RCS6.0 specification and UE_B supports the RCS6.0 specification.
  • Step 1 UE_A sends an OPTION capability detection message to UE_B.
  • Step 2 UE_B returns the capability of the terminal
  • Step 3 UE_A obtains the UE_B terminal capability, UE_B supports HTTP file transmission; UE_A sends the file by HTTP, and UE_A transmits the file content to HTTP_MSRP_A through the HTTP POST request;
  • Step 4 HTTP_MSRP_A receives and stores the file, and generates a corresponding HTTP URL according to the file storage location, returns a 200 OK response, and carries the HTTP URL corresponding to the file;
  • Step 5 UE_A encapsulates the HTTP URL and the corresponding file information (file type, file size, file name) and the like into the Message message body, and then sends it to IM_AS_A.
  • Step 6 IM_AS_A receives the Message message and forwards it to IM_AS_B.
  • UE_A sends a file to UE_B.
  • UE_A or UE_B does not support the RCS6.0 specification.
  • Step 1 UE_A sends an OPTION capability detection message to UE_B.
  • Step 2 UE_B returns the capability of the terminal
  • Step 3 UE_A obtains the UE_B terminal capability. If UE_B does not support HTTP file transmission or UE_A does not support HTTP file transmission; UE_A sends a file through SIP+MSRP, and UE_A sends an INVITE message to IM_AS_A through session description protocol (SDP, Session Description) Protocol) carrying file information and terminal MSRP link establishment information;
  • SDP Session Description
  • Step 4 IM_AS_A returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_A side;
  • Step 5 UE_A receives the response message and returns an ACK.
  • Step 6 IM_AS_A notifies HTTP_MSRP_A to receive the file
  • Step 7 The UE_A and the HTTP_MSRP_A establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and send the file content through the MSRP link.
  • Step 8 HTTP_MSRP_A receives the storage file, and then notifies the IM_AS_A file to be successfully received;
  • IM_AS_A sends an INVITE message to IM_AS_B, and carries the file information and the MSRP-building information on the IM_AS_A side through the SDP;
  • Step 9 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 10 IM_AS_A receives the response message and returns an ACK.
  • Step 11 IM_AS_A notifies HTTP_MSRP_A to send the file;
  • Step 12 IM_AS_B notifies HTTP_MSRP_B to receive the file
  • Step 13 HTTP_MSRP_A and HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation;
  • Step 14 HTTP_MSRP_A transmits the file content to the HTTP_MSRP_B through the MSRP_2 link;
  • Step 15 HTTP_MSRP_A sends the file, and then notifies the IM_AS_A file to be successfully sent;
  • Step 16 HTTP_MSRP_B receives the storage file and then notifies the IM_AS_B file that the reception was successful.
  • UE_A sends a file to UE_B.
  • UE_A does not support the RCS6.0 specification, and UE_B supports the RCS6.0 specification.
  • Step 1 UE_A sends an OPTION capability detection message to UE_B.
  • Step 2 UE_B returns the capability of the terminal
  • Step 3 UE_A obtains UE_B terminal capability, UE_B supports HTTP file transmission, but UE_A does not support HTTP file transmission; UE_A sends a file through SIP+MSRP, UE_A sends an INVITE message to IM_AS_A, and carries file information and terminal MSRP link establishment information through SDP. ;
  • Step 4 IM_AS_A returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_A side;
  • Step 5 UE_A receives the response message and returns an ACK.
  • Step 6 IM_AS_A notifies HTTP_MSRP_A to receive the file
  • Step 7 The UE_A and the HTTP_MSRP_A establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and send the file content through the MSRP link.
  • Step 8 HTTP_MSRP_A receives the storage file, and then notifies the IM_AS_A file to receive successfully; IM_AS_A sends an OPTION message to UE_B;
  • Step 9 UE_B returns the capability of the terminal
  • Step 10 IM_AS_A knows that UE_B supports HTTP file transmission.
  • IM_AS_A generates a corresponding HTTP URL according to the HTTP_MSRP_A storage file path, and encapsulates the HTTP URL and corresponding file information (file type, file size, file name) and the like into the message body. It is then forwarded to IM_AS_B.
  • IM_AS_A In the standard process, if UE_A does not support HTTP file transmission, IM_AS_A first receives and stores the file through SIP+MSRP, and then forwards it to IM_AS_B through SIP+MSRP. IM_AS_B receives and stores files, and IM_AS_A and IM_AS_B sides respectively receive and store. document content.
  • the network bandwidth consumption between IM_AS_A and IM_AS_B is large, and the performance and capacity of the storage device on the HTTP_MSRP_B side are occupied.
  • the UE_B terminal capability is detected first. If the UE_B supports the HTTP file transmission, the message is generated and sent to the IM_AS_B.
  • the message contains only the HTTP URL and the file related information, and does not include
  • the content of the file reduces the network transmission and file storage of the file contents between IM_AS_A and IM_AS_B, which greatly saves the network bandwidth between IM_AS_A and IM_AS_B, and saves the performance and capacity of the storage device on the HTTP_MSRP_B side.
  • UE_B receives the file transmitted by UE_A.
  • UE_A does not support the RCS6.0 specification, and UE_B supports the RCS6.0 specification.
  • Step 1 IM_AS_B receives the INVITE message sent by IM_AS_A, parses the SDP to obtain file related information, and MS_AS_A side MSRP link establishment information;
  • Step 2 IM_AS_B returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_B side;
  • Step 3 IM_AS_A receives the response message and returns an ACK.
  • Step 4 IM_AS_A notifies HTTP_MSRP_A to send the file
  • Step 5 IM_AS_B notifies HTTP_MSRP_B to receive the file
  • Step 6 HTTP_MSRP_A and HTTP_MSRP_B establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation; HTTP_MSRP_A transmits the file content to the HTTP_MSRP_B through the MSRP_1 link;
  • Step 7 HTTP_MSRP_A sends the file, and then notifies the IM_AS_A file that the transmission is successful.
  • Step 8 HTTP_MSRP_B receives the storage file, and then notifies the IM_AS_B file that the reception is successful;
  • Step 9 The IM_AS_B sends an INVITE message to the UE_B, which includes information about the received file.
  • Step 10 After receiving the INVITE message, the UE_B actively receives the file, and the UB_B sends an INVITE message to the IM_AS_B, and carries the information about the received file and the MSRP link establishment information of the terminal through the SDP.
  • Step 11 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 12 UE_B receives the response message and returns an ACK.
  • Step 13 IM_AS_B notifies HTTP_MSRP_B to send the file
  • Step 14 The UE_B and the HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link.
  • Step 15 After the HTTP_MSRP_B file is sent, notify IM_AS_B that the file is successfully sent.
  • UE_B receives the file transmitted by UE_A.
  • UE_A does not support the RCS6.0 specification, and UE_B supports the RCS6.0 specification.
  • the point-to-point file transmission process of the embodiment of the present application is as shown in FIG. 11 and is described in detail as follows:
  • Step 1 IM_AS_B receives the file transfer Message message
  • Step 2 IM_AS_B forwards the Message message to UE_B;
  • Step 3 UE_B parses the received Message message to obtain an HTTP URL; UE_B sends an HTTP GET request to the HTTP_MSRP_A server to obtain the file content;
  • Step 4 The HTTP_MSRP_A server returns the file content to UE_B.
  • the end-to-end transmission process uses SIP and MSRP transmission.
  • the IM_AS_A is forwarded to the IM_AS_B through the SIP+MSRP.
  • the IM_AS_B receives and stores the file.
  • the IM_AS_B is sent to the UE_B through the SIP+MSRP.
  • the IM_AS_B side also receives and stores the file contents.
  • the network bandwidth consumption between IM_AS_A and IM_AS_B is large, and the performance and capacity of the storage device on the HTTP_MSRP_B side are occupied.
  • the IM_AS_B receives the Message message of the IM_AS_A, and then directly forwards the Message message to the UE_B.
  • the Message message only includes the HTTP URL and the file related information, does not include the file content, and reduces the file content between the IM_AS_A and the IM_AS_B.
  • the network transmission and file storage greatly save the network bandwidth between IM_AS_A and IM_AS_B, and save the performance and capacity of the HTTP_MSRP_B side storage device.
  • the UE_A group sends files to UE_B and UE_C.
  • UE_B does not support the RCS6.0 specification
  • UE_A, UE_C supports the RCS6.0 specification.
  • Step 1 UE_A sends an OPTION capability detection message to UE_B and UE_C.
  • Step 2 UE_B and UE_C return the capability of the terminal;
  • Step 3 UE_A obtains UE_B and UE_C terminal capabilities. If UE_A does not support HTTP file transmission; UE_A sends a file through SIP+MSRP, UE_A sends an INVITE message to IM_AS_A, and carries file information and terminal MSRP link establishment information through SDP;
  • Step 4 IM_AS_A returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_A side;
  • Step 5 UE_A receives the response message and returns an ACK.
  • Step 6 IM_AS_A notifies HTTP_MSRP_A to receive the file
  • Step 7 UE_A and HTTP_MSRP_A establish MSRP according to the establishment information of the SIP negotiation. Link MSRP_1 and send the file content through the MSRP link;
  • Step 8 HTTP_MSRP_A receives the storage file, and then notifies the IM_AS_A file to be successfully received;
  • IM_AS_A sends an INVITE message to IM_AS_B, and carries the file information and IM_AS_A MSRP link establishment information through the SDP;
  • Step 9 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 10 IM_AS_A receives the response message and returns an ACK.
  • Step 11 IM_AS_A notifies HTTP_MSRP_A to send the file;
  • Step 12 IM_AS_B notifies HTTP_MSRP_B to receive the file
  • Step 13 HTTP_MSRP_A and HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation;
  • Step 14 HTTP_MSRP_A transmits the file content to the HTTP_MSRP_B through the MSRP_2 link;
  • Step 15 HTTP_MSRP_A sends the file, and then notifies the IM_AS_A file to be successfully sent;
  • Step 16 HTTP_MSRP_B receives the storage file, and then notifies the IM_AS_B file that the reception is successful;
  • Step 17 The IM_AS_B sends an INVITE message to the UE_B, which includes information about the received file.
  • Step 18 After receiving the INVITE message, the UE_B actively receives the file, and the UB_B sends an INVITE message to the IM_AS_B, and carries the information about the received file and the MSRP link establishment information of the terminal through the SDP.
  • Step 19 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 20 UE_B receives the response message and returns an ACK.
  • Step 21 IM_AS_B notifies HTTP_MSRP_B to send the file;
  • Step 22 The UE_B and the HTTP_MSRP_B establish an MSRP link MSRP_3 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link.
  • Step 23 After the HTTP_MSRP_B file is sent, notify IM_AS_B that the file is successfully sent.
  • Steps 24 to 32 In the same manner as Steps 8 to 23, the IM_AS_A forwards the file to the IM_AS_C through the SIP+MSRP, and the IM_AS_C sends the file to the UE_C.
  • the UE_A group sends files to UE_B and UE_C.
  • UE_B supports the RCS6.0 specification
  • UE_A does not support the RCS6.0 specification.
  • Step 1 UE_A transmits the file content to HTTP_MSRP_A through an HTTP POST request;
  • Step 2 HTTP_MSRP_A receives and stores the file, and generates a corresponding HTTP URL according to the file storage location, returns a 200 OK response, and carries the HTTP URL corresponding to the file;
  • Step 3 UE_A encapsulates the HTTP URL and the corresponding file information (file type, file size, file name) and the like into the message body, and then sends it to IM_AS_A;
  • Step 4 IM_AS_A receives the Message message and forwards it to IM_AS_B.
  • Step 5 IM_AS_B parses the Message message, obtains the HTTP URL of the file, and queries the local terminal UE_B registration capability. If HTTP file transmission is not supported, IM_AS_B sends an HTTP file acquisition notification to HTTP_MSRP_B.
  • Step 6 HTTP_MSRP_B sends an HTTP GET request to HTTP_MSRP_A;
  • Step 7 HTTP_MSRP_A returns the file content
  • Step 8 The HTTP_MSRP_B file is obtained, and the IM_AS_B is notified.
  • Step 9 IM_AS_B sends an INVITE message to UE_B, including the received file related information. interest;
  • Step 10 After receiving the INVITE message, the UE_B actively receives the file, and the UB_B sends an INVITE message to the IM_AS_B, and carries the information about the received file and the MSRP link establishment information of the terminal through the SDP.
  • Step 11 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 12 UE_B receives the response message and returns an ACK.
  • Step 13 IM_AS_B notifies HTTP_MSRP_B to send the file
  • Step 14 The UE_B and the HTTP_MSRP_B establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link.
  • Step 15 After the HTTP_MSRP_B file is sent, notify IM_AS_B that the file is successfully sent.
  • Step 16 IM_AS_A forwards the Message message to IM_AS_C;
  • Step 17 IM_AS_C queries the local terminal UE_C registration capability, and UE_C supports HTTP file transmission, and then forwards the Message message to UE_C;
  • Step 18 UE_C parses the received Message message to obtain an HTTP URL; UE_C sends an HTTP GET request to the HTTP_MSRP_A server to obtain the file content;
  • Step 19 The HTTP_MSRP_A server returns the file content to UE_C.
  • Point-to-multipoint file transfer In the standard process, if a terminal does not support HTTP file transmission, all end-to-end transmission processes are transmitted by SIP and MSRP.
  • the IM_AS_A is forwarded to the IM_AS_B/C through the SIP+MSRP.
  • the IM_AS_B/C receives and stores the file.
  • the IM_AS_B/C is sent to the UE_B/C through the SIP+MSRP.
  • the IM_AS_B/C side needs to receive and store the file contents.
  • the network bandwidth consumption between IM_AS_A, IM_AS_B, and IM_AS_C is large, and the performance and capacity of the HTTP_MSRP_B/C side storage device are occupied.
  • the receiver terminal UE_C supports HTTP file transmission.
  • the sender UE_A and the receiver UE_C adopt the HTTP file transfer mode.
  • IM_AS_A and IM_AS_C do not need to transfer file contents, and IM_AS_C does not need to store file contents, which greatly saves the network bandwidth between IM_AS_A and IM_AS_C, and saves the HTTP_MSRP_C side.
  • the performance and capacity of the storage device is not need to transfer file contents.
  • UE_A, UE_B, and UE_C belong to one chat room, and the chat room belongs to GC_AS_A.
  • UE_A sends a file in the chat room.
  • UE_B does not support the RCS6.0 specification
  • UE_A, UE_C supports the RCS6.0 specification.
  • Step 1 Since UE_A cannot ensure that all members of the chat room support HTTP file transmission, it can only transmit by SIP+MSRP; UE_A sends the file through SIP+MSRP, UE_A sends INVITE message to IM_AS_A/GC_AS_A, and carries file information through SDP and Terminal MSRP link establishment information;
  • Step 2 IM_AS_A/GC_AS_A returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_A/GC_AS_A side;
  • Step 3 UE_A receives the response message and returns an ACK.
  • Step 4 IM_AS_A/GC_AS_A notifies HTTP_MSRP_A to receive the file;
  • Step 5 The UE_A and the HTTP_MSRP_A establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and send the file content through the MSRP link.
  • Step 6 HTTP_MSRP_A receives the storage file, and then notifies the IM_AS_A/GC_AS_A file to be successfully received; IM_AS_A/GC_AS_A sends an INVITE message to IM_AS_B, and carries the file information and IM_AS_A/GC_AS_A MSRP link establishment information through the SDP;
  • Step 7 IM_AS_B returns a 200 OK response, carrying the MSRP link establishment information on the IM_AS_B side;
  • Step 8 IM_AS_A/GC_AS_A receives the response message and returns an ACK.
  • Step 9 IM_AS_A/GC_AS_A notifies HTTP_MSRP_A to send the file;
  • Step 10 IM_AS_B notifies HTTP_MSRP_B to receive the file
  • Step 11 HTTP_MSRP_A and HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation;
  • Step 12 HTTP_MSRP_A transmits the file content to the HTTP_MSRP_B through the MSRP_2 link;
  • Step 13 HTTP_MSRP_A sends the file, and then notifies the IM_AS_A/GC_AS_A file to be successfully sent;
  • Step 14 HTTP_MSRP_B receives the storage file, and then notifies the IM_AS_B file that the reception is successful;
  • Step 15 The IM_AS_B sends an INVITE message to the UE_B, which includes information about the received file.
  • Step 16 After receiving the INVITE message, the UE_B actively receives the file, and the UB_B sends an INVITE message to the IM_AS_B, and carries the information about the received file and the MSRP link establishment information of the terminal through the SDP.
  • Step 17 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 18 UE_B receives the response message and returns an ACK.
  • Step 19 IM_AS_B notifies HTTP_MSRP_B to send the file;
  • Step 20 The UE_B and the HTTP_MSRP_B establish an MSRP link MSRP_2 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link.
  • Step 21 After the HTTP_MSRP_B file is sent, notify IM_AS_B that the file is successfully sent.
  • Steps 22 to 30 In the same manner as step 6 to step 21, IM_AS_A/GC_AS_A forwards the file to IM_AS_C through SIP+MSRP, and IM_AS_C sends the file to UE_C.
  • UE_A, UE_B, and UE_C belong to one chat room, and the chat room belongs to GC_AS_A.
  • UE_A sends a file in the chat room.
  • UE_B does not support the RCS6.0 specification
  • UE_A, UE_C supports the RCS6.0 specification.
  • the group chat file transmission process in the embodiment of the present application is as described in FIG. 15 and is described in detail as follows:
  • Step 1 UE_A transmits the file content to HTTP_MSRP_A through an HTTP POST request;
  • Step 2 HTTP_MSRP_A receives and stores the file, and generates a corresponding HTTP URL according to the file storage location, returns a 200 OK response, and carries the HTTP URL corresponding to the file;
  • Step 3 UE_A encapsulates the HTTP URL and the corresponding file information (file type, file size, file name) and the like into the message body, and then sends it to IM_AS_A/GC_AS_A;
  • Step 4 IM_AS_A/GC_AS_A receives the Message message and forwards it to IM_AS_B.
  • Step 5 IM_AS_B parses the Message message, obtains the HTTP URL of the file, and queries the local terminal UE_B registration capability. If HTTP file transmission is not supported, IM_AS_B sends an HTTP file acquisition notification to HTTP_MSRP_B.
  • Step 6 HTTP_MSRP_B sends an HTTP GET request to HTTP_MSRP_A;
  • Step 7 HTTP_MSRP_A returns the file content
  • Step 8 The HTTP_MSRP_B file is obtained, and the IM_AS_B is notified.
  • Step 9 The IM_AS_B sends an INVITE message to the UE_B, which includes information about the received file.
  • Step 10 After receiving the INVITE message, the UE_B actively receives the file, and the UB_B sends an INVITE message to the IM_AS_B, and carries the information about the received file and the MSRP link establishment information of the terminal through the SDP.
  • Step 11 IM_AS_B returns a 200 OK response, and carries the MSRP link establishment information on the IM_AS_B side;
  • Step 12 UE_B receives the response message and returns an ACK.
  • Step 13 IM_AS_B notifies HTTP_MSRP_B to send the file
  • Step 14 The UE_B and the HTTP_MSRP_B establish an MSRP link MSRP_1 according to the establishment information of the SIP negotiation, and receive the file content through the MSRP link.
  • Step 15 After the HTTP_MSRP_B file is sent, notify IM_AS_B that the file is successfully sent.
  • Step 16 IM_AS_A/GC_AS_A forwards the Message message to IM_AS_C;
  • Step 17 IM_AS_C queries the local terminal UE_C registration capability, and UE_C supports HTTP file transmission, and then forwards the Message message to UE_C;
  • Step 18 UE_C parses the received Message message to obtain an HTTP URL; UE_C sends an HTTP GET request to the HTTP_MSRP_A server to obtain the file content;
  • Step 19 The HTTP_MSRP_A server returns the file content to UE_C.
  • Group chat file transfer in the standard process, because the sender can not ensure that all members of the chat room support HTTP file transfer, the file can only be transferred by SIP+MSRP; IM_AS_A/GC_AS_A is forwarded to IM_AS_B/C, IM_AS_B through SIP+MSRP /C receives and stores the file. Finally, IM_AS_B/C is sent to UE_B/C through SIP+MSRP. The IM_AS_B/C side needs to receive and store the file contents. The network bandwidth consumption of the IM_AS_A/GC_AS_A, IM_AS_B, and IM_AS_C is large, and the performance and capacity of the HTTP_MSRP_B/C side storage device are occupied.
  • the file is sent to the IM_AS_A/GC_AS_A by using the HTTP transmission mode, and the IM_AS_A/GC_AS_A forwards the Message message (including the file HTTP URL, file type, file size, etc.) to the chat.
  • the IM_AS to which the room member belongs is selected by the receiver IM_AS according to the terminal capability. Therefore, for all chat room member terminals that support HTTP file transmission, the end-to-end file transmission will be transmitted by HTTP, avoiding between GC_AS and IM_AS.
  • the IM_AS side of the receiver does not need to store file contents, which greatly saves network bandwidth between GC_AS and IM_AS, saves the performance and capacity of the HTTP_MSRP_C side storage device, and gives full play to the advantages of HTTP file transmission.
  • the above describes the specification definition process and the optimization process of the embodiment of the present application by comparing the file transmission processes of various scenarios such as point-to-point, point-to-multipoint, and chat room.
  • the specification definition process as long as the sender and the receiver have a terminal that does not support HTTP file transmission, the entire end-to-end file transmission adopts SIP+MSRP mode, and the file forwarding and storage of the sender AS and the receiver AS exist, and the network bandwidth and The receiving side AS storage device requirements are relatively high.
  • SIP+MSRP For group chat file transfer, all group member capabilities cannot be obtained, and files can only be transferred by SIP+MSRP.
  • the receiving terminal has the HTTP file transmission capability, the file is transmitted through the HTTP method, and the advantage of the HTTP file transmission is utilized as much as possible, thereby saving network bandwidth and storing server resources.
  • Figure 16 is a block diagram of a file transfer system according to an embodiment of the present application, the system includes: a storage server 161, an application server 162;
  • the storage server 161 is configured to: when the first terminal does not support HTTP, establish an MSRP link with the first terminal, and receive the file sent by the first terminal by using the MSRP link;
  • the application server 162 is configured to send, when the second terminal supports HTTP, the storage address of the file in the storage server to the second application server.
  • the application server 162 is configured to: when the first terminal does not support HTTP, receive a request message sent by the first terminal, where the request message carries file information and MSRP link establishment information of the first terminal; and returns a response message to the first terminal.
  • the response message carries the MSRP link establishment information of the application server; after receiving the positive acknowledgement message returned by the first terminal, the storage server is notified to receive the file sent by the first terminal;
  • the storage server 161 is configured to be established with the first terminal according to the MSRP link establishment information. Establishing an MSRP link, and receiving the file sent by the first terminal by using an MSRP link; storing the received file, and notifying the application server that the file is successfully received.
  • the application server 162 is configured to: when the second terminal supports HTTP, generate a corresponding HTTP link according to the path of the file stored in the storage server; and encapsulate the HTTP link of the file into the instant messaging message body to forward to the first Two application servers.
  • the application server 162 is configured to: when receiving an instant messaging message with an HTTP link sent by the first application server, query whether the second terminal supports HTTP; and when the second terminal does not support HTTP, the application server Sending a file acquisition notification message, so that the storage server acquires the file from the first storage server by using an HTTP method; and when the second terminal supports HTTP, sending the instant messaging message to the second terminal Soing that the second terminal acquires the file from the first storage server according to the HTTP link.
  • the application server 162 is configured to send an HTTP file acquisition notification message to the storage server.
  • the storage server 161 is configured to send an HTTP acquisition request message to the first storage server, receive the file sent by the first storage server, store the file, and notify the second application server that the file is successfully received.
  • the storage server 161 is configured to establish an MSRP link with the second terminal, and send the file to the second terminal by using the MSRP link.
  • the application server 162 is configured to receive a request message sent by the second terminal, where the request message carries the file information and the MSRP link establishment information of the terminal, and returns a response message to the second terminal, where the response message carries the application server.
  • the MSRP establishes chain information; receives a positive confirmation message sent by the second terminal; and notifies the storage server to send the file;
  • the storage server 161 is configured to establish an MSRP link with the second terminal according to the MSRP link establishment information, and send the file to the second terminal by using the MSRP link; After that, the second application server file is notified that the file is successfully sent.
  • FIG. 17 is a second diagram of a file transmission system according to an embodiment of the present disclosure.
  • the system includes: a first terminal 171, a first storage server 172, a first application server 173, a second terminal 174, and a second application server 175; ,
  • the first terminal 171 is configured to establish an MSRP link with the first storage server 172 when the first terminal 171 does not support HTTP, and the first terminal 171 is located through the MSRP link.
  • the first storage server 172 sends a file;
  • the first application server 173 is configured to send the storage address of the file in the first storage server 172 to the second application server 175 when the second terminal 174 supports HTTP;
  • the second application server 175 is configured to send the storage address to the second terminal 174;
  • the second terminal 174 is configured to acquire the file from the first storage server 172 by using an HTTP method according to the storage address.
  • system further includes:
  • the second storage server 176 is configured to: when the second terminal 174 does not support HTTP, the second storage server 176 acquires the file from the first storage server 172 by using an HTTP method; the second storage server 176 The second terminal 174 establishes an MSRP link;
  • the second terminal 174 is configured to acquire the file from the second storage server 176 through the MSRP link.
  • the file is sent by the first terminal 171 to a second terminal 174;
  • the file is sent by the first terminal 171 to the plurality of second terminals 174; or
  • the file is sent by the first terminal 171 to the first group, and the first group includes the first A terminal 171 and a plurality of second terminals 174.
  • the second application server 175 is configured to acquire the terminal capability information of the second terminal 174; or obtain the terminal capability information of the multiple second terminals 174.
  • the first terminal 171 is configured to: when the first terminal 171 supports HTTP, the first terminal 171 sends a file to the first storage server 172 by using an HTTP method;
  • the second storage server 176 is configured to: when the second terminal 174 does not support HTTP, the second storage server 176 acquires the file from the first storage server 172 by using an HTTP method; and establishes an MSRP with the second terminal 174. link;
  • the second terminal 174 is configured to acquire the file from the second storage server 176 through the MSRP link.
  • the system further includes: a first application server 173 and a second application server 175;
  • the first application server 173 is configured to send the storage address of the file in the first storage server 172 to the second application server 175 when the second terminal 174 supports HTTP;
  • the second application server 175 is configured to send the storage address to the second terminal 174;
  • the second terminal 174 is configured to acquire the file from the first storage server 172 by using an HTTP method according to the storage address.
  • the file is sent by the first terminal 171 to a second terminal 174;
  • the file is sent by the first terminal 171 to the plurality of second terminals 174; or
  • the file is transmitted by the first terminal 171 to the first group, and the first group includes the first terminal 171 and a plurality of second terminals 174.
  • the second application server 175 is configured to acquire the terminal capability information of the second terminal 174; or obtain the terminal capability information of the multiple second terminals 174.
  • FIG. 18 is a first schematic structural diagram of a file transmission apparatus according to an embodiment of the present application. As shown in FIG. 18, the apparatus includes:
  • the generating unit 181 is configured to generate an HTTP link according to a storage address of the file in the first storage server when the first terminal does not support HTTP;
  • Encapsulating unit 182 configured to encapsulate the HTTP link into an instant messaging message
  • the communication unit 183 is configured to send the communication message to the second application server
  • the communication unit 183 is configured to: when the first terminal supports HTTP, the first application server receives the instant messaging message sent by the first terminal and carries the HTTP link, and sends the instant messaging message to the second application server.
  • FIG. 19 is a second structural diagram of a file transmission apparatus according to an embodiment of the present disclosure. As shown in FIG. 19, the apparatus includes:
  • the communication unit 191 is configured to receive an instant messaging message that is sent by the first application server and that carries an HTTP link.
  • the query unit 192 is configured to query whether the second terminal supports HTTP;
  • the communication unit 191 is configured to: when the second terminal does not support HTTP, send a file acquisition notification message to the second storage server, so that the second storage server acquires the information from the first storage server by using an HTTP method.
  • the file is sent to the second terminal when the second terminal supports HTTP, so that the second terminal acquires the file from the first storage server according to the HTTP link.
  • each unit in the file transfer device may be implemented by a central processing unit (CPU) or a microprocessor (MPU, Micro Processor Unit) located in the file transfer device.
  • CPU central processing unit
  • MPU Micro Processor Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • the embodiment of the present application further provides an electronic device, including a processor and a memory, where the computer stores computer program instructions, and when the processor executes the computer program instructions, the processor is used to execute the The file transfer method of any of the embodiments is applied.
  • embodiments of the present application can be provided as a method, system, or computer program product. Accordingly, the application can take the form of a hardware embodiment, a software embodiment, or an embodiment in combination with software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions are provided to implement the work specified in one or more blocks of a flow or a flow and/or a block diagram of the flowchart The steps that can be made.
  • an embodiment of the present invention further provides a computer storage medium, wherein a computer program is configured, and the computer program is configured to execute the file transmission method of the embodiment of the present invention.
  • the first terminal when the first terminal does not support HTTP, the first terminal establishes an MSRP link with the first storage server, and the first terminal passes the MSRP link to The first storage server sends a file; when the second terminal supports HTTP, the first application server sends the storage address of the file in the first storage server to the second application server; the second application server The storage address is sent to the second terminal, and the second terminal acquires the file from the first storage server by using an HTTP method according to the storage address.
  • the first terminal when the first terminal supports HTTP, the first terminal sends a file to the first storage server by using an HTTP method; when the second terminal does not support HTTP, the second storage server uses the HTTP mode from the The first storage server acquires the file; the second storage server establishes an MSRP link with the second terminal, and the second terminal acquires the file from the second storage server by using the MSRP link.
  • terminals that implement the two protocols can transfer files to each other, reduce network traffic, and save resources of the storage server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种文件传输方法及系统、装置、电子设备、计算机存储介质，所述方法包括：当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件；当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。

Description

文件传输方法及系统、装置、电子设备、计算机存储介质
相关申请的交叉引用
本申请基于申请号为201710052237.8、申请日为2017年01月20日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及富媒体通信(RCS，Rich Communication Suite)领域，尤其涉及一种基于RCS的文件传输方法及系统、装置、电子设备、计算机存储介质。
背景技术
RCS定义了基于IP多媒体子系统(IMS，IP Multimedia Subsystem)与现有移动网络的一组业务能力，为移动用户提供增强型地址簿、内容共享、文件传输、增强型消息等功能。
随着3G、长期演进(LTE，Long Term Evolution)等移动通信和无线接入技术的不断涌现，RCS等社交类消息系统产品也迅速发展起来，其中图片、视频等文件类型的消息占比大幅度上升。RCS消息系统在发展过程中，采取了各种优化方法来提高产品的竞争力。
在RCS产品演进过程中，有一类终端通过会话初始协议(SIP，Session Initiation Protocol)和消息会话中继协议(MSRP，Message Session Relay Protocol)，进行文件传输；另一类终端通过超文本传输协议(HTTP，HyperText Transfer Protocol)，进行文件传输。然而，对于支持SIP+MSRP的终端与支持HTTP的终端之间如何传输文件，尚未有解决方案。
申请内容
为解决上述技术问题，本申请实施例提供了一种文件传输方法及系统、装置、电子设备、计算机存储介质。
本申请实施例提供一种文件传输方法，所述方法包括：
当第一终端不支持超文本传输协议HTTP时，第一存储服务器与所述第一终端建立消息会话中继协议MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件；
当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器。
上述方案中，所述当第一终端不支持HTTP时，第一存储服务器与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件，包括：
当第一终端不支持HTTP时，第一应用服务器接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；
第一应用服务器向第一终端返回响应消息，所述响应消息携带第一应用服务器的MSRP建链信息；
第一应用服务器接收第一终端返回的肯定确认消息后，通知第一存储服务器接收第一终端发送的文件；
第一存储服务器与第一终端根据所述MSRP建链信息建立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；
第一存储服务器存储接收到的文件，并通知第一应用服务器文件接收成功。
上述方案中，所述当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器，包括：
当第二终端支持HTTP时，第一应用服务器根据第一存储服务器中存 储的文件的路径生成对应的HTTP链接；
第一应用服务器将所述文件的HTTP链接封装到即时通讯消息体中转发给第二应用服务器。
本申请实施例还提供一种文件传输方法，所述方法包括：
第二应用服务器接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP；
当所述第二终端不支持HTTP时，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
当所述第二终端支持HTTP时，所述第二应用服务器将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
上述方案中，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件，包括：
第二应用服务器向第二存储服务器发送HTTP文件获取通知消息；
第二存储服务器向第一存储服务器发送HTTP获取请求消息；
第二存储服务器接收第一存储服务器发送的文件；
第二存储服务器存储所述文件，并通知第二应用服务器文件接收成功。
上述方案中，所述方法还包括：
所述第二存储服务器与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
上述方案中，所述第二存储服务器与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件，包括：
第二应用服务器接收第二终端发送的请求消息，所述请求消息携带文 件信息及终端的MSRP建链信息；
第二应用服务器向第二终端返回响应消息，所述响应消息携带第二应用服务器的MSRP建链信息；
第二应用服务器接收第二终端发送的肯定确认消息；
第二应用服务器通知第二存储服务器发送文件；
第二存储服务器与第二终端根据MSRP建链信息建立MSRP链路，并通过所述MSRP链路向第二终端发送文件；
第二存储服务器发送文件完成后，通知第二应用服务器文件发送成功。
本申请实施例提供一种文件传输方法，所述方法包括：
当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件；
当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
上述方案中，所述方法还包括：
当所述第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
上述方案中，所述文件由第一终端向一个第二终端发送；或者，
所述文件由第一终端向多个第二终端发送；或者，
所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终 端以及多个第二终端。
上述方案中，所述方法还包括：
所述第二应用服务器获取所述第二终端的终端能力信息；或者，
所述第二应用服务器获取所述多个第二终端的终端能力信息。
本申请实施例还提供一种文件传输方法，所述方法包括：
当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；
当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
上述方案中，所述方法还包括：
当所述第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
上述方案中，所述文件由第一终端向一个第二终端发送；或者，
所述文件由第一终端向多个第二终端发送；或者，
所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
上述方案中，所述方法还包括：
所述第二应用服务器获取所述第二终端的终端能力信息；或者，
所述第二应用服务器获取所述多个第二终端的终端能力信息。
本申请实施例又提供一种文件传输系统，所述系统包括：存储服务器、 应用服务器；其中，
所述存储服务器，配置为当第一终端不支持HTTP时，与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件；
所述应用服务器，配置为当第二终端支持HTTP时，将所述文件在所述存储服务器中的存储地址发送给第二应用服务器。
上述方案中，所述应用服务器，配置为当第一终端不支持HTTP时，接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；向第一终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第一终端返回的肯定确认消息后，通知所述存储服务器接收第一终端发送的文件；
所述存储服务器，配置为与第一终端根据所述MSRP建链信息建立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；存储接收到的文件，并通知所述应用服务器文件接收成功。
上述方案中，所述应用服务器，配置为当第二终端支持HTTP时，根据所述存储服务器中存储的文件的路径生成对应的HTTP链接；将所述文件的HTTP链接封装到即时通讯消息体中转发给第二应用服务器。
本申请实施例提供一种文件传输系统，所述系统包括：存储服务器、应用服务器；其中，
所述应用服务器，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP；当所述第二终端不支持HTTP时，向所述存储服务器发送文件获取通知消息，以使得所述存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
上述方案中，所述应用服务器，配置为向所述存储服务器发送HTTP 文件获取通知消息；
所述存储服务器，配置为向第一存储服务器发送HTTP获取请求消息；接收第一存储服务器发送的文件；存储所述文件，并通知第二应用服务器文件接收成功。
上述方案中，所述存储服务器，配置为：与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
上述方案中，所述应用服务器，配置为接收第二终端发送的请求消息，所述请求消息携带文件信息及终端的MSRP建链信息；向第二终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第二终端发送的肯定确认消息；通知所述存储服务器发送文件；
所述存储服务器，配置为与第二终端根据MSRP建链信息建立MSRP链路，并通过所述MSRP链路向第二终端发送文件；发送文件完成后，通知第二应用服务器文件发送成功。
本申请实施例还提供一种文件传输系统，所述系统包括：第一终端、第一存储服务器、第一应用服务器、第二终端、第二应用服务器；其中，
所述第一终端，配置为当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，通过所述MSRP链路所述第一终端向所述第一存储服务器发送文件；
所述第一应用服务器，配置为当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
所述第二应用服务器，配置为将所述存储地址发送给所述第二终端；
所述第二终端，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
上述方案中，所述系统还包括：
第二存储服务器，配置为当所述第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；所述第二存储服务器与所述第二终端建立MSRP链路；
所述第二终端，配置为通过所述MSRP链路从所述第二存储服务器获取所述文件。
上述方案中，所述文件由第一终端向一个第二终端发送；或者，
所述文件由第一终端向多个第二终端发送；或者，
所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
上述方案中，所述第二应用服务器，配置为获取所述第二终端的终端能力信息；或者，获取所述多个第二终端的终端能力信息。
本申请实施例提供一种文件传输系统，所述系统包括：第一终端、第一存储服务器、第二终端、第二存储服务器；其中，
所述第一终端，配置为当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；
所述第二存储服务器，配置为当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；与所述第二终端建立MSRP链路；
所述第二终端，配置为通过所述MSRP链路从所述第二存储服务器获取所述文件。
上述方案中，所述系统还包括：第一应用服务器、第二应用服务器；其中，
所述第一应用服务器，配置为当所述第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
所述第二应用服务器，配置为将所述存储地址发送给所述第二终端；
所述第二终端，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
上述方案中，所述文件由第一终端向一个第二终端发送；或者，
所述文件由第一终端向多个第二终端发送；或者，
所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
上述方案中，所述第二应用服务器，配置为获取所述第二终端的终端能力信息；或者，获取所述多个第二终端的终端能力信息。
本申请实施例还提供一种文件传输装置，所述装置包括：
生成单元，配置为当第一终端不支持HTTP时，根据文件在第一存储服务器中的存储地址生成HTTP链接；
封装单元，配置为将所述HTTP链接封装至即时通讯消息中；
通信单元，配置为将所述通讯消息发送给第二应用服务器；
所述通信单元，配置为当第一终端支持HTTP时，第一应用服务器接收所述第一终端发送的携有HTTP链接的即时通讯消息，将所述即时通讯消息发送给第二应用服务器。
本申请实施例提供一种文件传输装置，所述装置包括：
通信单元，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息；
查询单元，配置为查询第二终端是否支持HTTP；
所述通信单元，配置为当所述第二终端不支持HTTP时，向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述 HTTP链接从第一存储服务器中获取所述文件。
本申请实施例还提供一种电子设备，所述电子设备包括处理器和存储器，所述存储器中存储有计算机程序指令，当所述处理器执行所述计算机程序指令时，所述处理器用于执行上面任意一种所述的文件传输方法。
本申请实施例还提供一种计算机存储介质，该计算机存储介质存储有计算机程序，该计算机程序配置为执行上述文件传输方法。
本申请实施例的技术方案中，在一种情况下，当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件；当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。在另一种情况下，当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。采用本申请实施例的技术方案，实现了两种协议的终端能够相互传输文件，同时减少了网络流量，以及节省了存储服务器的资源。
附图说明
附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为本申请实施例的文件传输方法的流程示意图一；
图2为本申请实施例的文件传输方法的流程示意图二；
图3为本申请实施例的文件传输方法的流程示意图三；
图4为本申请实施例的文件传输方法的流程示意图四；
图5为本申请实施例的文件传输方法的流程示意图五；
图6为本申请实施例的文件传输方法的流程示意图六；
图7为规范定义的点对点文件传输流程示意图一；
图8为规范定义的点对点文件传输流程示意图二；
图9为本申请实施例的点对点文件传输流程示意图一；
图10为规范定义的点对点文件传输流程示意图三；
图11为本申请实施例的对点文件传输流程示意图二；
图12为规范定义的点到多点文件传输流程示意图；
图13为本申请实施例的点到多点文件传输流程示意图；
图14为规范定义的聊天室文件传输流程示意图；
图15为本申请实施例的聊天室文件传输流程示意图；
图16为本申请实施例的文件传输系统的框架图一；
图17为本申请实施例的文件传输系统的框架图二；
图18为本申请实施例的文件传输装置的结构组成示意图一；
图19为本申请实施例的文件传输装置的结构组成示意图二。
具体实施方式
为了能够更加详尽地了解本申请实施例的特点与技术内容，下面结合附图对本申请实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本申请实施例。
以下为本申请实施例中涉及到的关键术语的解释说明：
SIP协议相关的关键术语：
INVITE：表示主叫用户发起会话请求，邀请其他用户加入一个会话。
ACK：客户端向服务器端证实它已经收到了对INVITE请求的最终响应。
BYE：表示终止一个已经建立的呼叫。
REGISTER：表示客户端向SIP服务器端注册。
OPTION：能力探测消息，用于探测对方终端能力。
MESSAG：用来发送即时消息，可以不保持会话，内容大小有限制，一般为900字节。
MSRP协议相关的关键术语：
Request：SEND，传输一个完整的消息或者分块消息。
Responses：200，成功。
HTTP协议相关的关键术语：
POST：上传数据请求。
GET：获取数据请求。
UE：用户设备(User Equipment)，负责发起或接收群聊聊天消息，如手机、PAD等。
IM_AS：即时通讯应用服务器(Instant Messenger Application Server)，负责接收终端提交的消息，根据接收方地址进行投递，目的方为UE，则向目的方归属的AS发送聊天消息。
UE_A，UE_B，UE_C为三个UE终端。
IM_AS_A，IM_AS_B，IM_AS_C分别为UE_A，UE_B，UE_C归属的聊天AS。
GC_AS_A，GC_AS_B，IM_AS_C分别为UE_A，UE_B，UE_C归属的群聊AS。
HTTP_MSRP_A，HTTP_MSRP_B，HTTP_MSRP_C分别为IM_AS_A，IM_AS_B，IM_AS_C侧对应的存储服务器，对外提供HTTP和MSRP服务。
在RCS产品演进过程中，RCS5.0及之前的规范中定义了RCS文件存储转发的方法，通过SIP和MSRP两种协议配合来传输文件，发送方归属的RCS应用服务器(AS，Application Server)接收到新文件后，先存储， 然后通过SIP和MSRP再传输到接送方归属的RCS AS，接收方归属的RCS AS接收完文件后再转发给接收方终端。为了减少发送方归属AS跟接收方归属AS之间网络传输流量，节省网络带宽，RCS6.0规范中定义了另一种RCS文件传输方法，发送方终端通过HTTP，先把文件内容上传到本地HTTP服务器，生成对应的HTTP统一资源定位符(URL，Uniform Resoure Locator)，然后再通过RCS AS把HTTP URL发送给接收方，接收方终端再通过HTTP URL到HTTP服务器上获取文件内容，避免RCS AS之间传输文件内容。
在RCS规范演进过程中，会出现用SIP+MSRP方式传输文件和用HTTP方式传输文件的终端并存，这些文件传输方式不同的终端之间的文件传输互通流程如何优化才能充分发挥HTTP文件传输的优势，是本申请实施例所要解决的问题。
下文中将通过群消息的实现来详细说明本申请实施例。为描述方便省略中间核心网网元，如呼叫会话控制功能(CSCF，Call Session Control Function)等。
图1为本申请实施例的文件传输方法的流程示意图一，本示例中，第一终端不支持HTTP，如图1所示，所述文件传输方法包括：
步骤101：当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件。
本申请实施例应用的场景包括以下三种：
第一种：所述文件由第一终端向一个第二终端发送；
第二种：所述文件由第一终端向多个第二终端发送；
第三种：所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
对于第一种情况，也即点对点传输文件的场景；对于第二种情况，也即点对多点传输文件的场景；对于第三种情况，也即聊天室文件传输情况。对于这三种情况下，具体流程均为：
第一终端为UE_A，第一应用服务器为IM_AS_A，第一存储服务器为HTTP_MSRP_A；当第一终端不支持HTTP时，UE_A向IM_AS_A发送INVITE消息，通过SDP携带文件信息及终端MSRP建链信息；IM_AS_A向UE_A返回200OK响应，携带IM_AS_A侧MSRP建链信息；UE_A收到响应消息，返回ACK；IM_AS_A通知HTTP_MSRP_A接收文件；UE_A与HTTP_MSRP_A根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路发送文件；HTTP_MSRP_A接收存储文件，然后通知IM_AS_A文件接收成功。上述过程为第一终端通过MSRP链路向第一存储服务器发送文件的具体过程。
步骤102：当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器。
本申请实施例中，第二终端为UE_B，第二应用服务器为IM_AS_B；IM_AS_A根据HTTP_MSRP_A存储文件路径生成对应的HTTP URL，把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后转发给IM_AS_B。IM_AS_B确定本地UE_B支持HTTP，IM_AS_B将Message发送给UE_B；UE_B解析接收到的Message消息，得到HTTP URL；UE_B发送HTTP GET请求到HTTP_MSRP_A服务器获取文件内容；HTTP_MSRP_A服务器返回文件内容给UE_B。
步骤103：所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
本申请实施例中，所述方法还包括：
当所述第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
具体地，当第二终端不支持HTTP时，IM_AS_B给HTTP_MSRP_B发送HTTP文件获取通知；HTTP_MSRP_B向HTTP_MSRP_A发送HTTP GET请求；HTTP_MSRP_A返回文件内容；HTTP_MSRP_B文件获取完成，通知IM_AS_B；IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；UE_B收到响应消息，返回ACK；IM_AS_B通知HTTP_MSRP_B发送文件；UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2，并通过MSRP链路接收文件内容；HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功。
本申请实施例中，所述方法还包括：所述第二应用服务器获取所述第二终端的终端能力信息；或者，所述第二应用服务器获取所述多个第二终端的终端能力信息。
具体地，如果是点对点传输文件的场景，第二应用服务器获取第二终端的终端能力信息，当第二终端支持HTTP时，执行HTTP相应的流程；当第二终端不支持HTTP时，执行SIP+MSRP相应的流程。
如果是点对点或者聊天室文件传输场景，第二应用服务器获取多个第二终端的终端能力信息，对于支持HTTP的第二终端，执行HTTP相应的流程；对于不支持HTTP的第二终端，执行SIP+MSRP相应的流程。
图2为本申请实施例的文件传输方法的流程示意图二，本示例中，第一终端支持HTTP，如图2所示，所述文件传输方法包括：
步骤201：当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件。
本申请实施例应用的场景包括以下三种：
第一种：所述文件由第一终端向一个第二终端发送；
第二种：所述文件由第一终端向多个第二终端发送；
第三种：所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
对于第一种情况，也即点对点传输文件的场景；对于第二种情况，也即点对多点传输文件的场景；对于第三种情况，也即聊天室文件传输情况。对于这三种情况下，具体流程均为：
第一终端为UE_A，第一应用服务器为IM_AS_A，第一存储服务器为HTTP_MSRP_A；当第一终端支持HTTP时，UE_A通过HTTP POST请求把文件内容传送给HTTP_MSRP_A；HTTP_MSRP_A接收、存储文件，并根据文件存储位置生成相应的HTTP URL，返回200OK响应，携带文件对应的HTTP URL；UE_A把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后发送给IM_AS_A。
步骤202：当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件。
具体地，IM_AS_A接收到Message消息，转发给IM_AS_B；IM_AS_B解析Message消息，得到文件的HTTP URL，查询本地终端UE_B注册能力，如果不支持HTTP文件传输，则IM_AS_B给HTTP_MSRP_B发送HTTP文件获取通知；HTTP_MSRP_B向HTTP_MSRP_A发送HTTP GET请求；HTTP_MSRP_A返回文件内容。
步骤203：所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
具体地，HTTP_MSRP_B文件获取完成，通知IM_AS_B；IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；UE_B收到响应消息，返回ACK；IM_AS_B通知HTTP_MSRP_B发送文件；UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2，并通过MSRP链路接收文件内容；HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功。
本申请实施例中，所述方法还包括：
当所述第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
具体地，IM_AS_B查询本地终端UE_B注册能力，UE_B支持HTTP文件传输，则转发Message消息给UE_B；UE_B解析接收到的Message消息，得到HTTP URL；UE_B发送HTTP GET请求到HTTP_MSRP_A服务器获取文件内容；HTTP_MSRP_A服务器返回文件内容给UE_B。
本申请实施例中，所述方法还包括：所述第二应用服务器获取所述第二终端的终端能力信息；或者，所述第二应用服务器获取所述多个第二终端的终端能力信息。
具体地，如果是点对点传输文件的场景，第二应用服务器获取第二终端的终端能力信息，当第二终端支持HTTP时，执行HTTP相应的流程；当第二终端不支持HTTP时，执行SIP+MSRP相应的流程。
如果是点对点或者聊天室文件传输场景，第二应用服务器获取多个第 二终端的终端能力信息，对于支持HTTP的第二终端，执行HTTP相应的流程；对于不支持HTTP的第二终端，执行SIP+MSRP相应的流程。
图3为本申请实施例的文件传输方法的流程示意图三，本示例应用于第一应用服务器侧，如图3所示，所述文件传输方法包括：
步骤301：当第一终端不支持HTTP时，第一应用服务器根据文件在第一存储服务器中的存储地址生成HTTP链接；所述第一应用服务器将所述HTTP链接封装至即时通讯消息中，发送给第二应用服务器。
步骤302：当第一终端支持HTTP时，第一应用服务器接收所述第一终端发送的携有HTTP链接的即时通讯消息，将所述即时通讯消息发送给第二应用服务器。
本领域技术人员应当理解，本示例中的第一应用服务器所执行的操作步骤可参照前述图1和图2所示的内容进行理解。
图4为本申请实施例的文件传输方法的流程示意图四，本示例应用于第一应用服务器侧，如图4所示，所述文件传输方法包括：
步骤401：第二应用服务器接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP。
步骤402：当所述第二终端不支持HTTP时，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件。
步骤403：当所述第二终端支持HTTP时，所述第二应用服务器将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
本领域技术人员应当理解，本示例中的第一应用服务器所执行的操作步骤可参照前述图1和图2所示的内容进行理解。
图5为本申请实施例的文件传输方法的流程示意图五，如图5所示， 所述文件传输方法包括：
步骤501：当第一终端不支持超文本传输协议HTTP时，第一存储服务器与所述第一终端建立消息会话中继协议MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件。
本申请实施例中，所述当第一终端不支持HTTP时，第一存储服务器与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件，包括：
当第一终端不支持HTTP时，第一应用服务器接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；
第一应用服务器向第一终端返回响应消息，所述响应消息携带第一应用服务器的MSRP建链信息；
第一应用服务器接收第一终端返回的肯定确认消息后，通知第一存储服务器接收第一终端发送的文件；
第一存储服务器与第一终端根据所述MSRP建链信息建立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；
第一存储服务器存储接收到的文件，并通知第一应用服务器文件接收成功。
步骤502：当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器。
本申请实施例中，所述当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器，包括：
当第二终端支持HTTP时，第一应用服务器根据第一存储服务器中存储的文件的路径生成对应的HTTP链接；
第一应用服务器将所述文件的HTTP链接封装到即时通讯消息体中转 发给第二应用服务器。
图6为本申请实施例的文件传输方法的流程示意图六，如图6所示，所述文件传输方法包括：
步骤601：第二应用服务器接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP。
步骤602：当所述第二终端不支持HTTP时，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件。
本申请实施例中，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件，包括：
第二应用服务器向第二存储服务器发送HTTP文件获取通知消息；
第二存储服务器向第一存储服务器发送HTTP获取请求消息；
第二存储服务器接收第一存储服务器发送的文件；
第二存储服务器存储所述文件，并通知第二应用服务器文件接收成功。
本申请实施例中，所述方法还包括：
所述第二存储服务器与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
具体地，第二应用服务器接收第二终端发送的请求消息，所述请求消息携带文件信息及终端的MSRP建链信息；
第二应用服务器向第二终端返回响应消息，所述响应消息携带第二应用服务器的MSRP建链信息；
第二应用服务器接收第二终端发送的肯定确认消息；
第二应用服务器通知第二存储服务器发送文件；
第二存储服务器与第二终端根据MSRP建链信息建立MSRP链路，并 通过所述MSRP链路向第二终端发送文件；
第二存储服务器发送文件完成后，通知第二应用服务器文件发送成功。
步骤603：当所述第二终端支持HTTP时，所述第二应用服务器将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
以下结合具体应用场景对本申请实施例的文件传输方法做详细描述。
实施例一：
UE_A发文件给UE_B。UE_A支持RCS6.0规范，UE_B支持RCS6.0规范。
规范定义流程如图7所述，详细描述如下：
步骤1：UE_A给UE_B发送OPTION能力探测消息；
步骤2：UE_B返回本终端能力；
步骤3：UE_A得到UE_B终端能力，UE_B支持HTTP文件传输；UE_A通过HTTP方式发送文件，UE_A通过HTTP POST请求把文件内容传送给HTTP_MSRP_A；
步骤4：HTTP_MSRP_A接收、存储文件，并根据文件存储位置生成相应的HTTP URL，返回200OK响应，携带文件对应的HTTP URL；
步骤5：UE_A把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后发送给IM_AS_A。
步骤6：IM_AS_A接收到Message消息，转发给IM_AS_B。
实施例二
UE_A发文件给UE_B。UE_A或UE_B不支持RCS6.0规范。
点到点文件传输规范定义流程如图8所述，详细描述如下：
步骤1：UE_A给UE_B发送OPTION能力探测消息；
步骤2：UE_B返回本终端能力；
步骤3：UE_A得到UE_B终端能力，如果UE_B不支持HTTP文件传输或者UE_A本身不支持HTTP文件传输；UE_A通过SIP+MSRP方式发送文件，UE_A给IM_AS_A发送INVITE消息，通过会话描述协议(SDP，Session Description Protocol)携带文件信息及终端MSRP建链信息；
步骤4：IM_AS_A返回200OK响应，携带IM_AS_A侧MSRP建链信息；
步骤5：UE_A收到响应消息，返回ACK；
步骤6：IM_AS_A通知HTTP_MSRP_A接收文件；
步骤7：UE_A与HTTP_MSRP_A根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路发送文件内容；
步骤8：HTTP_MSRP_A接收存储文件，然后通知IM_AS_A文件接收成功；IM_AS_A给IM_AS_B发送INVITE消息，通过SDP携带文件信息及IM_AS_A侧MSRP建链信息；
步骤9：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤10：IM_AS_A收到响应消息，返回ACK；
步骤11：IM_AS_A通知HTTP_MSRP_A发送文件；
步骤12：IM_AS_B通知HTTP_MSRP_B接收文件；
步骤13：HTTP_MSRP_A与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2；
步骤14：HTTP_MSRP_A通过MSRP_2链路传输文件内容给HTTP_MSRP_B；
步骤15：HTTP_MSRP_A发送文件，然后通知IM_AS_A文件发送成功；
步骤16：HTTP_MSRP_B接收存储文件，然后通知IM_AS_B文件接收成功。
实施例三
UE_A发文件给UE_B。UE_A不支持RCS6.0规范，UE_B支持RCS6.0规范。
本申请实施例的点到点文件传输流程如图9所述，详细描述如下：
步骤1：UE_A给UE_B发送OPTION能力探测消息；
步骤2：UE_B返回本终端能力；
步骤3：UE_A得到UE_B终端能力，UE_B支持HTTP文件传输，但是UE_A不支持HTTP文件传输；UE_A通过SIP+MSRP方式发送文件，UE_A给IM_AS_A发送INVITE消息，通过SDP携带文件信息及终端MSRP建链信息；
步骤4：IM_AS_A返回200OK响应，携带IM_AS_A侧MSRP建链信息；
步骤5：UE_A收到响应消息，返回ACK；
步骤6：IM_AS_A通知HTTP_MSRP_A接收文件；
步骤7：UE_A与HTTP_MSRP_A根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路发送文件内容；
步骤8：HTTP_MSRP_A接收存储文件，然后通知IM_AS_A文件接收成功；IM_AS_A发OPTION消息给UE_B；
步骤9：UE_B返回本终端能力；
步骤10：IM_AS_A获知UE_B支持HTTP文件传输，IM_AS_A根据HTTP_MSRP_A存储文件路径生成对应的HTTP URL，把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后转发给IM_AS_B。
在规范标准流程中，如果UE_A不支持HTTP文件传输，IM_AS_A首先通过SIP+MSRP接收、存储文件，然后再通过SIP+MSRP转发给IM_AS_B，IM_AS_B接收、存储文件，IM_AS_A和IM_AS_B侧分别要接收、存储文件内容。对IM_AS_A和IM_AS_B之间网络带宽消耗较大，同时占用HTTP_MSRP_B侧存储设备的性能和容量。
本申请实施例的技术方案中，IM_AS_A接收完文件后，先探测UE_B终端能力，如果UE_B支持HTTP文件传输，则生成Message消息发给IM_AS_B，Message消息中只包含HTTP URL和文件相关信息，不包含文件内容，减少IM_AS_A和IM_AS_B之间文件内容的网络传输及文件存储，大大节省了IM_AS_A和IM_AS_B之间网络带宽，节省了HTTP_MSRP_B侧存储设备的性能和容量。
实施例四
UE_B接收UE_A发送的文件。UE_A不支持RCS6.0规范，UE_B支持RCS6.0规范。
点到点文件传输规范定义流程如图10所述，详细描述如下：
步骤1：IM_AS_B接收到IM_AS_A发送来的INVITE消息，解析SDP得到文件相关信息及IM_AS_A侧MSRP建链信息；
步骤2：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤3：IM_AS_A收到响应消息，返回ACK；
步骤4：IM_AS_A通知HTTP_MSRP_A发送文件；
步骤5：IM_AS_B通知HTTP_MSRP_B接收文件；
步骤6：HTTP_MSRP_A与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_1；HTTP_MSRP_A通过MSRP_1链路传输文件内容给HTTP_MSRP_B；
步骤7：HTTP_MSRP_A发送文件，然后通知IM_AS_A文件发送成功；
步骤8：HTTP_MSRP_B接收存储文件，然后通知IM_AS_B文件接收成功；
步骤9：IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；
步骤10：UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；
步骤11：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤12：UE_B收到响应消息，返回ACK；
步骤13：IM_AS_B通知HTTP_MSRP_B发送文件；
步骤14：UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2，并通过MSRP链路接收文件内容；
步骤15：HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功。
实施例五
UE_B接收UE_A发送的文件。UE_A不支持RCS6.0规范，UE_B支持RCS6.0规范。
本申请实施例的点到点文件传输流程如图11所述，详细描述如下：
步骤1：IM_AS_B接收到文件传输Message消息；
步骤2：IM_AS_B转发Message消息给UE_B；
步骤3：UE_B解析接收到的Message消息，得到HTTP URL；UE_B发送HTTP GET请求到HTTP_MSRP_A服务器获取文件内容；
步骤4：HTTP_MSRP_A服务器返回文件内容给UE_B。
在规范标准流程中，如果UE_A不支持HTTP文件传输，UE_B、IM_AS_A、IM_AS_B支持HTTP文件传输，则端到端传输流程全部采用SIP、MSRP传输。IM_AS_A通过SIP+MSRP转发给IM_AS_B，IM_AS_B接收、存储文件，最后IM_AS_B再通过SIP+MSRP发送给UE_B，IM_AS_B侧也要接收、存储文件内容。对IM_AS_A和IM_AS_B之间网络带宽消耗较大，同时占用HTTP_MSRP_B侧存储设备的性能和容量。
本申请实施例的技术方案中，IM_AS_B接收到IM_AS_A的Message消息，然后直接转发Message消息给UE_B，Message消息中只包含HTTP URL和文件相关信息，不包含文件内容，减少IM_AS_A和IM_AS_B之间文件内容的网络传输及文件存储，大大节省了IM_AS_A和IM_AS_B之间网络带宽，节省了HTTP_MSRP_B侧存储设备的性能和容量。
实施例六
UE_A群发文件给UE_B、UE_C。UE_B不支持RCS6.0规范，UE_A，UE_C支持RCS6.0规范。
点到多点文件传输规范定义流程如图12所述，详细描述如下：
步骤1：UE_A给UE_B、UE_C发送OPTION能力探测消息；
步骤2：UE_B、UE_C返回本终端能力；
步骤3：UE_A得到UE_B、UE_C终端能力，如果UE_A不支持HTTP文件传输；UE_A通过SIP+MSRP方式发送文件，UE_A给IM_AS_A发送INVITE消息，通过SDP携带文件信息及终端MSRP建链信息；
步骤4：IM_AS_A返回200OK响应，携带IM_AS_A侧MSRP建链信息；
步骤5：UE_A收到响应消息，返回ACK；
步骤6：IM_AS_A通知HTTP_MSRP_A接收文件；
步骤7：UE_A与HTTP_MSRP_A根据SIP协商的建链信息建立MSRP 链路MSRP_1，并通过MSRP链路发送文件内容；
步骤8：HTTP_MSRP_A接收存储文件，然后通知IM_AS_A文件接收成功；IM_AS_A给IM_AS_B发送INVITE消息，通过SDP携带文件信息及IM_AS_A MSRP建链信息；
步骤9：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤10：IM_AS_A收到响应消息，返回ACK；
步骤11：IM_AS_A通知HTTP_MSRP_A发送文件；
步骤12：IM_AS_B通知HTTP_MSRP_B接收文件；
步骤13：HTTP_MSRP_A与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2；
步骤14：HTTP_MSRP_A通过MSRP_2链路传输文件内容给HTTP_MSRP_B；
步骤15：HTTP_MSRP_A发送文件，然后通知IM_AS_A文件发送成功；
步骤16：HTTP_MSRP_B接收存储文件，然后通知IM_AS_B文件接收成功；
步骤17：IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；
步骤18：UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；
步骤19：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤20：UE_B收到响应消息，返回ACK；
步骤21：IM_AS_B通知HTTP_MSRP_B发送文件；
步骤22：UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_3，并通过MSRP链路接收文件内容；
步骤23：HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功；
步骤24～步骤32：同步骤8～步骤23，IM_AS_A通过SIP+MSRP转发文件到IM_AS_C，IM_AS_C下发文件给UE_C。
实施例七
UE_A群发文件给UE_B、UE_C。UE_B支持RCS6.0规范，UE_A，UE_C不支持RCS6.0规范。
本申请实施例的点到多点文件传输流程如图13所述，详细描述如下：
步骤1：UE_A通过HTTP POST请求把文件内容传送给HTTP_MSRP_A；
步骤2：HTTP_MSRP_A接收、存储文件，并根据文件存储位置生成相应的HTTP URL，返回200OK响应，携带文件对应的HTTP URL；
步骤3：UE_A把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后发送给IM_AS_A；
步骤4：IM_AS_A接收到Message消息，转发给IM_AS_B；
步骤5：IM_AS_B解析Message消息，得到文件的HTTP URL，查询本地终端UE_B注册能力，如果不支持HTTP文件传输，则IM_AS_B给HTTP_MSRP_B发送HTTP文件获取通知；
步骤6：HTTP_MSRP_B向HTTP_MSRP_A发送HTTP GET请求；
步骤7：HTTP_MSRP_A返回文件内容；
步骤8：HTTP_MSRP_B文件获取完成，通知IM_AS_B；
步骤9：IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信 息；
步骤10：UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；
步骤11：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤12：UE_B收到响应消息，返回ACK；
步骤13：IM_AS_B通知HTTP_MSRP_B发送文件；
步骤14：UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路接收文件内容；
步骤15：HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功；
步骤16：IM_AS_A转发Message消息给IM_AS_C；
步骤17：IM_AS_C查询本地终端UE_C注册能力，UE_C支持HTTP文件传输，则转发Message消息给UE_C；
步骤18：UE_C解析接收到的Message消息，得到HTTP URL；UE_C发送HTTP GET请求到HTTP_MSRP_A服务器获取文件内容；
步骤19：HTTP_MSRP_A服务器返回文件内容给UE_C。
点到多点文件传输，在规范标准流程中，接收方终端只要有一个终端不支持HTTP文件传输，则端到端所有传输流程全部采用SIP、MSRP传输。IM_AS_A通过SIP+MSRP转发给IM_AS_B/C，IM_AS_B/C接收、存储文件，最后IM_AS_B/C再通过SIP+MSRP发送给UE_B/C，IM_AS_B/C侧需要接收、存储文件内容。对IM_AS_A、IM_AS_B、IM_AS_C之间网络带宽消耗较大，同时占用HTTP_MSRP_B/C侧存储设备的性能和容量。
本申请实施例的技术方案中，接收方终端UE_C支持HTTP文件传输， 则发送方UE_A、接收方UE_C之间采用HTTP文件传输方式，IM_AS_A、IM_AS_C之间不需要传输文件内容，IM_AS_C也不需要存储文件内容，大大节省了IM_AS_A和IM_AS_C之间网络带宽，节省了HTTP_MSRP_C侧存储设备的性能和容量。
实施例八
UE_A、UE_B、UE_C同属于一个聊天室，聊天室归属GC_AS_A，UE_A在聊天室中发一文件。UE_B不支持RCS6.0规范，UE_A，UE_C支持RCS6.0规范。
规范定义流程如图14所述，详细描述如下：
步骤1：由于UE_A无法确保聊天室所有成员都支持HTTP文件传输，只能通过SIP+MSRP方式传输；UE_A通过SIP+MSRP方式发送文件，UE_A给IM_AS_A/GC_AS_A发送INVITE消息，通过SDP携带文件信息及终端MSRP建链信息；
步骤2：IM_AS_A/GC_AS_A返回200OK响应，携带IM_AS_A/GC_AS_A侧MSRP建链信息；
步骤3：UE_A收到响应消息，返回ACK；
步骤4：IM_AS_A/GC_AS_A通知HTTP_MSRP_A接收文件；
步骤5：UE_A与HTTP_MSRP_A根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路发送文件内容；
步骤6：HTTP_MSRP_A接收存储文件，然后通知IM_AS_A/GC_AS_A文件接收成功；IM_AS_A/GC_AS_A给IM_AS_B发送INVITE消息，通过SDP携带文件信息及IM_AS_A/GC_AS_A MSRP建链信息；
步骤7：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤8：IM_AS_A/GC_AS_A收到响应消息，返回ACK；
步骤9：IM_AS_A/GC_AS_A通知HTTP_MSRP_A发送文件；
步骤10：IM_AS_B通知HTTP_MSRP_B接收文件；
步骤11：HTTP_MSRP_A与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2；
步骤12：HTTP_MSRP_A通过MSRP_2链路传输文件内容给HTTP_MSRP_B；
步骤13：HTTP_MSRP_A发送文件，然后通知IM_AS_A/GC_AS_A文件发送成功；
步骤14：HTTP_MSRP_B接收存储文件，然后通知IM_AS_B文件接收成功；
步骤15：IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；
步骤16：UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；
步骤17：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤18：UE_B收到响应消息，返回ACK；
步骤19：IM_AS_B通知HTTP_MSRP_B发送文件；
步骤20：UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_2，并通过MSRP链路接收文件内容；
步骤21：HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功；
步骤22～步骤30：同步骤6～步骤21，IM_AS_A/GC_AS_A通过SIP+MSRP转发文件到IM_AS_C，IM_AS_C下发文件给UE_C。
实施例九
UE_A、UE_B、UE_C同属于一个聊天室，聊天室归属GC_AS_A，UE_A在聊天室中发一文件。UE_B不支持RCS6.0规范，UE_A，UE_C支持RCS6.0规范。
本申请实施例的群聊文件传输流程如图15所述，详细描述如下：
步骤1：UE_A通过HTTP POST请求把文件内容传送给HTTP_MSRP_A；
步骤2：HTTP_MSRP_A接收、存储文件，并根据文件存储位置生成相应的HTTP URL，返回200OK响应，携带文件对应的HTTP URL；
步骤3：UE_A把HTTP URL及相应的文件信息(文件类型、文件大小、文件名)等内容封装到Message消息体中，然后发送给IM_AS_A/GC_AS_A；
步骤4：IM_AS_A/GC_AS_A接收到Message消息，转发给IM_AS_B；
步骤5：IM_AS_B解析Message消息，得到文件的HTTP URL，查询本地终端UE_B注册能力，如果不支持HTTP文件传输，则IM_AS_B给HTTP_MSRP_B发送HTTP文件获取通知；
步骤6：HTTP_MSRP_B向HTTP_MSRP_A发送HTTP GET请求；
步骤7：HTTP_MSRP_A返回文件内容；
步骤8：HTTP_MSRP_B文件获取完成，通知IM_AS_B；
步骤9：IM_AS_B给UE_B下发INVITE消息，包含接收文件相关信息；
步骤10：UE_B收到文件传输INVITE消息后，主动接收文件，UB_B给IM_AS_B发送INVITE消息，通过SDP携带接收文件相关信息及终端MSRP建链信息；
步骤11：IM_AS_B返回200OK响应，携带IM_AS_B侧MSRP建链信息；
步骤12：UE_B收到响应消息，返回ACK；
步骤13：IM_AS_B通知HTTP_MSRP_B发送文件；
步骤14：UE_B与HTTP_MSRP_B根据SIP协商的建链信息建立MSRP链路MSRP_1，并通过MSRP链路接收文件内容；
步骤15：HTTP_MSRP_B文件发送完成后通知IM_AS_B，文件发送成功；
步骤16：IM_AS_A/GC_AS_A转发Message消息给IM_AS_C；
步骤17：IM_AS_C查询本地终端UE_C注册能力，UE_C支持HTTP文件传输，则转发Message消息给UE_C；
步骤18：UE_C解析接收到的Message消息，得到HTTP URL；UE_C发送HTTP GET请求到HTTP_MSRP_A服务器获取文件内容；
步骤19：HTTP_MSRP_A服务器返回文件内容给UE_C。
群聊文件传输，在规范标准流程中，由于发送方无法确保聊天室所有成员都支持HTTP文件传输，只能通过SIP+MSRP方式传输文件；IM_AS_A/GC_AS_A通过SIP+MSRP转发给IM_AS_B/C，IM_AS_B/C接收、存储文件，最后IM_AS_B/C再通过SIP+MSRP发送给UE_B/C，IM_AS_B/C侧需要接收、存储文件内容。对IM_AS_A/GC_AS_A、IM_AS_B、IM_AS_C之间网络带宽消耗较大，同时占用HTTP_MSRP_B/C侧存储设备的性能和容量。
本申请实施例的技术方案中，如果UE_A支持HTTP文件传输，则通过HTTP传输方式发送文件至IM_AS_A/GC_AS_A，IM_AS_A/GC_AS_A转发Message消息(包含文件HTTP URL、文件类型、文件大小等信息)至聊天室成员归属的IM_AS，由接收方IM_AS根据终端能力选择相应的下发方式，这样对于所有支持HTTP文件传输的聊天室成员终端，端到端文件传输都会使用HTTP方式传输，避免GC_AS、IM_AS之间传输文件内容， 接收方IM_AS侧也不需要存储文件内容，大大节省了GC_AS、IM_AS之间网络带宽，节省了HTTP_MSRP_C侧存储设备的性能和容量，充分发挥HTTP文件传输的优势。
上述通过对点到点、点到多点、聊天室等多种场景的文件传输流程对比，介绍了规范定义流程和本申请实施例的优化流程。规范定义流程，只要发送方、接收方有一个终端不支持HTTP文件传输，则整个端到端文件传输采用SIP+MSRP方式，存在发送方AS和接收方AS的文件转发、存储，对网络带宽及接收方AS存储设备要求比较高。对于群聊文件传输，无法获取所有群成员能力，只能采用SIP+MSRP方式传输文件。本申请实施例的技术方案中，只要接收方本终端具备HTTP文件传输能力，就会通过HTTP方式传输文件，尽可能发挥HTTP文件传输的优势，节省网络带宽和存储服务器资源。
图16为本申请实施例的文件传输系统的框架图一，所述系统包括：存储服务器161、应用服务器162；
第一实施方式：
所述存储服务器161，配置为当第一终端不支持HTTP时，与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件；
所述应用服务器162，配置为当第二终端支持HTTP时，将所述文件在所述存储服务器中的存储地址发送给第二应用服务器。
所述应用服务器162，配置为当第一终端不支持HTTP时，接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；向第一终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第一终端返回的肯定确认消息后，通知所述存储服务器接收第一终端发送的文件；
所述存储服务器161，配置为与第一终端根据所述MSRP建链信息建 立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；存储接收到的文件，并通知所述应用服务器文件接收成功。
所述应用服务器162，配置为当第二终端支持HTTP时，根据所述存储服务器中存储的文件的路径生成对应的HTTP链接；将所述文件的HTTP链接封装到即时通讯消息体中转发给第二应用服务器。
第二实施方式：
所述应用服务器162，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP；当所述第二终端不支持HTTP时，向所述存储服务器发送文件获取通知消息，以使得所述存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
所述应用服务器162，配置为向所述存储服务器发送HTTP文件获取通知消息；
所述存储服务器161，配置为向第一存储服务器发送HTTP获取请求消息；接收第一存储服务器发送的文件；存储所述文件，并通知第二应用服务器文件接收成功。
所述存储服务器161，配置为：与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
所述应用服务器162，配置为接收第二终端发送的请求消息，所述请求消息携带文件信息及终端的MSRP建链信息；向第二终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第二终端发送的肯定确认消息；通知所述存储服务器发送文件；
所述存储服务器161，配置为与第二终端根据MSRP建链信息建立MSRP链路，并通过所述MSRP链路向第二终端发送文件；发送文件完成 后，通知第二应用服务器文件发送成功。
图17为本申请实施例的文件传输系统的框架图二，所述系统包括：第一终端171、第一存储服务器172、第一应用服务器173、第二终端174、第二应用服务器175；其中，
在第一终端171不支持HTTP的场景下：
所述第一终端171，配置为当第一终端171不支持HTTP时，所述第一终端171与第一存储服务器172建立MSRP链路，通过所述MSRP链路所述第一终端171向所述第一存储服务器172发送文件；
所述第一应用服务器173，配置为当第二终端174支持HTTP时，第一应用服务器173将所述文件在所述第一存储服务器172中的存储地址发送给第二应用服务器175；
所述第二应用服务器175，配置为将所述存储地址发送给所述第二终端174；
所述第二终端174，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器172中获取所述文件。
本申请实施例中，所述系统还包括：
第二存储服务器176，配置为当所述第二终端174不支持HTTP时，第二存储服务器176通过HTTP方式从所述第一存储服务器172获取所述文件；所述第二存储服务器176与所述第二终端174建立MSRP链路；
所述第二终端174，配置为通过所述MSRP链路从所述第二存储服务器176获取所述文件。
本申请实施例中，所述文件由第一终端171向一个第二终端174发送；或者，
所述文件由第一终端171向多个第二终端174发送；或者，
所述文件由第一终端171向第一群组发送，所述第一群组包括所述第 一终端171以及多个第二终端174。
本申请实施例中，所述第二应用服务器175，配置为获取所述第二终端174的终端能力信息；或者，获取所述多个第二终端174的终端能力信息。
在第一终端171支持HTTP的场景下：
所述第一终端171，配置为当第一终端171支持HTTP时，所述第一终端171通过HTTP方式向第一存储服务器172发送文件；
所述第二存储服务器176，配置为当第二终端174不支持HTTP时，第二存储服务器176通过HTTP方式从所述第一存储服务器172获取所述文件；与所述第二终端174建立MSRP链路；
所述第二终端174，配置为通过所述MSRP链路从所述第二存储服务器176获取所述文件。
本申请实施例中，所述系统还包括：第一应用服务器173、第二应用服务器175；其中，
所述第一应用服务器173，配置为当所述第二终端174支持HTTP时，第一应用服务器173将所述文件在所述第一存储服务器172中的存储地址发送给第二应用服务器175；
所述第二应用服务器175，配置为将所述存储地址发送给所述第二终端174；
所述第二终端174，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器172中获取所述文件。
本申请实施例中，所述文件由第一终端171向一个第二终端174发送；或者，
所述文件由第一终端171向多个第二终端174发送；或者，
所述文件由第一终端171向第一群组发送，所述第一群组包括所述第一终端171以及多个第二终端174。
本申请实施例中，所述第二应用服务器175，配置为获取所述第二终端174的终端能力信息；或者，获取所述多个第二终端174的终端能力信息。
图18为本申请实施例的文件传输装置的结构组成示意图一，如图18所示，所述装置包括：
生成单元181，配置为当第一终端不支持HTTP时，根据文件在第一存储服务器中的存储地址生成HTTP链接；
封装单元182，配置为将所述HTTP链接封装至即时通讯消息中；
通信单元183，配置为将所述通讯消息发送给第二应用服务器；
所述通信单元183，配置为当第一终端支持HTTP时，第一应用服务器接收所述第一终端发送的携有HTTP链接的即时通讯消息，将所述即时通讯消息发送给第二应用服务器。
图19为本申请实施例的文件传输装置的结构组成示意图二，如图19所示，所述装置包括：
通信单元191，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息；
查询单元192，配置为查询第二终端是否支持HTTP；
所述通信单元191，配置为当所述第二终端不支持HTTP时，向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
在实际应用中，所述文件传输装置中的各个单元所实现的功能，均可由位于文件传输装置中的中央处理器(CPU，Central Processing Unit)、或微处理器(MPU，Micro Processor Unit)、或数字信号处理器(DSP，Digital Signal Processor)、或现场可编程门阵列(FPGA，Field Programmable Gate  Array)等实现。
本申请实施例还提供一种电子设备，该电子设备包括处理器和存储器，所述存储器中存储有计算机程序指令，当所述处理器执行所述计算机程序指令时，所述处理器用于执行本申请实施例任意所述的文件传输方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功 能的步骤。
相应地，本发明实施例还提供一种计算机存储介质，其中存储有计算机程序，该计算机程序配置为执行本发明实施例的文件传输方法。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。
工业实用性
本申请实施例的技术方案，在一种情况下，当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件；当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。在另一种情况下，当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。采用本申请实施例的技术方案，实现了两种协议的终端能够相互传输文件，同时减少了网络流量，以及节省了存储服务器的资源。

Claims (34)

  1. 一种文件传输方法，所述方法包括：
    当第一终端不支持超文本传输协议HTTP时，第一存储服务器与所述第一终端建立消息会话中继协议MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件；
    当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器。
  2. 根据权利要求1所述的文件传输方法，其中，所述当第一终端不支持HTTP时，第一存储服务器与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件，包括：
    当第一终端不支持HTTP时，第一应用服务器接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；
    第一应用服务器向第一终端返回响应消息，所述响应消息携带第一应用服务器的MSRP建链信息；
    第一应用服务器接收第一终端返回的肯定确认消息后，通知第一存储服务器接收第一终端发送的文件；
    第一存储服务器与第一终端根据所述MSRP建链信息建立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；
    第一存储服务器存储接收到的文件，并通知第一应用服务器文件接收成功。
  3. 根据权利要求1所述的文件传输方法，其中，所述当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器，包括：
    当第二终端支持HTTP时，第一应用服务器根据第一存储服务器中存储的文件的路径生成对应的HTTP链接；
    第一应用服务器将所述文件的HTTP链接封装到即时通讯消息体中转发给第二应用服务器。
  4. 一种文件传输方法，所述方法包括：
    第二应用服务器接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP；
    当所述第二终端不支持HTTP时，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
    当所述第二终端支持HTTP时，所述第二应用服务器将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
  5. 根据权利要求4所述的文件传输方法，其中，所述第二应用服务器向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件，包括：
    第二应用服务器向第二存储服务器发送HTTP文件获取通知消息；
    第二存储服务器向第一存储服务器发送HTTP获取请求消息；
    第二存储服务器接收第一存储服务器发送的文件；
    第二存储服务器存储所述文件，并通知第二应用服务器文件接收成功。
  6. 根据权利要求5所述的文件传输方法，其中，所述方法还包括：
    所述第二存储服务器与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
  7. 根据权利要求6所述的文件传输方法，其中，所述第二存储服务器与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件，包括：
    第二应用服务器接收第二终端发送的请求消息，所述请求消息携带文件信息及终端的MSRP建链信息；
    第二应用服务器向第二终端返回响应消息，所述响应消息携带第二应用服务器的MSRP建链信息；
    第二应用服务器接收第二终端发送的肯定确认消息；
    第二应用服务器通知第二存储服务器发送文件；
    第二存储服务器与第二终端根据MSRP建链信息建立MSRP链路，并通过所述MSRP链路向第二终端发送文件；
    第二存储服务器发送文件完成后，通知第二应用服务器文件发送成功。
  8. 一种文件传输方法，所述方法包括：
    当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，所述第一终端通过所述MSRP链路向所述第一存储服务器发送文件；
    当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
    所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
  9. 根据权利要求8所述的文件传输方法，其中，所述方法还包括：
    当所述第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
    所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
  10. 根据权利要求8所述的文件传输方法，其中，
    所述文件由第一终端向一个第二终端发送；或者，
    所述文件由第一终端向多个第二终端发送；或者，
    所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
  11. 根据权利要求10所述的文件传输方法，其中，所述方法还包括：
    所述第二应用服务器获取所述第二终端的终端能力信息；或者，
    所述第二应用服务器获取所述多个第二终端的终端能力信息。
  12. 一种文件传输方法，所述方法包括：
    当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；
    当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；
    所述第二存储服务器与所述第二终端建立MSRP链路，所述第二终端通过所述MSRP链路从所述第二存储服务器获取所述文件。
  13. 根据权利要求12所述的文件传输方法，其中，所述方法还包括：
    当所述第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
    所述第二应用服务器将所述存储地址发送给所述第二终端，所述第二终端根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
  14. 根据权利要求12所述的文件传输方法，其中，
    所述文件由第一终端向一个第二终端发送；或者，
    所述文件由第一终端向多个第二终端发送；或者，
    所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
  15. 根据权利要求14所述的文件传输方法，其中，所述方法还包括：
    所述第二应用服务器获取所述第二终端的终端能力信息；或者，
    所述第二应用服务器获取所述多个第二终端的终端能力信息。
  16. 一种文件传输系统，所述系统包括：存储服务器、应用服务器；其中，
    所述存储服务器，配置为当第一终端不支持HTTP时，与所述第一终端建立MSRP链路，通过所述MSRP链路接收所述第一终端发送的文件；
    所述应用服务器，配置为当第二终端支持HTTP时，将所述文件在所述存储服务器中的存储地址发送给第二应用服务器。
  17. 根据权利要求16所述的文件传输系统，其中，所述应用服务器，配置为当第一终端不支持HTTP时，接收第一终端发送的请求消息，所述请求消息携带文件信息及第一终端的MSRP建链信息；向第一终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第一终端返回的肯定确认消息后，通知所述存储服务器接收第一终端发送的文件；
    所述存储服务器，配置为与第一终端根据所述MSRP建链信息建立MSRP链路，并通过MSRP链路接收所述第一终端发送的文件；存储接收到的文件，并通知所述应用服务器文件接收成功。
  18. 根据权利要求16所述的文件传输系统，其中，所述应用服务器，配置为当第二终端支持HTTP时，根据所述存储服务器中存储的文件的路径生成对应的HTTP链接；将所述文件的HTTP链接封装到即时通讯消息体中转发给第二应用服务器。
  19. 一种文件传输系统，所述系统包括：存储服务器、应用服务器；其中，
    所述应用服务器，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息时，查询第二终端是否支持HTTP；当所述第二终端不支持HTTP时，向所述存储服务器发送文件获取通知消息，以使得所述存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，将所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
  20. 根据权利要求19所述的文件传输系统，其中，所述应用服务器，配置为向所述存储服务器发送HTTP文件获取通知消息；
    所述存储服务器，配置为向第一存储服务器发送HTTP获取请求消息；接收第一存储服务器发送的文件；存储所述文件，并通知第二应用服务器文件接收成功。
  21. 根据权利要求20所述的文件传输系统，其中，所述存储服务器，配置为：与所述第二终端建立MSRP链路，通过所述MSRP链路向所述第二终端发送所述文件。
  22. 根据权利要求21所述的文件传输系统，其中，所述应用服务器，配置为接收第二终端发送的请求消息，所述请求消息携带文件信息及终端的MSRP建链信息；向第二终端返回响应消息，所述响应消息携带所述应用服务器的MSRP建链信息；接收第二终端发送的肯定确认消息；通知所述存储服务器发送文件；
    所述存储服务器，配置为与第二终端根据MSRP建链信息建立MSRP链路，并通过所述MSRP链路向第二终端发送文件；发送文件完成后，通知第二应用服务器文件发送成功。
  23. 一种文件传输系统，所述系统包括：第一终端、第一存储服务器、第一应用服务器、第二终端、第二应用服务器；其中，
    所述第一终端，配置为当第一终端不支持HTTP时，所述第一终端与第一存储服务器建立MSRP链路，通过所述MSRP链路所述第一终端向所述第一存储服务器发送文件；
    所述第一应用服务器，配置为当第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
    所述第二应用服务器，配置为将所述存储地址发送给所述第二终端；
    所述第二终端，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
  24. 根据权利要求23所述的文件传输系统，其中，所述系统还包括：
    第二存储服务器，配置为当所述第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；所述第二存储服务器与所述第二终端建立MSRP链路；
    所述第二终端，配置为通过所述MSRP链路从所述第二存储服务器获取所述文件。
  25. 根据权利要求23所述的文件传输系统，其中，
    所述文件由第一终端向一个第二终端发送；或者，
    所述文件由第一终端向多个第二终端发送；或者，
    所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
  26. 根据权利要求25所述的文件传输系统，其中，所述第二应用服务器，配置为获取所述第二终端的终端能力信息；或者，获取所述多个第二终端的终端能力信息。
  27. 一种文件传输系统，所述系统包括：第一终端、第一存储服务器、第二终端、第二存储服务器；其中，
    所述第一终端，配置为当第一终端支持HTTP时，所述第一终端通过HTTP方式向第一存储服务器发送文件；
    所述第二存储服务器，配置为当第二终端不支持HTTP时，第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；与所述第二终端建立MSRP链路；
    所述第二终端，配置为通过所述MSRP链路从所述第二存储服务器获取所述文件。
  28. 根据权利要求27所述的文件传输系统，其中，所述系统还包括：第一应用服务器、第二应用服务器；其中，
    所述第一应用服务器，配置为当所述第二终端支持HTTP时，第一应用服务器将所述文件在所述第一存储服务器中的存储地址发送给第二应用服务器；
    所述第二应用服务器，配置为将所述存储地址发送给所述第二终端；
    所述第二终端，配置为根据所述存储地址通过HTTP方式从所述第一存储服务器中获取所述文件。
  29. 根据权利要求27所述的文件传输系统，其中，
    所述文件由第一终端向一个第二终端发送；或者，
    所述文件由第一终端向多个第二终端发送；或者，
    所述文件由第一终端向第一群组发送，所述第一群组包括所述第一终端以及多个第二终端。
  30. 根据权利要求29所述的文件传输系统，其中，所述第二应用服务器，配置为获取所述第二终端的终端能力信息；或者，获取所述多个第二终端的终端能力信息。
  31. 一种文件传输装置，所述装置包括：
    生成单元，配置为当第一终端不支持HTTP时，根据文件在第一存 储服务器中的存储地址生成HTTP链接；
    封装单元，配置为将所述HTTP链接封装至即时通讯消息中；
    通信单元，配置为将所述通讯消息发送给第二应用服务器；
    所述通信单元，配置为当第一终端支持HTTP时，第一应用服务器接收所述第一终端发送的携有HTTP链接的即时通讯消息，将所述即时通讯消息发送给第二应用服务器。
  32. 一种文件传输装置，所述装置包括：
    通信单元，配置为接收到第一应用服务器发送的携有HTTP链接的即时通讯消息；
    查询单元，配置为查询第二终端是否支持HTTP；
    所述通信单元，配置为当所述第二终端不支持HTTP时，向第二存储服务器发送文件获取通知消息，以使得所述第二存储服务器通过HTTP方式从所述第一存储服务器获取所述文件；当所述第二终端支持HTTP时，所述即时通讯消息发送给所述第二终端，以使得所述第二终端根据所述HTTP链接从第一存储服务器中获取所述文件。
  33. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令配置为执行权利要求1-15任一项所述的文件传输方法。
  34. 一种电子设备，所述电子设备包括处理器和存储器，所述存储器中存储有计算机程序指令，当所述处理器执行所述计算机程序指令时，所述处理器用于执行权利要求1至15任一项所述的文件传输方法。
PCT/CN2017/113124 2017-01-20 2017-11-27 文件传输方法及系统、装置、电子设备、计算机存储介质 WO2018133542A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710052237.8A CN108337215B (zh) 2017-01-20 2017-01-20 一种文件传输方法及系统、装置、电子设备
CN201710052237.8 2017-01-20

Publications (1)

Publication Number Publication Date
WO2018133542A1 true WO2018133542A1 (zh) 2018-07-26

Family

ID=62907736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/113124 WO2018133542A1 (zh) 2017-01-20 2017-11-27 文件传输方法及系统、装置、电子设备、计算机存储介质

Country Status (2)

Country Link
CN (1) CN108337215B (zh)
WO (1) WO2018133542A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112671899A (zh) * 2020-12-23 2021-04-16 中移（杭州）信息技术有限公司 一种文件传输方法、文件传输装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056320A (zh) * 2007-05-29 2007-10-17 中兴通讯股份有限公司 一种数据会议中的文件传输方法及其系统
CN101309237A (zh) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 一种家庭网关及远程共享多媒体资料的系统和方法
US20090168758A1 (en) * 2007-12-31 2009-07-02 Sony Ericsson Mobile Communications Ab Methods for facilitating communication between internet protocol multimedia subsystem (ims) devices and non-ims devices and between ims devices on different ims networks and related electronic devices and computer program products
CN101505226A (zh) * 2009-02-25 2009-08-12 中国联合网络通信集团有限公司 多媒体通信交互系统和方法
US20150189090A1 (en) * 2013-12-26 2015-07-02 Cellco Partnership D/B/A Verizon Wireless Uniform rcs voice/videomail services

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859380B (zh) * 2005-07-28 2011-12-07 华为技术有限公司 一种离线消息获取方法
CN101047668B (zh) * 2007-03-22 2011-04-13 中兴通讯股份有限公司 扩展信息发送方法
KR101378309B1 (ko) * 2011-11-22 2014-03-28 에스케이텔레콤 주식회사 채팅 중 ｈｔｔｐ를 이용한 파일 전송을 위한 장치 및 기록매체
KR101330051B1 (ko) * 2011-11-29 2014-01-13 에스케이텔레콤 주식회사 수신불능 단말로의 파일 전송 장치 및 기록매체

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101056320A (zh) * 2007-05-29 2007-10-17 中兴通讯股份有限公司 一种数据会议中的文件传输方法及其系统
US20090168758A1 (en) * 2007-12-31 2009-07-02 Sony Ericsson Mobile Communications Ab Methods for facilitating communication between internet protocol multimedia subsystem (ims) devices and non-ims devices and between ims devices on different ims networks and related electronic devices and computer program products
CN101309237A (zh) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 一种家庭网关及远程共享多媒体资料的系统和方法
CN101505226A (zh) * 2009-02-25 2009-08-12 中国联合网络通信集团有限公司 多媒体通信交互系统和方法
US20150189090A1 (en) * 2013-12-26 2015-07-02 Cellco Partnership D/B/A Verizon Wireless Uniform rcs voice/videomail services

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112671899A (zh) * 2020-12-23 2021-04-16 中移（杭州）信息技术有限公司 一种文件传输方法、文件传输装置及系统
CN112671899B (zh) * 2020-12-23 2022-12-13 中移（杭州）信息技术有限公司 一种文件传输方法、文件传输装置及系统

Also Published As

Publication number Publication date
CN108337215A (zh) 2018-07-27
CN108337215B (zh) 2021-07-27

Similar Documents

Publication Publication Date Title
US9781167B2 (en) WebRTC data channel facilitating IMS support of RCS features
KR101150594B1 (ko) 메시지 및 세션의 교환
KR102324354B1 (ko) 호 관련 강화된 정보 공유를 위한 방법 및 장치
US20070070988A1 (en) Method For Transmitting Deferred Messages
KR101054787B1 (ko) Ｉｍｓ 인스턴트 메시지를 전송하기 위한 방법, 시스템, 및장치
US8014775B2 (en) Method and system for implementing messaging services and a message application server
JP5666020B2 (ja) パケット交換ネットワークを介してアプリケーション発信テキスト・メッセージを配送するための方法および装置
WO2007041937A1 (fr) Methode d'envoi et de reception de message hors ligne, appareil client, serveur et systeme
CN107431698A (zh) 电信系统中的ims间服务支持
US10498791B2 (en) Negotiation of message chunk size for message session relay protocol session
US20140059118A1 (en) Method and Devices for Enhanced File Transfer
US20140250197A1 (en) Content server, terminal, and method using http
CN110875914B (zh) 一种基于共享会话链路传输消息的方法及装置
US9350695B2 (en) Method for transferring and storing CPM service message and service thereof
WO2015172629A1 (zh) 一种消息传输的方法、装置及系统
US20120011260A1 (en) Method and system for transmitting large message mode converged IP messaging
WO2018133542A1 (zh) 文件传输方法及系统、装置、电子设备、计算机存储介质
WO2023078458A1 (zh) 通话异常处理方法、装置及电子设备
CN109120578B (zh) 一种实现链路连接处理的方法及装置
US8719424B2 (en) Transmission method and system for converged IP messaging
KR100690793B1 (ko) 멀티미디어 시스템에서의 데이터 전송방법
US20140258476A1 (en) File transmission to communication-disabled terminal
KR20080090250A (ko) 이종 메시지의 상호 연동을 통한 메시지 전송 방법
KR101467970B1 (ko) 패킷-스위치된 네트워크를 통해 ao 문자 메시지들을 전달하기 위한 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17892622

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17892622

Country of ref document: EP

Kind code of ref document: A1