CN105379194B

CN105379194B - Method and device for processing call message

Info

Publication number: CN105379194B
Application number: CN201480000620.3A
Authority: CN
Inventors: 吴问付
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2014-04-28
Filing date: 2014-04-28
Publication date: 2020-02-14
Anticipated expiration: 2034-04-28
Also published as: CN105379194A; WO2015164997A1

Abstract

The invention provides a method for processing a call message, which is characterized in that when a first session request of a calling client is processed, a called client logs in a WebRTC server for webpage real-time communication by sending login indication information to the called client requested by the first session request so as to establish a session between the calling client and the called client. Namely, when the WebRTC client initiated with the session request is in a non-login state, the embodiment of the invention can enable the WebRTC client initiated with the session request to establish a session with the WebRTC client.

Description

Method and device for processing call message

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for processing a call message.

Background

When a plurality of WebRTC clients log in to the same WebRTC Server (Web Real-time Communication Server) through a Web page of the WebServer and keep a login state, the WebRTC Server can establish a video/voice session between the WebRTC client and other WebRTC clients according to a session request initiated by any WebRTC client to other WebRTC clients in the login state.

Therefore, in the prior art, the WebRTC client can only initiate a session request to other WebRTC clients in a login state through the WebRTC Server, and when the WebRTC client initiating the session request is in a non-login state, the WebRTC Server cannot find the WebRTC client initiating the session request, and thus cannot establish a session between the WebRTC client initiating the session request and the WebRTC client initiating the session request, and the WebRTC client initiating the session request cannot establish a session with the WebRTC client through the WebRTC Server.

Disclosure of Invention

In order to obviate or mitigate at least one of the above technical drawbacks, a method for processing a call message according to a first aspect of the embodiments of the present application includes:

receiving a first session request of a calling client, wherein the first session request carries a called client identifier;

acquiring the called client identification;

and sending login indication information to the called client corresponding to the called client identification, wherein the login indication information is used for indicating the called client to log in a webpage real-time communication WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

With reference to the first aspect, in a first possible implementation manner, the sending login indication information to a called client corresponding to the called client identifier includes:

acquiring the called client Internet Protocol (IP) address corresponding to the called client identification;

generating the login indication information;

and sending the login indication information to a called client corresponding to the IP address of the called client.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the obtaining the internet protocol IP address of the called client corresponding to the called client identifier includes:

sending an address searching message carrying the called client identification to an address conversion network element;

and receiving the IP address of the called client fed back by the address conversion network element.

With reference to the first aspect, in a third possible implementation manner, after obtaining the identifier of the called client, before sending login indication information to the called client corresponding to the identifier of the called client, the method further includes:

sending a WebRTC capability query message to the called client corresponding to the called client identification;

receiving WebRTC capability response information sent by the called client, wherein the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

sending the WebRTC capability query message to the called client corresponding to the called client identification;

and when the WebRTC capability response information sent by the called client is not received within the specified time, the login indication information is not sent to the called client corresponding to the called client identification.

With reference to the first aspect, in a fourth possible implementation manner, after obtaining the identifier of the called client, before sending login indication information to the called client corresponding to the identifier of the called client, the method further includes:

sending a WebRTC capability query instruction of a called client to a capability query network element, wherein the WebRTC capability query instruction of the called client carries an identifier of the called client;

receiving WebRTC capability confirmation information sent by the capability query network element, wherein the WebRTC capability confirmation information is generated after the capability query network element executes a WebRTC capability query instruction of the called client to query that the called client has the WebRTC capability;

alternatively, the first and second electrodes may be,

sending the WebRTC capability query instruction of the called client to the capability query network element;

and when the WebRTC capability confirmation information sent by the capability query network element is not received within the specified time, the login indication information is not sent to the called client corresponding to the called client identification.

With reference to the first aspect, in a fifth possible implementation manner, the sending login indication information to the called client corresponding to the called client identifier includes:

sending a push request to a push server, wherein the push request comprises the login indication information, and the push request is used for enabling the push server to push the login indication information to the called client corresponding to the called client identification.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, or the fourth possible implementation manner of the first aspect, or the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, the login indication information further includes one or two of login manner information and Uniform Resource Locator (URL) information of the WebRTC server, where the login manner information is used to indicate that the called client logs in to the WebRTC server according to the login manner information, and the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information.

With reference to any one of the first aspect to the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, after sending login indication information to the called client corresponding to the called client identifier, the method further includes:

when the called client is detected to log in the WebRTC server, a second session request is sent to the called client;

and after receiving a session response of the called client for responding to the second session request, forwarding the session response to the calling client, and establishing a session between the called client and the calling client.

In a second aspect, an embodiment of the present invention provides a method for processing a call message, including:

receiving login indication information sent by call message processing equipment, wherein the call message processing equipment comprises any one of a web real-time communication (WebRTC) server and an interworking gateway;

and logging in the WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

With reference to the second aspect, in a first possible implementation manner, before receiving the login indication information, the method further includes:

receiving a WebRTC capability query message sent by the call message processing equipment;

confirming whether the called client has the WebRTC capability;

if the called client is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the call message processing equipment; alternatively, the first and second electrodes may be,

and if the called client is confirmed not to have the WebRTC capability, not sending the WebRTC capability response information to the call message processing equipment.

With reference to the second aspect, in a second possible implementation manner, before receiving the login indication information, the method further includes:

receiving a WebRTC capability query message sent by a login capability query network element;

confirming whether the called client has the WebRTC capability;

if the called client is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the login capability query network element, so that the login capability query network element sends WebRTC capability confirmation information to the call message processing equipment according to the WebRTC capability response information; alternatively, the first and second electrodes may be,

and if the called client is confirmed not to have the WebRTC capability, not sending the WebRTC capability response information to the login capability query network element.

With reference to the second aspect, in a third possible implementation manner, the login indication information further includes login manner information, and logging in to the WebRTC server according to the login indication information includes:

acquiring the login mode information contained in the login indication information;

and logging in the WebRTC server according to the login mode information.

With reference to the second aspect, in a fourth possible implementation manner, the login indication information further includes uniform resource locator URL information of the WebRTC server, and logging in the WebRTC server for web page real-time communication according to the login indication information includes:

acquiring the URL information contained in the login indication information;

logging in the WebRTC server corresponding to the URL information.

With reference to the second aspect to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner, after logging in to the WebRTC server according to the login indication information, the method further includes:

receiving a session request sent by the WebRTC server, wherein the session request is used for a calling client to request to establish a session with a called client;

and sending a session response to the WebRTC server according to the session request, so that the WebRTC server forwards the session response to the calling client and establishes a session between the called client and the calling client.

In a third aspect, an embodiment of the present invention provides a call message processing apparatus, including:

the receiving module is used for receiving a first session request of a calling client, wherein the first session request carries a called client identifier;

the acquisition module is used for acquiring the called client identification;

and the sending module is used for sending login indication information to the called client corresponding to the called client identification, wherein the login indication information is used for indicating the called client to log in a webpage real-time communication WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

With reference to the third aspect, in a first possible implementation manner, the sending module includes:

the obtaining submodule is used for obtaining the called client Internet Protocol (IP) address corresponding to the called client identification;

the generation submodule is used for generating the login indication information;

and the sending submodule is used for sending the login indication information to the called client corresponding to the IP address of the called client.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner, the obtaining sub-module includes:

a sending unit, configured to send an address lookup message carrying the called client identifier to an address translation network element;

and the receiving unit is used for receiving the IP address of the called client fed back by the address conversion network element.

With reference to the third aspect, in a third possible implementation manner,

the sending module is further configured to send a WebRTC capability query message to the called client corresponding to the called client identifier;

the receiving module is further configured to receive WebRTC capability response information sent by the called client, where the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

the sending module is further configured to send the WebRTC capability query message to the called client corresponding to the called client identifier;

the receiving module is further configured to generate a first termination prompt message and send the first termination prompt message to the sending module when the WebRTC capability response message sent by the called client is not received within a specified time;

the sending module is further configured to not send the login indication sending information to the called client corresponding to the called client identifier after the first termination prompt message sent by the receiving module is sent.

With reference to the third aspect, in a third possible implementation manner, in a fourth possible implementation manner,

the sending module is further configured to send a WebRTC capability query instruction of the called client to a capability query network element, where the WebRTC capability query instruction of the called client carries the identifier of the called client;

the receiving module is further configured to receive WebRTC capability confirmation information sent by the capability query network element, where the WebRTC capability confirmation information is generated by the capability query network element after executing a WebRTC capability query instruction of the called client to query that the called client has the WebRTC capability;

