CN118803584A - A request processing method, device, equipment and readable storage medium - Google Patents

Abstract

The present application discloses a request processing method, device, equipment and readable storage medium, which relates to the field of communication technology, to establish a new call between an application side and a terminal. The method includes: receiving a first message, wherein the first message is used to request to establish a new call between the application side and the terminal; and establishing a new call between the application side and the terminal according to the first message. The embodiment of the present application can establish a new call between the application side and the terminal.

Description

A request processing method, device, equipment and readable storage medium

Technical Field

The present application relates to the field of communication technology, and in particular to a request processing method, device, equipment and readable storage medium.

Background Art

5G New Call is an ultra-clear voice call, video call service and related value-added services based on the 5G network, such as 5G ultra-clear video call, 5G video customer service, barrier-free communication function, screen sharing, remote collaboration, AR fun call and other functions, which can provide users with visual, multimedia, and highly perceived ultra-clear call experience. 5G New Call is based on the IMS (IP Multimedia Subsystem) Data Channel (DC for short) technology vision, and adds DC negotiation during the SDP (Session Description Protocol) negotiation process. DC can exist simultaneously with the call audio and video streams and provide basic capabilities for data interaction. The existing specifications define the main transmission content in the IMS Data Channel as Web Page (webpage) and Script (script) to solve the problem of lack of call interaction service capabilities in the IMS network. The new call network system architecture supports how to implement the process of establishing a new call between two terminals in the IMS network.

Existing technical solutions, such as Skype, generally use a gateway to convert calls into their own application private protocols, or use a Web Real-Time Communication (Webrtc) solution, using the Session Initialization Protocol (SIP)/Webrtc conversion gateway to achieve intercommunication with the application side. Existing calls supported with the application side are generally ordinary audio calls, or support video calls, but do not support the application side (such as web pages, APPs, third-party application servers that do not support IMS, etc.) to establish new calls with the terminal.

Summary of the invention

Embodiments of the present application provide a request processing method, apparatus, device, and readable storage medium to establish a new call between an application side and a terminal.

In a first aspect, an embodiment of the present application provides a request processing method, which is applied to a network function, including:

Receiving a first message, wherein the first message is used to request to establish a new call between the application side and the terminal;

A new call is established between the application side and the terminal according to the first message.

Optionally, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the method further includes:

Send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the method further includes:

Sending service configuration information of the new call to the first network element; receiving a third message sent by the first network element;

or,

According to the subscription information of the application side, information of the candidate mini-programs used by the application side in this new call is determined.

Optionally, establishing a new call between the application side and the terminal according to the first message includes:

An INVITE message is sent to an IP Multimedia Subsystem (IMS) used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal.

Optionally, the INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS;

Session Description Protocol (SDP) information for this new call;

ID of the called party.

Optionally, the method further includes:

receiving a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information;

Generate first information according to the fourth message;

Sending a fifth message to the application side, wherein the fifth message includes the first information;

Execute the applet list and/or applet download process.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the first message is a first message sent by an IMS used for a new call, and the first message includes SDP information of the new call.

Optionally, establishing a new call between the application side and the terminal according to the first message includes:

generating second information according to the first message;

Sending a fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Receive a sixth message sent by the application side, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the method further includes:

Receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the method further includes:

Send the service configuration information of the new call to the first network element.

Optionally, the method further includes:

Notify the home network of data channel related events and make media reservations;

Sending an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

Execute the applet list and/or applet download process.

Optionally, the method further includes:

Sending a call establishment process event to the application side.

Optionally, the method further includes:

receiving a fifteenth message, wherein the fifteenth message is used to request to establish an application data channel between the application side and the terminal;

An application data channel is established between the application side and the terminal according to the fifteenth message.

Optionally, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address;

Session ID.

Optionally, the method further includes:

A ninth message is sent to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, establishing an application data channel between the application side and the terminal according to the fifteenth message includes:

A re-INVITE message is sent to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal.

Optionally, the re-INVITE message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information for this new call;

Session ID.

Optionally, the routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the method further includes:

receiving a tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

generating third information according to the tenth message;

Sending an eleventh message to the application side, wherein the eleventh message includes the third information and is used to indicate a result of establishing the application data channel;

An application data channel is established with the terminal.

Optionally, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes SDP information of the new call.

Optionally, establishing an application data channel between the application side and the terminal according to the fifteenth message includes:

Generate fourth information according to the fifteenth message;

Sending a sixteenth message to the application side, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message sent by the application side is received, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the method further includes:

receiving a seventeenth message sent by the application side, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

Mapping the seventeenth message into a SIP BYE, and sending the SIP BYE to the terminal;

A response sent by the terminal is received, the response is mapped into a response, and the response is sent to the application side.

Optionally, the method further includes:

receiving a Session Initialization Protocol (SIP) BYE sent by the terminal, mapping the SIP BYE into a fifth message, and sending the fifth message to the application side;

A response sent by the application side is received, the response is mapped into a SIP response, and the SIP response is sent to the terminal.

Optionally, the method further includes:

receiving an eighteenth message sent by the application side, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A thirteenth message is sent to the application side, wherein the thirteenth message is used to indicate a query result of the new call.

In a second aspect, the embodiment of the present application further provides a request processing method, which is applied to the application side, including:

A first message is sent to a network function, wherein the first message is used to request establishment of a new call between the application side and the terminal.

Optionally, the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the method further includes:

A second message sent by the network function is received, wherein the second message is used to indicate whether the first message is successful.

Optionally, the method further includes:

A fifth message sent by the network function is received, wherein the fifth message includes the first information.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the method further includes:

Receive a call establishment process event sent by the network function.

Optionally, the method further includes:

A fifteenth message is sent to the network function, wherein the fifteenth message is used to request establishment of an application data channel between the application side and the terminal.

Optionally, the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the method further includes:

A ninth message sent by the network function is received, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the method further includes:

An eleventh message sent by the network function is received, wherein the eleventh message is used to indicate a result of establishing the application data channel.

Optionally, the method further includes:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the method further includes:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the method further includes:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the method further includes:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In a third aspect, an embodiment of the present application provides a request processing method, which is applied to an application side, including:

receiving a fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Send a sixth message to the network function, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the method further includes:

Sending a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the method further includes:

Receive a call establishment process event sent by the network function.

Optionally, the method further includes:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the method further includes:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the method further includes:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the method further includes:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In a fourth aspect, an embodiment of the present application further provides a request processing method, which is applied to an IMS used for a new call, comprising:

A first message is sent to a network function, wherein the first message is used to request establishment of a new call between the terminal and the application side.

Optionally, the first message includes SDP information of the new call.

Optionally, the method further includes:

An eighth message sent by the network function is received, wherein the eighth message includes SDP information.

In a fifth aspect, an embodiment of the present application further provides a request processing method, which is applied to a terminal, comprising:

Sending an INVITE request to an IMS used for the new call, whereby the IMS used for the new call sends a first message to a network function;

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the method further includes:

Receive the SIP BYE sent by the network function, and send a response to the network function.

Optionally, the method further includes:

Send a SIP BYE to the network function, and receive a SIP response sent by the network function.

In a sixth aspect, an embodiment of the present application further provides a request processing device, applied to a network function, including:

A first receiving module, configured to receive a first message, wherein the first message is used to request to establish a new call between the application side and the terminal;

The first processing module is used to establish a new call between the application side and the terminal according to the first message.

Optionally, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The first sending module is used to send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the device further comprises:

A second sending module, configured to send service configuration information of the new call to the first network element; and receive a third message sent by the first network element;

or,

The second processing module is used to determine the information of the candidate mini-programs used by the application side in this new call according to the subscription information of the application side.

Optionally, the first processing module is further used for:

An invitation INVITE message is sent to the IP Multimedia Subsystem IMS used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal.

Optionally, the INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS;

Session Description Protocol (SDP) information for this new call;

ID of the called party.

Optionally, the device further comprises:

A second receiving module, configured to receive a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information;

A first generating module, configured to generate first information according to the fourth message;

a third sending module, configured to send a fifth message to the application side, wherein the fifth message includes the first information;

The third processing module is used to execute the mini-program list and/or mini-program download process.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the first message is a first message sent by an IMS used for a new call, and the first message includes SDP information of the new call.

Optionally, the first processing module is further used for:

generating second information according to the first message;

Sending a fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Receive a sixth message sent by the application side, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the device further comprises:

The third receiving module is used to receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The fourth sending module is used to send the service configuration information of the new call to the first network element.

Optionally, the device further comprises:

A fifth processing module, configured to perform data channel related event notification and media reservation with the home network;

a fifth sending module, configured to send an eighth message to the IMS used for the new call, wherein the eighth message includes SDP information;

The sixth processing module is used to execute the mini-program list and/or mini-program download process.

Optionally, the device further comprises:

The fifth sending module is used to send a call establishment process event to the application side.

Optionally, the device further comprises:

a fourth receiving module, configured to receive a fifteenth message, wherein the fifteenth message is used to request establishment of an application data channel between the application side and the terminal;

An eighth processing module is used to establish an application data channel between the application side and the terminal according to the fifteenth message.

Optionally, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address;

Session ID.

Optionally, the device further comprises:

The sixth sending module is used to send a ninth message to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the eighth processing module is further used for:

A re-INVITE message is sent to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal.

Optionally, the re-INVITE message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information for this new call;

Session ID.

Optionally, the routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the device further comprises:

a fifth receiving module, configured to receive a tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

A second generating module, used to generate third information according to the tenth message;

a seventh sending module, configured to send an eleventh message to the application side, wherein the eleventh message includes the third information and is configured to indicate a result of establishing the application data channel;

The ninth processing module is used to establish an application data channel with the terminal.

Optionally, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes SDP information of the new call.

Optionally, the eighth processing module is further used for:

Generate fourth information according to the fifteenth message;

Sending a sixteenth message to the application side, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message sent by the application side is received, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a sixth receiving module, configured to receive a seventeenth message sent by the application side, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A first mapping module, configured to map the seventeenth message into a SIP BYE, and send the SIP BYE to the terminal;

The seventh receiving module is used to receive the response sent by the terminal, map the response into a response, and send the response to the application side.

Optionally, the device further comprises:

an eighth receiving module, configured to receive the SIP BYE sent by the terminal, map the SIP BYE into a fifth message, and send the fifth message to the application side;

The second mapping module is used to receive the response sent by the application side, map the response into a SIP response, and send the SIP response to the terminal.

Optionally, the device further comprises:

a ninth receiving module, configured to receive an eighteenth message sent by the application side, wherein the eighteenth message is used to query a new call between the application side and the terminal;

An eighth sending module is used to send a thirteenth message to the application side, wherein the thirteenth message is used to indicate the query result of the new call.

In a seventh aspect, an embodiment of the present application further provides a request processing device, which is applied to an application side, including:

