Web real-time communication call transferring method and apparatus

1. A web real-time communication (WebRTC) call transferring apparatus comprising:

at least one memory comprising instructions; and

at least one hardware processor coupled to the at least one memory, wherein the instructions cause the at least one hardware processor to be configured to:

receive a first request message used for requesting page information corresponding to a to-be-transferred call and received from a destination terminal according to a first identifier, wherein the first identifier is used for identifying the to-be-transferred call, and wherein the to-be-transferred call is a WebRTC call having been established between a source terminal and a remote terminal;

receive authentication information of a first token from the destination terminal, wherein the first token is a token allocated by a browser server for the destination terminal and used for identifying the destination terminal;

send, according to the first request message, the page information corresponding to the to-be-transferred call to the destination terminal;

receive from the destination terminal a call request message used for calling the remote terminal, wherein the call request message comprises a first session identifier corresponding to the destination terminal;

change the first session identifier in the call request message into a second session identifier corresponding to the source terminal to generate a changed call request message;

send the changed call request message to the remote terminal;

receive a response message from the remote terminal according to the changed call request message, wherein the response message comprises the second session identifier;

change the second session identifier in the response message into the first session identifier to generate a changed response message;

send the changed response message to the destination terminal so that the destination terminal establishes a call connection with the remote terminal; and

send the source terminal a release indication message used for instructing the source terminal to release the to-be-transferred call after the destination terminal establishes the call connection with the remote terminal.

2. The apparatus according to claim 1 , wherein the instructions further cause the at least one hardware processor to be configured to:

perform, according to a second token sent by the source terminal, authentication on the authentication information of the first token used for identifying the destination terminal; and

send the page information corresponding to the to-be-transferred call to the destination terminal when it is determined through the authentication on the authentication information of the first token that the first token is the same as the second token.

3. The apparatus according to claim 1 , wherein the instructions further cause the at least one hardware processor to be configured to:

receive a generation request for generating the first identifier, which is received from the source terminal, before receiving the first request message used for requesting the page information corresponding to the to-be-transferred call and received from the destination terminal according to the first identifier; and

send the first identifier generated according to the generation request to the source terminal.

4. The apparatus according to claim 1 , wherein a browser account logged into the source terminal is the same as a browser account logged into the destination terminal.

5. The apparatus according to claim 1 , wherein a browser account logged into the source terminal is different from a browser account logged into the destination terminal, and wherein the browser server determines that a binding relationship exists between the source terminal and the destination terminal.

6. The apparatus according to claim 1 , wherein the page information comprises at least one of a uniform resource locator (URL), user identifiers of two parties of the to-be-transferred call, a hypertext markup language (HTML) file, a JAVASCRIPT file, or a picture.

7. The apparatus according to claim 1 , wherein the instructions further cause the at least one hardware processor to be configured to receive a second token from the source terminal before sending the page information corresponding to the to-be-transferred call to the destination terminal, wherein the first token is allocated by a browser server for the destination terminal and used for identifying the destination terminal.

8. The apparatus according to claim 7 , wherein the instructions further cause the at least one hardware processor to be configured to:

compare the first token and the second token; and

send, according to the first request message, the page information corresponding to the to-be-transferred call to the destination terminal when the first token and the second token are the same, wherein the destination terminal establishes, according to identification information of the remote terminal in the page information, a call connection used for bearing the to-be-transferred call with the remote terminal so as to implement transferring of the to-be-transferred call from between the source terminal and the remote terminal to between the destination terminal and the remote terminal.

9. The apparatus according to claim 8 , wherein the browser server generates the first token and the second token.

10. A web real-time communication (WebRTC) call transferring method comprising:

receiving a first request message used for requesting page information corresponding to a to-be-transferred call and received from a destination terminal according to a first identifier, wherein the first identifier is used for identifying the to-be-transferred call, and wherein the to-be-transferred call is a WebRTC call having been established between a source terminal and a remote terminal;

receiving authentication information of a first token from the destination terminal, wherein the first token is a token allocated by a browser server for the destination terminal and used for identifying the destination terminal;

sending, according to the first request message, the page information corresponding to the to-be-transferred call to the destination terminal;

receiving from the destination terminal a call request message used for calling the remote terminal, wherein the call request message comprises a first session identifier corresponding to the destination terminal;

changing the first session identifier in the call request message into a second session identifier corresponding to the source terminal to generate a changed call request message;

sending the changed call request message to the remote terminal;

receiving a response message from the remote terminal according to the changed call request message, wherein the response message comprises the second session identifier;

changing the second session identifier in the response message into the first session identifier to generate a changed response message;

sending the changed response message to the destination terminal so that the destination terminal establishes a call connection with the remote terminal; and

sending the source terminal a release indication message used for instructing the source terminal to release the to-be-transferred call after the destination terminal establishes the call connection with the remote terminal.

11. The method according to claim 10 , further comprising:

performing, according to a second token sent by the source terminal, authentication on the authentication information of the first token used for identifying the destination terminal; and

sending the page information corresponding to the to-be-transferred call to the destination terminal when it is determined through the authentication on the authentication information of the first token that the first token is the same as the second token.

12. The method according to claim 10 , further comprising:

receiving a generation request for generating the first identifier, which is received from the source terminal, before receiving the first request message used for requesting the page information corresponding to the to-be-transferred call and received from the destination terminal according to the first identifier; and

sending the first identifier generated according to the generation request to the source terminal.

13. The method according to claim 10 , wherein a browser account logged into the source terminal is the same as a browser account logged into the destination terminal.

14. The method according to claim 10 , wherein a browser account logged into the source terminal is different from a browser account logged into the destination terminal, and wherein the browser server determines that a binding relationship exists between the source terminal and the destination terminal.

15. The method according to claim 10 , wherein the page information comprises at least one of a uniform resource locator (URL), user identifiers of two parties of the to-be-transferred call, a hypertext markup language (HTML) file, a JAVASCRIPT file, or a picture.

16. The method according to claim 10 , further comprising receiving a second token from the source terminal before sending the page information corresponding to the to-be-transferred call to the destination terminal, wherein the first token is allocated by a browser server for the destination terminal and used for identifying the destination terminal.

17. The method according to claim 16 , further comprising:

comparing the first token and the second token; and

sending, according to the first request message, the page information corresponding to the to-be-transferred call to the destination terminal when the first token and the second token are the same, wherein the destination terminal establishes, according to identification information of the remote terminal in the page information, a call connection used for bearing the to-be-transferred call with the remote terminal so as to implement transferring of the to-be-transferred call from between the source terminal and the remote terminal to between the destination terminal and the remote terminal.

18. The method according to claim 17 , wherein the browser server generates the first token and the second token.