alternatively, the first and second electrodes may be,

the sending module is further configured to send a WebRTC capability query instruction of the called client to the capability query network element;

the receiving module is further configured to generate a second termination prompt message and send the second termination prompt message to the sending module when the WebRTC capability confirmation message sent by the capability query network element is not received within a specified time;

the sending module is further configured to not send the login indication information to the called client corresponding to the called client identifier after receiving the second termination prompt message sent by the receiving module.

With reference to the third aspect, in a fifth possible implementation manner,

the sending module is further configured to send a push request to a push server, where the push request includes the login indication information, and the push request is used to enable the push server to push the login indication information to the called client corresponding to the called client identifier.

With reference to the third aspect, or the first possible implementation manner of the third aspect, or the third possible implementation manner of the third aspect, or the fourth possible implementation manner of the third aspect, or the fifth possible implementation manner of the third aspect, in a sixth possible implementation manner, the login indication information further includes one or both of login manner information and Uniform Resource Locator (URL) information of the WebRTC server, where the login manner information is used to indicate that the called client logs in to the WebRTC server according to the login manner information, and the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information.

With reference to any one of the third to sixth possible implementation manners of the third aspect, in a seventh possible implementation manner,

the sending module is further configured to send a second session request to the called client when detecting that the called client logs in the WebRTC server;

the receiving module is further configured to forward the session response to the calling client after receiving the session response of the called client responding to the second session request, and establish a session between the called client and the calling client.

In a fourth aspect, an embodiment of the present invention provides a called client, including:

the system comprises a receiving module, a login indication module and a login processing module, wherein the login indication information is sent by a call message processing device, and the call message processing device comprises any one of a web real-time communication (WebRTC) server or an interworking gateway;

and the login module is used for logging in the WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

With reference to the fourth aspect, in a first possible implementation manner,

the receiving module is further configured to receive a WebRTC capability query message of the call message processing device;

further comprising:

the first confirmation module is used for confirming whether the called client has the WebRTC capability; the call message processing device is further used for sending WebRTC capability response information to the call message processing device when the called client is confirmed to have the WebRTC capability; and the WebRTC server is further configured to confirm that the called client does not have the WebRTC capability and not send the WebRTC capability response information to the call message processing device.

With reference to the fourth aspect, in a second possible implementation manner,

the receiving module is further configured to receive a WebRTC capability query message sent by a login capability query network element;

further comprising:

the second confirmation module is used for confirming whether the called client has the WebRTC capability; the WebRTC capability query network element is further configured to send WebRTC capability response information to the login capability query network element when the called client is determined to have the WebRTC capability, so that the login capability query network element sends WebRTC capability confirmation information to the call message processing device according to the WebRTC capability response information; and the login capability query network element is further configured to not send the WebRTC capability response information to the login capability query network element when the called client is determined not to have the WebRTC capability.

With reference to the fourth aspect, in a third possible implementation manner, the login indication information further includes login manner information, and the login module includes:

a first obtaining unit, configured to obtain the login manner information included in the login indication information;

and the first login unit is used for logging in the WebRTC server according to the login mode information.

With reference to the fourth aspect, in a fourth possible implementation manner, the login indication information further includes uniform resource locator URL information of the WebRTC server, and the login module includes:

a second obtaining unit, configured to obtain the URL information included in the login instruction information;

and the second login unit is used for logging in the WebRTC server corresponding to the URL information.

With reference to the fourth possible implementation manner of the fourth aspect to the fourth aspect, in a fifth possible implementation manner,

the receiving module is further configured to receive a session request sent by the WebRTC server, where the session request is used by a calling client to request a session to be established with the called client;

further comprising:

and the response module is used for sending a session response to the WebRTC server according to the session request, so that the WebRTC server forwards the session response to the calling client and establishes a session between the called client and the calling client.

When the embodiment of the invention processes the first session request of the calling client, the called client can log in the WebRTC server through sending the login indication information to the called client requested by the first session request so as to establish the session between the calling client and the called client.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a flowchart of a method for processing a call message according to an embodiment of the present invention;

fig. 2 is a flowchart of another call message processing method according to an embodiment of the present invention;

fig. 3a is a structural diagram of a call message processing apparatus according to a first embodiment of the present invention;

fig. 3b is a structural diagram of a call message processing apparatus according to a second embodiment of the present invention;

fig. 3c is a structural diagram of a call message processing apparatus according to a third embodiment of the present invention;

fig. 4a is a structural composition diagram of a called client according to a first embodiment of the present invention;

fig. 4b is a structural composition diagram of a called client according to a second embodiment of the present invention;

fig. 4c is a structural composition diagram of a called client according to a third embodiment of the present invention;

fig. 4d is a structural composition diagram of a called client according to a fourth embodiment of the present invention;

fig. 4e is a structural composition diagram of a called client according to a fifth embodiment of the present invention;

fig. 4f is a structural composition diagram of a called client according to a sixth embodiment of the present invention;

fig. 5 is a flowchart of a calling system according to a first embodiment of the present invention;

fig. 6 is a flowchart of a calling system according to a second embodiment of the present invention;

fig. 7 is a flowchart of a calling system according to a third embodiment of the present invention;

fig. 8 is a flowchart of a calling system according to a fourth embodiment of the present invention;

fig. 9 is a structural diagram of another call message processing apparatus according to an embodiment of the present invention;

fig. 10 is a structural composition diagram of another called client according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 1, fig. 1 is a flowchart of a method for processing a call message according to an embodiment of the present invention, where the method is used when a called (also called Terminating call) client (e.g., user equipment UE) that is requested to establish a session is in a state of not logging in a WebRTC server, and establishes a session between the calling (also called Originating call) client and the called client; the call processing method shown in fig. 1 is described from the perspective of a call message processing apparatus. In the embodiment of the present invention, the call message processing device may be the foregoing WebRTC server, or may also be an interworking gateway. As shown in fig. 1, the method for processing a call message provided in this embodiment includes:

step S110, receiving a first session request of the calling client. In the embodiment of the invention, the first session request carries the called client identification, and the first session request is the request of the calling client to establish session connection with the called client corresponding to the called client identification. In the embodiment of the present invention, the main body for processing the first session request of the calling client is a call message processing device, which may be a WebRTC server or an interworking gateway. In the embodiment of the invention, the calling client logs in the WebRTC server in a certain way, and then sends the first session request to the WebRTC server so as to establish a session with the called client in a non-login state, wherein the non-login state mentioned in the embodiment of the invention is the state that the client does not log in the WebRTC server adopted in the embodiment of the invention. When the call message processing device for processing the first session request is the WebRTC server in the embodiment of the present invention, the first session request is received by the WebRTC server from the calling client; when the call message processing device for processing the first session request is the intercommunication gateway, the first session request is sent to the WebRTC server by the calling client and then forwarded to the intercommunication gateway through the WebRTC server. In addition, the embodiment of the invention does not limit the mode of logging in the calling client to the WebRTC server, and does not limit the sending mode of forwarding the first session request to the intercommunication gateway by the WebRTC server.

And step S111, acquiring the called client identification. When the call message processing device executing the step is a WebRTC server, the WebRTC server acquires the identification of the called client from the first session request; when the call message processing device executing the step is the intercommunication gateway, the intercommunication gateway obtains the called client terminal identification from the first session request.

And step S112, sending login indication information to the called client corresponding to the called client identification. The login indication information is used for indicating the called client to log in the WebRTC server for web page real-time communication according to the login indication information so as to establish a session between the calling client and the called client.

In the embodiment of the present invention, both the calling client and the called client are clients that can log in to the WebRTC server in a certain manner, where the client Identifier may be a universal Identifier for differentiation, such as an MSISDN (mobile station International ISDN Number) of the client, a URL (universal Resource Locator) of the client, a URI (universal Resource Identifier) of the client, and the like, and may also be a customized non-universal Identifier.

As an optional implementation manner, when a client logs in the WebRTC server, the WebRTC server allocates a temporary identity Peer ID to the client, where the temporary identity Peer ID is used for the WebRTC server to forward session messages between login state clients and identify the client according to the temporary identity, so that after the calling client logs in the WebRTC server, there is a temporary identity of the calling client, and when the called client does not log in the WebRTC server, there is no temporary identity of the called client, then, when the WebRTC server detects that the received first session request does not contain the temporary identity of the called client, the WebRTC server can directly serve as a call message processing device, and by implementing the method of the embodiment of the present invention, the called client logs in the WebRTC server, and can also forward the first session request to the interworking gateway, so that the interworking gateway serves as a call message processing device, by implementing the method of the embodiment of the invention, the called client logs in the WebRTC server.