The first sending module is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the application side and the terminal.

Optionally, the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The first receiving module is used to receive a second message sent by the network function, wherein the second message is used to indicate whether the first message is successful.

Optionally, the device further comprises:

The second receiving module is used to receive a fifth message sent by the network function, wherein the fifth message includes the first information.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the device further comprises:

The third receiving module is used to receive a call establishment process event sent by the network function.

Optionally, the device further comprises:

The second sending module is used to send a fifteenth message to the network function, wherein the fifteenth message is used to request to establish an application data channel between the application side and the terminal.

Optionally, the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The fourth receiving module is used to receive a ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the device further comprises:

A fifth receiving module is used to receive an eleventh message sent by the network function, wherein the eleventh message is used to indicate a result of establishing the application data channel.

Optionally, the device further comprises:

a sixth receiving module, configured to receive a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

The third sending module is used to send a twelfth message to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a fourth sending module, configured to send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

The seventh receiving module is used to receive a response sent by the network function.

An eighth receiving module is used to receive a fifth message sent by the network function and send a response to the network function.

a fifth sending module, configured to send an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A ninth receiving module is used to receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In an eighth aspect, an embodiment of the present application further provides a request processing device, which is applied to an application side, including:

A first receiving module, configured to receive a fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes second information;

The first sending module is used to send a sixth message to the network function, wherein the sixth message is used to indicate the result of establishing the new call.

Optionally, the device may further include:

The second sending module is used to send a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the device further comprises:

The second receiving module is used to receive a call establishment process event sent by the network function.

Optionally, the device further comprises:

A third receiving module, configured to receive a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

The third sending module is used to send a twelfth message to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a fifth sending module, configured to send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

The fourth receiving module is used to receive a response sent by the network function.

Optionally, the device further comprises:

A fifth receiving module receives a fifth message sent by the network function and sends a response to the network function.

Optionally, the device further comprises:

a sixth sending module, configured to send an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A sixth receiving module receives a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In a ninth aspect, an embodiment of the present application further provides a request processing device, which is applied to an IMS used for a new call, including:

The first sending module is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the first message includes SDP information of the new call.

Optionally, the device further comprises:

The first receiving module is used to receive an eighth message sent by the network function, wherein the eighth message includes SDP information.

In a tenth aspect, an embodiment of the present application further provides a request processing device, applied to a terminal, comprising:

A first sending module, configured to send an INVITE request to an IMS used for a new call, and for the IMS used for the new call to send a first message to a network function;

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the device further comprises:

The first receiving module is used to receive the SIP BYE sent by the network function and send a response to the network function.

Optionally, the device further comprises:

The second sending module is used to send a SIP BYE to the network function and receive a SIP response sent by the network function.

In an eleventh aspect, an embodiment of the present application further provides a request processing device, applied to a network function, comprising: a processor and a transceiver;

The transceiver is used to receive a first message, wherein the first message is used to request to establish a new call between the application side and the terminal;

The processor is used to establish a new call between the application side and the terminal according to the first message.

Optionally, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver is further used for:

Send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the processor is further configured to:

Sending service configuration information of the new call to the first network element; receiving a third message sent by the first network element;

or,

According to the subscription information of the application side, information of the candidate mini-programs used by the application side in this new call is determined.

Optionally, the processor is further configured to:

An invitation INVITE message is sent to the IP Multimedia Subsystem IMS used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal.

Optionally, the INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS;

Session Description Protocol (SDP) information for this new call;

ID of the called party.

Optionally, the processor is further configured to:

receiving a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information;

Generate first information according to the fourth message;

Sending a fifth message to the application side, wherein the fifth message includes the first information;

Execute the applet list and/or applet download process.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the first message is a first message sent by an IMS used for a new call, and the first message includes SDP information of the new call.

Optionally, the processor is further configured to:

generating second information according to the first message;

Sending a fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Receive a sixth message sent by the application side, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the transceiver is further used for:

Receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver is further used for:

Send the service configuration information of the new call to the first network element.

Optionally, the processor is further configured to:

Notify the home network of data channel related events and make media reservations;

Sending an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

Execute the applet list and/or applet download process.

Optionally, the transceiver is further used for:

Sending a call establishment process event to the application side.

Optionally, the processor is further configured to:

receiving a fifteenth message, wherein the fifteenth message is used to request to establish an application data channel between the application side and the terminal;

An application data channel is established between the application side and the terminal according to the fifteenth message.

Optionally, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address;

Session ID.

Optionally, the transceiver is further used for:

A ninth message is sent to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the processor is further configured to:

A re-INVITE message is sent to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal.

Optionally, the re-INVITE message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information for this new call;

Session ID.

Optionally, the routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the transceiver is further used for:

receiving a tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

generating third information according to the tenth message;

Sending an eleventh message to the application side, wherein the eleventh message includes the third information and is used to indicate a result of establishing the application data channel;

An application data channel is established with the terminal.

Optionally, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes SDP information of the new call.

Optionally, the processor is further configured to:

Generate fourth information according to the fifteenth message;

Sending a sixteenth message to the application side, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message sent by the application side is received, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver is further used for:

receiving a seventeenth message sent by the application side, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

Mapping the seventeenth message into a SIP BYE, and sending the SIP BYE to the terminal;

A response sent by the terminal is received, the response is mapped into a response, and the response is sent to the application side.

Optionally, the transceiver is further used for:

receiving a SIP BYE sent by the terminal, mapping the SIP BYE into a fifth message, and sending the fifth message to the application side;

A response sent by the application side is received, the response is mapped into a SIP response, and the SIP response is sent to the terminal.

Optionally, the transceiver is further used for:

receiving an eighteenth message sent by the application side, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A thirteenth message is sent to the application side, wherein the thirteenth message is used to indicate a query result of the new call.

In a twelfth aspect, an embodiment of the present application further provides a request processing device, applied to an application side, comprising: a processor and a transceiver;

The transceiver is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the application side and the terminal.

Optionally, the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver is further used for:

A second message sent by the network function is received, wherein the second message is used to indicate whether the first message is successful.

Optionally, the transceiver is further used for:

A fifth message sent by the network function is received, wherein the fifth message includes the first information.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the transceiver is further used for:

Receive a call establishment process event sent by the network function.

Optionally, the transceiver is further used for:

A fifteenth message is sent to the network function, wherein the fifteenth message is used to request establishment of an application data channel between the application side and the terminal.

Optionally, the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver is further used for:

A ninth message sent by the network function is received, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the transceiver is further used for:

An eleventh message sent by the network function is received, wherein the eleventh message is used to indicate a result of establishing the application data channel.

Optionally, the transceiver is further used for:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver is further used for:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the transceiver is further used for:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the transceiver is further used for:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In a thirteenth aspect, an embodiment of the present application further provides a request processing device, applied to an application side, comprising: a processor and a transceiver;

The transceiver is used to receive a fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information; and send a sixth message to the network function, wherein the sixth message is used to indicate the result of establishing this new call.

Optionally, the transceiver is further used for:

Sending a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the transceiver is further used for:

Receive a call establishment process event sent by the network function.

Optionally, the transceiver is further used for:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver is further used for:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the transceiver is further used for:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the transceiver is further used for:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

In a fourteenth aspect, an embodiment of the present application further provides a request processing device, applied to an IMS used for a new call, comprising: a processor and a transceiver;

The transceiver is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the first message includes SDP information of the new call.

Optionally, the transceiver is further used for:

An eighth message sent by the network function is received, wherein the eighth message includes SDP information.

In a fifteenth aspect, an embodiment of the present application further provides a request processing device, applied to a terminal, comprising: a processor and a transceiver;

The transceiver is used to send an INVITE request to the IMS used for the new call, and the IMS used for the new call sends a first message to the network function;

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the transceiver is further used for:

Receive the SIP BYE sent by the network function, and send a response to the network function.

Optionally, the transceiver is further used for:

Send a SIP BYE to the network function, and receive a SIP response sent by the network function.

In the sixteenth aspect, an embodiment of the present application further provides a communication device, comprising: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor implements the steps in the request processing method as described above when executing the program.

In the seventeenth aspect, an embodiment of the present application further provides a readable storage medium, on which a program is stored, and when the program is executed by a processor, the steps in the request processing method as described above are implemented.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a system architecture diagram of an embodiment of the present application;

FIG2 is a flowchart of a request processing method provided in an embodiment of the present application;

FIG3 is a second flowchart of the request processing method provided in an embodiment of the present application;

FIG4 is a third flowchart of the request processing method provided in an embodiment of the present application;

FIG5 is a fourth flowchart of the request processing method provided in an embodiment of the present application;

FIG6 is a fifth flowchart of the request processing method provided in an embodiment of the present application;

FIG7 is a sixth flowchart of the request processing method provided in an embodiment of the present application;

FIG8 is a flowchart of the request processing method provided in an embodiment of the present application;

FIG9 is a flowchart of an eighth request processing method provided in an embodiment of the present application;

FIG10 is a flowchart of a request processing method according to an embodiment of the present application;

FIG11 is a flowchart of a request processing method according to an embodiment of the present application;

FIG12 is a structural diagram of a request processing device provided in an embodiment of the present application;

FIG13 is a second structural diagram of the request processing device provided in an embodiment of the present application;

FIG14 is a third structural diagram of the request processing device provided in an embodiment of the present application;

FIG15 is a fourth structural diagram of the request processing device provided in an embodiment of the present application;

FIG16 is a fifth structural diagram of a request processing device provided in an embodiment of the present application;

FIG17 is a sixth structural diagram of the request processing device provided in an embodiment of the present application;

FIG18 is a seventh structural diagram of a request processing device provided in an embodiment of the present application;

FIG19 is an eighth structural diagram of a request processing device provided in an embodiment of the present application;

FIG20 is a ninth structural diagram of a request processing device provided in an embodiment of the present application;

FIG. 21 is the tenth structural diagram of the request processing device provided in an embodiment of the present application.

DETAILED DESCRIPTION

In the embodiments of the present application, the term "and/or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects before and after are in an "or" relationship.

In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

See Figure 1, which is a schematic diagram of the system architecture supporting the 5G new call third-party call function in an embodiment of the present application.

This architecture is based on the international standard 5G new call system architecture. The newly added network function (for example, it can be called the 5G new call enabling layer (eMMtel Enabler)) between third-party applications or vertical industries and the 5G new call system is connected to the interface between the 5G new call system and the application server (DC Application Server) (including the signaling-related interface DC3, namely N33, and DC4, and media-related interfaces MDC2 and MDC3 exposed through the network exposure function (NEF). Through network function processing, the network element function-level interface exposed by the above interface is encapsulated as a business application-level interface, and exposed to third-party applications or vertical industries through the network function capability exposure interface (eMMTel-2). At the same time, the network function can integrate the applet management function and connect to DCSF through the DC5 interface.

In the embodiment of the present application, the network function may be an independent device, or a module or unit set in a certain device, which may be an IMS AS (Application Service) or an AF (Application Function) in a 5G network. In addition, the network function may access the new call IMS network as an application server or as a terminal.

The network functions may include the following functions (not limited to):

1) Mini Program Management: It is used by mini program developers to upload and download new call mini programs, and has the functions of storing and managing mini programs.

