Method for transmitting multimedia information, terminal and communication platform

By initiating an HTTP request from the terminal to obtain the program script and using the authentication platform for authentication, a token is obtained for multimedia information transmission. This solves the problems of high terminal modification costs and long business development cycles in VoLTE and WebRTC, and realizes real-time interaction of multimedia information and business interconnection.

CN115913557BActive Publication Date: 2026-03-27CHINA MOBILE COMM LTD RES INST +1
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-08-04
Publication Date
2026-03-27

AI Technical Summary

Technical Problem

Existing technologies in VoLTE and WebRTC suffer from high terminal modification costs, long service development cycles, and difficulties in service interconnection, making it impossible to achieve real-time interaction of multimedia information.

Method used

The terminal initiates an HTTP request to obtain the program script, uses the authentication platform for identity authentication, obtains a token, and interacts with the communication platform to achieve multimedia information transmission. The terminal does not need to modify the underlying IMS protocol stack and utilizes the HTTP protocol and operator network equipment.

Benefits of technology

It reduced the cost of terminal modification, shortened the business development cycle, and enabled the interconnection of multimedia services, thereby improving the ability to quickly launch services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115913557B_ABST
    Figure CN115913557B_ABST
Patent Text Reader

Abstract

A multimedia information transmission method, terminal and communication platform, the method comprising: receiving a first HTTP request sent by a first terminal, the first HTTP request carrying a second terminal identifier of a second terminal; in a case where the first terminal and the second terminal are in a call state, sending a first program script to the first terminal, the first program script comprising script code for assisting the terminal to initiate an authentication request to an authentication platform; receiving a second HTTP request sent by the first terminal, the second HTTP request carrying a token of the first terminal; and authenticating the token of the first terminal by using the authentication platform, and in a case where the authentication is successful, sending first multimedia information to the first terminal. The present application does not need to modify the terminal bottom IMS protocol stack, greatly saves the terminal modification cost and service development period and can be implemented by using the existing equipment in the operator network, and is beneficial to realizing the interconnection and intercommunication of multimedia services.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data communication, in particular to a multimedia information transmission method, terminal and communication platform. BACKGROUND

[0002] In addition to audio and video interaction, other multimedia assisted call information interaction is realized in the call, and the prior art mainly has the following two technical solutions:

[0003] Solution 1: In the Voice over Long-Term Evolution (VoLTE) phone of the current communication operator, only audio and video data can be transmitted, and the audio and video data interaction in the call can only be completed through Dual-Tone Multi-Frequency (DTMF), and there is no method for transmitting other data, and the ability of multimedia real-time interaction is lacking.

[0004] Solution 2: In the field of Internet, the audio and video call solution based on Web Real-Time Communication (WebRTC) technology also provides a data channel (DataChannel), creates a data channel in the call process, provides assisted call function, and realizes the interaction of multimedia call ability.

[0005] Both of the above two technical solutions have their own limitations, for example, solution 1 does not have the ability to transmit other data in addition to audio and video data, and if modified, the bottom IP Multimedia Subsystem (IMS) protocol stack needs to be modified, which needs to promote the chip manufacturers to implement. This solution is heavily dependent on the modification of the terminal side system application, and needs to be deeply developed and integrated, and the iteration speed is slow, which is not conducive to the rapid online of the business. Generally, the development progress of the terminal manufacturer needs to wait for the chip manufacturer to complete the function before starting the upper layer development, and the cycle is about 6-10 months, in addition to the time for online testing, so the business development cycle is too long, which cannot meet the time requirements of new call business. Solution 2 cannot interwork with the VoLTE of the operator, and is based on the account system of each Internet manufacturer or terminal manufacturer, which has great limitations and is not conducive to interconnection.

[0006] Therefore, a multimedia information transmission method is needed to reduce the modification cost of the terminal, shorten the development cycle of the business and be conducive to the interconnection of the business. SUMMARY

[0007] At least one embodiment of the present application provides a multimedia information transmission method, terminal and communication platform, which can reduce the modification cost of the terminal, shorten the development cycle of the business and be conducive to the interconnection of the business.

[0008] According to an aspect of the present application, at least one embodiment provides a multimedia information transmission method applied to a communication platform, comprising:

[0009] receiving a first HTTP request sent by a first terminal, the first HTTP request carrying a second terminal identifier of a second terminal;

[0010] in a case where the first terminal and the second terminal are in a call state, sending a first program script to the first terminal, the first program script comprising script code for assisting the terminal to initiate an authentication request to an authentication platform;

[0011] receiving a second HTTP request sent by the first terminal, the second HTTP request carrying a token of the first terminal;

[0012] authenticating the token of the first terminal by using the authentication platform, and in a case where the authentication is successful, sending first multimedia information to the first terminal.

[0013] According to another aspect of the present application, at least one embodiment provides a multimedia information transmission method applied to a first terminal, comprising:

[0014] in a case where the first terminal detects that the terminal enters a call state with a second terminal, sending a first HTTP request to a communication platform, the first HTTP request carrying a second terminal identifier of the second terminal;

[0015] receiving a first program script sent by the communication platform, the first program script comprising script code for assisting the terminal to initiate an authentication request to an authentication platform;

[0016] initiating an authentication request to the authentication platform by using the first program script, and receiving a first token allocated to the first terminal by the authentication platform after the authentication is passed;

[0017] sending a second HTTP request to the communication platform, the second HTTP request carrying the first token;

[0018] receiving first multimedia information sent by the communication platform and displaying the first multimedia information locally.

[0019] According to another aspect of the present application, at least one embodiment provides a communication platform, comprising a transceiver and a processor, wherein,

[0020] The transceiver is configured to receive a first HTTP request sent by a first terminal, the first HTTP request carrying a second terminal identifier of a second terminal; send a first program script to the first terminal in a case where the first terminal and the second terminal are in a call state, the first program script including script code for assisting the terminal to initiate an authentication request to an authentication platform; and receive a second HTTP request sent by the first terminal, the second HTTP request carrying a token of the first terminal.

[0021] The processor is configured to authenticate the token of the first terminal by using the authentication platform, and send first multimedia information to the first terminal in a case where the authentication is successful.

[0022] According to another aspect of the present application, at least one embodiment provides a communication platform, comprising a processor, a memory, and a program stored in the memory and executable in the processor, the program, when executed by the processor, implements the steps of the method as described above.

[0023] According to another aspect of the present application, at least one embodiment provides a first terminal, comprising a transceiver and a processor, wherein,

[0024] The transceiver is configured to send a first HTTP request to a communication platform in a case where it is detected that the terminal enters a call state with a second terminal, the first HTTP request carrying a second terminal identifier of the second terminal; and receive a first program script sent by the communication platform, the first program script including script code for assisting the terminal to initiate an authentication request to an authentication platform.

[0025] The processor is configured to initiate an authentication request to the authentication platform by using the first program script, and receive a first token allocated to the first terminal by the authentication platform after the authentication is passed; send a second HTTP request to the communication platform, the second HTTP request carrying the first token; and receive first multimedia information sent by the communication platform and display the first multimedia information locally.

[0026] According to another aspect of the present application, at least one embodiment provides a first terminal, comprising a processor, a memory, and a program stored in the memory and executable in the processor, the program, when executed by the processor, implements the steps of the method as described above.

[0027] According to another aspect of the present application, at least one embodiment provides a computer readable storage medium, the computer readable storage medium storing a program, the program, when executed by a processor, implements the steps of the method as described above.

[0028] Compared with the prior art, the method for transmitting multimedia information, the terminal and the communication platform provided by the embodiment of the present application have the following advantages: the terminal requests a program script from the communication platform by means of an HTTP request, the authentication platform provides the program script to the terminal in a call state, the terminal obtains a token, and the terminal initiates an HTTP request for a related service to the communication platform by using the token. In the above process, the terminal can interact with the communication platform by means of the HTTP request, so that the underlying IMS protocol stack of the terminal does not need to be modified, and the modification cost and the service development period of the terminal can be greatly saved. In addition, the terminal has widely supported the HTTP protocol, and the above scheme can be implemented by using the existing equipment in the operator network, which is beneficial to the interconnection and intercommunication of the multimedia service. BRIEF DESCRIPTION OF DRAWINGS

[0029] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The detailed description is made with reference to the accompanying drawings.

[0030] Figure 1 An interaction schematic diagram of the method for transmitting multimedia information according to the embodiment of the present application;

