WO2015164997A1 - Procédé et dispositif de traitement de messages d'appel - Google Patents

Procédé et dispositif de traitement de messages d'appel Download PDF

Info

Publication number
WO2015164997A1
WO2015164997A1 PCT/CN2014/076317 CN2014076317W WO2015164997A1 WO 2015164997 A1 WO2015164997 A1 WO 2015164997A1 CN 2014076317 W CN2014076317 W CN 2014076317W WO 2015164997 A1 WO2015164997 A1 WO 2015164997A1
Authority
WO
WIPO (PCT)
Prior art keywords
called client
webrtc
client
login
capability
Prior art date
Application number
PCT/CN2014/076317
Other languages
English (en)
Chinese (zh)
Inventor
吴问付
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201480000620.3A priority Critical patent/CN105379194B/zh
Priority to PCT/CN2014/076317 priority patent/WO2015164997A1/fr
Publication of WO2015164997A1 publication Critical patent/WO2015164997A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and an apparatus for processing a call message.
  • WebRTC Web Real-time Communication
  • WebRTC Server can initiate a session request to other WebRTC clients in the login state according to any WebRTC client, and establish the WebRTC client and other WebRTCs. Video/voice session between clients.
  • the WebRTC client can only request a session initiated by the WebRTC server to other WebRTC clients that are in the login state.
  • the WebRTC client that initiated the session request is in the non-login state, the WebRTC Server cannot find the session.
  • the WebRTC client that initiated the session request cannot establish a session between the WebRTC client that initiated the request and the WebRTC client that initiated the session request, so the WebRTC client that initiated the request cannot establish a session with the WebRTC Server.
  • a method for processing a call message according to the first aspect of the embodiments of the present application includes:
  • the login indication information is sent to the The called client corresponding to the client identifier includes:
  • the acquiring the called client Internet Protocol IP address corresponding to the called client identifier includes: sending The address of the called client identifies the address to the address translation network element;
  • the method further includes:
  • the login indication information is not sent to the called client corresponding to the called client identifier.
  • the method further includes:
  • the sending the login indication information to the called client corresponding to the called client identifier includes:
  • the push request includes the login indication information, where the push request is used to cause the push server to push the login indication information to the called corresponding to the called client identifier Call the client.
  • the login indication information further includes one or two of login mode information and uniform resource locator URL information of the WebRTC server, where the login mode information is used to indicate The called client logs in to the WebRTC server according to the login mode information, and the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information.
  • the login indication information is sent to the called party corresponding to the called client identifier After the client, it also includes:
  • the second aspect of the present invention provides a method for processing a call message, including: receiving login indication information sent by a call message processing device, where the call message processing device includes any one of a webpage real-time communication WebRTC server and an interworking gateway. ;
  • the method before receiving the login indication information, the method further includes:
  • the WebRTC capability response information is not sent to the call message processing device.
  • the method before receiving the login indication information, the method further includes:
  • the WebRTC capability response information is not sent to the login capability query network element.
  • the login indication information further includes the landing mode information
  • the login to the WebRTC server according to the login indication information includes:
  • the login indication information further includes a uniform resource locator URL information of the WebRTC server, and logging in to the webpage real-time communication according to the login indication information
  • the WebRTC server includes:
  • the method further includes: receiving a session request sent by the WebRTC server, where the session request is used by the calling client to establish a session with the called client. ;
  • an embodiment of the present invention provides a call message processing device, including: a receiving module, configured to receive a first session request of a calling client, where the first session request carries a called client identifier;
  • An obtaining module configured to obtain the called client identifier
  • a sending module configured to send the login indication information to the called client corresponding to the called client identifier, where the login indication information is used to indicate that the called client logs in to the webpage according to the login indication information in real time.
  • the sending module includes: an obtaining submodule, configured to obtain an IP address of the called client internet protocol corresponding to the called client identifier;
  • a sending submodule configured to send the login indication information to the called client corresponding to the IP address of the called client.
  • the obtaining submodule includes:
  • a sending unit configured to send an address lookup message carrying the identifier of the called client to an address translation network element
  • the receiving unit is configured to receive the called client IP address fed back by the address translation network element.
  • 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 a WebRTC capability response message sent by the called client.
  • the WebRTC capability response information is generated after the called client confirms that the called client has the WebRTC capability;
  • 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: when the webRTC capability response information sent by the called client is not received within a predetermined time, generate a first termination prompt message and send the message to the sending module; And after the first termination prompt message sent by the receiving module, the sending login indication information is not sent to the called client corresponding to the called client identifier.
  • the sending module is further configured to send a called client WebRTC capability query command to a capability query network element, where The called client WebRTC capability query instruction carries the called client identifier;
  • the receiving module is further configured to receive the WebRTC capability confirmation information sent by the capability query network element, where the WebRTC capability confirmation information is the capability query.
  • the network element executes the called client WebRTC capability query instruction to query, after the called client has the WebRTC capability, generated;
  • the sending module is further configured to send the called client WebRTC capability query command to the capability query network element;
  • the receiving module is further configured to: when the WebRTC capability confirmation information sent by the capability query network element is not received within a predetermined time, generate a second termination prompt message and send the message to the sending module; And after receiving the second termination prompt message sent by the receiving module, the login indication information is not sent to the called client corresponding to the called client identifier.
  • the sending module is further configured to send a push request to the push server, where the push request includes the login indication information, where the push request is used to cause the push server to push the login indication information to the called client The called client corresponding to the end identifier.
  • the login indication information further includes one or two of login method information and uniform resource locator URL information of the WebRTC server, where the login The mode information is used to indicate that the called client logs in to the WebRTC server according to the login mode information, and the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information.
  • the sending module is further configured to: when detecting that the called client logs in to the WebRTC server, send a second session request to the called client;
  • the receiving module is further configured to: after receiving the session response of the called client in response to the second session request, forwarding the session response to the calling client, establishing the called client and the client The session between the calling client and the client.
  • an embodiment of the present invention provides a called client, including:
  • a receiving module configured to receive login indication information sent by the call message processing device, where the call message processing device includes any one of a webpage real-time communication WebRTC server or an interworking gateway;
  • the login module 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.
  • the receiving module is further configured to receive a WebRTC capability query message of the call message processing device;
  • a first confirmation module configured to confirm whether the called client has the WebRTC capability, and configured to: when the called client has the WebRTC capability, send a WebRTC capability response message to the call message processing
  • the device is further configured to: confirm that the called client does not have the WebRTC capability, and does not send the WebRTC capability response information to the call message processing device.
  • the receiving module is further configured to receive a WebRTC capability query message sent by the login capability query network element;
  • the network element is configured to send the WebRTC capability confirmation information to the call message processing device according to the WebRTC capability response information, and to confirm that the called client does not have the WebRTC capability.
  • the WebRTC capability response information is not sent to the login capability query network element.
  • the login indication information further includes a login mode information, where the login module includes:
  • the first obtaining unit is configured to acquire the login mode information included in the login indication information, and the first login unit is configured to log in to the WebRTC server according to the login mode information.
  • the login indication information further includes a uniform resource locator URL information of the WebRTC server, where the login module includes:
  • a second acquiring unit configured to acquire the URL information included in the login indication information
  • a second login unit configured to log in to the WebRTC server corresponding to the URL information.
  • the receiving module is further configured to receive a session request sent by the WebRTC server, where the session request is used by the calling client to establish a session with the called client.
  • a response module configured to send a session response to the WebRTC server according to the session request, cause the WebRTC server to forward the session response to the calling client, and establish the called client and the calling party A session between clients.
  • the embodiment of the present invention can send the login indication information to the called client requested by the first session request, so that the called client logs in to the webpage real-time communication WebRTC server to establish the master.
  • the session between the client and the called client is called.
  • the embodiment of the present invention implements that the called client is in a non-login to the WebRTC server state, and supports the calling client to establish a session with the calling client.
  • the client can call the called party anytime and anywhere, thereby improving the user experience.
  • 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 method for processing a call message according to an embodiment of the present invention
  • FIG. 3 is a structural diagram of a call message processing apparatus according to a second embodiment of the present invention
  • FIG. 3 is a schematic diagram of a call message according to a third embodiment of the present invention
  • FIG. 4 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
  • 4c is a structural composition diagram of a called client according to a third embodiment of the present invention
  • FIG. 4 is a structural composition diagram of a called client according to a fourth embodiment of the present invention
  • FIG. 4e is a fifth embodiment of the present invention
  • FIG. 4 is a structural composition diagram of a called client according to a sixth embodiment of the present invention
  • FIG. 5 is a structural diagram of a called client according to a sixth embodiment of the present invention
  • a call flow system schematic
  • FIG. 6 is a schematic flowchart of a call system according to a second embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a call system according to a third embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a call 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
  • FIG. 1 is a flowchart of a method for processing a call message according to an embodiment of the present invention.
  • the method is used for a called party (also called a terminating call) client (eg, a user equipment) that is requested to establish a session.
  • a called party also called a terminating call
  • client eg, a user equipment
  • the UE is in a state of not logging in to the WebRTC server, and establishes a session between the client (also called an Originating call) client and the called client; wherein, the call processing method shown in FIG. 1 is a call message.
  • the angle of the processing device is described.
  • the call message processing device may be the foregoing WebRTC server, or may be an interworking gateway.
  • the method for processing a call message provided by this embodiment includes:
  • Step S110 Receive a first session request of the calling client.
  • the first session request carries the called client identifier, and the first session requests the calling client to establish a session connection with the called client corresponding to the called client identifier.
  • the subject of the first session request of the calling client is a call message processing device, which may be a WebRTC server or an interworking gateway.
  • the calling client first logs in to the WebRTC server in a certain manner, and then sends a first session request to the WebRTC server to establish a session with the called client in the non-login state.
  • the non-login state mentioned in the example is a state in which the client does not log in to the WebRTC server used in the embodiment of the present invention.
  • the call message processing apparatus that processes the first session request is a WebRTC server
  • the first session request is received by the WebRTC server from the calling client; when implementing the embodiment of the present invention, processing the first session request
  • the call message processing device is an interworking gateway
  • the first session request is sent by the calling client to the WebRTC server, and then forwarded to the interworking gateway via the WebRTC server.
  • the embodiment of the present invention does not limit the manner in which the calling client logs in to the WebRTC server, and the manner in which the WebRTC server forwards the first session request to the interworking gateway is not limited.
  • Step Sl11 Obtain the called client identifier.
  • the call message processing device performing this step is a WebRTC server
  • the WebRTC server obtains the called client identifier from the first session request;
  • the call message processing device performing this step is the interworking gateway, the interworking gateway requests from the first session Get the called client ID.
  • Step S112 Send the login indication information to the called client corresponding to the called client identifier.
  • the login indication information is used to instruct the called client to log in to the webpage real-time communication WebRTC server according to the login indication information to establish a session between the calling client and the called client.
  • both the calling client and the called client can log in to the system in a certain manner.
  • the client of the WebRTC server where the client identifier can be a universal identifier for distinguishing functions, such as the MSISDN (Mobile Station International ISDN Number) of the client, the URL of the client (Uniform Resource Locator), The URI (Uniform Resource Identifier) of the client, etc., may also be a customized non-universal identifier.
  • the WebRTC server allocates a temporary identifier Peer ID to the client, and the temporary identifier Peer ID is used by the WebRTC server to forward the session between the login state clients.
  • the message identifies the client according to the temporary identifier. Therefore, after the calling client logs in to the WebRTC server, there is a temporary identifier of the calling client, and when the called client does not log in to the WebRTC server, there is no temporary identifier of the called client.
  • the WebRTC server detects that the received first session request does not include the called client temporary identifier, the WebRTC server can directly act as a call message processing device, and the called client is logged in by implementing the method of the embodiment of the present invention.
  • the first session request may be forwarded to the interworking gateway, and the interworking gateway is used as the call message processing device to enable the called client to log in to the WebRTC server by implementing the method in the embodiment of the present invention.
  • the interworking gateway is a gateway with message analysis and notification capability, which can receive the message sent by the WebRTC server, and send the login indication information to the called client, so that the called client logs in to the WebRTC server.
  • the interworking gateway can support the WebRTC server to establish a session between the calling client and the called client.
  • 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).
  • SMSC Short Message Service Center
  • the call message processing apparatus may also send the login indication information to the called client in the form of an IP address packet:
  • the call message processing apparatus 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 of the called client.
  • the address of the called client IP address can be obtained from the information saved in the call message processing device, and can also be obtained from other server terminals.
  • the IP address of the called client can be obtained through the address translation network element:
  • the address translation network element used in the embodiment of the present invention is a communication device capable of obtaining a client IP address according to a client identifier.
  • the IP address request may be sent to the gateway, and the IP address of the called client is obtained by the gateway and sent to the call message processing apparatus.
  • the call message processing apparatus may further confirm whether the called client can log in to the WebRTC server, that is, whether the called client has the WebRTC capability, and then determine whether to perform the notification of the called client login.
  • the WebRTC server To the operation of the WebRTC server:
  • the call message processing device receives the WebRTC capability response information, and considers that the called client has the WebRTC capability, and can log in to the WebRTC server in a certain manner, and if the call message processing device fails to receive the WebRTC capability.
  • the WebRTC server considers that the called client does not have the WebRTC capability, and then no longer informs the called client to log in.
  • the call message processing apparatus further confirms whether the called client has WebRTC capable operation and can also confirm by the capability query network element:
  • the receiving capability queries the WebRTC capability confirmation information sent by the network element, where the WebRTC capability confirmation information is the capability query network element executes the called client WebRTC capability query instruction to query the called party. Generated after the client has WebRTC capabilities; or,
  • the login indication information is not sent to the called client corresponding to the called client identifier.
  • the call message processing device receives the WebRTC capability confirmation information, and considers that the called client has the WebRTC capability, and can log in to the WebRTC server in a certain manner, and if the call message processing device fails to receive the WebRTC capability. If the information is confirmed, the WebRTC server considers that the called client does not have the WebRTC capability, and then does not continue to notify the called client to log in.
  • the call message processing apparatus may further send the landing indication information to the called client corresponding to the called client identifier by using the push server:
  • the push server used in the embodiment of the present invention may send the login indication information to the called client in the form of a short message through the SMSC (Short Message Service Center), or may log in as an IP address packet.
  • the indication information is pushed to the called client corresponding to the IP address of the called client.
  • the login indication information generated by the call message processing apparatus in the embodiment of the present invention may further include login mode information, where the login mode information is used to indicate, in which identifier corresponding manner, the called client logs in to the WebRTC server.
  • the login mode information may be an MSISDN identification login information, a URL identification login information, and a URI identification login information.
  • the login indication information includes the MSISDN identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the MSISDN identifier.
  • the login indication information includes the URL identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the URL identifier.
  • the login indication information includes the URI identification login information
  • the called client should log in to the corresponding manner by the URI identifier.
  • WebRTC server The login mode information included in the login indication information is usually 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 is made.
  • the message processing device uses the login method specified by the calling client as the login mode information and sends the login method to the called client.
  • the login indication information generated by the call message processing apparatus in the embodiment of the present invention may further include a URL of the WebRTC server (Uniform Resource Locator M), the URL information indicates that the called client logs in to the URL.
  • the WebRTC server corresponding to the information. Adding the URL information in the login indication information enables the called client to accurately log in to the WebRTC server to which the calling client logs in.
  • the login indication information generated by the call message processing apparatus in the embodiment of the present invention may further include a webpage URL, and the called client may download the webpage corresponding to the webpage URL, and then log in to the foregoing through the webpage.
  • the WebRTC server corresponding to the URL information may be further included in the login indication information generated by the call message processing apparatus in the embodiment of the present invention.
  • the WebRTC server when detecting that the calling client logs in, allocates a temporary identity of the calling client to the calling client, and temporarily identifies the calling client.
  • the calling client ID and the calling client IP address are associated:
  • the WebRTC server After detecting that the calling client logs in to the WebRTC server, the WebRTC server allocates a temporary identifier of the calling client to the calling client;
  • the WebRTC server binds the calling client IP address and the calling client temporary identity to the calling client identity.
  • the WebRTC server after the called client logs in to 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 to the WebRTC server, it will send the first Two session requests to the called client.
  • the second session request is used to indicate that the calling client request establishes a session with the called client.
  • the WebRTC server receives the called client response.
  • the forwarding session responds to the calling client to establish a session between the called client and the calling client.
  • sending the second session request to the called client includes:
  • the WebRTC server After detecting that the called client logs in to the WebRTC server, the WebRTC server allocates the called client temporary identifier to the called client.
  • the WebRTC server binds the called client temporary identifier, the called client IP address, and the called client identifier.
  • the WebRTC server sends a second session request to the called client, and the second session request includes the main Call the client temporary ID, 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 the message header content of the second session request, and the calling client IP address and the called client IP address may be the message body content of the second session request.
  • a session response for responding to the second session request is generated and sent to the WebRTC server, and the WebRTC server receives After the session response, the session response may be forwarded to the calling client to establish a session between the called client and the calling client:
  • the WebRTC server receives the session response sent by the called client for responding to the second session request, where the session response includes the calling client temporary identifier, the calling client IP address, the called client temporary identifier, and the called client. End IP address;
  • the WebRTC server forwards the session response to the calling client corresponding to the temporary identifier of the calling client, and establishes a session between the called client and the calling client.
  • the embodiment of the present invention sends the login indication information to the called client requested by the first session request, so that the called client logs in to the webpage real-time communication WebRTC server to establish the calling party.
  • the call service between the client and the called client does not require the calling client and the called client to remain in the login state at the same time, and the called client that is initiated the session request is not logged in.
  • the calling client can establish a session with the method of the embodiment of the present invention, thereby improving the efficiency of call processing, enabling the calling client to call the called party anytime and anywhere, thereby improving the user experience.
  • FIG. 2 is a flowchart of another method for processing a call message according to an embodiment of the present invention.
  • the method can be implemented by a called client in a non-login state to establish a session with a calling client according to the login indication information.
  • the method for processing the call shown in FIG. 2 is described from the perspective of a called client.
  • the method for processing a call message provided by this embodiment includes:
  • Step S210 Receive login indication information sent by the call message processing device, where the call message processing device includes any one of a webpage real-time communication WebRTC server and an interworking gateway;
  • Step S211 Log in to the WebRTC server according to the login indication information, to establish a calling client. The session between the endpoint and the called client.
  • the sender of the login indication information may be a call message processing device such as a WebRTC server or an interworking gateway, or may be a push server with a forwarding capability, a communication device such as an SMSC, etc.
  • the sender is not restricted.
  • 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 to the WebRTC server according to the login indication information.
  • the login indication information may also be an IP address package, and the called client in the embodiment of the present invention will read the login indication information in the form of an IP address packet, and log in to the WebRTC server according to the login indication information.
  • the form of the login instruction information is not limited.
  • the communication device that sends the login indication information usually confirms whether the called client can log in to the WebRTC server, that is, whether the called client has the WebRTC capability, and is Ask the client to confirm and send if it has WebRTC capabilities:
  • the WebRTC capability response information is sent to the call message processing device.
  • the WebRTC capability response message is not sent to the call message processing device.
  • the called client generates the WebRTC capability response information, and the called client has the WebRTC capability, and can log in to the WebRTC server in a certain manner. Otherwise, if the called client does not generate the WebRTC capability response information, the representative The called client does not have the WebRTC capability and cannot log in to the WebRTC server in a certain way.
  • the confirming party that confirms whether the called client can log in to the WebRTC server can also query the network element for the login capability:
  • the login capability querying network element enables the login capability querying network element to send the WebRTC capability confirmation information to the call message processing device according to the WebRTC capability response information;
  • the WebRTC capability response information is not sent to the login capability to query the network element.
  • the called client sends the WebRTC capability response information on behalf of the called client to have the WebRTC capability, and can log in to the WebRTC server in a certain manner, and if the called client does not send the WebRTC capability response information, the representative The called client does not have the WebRTC capability and cannot log in to the WebRTC server in a certain way.
  • the login indication information in the embodiment of the present invention may further include login mode information, where the login mode information is used to indicate, in which identity manner the called client logs in to the WebRTC server:
  • the login mode information may be an MSISDN identifier login information, a URL identifier login information, and a URI identifier login information.
  • the login indication information includes the MSISDN identifier login information
  • the called client should use the MSISDN identifier corresponding manner.
  • the login indication information includes the URL identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the URL identifier.
  • the login indication information includes the URI identification login information
  • the called client should use the URI. Log in to the WebRTC server in the same way as the logo.
  • the login indication information in the embodiment of the present invention may further include a uniform resource locator URL information of the WebRTC server, where the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information:
  • the URL information contained in the login indication information enables the called client to accurately log in to the WebRTC server to which the calling client logs in.
  • the login indication information in the embodiment of the present invention may further include a webpage URL
  • the called client may download the webpage corresponding to the webpage URL, and then log in to the WebRTC server corresponding to the URL information through the webpage.
  • the called client after the called client logs in to the WebRTC server, it can be connected.
  • the called client IP address the called client sends a session response to the WebRTC server according to the session request, including:
  • the called client determines whether to establish a session with the calling client according to the session request
  • the called client If the called client confirms that a 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 called client and the calling client.
  • the session response includes 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 the message header content of the session response, and the calling client IP address and the called client IP address may be the message body content of the session response.
  • the called client after receiving the login indication information, the called client logs in to the WebRTC server according to the login indication information, and then confirms whether to establish a session with the calling client according to the session request sent by the WebRTC server.
  • the calling client and the called client are not required to maintain the login state at the same time, and the calling client of the calling client may be the called client in the non-login state, thereby improving the efficiency of call processing.
  • the client can call the called party anytime and anywhere, improving the user experience.
  • FIG. 3a is a structural diagram of a call message processing apparatus according to a first embodiment of the present invention.
  • the call message processing apparatus according to the embodiment of the present invention corresponds to the processing method of the call message shown in FIG. 1, and is an execution subject based on the processing method of the call message shown in FIG. 1.
  • the specific implementation is 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 the calling client.
  • the first session request carries the called client identifier, and the first session requests the calling client to establish a session connection with the called client corresponding to the called client identifier.
  • the subject of the first session request of the calling client is a call message processing device, which may be a WebRTC server or an interworking gateway.
  • the calling client first uses a certain party. Log in to the WebRTC server, and then send a first session request to the WebRTC server to establish a session with the called client in the non-login state.
  • the non-login state mentioned in the embodiment of the present invention is that the client is not logged in.
  • the state of the WebRTC server used in the embodiment of the present invention is a WebRTC server
  • the first session request is received by the WebRTC server from the calling client; when the embodiment of the present invention is implemented, the first session request is processed.
  • the call message processing device is an interworking gateway
  • the first session request is sent by the calling client to the WebRTC server, and then forwarded to the interworking gateway via the WebRTC server.
  • the obtaining module 32 is configured to obtain the called client identifier.
  • the call message processing device that performs this step is a WebRTC server
  • the WebRTC server obtains the called client identifier from the first session request;
  • the call message processing device that performs this step is the interworking gateway, the interworking gateway requests from the first session. Get the called client ID.
  • the sending module 33 is configured to send the login indication information to the called client corresponding to the called client identifier.
  • the login indication information is used to indicate that the called client logs in to the 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.
  • both the calling client and the called client can log in to the client of the WebRTC server in a certain manner, wherein the client identifier can be a universal identifier for distinguishing functions, such as the MSISDN of the client (Mobile Station International)
  • the ISDN number, the mobile station international ISDN number, the client's URL (Uniform Resource Locator), the client's URI (Uniform Resource Identifier), etc. may also be customized non-generic identifiers.
  • 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).
  • SMSC Short Message Service Center
  • the sending module 33 can improve the sending of the login indication information to the called client identifier by the obtaining submodule 331, the generating submodule 332, and the sending submodule 333.
  • the obtaining sub-module 331 is configured to obtain the called client Internet Protocol IP address corresponding to the called client identifier.
  • the sending submodule 333 is configured to send the login indication information to the called client corresponding to the IP address of the called client.
  • the call message processing apparatus when the call message processing apparatus sends the login indication information to the called client in the form of an IP address packet, it is necessary to know the IP address of the called client, and obtain The called client IP address path can be obtained from the information saved in the call message processing device, and can also be obtained from other server terminals.
  • the obtaining submodule 331 can obtain the called client IP address through the address translation network element:
  • the sending unit 3311 is configured to send an address lookup message carrying the identifier of the called client to the address translation network element.
  • the receiving unit 3312 is configured to receive the called client IP address fed back by the address translation network element.
  • the address translation network element used in the embodiment of the present invention is a communication device capable of obtaining a client IP address according to a client identifier.
  • the 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.
  • the call message processing apparatus may further confirm whether the called client can log in to the WebRTC server, that is, whether the called client has the WebRTC capability, and then determine whether to perform the notification of the called client login.
  • the operation to 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 the 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 the WebRTC capability;
  • 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: when the webRTC capability response information sent by the called client is not received within the specified time, generate a first termination prompt message and send the message to the sending module 33;
  • the sending module 33 is further configured to: after receiving the first termination prompt message sent by the module 31, The land indication information is to the called client corresponding to the called client identifier.
  • the receiving module 31 receives the WebRTC capability response information, and considers 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. If the called client does not have the WebRTC capability, the sending module 33 does not send the login indication information to the called client corresponding to the called client identifier, and the calling message processing device can not have the WebRTC capability of the called client. The information is fed back to the calling client.
  • the call message processing apparatus further confirms whether the called client has WebRTC capable operation and can also confirm by the capability query network element:
  • the sending module 33 is further configured to send the called client WebRTC capability query command to the capability query network element, and the called client WebRTC capability query command carries the called client identifier;
  • the receiving module 31 is further configured to receive the 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 executing the called client WebRTC capability query command to query the called client to have the WebRTC capability;
  • the sending module 33 is further configured to send the called client WebRTC capability query command to the capability query network element;
  • the receiving module 31 is further configured to: when the WebRTC capability confirmation information sent by the capability query network element is not received within the specified time, generate a second termination prompt message and send the message to the sending module 33;
  • the sending module 33 is further configured to: after receiving the second termination prompt message sent by the receiving module 31, send the login indication information to the called client corresponding to the called client identifier.
  • the receiving module 31 receives the WebRTC capability confirmation information, and considers 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. If the called client does not have the WebRTC capability, the sending module 33 does not send the login indication information to the called client corresponding to the called client identifier, and the calling message processing device can not have the WebRTC capability of the called client. The information is fed back to the calling client.
  • 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 log in the login indication
  • the information is pushed to the called client corresponding to the called client identifier.
  • the push server used in the embodiment of the present invention may send the login indication information to the called client in the form of a short message through the SMSC (Short Message Service Center), or may log in as an IP address packet.
  • the indication information is pushed to the called client corresponding to the IP address of the called client.
  • the login indication information generated by the generating submodule 332 of the sending module 33 in the embodiment of the present invention may further include login mode information, where the login mode information is used to indicate which identifier is used by the called client. Log in to the WebRTC server in the corresponding way.
  • the login mode information may be an MSISDN identification login information, a URL identification login information, and a URI identification login information.
  • the login indication information includes the MSISDN identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the MSISDN identifier.
  • the login indication information includes the URL identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the URL identifier.
  • the called client When the login indication information includes the URI identification login information, the called client should log in to the corresponding manner by the URI identifier. WebRTC server.
  • the login mode information included in the login indication information is usually 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 is made.
  • the message processing device uses the login mode specified by the calling client as the login mode information and sends the login mode information to the called client.
  • the login indication information generated by the generating submodule 332 of the sending module 33 in the embodiment of the present invention may further include a URL (Uniform Resource Locator) information of the WebRTC server, where the URL information indicates the called client. Log in to the WebRTC server corresponding to the URL information. Adding URL information to the login indication information allows the called client to accurately log in to the WebRTC server where the calling client is logged.
  • URL Uniform Resource Locator
  • the login indication information generated by the generating submodule 332 of the sending module 33 in the embodiment of the present invention may further include a webpage URL, and the called client may download the webpage corresponding to the webpage URL, and then pass the webpage.
  • the web page is logged in to the WebRTC server corresponding to the aforementioned URL information.
  • the sending module 33 is further configured to: when detecting that the called client logs in to the WebRTC server, send a second session request to the called client;
  • the receiving module 31 is further configured to: after receiving the session response of the called client in response to the second session request, forward the session response to the calling client, and establish a session between the called client and the calling client.
  • the call message processing apparatus provided by the embodiment of the present invention sends the login indication information to the called client requested by the first session request, so that the called client logs in to the webpage for real-time communication.
  • the WebRTC server is configured to establish a session between the calling client and the called client.
  • the call service supported by the call message processing apparatus in the embodiment of the present invention does not require the calling client and the called client to remain in the login state at the same time.
  • the calling client can establish a session with the method according to the embodiment of the present invention, thereby improving the efficiency of call processing and enabling the calling client to call anytime and anywhere. Calling the end, improving the user experience.
  • FIG. 4a is a structural diagram of a called client according to a first embodiment of the present invention.
  • the called client according to the embodiment of the present invention corresponds to the processing method of the call message shown in FIG. 2, and is an execution body based on the processing method of the call message shown in FIG. 2.
  • the specific implementation is 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 the login indication information sent by the call message processing device, where the call message processing device includes any one of a webpage real-time communication WebRTC server or an interworking gateway; and the login module 42 is configured to log in to the WebRTC according to the login indication information.
  • the server to establish a session between the calling client and the called client.
  • the sender that sends the login indication information may be a WebRTC server, an interworking gateway, or a push server with a forwarding capability, a communication device such as an SMSC, and the like, and the sender of the login indication information is not used in the embodiment of the present invention. limit.
  • 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 to the WebRTC server according to the login indication information.
  • the login indication information may also be an IP address package, and the called client in the embodiment of the present invention will read the login indication information in the form of an IP address packet, and log in to the WebRTC server according to the login indication information.
  • the form of the login instruction information is not limited.
  • the called client further includes the first authentic
  • the module 43 the communication device that wants to send the login indication information, generally confirms whether the called client can log in to the WebRTC server before sending the login indication information, that is, whether the called client has WebRTC capability, and the called client can perform Acknowledge and feedback whether it has the WebRTC capability: the receiving module 41 is further configured to receive the WebRTC capability query message sent by the call message processing device;
  • the first confirmation module 43 is configured to confirm whether the called client has the WebRTC capability; and is further configured to: when the called client has the WebRTC capability, send the WebRTC capability response information to the call message processing device; and also used to confirm the called client When the terminal does not have the WebRTC capability, the WebRTC capability response message is not sent to the call message processing device.
  • the first confirmation module 43 sends 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. Otherwise, if the first confirmation module 43 does not send the WebRTC capability response information, On behalf of the called client does not have WebRTC capabilities, can not log in to the WebRTC server in a certain way.
  • FIG. 4c can also query the network element for the login capability, and the called client further includes the second confirming module 44. :
  • the receiving module 41 is further configured to receive the WebRTC capability query message sent by the login capability query network element, where the WebRTC capability query message is sent after the login capability query network element executes the called client WebRTC capability query command sent by the call message processing device;
  • the second confirmation module 44 is configured to confirm whether the called client has the WebRTC capability; and is further configured to: when the called client has the WebRTC capability, send the WebRTC capability response information to the login capability query network element, so that the login capability queries the network element.
  • the WebRTC capability confirmation information is sent 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.
  • the second confirmation module 44 generates the WebRTC capability response information, and the called client has the WebRTC capability, and can log in to the WebRTC server in a certain manner. Otherwise, if the second confirmation module 44 does not generate the WebRTC capability response information, On behalf of the called client does not have WebRTC capabilities, can not log in to the WebRTC server in a certain way.
  • the received login indication information further includes login mode information, and correspondingly, the login mode information is used to indicate, in which identifier corresponding manner, the called client logs in to the
  • the WebRTC server can refer to FIG. 4d together, and the login module 42 can further log in through the first obtaining unit 421 and the first login unit 422:
  • the first obtaining unit 421 is configured to obtain the login mode information included in the login indication information.
  • the first login unit 422 is configured to log in to the WebRTC server according to the login mode information.
  • the login mode information may be an MSISDN identifier login information, a URL identifier login information, and a URI identifier login information.
  • the login indication information includes the MSISDN identifier login information
  • the called client should use the MSISDN identifier corresponding manner.
  • the login indication information includes the URL identification login information
  • the called client should log in to the WebRTC server in the corresponding manner of the URL identifier.
  • the login indication information includes the URI identification login information
  • the called client should use the URI. Log in to the WebRTC server in the same way as the logo.
  • the received login indication information further includes a URL (Uniform Resource Locator) information of the WebRTC server, and correspondingly, referring to FIG. 4e, the login module 42 may further pass the second obtaining unit. 423 and the second login unit 424 perform login:
  • URL Uniform Resource Locator
  • the second obtaining unit 423 is configured to obtain the URL information included in the login indication information, and the second login unit 424 is configured to log in to the WebRTC server corresponding to the URL information.
  • the login indication information in the embodiment of the present invention may further include a webpage URL
  • the called client may download the webpage corresponding to the webpage URL, and then log in to the WebRTC server corresponding to the URL information through the webpage.
  • the specific implementation may be that after the underlying operating system of the called client receives the login indication information, the login indication information is sent to the browser with WebRTC installed, and the browser logs in to the WebRTC server after receiving the login indication information.
  • the session request sent by the WebRTC server can also be received.
  • the called client in the embodiment of the present invention is used.
  • a response module 45 can also be included:
  • 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 establish a session with the called client.
  • the response module 45 is configured to send a session response to the WebRTC server according to the session request, enable the WebRTC server to forward the session response to the calling client, and establish the called client and the calling client. The conversation between.
  • the called client After receiving the login indication information, the called client according to the embodiment of the present invention logs in to the WebRTC server according to the login indication information, and then confirms whether to establish a session with the calling client according to the session request sent by the WebRTC server.
  • the called client processes the call service in the embodiment of the present invention, the calling client and the called client are not required to remain in the login state at the same time, and the calling client of the calling client may be the called client in the non-login state, and the call is improved.
  • the processing efficiency, the calling client can call the called party anytime and anywhere, improving the user experience.
  • FIG. 5 is a schematic flowchart of a call system according to a first embodiment of the present invention.
  • the figure shows a process of establishing a session between a calling client and a called client in a non-login state in a call system.
  • the call system in the embodiment of the present invention includes UE A (ie, client A), WebRTC Server (Website real-time communication WebRTC server), Web Server (Web server), Open Platform (Network Element), and GW (Gateway).
  • UE A ie, client A
  • WebRTC Server Website real-time communication WebRTC server
  • Web Server Web Server
  • Open Platform Network Element
  • GW Gateway
  • the push server and the UE B (ie, the client B), wherein when the UE A requests to establish a session with the UE B through the WebRTC Server, the UE A will become the calling client mentioned in the foregoing embodiment, and the UE B will become the foregoing.
  • the called client mentioned in the embodiment, the WebRTC Server is the call message processing device mentioned in the foregoing embodiment, and the Open Platform includes but is not limited to the address translation network element and the capability query network element. Specifically, the process of this embodiment The steps can be included:
  • Step S510 UE A download page to connect to the Web Server c which, UE A is a client WebRTC Server, you can log in to WebRTC Server by downloading web pages, when UE A establishes a session with other clients through WebRTC Server request UE A will become the calling client.
  • Step S511 UE A logs in to the WebRTC Server.
  • Step S512 The WebRTC Server allocates a temporary identifier to the UE A, and binds the UE A temporary identifier and the identifier of the UE A and the IP address of the UE A.
  • Step S513 UE A sends a first session request to the WebRTC Server, requesting to establish a session with UE B.
  • the first session request includes an identifier of the UE B.
  • Step S514 The WebRTC Server obtains the IP address of the UE B through the network element according to the identifier of the UE B.
  • the WebRTC Server discovery request carries the identifier of UE B instead of UE B temporary
  • the identifier is processed according to the non-login state of UE B.
  • Step S515 the network element feeds back the IP address of the UE B to the WebRTC Server.
  • Step S5166 the UE B's WebRTC capability is acquired by the UE B.
  • Step S517 UE B confirms that UE B has WebRTC capability. If UE B feedback UE B does not have WebRTC capability, or UE B fails to perform WebRTC capability feedback within a specified time, the following steps are stopped.
  • Step S518, the WebRTC Server sends a push request to the push server.
  • This step is used to enable the push server to push the login indication information to the UE B, and the login indication information is used to instruct the UE B to log in to the WebRTC Server.
  • the push server may push the login indication information in the form of an IP address packet to the UE B where the IP address of the UE B is located.
  • the login indication information may include a webpage address for connecting to the web server, a URL for indicating the WebRTC Server, and a login method 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 UE B connects to the Web Server according to the webpage address in the login indication information.
  • Step S5111 UE B logs in to the WebRTC Server corresponding to the URL address according to the login manner in the login indication information through the webpage.
  • Step S5112 The WebRTC Server allocates a temporary identifier to the UE B, and binds the UE B temporary identifier and the identifier of the UE B and the IP address of the UE B.
  • Step S5113 The WebRTC Server sends a second session request to UE B.
  • the message header of the second session request includes the UE A temporary identifier and the UE B temporary identifier, and the message body of the second session request includes the IP address of the UE A and the IP address of the UE B.
  • Step S5114 UE B sends a session response for responding to the second session request to the WebRTC Server.
  • the message header of the session response includes a UE A temporary identifier and a UE B temporary identifier, and the message body of the session response includes 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 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 the UE B by querying the gateway.
  • the network element fails to query the IP address of UE B, it can query by querying the gateway.
  • Step S5117 The query gateway feeds back the IP address of the UE B to the network element.
  • Step S5119 The network element acquires the WebRTC capability of the UE B through the UE B.
  • Step S5120 UE B feeds back the WebRTC capability of UE B to the network element.
  • Step S5121 The network element feeds back the WebRTC capability of UE B.
  • UE A and UE B are both clients that can log in to the WebRTC Server in a certain manner, where the client identifier can be a universal identifier for distinguishing functions, such as the MSISDN of the client (Mobile Station International ISDN Number) , the mobile station international ISDN number), the client's URL (Uniform Resource Locator), the client's URI (Uniform Resource Identifier), etc., may also be customized non-universal identifiers.
  • MSISDN of the client Mobile Station International ISDN Number
  • the mobile station international ISDN number the client's URL (Uniform Resource Locator), the client's URI (Uniform Resource Identifier), etc.
  • URI Uniform Resource Identifier
  • the login mode information may be an MSISDN identifier login information, a URL identifier login information, and a URI identifier login information.
  • the login indication information includes the MSISDN identifier login information
  • the UE B shall use the MSISDN identifier corresponding manner.
  • the login indication information includes the URL identification login information
  • the UE B should log in to the WebRTC Server in the manner corresponding to the URL identifier.
  • the login indication information includes the URI identification login information
  • the UE B should identify the corresponding manner by the URI. Log in to the WebRTC Server.
  • the query gateway used in 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, a packet data network gateway, etc., the type of the query gateway in the embodiment of the present invention. No restrictions.
  • the capability query network element may further query by querying the gateway.
  • FIG. 6 is a schematic flowchart of a call system according to a second embodiment of the present invention. The figure shows a process of establishing a session between a calling client and a called client in a non-login state in a call system.
  • the call system in the embodiment of the present invention includes UE A (ie, client A), WebRTC Server (Web real-time communication WebRTC server), interworking gateway, Web server (Web server), Open Platform (network element), and GW (Gate Way).
  • UE A ie, client A
  • WebRTC Server Web real-time communication WebRTC server
  • interworking gateway Web server
  • Web server Web server
  • Open Platform network element
  • GW Gate Way
  • Step S610 UE A download page to connect to the Web Server c which, UE A is a client WebRTC Server, you can log in to WebRTC Server by downloading web pages, when UE A establishes a session with other clients through WebRTC Server request UE A will become the calling client.
  • Step S611 UE A logs in to the WebRTC Server.
  • Step S612 The WebRTC Server allocates a temporary identifier to the UE A, and binds the UE A temporary identifier and the identifier of the UE A and the IP address of the UE A.
  • Step S613 UE A sends a first session request to the WebRTC Server, requesting to establish a session with UE B.
  • the first session request includes an identifier of the UE B.
  • Step S614 The WebRTC Server forwards the first session request to the interworking gateway.
  • the WebRTC Server discovery request carries the identifier of the UE B instead of the UE B temporary identifier
  • the first session request is processed according to the non-login state of the UE B.
  • Step S615 The interworking gateway acquires the IP address of the UE B through the network element according to the identifier of the UE B.
  • Step S616 The network element feeds back the IP address of the UE B to the interworking gateway.
  • Step S617 The interworking gateway acquires the WebRTC capability of the UE B through the UE B.
  • Step S619 the interworking gateway sends a push request to the push server.
  • This step is used to enable the push server to push the login indication information to the UE B, and the login indication information is used to instruct the UE B to log in to the WebRTC. Server.
  • the push server may push the login indication information in the form of an IP address packet to the UE B where the IP address of the UE B is located.
  • the login indication information may include a webpage address for connecting to the Web Server, a URL address indicating the WebRTC Server, and a login mode information that the UE B logs 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 the Web Server according to the webpage address in the login indication information.
  • Step S6112 The UE B logs in to the WebRTC Server corresponding to the URL address according to the login manner in the login indication information through the webpage.
  • Step S6113 The WebRTC Server allocates a temporary identifier to the UE B, and binds the UE B temporary identifier and the identifier of the UE B and the IP address of the UE B.
  • Step S6114 The WebRTC Server sends a second session request to UE B.
  • the message header of the second session request includes the UE A temporary identifier and the UE B temporary identifier, and the message body of the second session request includes the IP address of the UE A and the IP address of the UE B.
  • Step S6115 UE B sends a session response for responding to the second session request to the WebRTC Server.
  • the message header of the session response includes a UE A temporary identifier and a UE B temporary identifier, and the message body of the session response includes 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 UE A.
  • the session between UE A and UE B has been successfully established.
  • Step S6117 The network element obtains the IP address of the UE B through the gateway. When the network element fails to query the IP address of UE B, it can query through the gateway.
  • Step S6118 The gateway feeds back the IP address of the UE B to the network element.
  • Step S6119 Obtain the WebRTC capability of the UE B by using the network element.
  • the network element fails to query the WebRTC capability of UE B, it can query through the gateway and query through UE B.
  • Step S6120 The network element acquires the WebRTC capability of the UE B through the UE B.
  • Step S6121 UE B feeds back the WebRTC capability of UE B to the network element.
  • Step S6122 The network element feeds back the WebRTC capability of UE B to the interworking gateway.
  • FIG. 7 is a schematic flowchart of a call system according to a third embodiment of the present invention.
  • the figure shows the process of establishing a session between the calling client and the called client in the non-login state in the calling system.
  • the call system in the embodiment of the present invention includes UE A (ie, client A), WebRTC Server (Webpage real-time communication WebRTC server), Web Server (Web server), Open Platform (network element), push server, SMSC (Short Message Service). Center, short message service center) and UE B (ie, client B), where UE A will become the calling client mentioned in the foregoing embodiment, when UE A requests to establish a session with UE B through the WebRTC Server.
  • the process of an embodiment may include the following steps:
  • Step S710 UE A downloads a webpage to connect to the Web Server.
  • Step S711 UE A logs in to the WebRTC Server.
  • Step S712 The WebRTC Server allocates a temporary identifier to the UE A, and binds the UE A temporary identifier and the identifier of the UE A and the IP address of the UE A.
  • Step S713 UE A sends a first session request to the WebRTC Server, requesting to establish a session with UE B.
  • the first session request includes an identifier of the 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.
  • This step is used to enable the push server to push the login indication information to the UE B, and the login indication information is used to instruct the UE B to log in to the WebRTC Server.
  • the login indication information may include a webpage address for connecting to the Web Server, a URL for indicating the WebRTC Server, and a login method for the UE B to log in to the WebRTC Server.
  • Step S717 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 S719 the UE B connects to the Web Server according to the webpage address in the login indication information.
  • Step S7110 The UE B logs in to the WebRTC Server corresponding to the URL address according to the login manner in the login indication information through the webpage.
  • Step S7111 the WebRTC Server allocates a temporary identifier to the UE B, and binds the UE B temporary.
  • Step S7112 The WebRTC Server sends a second session request to the UE B.
  • Step S7113 UE B sends a session response for responding to the second session request to WebRTC.
  • Step S7114 the WebRTC Server forwards the session response to UE A.
  • the session between UE A and UE B has been successfully established.
  • Step S7115 The WebRTC Server obtains the WebRTC capability of the UE B by using the network element.
  • the network element fails to query the WebRTC capability of UE B, it can query by querying the gateway.
  • Step S7116 The network element acquires the WebRTC capability of the UE B through the UE B.
  • Step S7117 UE B feeds back the WebRTC capability of UE B to the network element.
  • Step S7118 The network element feeds back the WebRTC capability of UE B.
  • the system provided by the embodiment of the present invention can send the login indication information to the UE B in the form of a short message through the SMSC, and the UE B can read the information sent by the SMSC to perform the login operation.
  • FIG. 8 is a schematic flowchart of a call system according to a fourth embodiment of the present invention.
  • the figure shows a process of establishing a session between a calling client and a called client in a non-login state in a call system.
  • the call system in the embodiment of the present invention includes UE A (ie, client A), WebRTC Server (Web real-time communication WebRTC server), interworking gateway, Web server (Web server), Open Platform (network element), push server, SMSC ( Short Message Service Center, and UE B (ie, Client B), where UE A will become the calling client mentioned in the foregoing embodiment when UE A requests to establish a session with UE B through WebRTC Server.
  • UE A ie, client A
  • WebRTC Server Web real-time communication WebRTC server
  • interworking gateway Web server
  • Web server Web server
  • Open Platform network element
  • push server SMSC ( Short Message Service Center
  • UE B ie, Client B
  • the UE B will be the called client mentioned in the foregoing embodiment, and the interworking gateway is the call message processing device mentioned in the foregoing embodiment.
  • the Open Platform includes but is not limited to the address translation network element and the capability query network element. The process of this embodiment may include the following steps:
  • Step S810 UE A downloads a webpage to connect to the Web Server.
  • Step S811 UE A logs in to the WebRTC Server.
  • Step S812 the WebRTC Server allocates a temporary identifier to the UE A, and binds the UE A temporary label. Identifies the identity of UE A and the IP address of UE A.
  • Step S813 UE A sends a first session request to the WebRTC Server, requesting to establish a session with UE B.
  • the first session request includes an identifier of the UE B.
  • Step S814 the WebRTC Server forwards the first session request to the interworking gateway.
  • the WebRTC Server discovery request carries the identifier of the UE B instead of the UE B temporary identifier
  • the first session request is processed according to the non-login state of the UE B.
  • Step S815 The interworking gateway acquires the WebRTC capability of the UE B.
  • Step S817 The interworking gateway sends a push request to the push server. This step is used to enable the push server to push the login indication information to the UE B, and the login indication information is used to instruct the UE B to log in to the WebRTC Server.
  • the login indication information may include a webpage address for connecting to the Web Server, a URL for indicating the WebRTC Server, and a login method 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.
  • Step S8110 UE B connects to the Web Server according to the webpage address in the login indication information.
  • Step S8111 UE B logs in to the webpage according to the login method in the login indication information.
  • the WebRTC Server corresponding to the URL address.
  • Step S8112 - Step S8119 is the same as the foregoing step S7111 - step S7118.
  • the system provided by the embodiment of the present invention can send the login indication information to the UE B in the form of a short message through the SMSC, and the UE B can read the information sent by the SMSC to perform the login operation.
  • 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 processing method of the call message shown in FIG. 1, and is an execution body based on the processing method of the call message shown in FIG. 1.
  • the specific implementation form is as shown in FIG. 9.
  • the call message processing apparatus provided in this embodiment includes: an input device 91 and an output device. 92.
  • the memory 93 and the processor 94 wherein the memory 93 stores a set of program codes, and the processor 94 is configured to call the program code stored in the memory 93 for performing the following operations:
  • the processor 94 performs the sending of the login indication information to the called client corresponding to the called client identifier, including:
  • the processor 94 performs the acquisition of the called client Internet Protocol IP address corresponding to the called client identifier, including:
  • the processor 94 is further configured to: send a WebRTC capability query message.
  • the called client corresponding to the called client identifier receiving the WebRTC capability response information sent by the called client, and the WebRTC capability response information is generated after the called client confirms that the called client has the WebRTC capability;
  • the processor 94 is further configured to perform the following operations: sending the called client WebRTC capability query command to capability query network element, called client The WebRTC capability query instruction carries the called client identifier;
  • the receiving capability queries the WebRTC capability confirmation information sent by the network element.
  • the WebRTC capability confirmation information is that the capability query network element executes the called client.
  • the WebRTC capability query instruction queries the called client to generate the WebRTC capability.
  • the login indication information is not sent to the called client corresponding to the called client identifier.
  • the processor 94 performs the sending of the login indication information to the called client corresponding to the called client identifier, including:
  • the login indication information further includes one or two types of login mode information and a uniform resource locator URL information of the WebRTC server, where the login mode information is used to indicate that the called client logs in according to the login mode information.
  • the WebRTC server, the URL information indicates that the called client logs in to the WebRTC server corresponding to the URL information.
  • the processor 94 is further configured to perform the following operations:
  • the forwarding session After receiving the session response of the called client in response to the second session request, the forwarding session responds to the calling client to establish a session between the called client and the calling client.
  • FIG. 10 is a structural diagram of another called client according to an embodiment of the present invention.
  • the called client provided in this embodiment corresponds to the processing method of the call message shown in FIG. 2, and is an execution body based on the processing method of the call message shown in FIG. 2.
  • the specific implementation is shown in FIG. 10.
  • the called client provided in this embodiment includes: an input device 101, an output device 102, and a memory. 103 and the processor 104, wherein the memory 103 stores a set of program codes, and the processor 104 is configured to call the program code stored in the memory 103 for performing the following operations:
  • the call message processing device receives, by the call message processing device, the login indication information, where the call message processing device comprises any one of a webpage real-time communication WebRTC server and an interworking gateway;
  • the processor 104 before the processor 104 performs the receiving the login indication information, the processor 104 is further configured to perform the following operations:
  • the WebRTC capability response information is sent to the call message processing device.
  • the WebRTC capability response message is not sent to the call message processing device.
  • the processor 104 before the processor 104 performs the receiving the login indication information, the processor 104 is further configured to perform the following operations:
  • the WebRTC capability response information is sent to the login capability query network element, 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;
  • the WebRTC capability response information is not sent to the login capability to query the network element.
  • the login indication information further includes login mode information
  • the processor 104 logs in to the WebRTC server according to the login indication information, including:
  • the login indication information further includes the unification of the WebRTC server.
  • the resource locator URL information, the processor 104 performs login to the webpage according to the login indication information, and the real-time communication WebRTC server includes:
  • the processor 104 is further configured to perform the following operations:
  • the session response is sent 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.
  • the disclosed apparatus and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or modules may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct connection or communication connection shown or discussed may be an indirect connection or communication connection through some interface, device, module or unit, or may be an electrical, mechanical or other form. connection.
  • modules or units described as separate components may or may not be physically separated, and the components displayed as modules or units may or may not be physical modules or units, that is, may be located in one place, or may be distributed to multiple On a network module or unit. Some or all of the modules or units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.
  • each functional module or unit in each embodiment of the present application may be integrated into one processing module or unit, or each module or unit may exist physically separately, or two or more modules or units may be integrated in In a module or unit.
  • the above integrated modules or units can be implemented either in the form of hardware or in the form of software functional units.
  • An integrated module or unit if implemented in the form of a software function module or unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present application is essential or the part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium, including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program code. .

Landscapes

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

Abstract

L'invention concerne un procédé de traitement de messages d'appel, comportant les étapes consistant: lors du traitement d'une première demande de session d'un client appelant, à envoyer des informations d'instruction de connexion à un client appelé faisant l'objet de la première demande de session, de sorte que le client appelé se connecte sur un serveur de communication en temps réel par web (WebRTC) pour établir une session avec le client appelant. Autrement dit, lorsqu'un client WebRTC demandé pour une session n'est pas connecté, un mode de réalisation de la présente invention permet au client WebRTC à l'origine de la demande d'établir une session avec le client WebRTC demandé pour la session.
PCT/CN2014/076317 2014-04-28 2014-04-28 Procédé et dispositif de traitement de messages d'appel WO2015164997A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201480000620.3A CN105379194B (zh) 2014-04-28 2014-04-28 一种呼叫消息的处理方法及装置
PCT/CN2014/076317 WO2015164997A1 (fr) 2014-04-28 2014-04-28 Procédé et dispositif de traitement de messages d'appel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/076317 WO2015164997A1 (fr) 2014-04-28 2014-04-28 Procédé et dispositif de traitement de messages d'appel

Publications (1)

Publication Number Publication Date
WO2015164997A1 true WO2015164997A1 (fr) 2015-11-05

Family

ID=54357966

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/076317 WO2015164997A1 (fr) 2014-04-28 2014-04-28 Procédé et dispositif de traitement de messages d'appel

Country Status (2)

Country Link
CN (1) CN105379194B (fr)
WO (1) WO2015164997A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005463A (zh) * 2006-01-17 2007-07-25 千橡世纪科技发展（北京）有限公司 一种在浏览器网页中向桌面系统发送信息的系统和方法
CN101483537A (zh) * 2009-02-12 2009-07-15 周佺喜 网页即时通讯中实时显示网站用户状态的方法
WO2010060465A1 (fr) * 2008-11-26 2010-06-03 Nokia Siemens Networks Oy Communication en temps réel
CN103404132A (zh) * 2013-03-08 2013-11-20 华为终端有限公司 视频通信方法及家庭终端、家庭服务器

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102347950B (zh) * 2011-09-29 2018-02-06 中兴通讯股份有限公司 电信网络向互联网提供会话服务的方法及系统
CN103051863B (zh) * 2011-10-17 2016-09-14 腾讯科技（深圳）有限公司 一种会话发起方法和系统
US9247062B2 (en) * 2012-06-19 2016-01-26 Twilio, Inc. System and method for queuing a communication session
CN103580986B (zh) * 2012-07-30 2016-12-21 华为终端有限公司 一种实时通信方法、终端设备、实时通信服务器及系统
CN103414835A (zh) * 2013-07-24 2013-11-27 佳都新太科技股份有限公司 一种使用WebRTC技术实现呼叫中心视频坐席的方法
WO2015021650A1 (fr) * 2013-08-16 2015-02-19 华为技术有限公司 Procédé, dispositif et système de transmission pour un flux multimédia
CN103702062A (zh) * 2013-12-27 2014-04-02 Tcl集团股份有限公司 一种音视频通讯方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005463A (zh) * 2006-01-17 2007-07-25 千橡世纪科技发展（北京）有限公司 一种在浏览器网页中向桌面系统发送信息的系统和方法
WO2010060465A1 (fr) * 2008-11-26 2010-06-03 Nokia Siemens Networks Oy Communication en temps réel
CN101483537A (zh) * 2009-02-12 2009-07-15 周佺喜 网页即时通讯中实时显示网站用户状态的方法
CN103404132A (zh) * 2013-03-08 2013-11-20 华为终端有限公司 视频通信方法及家庭终端、家庭服务器

Also Published As

Publication number Publication date
CN105379194A (zh) 2016-03-02
CN105379194B (zh) 2020-02-14

Similar Documents

Publication Publication Date Title
US9781167B2 (en) WebRTC data channel facilitating IMS support of RCS features
RU2288545C2 (ru) Способ и система передачи мультимедийных сообщений
US9130759B2 (en) Capability exchange during an authentication process for an access terminal
CN109495599B (zh) 数据传输方法和系统、电子装置及计算机可读存储介质
EP2863615A1 (fr) Procédé de configuration, système de distribution sélective et dispositif correspondant pour des sessions de distribution sélective
US20160241664A1 (en) Method, device, and system for redirecting data by using service proxy
JP2016500234A (ja) リアルタイム通信におけるブラウザ緊急呼び出し方法、システムおよび移動装置
WO2015000356A1 (fr) Procédé de communication webrtc, et dispositif et système associés
WO2015131487A1 (fr) Procédé et dispositif d'intercommunication pour service de messages courts
KR100805093B1 (ko) 압축된 메시지들을 전송하기 위한 시스템 및 방법
WO2015065210A1 (fr) Accès mobile sécurisé à des ressources dans un réseau privé
WO2012062070A1 (fr) Procédé, système et serveur pour donner en retour l'état d'une extrémité de réception
CN103973648B (zh) 应用数据推送方法、装置及系统
TWI549553B (zh) Communication methods and communication systems
EP3804407B1 (fr) Procédés et noeuds pour faciliter des communications d'ue à ue non ip
WO2016029854A1 (fr) Procédé, dispositif, et système de connexion au réseau sans fil
WO2014117727A1 (fr) Système, appareil et procédé de transfert de supports
EP3107352B1 (fr) Procédé, système et appareil de transfert d'informations
WO2015164997A1 (fr) Procédé et dispositif de traitement de messages d'appel
CN112202780B (zh) 一种基于双套接字的数据传输方法、装置、设备及介质
JP2006005754A (ja) Ｓｉｐ信号変換方法、ｓｉｐ−ａｌｇ装置、ｓｉｐ信号変換プログラム、および記録媒体
JP6807952B2 (ja) 通信サービスを端末通信装置に提供する通信ネットワークを決定する方法及び装置
CN108337215A (zh) 一种文件传输方法及系统、装置、电子设备
WO2009065362A1 (fr) Procédé, système et dispositif pour le routage d'un message selon un protocole sip dans un réseau traditionnel
CN112913206A (zh) 无线电通信

Legal Events

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

Ref document number: 14890486

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14890486

Country of ref document: EP

Kind code of ref document: A1