In the embodiment of the invention, the interworking gateway is a gateway with message analysis and notification capabilities, and can receive messages sent by the WebRTC server and send login indication information to the called client, so that the called client logs in the WebRTC server to support the WebRTC server to establish a session between the calling client and the called client.

As an alternative embodiment, the call message processing apparatus may send the login indication information to the called client in the form of a Short message through an SMSC (Short message service Center).

As an optional implementation, the call message processing apparatus may also send the login indication information to the called client in the form of an IP address packet:

acquiring a called client Internet Protocol (IP) address corresponding to a called client identification;

generating login indication information;

and sending login indication information to a called client corresponding to the IP address of the called client.

As an optional implementation manner, when the call message processing apparatus sends the login indication information to the called client in the form of an IP address packet, the call message processing apparatus needs to know the IP address of the called client, and the way to obtain the IP address of the called client may be obtained from information stored in the call message processing apparatus, and may also be obtained from other servers, for example, the IP address of the called client may be obtained through an address translation network element:

The address conversion network element adopted by the embodiment of the invention is communication equipment capable of acquiring the IP address of the client according to the client identifier. In addition, if the address conversion network element fails to acquire the IP address of the called client, the IP address request may be sent to the gateway, and the IP address of the called client is acquired through the gateway and sent to the call message processing device.

As an optional implementation manner, the call message processing apparatus may further determine whether the called client is capable of logging in the WebRTC server, that is, whether the called client has WebRTC capability, and then determine whether to perform an operation of notifying the called client to log in the WebRTC server:

sending a WebRTC capability query message to a called client corresponding to a called client identification;

receiving WebRTC capability response information sent by a called client, wherein the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability; alternatively, the first and second electrodes may be,

In the embodiment of the invention, if the call message processing device receives the WebRTC capability response information, the called client is considered to have WebRTC capability and can log in the WebRTC server in a certain mode, otherwise, if the call message processing device cannot receive the WebRTC capability response information, the WebRTC server considers that the called client does not have the WebRTC capability, and then the called client is not continuously informed to log in.

As an optional implementation manner, the operation of the call message processing apparatus to further confirm whether the called client has WebRTC capability may further confirm through the capability query network element that:

sending a WebRTC capability query instruction of a called client to a capability query network element, wherein the WebRTC capability query instruction of the called client carries a called client identifier;

receiving WebRTC capability confirmation information sent by a capability query network element, wherein the WebRTC capability confirmation information is generated after the capability query network element executes a WebRTC capability query instruction of a called client to query that the called client has WebRTC capability; alternatively, the first and second electrodes may be,

sending a WebRTC capability query instruction of a called client to a capability query network element;

In the embodiment of the invention, when the call message processing device receives the WebRTC capability confirmation information, the called client is considered to have WebRTC capability and can log in the WebRTC server in a certain mode, otherwise, if the call message processing device cannot receive the WebRTC capability confirmation information, the WebRTC server considers that the called client does not have the WebRTC capability, and then the called client is not continuously informed to log in.

As an optional implementation manner, the call message processing apparatus may further send, by using the push server, login indication information to the called client corresponding to the called client identifier:

and sending a pushing request to a pushing server, wherein the pushing request comprises login indication information, and the pushing request is used for enabling the pushing server to push the login indication information to a called client corresponding to the called client identification. The push server adopted by the embodiment of the invention can send the login indication information to the called client in the form of Short Message through an SMSC (Short Message Service Center), and can also push the login indication information to the called client corresponding to the IP address of the called client in the form of an IP address packet.

As an optional implementation manner, the login indication information generated by the call message processing device in the embodiment of the present invention may further include login manner information, where the login manner information is used to indicate which identification corresponding manner the called client logs in to the WebRTC server. The login mode information can be MSISDN identification login information, URL identification login information, URI identification login information and the like, when the login indication information comprises MSISDN identification login information, the called client side should log in the WebRTC server in a mode corresponding to the MSISDN identification, when the login indication information comprises the URL identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URL identification, and when the login indication information comprises the URI identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URI identification. The login mode information included in the login indication information is generally the same as the called client identification information included in the first session request, or if the calling client specifies the login mode of the called client in the first session request, the call message processing device takes the login mode specified by the calling client as the login mode information and sends the login mode information to the called client.

As an optional implementation manner, the login indication information generated by the call message processing apparatus in this embodiment of the present invention may further include URL (uniform resource locator) information of the WebRTC server, where the URL information indicates that the called client logs in the WebRTC server corresponding to the URL information. And URL information is added in the login indication information, so that the called client can accurately log in the WebRTC server where the calling client logs in.

As an optional implementation manner, the login indication information generated by the call message processing apparatus in the embodiment of the present invention may further include a web page URL, and the called client may download a web page corresponding to the web page URL and log in the WebRTC server corresponding to the URL information through the web page.

As an optional implementation manner, in the embodiment of the present invention, when detecting that a calling client logs in, a WebRTC server allocates a calling client temporary identifier to the calling client, and associates the calling client temporary identifier with a calling client identifier and a calling client IP address:

after detecting that the calling client logs in the WebRTC server, the WebRTC server distributes a calling client temporary identifier for the calling client;

and the WebRTC server binds the IP address of the calling client and the temporary identification of the calling client with the identification of the calling client.

Accordingly, as an optional implementation manner, after the called client logs in the WebRTC server according to the login indication information sent by the call message processing device, when the WebRTC server detects that the called client logs in the WebRTC server, the WebRTC server sends a second session request to the called client. The second session request is used for indicating that the calling client requests to establish a session with the called client; and after the called client responds to the second session request and sends a session response to the WebRTC server, the WebRTC server receives the session response of the called client responding to the second session request, and then forwards the session response to the calling client to establish the session between the called client and the calling client.

As an optional implementation manner, correspondingly, when the WebRTC server detects that the called client logs in, sending the second session request to the called client includes:

after the WebRTC server detects that the called client logs in the WebRTC server, the temporary identification of the called client is distributed to the called client;

the WebRTC server binds the called client temporary identifier, the IP address of the called client and the called client identifier;

the WebRTC server sends a second session request to the called client, wherein the second session request comprises the calling client temporary identifier, the calling client IP address, the called client temporary identifier and the called client IP address. The calling client temporary identifier and the called client temporary identifier may be header content of the second session request, and the calling client IP address and the called client IP address may be body content of the second session request.

As an optional implementation manner, after the called client logs in the WebRTC server and confirms that a session is established with the calling client, a session response for responding to the second session request is generated and sent to the WebRTC server, and after receiving the session response, the WebRTC server may forward the session response to the calling client to establish a session between the called client and the calling client:

the WebRTC server receives a session response which is sent by a called client and used for responding to a second session request, wherein the session response comprises a calling client temporary identifier, a calling client IP address, a called client temporary identifier and a called client IP address;

and the WebRTC server forwards the session response to the calling client corresponding to the calling client temporary identifier, and establishes a session between the called client and the calling client.

When the embodiment of the invention processes the first session request of the calling client, the called client logs in the WebRTC server for webpage real-time communication by sending the login indication information to the called client requested by the first session request so as to establish the session between the calling client and the called client.

Referring to fig. 2, fig. 2 is a flowchart of another call message processing method according to an embodiment of the present invention, where the method can implement that a called client in a non-login state establishes a session with a calling client according to login indication information; the call processing method shown in fig. 2 is described from the perspective of a called client. As shown in fig. 2, the method for processing a call message provided in this embodiment includes:

step S210, receiving login indication information sent by a call message processing device, wherein the call message processing device comprises any one of a WebRTC server and an intercommunication gateway;

and step S211, logging in the WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

In the embodiment of the present invention, the sender sending the login indication information may be a call message processing device such as a WebRTC server and an interworking gateway, or may also be a communication device such as a push server and an SMSC having a forwarding capability.

As an optional implementation manner, the login indication information may be an SMSC short message, and then the called client in the embodiment of the present invention reads the login indication information in the form of a short message and logs in the WebRTC server according to the login indication information; the login indication information may also be an IP address packet, and then the called client in the embodiment of the present invention reads the login indication information in the form of the IP address packet and logs in the WebRTC server according to the login indication information.

As an optional implementation manner, before sending the login indication information, the communication device that wants to send the login indication information generally confirms whether the called client is able to log in the WebRTC server, that is, confirms whether the called client has the WebRTC capability, and the called client can confirm and send whether the called client has the WebRTC capability:

receiving a WebRTC capability query message sent by a call message processing device;

confirming whether a called client has WebRTC capability;

if the called client side is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the call message processing equipment; alternatively, the first and second electrodes may be,

and if the called client does not have the WebRTC capability, not sending WebRTC capability response information to the call message processing equipment.

In the embodiment of the invention, the called client generates the WebRTC capability response information to represent that the called client has WebRTC capability and can log in the WebRTC server in a certain mode, otherwise, if the called client does not generate the WebRTC capability response information, the called client does not have the WebRTC capability and cannot log in the WebRTC server in a certain mode.

As an optional implementation manner, the confirming party that confirms whether the called client can log in the WebRTC server may also query the network element for the login capability:

confirming whether a called client has WebRTC capability;

and if the called client does not have the WebRTC capability, not sending WebRTC capability response information to the login capability query network element.

In the embodiment of the invention, the called client sends the WebRTC capability response information to represent that the called client has WebRTC capability and can log in the WebRTC server in a certain mode, otherwise, if the called client does not send the WebRTC capability response information, the called client does not have the WebRTC capability and cannot log in the WebRTC server in a certain mode.

As an optional implementation manner, the login indication information in the embodiment of the present invention may further include login manner information, where the login manner information is used to indicate which identifier corresponding manner the called client logs in to the WebRTC server:

obtaining login mode information contained in login indication information;

and logging in the WebRTC server according to the login mode information.

In the embodiment of the invention, the login mode information can be MSISDN identification login information, URL identification login information, URI identification login information and the like, when the login indication information comprises MSISDN identification login information, the called client side should log in the WebRTC server in a mode corresponding to the MSISDN identification, when the login indication information comprises URL identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URL identification, and when the login indication information comprises URI identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URI identification.

As an optional implementation manner, in the embodiment of the present invention, the login indication information may further include uniform resource locator URL information of the WebRTC server, where the URL information indicates that the called client logs in the WebRTC server corresponding to the URL information:

acquiring URL information contained in login indication information;

and logging in the WebRTC server corresponding to the URL information. The URL information contained in the login indication information can enable the called client to accurately log in the WebRTC server where the calling client logs in.

As an optional implementation manner, in the embodiment of the present invention, the login indication information may further include a web page URL, and the called client may download a web page corresponding to the web page URL and login to the WebRTC server corresponding to the URL information through the web page.

As an optional implementation manner, after a called client logs in a WebRTC server, a session request sent by the WebRTC server may be received, where the session request represents that the calling client requests to establish a session with the called client, where the session request includes a calling client temporary identifier, a calling client IP address, a called client temporary identifier, and a called client IP address, and the called client sends a session response to the WebRTC server according to the session request includes:

the called client determines whether to establish a session with the calling client according to the session request;

and if the called client confirms that the session is established with the calling client, the called client sends a session response to the WebRTC server, so that the WebRTC server forwards the session response to the calling client and establishes the session between the called client and the calling client, wherein the session response comprises the calling client temporary identifier, the calling client IP address, the called client temporary identifier and the called client IP address. The calling client temporary identifier and the called client temporary identifier may be header content of a session response, and the calling client IP address and the called client IP address may be body content of a session response.

In the method of the embodiment of the invention, after receiving the login indication information, the called client logs in the WebRTC server according to the login indication information, and then confirms whether to establish a session with the calling client according to a session request sent by the WebRTC server. The embodiment of the invention does not need to keep the login state of the calling client and the called client at the same time when processing the calling service, the calling object of the calling client can be the called client in the non-login state, the efficiency of calling processing is improved, the calling client can call the called client at any time and any place, and the user experience is improved.

Referring to fig. 3a, fig. 3a is a structural diagram of a call message processing apparatus according to a first embodiment of the present invention. As shown in fig. 3a, the call message processing apparatus according to the embodiment of the present invention corresponds to the call message processing method shown in fig. 1, and is an execution subject based on the call message processing method shown in fig. 1. As shown in fig. 3a, the call message processing apparatus provided in this embodiment includes a receiving module 31, an obtaining module 32, and a sending module 33.

The receiving module 31 is configured to receive a first session request of a calling client. In the embodiment of the invention, the first session request carries the called client identification, and the first session request is the request of the calling client to establish session connection with the called client corresponding to the called client identification. In the embodiment of the present invention, the main body for processing the first session request of the calling client is a call message processing device, which may be a WebRTC server or an interworking gateway. In the embodiment of the invention, the calling client logs in the WebRTC server in a certain way, and then sends the first session request to the WebRTC server so as to establish a session with the called client in a non-login state, wherein the non-login state mentioned in the embodiment of the invention is the state that the client does not log in the WebRTC server adopted in the embodiment of the invention. When the call message processing device for processing the first session request is the WebRTC server in the embodiment of the present invention, the first session request is received by the WebRTC server from the calling client; when the call message processing device for processing the first session request is the intercommunication gateway, the first session request is sent to the WebRTC server by the calling client and then forwarded to the intercommunication gateway through the WebRTC server.

And an obtaining module 32, configured to obtain the called client identifier. When the call message processing device executing the step is a WebRTC server, the WebRTC server acquires the identification of the called client from the first session request; when the call message processing device executing the step is the intercommunication gateway, the intercommunication gateway obtains the called client terminal identification from the first session request.

And the sending module 33 is configured to send login indication information to the called client corresponding to the called client identifier. The login indication information is used for indicating the called client to log in the WebRTC server for web page real-time communication according to the login indication information so as to establish a session between the calling client and the called client.

As an alternative embodiment, referring to fig. 3b, the sending module 33 may further send the login indication information to the called client corresponding to the called client identifier through the obtaining sub-module 331, the generating sub-module 332, and the sending sub-module 333:

the obtaining submodule 331 is configured to obtain a called client internet protocol IP address corresponding to the called client identifier;

the generating submodule 332 is configured to generate login instruction information;

the sending submodule 333 is configured to send login indication information to the called client corresponding to the IP address of the called client.

As an alternative embodiment, referring to fig. 3c, when the call message processing apparatus sends the login indication information to the called client in the form of an IP address packet, the IP address of the called client needs to be known, and the way to acquire the IP address of the called client may be acquired from information stored in the call message processing apparatus, and may also be acquired from other servers, for example, the acquiring sub-module 331 may acquire the IP address of the called client through the address translation network element:

a sending unit 3311, configured to send an address lookup message carrying the called client identifier to an address translation network element;

the receiving unit 3312 is configured to receive the IP address of the called client fed back by the address translation network element.

The address conversion network element adopted by the embodiment of the invention is communication equipment capable of acquiring the IP address of the client according to the client identifier. In addition, in the embodiment of the present invention, when the address translation network element fails to obtain the IP address of the called client, an IP address request may be sent to the gateway, and the IP address of the called client is obtained through the gateway and fed back to the receiving unit 3312.

As an optional implementation manner, the call message processing apparatus may further determine whether the called client is capable of logging in the WebRTC server, that is, whether the called client has WebRTC capability, and then determine whether to perform an operation of notifying the called client to log in the WebRTC server, where:

the sending module 33 is further configured to send a WebRTC capability query message to the called client corresponding to the called client identifier;

the receiving module 31 is further configured to receive WebRTC capability response information sent by the called client, where the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

the receiving module 31 is further configured to generate a first termination prompt message and send the first termination prompt message to the sending module 33 when the WebRTC capability response information sent by the called client is not received within the specified time;

the sending module 33 is further configured to not send login indication information to the called client corresponding to the called client identifier after receiving the first termination prompt message sent by the module 31.

In the embodiment of the present invention, if the receiving module 31 receives the WebRTC capability response information, it is considered that the called client has the WebRTC capability and can log in to the WebRTC server in a certain manner, otherwise, if the receiving module 31 fails to receive the WebRTC capability response information, it is considered that the called client does not have the WebRTC capability, the sending module 33 does not send login indication information to the called client corresponding to the called client identifier, and the call message processing device can feed back information that the called client does not have the WebRTC capability to the calling client.

the sending module 33 is further configured to send a WebRTC capability query instruction of the called client to the capability query network element, where the WebRTC capability query instruction of the called client carries a called client identifier;

the receiving module 31 is further configured to receive WebRTC capability confirmation information sent by the capability query network element, where the WebRTC capability confirmation information is generated after the capability query network element executes a WebRTC capability query instruction of the called client to query that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