[0031] Figure 2 A flowchart when the method for transmitting multimedia information according to the embodiment of the present application is applied to a call platform;

[0032] Figure 3 A flowchart when the method for transmitting multimedia information according to the embodiment of the present application is applied to a first terminal;

[0033] Figure 4 An interaction flow example diagram of the method for transmitting multimedia information according to the embodiment of the present application;

[0034] Figure 5 Another interaction flow example diagram of the method for transmitting multimedia information according to the embodiment of the present application;

[0035] Figure 6 A structure schematic diagram of the call platform according to the embodiment of the present application;

[0036] Figure 7 Another structure schematic diagram of the call platform according to the embodiment of the present application;

[0037] Figure 8 A structure schematic diagram of the first terminal according to the embodiment of the present application;

[0038] Figure 9 Another structure schematic diagram of the first terminal according to the embodiment of the present application. Detailed Implementation

[0039] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0040] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The terms “and / or” in the specification and claims indicate at least one of the connected objects.

[0041] The technology described herein is not limited to NR systems and Long Time Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used for various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. UTRA includes Wideband-CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system can implement a radio technology such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.21 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). LTE and LTE-Advanced (e.g., LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2).The techniques described herein can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. The description below, however, describes a NR system for purposes of example, and NR terminology is used in much of the description below, although the techniques are applicable beyond NR systems.

[0042] The following description provides examples, and is not limiting of the scope, applicability, or configuration set forth in the claims. Changes can be made in the function and arrangement of elements discussed without departing from the scope and spirit of aspects of the disclosure. Various examples can omit, substitute, or add various procedures or components as appropriate. For instance, the methods described can be performed in an order different from that described, and various steps can be added, omitted, or combined. Also, features described with respect to certain examples can be combined in other examples.

[0043] As described in the background, the scheme of realizing multimedia information interaction in the call process in the prior art usually has problems such as high modification cost of the terminal, long service development period or difficulty in interconnection and intercommunication of the service. To solve at least one of the above problems, the embodiment of the present application provides a multimedia information transmission method, which can reduce the modification cost of the terminal, shorten the development period of the service and be beneficial to the interconnection and intercommunication of the service.

[0044] The embodiment of the present application provides a multimedia information transmission method, which realizes an auxiliary call scheme of multimedia information based on a browser at the terminal side, and service logic can be realized at the communication platform side and realized by using a Web mode at the terminal side. In the scheme, the terminal initiates an HTTP request, requests a call platform, and obtains a multimedia interaction content main menu or other multimedia information. The communication platform returns a corresponding HTML5 page to the terminal according to a main called number and a call state. In addition, the platform returned page can carry a JavaScript script, which is used for subsequent service processing. The security and reliability of terminal identity authentication need to be ensured in the process of user request to the platform.

[0045] In the embodiment of the present application, the VoLTE original call module at the terminal side does not need to be modified, a WebView control can be integrated on the terminal call interface to realize the initiation of the HTTP request, the rendering of the HTML5 and the like, and a small amount of interface is provided for the WebView. The identity authentication of the terminal can adopt an operator unified authentication platform to authenticate the legality of the user.

[0046] Please refer to Figure 1 The multimedia information transmission method provided by the embodiment of the present application is shown in a flowchart of interaction between a plurality of devices. Figure 1The system mainly comprises a first terminal (a calling terminal), a second terminal (a called terminal), a communication platform and an authentication platform. For better understanding, Figure 1 Some transmission devices (such as gateway devices) in a mobile communication network are omitted in the system. As shown in the figure, Figure 1 The flow comprises the following steps:

[0047] In step 101, when the calling terminal and the called terminal establish a call, the terminals initiate a first HTTP request to the communication platform, and the communication platform returns a program script.

[0048] Here, the calling terminal and the called terminal can respectively send the first HTTP request to the communication platform when establishing a call, and the request carries terminal identification information of the call opposite terminal, such as the terminal number of the second terminal. The first HTTP request is used to request the communication platform to provide a program script. Figure 1 In the embodiment, only the first terminal initiates the first HTTP request is taken as an example for description. In addition, the call establishment here refers to the terminal in a call state, and the call state comprises any one of a ringing state, a voice call state, a video call state and a call waiting state. The program script at least comprises a script code for assisting the terminal to initiate an authentication request to the authentication platform, and the program script comprises but is not limited to a JS script code.

[0049] In step 102, after the communication platform receives the first HTTP request, it checks the communication state of the first terminal, and in the case that the first terminal and the second terminal are in a call state, it sends a first program script to the first terminal, and the first program script comprises a script code for assisting the terminal to initiate an authentication request to the authentication platform. The first terminal receives the first program script sent by the communication platform, and the first program script comprises a script code for assisting the terminal to initiate an authentication request to the authentication platform.

[0050] In step 103, the first terminal initiates an authentication request to the authentication platform by using the first program script, and the authentication request can be sent through an HTTP request. When the authentication request is sent through a gateway in a communication network, the gateway adds the first terminal identification of the first terminal, such as the calling number of the first terminal, in the authentication request.

[0051] In step 104, after the authentication platform receives the authentication request of the first terminal, it authenticates the first terminal, and various authentication manners of the prior art can be adopted, and the embodiment of the present application does not make a specific limitation. After authentication, a token (namely, token, assuming a first token) is allocated to the first terminal, a corresponding relationship between the first terminal identification and the first token is generated and saved, and then the first token is sent to the first terminal. The first terminal receives the first token allocated to the first terminal by the authentication platform.

[0052] Step 105: The first terminal sends a second HTTP request to the communication platform, the second HTTP request carrying the first token.

[0053] Step 106: The communication platform receives the second HTTP request and authenticates the first token information. For example, it requests the authentication platform to authenticate the first token and receives the authentication result returned by the authentication platform. Based on the authentication result, it determines whether the authentication was successful. If the authentication is successful, it returns the first multimedia information to the first terminal.

[0054] The first multimedia information here can specifically be a webpage file or the webpage address corresponding to a webpage file. The content of this webpage file can be the user interactive interface for call services, multimedia caller ID content, or other multimedia service information.

[0055] It should also be noted that Figure 1 This explanation uses the interaction between the first terminal and the platform as an example. The second terminal can also interact with the platform through similar steps; that is, the roles of the first and second terminals in the above process can be interchanged. Furthermore, the first terminal can be either the calling terminal or the called terminal.

[0056] from Figure 1 As can be seen from the steps described, in this embodiment of the invention, the terminal requests a program script from the communication platform via an HTTP request. The authentication platform then provides the program script to the terminal in a call state, assisting the terminal in obtaining a token. The terminal then uses this token to initiate an HTTP request for related services to the communication platform. Since the terminal can interact with the communication platform via HTTP requests in the above process, there is no need to modify the terminal's underlying IMS protocol stack, which can greatly save on terminal modification costs and service development cycles. Furthermore, since terminals now widely support the HTTP protocol, and the above solution fully utilizes existing equipment in the operator's network, it is beneficial for achieving interconnectivity of multimedia services.

[0057] Please refer to Figure 2 The multimedia information transmission method of this invention, when applied to a communication platform, includes:

[0058] Step 201: The communication platform receives a first HTTP request sent by the first terminal, the first HTTP request carrying the second terminal identifier of the second terminal.

[0059] Here, the second terminal identifier can be a terminal number of the second terminal, and the first HTTP request is used to request the communication platform to provide a program script. In addition, when the first HTTP request is routed to the communication platform through the communication network, the gateway device usually adds the identifier of the first terminal, such as the terminal number of the first terminal, in the message of the first HTTP request.

[0060] In step 202, when the first terminal and the second terminal are in a call state, the communication platform sends a first program script to the first terminal, and the first program script includes script code for assisting the terminal to initiate an authentication request to the authentication platform.

[0061] Here, the communication platform receives the first HTTP request, judges whether the first terminal is in a call state with the second terminal, and the call state includes at least one of a ringing state, a voice call state, a video call state, and a call waiting state. If yes, the first program script is sent to the first terminal, so that the first terminal initiates authentication to the authentication platform by using the first program script and obtains a token allocated by the authentication platform.

[0062] In step 203, the communication platform receives a second HTTP request sent by the first terminal, and the second HTTP request carries the token of the first terminal.

[0063] In step 204, the communication platform authenticates the token of the first terminal by using the authentication platform, and sends first multimedia information to the first terminal when the authentication is successful.