2) Session/media management: As a related communication terminal of 5G new call, it is used to terminate the 5G new call session and media sent to the application side, and produce corresponding API requests/responses based on the 5G new call session and media, or initiate the 5G new call session and media to the terminal side based on the API requests of third-party applications or vertical industries. At the same time, it maintains the session-related status and the correspondence between the session and the network function capability exposure request/response, allocates and maintains the routable identifiers of third-party applications or vertical industries in IMS, and maintains the mapping relationship between the user identifiers of third-party applications or vertical industries and the routable identifiers in IMS.

3) Call profile management: Based on the specific session information of a certain type of session (such as a specific session, or a session related to each user, etc.), the relevant information of the mini-program that can be used in this specific session is issued.

4) Interface encapsulation and conversion: used for the encapsulation and conversion between new call-related sessions and media and network function capability open APIs on the IMS side, and can also support the encapsulation and conversion of other application layer capabilities.

5) Capability management: used to manage network functional capabilities, including related capability discovery, capability call authentication and authorization, etc.

6) Data channel agent: As a data channel agent, it establishes data channels between third-party applications or vertical industry users and the Data Channel Signaling Function (DCSF)/Data Channel Media Function (DCMF)/terminal.

Referring to FIG. 2 , FIG. 2 is a flow chart of a request processing method in an embodiment of the present application, which is applied to a network function and includes:

Step 201: Receive a first message, wherein the first message is used to request to establish a new call between the application side and the terminal.

In the embodiment of the present application, the new call is an upgrade of the call service. It is based on audio and video calls and combines artificial intelligence (AI) technology, extended reality (XR) technology, media processing technology, etc. to provide users with a series of high-definition, intelligent, and interactive innovative call services.

New call services are divided into two categories. One is a value-added service based on the new air interface voice bearer (VoNR)/long-term evolution voice bearer (VoLTE) video call, which provides services for users of VoLTE and VoNR video call terminals, bringing users a "visualized" and "intelligent" call experience, such as intelligent translation and other services. The other is a value-added service based on IMSDC technology, which provides services for 5G new call terminal users. Users can interact with the other party in real time through the new call applet, bringing users an "interactive" call experience.

In practical applications, the new call can be called enhanced call, real-time communication, next generation real-time communication (Next Generation-Real Time Communication, NG_RTC or NGRTC), enhanced multimedia telephony (enhanced multimedia telephony, eMMTel), etc.

Step 202: Establish a new call between the application side and the terminal according to the first message.

In the embodiment of the present application, the application side (third-party applications or vertical industry users (such as APP, application servers, web pages, enterprise user-level switches (Private Branch eXchange, IPPBX) and other devices), third-party application servers that do not support IMS) or the terminal side can actively initiate the process of establishing a new call.

1. Application side actively initiates

In this case, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call (which may be a private identifier, etc.);

Callee identification (such as telephone number, etc.);

whether to use the new call capability;

The service configuration information of this new call (also called call profile, such as the list of mini-programs that can be used for this call or subsequent calls of the same type);

Media information for this new call (e.g., the receiving address ports of the audio, video, and data channels planned for this call, etc.);

Call event notification address (used for various event notifications related to call establishment on the application side).

Optionally, the network function may also send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the network function may also send the service configuration information of the new call to the first network element (such as DCSF) and receive a third message sent by the first network element. The response may include the call profile setting result, a list of successfully set mini-programs, etc. DCSF may also be called a new call media capability platform, or may be a part of the call AS. Alternatively, the network function may also determine the information of the candidate mini-programs on the application side in the new call based on the subscription information on the application side, that is, the information of the mini-programs that can be selected for use in subsequent processes.

In this case, the network function may send an INVITE message to the IMS used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal. The INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS (such as a phone number, a routable third-party ID, etc.);

SDP information for this new call;

ID of the called party.

The routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first correspondence, and the first correspondence is a correspondence between the identifier of the application side and the routable identifier in the IMS used for the new call. The routable identifier in the IMS for the new call by the application side can be allocated by the network function, such as randomly selected from a number pool of the network function, or the network function generates a routable third-party ID according to a specific algorithm.

Among them, the SDP information of this new call can be generated by the network function according to the media information such as the audio, video and data channel receiving address port to be used in this call plan, and the SDP information can be an SDP offer.

Optionally, the network function may also receive a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information. The fourth message may be 200OK, etc., and the SDP information may be SDP answer. The network function generates first information based on the fourth message, and sends a fifth message to the application side, wherein the fifth message includes the first information. The first information may be an application programming interface (API) or a capability exposure interface, or may be implemented using other protocols. Afterwards, the network function may execute a mini-program list and/or mini-program download process.

The first information includes one or more of the following:

The identifier of the application side in this new call (which may be a private identifier, etc.);

Callee identification (such as telephone number, etc.);

whether to use the new call capability;

Service configuration information for this new call (such as a list of mini-programs that can be used for this call or subsequent calls of the same type);

Media information of this new call (receiving address and port of audio, video and data channels of called terminal A of this call, etc.);

Session ID.

2. Terminal side actively initiates

In this case, the terminal side executes the standard new call establishment process. The initial INVITE request sent by the terminal to the IMS used for the new call (also called the new call IMS) contains an SDP offer generated according to media information such as the receiving address port of the audio, video and data channels planned to be used in this session. In this case, the IMS used for the new call establishes a new call according to the INVITE request. Among them, the first message is the first message sent by the IMS used for the new call, and the first message includes the SDP information of this new call, such as the SDP offer.

When establishing a new call, the network function generates the second information according to the first message, and sends the fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information. Afterwards, the network function may receive the sixth message sent by the application side, wherein the sixth message is used to indicate the result of establishing the new call.

Optionally, the network function may also receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

The second information may be an API or a capability exposure interface, or may be implemented using other protocols, including one or more of the following:

Identification of the calling terminal (such as telephone number, etc.);

The identifier of the application side in this new call (an identifier that can be routed in IMS, such as a telephone number, etc.);

whether to use the new call capability;

Media information of this new call (media information such as the audio, video and data channel receiving address port of the calling terminal of this call).

The sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call (e.g., a list of mini-programs available for number A, or a list of mini-programs available for a certain type of call, such as a list of mini-programs available for caller A to 10086, etc.);

Media information for this new call;

Call event notification address.

Optionally, the network function may also send the service configuration information of the new call to the first network element (such as DSCF).

Optionally, the network function may also perform data channel related event notification and media reservation with the home network, and send an eighth message to the IMS used for the new call, wherein the eighth message includes SDP information, such as SDP answer. Afterwards, the network function executes the applet list and/or applet download process.

In the above two methods, the network function can send call establishment process events to the application side, such as the called party's 18x ringing information.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

Optionally, based on the above embodiment, the network function may further establish an application data channel (Application Data Channel, ADC) between the application side and the terminal. The network function may receive a fifteenth message, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal. Afterwards, the network function may establish an application data channel between the application side and the terminal according to the fifteenth message.

Similarly, the establishment of the ADC may be initiated by the application side or by the terminal side.

1. The application side initiates the establishment of a new call ADC

In this case, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call (which may be a private identifier, etc.);

Callee identification (such as telephone number, etc.);

whether to use the new call capability;

Service configuration information for this new call (such as a list of mini-programs that can be used for this call or subsequent calls of the same type);

Media information for this new call (such as the audio, video, and data channel receiving address ports planned for this call);

Call event notification address (used for notification of various events related to call establishment on the application side);

Session ID.

Optionally, the network function may also send a ninth message to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

In the process of initiating the establishment of ADC on the application side, the network function may send a re-INVITE message to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal. The re-INVITE message includes one or more of the following:

The routable identifier (such as a phone number, a routable third-party ID, etc.) in the IMS used by the application side for the new call;

The SDP information of this new call, such as SPP offer, is generated based on the media information such as the audio, video and data channel receiving address ports that the data channel of this application plans to use;

Session ID.

The routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the network function may also receive a tenth message (such as 200OK) sent by the IMS used for the new call, wherein the tenth message includes SDP information (such as SDP answer). The network function may generate third information based on the tenth message, and send an eleventh message to the application side, wherein the eleventh message includes the third information, which is used to indicate the result of establishing the application data channel and establish the application data channel with the terminal.

The third information may be an API or a capability exposure interface, or may be implemented using other protocols.

2. The process of establishing ADC initiated by the terminal

In this process, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes the SDP information of the new call (such as the SDP offer generated according to the media information such as the audio, video and data channel receiving address port planned to be used by the application data channel carried in the application data channel request). When establishing the ADC between the application side and the terminal according to the fifteenth message, the network function generates the fourth information according to the fifteenth message, sends the sixteenth message to the application side, wherein the sixteenth message is used to establish the application data channel between the terminal and the application side and includes the fourth information, and receives the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

The fourth information may be an API or a capability exposure interface, or may be implemented using other protocols, including one or more of the following:

The identifier of the application side in this new call (which may be a private identifier, etc.);

Callee identification (such as telephone number, etc.);

Media information for this new call (media information such as the audio, video, and data channel receiving address ports planned to be used by the data channel for this application);

Call event notification address (used for various event notifications related to call establishment on the application side).

The twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call (such as a telephone number, a routable application side ID, etc.);

SDP information, such as SDP answer, is generated based on the media information such as the audio, video and data channel receiving address ports planned to be used by the application data channel carried in the application data channel request.

In the embodiment of the present application, the application side or the network side may also terminate the new call.

When the application side terminates the new call, the network function receives the seventeenth message sent by the application side, wherein the seventeenth message is used to terminate the new call between the application side and the terminal, and may include a session identifier (Session ID) to be terminated. The network function maps the seventeenth message to a SIP BYE, sends the SIP BYE to the terminal, receives a response sent by the terminal, maps the response to a response, and sends the response to the application side.

When the terminal side terminates the new call, the network function receives the SIP BYE sent by the terminal, maps the SIP BYE into a fifth message, and sends the fifth message to the application side. Afterwards, the network function receives the response sent by the application side, maps the response into a SIP response, and sends the SIP response to the terminal.

In the embodiment of the present application, the network function may also receive an eighteenth message sent by the application side, wherein the eighteenth message is used to query the new call between the application side and the terminal. Afterwards, the network function sends a thirteenth message to the application side, wherein the thirteenth message is used to indicate the query result of the new call. For example, the response may include the query result of the new call session (success, failure, etc., if failure includes the reason for failure), the calling parties of the new call, a list of available applets, call establishment time, and other contents.