the sending module 33 is further configured to send a WebRTC capability query instruction of the called client to the capability query network element;

the receiving module 31 is further configured to generate a second termination prompt message and send the second termination prompt message to the sending module 33 when the WebRTC capability confirmation message sent by the capability query network element is not received within the specified time;

the sending module 33 is further configured to not send the login indication information to the called client corresponding to the called client identifier after receiving the second termination prompt message sent by the receiving module 31.

In the embodiment of the present invention, if the receiving module 31 receives the WebRTC capability confirmation information, it is considered that the called client has the WebRTC capability and can log in to the WebRTC server in a certain manner, otherwise, if the receiving module 31 fails to receive the WebRTC capability confirmation information, it is considered that the called client does not have the WebRTC capability, the sending module 33 does not send login indication information to the called client corresponding to the called client identifier, and the call message processing device can feed back information that the called client does not have the WebRTC capability to the calling client.

As an optional implementation manner, the sending module 33 is further configured to send a push request to the push server, where the push request includes login indication information, and the push request is used to enable the push server to push the login indication information to the called client corresponding to the called client identifier. The push server adopted by the embodiment of the invention can send the login indication information to the called client in the form of Short message through an SMSC (Short message service Center) and can also push the login indication information to the called client corresponding to the IP address of the called client in the form of an IP address packet.

As an optional implementation manner, the login indication information generated by the generation sub-module 332 of the sending module 33 in the embodiment of the present invention may further include login manner information, where the login manner information is used to indicate which identifier corresponding manner the called client logs in to the WebRTC server. The login mode information can be MSISDN identification login information, URL identification login information, URI identification login information and the like, when the login indication information comprises MSISDN identification login information, the called client side should log in the WebRTC server in a mode corresponding to the MSISDN identification, when the login indication information comprises the URL identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URL identification, and when the login indication information comprises the URI identification login information, the called client side should log in the WebRTC server in a mode corresponding to the URI identification. The login mode information contained in the login indication information is generally the same as the identification information of the called client contained in the first session request, or if the calling client specifies the login mode of the called client in the first session request, the call message processing device takes the login mode specified by the calling client as the login mode information and sends the login mode information to the called client.

As an optional implementation manner, in this embodiment of the present invention, the login indication information generated by the generation sub-module 332 of the sending module 33 may further include URL (uniform resource locator) information of the WebRTC server, where the URL information indicates that the called client logs in the WebRTC server corresponding to the URL information. And URL information is added in the login indication information, so that the called client can accurately log in the WebRTC server where the calling client logs in.

As an optional implementation manner, in this embodiment of the present invention, the login indication information generated by the generating sub-module 332 of the sending module 33 may further include a web page URL, and the called client may download a web page corresponding to the web page URL and log in the WebRTC server corresponding to the URL information through the web page.

As an alternative to the above-described embodiment,

the sending module 33 is further configured to send a second session request to the called client when detecting that the called client logs in the WebRTC server;

the receiving module 31 is further configured to forward the session response to the calling client after receiving the session response of the called client responding to the second session request, and establish a session between the called client and the calling client.

After receiving a first session request of a calling client, the call message processing device provided by the embodiment of the invention enables the called client to log in a WebRTC server for webpage real-time communication by sending login indication information to a called client requested by the first session request so as to establish a session between the calling client and the called client.

Referring to fig. 4a, fig. 4a is a structural composition diagram of a called client according to a first embodiment of the present invention. As shown in fig. 4a, the called client provided in the embodiment of the present invention corresponds to the call message processing method shown in fig. 2, and is an execution subject based on the call message processing method shown in fig. 2. As shown in fig. 4a, the called client provided in this embodiment includes a receiving module 41 and a login module 42.

The receiving module 41 is configured to receive login indication information sent by a call message processing device, where the call message processing device includes any one of a WebRTC server for web page real-time communication or an interworking gateway;

and the login module 42 is configured to log in to the WebRTC server according to the login indication information to establish a session between the calling client and the called client.

In the embodiment of the present invention, the sender sending the login indication information may be a WebRTC server, an interworking gateway, or may also be a push server with forwarding capability, an SMSC, or other communication devices.

As an optional implementation manner, referring to fig. 4b, the called client further includes a first confirmation module 43, before the communication device that wants to send the login indication information sends the login indication information, it usually confirms whether the called client can log in the WebRTC server, that is, whether the called client has the WebRTC capability, and the called client can confirm and feed back whether the called client has the WebRTC capability:

a receiving module 41, further configured to receive a WebRTC capability query message sent by the call message processing device;

a first confirming module 43, configured to confirm whether the called client has WebRTC capability; the call message processing device is also used for sending WebRTC capability response information to the call message processing device when the called client is confirmed to have the WebRTC capability; and the call message processing device is also used for confirming that the called client does not have the WebRTC capability, and not sending WebRTC capability response information to the call message processing device.

In the embodiment of the present invention, the first confirmation module 43 sends the WebRTC capability response information to indicate that the called client has the WebRTC capability and can log in to the WebRTC server in a certain manner, whereas if the first confirmation module 43 does not send the WebRTC capability response information, the first confirmation module represents that the called client does not have the WebRTC capability and cannot log in to the WebRTC server in a certain manner.

As an optional implementation manner, referring to fig. 4c, the confirmer that confirms whether the called client can log in to the WebRTC server can also query the network element for the login capability, and the called client further includes a second confirmation module 44:

the receiving module 41 is further configured to receive a WebRTC capability query message sent by the login capability query network element, where the WebRTC capability query message is sent by the login capability query network element after executing a WebRTC capability query instruction of the called client sent by the call message processing device;

further comprising:

a second confirming module 44, configured to confirm whether the called client has WebRTC capability; the device is also used for sending WebRTC capability response information to the login capability query network element when the called client is confirmed to have WebRTC capability, so that the login capability query network element sends the WebRTC capability confirmation information to the call message processing device according to the WebRTC capability response information; and when the called client does not have the WebRTC capability, the WebRTC capability response information is not sent to the login capability query network element.

In the embodiment of the present invention, the second confirmation module 44 generates the WebRTC capability response information to represent that the called client has the WebRTC capability and can log in to the WebRTC server in a certain manner, and on the contrary, if the second confirmation module 44 does not generate the WebRTC capability response information, the second confirmation module represents that the called client does not have the WebRTC capability and cannot log in to the WebRTC server in a certain manner.

As an optional implementation manner, the received login indication information further includes login manner information, and accordingly, the login manner information is used to indicate which identifier corresponding manner the called client logs in to the WebRTC server, as shown in fig. 4d, the login module 42 may further log in through the first obtaining unit 421 and the first login unit 422:

a first obtaining unit 421, configured to obtain login manner information included in the login instruction information;

the first login unit 422 is configured to log in to the WebRTC server according to the login manner information.

As an optional implementation manner, the received login indication information further includes URL (uniform resource locator) information of the WebRTC server, and accordingly, referring to fig. 4e together, the login module 42 may further perform login through the second obtaining unit 423 and the second login unit 424:

a second acquiring unit 423 for acquiring URL information included in the login instruction information;

and a second login unit 424, configured to log in to the WebRTC server corresponding to the URL information.

As an optional implementation manner, in the embodiment of the present invention, the login indication information may further include a web page URL, and the called client may download a web page corresponding to the web page URL and login to the WebRTC server corresponding to the URL information through the web page. The specific implementation may be that after receiving the login instruction information, the underlying operating system of the called client sends the login instruction information to the browser installed with the WebRTC, and the browser logs in the WebRTC server after receiving the login instruction information.

As an optional implementation manner, after logging in to the WebRTC server, the called client in the embodiment of the present invention may further receive a session request sent by the WebRTC server, please refer to fig. 4f, and the called client in the embodiment of the present invention may further include a response module 45:

the receiving module 41 is further configured to receive a session request sent by the WebRTC server, where the session request is used by the calling client to request to establish a session with the called client;

and the response module 45 is configured to send a session response to the WebRTC server according to the session request, so that the WebRTC server forwards the session response to the calling client, and establishes a session between the called client and the calling client.

After receiving the login indication information, the called client logs in the WebRTC server according to the login indication information, and then confirms whether a session is established with the calling client according to a session request sent by the WebRTC server. When the called client processes the call service, the calling client and the called client do not need to keep the login state at the same time, the calling object of the calling client can be the called client in the non-login state, the call processing efficiency is improved, the calling client can call the called client at any time and any place, and the user experience is improved.