[0064] Here, the communication platform authenticates the token of the first terminal carried by the second HTTP request, and the authentication can be performed by the authentication platform. When the authentication is successful, the first multimedia information is returned to the first terminal. For example, the communication platform sends the token of the first terminal to the authentication platform, and receives an authentication result of the token of the first terminal returned by the authentication platform. When the authentication platform judges that the token of the first terminal is the same as the token allocated to the first terminal by the authentication platform, the authentication result is authentication passed, otherwise, the authentication result is authentication failed.

[0065] In the embodiment of the present application, the second HTTP request can also carry the second terminal identifier, and the communication platform can acquire the first multimedia information to be sent to the first terminal according to at least one of the call state, the call role and the multimedia call service registered by the first terminal and the second terminal, wherein the call role includes calling and called. For example, when the first terminal is calling and in the ringing state, the interactive interface of the call service can be returned to the first terminal; when the first terminal is called and in the ringing state, the caller display information of the second terminal, such as the multimedia business card of the second terminal, can be sent to the first terminal. In addition, the communication platform can also request the service server for the multimedia information of the second terminal to be displayed in the current call state, receive the first multimedia information returned by the service server, and then send the first multimedia information to the first terminal for playing.

[0066] As the first implementation, the first program script further includes script code for assisting the terminal to initiate a service request to the communication platform. In the step 203, the second HTTP request is an HTTP request for requesting the multimedia information of the first service sent by the first terminal using the first program script. The second HTTP request can carry the service identifier information of the first service, or can not carry any service identifier, in which case the multimedia information of the preset default service is requested.

[0067] In the first implementation, after receiving the second HTTP request, the communication platform generates a first token key (referred to as tokenKey herein) for identifying the first terminal according to the first terminal identifier of the first terminal, the domain name of the communication platform and the token of the first terminal, and then sends the first token key to the first terminal, for example, the first token key is sent to the first terminal while the first multimedia information is returned in the step 204.

[0068] In the embodiment of the present application, the websocket connection can also be established between the terminal and the communication platform, so that the subsequent multimedia information interaction between the terminal and the communication platform can be transmitted through the websocket connection.

[0069] In the first implementation manner, the first program script can further include script code for assisting the terminal to initiate a websocket connection with the communication platform; after step 204, the communication platform can further receive a third HTTP request for establishing an end-to-end websocket connection sent by the first terminal, the third HTTP request carrying a token key of the first terminal and a second terminal identifier; the token key of the first terminal is authenticated, and whether the authentication is passed is determined according to whether the token key of the first terminal is the same as a first token key allocated by the communication platform for the first terminal, and after the authentication is passed, the first websocket connection between the communication platform and the first terminal is established in response to the third HTTP request.

[0070] Next, the communication platform can receive a first service request message sent by the first terminal through the first websocket connection, the first service request message carrying the token key of the first terminal; then, the token key of the first terminal is authenticated, and after the authentication is passed, the first terminal is sent multimedia information corresponding to the first service request message through the first websocket connection.

[0071] Similarly, the communication platform can establish a second websocket connection with the second terminal in the same manner as described above, for example, the communication platform can receive a fourth HTTP request for an end-to-end websocket connection sent by the second terminal, the fourth HTTP request carrying a token key of the second terminal and a first terminal identifier of the first terminal; the token key of the second terminal is authenticated, and after the authentication is passed, the second websocket connection between the communication platform and the second terminal is established in response to the fourth HTTP request.

[0072] In actual application, the multimedia information of the terminal can be updated, and the terminal can send the updated multimedia information to the service server. The embodiment of the application can update the multimedia information between the communication terminals in time through the websocket connection by using the update mechanism.

[0073] Taking an example of multimedia information update of the second terminal, the communication platform can receive the multimedia information update notification message sent by the second terminal through the second websocket connection, and forward the multimedia information update notification message to the first terminal through the first websocket connection. Then, the communication platform receives the second service request message sent by the first terminal, the second service request message carrying the token key of the first terminal, authenticates the token key of the first terminal, and after the authentication is passed, requests the service server for the updated multimedia information of the second terminal. Then, the communication platform receives the updated multimedia information of the second terminal sent by the service server, and forwards the updated multimedia information of the second terminal to the first terminal through the first websocket connection.

[0074] In the first implementation manner, the first terminal establishes the first websocket connection with the communication platform after receiving the response (the first multimedia information) of the communication platform to the second HTTP. In the second implementation manner, the terminal sends the second HTTP request to request to establish the first websocket connection, so that the subsequent first multimedia information can be directly sent through the first websocket connection.

[0075] Specifically, in the second implementation manner, the first program script returned to the first terminal in step 202 further includes script code for assisting the terminal to initiate the websocket connection to the communication platform, so that the first terminal initiates the establishment request of the websocket connection according to the first program script. In step 203, the second HTTP request received by the communication platform is the HTTP request for initiating the websocket connection sent by the first terminal using the first program script. In step 204, the communication platform authenticates the token of the first terminal using the authentication platform, and in the case of successful authentication, establishes the first websocket connection with the first terminal in response to the second HTTP request, and then sends the first multimedia information to the first terminal through the first websocket connection.

[0076] Subsequently, the communication platform can receive the third service request message sent by the first terminal through the first websocket connection, the third service request message carrying the token of the first terminal, then authenticate the token of the first terminal, and after the authentication is passed, send the multimedia information corresponding to the third service request message to the first terminal through the first websocket connection.

[0077] Similarly, the communication platform can also establish a second websocket connection with the second terminal in the above manner. Specifically, the communication platform can receive a fifth HTTP request for initiating a websocket connection sent by the second terminal, the fifth HTTP request carrying a token of the second terminal. Then, the communication platform authenticates the token of the second terminal by using the authentication platform, and in the case of successful authentication, establishes a second websocket connection with the second terminal in response to the fifth HTTP request.

[0078] Similarly, when the multimedia information of the terminal is updated, the embodiment of the application can update in time through the websocket connection. Still taking the multimedia information of the second terminal as an example, the communication platform receives a multimedia information update notification message sent by the second terminal through the second websocket connection, and forwards the multimedia information update notification message to the first terminal through the first websocket connection. Then, the communication platform receives a fourth service request message sent by the first terminal, the fourth service request message carrying a token of the first terminal. The communication platform authenticates the token of the first terminal, specifically, the communication platform can send the token of the first terminal to the authentication platform, receive an authentication result returned by the authentication platform, and request the service server for the updated multimedia information of the second terminal after the authentication is passed. Then, the communication platform receives the updated multimedia information of the second terminal sent by the service server, and forwards the updated multimedia information to the first terminal through the first websocket connection.

[0079] In the above steps, the service request message sent by the terminal (such as the first, second, third, and fourth service request messages described above) can be sent by using an HTTP request. The URL of the service request message can include at least one of the following parameters:

[0080] The calling number or the token key of the calling number;

[0081] The called number or the token key of the called number;

[0082] The call state;

[0083] The initiator of the service request message is the caller or the callee;

[0084] The service route flag corresponding to the requested service.

[0085] The above describes the method of the embodiment of the application from the communication platform side. The following describes the method from the first terminal side. It should be noted that the first terminal and the second terminal in the following embodiments have reciprocity, i.e., the roles of the two terminals can be interchanged.

[0086] Please refer to Figure 3 The multimedia information transmission method of the embodiment of the present application, when applied to the first terminal, comprises:

[0087] Step 301, the first terminal sends a first HTTP request to the communication platform when detecting that the terminal enters a call state with the second terminal, the first HTTP request carrying a second terminal identifier of the second terminal.

[0088] Here, the call state comprises at least one of a ringing state, a voice call state, a video call state and a call waiting state. The address of the communication platform can be notified to the terminal by the network during the terminal accessing the network, or can be pre-stored in the terminal. The first HTTP request is used to request a program script from the communication platform.

[0089] Step 302, the first terminal receives a first program script sent by the communication platform, the first program script comprising script code for assisting the terminal to initiate an authentication request to the authentication platform.

[0090] Step 303, the first terminal initiates an authentication request to the authentication platform by using the first program script, and receives a first token allocated to the first terminal by the authentication platform after the authentication is passed.

[0091] Step 304, the first terminal sends a second HTTP request to the communication platform, the second HTTP request carrying the first token.

[0092] Here, the second HTTP request is used to request multimedia information of a first service from the communication platform. The second HTTP request can carry service identification information of the first service, or can not carry any service identification information, in which case it is considered to request multimedia information of a preset default service.

[0093] Step 305, the first terminal receives first multimedia information sent by the communication platform and displays it locally.