Referring to FIG. 3 , FIG. 3 is a flow chart of a request processing method in an embodiment of the present application, which is applied to the application side and includes:

Step 301: Send a first message to a network function, wherein the first message is used to request to establish a new call between the application side and the terminal. The meaning and explanation of the first message may refer to the description of the above method embodiment.

Optionally, the application side may also receive a second message sent by the network function, wherein the second message is used to indicate whether the first message is successful.

Optionally, the application side may also receive a fifth message sent by the network function, wherein the fifth message includes the first information. The meaning and interpretation of the first information may refer to the description of the aforementioned method embodiment.

Optionally, the application side may also receive a call establishment process event sent by the network function.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

Optionally, based on the above embodiment, in the process of the application side actively initiating the establishment of an ADC between the application side and the terminal, the application side may also send a fifteenth message to the network function, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal. The meaning and interpretation of the fifteenth message may refer to the description of the aforementioned method embodiment. Optionally, the application side may also receive a ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the application side may also receive an eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of establishing the application data channel.

Optionally, based on the above embodiment, in the process of the terminal side actively initiating the establishment of an ADC with the application side, the application side may also receive a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information. The application side may also send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the establishment of the data channel.

The fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

The twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

For more explanations about the fourth information and the twelfth message, please refer to the description of the aforementioned method embodiment.

Optionally, the application side may also initiate termination of the new call. Specifically, the application side may send a seventeenth message to the network function, wherein the seventeenth message is used to terminate the new call between the application side and the terminal, and the application side receives a response sent by the network function.

Optionally, the terminal may also initiate termination of the new call. Specifically, in this process, the application side receives the fifth message sent by the network function, and sends a response to the network function.

Optionally, the application side may further send an eighteenth message to the network function, wherein the eighteenth message is used to query the new call between the application side and the terminal. Afterwards, the application side may receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

Referring to FIG. 4 , FIG. 4 is a flow chart of a request processing method in an embodiment of the present application, which is applied to the application side and includes:

Step 401: Receive a fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes second information.

The second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

For more explanation about the second information, please refer to the description of the aforementioned method embodiment.

Step 402: Send a sixth message to the network function, where the sixth message is used to indicate the result of establishing the new call.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

Optionally, the application side may also receive an eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of establishing the application data channel.

Optionally, based on the above embodiment, the application side may further send a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful. The application side may also receive a call establishment process event sent by the network function.

Optionally, based on the above embodiment, the application side may also receive a sixteenth message sent by the network function during the process of establishing a new call initiated by the terminal, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information. The application side may send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of establishing the data channel.

The fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

The twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, in the process of terminating a new call initiated by the application side, the application side may send a seventeenth message to the network function, wherein the seventeenth message is used to terminate the new call between the application side and the terminal, and receive a response sent by the network function.

Optionally, during the process of terminating a new call initiated by the terminal, the application side may receive the fifth message sent by the network function and send a response to the network function.

Optionally, the application side may also send an eighteenth message to the network function, wherein the eighteenth message is used to query the new call between the application side and the terminal, and receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

Referring to FIG. 5 , FIG. 5 is a flow chart of a request processing method in an embodiment of the present application, which is applied to an IMS used for a new call, and includes:

Step 501: Send a first message to a network function, wherein the first message is used to request to establish a new call between the terminal and the application side. The first message includes SDP information of the new call. For an explanation of the SDP information, refer to the description of the above embodiment.

Optionally, the IMS may also receive an eighth message sent by the network function, wherein the eighth message includes SDP information.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

Referring to FIG. 6 , FIG. 6 is a flow chart of a request processing method in an embodiment of the present application, which is applied to a terminal and includes:

Step 601: Send an INVITE request to an IMS used for a new call, and the IMS used for the new call sends a first message to a network function.

The meaning of the first message may refer to the description of the aforementioned method embodiment.

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

In an embodiment of the present application, the network function can establish a new call between the application side and the network according to the first message, thereby realizing the establishment of a new call between the application side and the network.

Optionally, in the process of terminating the new call initiated by the application side, the terminal may receive the SIP BYE sent by the network function and send a response to the network function.

Optionally, in the process of terminating a new call initiated by the terminal, the terminal may send a SIP BYE to the network function, and receive a SIP response sent by the network function.

The specific implementation process of the embodiment of the present application is described in detail below in conjunction with the system shown in Figure 1. The application side is described by taking third-party applications or vertical industry users as examples, and the network function is described by taking the 5G new call enabling layer as an example.

In this system architecture, when a third-party application or vertical industry user initiates a new call with a terminal by calling the 5G new call enabling layer capability exposure interface, the process of guiding the data channel (BDC) is shown in Figure 7. The process may include:

1) Third-party applications or vertical industry users (such as APP, application servers, web pages, enterprise IPPBX and other devices) call the 5G new call enabling layer capability exposure interface and send a new call establishment request (eMMTelAPI request) to the 5G new call enabling layer.

The request may include the caller ID of the call by the user of a third-party application or vertical industry (which may be a private ID, etc.), the user ID of the called terminal (A) (such as a phone number, etc.), whether to use the new call capability, the call profile (such as a list of mini-programs that can be used for this call or subsequent calls of the same type, etc.), media information such as the audio, video and data channel receiving address ports planned to be used for this call, the call event notification address (used for various event notifications related to third-party call establishment), and other information.

1’) (Optional) The 5G new call enabling layer replies to the third-party application or vertical industry user with a new call establishment response, which includes information such as whether the new call establishment request is successful. (It only means that the call request is successful, not that the call has been finally established).

2) (Optional) The 5G new call enabling layer notifies DCSF of the call profile related to this call (such as the list of mini-programs corresponding to number A, or a certain type of call, such as the list of available mini-programs, etc.). It should be noted that the response from DCSF can be omitted here, and the response may include the call profile setting results, the list of successfully set mini-programs, etc. If this step is not performed, the normal new call establishment process is followed to determine the mini-programs that can be used in this third-party call based on the subscription information of the called party A and users of third-party applications or vertical industries.

3) The G new call enabling layer initiates a call session, generates SDP, and maintains the session state.

The 5G new call enabling layer generates an INVITE request based on the parameters carried in the request to establish a new call. The sender of the request is converted from the caller ID (which may be a private ID, etc.) of the call by the user of the third-party application or vertical industry to a routable ID (such as a phone number, a routable third-party ID, etc.) in the IMS. The 5G new call enabling layer maintains the mapping relationship between the caller ID (which may be a private ID, etc.) of the user of the third-party application or vertical industry and the routable ID in the IMS. The routing ID in the IMS can be allocated by the 5G new call enabling layer, such as randomly selecting from the number pool of the 5G new call enabling layer, or generating a routable third-party ID according to a specific algorithm. The INVITE request also includes an SDP offer generated based on the media information such as the audio, video and data channel receiving address port planned to be used for this call carried in the new call establishment request. In addition, it can also carry other information that should be carried by the new call signaling.

4) The 5G new call enabling layer sends the INVITE request generated in step 3 to the 5G new call IMS.

5) For new calls, IMS determines that DC needs to be used and performs DCSF discovery.

New call IMS recognizes that this INVITE request contains new call related media information, and third-party applications or vertical industry users have subscribed to new call services, so it determines that this call needs to be established as a new call, and this INVITE request needs to be routed to DCSF.

Steps 6-13 are standard processes, used for DC-related event notifications and media reservation, etc. In this step, DCSF and DCMF will determine which mini-programs can be used by terminal A and third-party applications or vertical industry users for this call based on the call profile obtained in step 2.

6), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; 7), DCSF determines whether 5G new calls can be used and the 5G new call control strategy; 8), DCSF generates DC media information for the local and remote networks, including a list of mini-programs, etc.; 9), DCSF sends Nimsas_MediaControl_MediaInstruction to the new call IMS; 10), the new call IMS performs DCMF/eMRF (enhanced MRF) discovery; 11), the new call IMS requests DCMF/eMRF to reserve the media resources required for the local and remote networks. DCMF/Enhance MRF allocates media resources to the local and remote networks; 12), the new call IMS sends Nimsas_MediaControl_MediaInstructionresponse to DCSF; 13), DCSF sends Nimsas_SessionEventControl_Notify response to the new call IMS; 14) DCSF sends Nimsas_SessionEventControl_Notify response to the new call IMS.

14) After completing the DC-related event notification and media reservation processes, the new call IMS sends an INVITE request containing an SDP offer to the home network of the called terminal A.

15) The called network completes the call session negotiation, DC-related event notification, media reservation, etc. In this step, the called network DCSF and DCMF will determine which applets Terminal A can use for this call based on the call profile obtained in step 2.

16) The called network and the calling side complete the necessary 18X/PRACK/UPDATE/200OK processes.

17) The called network replies 200OK to the calling side. The 200OK includes the SDP answer from the called side, including media information such as the audio, video and data channel receiving address port that the called terminal A plans to use for this call.

18-19) The calling network completes the necessary media update process.

20) The new call IMS responds 200OK to the 5G new call enabling layer.

21) The 5G new call enabling layer generates the corresponding API content based on the previously maintained 5G new call session information, the received 200OK and the SDP answer contained therein, and sends the eMMTelAPI called success request to third-party applications or vertical industry users. This API includes the caller ID (which may be a private ID, etc.) of the third-party application or vertical industry user, the called terminal (A) user ID (such as phone number, etc.), whether to use the new call capability, call profile (such as the list of mini-programs that can be used for this call or subsequent calls of the same type, etc.), and the audio, video and data channel receiving address port of the called terminal A of this call and other media information.

If there is no step 1') before, the above information is included in the new called success request generated by the 5G new call enabling layer; if there is step 1') before, the above information is included in the new call call response; if the above information is included in the called success request, the third-party application or vertical industry user replies with the called success response, which includes whether the called success request is successful.

22) The DC1 from the 5G new call enabling layer to the local network is established, and the corresponding mini-program list and mini-program download process are included. Here, only the call profile obtained in step 2 can be obtained to determine which mini-programs terminal A can use for this call. If the enabling layer uses the Hypertext Transfer Protocol (HTTP) proxy method, DC1 can be directly established between users such as third-party applications or vertical industries and the local network.

23) Terminal A establishes DC2 to the local network, and the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 2 can be obtained to determine which mini-programs terminal B can use for this call.

24) DC3 establishment from the 5G new call enabling layer to the remote network, the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 2 can be obtained to determine which mini-programs terminal A can use for this call. If the enabling layer uses HTTP proxy, DC3 can be directly established between users such as third-party applications or vertical industries and the remote network.

25) Terminal A establishes DC4 to the remote network, and the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 2 can be obtained to determine which mini-programs terminal B can use for this call.

During the above call establishment process, if the call event notification address carried in the new call request is established, the 5G new call enabling layer can notify the necessary call establishment process events, such as the called party's 18x ringing information, to users such as third-party applications or vertical industries.

In this system architecture, the process of guiding the data channel (BDC) when the terminal initiates a new call to a third-party application or a vertical industry user is shown in Figure 8. The process may include:

1-10) Standard new call establishment process, used for DC-related event notification and media reservation on the calling side. The initial INVITE request contains an SDP offer generated based on the media information such as the receiving address port of the audio, video and data channels planned to be used in this session.

1), the terminal sends an INVITE request to the new call IMS; 2), the new call IMS determines that DC needs to be used and performs DCSF discovery; 3), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; 4), DCSF determines whether 5G new calls can be used and the 5G new call control strategy; 5), DCSF generates DC media information for the local and remote networks, including a list of mini-programs, etc.; 6), DCSF sends Nimsas_MediaControl_MediaInstruction to the new call IMS; 7), the new call IMS performs DCMF/eMRF (enhanced MRF) discovery; 8), the new call IMS requests DCMF/eMRF to reserve the media resources required for the local and remote networks. DCMF/Enhance MRF allocates media resources to the local and remote networks; 9), the new call IMS sends Nimsas_MediaControl_MediaInstructionresponse to DCSF.

11) The new call IMS routes the INVITE request to the 5G new call enabling layer based on the called number.

12) The 5G new call enabling layer generates the corresponding API content based on the received INVITE and the SDP answer contained therein, and sends an eMMTel API request to third-party applications or vertical industry users. This API includes the calling terminal (A) identifier (such as a phone number, etc.), the called party identifier of the third-party application or vertical industry user for this call (an identifier that can be routed in IMS, such as a phone number, etc.), whether to use the new call capability, and the media information such as the audio, video and data channel receiving address port of the called terminal A for this call. This API content is included in the new call incoming request generated by the 5G new call enabling layer. The 5G new call enabling layer maintains the state of this INVITE and maintains the subsequent established session. The 5G new call enabling layer maintains the mapping relationship between the called party identifier of the third-party application or vertical industry user for this call (an identifier that can be routed in IMS, such as a phone number, etc.) and the calling party identifier of the third-party application or vertical industry user for this call (which may be a private identifier, etc.). The third-party application or vertical industry user can immediately return a new call incoming response. If a new call incoming response is returned, this response only indicates whether the new call incoming request is successful, and does not mean that the new call is finally established successfully.

13) The 5G new call enabling layer acts as a session endpoint, maintains session status, and generates an API.

14) After the call between the 5G new call enabling layer and third-party applications or vertical industries is established, the third-party applications or vertical industries will make a successful call establishment request, or if the new call incoming response is not returned in step 12), the result of the call establishment is carried in the returned new call incoming response. This call establishment success request or new call incoming response contains relevant information about the call, including whether to use the new call capability, call profile (such as the list of mini-programs that can be used for this call or subsequent calls of the same type), media information such as the audio, video and data channel receiving address ports planned for this call, and call event notification address (used for various event notifications related to third-party call establishment).

15) (Optional) The 5G new call enabling layer notifies DCSF of the call profile related to this call (such as the list of mini-programs that can be used by number A, or the list of mini-programs that can be used for a certain type of call, such as caller A is 10086, etc.) according to the contents of steps 12 and 13. It should be noted that the response from DCSF can be omitted here, and the response may include the call profile setting results, the list of successfully set mini-programs, etc. If this step is not performed, the normal new call establishment process is followed to determine the mini-programs that can be used in this third-party call based on the subscription information of caller A and users of third-party applications or vertical industries.

16) The 5G new call enabling layer communicates with the network to which it belongs to perform DC-related event notifications and media reservations.

17) The called network and the calling side complete the necessary 18X/PRACK/UPDATE/200OK processes.

18) The 5G new call enabling layer replies a 200OK response to the calling side based on the session information maintained in steps 12 and 13. The response includes an SDP answer generated based on the information obtained in step 12. The SDP contains media information such as the audio, video and data channel receiving address ports that users such as root call third-party applications or vertical industries plan to use.

19-20) The calling network completes the necessary media update process.

21) The new call IMS sends a 200 OK response to the calling terminal A.

22) Terminal A establishes a connection with DC1 of the local network, and the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 15 can be obtained to determine which mini-programs can be used by terminal A in this call.

23) DC2 is established from the 5G new call enabling layer to the local network, and the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 15 can be obtained to determine which mini-programs terminal B can use for this call. If the enabling layer uses HTTP proxy, DC2 can be directly established between users such as third-party applications or vertical industries and the local network.

24) DC3 from terminal A to the remote network is established, and the corresponding mini-program list and mini-program download process are obtained. Here, only the call profile obtained in step 15 can be obtained to determine which mini-programs terminal A can use for this call.

25) DC4 is established from the 5G new call enabling layer to the remote network, and the corresponding mini-program list and mini-program download process. Here, only the call profile obtained in step 15 can be obtained to determine which mini-programs terminal B can use for this call. If the enabling layer uses HTTP proxy, DC4 can be directly established between users such as third-party applications or vertical industries and the remote network.

During the above call establishment process, if the call event notification address carried in the new call request is established, the 5G new call enabling layer can notify the necessary call establishment process events, such as the called party's 18x ringing information, to users such as third-party applications or vertical industries.

After the application side initiates a new call with the terminal, it can also initiate an application data channel between the application side and the terminal. The difference is that at this time, terminal A and third-party applications or vertical industry users can only use the new call applet determined by the call profile obtained in step 2 of Figure 7. The process of establishing a new call application data channel (ADC) initiated by the application side is shown in Figure 9. The process may include:

1) A third-party application or vertical industry user (such as an APP, an application server, a web page, an enterprise IPPBX, or other equipment) has established a new call session using the method shown in FIG. 7 or FIG. 8 .

2) Third-party applications or vertical industry users call the 5G new call enabling layer capability exposure interface and send an application data channel establishment request (eMMTel API ADC establishment request) to the 5G new call enabling layer. The request may include the caller ID (which may be a private ID, etc.) of the third-party application or vertical industry user for the call, the called terminal (A) user ID (such as phone number, etc.), whether to use the new call capability, call profile (such as the list of mini-programs that can be used for this call or subsequent calls of the same type), media information such as the audio, video and data channel receiving address ports planned to be used for this call, call event notification address (used for various event notifications related to third-party call establishment) and other information.

1’) (Optional) The 5G new call enabling layer responds to the third-party application or vertical industry user with an application data channel establishment response (API response), which includes information such as whether the request to establish the application data channel is successful (it only means that the call request is successful, and does not mean that the application data channel has been finally established).

3) The 5G new call enabling layer updates the call session, generates SDP, and maintains the session status.

The 5G new call enabling layer generates a re-INVITE request based on the parameters carried in the new call request. The sender of the request converts the caller ID (which may be a private ID, etc.) of the third-party application or vertical industry user into a routable ID (such as a phone number, a routable third room ID, etc.) within the IMS based on the mapping relationship saved when the new call is established. The re-INVITE request also includes an SDP offer generated based on the media information such as the audio, video and data channel receiving address port planned to be used by the application data channel carried in the application data channel request. In addition, it can also carry other information that should be carried by the new call signaling.

4-16) is the same as the standard ADC establishment process. Among them:

4), the 5G new call enabling layer sends a reINVITE request to the new call IMS; 5), the new call IMS determines that DC needs to be used and performs DCSF discovery; 6), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; 7), DCSF determines whether 5G new calls can be used and the 5G new call control strategy; 8), DCSF generates DC media information for the local and remote networks, including a list of mini-programs, etc.; 9), DCSF sends Nimsas_SessionEventControl_Notify_response to the new call IMS; 10), the new call IMS sends re-INVITE (SDP with audio/video and Bootstrap DC offer) to the terminal; 11), the called network negotiates; 12), the terminal sends 200OK (SDP with audio/video and Bootstrap DC) to the new call IMS. answer); 13), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; 14) DCSF sends Nimsas_SessionEventControl_Notify response to the new call IMS; 15), execute QoS flow (quality of service flow); 16), the new call IMS sends 200OK to the 5G new call enabling layer.

17) The 5G new call enabling layer acts as a session endpoint, maintains session status, and generates an API.

18) After the call between the 5G new call enabling layer and third-party applications or vertical industry users is established, the 5G new call enabling layer sends a successful application data channel establishment request (eMMTel API called success request), or when no new call incoming response is returned in 2), the application data channel response is returned with the result of the application data channel establishment. This application data channel establishment success request or application data channel establishment response contains relevant information about the call, such as media information such as the audio, video and data channel receiving address port used by this application data channel.

19-20) is the same as the standard ADC establishment process.

After the terminal establishes a new call with the application side, an application data channel can also be established between the initiator and the application side. The difference is that at this time, terminal A and third-party applications or vertical industry users can only use the new call applet determined by the call profile obtained in step 15 of Figure 8. The process of establishing an application data channel (ADC) for initiating a new call on the application side is shown in Figure 10. This process may include:

1-8) is the same as the standard ADC establishment process.

In 1), the terminal sends a re-INVITE request to the new call IMS; in 2), the new call IMS determines that DC needs to be used and performs DCSF discovery; in 3), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; in 4), DCSF determines whether 5G new calls can be used and the 5G new call control strategy; in 5), DCSF generates DC media information for the local and remote networks, including a list of mini-programs, etc.; in 6), DCSF sends Nimsas_MediaControl_MediaInstruction to the new call IMS; 7), DCSF sends Nimsas_SessionEventControl_Notify_response to the new call IMS; 8), the new call IMS sends re-INVITE (SDP with audio/video and BootstrapDC offer) to DCSF.

9) The 5G new call enabling layer acts as a session endpoint, maintains session status, and generates an API.

10) The 5G new call enabling layer generates an application data channel establishment request (eMMTel API request) based on the parameters carried in the re-INVITE request. The sender of the request converts the routable identifier (such as phone number, routable third room ID, etc.) in the IMS into the caller identifier (which may be a private identifier, etc.) of the third-party application or vertical industry user for the call based on the mapping relationship saved when the new call is established. The data channel establishment request also includes an SDP offer generated based on the media information such as the audio, video and data channel receiving address port planned to be used by the application data channel carried in the application data channel request. In addition, it can also carry other information that should be carried by the new call signaling.

11) Third-party applications or vertical industry users call the 5G new call enabling layer capability exposure interface and send a data channel establishment response (eMMTel API response) to the 5G new call enabling layer. The response may include the caller ID (which may be a private ID, etc.) of the third-party application or vertical industry user for the call, the called terminal (A) user ID (such as telephone number, etc.), the audio, video and data channel receiving address port and other media information planned to be used for the data channel of this application, the call event notification address (used for various event notifications related to third-party call establishment) and other information.