Referring to fig. 5, fig. 5 is a flowchart illustrating a process of establishing a session between a calling client and a called client in a non-login state in a calling system according to a first embodiment of the present invention. The call system in the embodiment of the present invention includes a UE a (i.e., a client a), a WebRTC Server (WebRTC Server for web real-time communication), a WebServer, an Open Platform (network element), a GW (Gate Way, query gateway), a push Server, and a UEB (i.e., a client B), where when the UE a requests to establish a session with the UE B through the WebRTC Server, the UE a will become a calling client in the foregoing embodiment, the UE B will become a called client in the foregoing embodiment, the WebRTC Server is a call message processing apparatus in the foregoing embodiment, the Open Platform includes, but is not limited to, an address translation network element and a capability query network element, and specifically, the flow in this embodiment may include the following steps:

in step S510, UE a downloads a Web page to connect to the Web Server. The UE A is a client of the WebRTC Server and can log in the WebRTC Server through a downloaded webpage, and when the UE A requests to establish a session with other clients through the WebRTC Server, the UE A becomes a calling client.

Step S511, the UE A logs in the WebRTC Server.

Step S512, the WebRTC Server allocates a temporary identifier for the UE A, and binds the temporary identifier of the UE A, the identifier of the UE A and the IP address of the UE A.

Step S513, UE A sends the first session request to WebRTC Server, requesting to establish session with UE B. Wherein the first session request includes an identity of UE B.

Step S514, the WebRTC Server obtains the IP address of the UE B through the network element according to the identification of the UE B. And when the WebRTC Server finds that the identifier of the UE B is carried in the request instead of the temporary identifier of the UE B, processing the first session request according to the non-login state of the UE B.

Step S515, the network element feeds back the IP address of the UE B to the WebRTC Server.

Step S516, the WebRTC capability of the UE B is obtained through the UE B.

Step S517, UE B confirms that UE B has WebRTC capability. And if the UE B feeds back that the UE B does not have the WebRTC capability or the UE B fails to feed back the WebRTC capability within the specified time, stopping executing the following steps.

Step S518, the WebRTC Server sends a push request to the push Server. The step is used for enabling the push Server to push login indication information to the UE B, wherein the login indication information is used for indicating the UE B to log in the WebRTC Server. When the push request includes the IP address of the UE B, the push server may push the login indication information in the form of the IP address packet to the UE B where the IP address of the UE B is located. The login indication information may include a Web page address for connecting to the Web Server, a URL address for indicating the WebRTC Server, and may also include login mode information for the UE B to log in to the WebRTC Server.

Step S519, the push server pushes the login indication information to the UE B.

Step S5110, the UE B connects to the Web Server according to the webpage address in the login indication information.

Step S5111, the UE B logs in the WebRTC Server corresponding to the URL address through the webpage according to the login mode in the login indication information.

Step S5112, the WebRTC Server allocates a temporary identifier for the UE B, and binds the temporary identifier of the UE B, the identifier of the UE B and the IP address of the UE B.

Step S5113, the WebRTC Server sends the second session request to the UE B. The message header of the second session request comprises the UE A temporary identifier and the UE B temporary identifier, and the message body of the second session request comprises the IP address of the UE A and the IP address of the UE B.

In step S5114, UE B sends a session response to the WebRTC Server for responding to the second session request. The message header of the session response contains the UE A temporary identifier and the UE B temporary identifier, and the message body of the session response contains the IP address of the UE A and the IP address of the UE B.

Step S5115, the WebRTC Server forwards the session response to the UE a. At this point, the session between UE A and UE B has been successfully established.

Step S5116, the network element obtains the IP address of UE B through the query gateway. When the network element fails to inquire the IP address of the UE B, the network element can inquire through the inquiring gateway.

Step S5117, the gateway is queried to feed back the IP address of UE B to the network element.

Step S5118, the WebRTC Server obtains the WebRTC capability of the UE B through the network element. When the network element fails to inquire the WebRTC capability of the UE B, the inquiry can be carried out through the inquiry gateway.

Step S5119, the network element obtains the WebRTC capability of the UE B through the UE B.

Step S5120, the UE B feeds back the WebRTC capability of the UE B to the network element.

Step S5121, the network element feeds back the WebRTC capability of the UE B.

In the system of the embodiment of the present invention, both UE a and UE B may log in to the WebRTCServer in a certain manner, where the client Identifier may be a universal Identifier for distinguishing, such as an MSISDN (mobile station International ISDN Number) of the client, a URL (universal Resource Locator) of the client, a URI (universal Resource Identifier) of the client, and the like, and may also be a customized non-universal Identifier.

In the system of the embodiment of the invention, the login mode information can be MSISDN identification login information, URL identification login information, URI identification login information and the like, when the login indication information comprises MSISDN identification login information, the UE B should log in the WebRTC Server in a mode corresponding to the MSISDN identification, when the login indication information comprises URL identification login information, the UE B should log in the WebRTC Server in a mode corresponding to the URL identification, and when the login indication information comprises URI identification login information, the UE B should log in the WebRTC Server in a mode corresponding to the URI identification.