[0094] After the first token is authenticated by the communication platform, first multimedia information of the first service can be returned. The first multimedia information can be a web page file or a web page address corresponding to the web page file. After being received by the first terminal, it is played locally, such as displaying web page content and / or playing audio and video files in the first multimedia information, etc.

[0095] Corresponding to the first implementation manner described above, the first program script further includes script code for assisting the terminal to initiate a service request to the communication platform; the second HTTP request sent in step 304 is an HTTP request sent by the first terminal using the first program script to request multimedia information corresponding to a first service. The second HTTP request can carry service identification information of the first service, or can not carry any service identification, in which case, the multimedia information of a preset default service is requested.

[0096] After sending the second HTTP request, the first terminal can further receive a first token key (i.e., tokenKey) returned by the communication platform to identify the first terminal. Specifically, the first token key can be received at the same time as the first multimedia information is received in step 305.

[0097] In the embodiment of the application, the first program script can further include script code for assisting the terminal to initiate a websocket connection to the communication platform. In the first implementation manner described above, the first terminal can use the first program script to send a third HTTP request to establish an end-to-end websocket connection, the third HTTP request carrying the first token key and the second terminal identification. Then, a response message sent by the communication platform after passing the authentication of the first token key is received, and a first websocket connection between the first terminal and the communication platform is established.

[0098] Subsequently, the first terminal can send a first service request message to the communication platform through the first websocket connection, the first service request message carrying the first token key; then, the first terminal receives and displays the multimedia information corresponding to the first service request message returned by the communication platform through the first websocket connection.

[0099] In the multimedia information updating process of the second terminal, the first terminal can receive a multimedia information updating notification message of the second terminal sent by the communication platform through the first websocket connection; then, a second service request message for requesting to update the multimedia information of the second terminal is sent to the communication platform through the first websocket connection, the second service request message carrying the token key of the first terminal; then, the first terminal receives the updated multimedia information of the second terminal sent by the communication platform through the first websocket connection.

[0100] Corresponding to the first implementation manner described above, the first program script further includes script code for assisting the terminal to initiate a websocket connection with the communication platform; the second HTTP request is an HTTP request for initiating a websocket connection sent by the first terminal using the first program script; in step 305, the first terminal receives the first multimedia information sent by the communication platform, specifically, the first terminal can receive a response message sent by the communication platform after passing the authentication of the first token, establish a first websocket connection with the communication platform, and receive and display the first multimedia information sent by the communication platform through the first websocket connection.

[0101] Subsequently, the first terminal can send a third service request message to the communication platform through the first websocket connection, the third service request message carrying the first token, and receive and display the multimedia information corresponding to the third service request message returned by the communication platform through the first websocket connection.

[0102] In the multimedia information updating process, the first terminal can receive the multimedia information updating notification message of the second terminal sent by the communication platform through the first websocket connection. Then, the first terminal sends a fourth service request message for requesting to update the multimedia information of the second terminal to the communication platform through the first websocket connection, the fourth service request message carrying the first token. Then, the first terminal receives the updated multimedia information of the second terminal sent by the communication platform through the first websocket connection.

[0103] Here, the URL of the service request message sent by the first terminal includes at least one of the following parameters:

[0104] The calling number or the token key of the calling number;

[0105] The called number or the token key of the called number;

[0106] The call state;

[0107] The initiator of the service request message is the caller or the callee;

[0108] The service route flag corresponding to the requested service.

[0109] The first and second implementation manners are described below through the interaction process between devices.

[0110] Please refer to Figure 4The first implementation manner is given in the interaction flow between devices, in which the WebSocket channel is created to assist the new call service. The terminal first requests the call platform through the HTTP GET method, and the platform returns the HTML5 page and the JS script. The terminal obtains the token through the unified authentication platform by using the JS script. Thus, the JS script obtains the token, and then requests the call platform for service processing. After the platform returns the HTML5 page, the terminal displays the page and initiates the WebSocket request to create the bidirectional connection through the JS script, so that the communication platform can actively push the update request to the terminal, and the multimedia information is updated in time. As shown in FIG. 8, Figure 4 The flow includes the following steps.

[0111] Step 400: The calling UE B and the called UE A establish a normal VoLTE call.

[0112] Steps 401-402: The called UE A starts the browser or the WebView control, and requests the call platform to download the JS code. After receiving the request, the call platform returns a piece of JS program to the UE A.

[0113] Steps 403-404: The called UE A uses the above JS program to initiate the HTTP request to the authentication server to request the authentication token. The authentication server returns the token after authenticating the UE A. After receiving the token, the UE A caches the token locally.

[0114] Steps 405-410: The called UE A sends the HTTP Get request to the call platform through the JS code, and the request carries the token. After receiving the above request with the token, the call platform verifies the token with the authentication server. If the token is valid, the authentication is passed. The communication platform queries the call state of the terminal through the IMS core network (VoLTE AS). When it is found that the calling MO and the called MT numbers are in the pre-call state (ringing), if the terminal subscribes to the multimedia caller ID (also referred to as the multimedia caller display in the present document), the terminal's multimedia caller display is requested from the service AS, and the HTML5 page of the multimedia caller display is returned to the UE A, which can be carried through the 200 OK message. In addition, the call platform can generate the token key tokenkey based on the number of the UE A and send the token key to the UE A in step 410. The terminal needs to support the JS running environment. After receiving the tokenkey, the subsequent operation is based on the tokenkey.

[0115] Step 411: The terminal obtains the HTML5 page of the media content from the 200 OK returned by the call platform, and displays the page through the browser.

[0116] In addition, the terminal can also establish an end-to-end WebSocket connection with the call platform through JS code, for subsequent updating of multimedia file content.

[0117] Steps 412-414: UE B uploads or modifies new multimedia content to the service AS, which can be achieved by browser file upload. If the upload is successful, UE B can notify UE A to update the media information through the WebSocket connection.

[0118] Steps 415-416: The called UE A carries the last tokenkey and initiates an HTTP request through JS code. The browser can cache the tokenkey. If the tokenkey is not expired, the call platform can return the media information normally. If the tokenkey is expired, UE A needs to obtain a new tokenkey through JS code, initiate a request carrying the new tokenkey, and the call platform returns new multimedia content. UE A updates the media content in the browser. Here, the call platform can obtain new multimedia content from the service AS.

[0119] Please refer to Figure 5 , which gives the interaction flow between devices in the above-mentioned second implementation mode, in which a WebSocket channel is created for homepage URL push. The terminal first requests the call platform through the HTTP GET method. The call platform returns a JS script. The terminal obtains a token through the unified authentication platform using the JS script. After receiving the token, the terminal initiates a WebSocket request through the JS script. The call platform pushes the URL of the new call service homepage to the terminal through the WebSocket bidirectional connection. The terminal displays, and subsequent service platforms can push content to the terminal based on this WebSocket. As shown in Figure 5 , the flow includes:

[0120] Step 500: The calling UE B and the called UE A establish a normal VoLTE call.

[0121] Steps 501-502: The called UE A starts the browser or uses the WebView control to request the call platform to download the JS code. After receiving the request, the call platform returns a piece of JS program to the UE A.

[0122] Steps 503-504: The called UE A uses the above-mentioned JS program to initiate an HTTP request to the authentication server to request an authentication token. The authentication server returns the token after authenticating the UE A. The UE A caches the token locally after receiving the token.

[0123] Steps 505-510: The called UE A sends an HTTP Get request to the call platform through JS code, the request carrying a token, a call state and a mobile phone number, for requesting to establish a WebSocket connection with the call platform. After receiving the above request with the token, the call platform checks the token with the authentication server. If the token is valid, the authentication is passed. The communication platform queries the call state of the terminal through the IMS core network (VoLTE AS). When it is found that the calling MO and the called MT numbers are both in the ringing state, if the terminal subscribes to multimedia caller ID (also referred to as multimedia caller display in the present document), the multimedia caller display of the terminal is requested from the service AS, and the multimedia caller display returned by the service AS is received. After the authentication is passed, the call platform sends a 200 OK response message to the UE A, the response message being used to indicate that the WebSocket connection is successfully created.

[0124] Step 511: The call platform returns a URL link of an HTML5 page corresponding to the service according to the state of the terminal through the WebSocket connection. After receiving the URL link, the terminal displays the HTML5 page through browser rendering.

[0125] Steps 512-513: The UE A can also initiate a service request through the WebSocket connection, the request carrying the token. The call platform returns multimedia content of the service, and the UE A displays the multimedia content through browser rendering.

[0126] In addition, the terminal can also establish an end-to-end WebSocket connection with the call platform through JS code, for subsequent update of multimedia file content.

[0127] Steps 514-516: The UE B uploads or modifies new multimedia caller display content to the service AS, which can be implemented through a browser. If the uploading is successful, the UE B can notify the UE A to update the multimedia information through the WebSocket connection. The call platform can send the updated URL to the UE A through the WebSocket connection, and the UE A displays the URL through browser rendering.

[0128] In the first implementation mode, the one-time token key generated based on the mobile phone number (or terminal identifier) is used to ensure the secure WebSocket connection between the terminal and the call platform in the process of creating the WebSocket connection through the HTTP protocol. The value (token key) of the Sec-WebSocket-key used for WebSocket creation is as follows:

[0129] Sec-WebSocket-Key: {authentication: 5A4BXXX (token)}

[0130] An example of the HTTP GET message is as follows:

[0131] GET / chat HTTP / 1.1

[0132] Upgrade: websocket

[0133] Connection: Upgrade

[0134] Sec-WebSocket-Key: {authentication: 5A4BXXX}

[0135] IMPI: 13811060120

[0136] Sec-WebSocket-Protocol: chat, superchat

[0137] Sec-WebSocket-Version: 13

[0138] The value (5A4BXXX) of the authentication field is the token key returned by the platform.

[0139] After receiving the above GET message, the call platform verifies the Sec-WebSocket-Key, and if the verification is passed, the following message is returned to create a WebSocket successfully:

[0140] HTTP / 1.1 101 Switching Protocols

[0141] Upgrade: websocket

[0142] Connection: Upgrade

[0143] Sec-WebSocket-Accept: {Authenticated: ok, lifetime: xxx}

[0144] Sec-WebSocket-Protocol: chat

[0145] Sec-WebSocket-Version: 13

[0146] The terminal judges by the JS code, if receiving Authenticated: ok, then it indicates that the WebSocket connection is created successfully.

[0147] In the embodiment of the application, the call platform needs a security mechanism to ensure the authentication of user requests, that is, any terminal cannot request the URL of the new call platform, therefore, the embodiment of the application introduces a user identity authentication and tokenKey generation rule, adopts a H5 unified authentication based mode to perform identity authentication on the user, authenticates based on the user's mobile phone number, and only in the call state can the request be made (different from traditional Internet applications). The call platform can obtain the mobile phone number (or terminal identifier) through the unified authentication server, in order to ensure security, based on the mobile phone number (or terminal identifier), a one-time tokenKey is generated according to an algorithm and returned to the terminal, and the terminal requests the server after obtaining the tokenKey. A generation rule of the tokenKey is as follows:

[0148] tokenKey = MD5 (mobile number: realm: unified authentication token)

[0149] Wherein, the realm is a Fully Qualified Domain Name (FQDN) of the new call platform.

[0150] In the embodiment of the application, the terminal needs to actively request the call platform to initiate a new call service, and the request URL needs to carry the following parameters:

[0151]

[0152] In the above table, moNumber and mtNumber represent the calling and called numbers respectively;

[0153] The status represents the call state, wherein, ringing represents the ringing state; active-audio represents the voice call state; active-video represents the video call state; and holding represents the call waiting state.

[0154] The role represents the terminal role, that is, the calling MO or the called MT.

[0155] The call platform judges whether the terminal should push the multimedia display according to the values of moNumber and mtNumber, if the string is tokenkey, it indicates that the call platform knows the mobile number of the requesting mobile phone, and if the terminal uses the token to request, it indicates that the call platform does not know the mobile number of the requesting mobile phone. The URL format is as follows:

[0156] https: / / FQDN / ?monumber=13811060120&mtnumber=A1B2C3XXXXXXXXX&status=ringing&role=mo

[0157] Wherein, the domain name FQDN represents the full domain name of the call platform.

[0158] In addition, after the FQDN, a business routing flag can be added according to the business needs for different businesses, to facilitate the call platform to perform business distribution processing.

[0159] https: / / FQDN / APPLICATIONID / ?monumber=13811060120&mtnumber=A1B2C3XXXXXXXXX&status=ringing&role=mo

[0160] Wherein, the APPLICATION represents a domain name field allocated for a certain business, and the mtnumber is a tokenKey generated by the platform according to a mobile phone number.

[0161] The embodiment of the application can solve the predicament that the current operator business is heavily dependent on terminals, and it is particularly difficult to promote the upgrade and reconstruction of the terminal protocol stack, so that the business can be developed through the call platform without excessive dependence on the terminal, which is very beneficial to the business development.

[0162] The above introduces various methods of the embodiment of the application. The device for implementing the above method will be further provided below.

[0163] The embodiment of the application provides Figure 6 A call platform as shown in the figure, comprising:

[0164] A first receiving module 61 is configured to receive a first HTTP request sent by a first terminal, wherein the first HTTP request carries a second terminal identifier of a second terminal;

[0165] A first sending module 62 is configured to send a first program script to the first terminal in a case where the first terminal and the second terminal are in a call state, wherein the first program script comprises script code for assisting the terminal to initiate an authentication request to an authentication platform;

[0166] A second receiving module 63 is configured to receive a second HTTP request sent by the first terminal, wherein the second HTTP request carries a token of the first terminal;

[0167] A second sending module 64 is configured to authenticate the token of the first terminal by using the authentication platform, and send first multimedia information to the first terminal in a case where the authentication is successful.

[0168] Optionally, the second HTTP request also carries the second terminal identifier, and the call platform further comprises:

[0169] a first obtaining module, configured to, before sending the first multimedia information to the first terminal, obtain the first multimedia information required to be sent to the first terminal according to at least one of a call state, a call role and a registered multimedia call service of the first terminal and the second terminal, wherein

[0170] the call state comprises a ringing state, a voice call state, a video call state and a call waiting state, and the call role comprises a calling and a called; and the first multimedia information is a web page file or a web page address corresponding to the web page file.

[0171] Optionally, the first obtaining module is further configured to request a service server for multimedia information of the second terminal required to be displayed in a current call state, and receive the first multimedia information returned by the service server.

[0172] Optionally, the second sending module is further configured to send the token of the first terminal to an authentication platform, and receive an authentication result of the token of the first terminal returned by the authentication platform, wherein when the token of the first terminal is the same as a token allocated to the first terminal by the authentication platform, the authentication result is authentication passed, otherwise, the authentication result is authentication failed.

[0173] Optionally, the first program script further comprises script code for assisting the terminal to initiate a service request to the communication platform; and the second HTTP request is an HTTP request for requesting multimedia information corresponding to the first service sent by the first terminal by using the first program script.

[0174] Optionally, the call platform further comprises:

[0175] a generating module, configured to, after receiving the second HTTP request, generate a first token key for identifying the first terminal according to the first terminal identifier of the first terminal, a domain name of the communication platform and the token of the first terminal; and send the first token key to the first terminal.

[0176] Optionally, the first program script further comprises script code for assisting the terminal to initiate a websocket connection to the communication platform; and the call platform further comprises:

[0177] The first connection establishment module is configured to receive a third HTTP request for establishing an end-to-end websocket connection sent by the first terminal after sending the first multimedia information to the first terminal, the third HTTP request carrying a token key of the first terminal and a second terminal identifier; authenticate the token key of the first terminal, and after authentication, establish a first websocket connection with the first terminal in response to the third HTTP request.

[0178] Optionally, the call platform further comprises:

[0179] The first service processing module is configured to receive a first service request message sent by the first terminal through the first websocket connection, the first service request message carrying a token key of the first terminal; authenticate the token key of the first terminal, and after authentication, send multimedia information corresponding to the first service request message to the first terminal through the first websocket connection.

[0180] Optionally, the call platform further comprises:

[0181] The second connection establishment module is configured to receive a fourth HTTP request for establishing an end-to-end websocket connection sent by the second terminal, the fourth HTTP request carrying a token key of the second terminal and a first terminal identifier of the first terminal; authenticate the token key of the second terminal, and after authentication, establish a second websocket connection with the second terminal in response to the fourth HTTP request;

[0182] The first service update module is configured to receive a multimedia information update notification message sent by the second terminal through the second websocket connection, and forward the multimedia information update notification message to the first terminal through the first websocket connection; receive a second service request message for requesting to update multimedia information of the second terminal sent by the first terminal, the second service request message carrying a token key of the first terminal; authenticate the token key of the first terminal, and after authentication, request the updated multimedia information of the second terminal from a service server; receive the updated multimedia information of the second terminal sent by the service server, and forward the updated multimedia information of the second terminal to the first terminal through the first websocket connection.

[0183] Optionally, the first program script further comprises script code for assisting the terminal to initiate a websocket connection with the communication platform; the second HTTP request is an HTTP request for initiating the websocket connection sent by the first terminal using the first program script; the second sending module is further configured to, in response to the second HTTP request, establish a first websocket connection with the first terminal if the authentication is successful; and send first multimedia information to the first terminal through the first websocket connection.

[0184] Optionally, the communication platform further comprises:

[0185] The second service processing module is configured to receive a third service request message sent by the first terminal through the first websocket connection, the third service request message carrying a token of the first terminal; authenticate the token of the first terminal, and send multimedia information corresponding to the third service request message to the first terminal through the first websocket connection if the authentication is successful.

[0186] Optionally, the communication platform further comprises:

[0187] The third connection establishing module is configured to receive a fifth HTTP request for initiating a websocket connection sent by a second terminal, the fifth HTTP request carrying a token of the second terminal; authenticate the token of the second terminal using the authentication platform, and establish a second websocket connection with the second terminal in response to the fifth HTTP request if the authentication is successful.

[0188] The second service updating module is configured to receive a multimedia information updating notification message sent by the second terminal through the second websocket connection, and forward the multimedia information updating notification message to the first terminal through the first websocket connection; receive a fourth service request message sent by the first terminal for requesting to update the multimedia information of the second terminal, the fourth service request message carrying a token of the first terminal; authenticate the token of the first terminal, and request the service server for the updated multimedia information of the second terminal if the authentication is successful; receive the updated multimedia information of the second terminal sent by the service server, and forward the updated multimedia information to the first terminal through the first websocket connection.

[0189] Optionally, the URL of the service request message sent by the first terminal comprises at least one of the following parameters:

[0190] A calling number or a token key of the calling number.

[0191] a called number or a token key of the called number;

[0192] a call state;

[0193] an initiator of a service request message is a caller or a callee;

[0194] a service route flag corresponding to a requested service.

[0195] It should be noted that the device in this embodiment is the equipment corresponding to the method described above Figure 2 The implementation manners in the above embodiments are all applicable to the embodiments of the equipment, and the same technical effects can be achieved. It should be noted that the above equipment provided by the embodiments of the present application can implement all the method steps achieved by the method embodiments, and the same technical effects can be achieved. Here, the same parts and beneficial effects in the method embodiments will not be described in detail.

[0196] Please refer to Figure 7 The embodiment of the present application provides a structural diagram of a call platform, which comprises a processor 701, a transceiver 702, a memory 703 and a bus interface, wherein:

[0197] In the embodiment of the present application, the call platform further comprises a program stored on the memory 703 and executable on the processor 701, and the program implements the following steps when executed by the processor 701:

[0198] receiving a first HTTP request sent by a first terminal, wherein the first HTTP request carries a second terminal identifier of a second terminal;

[0199] In the case that the first terminal and the second terminal are in a call state, a first program script is sent to the first terminal, wherein the first program script comprises script code for assisting the terminal to initiate an authentication request to the authentication platform;

[0200] receiving a second HTTP request sent by the first terminal, wherein the second HTTP request carries a token of the first terminal;

[0201] authenticating the token of the first terminal by using the authentication platform, and in the case that the authentication is successful, sending first multimedia information to the first terminal.

[0202] It can be understood that the computer program is executed by the processor 701 to implement each process of the method embodiments shown in the above Figure 2 , and the same technical effects can be achieved. To avoid repetition, it will not be described here.

[0203] In Figure 7In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 701 and the memory 703 represented by various circuitry linking the processor 701 and the memory 703. The bus architecture can also include various other circuitry, which is conventionally known as a bus interface, peripheral devices, voltage regulators, and power management circuitry, all of which are conventionally known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 702 can be a plurality of elements, i.e., including a transmitter and a receiver, which provides a means for communicating with various other apparatus over a transmission medium.

[0204] The processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 can store data used by the processor 701 in executing operations.

[0205] It should be noted that the terminal in this embodiment is a device corresponding to the method shown in the above Figure 2 The implementation manners in the above embodiments are all applicable to the terminal embodiment, and the same technical effects can be achieved. In the device, the transceiver 702 and the memory 703, and the transceiver 702 and the processor 701 can be connected through the bus interface, the function of the processor 701 can also be implemented by the transceiver 702, and the function of the transceiver 702 can also be implemented by the processor 701. It should be noted that the above device provided by the embodiment of the application can implement all method steps implemented by the method embodiment and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiment will not be described in detail.

[0206] In some embodiments of the application, a computer readable storage medium is also provided, and the program is stored on the computer readable storage medium. When the program is executed by the processor, the following steps are implemented:

[0207] Receiving a first HTTP request sent by a first terminal, the first HTTP request carrying a second terminal identifier of a second terminal;

[0208] In a case where the first terminal and the second terminal are in a call state, sending a first program script to the first terminal, the first program script including script code for assisting the terminal to initiate an authentication request to an authentication platform;

[0209] Receiving a second HTTP request sent by the first terminal, the second HTTP request carrying a token of the first terminal;

[0210] Authenticating the token of the first terminal by using the authentication platform, and in a case where the authentication is successful, sending first multimedia information to the first terminal.

[0211] The program is executed by the processor to implement all the implementation manners of the application of the transmission method of the multimedia information applied to the call platform, and achieve the same technical effects. To avoid repetition, details are not described here.

[0212] Please refer to Figure 8 The first terminal provided by the embodiment of the application comprises:

[0213] The first sending module 81 is configured to send a first HTTP request to a communication platform when it is detected that the terminal enters a call state with a second terminal, and the first HTTP request carries a second terminal identifier of the second terminal.

[0214] The first receiving module 82 is configured to receive a first program script sent by the communication platform, and the first program script comprises script code for assisting the terminal to initiate an authentication request to an authentication platform.

[0215] The authentication module 83 is configured to initiate an authentication request to the authentication platform by using the first program script, and receive a first token allocated by the authentication platform to the terminal after the authentication is passed.

[0216] The second sending module 84 is configured to send a second HTTP request to the communication platform, and the second HTTP request carries the first token.

[0217] The second receiving module 85 is configured to receive first multimedia information sent by the communication platform and display the first multimedia information locally.

[0218] Optionally, the call state comprises a ringing state, a voice call state, a video call state and a call waiting state; and the first multimedia information is a web page file or a web page address corresponding to the web page file.

[0219] Optionally, the first program script further comprises script code for assisting the terminal to initiate a service request to the communication platform; and the second HTTP request is an HTTP request for requesting multimedia information corresponding to a first service, which is sent by the terminal by using the first program script.

[0220] Optionally, the first terminal further comprises:

[0221] The third receiving module is configured to receive a first token key (i.e., tokenKey) for identifying the terminal returned by the communication platform after the second HTTP request is sent.

[0222] Optionally, the first program script further comprises script code for assisting the terminal to initiate a websocket connection to the communication platform; and the first terminal further comprises:

[0223] The first connection establishment module is configured to send, by using the first program script, a third HTTP request for establishing an end-to-end websocket connection, the third HTTP request carrying the first token key and the second terminal identifier; and receive a response message sent by the communication platform after passing authentication of the first token key, to establish a first websocket connection with the communication platform.

[0224] Optionally, the first terminal further comprises:

[0225] The first service processing module is configured to send, by using the first websocket connection, a first service request message to the communication platform, the first service request message carrying the first token key; and receive, by using the first websocket connection, multimedia information corresponding to the first service request message returned by the communication platform and display the multimedia information.

[0226] Optionally, the first terminal further comprises:

[0227] The first service updating module is configured to receive, by using the first websocket connection, a multimedia information updating notification message of the second terminal sent by the communication platform; send, by using the first websocket connection, a second service request message for requesting to update the multimedia information of the second terminal to the communication platform, the second service request message carrying the token key of the first terminal; and receive, by using the first websocket connection, updated multimedia information of the second terminal sent by the communication platform.

[0228] Optionally, the first program script further comprises script code for initiating a websocket connection by a secondary terminal to a communication platform; the second HTTP request is an HTTP request for initiating a websocket connection sent by the first terminal by using the first program script; the second receiving module 85 is further configured to receive a response message sent by the communication platform after passing authentication of the first token, to establish a first websocket connection with the communication platform; and receive, by using the first websocket connection, first multimedia information sent by the communication platform and display the first multimedia information.

[0229] Optionally, the first terminal further comprises:

[0230] The second service processing module is configured to send, by using the first websocket connection, a third service request message to the communication platform, the third service request message carrying the first token; and receive, by using the first websocket connection, multimedia information corresponding to the third service request message returned by the communication platform and display the multimedia information.

[0231] Optionally, the first terminal further comprises:

[0232] a second service updating module, configured to receive, through the first websocket connection, a multimedia information updating notification message of the second terminal sent by the communication platform; send, through the first websocket connection, a fourth service request message for requesting to update the multimedia information of the second terminal to the communication platform, the fourth service request message carrying the first token; and receive, through the first websocket connection, the updated multimedia information of the second terminal sent by the communication platform.

[0233] Optionally, the URL of the service request message sent by the first terminal comprises at least one of the following parameters:

[0234] a calling number or a token key of the calling number;

[0235] a called number or a token key of the called number;

[0236] a call state;

[0237] a caller or a callee of the initiator of the service request message;

[0238] a service route flag corresponding to the requested service.

[0239] It should be noted that the device in this embodiment is a device corresponding to the method shown in the above Figure 3 The implementation manners in the above embodiments are all applicable to the embodiment of the device, and the same technical effects can also be achieved. The device provided in the embodiment of the application can realize all the method steps achieved by the method embodiments, and achieve the same technical effects. Here, the same parts and beneficial effects in the method embodiments will not be described in detail.

[0240] Please refer to Figure 9 The first terminal provided in the embodiment of the application has a structure diagram, and the terminal comprises a processor 901, a transceiver 902, a memory 903, a user interface 904 and a bus interface.

[0241] In the embodiment of the application, the terminal further comprises a program stored on the memory 903 and executable on the processor 901.

[0242] The processor 901 implements the following steps when executing the program:

[0243] In the case of detecting that the terminal enters a call state with the second terminal, a first HTTP request is sent to the communication platform, and the first HTTP request carries a second terminal identifier of the second terminal.

[0244] receive a first program script sent by the communication platform, the first program script comprising script code for assisting the terminal to initiate an authentication request to the authentication platform;

[0245] initiate an authentication request to the authentication platform by using the first program script, and receive a first token allocated by the authentication platform to the first terminal after the authentication request is passed;

[0246] send a second HTTP request to the communication platform, the second HTTP request carrying the first token;

[0247] receive first multimedia information sent by the communication platform and display the first multimedia information locally.

[0248] It can be understood that, in the embodiment of the application, the computer program is executed by the processor 901 to implement the above-mentioned Figure 3 processes of the method embodiment shown in the figure, and the same technical effects can be achieved. To avoid repetition, no further description is given here.

[0249] In Figure 9 the bus architecture can include any number of interconnecting buses and bridges, and the various circuitry representative of the processor(s) 901 and the memory 903 that are linked together by the bus architecture, and that can be vulnerable to malicious attacks. The bus architecture can also link various other circuitry, which is well known, such as, for example, peripheral devices, volatile memory, non-volatile memory, power management circuitry, and the like, and therefore, no further details of the bus architecture will be given herein. The bus interface provides an interface between the bus architecture and the transceiver 902. The transceiver 902 can be a plurality of elements, including a transmitter and a receiver, that together enable the bus architecture to communicate with various other apparatus over a transmission medium. The user interface 904 can also be an interface that enables the apparatus to be connected to external devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0250] The processor 901 is responsible for managing the bus architecture and general processing, and the memory 903 can store data used by the processor 901 in performing operations.

[0251] It should be noted that the device in this embodiment is the same as the above Figure 3The method shown corresponds to the device, and the implementation manners in the above embodiments are applicable to the embodiments of the device, and the same technical effects can be achieved. In the device, the transceiver 902 and the memory 903, and the transceiver 902 and the processor 901 can be connected through a bus interface, the function of the processor 901 can also be realized by the transceiver 902, and the function of the transceiver 902 can also be realized by the processor 901. It should be noted that the above device provided by the embodiments of the present application can realize all the method steps realized by the above method embodiments, and can achieve the same technical effects, and the same parts and beneficial effects in the method embodiments will not be described in detail.

[0252] In some embodiments of the present application, a computer readable storage medium is also provided, which stores a program, and the program is executed by a processor to implement the following steps:

[0253] In the case of detecting that the terminal enters a call state with the second terminal, a first HTTP request is sent to the communication platform, and the first HTTP request carries a second terminal identifier of the second terminal;

[0254] The first program script sent by the communication platform is received, and the first program script includes script code for assisting the terminal to initiate an authentication request to the authentication platform;

[0255] An authentication request is initiated to the authentication platform by using the first program script, and a first token allocated by the authentication platform to the first terminal after the authentication is passed is received;

[0256] A second HTTP request is sent to the communication platform, and the second HTTP request carries the first token;

[0257] The first multimedia information sent by the communication platform is received and displayed locally.

[0258] The program is executed by the processor to implement all the implementation manners of the above-mentioned application of the terminal-side multimedia information transmission method, and the same technical effects can be achieved. To avoid repetition, this will not be described here.

[0259] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0260] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0261] In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other manners. For example, the apparatus embodiments described above are only schematic, for example, the division of the units is only a logical function division, and another division manner can be used in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0262] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment of the present application.

[0263] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0264] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the present application that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk, and various storage medium that can store program codes.

[0265] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for transmitting multimedia information, applied to a communication platform, characterized in that, include: Receive a first HTTP request sent by a first terminal, wherein the first HTTP request carries the second terminal identifier of the second terminal; When the first terminal and the second terminal are in a call, a first program script is sent to the first terminal. The first program script includes script code that assists the terminal in initiating an authentication request to the authentication platform. Receive a second HTTP request sent by the first terminal, the second HTTP request carrying the token of the first terminal; The authentication platform is used to authenticate the token of the first terminal. If the authentication is successful, the first multimedia information is sent to the first terminal. The second HTTP request also carries the second terminal identifier. Before sending the first multimedia information to the first terminal, the method further includes: Based on at least one of the call status of the first terminal and the second terminal, the call role, and the registered multimedia call services, the first multimedia information to be sent to the first terminal is obtained, wherein... The call status includes ringing, voice call in progress, video call in progress, and call waiting status; the call roles include caller and called party; the first multimedia information is a web page file or the web page address corresponding to the web page file.

2. The method as described in claim 1, characterized in that, The step of obtaining the first multimedia information to be sent to the first terminal includes: The system requests multimedia information of the second terminal that needs to be displayed in the current call state from the service server, and receives the first multimedia information returned by the service server.

3. The method as described in claim 1, characterized in that, The authentication of the token of the first terminal using the authentication platform includes: The first terminal sends its token to the authentication platform and receives the authentication result of the first terminal's token returned by the authentication platform. If the first terminal's token is the same as the token assigned to the first terminal by the authentication platform, the authentication result is successful; otherwise, the authentication result is unsuccessful.

4. The method as described in claim 1, characterized in that, The first program script also includes script code for the auxiliary terminal to initiate a service request to the communication platform; the second HTTP request is an HTTP request sent by the first terminal using the first program script to request multimedia information corresponding to the first service.

5. The method as described in claim 4, characterized in that, After receiving the second HTTP request, the method further includes: A token key for identifying the first terminal is generated based on the first terminal identifier of the first terminal, the domain name of the communication platform, and the token of the first terminal. Send the token key of the first terminal to the first terminal.

6. The method as described in claim 5, characterized in that, The first program script also includes script code for the auxiliary terminal to initiate a WebSocket connection to the communication platform; after sending the first multimedia information to the first terminal, the method further includes: The system receives a third HTTP request from the first terminal to establish an end-to-end WebSocket connection. The third HTTP request carries the token key of the first terminal and the identifier of the second terminal. The system authenticates the token key of the first terminal and, upon successful authentication, responds to the third HTTP request to establish a first WebSocket connection with the first terminal.

7. The method as described in claim 6, characterized in that, Also includes: The system receives a first service request message sent by the first terminal through the first websocket connection. The first service request message carries the token key of the first terminal. The token key of the first terminal is authenticated, and after successful authentication, the multimedia information corresponding to the first service request message is sent to the first terminal through the first websocket connection.

8. The method as described in claim 6, characterized in that, Also includes: Receive a fourth HTTP request for an end-to-end WebSocket connection sent by the second terminal, the fourth HTTP request carrying the token key of the second terminal and the first terminal identifier of the first terminal; The token key of the second terminal is authenticated, and after successful authentication, the fourth HTTP request is responded to to establish a second WebSocket connection with the second terminal; The system receives multimedia information update notification messages sent by the second terminal through the second websocket connection, and forwards the multimedia information update notification messages to the first terminal through the first websocket connection. The system receives a second service request message sent by the first terminal requesting to update the multimedia information of the second terminal, the second service request message carrying the token key of the first terminal; The token key of the first terminal is authenticated, and after successful authentication, the updated multimedia information of the second terminal is requested from the business server. The system receives the updated multimedia information from the second terminal sent by the service server and forwards it to the first terminal via the first websocket connection.

9. The method as described in claim 3, characterized in that, The first program script also includes script code for the auxiliary terminal to initiate a WebSocket connection to the communication platform; the second HTTP request is an HTTP request sent by the first terminal using the first program script to initiate a WebSocket connection, and sending the first multimedia information to the first terminal includes: If authentication is successful, in response to the second HTTP request, a first WebSocket connection is established with the first terminal; The first multimedia information is sent to the first terminal through the first WebSocket connection.

10. The method as described in claim 9, characterized in that, Also includes: The system receives a third service request message sent by the first terminal through the first websocket connection. The third service request message carries the token of the first terminal. The token of the first terminal is authenticated, and after successful authentication, the multimedia information corresponding to the third service request message is sent to the first terminal through the first websocket connection.

11. The method as described in claim 9, characterized in that, Also includes: Receive a fifth HTTP request sent by the second terminal to initiate a WebSocket connection, the fifth HTTP request carrying a token from the second terminal; The authentication platform is used to authenticate the token of the second terminal. If the authentication is successful, a second websocket connection is established with the second terminal in response to the fifth HTTP request. The system receives multimedia information update notification messages sent by the second terminal through the second websocket connection, and forwards the multimedia information update notification messages to the first terminal through the first websocket connection. The system receives a fourth service request message sent by the first terminal requesting an update of the multimedia information of the second terminal, the fourth service request message carrying a token of the first terminal. The token of the first terminal is authenticated, and after successful authentication, the updated multimedia information of the second terminal is requested from the business server. The system receives the updated multimedia information from the second terminal sent by the service server and forwards it to the first terminal via the first websocket connection.

12. The method as described in claim 7 or 8, characterized in that, The URL of the service request message sent by the first terminal includes at least one of the following parameters: The calling number or the token key of the calling number; The called number or the token key of the called number; Call status; The initiator of the service request message is either the caller or the called party; The service routing flag corresponding to the requested service.

13. A method for transmitting multimedia information, applied to a first terminal, characterized in that, include: When the first terminal detects that it has entered a call state with the second terminal, it sends a first HTTP request to the communication platform. The first HTTP request carries the second terminal identifier of the second terminal. The first terminal receives a first program script sent by the communication platform, the first program script including script code for the auxiliary terminal to initiate an authentication request to the authentication platform; The first terminal uses the first program script to initiate an authentication request to the authentication platform and receives the first token assigned to the first terminal by the authentication platform after successful authentication. The first terminal sends a second HTTP request to the communication platform, the second HTTP request carrying the first token; The first terminal receives the first multimedia information sent by the communication platform and displays it locally. The call status includes ringing, voice call in progress, video call in progress, and call waiting status; the first multimedia information is a web page file or the web page address corresponding to the web page file.

14. The method as described in claim 13, characterized in that, The first program script also includes script code for the auxiliary terminal to initiate a service request to the communication platform; the second HTTP request is an HTTP request sent by the first terminal using the first program script to request multimedia information corresponding to the first service.

15. The method as described in claim 14, characterized in that, After sending the second HTTP request, the method further includes: Receive the token key returned by the communication platform to identify the first terminal.

16. The method as described in claim 15, characterized in that, The first program script also includes script code for an auxiliary terminal to initiate a WebSocket connection to the communication platform; the method further includes: The first terminal uses the first program script to send a third HTTP request to establish an end-to-end WebSocket connection. The third HTTP request carries the token key of the first terminal and the identifier of the second terminal. The system receives a response message from the communication platform after successfully authenticating the token key of the first terminal, and establishes a first WebSocket connection with the communication platform.

17. The method as described in claim 16, characterized in that, Also includes: A first service request message is sent to the communication platform through the first websocket connection. The first service request message carries the token key of the first terminal. The system receives and displays multimedia information corresponding to the first service request message returned by the communication platform through the first WebSocket connection.

18. The method as described in claim 16, characterized in that, Also includes: The second terminal receives a multimedia information update notification message sent by the communication platform through the first WebSocket connection. Through the first WebSocket connection, a second service request message is sent to the communication platform to request the update of the multimedia information of the second terminal. The second service request message carries the token key of the first terminal. The second terminal receives updated multimedia information sent by the communication platform through the first WebSocket connection.

19. The method as described in claim 13, characterized in that, The first program script also includes script code for the auxiliary terminal to initiate a WebSocket connection to the communication platform; the second HTTP request is an HTTP request sent by the first terminal using the first program script to initiate a WebSocket connection. The first terminal receives first multimedia information sent by the communication platform, including: Receive the response message sent by the communication platform after the first token has been successfully authenticated, and establish a first websocket connection with the communication platform; as well as, The system receives and displays the first multimedia information sent by the communication platform through the first WebSocket connection.

20. The method as described in claim 19, characterized in that, Also includes: A third service request message is sent to the communication platform through the first WebSocket connection, and the third service request message carries the first token. The system receives and displays multimedia information corresponding to the third service request message returned by the communication platform through the first WebSocket connection.

21. The method as described in claim 19, characterized in that, Also includes: The second terminal receives a multimedia information update notification message sent by the communication platform through the first WebSocket connection. A fourth service request message, carrying the first token, is sent to the communication platform via the first WebSocket connection to request an update of the multimedia information of the second terminal. The second terminal receives updated multimedia information sent by the communication platform through the first WebSocket connection.

22. The method as described in claim 17 or 18, characterized in that, The URL of the service request message sent by the first terminal includes at least one of the following parameters: The calling number or the token key of the calling number; The called number or the token key of the called number; Call status; The initiator of the service request message is either the caller or the called party; The service routing flag corresponding to the requested service.

23. A communication platform, characterized in that, Includes transceivers and processors, among which, The transceiver is configured to receive a first HTTP request sent by a first terminal, the first HTTP request carrying a second terminal identifier of a second terminal; when the first terminal and the second terminal are in a call state, send a first program script to the first terminal, the first program script including script code for an auxiliary terminal to initiate an authentication request to an authentication platform; and receive a second HTTP request sent by the first terminal, the second HTTP request carrying a token of the first terminal. The processor is used to authenticate the token of the first terminal using the authentication platform, and if the authentication is successful, to send the first multimedia information to the first terminal. The second HTTP request also carries the second terminal identifier. Before sending the first multimedia information to the first terminal, the processor is further configured to: Based on at least one of the call status of the first terminal and the second terminal, the call role, and the registered multimedia call services, the first multimedia information to be sent to the first terminal is obtained, wherein... The call status includes ringing, voice call in progress, video call in progress, and call waiting status; the call roles include caller and called party; the first multimedia information is a web page file or the web page address corresponding to the web page file.

24. A communication platform, characterized in that, It includes a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 12.

25. A first terminal, characterized in that, Includes transceivers and processors, among which, The transceiver is configured to send a first HTTP request to a communication platform when it detects that the terminal has entered a call state with a second terminal, the first HTTP request carrying the second terminal identifier of the second terminal; and receive a first program script sent by the communication platform, the first program script including script code for an auxiliary terminal to initiate an authentication request to an authentication platform; The processor is configured to: initiate an authentication request to the authentication platform using the first program script; receive a first token assigned to the first terminal by the authentication platform after successful authentication; send a second HTTP request to the communication platform, the second HTTP request carrying the first token; and receive first multimedia information sent by the communication platform and display it locally. The call status includes ringing, voice call in progress, video call in progress, and call waiting status; the first multimedia information is a web page file or the web page address corresponding to the web page file.

26. A first terminal, characterized in that, It includes a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, performs the steps of the method as described in any one of claims 13 to 22.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 22.

Citation Information

Patent Citations

  • IMS network access method, system, and correlative device

    CN104113511A