12) The 5G new call enabling layer generates an SDP answer to update and maintain the session.

The 5G new call enabling layer generates a 200OK response based on the parameters carried in the data channel establishment response. The sender of the response converts the caller ID (which may be a private ID, etc.) of the call by the third-party application or vertical industry user into a routable ID (such as a phone number, a routable third-party ID, etc.) within the IMS based on the mapping relationship saved when the new call is established. The 200OK request also includes an SDP answer generated based on the media information such as the audio, video and data channel receiving address port planned to be used by the application data channel carried in the application data channel request. In addition, it also carries other information that should be carried by the new call signaling.

13-20) is the same as the standard ADC establishment process.

In 13), the 5G new call enabling layer negotiates; in 14), the 5G new call enabling layer sends 200OK to the new call IMS; in 15), the new call IMS sends Nimsas_SessionEventControl_Notify to DCSF; in 16), DCSF sends Nimsas_SessionEventControl_Notify response to the new call IMS; in 17), _{QoS flow is executed;} in 18), the new call IMS sends 200OK to the terminal; 19) the terminal and the 5G new call enabling layer ACK; 20) ADC is established and data is exchanged within ADC.

Optionally, in an embodiment of the present application, the application side may terminate the new call. Specifically, when the application side terminates the new call, a third-party application or a user in a vertical industry calls the 5G new call enabling layer capability exposure interface to send a call termination request, which includes the session identifier to be terminated (such as Session ID), and the 5G new call enabling layer maps it to SIP BYE, and maps it to the corresponding capability exposure interface API response when the terminal returns a response.

Optionally, in an embodiment of the present application, the terminal side terminates the new call. Specifically, the process of terminating a new call by the terminal is the same as the general process of terminating a call. When the SIP BYE sent to a third-party application or vertical industry user reaches the 5G new call enabling layer, the enabling layer maps it to the corresponding API, and the reverse confirmation is mapped by the API to the corresponding SIP response.

Optionally, in an embodiment of the present application, third-party applications or vertical industry users can also query the call status of new calls. The process of third-party applications or vertical industry users querying the new call between the terminal and the application by calling the 5G new call enabling layer capability exposure interface is shown in Figure 11. The process may include:

1) Third-party applications or vertical industry users (such as APP, application servers, web pages, enterprise IPPBX and other devices) call the 5G new call enabling layer capability exposure interface and send a new call query request (eMMTelAPI request) to the 5G new call enabling layer. The request may include information such as the call session identifier (Session ID).

2) The 5G new call enabling layer replies to the third-party application or vertical industry user with the response corresponding to the new call query. The response may include the result of the new call session query (success, failure, etc., and the reason for failure if failed), the two parties of the call (terminal A and third-party application or vertical industry user), the list of available mini-programs (obtained in the response to step 2 in Figure 7 or step 14 in Figure 8), call establishment time, etc.

It can be seen from the above description that the solution of the embodiment of the present application is used to realize the establishment of a new call between the application side and the terminal, the establishment of the ADC process, and other processes. For the terminal, in the embodiment of the present application, it is also applicable to the terminal that does not support IMS and does not support mobile code numbers to use the 5G new call through the solution of the embodiment of the present application.

See Figure 12, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to network functions. As shown in Figure 12, the request processing device includes:

The first receiving module 1201 is used to receive a first message, wherein the first message is used to request to establish a new call between the application side and the terminal; the first processing module 1202 is used to establish a new call between the application side and the terminal according to the first message.

Optionally, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The first sending module is used to send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the device further comprises:

A second sending module, configured to send service configuration information of the new call to the first network element; and receive a third message sent by the first network element;

or,

The second processing module is used to determine the information of the candidate mini-programs used by the application side in this new call according to the subscription information of the application side.

Optionally, the first processing module is further used for:

An invitation INVITE message is sent to the IP Multimedia Subsystem IMS used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal.

Optionally, the INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS;

Session Description Protocol (SDP) information for this new call;

ID of the called party.

Optionally, the device further comprises:

A second receiving module, configured to receive a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information;

A first generating module, configured to generate first information according to the fourth message;

a third sending module, configured to send a fifth message to the application side, wherein the fifth message includes the first information;

The third processing module is used to execute the mini-program list and/or mini-program download process.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the first message is a first message sent by an IMS used for a new call, and the first message includes SDP information of the new call.

Optionally, the first processing module is further used for:

generating second information according to the first message;

Sending a fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Receive a sixth message sent by the application side, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the device further comprises:

The third receiving module is used to receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The fourth sending module is used to send the service configuration information of the new call to the first network element.

Optionally, the device further comprises:

A fifth processing module, configured to perform data channel related event notification and media reservation with the home network;

a fifth sending module, configured to send an eighth message to the IMS used for the new call, wherein the eighth message includes SDP information;

The sixth processing module is used to execute the mini-program list and/or mini-program download process.

Optionally, the device further comprises:

The fifth sending module is used to send a call establishment process event to the application side.

Optionally, the device further comprises:

a fourth receiving module, configured to receive a fifteenth message, wherein the fifteenth message is used to request establishment of an application data channel between the application side and the terminal;

An eighth processing module is used to establish an application data channel between the application side and the terminal according to the fifteenth message.

Optionally, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address;

Session ID.

Optionally, the device further comprises:

The sixth sending module is used to send a ninth message to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the eighth processing module is further used for:

A re-INVITE message is sent to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal.

Optionally, the re-INVITE message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information for this new call;

Session ID.

Optionally, the routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the device further comprises:

a fifth receiving module, configured to receive a tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

A second generating module, used to generate third information according to the tenth message;

a seventh sending module, configured to send an eleventh message to the application side, wherein the eleventh message includes the third information and is configured to indicate a result of establishing the application data channel;

The ninth processing module is used to establish an application data channel with the terminal.

Optionally, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes SDP information of the new call.

Optionally, the eighth processing module is further used for:

Generate fourth information according to the fifteenth message;

Sending a sixteenth message to the application side, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message sent by the application side is received, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a sixth receiving module, configured to receive a seventeenth message sent by the application side, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A first mapping module, configured to map the seventeenth message into a SIP BYE, and send the SIP BYE to the terminal;

The seventh receiving module is used to receive the response sent by the terminal, map the response into a response, and send the response to the application side.

Optionally, the device further comprises:

an eighth receiving module, configured to receive the SIP BYE sent by the terminal, map the SIP BYE into a fifth message, and send the fifth message to the application side;

The second mapping module is used to receive the response sent by the application side, map the response into a SIP response, and send the SIP response to the terminal.

Optionally, the device further comprises:

a ninth receiving module, configured to receive an eighteenth message sent by the application side, wherein the eighteenth message is used to query a new call between the application side and the terminal;

An eighth sending module is used to send a thirteenth message to the application side, wherein the thirteenth message is used to indicate the query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 13, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to the application side. As shown in Figure 13, the request processing device includes:

The first sending module 1301 is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the application side and the terminal.

Optionally, the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The first receiving module is used to receive a second message sent by the network function, wherein the second message is used to indicate whether the first message is successful.

Optionally, the device further comprises:

The second receiving module is used to receive a fifth message sent by the network function, wherein the fifth message includes the first information.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the device further comprises:

The third receiving module is used to receive a call establishment process event sent by the network function.

Optionally, the device further comprises:

The second sending module is used to send a fifteenth message to the network function, wherein the fifteenth message is used to request to establish an application data channel between the application side and the terminal.

Optionally, the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the device further comprises:

The fourth receiving module is used to receive a ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the device further comprises:

A fifth receiving module is used to receive an eleventh message sent by the network function, wherein the eleventh message is used to indicate a result of establishing the application data channel.

Optionally, the device further comprises:

a sixth receiving module, configured to receive a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

The third sending module is used to send a twelfth message to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a fourth sending module, configured to send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

The seventh receiving module is used to receive a response sent by the network function.

An eighth receiving module is used to receive a fifth message sent by the network function and send a response to the network function.

a fifth sending module, configured to send an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A ninth receiving module is used to receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 14, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to the application side. As shown in Figure 14, the request processing device includes:

The first receiving module 1401 is used to receive a fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

The first sending module 1402 is used to send a sixth message to the network function, wherein the sixth message is used to indicate the result of establishing the new call.

Optionally, the device may further include:

The second sending module is used to send a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the device further comprises:

The second receiving module is used to receive a call establishment process event sent by the network function.

Optionally, the device further comprises:

A third receiving module, configured to receive a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

The third sending module is used to send a twelfth message to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the device further comprises:

a fifth sending module, configured to send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

The fourth receiving module is used to receive a response sent by the network function.

Optionally, the device further comprises:

A fifth receiving module receives a fifth message sent by the network function and sends a response to the network function.

Optionally, the device further comprises:

a sixth sending module, configured to send an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A sixth receiving module receives a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 15, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to an IMS used for a new call. As shown in Figure 15, the request processing device includes:

The first sending module 1501 is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the first message includes SDP information of the new call.

Optionally, the device further comprises:

The first receiving module is used to receive an eighth message sent by the network function, wherein the eighth message includes SDP information.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 16, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to a terminal. As shown in Figure 16, the request processing device includes:

The first sending module 1601 is used to send an INVITE request to the IMS used for the new call, and the IMS used for the new call sends a first message to the network function;

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the device further comprises:

The first receiving module is used to receive the SIP BYE sent by the network function and send a response to the network function.

Optionally, the device further comprises:

The second sending module is used to send a SIP BYE to the network function and receive a SIP response sent by the network function.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 17, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to a terminal. As shown in Figure 17, the request processing device includes: a processor 1701 and a transceiver 1702;

The transceiver 1702 is used to receive a first message, wherein the first message is used to request to establish a new call between the application side and the terminal;

The processor 1701 is configured to establish a new call between the application side and the terminal according to the first message.

Optionally, the first message is a first message sent by the application side; wherein the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver 1702 is further used for:

Send a second message to the application side, wherein the second message is used to indicate whether the first message is successful.

Optionally, the processor 1701 is further configured to:

Sending service configuration information of the new call to the first network element; receiving a third message sent by the first network element;

or,

According to the subscription information of the application side, information of the candidate mini-programs used by the application side in this new call is determined.

Optionally, the processor 1701 is further configured to:

An invitation INVITE message is sent to the IP Multimedia Subsystem IMS used for the new call, wherein the INVITE message is used to establish a new call between the application side and the terminal.

Optionally, the INVITE message includes one or more of the following:

The routable identifier of the application side in the new call IMS;

Session Description Protocol (SDP) information for this new call;

ID of the called party.

Optionally, the processor 1701 is further configured to:

receiving a fourth message sent by the IMS used for the new call, wherein the fourth message includes SDP information;

Generate first information according to the fourth message;

Sending a fifth message to the application side, wherein the fifth message includes the first information;

Execute the applet list and/or applet download process.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the first message is a first message sent by an IMS used for a new call, and the first message includes SDP information of the new call.

Optionally, the processor 1701 is further configured to:

generating second information according to the first message;

Sending a fourteenth message to the application side, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information;

Receive a sixth message sent by the application side, wherein the sixth message is used to indicate a result of establishing the new call.

Optionally, the transceiver 1702 is further used for:

Receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the sixth message includes one or more of the following:

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver 1702 is further used for:

Send the service configuration information of the new call to the first network element.

Optionally, the processor 1701 is further configured to:

Notify the home network of data channel related events and make media reservations;

Sending an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

Execute the applet list and/or applet download process.

Optionally, the transceiver 1702 is further used for:

Sending a call establishment process event to the application side.

Optionally, the processor 1701 is further configured to:

receiving a fifteenth message, wherein the fifteenth message is used to request to establish an application data channel between the application side and the terminal;

An application data channel is established between the application side and the terminal according to the fifteenth message.

Optionally, the fifteenth message is the fifteenth message sent by the application side; wherein the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address;

Session ID.

Optionally, the transceiver 1702 is further used for:

A ninth message is sent to the application side, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the processor 1701 is further configured to:

A re-INVITE message is sent to the IMS used for the new call, wherein the re-INVITE message is used to establish an application data channel between the application side and the terminal.

Optionally, the re-INVITE message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information for this new call;

Session ID.

Optionally, the routable identifier in the IMS used by the application side for the new call is determined by the network function according to a first corresponding relationship, where the first corresponding relationship is a corresponding relationship between the identifier of the application side and the routable identifier in the IMS used for the new call.

Optionally, the transceiver 1702 is further used for:

receiving a tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

generating third information according to the tenth message;

Sending an eleventh message to the application side, wherein the eleventh message includes the third information and is used to indicate a result of establishing the application data channel;

An application data channel is established with the terminal.

Optionally, the fifteenth message is the fifteenth message sent by the IMS used for the new call, and the fifteenth message includes SDP information of the new call.

Optionally, the processor 1701 is further configured to:

Generate fourth information according to the fifteenth message;

Sending a sixteenth message to the application side, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message sent by the application side is received, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver 1702 is further used for:

receiving a seventeenth message sent by the application side, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

Mapping the seventeenth message into a SIP BYE, and sending the SIP BYE to the terminal;

A response sent by the terminal is received, the response is mapped into a response, and the response is sent to the application side.

Optionally, the transceiver 1702 is further used for:

receiving a SIP BYE sent by the terminal, mapping the SIP BYE into a fifth message, and sending the fifth message to the application side;

A response sent by the application side is received, the response is mapped into a SIP response, and the SIP response is sent to the terminal.

Optionally, the transceiver 1702 is further used for:

receiving an eighteenth message sent by the application side, wherein the eighteenth message is used to query a new call between the application side and the terminal;

A thirteenth message is sent to the application side, wherein the thirteenth message is used to indicate a query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 18, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to the application side. As shown in Figure 18, the request processing device includes: a processor 1801 and a transceiver 1802;

The transceiver 1802 is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the application side and the terminal.

Optionally, the first message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver 1802 is further used for:

A second message sent by the network function is received, wherein the second message is used to indicate whether the first message is successful.

Optionally, the transceiver 1802 is further used for:

A fifth message sent by the network function is received, wherein the fifth message includes the first information.

Optionally, the first information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Session ID.

Optionally, the transceiver 1802 is further used for:

Receive a call establishment process event sent by the network function.

Optionally, the transceiver is further used for:

A fifteenth message is sent to the network function, wherein the fifteenth message is used to request establishment of an application data channel between the application side and the terminal.

Optionally, the fifteenth message includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

whether to use the new call capability;

Service configuration information for this new call;

Media information for this new call;

Call event notification address.

Optionally, the transceiver 1802 is further used for:

A ninth message sent by the network function is received, wherein the ninth message is used to indicate whether the fifteenth message is successful.

Optionally, the transceiver 1802 is further used for:

An eleventh message sent by the network function is received, wherein the eleventh message is used to indicate a result of establishing the application data channel.

Optionally, the transceiver 1802 is further used for:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver 1802 is further used for:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the transceiver 1802 is further used for:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the transceiver 1802 is further used for:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 19, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to the application side. As shown in Figure 19, the request processing device includes: a processor 1901 and a transceiver 1902;

The transceiver 1902 is used to receive the fourteenth message sent by the network function, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes the second information; and send the sixth message to the network function, wherein the sixth message is used to indicate the result of establishing this new call.

Optionally, the transceiver 1902 is further used for:

Sending a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message is successful.

Optionally, the second information includes one or more of the following:

The identification of the calling terminal;

The identifier of the application side in this new call;

whether to use the new call capability;

Media information for this new call;

Session ID.

Optionally, the transceiver 1902 is further used for:

Receive a call establishment process event sent by the network function.

Optionally, the transceiver 1902 is further used for:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used to establish an application data channel between the terminal and the application side and includes the fourth information;

A twelfth message is sent to the network function, wherein the twelfth message is used to indicate a result of establishing the data channel.

Optionally, the fourth information includes one or more of the following:

The identifier of the application side in this new call;

called party identification;

Media information for this new call;

Call event notification address.

Optionally, the twelfth message includes one or more of the following:

The routable identifier of the application side in the IMS used for the new call;

SDP information.

Optionally, the transceiver 1902 is further used for:

Sending a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application side and the terminal;

A response sent by the network function is received.

Optionally, the transceiver 1902 is further used for:

receiving a fifth message sent by the network function, and sending a response to the network function.

Optionally, the transceiver 1902 is further used for:

Sending an eighteenth message to the network function, wherein the eighteenth message is used to query a new call between the application side and the terminal;

Receive a thirteenth message sent by the network function, wherein the thirteenth message is used to indicate a query result of the new call.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

Refer to Figure 20, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to the application side. As shown in Figure 20, the request processing device includes: a processor 2001 and a transceiver 2002;

The transceiver 2002 is used to send a first message to the network function, wherein the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the first message includes SDP information of the new call.

Optionally, the transceiver 2002 is further used for:

An eighth message sent by the network function is received, wherein the eighth message includes SDP information.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

See Figure 21, which is a structural diagram of a request processing device provided in an embodiment of the present application, which is applied to a terminal. As shown in Figure 21, the request processing device includes: a processor 2101 and a transceiver 2102;

The transceiver 2102 is used to send an INVITE request to the IMS used for the new call, and the IMS used for the new call sends a first message to the network function;

The INVITE request includes the SDP information of the new call, and the first message is used to request to establish a new call between the terminal and the application side.

Optionally, the transceiver 2102 is further used for:

Receive the SIP BYE sent by the network function, and send a response to the network function.

Optionally, the transceiver 2102 is further used for:

Send a SIP BYE to the network function, and receive a SIP response sent by the network function.

The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

An embodiment of the present application provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is used to read the program in the memory to implement the steps in the request processing method described above.

The embodiment of the present application also provides a readable storage medium, on which a program is stored. When the program is executed by the processor, each process of the above-mentioned request processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid state drive (SSD)), etc.

It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, disk, CD), and includes a number of instructions for a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims (74)

1. A method for processing a request, applied to a network function, comprising:

receiving a first message, wherein the first message is used for requesting to establish a new call between an application side and a terminal;

And establishing a new call between the application side and the terminal according to the first message.

2. The method according to claim 1, wherein the first message is a first message sent by an application side; wherein the first message includes one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

a call event notification address.

3. The method according to claim 2, wherein the method further comprises:

And sending a second message to the application side, wherein the second message is used for indicating whether the first message is successful or not.

4. The method according to claim 2, wherein the method further comprises:

the service configuration information of the new call is sent to the first network element; receiving a third message sent by the first network element;

Or alternatively

And determining the information of the applet candidate used by the application side in the new call according to the subscription information of the application side.

5. The method according to claim 2, wherein said establishing a new call between the application side and the terminal according to said first message comprises:

And sending an INVITE message to an IP multimedia subsystem IMS used by the new call, wherein the INVITE message is used for establishing the new call between the application side and the terminal.

6. The method of claim 5, wherein the INVITE message comprises one or more of:

The application side can route the label in the new conversation IMS;

Session Description Protocol (SDP) information of the new call;

And (5) identifying the called party.

7. The method according to claim 2, wherein the method further comprises:

Receiving a fourth message sent by an IMS used for a new call, wherein the fourth message comprises SDP information;

Generating first information according to the fourth message;

sending a fifth message to the application side, wherein the fifth message comprises the first information;

And executing the applet list and/or the applet downloading flow.

8. The method of claim 7, wherein the first information comprises one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

And (5) session identification.

9. The method of claim 1, wherein the first message is a first message sent by an IMS used for a new call, and wherein the first message includes SDP information for the new call.

10. The method according to claim 9, wherein said establishing a new call between the application side and the terminal according to said first message comprises:

generating second information according to the first message;

A fourteenth message is sent to the application side, wherein the fourteenth message is used for establishing a new call between the terminal and the application side and comprises the second information;

and receiving a sixth message sent by the application side, wherein the sixth message is used for indicating the result of the establishment of the new call.

11. The method according to claim 10, wherein the method further comprises:

and receiving a seventh message of the application side, wherein the seventh message is used for indicating whether the first message is successful or not.

12. The method of claim 10, wherein the second information comprises one or more of:

an identification of the calling terminal;

The application side marks in the new call;

whether to use the new call capability;

media information of the new call;

And (5) session identification.

13. The method of claim 10, wherein the sixth message comprises one or more of:

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

a call event notification address.

14. The method according to claim 12, wherein the method further comprises:

and sending the service configuration information of the new call to a first network element.

15. The method according to claim 10, wherein the method further comprises:

carrying out data channel related event notification and media reservation with a home network;

Sending an eighth message to the IMS used by the new call, wherein the eighth message comprises SDP information;

And executing the applet list and/or the applet downloading flow.

16. The method according to any one of claims 2-15, further comprising:

And sending a call establishment process event to the application side.

17. The method according to claim 1, wherein the method further comprises:

A fifteenth message is received, wherein the fifteenth message is used for requesting to establish an application data channel between the application side and the terminal;

And establishing an application data channel between the application side and the terminal according to the fifteenth message.

18. The method according to claim 17, wherein the fifteenth message is a fifteenth message sent by the application side; wherein the fifteenth message includes one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

a call event notification address;

And (5) session identification.

19. The method of claim 18, wherein the method further comprises:

and sending a ninth message to the application side, wherein the ninth message is used for indicating whether the fifteenth message is successful or not.

20. The method according to claim 18, wherein said establishing an application data channel between the application side and the terminal according to the fifteenth message comprises:

And sending re-INVITE message to the IMS used by the new call, wherein the re-INVITE message is used for establishing an application data channel between the application side and the terminal.

21. The method of claim 20, wherein the re-INVITE message comprises one or more of:

The application side can route the label in IMS used in new conversation;

SDP information of the new call;

And (5) session identification.

22. A method according to claim 6 or 21, wherein the routable identity of the application side within the IMS used for the new call is determined by the network function according to a first correspondence between the identity of the application side and the routable identity within the IMS used for the new call.

23. The method of claim 18, wherein the method further comprises:

receiving a tenth message sent by an IMS used for a new call, wherein the tenth message comprises SDP information;

generating third information according to the tenth message;

An eleventh message is sent to the application side, wherein the eleventh message comprises the third information and is used for indicating the result of the establishment of the application data channel;

And establishing an application data channel between the terminal and the terminal.

24. The method of claim 17 wherein the fifteenth message is a fifteenth message sent by an IMS used for a new call, the fifteenth message including SDP information for the new call.

25. The method according to claim 24, wherein said establishing an application data channel between the application side and the terminal according to the fifteenth message comprises:

Generating fourth information according to the fifteenth message;

a sixteenth message is sent to the application side, wherein the sixteenth message is used for establishing an application data channel between a terminal and the application side and comprises the fourth information;

and receiving a twelfth message sent by the application side, wherein the twelfth message is used for indicating the result of data channel establishment.

26. The method of claim 25, wherein the fourth information comprises one or more of:

The application side marks in the new call;

A called identifier;

media information of the new call;

a call event notification address.

27. The method of claim 25, wherein the twelfth message comprises one or more of:

The application side can route the label in IMS used in new conversation;

SDP information.

28. The method according to claim 1, wherein the method further comprises:

Receiving a seventeenth message sent by the application side, wherein the seventeenth message is used for terminating a new call between the application side and the terminal;

Mapping the seventeenth message into an initial session protocol, then seeing a SIP BYE, and sending the SIP BYE to the terminal;

and receiving the response sent by the terminal, mapping the response into a response, and sending the response to the application side.

29. The method according to claim 1, wherein the method further comprises:

Receiving the SIP BYE sent by the terminal, mapping the SIP BYE into a fifth message, and sending the fifth message to the application side;

And receiving the response sent by the application side, mapping the response into a SIP response, and sending the SIP response to the terminal.

30. The method according to claim 1, wherein the method further comprises:

Receiving an eighteenth message sent by the application side, wherein the eighteenth message is used for inquiring a new call between the application side and the terminal;

And sending a thirteenth message to the application side, wherein the thirteenth message is used for indicating the query result of the new call.

31. A request processing method, applied to an application side, comprising:

and sending a first message to the network function, wherein the first message is used for requesting to establish a new call between the application side and the terminal.

32. The method of claim 31, wherein the first message comprises one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

a call event notification address.

33. The method according to claim 31, characterized in that the method further comprises:

and receiving a second message sent by the network function, wherein the second message is used for indicating whether the first message is successful or not.

34. The method according to claim 31, characterized in that the method further comprises:

And receiving a fifth message sent by the network function, wherein the fifth message comprises the first information.

35. The method of claim 34, wherein the first information comprises one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

And (5) session identification.

36. The method according to claim 31, characterized in that the method further comprises:

And receiving a call establishment process event sent by the network function.

37. The method according to claim 31, characterized in that the method further comprises:

and transmitting a fifteenth message to the network function, wherein the fifteenth message is used for requesting to establish an application data channel between the application side and the terminal.

38. The method of claim 37, wherein the fifteenth message comprises one or more of:

The application side marks in the new call;

A called identifier;

whether to use the new call capability;

service configuration information of the new call;

media information of the new call;

a call event notification address.

39. The method of claim 37, wherein the method further comprises:

and receiving a ninth message sent by the network function, wherein the ninth message is used for indicating whether the fifteenth message is successful or not.

40. The method of claim 37, wherein the method further comprises:

And receiving an eleventh message sent by the network function, wherein the eleventh message is used for indicating the result of the establishment of the application data channel.

41. The method according to claim 31, characterized in that the method further comprises:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used for establishing an application data channel between a terminal and an application side and comprises fourth information;

and sending a twelfth message to the network function, wherein the twelfth message is used for indicating the result of the establishment of the data channel.

42. The method of claim 41, wherein the fourth information comprises one or more of:

The application side marks in the new call;

A called identifier;

media information of the new call;

a call event notification address.

43. The method of claim 41, wherein the twelfth message comprises one or more of the following:

The application side can route the label in IMS used in new conversation;

SDP information.

44. The method according to claim 31, characterized in that the method further comprises:

Transmitting a seventeenth message to the network function, wherein the seventeenth message is used for terminating a new call between the application side and the terminal;

And receiving a response sent by the network function.

45. The method according to claim 31, characterized in that the method further comprises:

And receiving a fifth message sent by the network function and sending a response to the network function.

46. The method according to claim 31, characterized in that the method further comprises:

an eighteenth message is sent to the network function, wherein the eighteenth message is used for inquiring a new call between the application side and the terminal;

And receiving a thirteenth message sent by the network function, wherein the thirteenth message is used for indicating the query result of the new call.

47. A request processing method, applied to an application side, comprising: :

Receiving a fourteenth message sent by a network function, wherein the fourteenth message is used for establishing a new call between the terminal and the application side and comprises second information;

and sending a sixth message to the network function, wherein the sixth message is used for indicating the result of the establishment of the new call.

48. The method according to claim 47, characterized in that the method further comprises:

And sending a seventh message to the network function, wherein the seventh message is used for indicating whether the fourteenth message is successful or not.

49. The method of claim 47, wherein the second information comprises one or more of:

an identification of the calling terminal;

The application side marks in the new call;

whether to use the new call capability;

media information of the new call;

And (5) session identification.

50. The method according to claim 47, characterized in that the method further comprises:

And receiving a call establishment process event sent by the network function.

51. The method according to claim 47, characterized in that the method further comprises:

receiving a sixteenth message sent by the network function, wherein the sixteenth message is used for establishing an application data channel between a terminal and an application side and comprises fourth information;

and sending a twelfth message to the network function, wherein the twelfth message is used for indicating the result of the establishment of the data channel.

52. The method of claim 51, wherein the fourth information comprises one or more of:

The application side marks in the new call;

A called identifier;

media information of the new call;

a call event notification address.

53. The method of claim 51, wherein the twelfth message comprises one or more of:

The application side can route the label in IMS used in new conversation;

SDP information.

54. The method according to claim 47, characterized in that the method further comprises:

Transmitting a seventeenth message to the network function, wherein the seventeenth message is used for terminating a new call between the application side and the terminal;

And receiving a response sent by the network function.

55. The method according to claim 47, characterized in that the method further comprises:

And receiving a fifth message sent by the network function and sending a response to the network function.

56. The method according to claim 47, characterized in that the method further comprises:

an eighteenth message is sent to the network function, wherein the eighteenth message is used for inquiring a new call between the application side and the terminal;

And receiving a thirteenth message sent by the network function, wherein the thirteenth message is used for indicating the query result of the new call.

57. A request processing method, applied to IMS used for a new call, comprising:

and sending a first message to the network function, wherein the first message is used for requesting to establish a new call between the terminal and the application side.

58. The method of claim 57, wherein the first message includes SDP information for the new call.

59. The method of claim 57, characterized in that the method further comprises:

and receiving an eighth message sent by the network function, wherein the eighth message comprises SDP information.

60. A request processing method, applied to a terminal, comprising:

an INVITE request is sent to an IMS used for a new call, and the IMS used for the new call sends a first message to a network function;

the INVITE request includes SDP information of a new call, and the first message is used for requesting to establish the new call between the terminal and the application side.

61. The method of claim 60, wherein the step of, characterized in that the method further comprises:

and receiving the SIP BYE sent by the network function and sending a response to the network function.

62. The method of claim 60, wherein the step of, characterized in that the method further comprises:

And sending the SIP BYE to the network function, and receiving the SIP response sent by the network function.

63. A request processing apparatus, for use in a network function, comprising:

the first receiving module is used for receiving a first message, wherein the first message is used for requesting to establish a new call between the application side and the terminal;

And the first processing module is used for establishing a new call between the application side and the terminal according to the first message.

64. A request processing apparatus, applied to an application side, comprising:

And the first sending module is used for sending a first message to the network function, wherein the first message is used for requesting to establish a new call between the application side and the terminal.

65. A request processing apparatus, applied to an application side, comprising:

The first receiving module is used for receiving a fourteenth message sent by the network function, wherein the fourteenth message is used for establishing a new call between the terminal and the application side and comprises second information;

And the first sending module is used for sending a sixth message to the network function, wherein the sixth message is used for indicating the result of the establishment of the new call.

66. A request processing apparatus, for application to an IMS used for a new call, comprising:

And the first sending module is used for sending a first message to the network function, wherein the first message is used for requesting to establish a new call between the terminal and the application side.

67. A request processing apparatus, applied to a terminal, comprising:

A first sending module, configured to send an INVITE request to an IMS used for a new call, where the IMS used for the new call sends a first message to a network function;

the INVITE request includes SDP information of a new call, and the first message is used for requesting to establish the new call between the terminal and the application side.

68. A request processing apparatus, for use in a network function, comprising: a processor and a transceiver;

The transceiver is used for receiving a first message, wherein the first message is used for requesting to establish a new call between an application side and a terminal;

And the processor is used for establishing a new call between the application side and the terminal according to the first message.

69. A request processing apparatus, applied to an application side, comprising: a processor and a transceiver;

The transceiver is configured to send a first message to a network function, where the first message is used to request establishment of a new call between an application side and a terminal.

70. A request processing apparatus, applied to an application side, comprising: a processor and a transceiver;

The transceiver is configured to receive a fourteenth message sent by the network function, where the fourteenth message is used to establish a new call between the terminal and the application side and includes second information; and sending a sixth message to the network function, wherein the sixth message is used for indicating the result of the establishment of the new call.

71. A request processing apparatus, for application to an IMS used for a new call, comprising: a processor and a transceiver;

The transceiver is configured to send a first message to a network function, where the first message is used to request establishment of a new call between a terminal and an application side.

72. A request processing apparatus, applied to a terminal, comprising: a processor and a transceiver;

the transceiver is configured to send an INVITE request to an IMS used for a new call, and send a first message to a network function by the IMS used for the new call;

the INVITE request includes SDP information of a new call, and the first message is used for requesting to establish the new call between the terminal and the application side.

73. A communication device, comprising: a memory, a processor, and a program stored on the memory and executable on the processor; the method according to any one of claims 1 to 62, characterized in that the processor is arranged to read a program in a memory for implementing the steps in the request processing method.

74. A readable storage medium storing a program, wherein the program when executed by a processor implements the steps in a request processing method according to any one of claims 1 to 62.