The query Gateway used by the system of the embodiment of the present invention may be a GGSN (Gateway GPRS support node) or a PDN GW (Packet Data Network Gateway, etc., and the embodiment of the present invention does not limit the type of the query Gateway.

As an optional implementation manner, when the capability query network element fails to query the WebRTC capability of the UE B, the capability query network element may further query through the query gateway.

As an optional implementation manner, a specific implementation of logging in the WebRTC server by the UE B in the system according to the login indication information in the embodiment of the present invention may be that after receiving the login indication information, the underlying operating system of the called client sends the login indication information to a browser with WebRTC capability, and after receiving the login indication information, the browser logs in the WebRTC server.

Referring to fig. 6, fig. 6 is a flowchart illustrating a process of establishing a session between a calling client and a called client in a non-login state in a calling system according to a second embodiment of the present invention. The call system of the embodiment of the present invention includes a UE a (i.e., a client a), a WebRTC Server (WebRTC Server for Web real-time communication), an interworking gateway, a Web Server, an Open Platform (network element), a GW (Gate Way, query gateway), a push Server, and a UE B (i.e., a client B), where when the UE a requests to establish a session with the UE B through the WebRTC Server, the UE a will become a calling client in the foregoing embodiment, the UE B will become a called client in the foregoing embodiment, the interworking gateway is a call message processing apparatus in the foregoing embodiment, the Open Platform includes, but is not limited to, an address translation network element and a capability query network element, and specifically, the flow of the embodiment may include the following steps:

in step S610, UE a downloads a Web page to connect to the Web Server. The UE A is a client of the WebRTC Server and can log in the WebRTC Server through a downloaded webpage, and when the UE A requests to establish a session with other clients through the WebRTC Server, the UE A becomes a calling client.

In step S611, the UE a logs in to the WebRTC Server.

Step S612, the WebRTC Server allocates a temporary identifier for the UE A, and binds the temporary identifier of the UE A, the identifier of the UE A and the IP address of the UE A.

Step S613, UE a sends a first session request to WebRTC Server, requesting to establish a session with UE B. Wherein the first session request includes an identity of UE B.

Step S614, the WebRTC Server forwards the first session request to the interworking gateway. And when the WebRTC Server finds that the identifier of the UE B is carried in the request instead of the temporary identifier of the UE B, processing the first session request according to the non-login state of the UE B.

Step S615, the intercommunication gateway obtains the IP address of the UE B through the network element according to the identification of the UE B.

Step S616, the network element feeds back the IP address of UE B to the interworking gateway.

Step S617, the interworking gateway obtains the WebRTC capability of the UE B through the UE B.

In step S618, UE B confirms that UE B has WebRTC capability. And if the UE B feeds back that the UE B does not have the WebRTC capability or the UE B fails to feed back the WebRTC capability within the specified time, stopping executing the following steps.

Step S619, the interworking gateway sends the push request to the push server. The step is used for enabling the push Server to push login indication information to the UE B, wherein the login indication information is used for indicating the UE B to log in the WebRTC Server. When the push request includes the IP address of the UE B, the push server may push the login indication information in the form of the IP address packet to the UE B where the IP address of the UE B is located. The login indication information may include a Web page address for connecting to the Web Server, a URL address for indicating the WebRTC Server, and may also include login mode information for the UE B to log in to the WebRTC Server.

Step S6110, the push server pushes the login indication information to the UE B.

Step S6111, UE B connects to Web Server according to the webpage address in the login indication information.

Step S6112, the UE B logs in the WebRTC Server corresponding to the URL address according to the login manner in the login indication information through the web page.

Step S6113, the WebRTC Server allocates a temporary identifier for the UE B, and binds the temporary identifier of the UE B, the identifier of the UE B and the IP address of the UE B.

Step S6114, the WebRTC Server sends the second session request to the UE B. The message header of the second session request comprises the UE A temporary identifier and the UE B temporary identifier, and the message body of the second session request comprises the IP address of the UE A and the IP address of the UE B.

In step S6115, the UE B sends a session response for responding to the second session request to the WebRTC Server. The message header of the session response contains the UE A temporary identifier and the UE B temporary identifier, and the message body of the session response contains the IP address of the UE A and the IP address of the UE B.

Step S6116, the WebRTC Server forwards the session response to the UE a. At this point, the session between UE A and UE B has been successfully established.

Step S6117, the network element obtains the IP address of UE B through the gateway. When the network element fails to inquire the IP address of the UE B, the network element can inquire the IP address through the gateway.

Step S6118, the gateway feeds back the IP address of UE B to the network element.

Step S6119, the WebRTC capability of the UE B is acquired through the network element. When the network element fails to inquire the WebRTC capability of the UE B, the network element can inquire through the gateway and also can inquire through the UE B.

Step S6120, the network element obtains the WebRTC capability of the UE B through the UE B.

Step S6121, the UE B feeds back the WebRTC capability of the UE B to the network element.

Step S6122, the network element feeds back the WebRTC capability of the UE B to the interworking gateway.

Referring to fig. 7, fig. 7 is a flowchart illustrating a process of establishing a session between a calling client and a called client in a non-login state in a calling system according to a third embodiment of the present invention. The call system of the embodiment of the present invention includes a UE a (i.e., a client a), a WebRTC Server (WebRTC Server for web real-time communication), a WebServer (web Server), an Open Platform (network element), a push Server, an SMSC (Short Message service center), and a UE B (i.e., a client B), where when the UE a requests to establish a session with the UE B through the WebRTC Server, the UE a will become a calling client mentioned in the foregoing embodiment, the UE B will become a called client mentioned in the foregoing embodiment, the WebRTC Server is a call Message processing device mentioned in the foregoing embodiment, the OpenPlatform includes, but is not limited to, an address conversion network element and a capability query network element, and specifically, the flow of the embodiment may include the following steps:

in step S710, UE a downloads a Web page to connect to the Web Server.

Step S711, the UE A logs in the WebRTC Server.

Step S712, the WebRTC Server allocates a temporary identifier for the UE A, and binds the temporary identifier of the UE A, the identifier of the UE A and the IP address of the UE A.

Step S713, UE A sends a first session request to WebRTC Server to request to establish session with UE B. Wherein the first session request includes an identity of UE B.

Step S714, the WebRTC Server acquires the WebRTC capability of the UE B.

Step S715, UE B confirms that UE B has WebRTC capability.

Step S716, the WebRTC Server sends a push request to the push Server. The step is used for enabling the push Server to push login indication information to the UE B, wherein the login indication information is used for indicating the UE B to log in the WebRTC Server. The login indication information may include a Web page address for connecting to the Web Server, a URL address for indicating the WebRTC Server, and may also include login mode information for the UE B to log in to the WebRTC Server.

Step S717, the push server pushes the login instruction information to the SMSC, so that the SMSC sends the login instruction information to the UE B in the form of a short message.

Step S718, the SMSC sends the login indication information to the UE B in the form of a short message.

And step S719, the UE B connects to the Web Server according to the webpage address in the login indication information.

And step S7110, the UE B logs in the WebRTC Server corresponding to the URL address through the webpage according to the login mode in the login indication information.

Step S7111, the WebRTC Server distributes the temporary identification for the UE B, and binds the temporary identification of the UE B, the identification of the UE B and the IP address of the UE B.

Step S7112, the WebRTC Server sends a second session request to the UE B.

In step S7113, the UE B sends a session response for responding to the second session request to the WebRTC Server.

Step S7114, the WebRTC Server forwards the session response to the UE a. At this point, the session between UE A and UE B has been successfully established.

And step S7115, the WebRTC Server acquires the WebRTC capability of the UE B through the network element. When the network element fails to inquire the WebRTC capability of the UE B, the inquiry can be carried out through the inquiry gateway.

Step S7116, the network element acquires the WebRTC capability of the UE B through the UE B.

Step S7117, the UE B feeds back the WebRTC capability of the UE B to the network element.

Step S7118, the network element feeds back the WebRTC capability of the UE B.

Compared with the system shown in fig. 7, the system provided by the embodiment of the invention can send the login indication information to the UE B through the SMSC in the form of a short message, and the UE B can read the information sent by the SMSC to perform login operation.

Referring to fig. 8, fig. 8 is a flowchart illustrating a process of establishing a session between a calling client and a called client in a non-login state in a calling system according to a fourth embodiment of the present invention. The call system of the embodiment of the present invention includes a UE a (i.e., a client a), a WebRTC Server (WebRTC Server for Web page real-time communication), an interworking gateway, a Web Server, an Open Platform (network element), a push Server, an SMSC (Short message service Center), and a UE B (i.e., a client B), where when the UE a requests to establish a session with the UE B through the WebRTCServer, the UE a will become a calling client in the foregoing embodiment, the UE B will become a called client in the foregoing embodiment, the interworking gateway is a call message processing apparatus in the foregoing embodiment, the Open Platform includes, but is not limited to, an address conversion network element and a capability query network element, and specifically, the flow of the embodiment may include the following steps:

in step S810, UE A downloads a Web page to connect to a Web Server.

Step S811, UE A logs on to WebRTC Server.

In step S812, the WebRTC Server allocates a temporary identifier for the UE a, and binds the UE a temporary identifier, the identifier of the UE a, and the IP address of the UE a.

In step S813, UE a sends a first session request to the WebRTC Server to request to establish a session with UE B. Wherein the first session request includes an identity of UE B.

Step S814, the WebRTC Server forwards the first session request to the interworking gateway. And when the WebRTC Server finds that the identifier of the UE B is carried in the request instead of the temporary identifier of the UE B, processing the first session request according to the non-login state of the UE B.

Step S815, the interworking gateway obtains the WebRTC capability of the UE B.

Step S816, UE B confirms that UE B has WebRTC capability.

Step S817, the interworking gateway sends the push request to the push server. The step is used for enabling the push Server to push login indication information to the UE B, wherein the login indication information is used for indicating the UE B to log in the WebRTC Server. The login indication information may include a Web page address for connecting to the Web Server, a URL address for indicating the WebRTC Server, and may also include login mode information for the UE B to log in to the WebRTC Server.

Step S818, the push server pushes the login indication information to the SMSC, so that the SMSC sends the login indication information to the UE B in the form of a short message.

Step S819, the SMSC sends the login indication information to the UE B in the form of a short message.

And step S8110, the UE B is connected to the Web Server according to the webpage address in the login indication information.

And step S8111, the UE B logs in the WebRTC Server corresponding to the URL address through the webpage according to the login mode in the login indication information.

Steps S8112 to S8119 are the same as steps S7111 to S7118 described above.

Compared with the system shown in fig. 8, the system provided by the embodiment of the invention can send the login indication information to the UE B through the SMSC in the form of a short message, and the UE B can read the information sent by the SMSC to perform login operation.

Referring to fig. 9, fig. 9 is a structural diagram of another call message processing apparatus according to an embodiment of the present invention. The call message processing apparatus provided in this embodiment corresponds to the call message processing method shown in fig. 1, and is an execution subject based on the call message processing method shown in fig. 1. As shown in fig. 9, the call message processing apparatus provided in this embodiment includes: an input device 91, an output device 92, a memory 93, and a processor 94, wherein the memory 93 stores a set of program codes therein, and the processor 94 is configured to call the program codes stored in the memory 93 for performing the following operations:

acquiring a called client identifier;

and sending login indication information to a called client corresponding to the called client identification, wherein the login indication information is used for indicating the called client to log in a webpage real-time communication WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

As an alternative embodiment, the processor 94 executes sending the login indication information to the called client corresponding to the called client identifier, including:

generating login indication information;

As an alternative embodiment, the processor 94 performs the step of obtaining the called client internet protocol IP address corresponding to the called client identification, including:

As an optional implementation manner, after acquiring the called client identifier, the processor 94 is further configured to perform the following operations before sending the login indication information to the called client corresponding to the called client identifier:

receiving WebRTC capability response information sent by a called client, wherein the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

receiving WebRTC capability confirmation information sent by a capability query network element, wherein the WebRTC capability confirmation information is generated after the capability query network element executes a WebRTC capability query instruction of a called client to query that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

and sending a pushing request to a pushing server, wherein the pushing request comprises login indication information, and the pushing request is used for enabling the pushing server to push the login indication information to a called client corresponding to the called client identification.

As an optional implementation manner, the login indication information further includes one or two of login manner information and uniform resource locator URL information of the WebRTC server, the login manner information is used to indicate the called client to log in the WebRTC server according to the login manner information, and the URL information indicates the called client to log in the WebRTC server corresponding to the URL information.

As an alternative embodiment, after the processor 94 executes sending the login indication information to the called client corresponding to the called client identifier, the following operations are further performed:

when a called client is detected to log in the WebRTC server, a second session request is sent to the called client;

and after receiving a session response of the called client responding to the second session request, forwarding the session response to the calling client, and establishing a session between the called client and the calling client.

Referring to fig. 10, fig. 10 is a block diagram of another called client according to an embodiment of the present invention. The called client provided in this embodiment corresponds to the method for processing the call message shown in fig. 2, and is an execution subject of the method for processing the call message shown in fig. 2. A specific implementation form is shown in fig. 10, where the called client provided in this embodiment includes: an input device 101, an output device 102, a memory 103, and a processor 104, wherein the memory 103 stores a set of program codes therein, and the processor 104 is configured to call the program codes stored in the memory 103 for performing the following operations:

and logging in the WebRTC server according to the login indication information to establish a session between the calling client and the called client.

As an optional implementation manner, before the processor 104 performs the step of receiving the login indication information, the following operation is further performed:

confirming whether a called client has WebRTC capability;

if the called client is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the login capability query network element, so that the login capability query network element sends WebRTC capability confirmation information to the call message processing equipment according to the WebRTC capability response information;

alternatively, the first and second electrodes may be,

As an optional implementation manner, the login indication information further includes login manner information, and the logging in the WebRTC server by the processor 104 according to the login indication information includes:

obtaining login mode information contained in login indication information;

and logging in the WebRTC server according to the login mode information.

As an optional implementation, the login indication information further includes uniform resource locator URL information of the WebRTC server, and the processor 104 executing logging in to the WebRTC server for web page real-time communication according to the login indication information includes:

acquiring URL information contained in login indication information;

and logging in the WebRTC server corresponding to the URL information.

As an optional implementation manner, after logging in to the WebRTC server according to the login indication information, the processor 104 is further configured to:

receiving a session request sent by a WebRTC server, wherein the session request is used for a calling client to request to establish a session with a called client;

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a module or a unit may be divided into only one logical function, and may be implemented in other ways, for example, a plurality of units or modules may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices, modules or units, and may also be an electrical, mechanical or other form of connection.

Modules or units described as separate parts may or may not be physically separate, and parts displayed as modules or units may or may not be physical modules or units, may be located in one place, or may be distributed on a plurality of network modules or units. Some or all of the modules or units can be selected according to actual needs to achieve the purpose of the scheme of the embodiment of the application.

In addition, functional modules or units in the embodiments of the present application may be integrated into one processing module or unit, or each module or unit may exist alone physically, or two or more modules or units are integrated into one module or unit. The integrated module or unit may be implemented in the form of hardware, or may be implemented in the form of a software functional unit.

The integrated modules or units, if implemented in the form of software functional modules or units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention, and these modifications or substitutions are intended to be included in the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for processing a call message, comprising:

acquiring the called client identification;

sending a WebRTC capability query message to a capability query network element or the called client corresponding to the called client identification;

receiving WebRTC capability response information sent by the capability query network element or the called client, wherein the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability;

alternatively, the first and second electrodes may be,

sending the WebRTC capability query message to a capability query network element or the called client corresponding to the called client identification;

when the WebRTC capability response information sent by a capability query network element or the called client is not received within the specified time, login indication information is not sent to the called client corresponding to the called client identification;

and when receiving WebRTC capability response information sent by a capability query network element or the called client, sending login indication information to the called client corresponding to the called client identification, wherein the login indication information is used for indicating the called client to login a webpage real-time communication WebRTC server according to the login indication information so as to establish a session between the calling client and the called client.

2. The method of claim 1, wherein sending login indication information to a called client corresponding to the called client identifier comprises:

generating the login indication information;

and sending the login indication information to the called client corresponding to the IP address of the called client.

3. The method of claim 2, wherein obtaining the called client internet protocol IP address corresponding to the called client identification comprises:

4. The method of claim 1, wherein sending login indication information to the called client corresponding to the called client identifier comprises:

5. The method of claim 1 or 2, wherein the login indication information further includes one or both of login manner information and Uniform Resource Locator (URL) information of the WebRTC server, the login manner information is used for indicating that the called client logs in the WebRTC server according to the login manner information, and the URL information indicates that the called client logs in the WebRTC server corresponding to the URL information.

6. The method according to any one of claims 1 to 4, wherein after sending login indication information to the called client corresponding to the called client identifier, further comprising:

7. A method for processing a call message, comprising:

receiving a WebRTC capability query message sent by a call message processing device or a capability query network element;

confirming whether a called client has the WebRTC capability;

if the called client is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the call message processing equipment or the capability query network element; alternatively, the first and second electrodes may be,

if the called client is confirmed not to have the WebRTC capability, the WebRTC capability response information is not sent to the call message processing equipment or the capability query network element;

receiving login indication information sent by a call message processing device under the condition that the called client is confirmed to have the WebRTC capability, wherein the call message processing device comprises any one of a webpage real-time communication WebRTC server and an interworking gateway;

8. The method of claim 7, wherein the login indication information further includes login manner information, logging in to the WebRTC server according to the login indication information includes:

and logging in the WebRTC server according to the login mode information.

9. The method of claim 7, wherein the login indication information further includes Uniform Resource Locator (URL) information of the WebRTC server, logging in to the WebRTC server for web page real-time communication according to the login indication information includes:

acquiring the URL information contained in the login indication information;

logging in the WebRTC server corresponding to the URL information.

10. The method of any of claims 7-9, wherein after logging into the WebRTC server according to the login indication information, further comprising:

11. A call message processing apparatus, comprising:

the acquisition module is used for acquiring the called client identification;

the sending module is used for sending a WebRTC capability query message to a capability query network element or the called client corresponding to the called client identification; receiving WebRTC capability response information sent by the capability query network element or the called client, wherein the WebRTC capability response information is generated after the called client confirms that the called client has WebRTC capability; or, sending the WebRTC capability query message to a capability query network element or the called client corresponding to the called client identifier; when the WebRTC capability response information sent by a capability query network element or the called client is not received within the specified time, login indication information is not sent to the called client corresponding to the called client identification;

the sending module is further configured to send login indication information to the called client corresponding to the called client identifier when receiving the WebRTC capability response information sent by the capability query network element or the called client, where the login indication information is used to indicate the called client to log in a WebRTC server for web page real-time communication according to the login indication information, so as to establish a session between the calling client and the called client.

12. The call message processing device according to claim 11, wherein the transmission module includes:

13. The call message processing device according to claim 12, wherein the acquisition sub-module includes:

14. The call message processing apparatus of claim 11,

15. The device for processing call messages according to claim 11 or 12, wherein the login indication information further includes one or both of login manner information and uniform resource locator URL information of the WebRTC server, the login manner information is used to indicate that the called client logs in the WebRTC server according to the login manner information, and the URL information indicates that the called client logs in the WebRTC server corresponding to the URL information.

16. The call message processing apparatus according to any one of claims 11-14,

17. A called client, comprising:

the receiving module is used for receiving WebRTC capability query messages sent by the call message processing equipment or the capability query network element;

the confirmation module is used for confirming whether the called client has the WebRTC capability; under the condition that the called client is confirmed to have the WebRTC capability, WebRTC capability response information is sent to the call message processing equipment or the capability query network element; or, under the condition that it is confirmed that the called client does not have the WebRTC capability, not sending the WebRTC capability response information to the call message processing device or the capability query network element;

the receiving module is used for receiving login indication information sent by a call message processing device under the condition that the called client is confirmed to have the WebRTC capability, and the call message processing device comprises any one of a WebRTC server for webpage real-time communication or an interworking gateway;

18. The called client side according to claim 17, wherein the login indication information further includes login manner information, and the login module includes:

19. The called client of claim 17, wherein the login indication information further includes Uniform Resource Locator (URL) information of the WebRTC server, the login module comprising:

20. Called client according to any of claims 17-19,

further comprising: