Request processing method and apparatus, device, and readable storage medium

Abstract

The present disclosure relates to the technical field of communications, and provides a request processing method and apparatus, a device, and a readable storage medium, used for establishing a new call between an application side and a terminal. The method comprises: 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 on the basis of the first message, establishing the new call between the application side and the terminal.

Description

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

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202311466776.8, filed in China on November 6, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to a request processing method, apparatus, device, and readable storage medium. Background Technology

[0004] 5G New Call (in this disclosure, "New Call" is a specific term, not referring to a "new" call) refers to ultra-high-definition voice and video call services and related value-added services based on the 5G network, such as 5G ultra-high-definition video call, 5G video customer service, barrier-free communication functions, screen sharing, remote collaboration, and augmented reality (AR) fun calls, which can provide users with a visual, multimedia, and highly immersive ultra-high-definition call experience. 5G New Call is implemented based on IP Multimedia Subsystem (IMS) Data Channel (DC) technology. DC negotiation is added during the Session Description Protocol (SDP) negotiation process. The DC can coexist with the call audio and video streams and provides basic capabilities for data interaction. Existing specifications define the main transmitted content in the IMS Data Channel as web pages and scripts to address the lack of call interaction capabilities within the IMS network. The new call network system architecture supports the process of establishing a new call between two terminals in the IMS network.

[0005] In related technologies, such as Skype, gateways are generally used to convert calls into their own application's proprietary protocol, or Web Real-Time Communication (WebRTC) solutions are used, employing a Session Initialization Protocol (SIP) / WebRTC conversion gateway to achieve interoperability with the application side. Existing support for calls with the application side is generally limited to ordinary audio calls or video calls, but none support establishing new calls between the application side (such as web pages, applications (APPs), third-party application servers that do not support IMS, etc.) and the terminal.

[0006] Summary of the Invention

[0007] This disclosure provides a request processing method, apparatus, device, and readable storage medium to establish a new call between an application and a terminal.

[0008] In a first aspect, embodiments of this disclosure provide a request processing method applied to network functions, including:

[0009] Receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal;

[0010] A new call is established between the application and the terminal based on the first message.

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

[0012] The application's identifier in this new call;

[0013] Callee identifier;

[0014] Should we use the new call capability?

[0015] Service configuration information for this new call;

[0016] Media information regarding this new call;

[0017] Call event notification address.

[0018] Optionally, the method further includes:

[0019] A second message is sent to the application side, wherein the second message is used to indicate whether the first message was successful.

[0020] Optionally, the method further includes:

[0021] Send the service configuration information for this new call to the first network element; receive the third message sent by the first network element;

[0022] or,

[0023] Based on the subscription information of the application side, the information of the mini-program that the application side can use in this new call is determined.

[0024] Optionally, establishing a new call between the application side and the terminal based on the first message includes:

[0025] Send an invitation (INVITE) message 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.

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

[0027] The application-side routable identifier within the new call IMS;

[0028] The Session Description Protocol (SDP) information for this new call;

[0029] Callee identifier.

[0030] Optionally, the method further includes:

[0031] Receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information;

[0032] First information is generated based on the fourth message;

[0033] Send a fifth message to the application side, wherein the fifth message includes the first information;

[0034] Execute the mini-program list and / or mini-program download process.

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

[0036] The application's identifier in this new call;

[0037] Callee identifier;

[0038] Should we use the new call capability?

[0039] Service configuration information for this new call;

[0040] Media information regarding this new call;

[0041] Session identifier.

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

[0043] Optionally, establishing a new call between the application side and the terminal based on the first message includes:

[0044] Generate second information based on the first message;

[0045] Send 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;

[0046] Receive a sixth message sent by the application side, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0047] Optionally, the method further includes:

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

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

[0050] The identifier of the calling terminal;

[0051] The application's identifier in this new call;

[0052] Should we use the new call capability?

[0053] Media information regarding this new call;

[0054] Session identifier.

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

[0056] Should we use the new call capability?

[0057] Service configuration information for this new call;

[0058] Media information regarding this new call;

[0059] Call event notification address.

[0060] Optionally, the method further includes:

[0061] Send the service configuration information for this new call to the first network element.

[0062] Optionally, the method further includes:

[0063] Notify the network of data channel-related events and reserve media access with the home network;

[0064] Send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

[0065] Execute the mini-program list and / or mini-program download process.

[0066] Optionally, the method further includes:

[0067] Send a call setup process event to the application side.

[0068] Optionally, the method further includes:

[0069] Receive the fifteenth message, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal;

[0070] The application data channel between the application side and the terminal is established according to the fifteenth message.

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

[0072] The application's identifier in this new call;

[0073] Callee identifier;

[0074] Should we use the new call capability?

[0075] Service configuration information for this new call;

[0076] Media information regarding this new call;

[0077] Call event notification address;

[0078] Session identifier.

[0079] Optionally, the method further includes:

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

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

[0082] 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.

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

[0084] The application side has a routable identifier in the IMS used in the new call;

[0085] SDP information for this new call;

[0086] Session identifier.

[0087] Optionally, the routable identifier in the IMS used by the application side in the new call is determined by the network function according to a first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[0088] Optionally, the method further includes:

[0089] Receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

[0090] Generate third information based on the tenth message;

[0091] Send an eleventh message to the application side, wherein the eleventh message includes the third information, used to indicate the result of the application data channel establishment;

[0092] Establish an application data channel with the terminal.

[0093] Optionally, 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 this new call.

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

[0095] Generate the fourth information based on the fifteenth message;

[0096] Send 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;

[0097] Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0099] The application's identifier in this new call;

[0100] Callee identifier;

[0101] Media information regarding this new call;

[0102] Call event notification address.

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

[0104] The application side has a routable identifier in the IMS used in the new call;

[0105] SDP information.

[0106] Optionally, the method further includes:

[0107] Receive 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;

[0108] The seventeenth message is mapped to a SIP BYE, and the SIP BYE is sent to the terminal.

[0109] The system receives the response sent by the terminal, maps the response to a new response, and sends the response to the application side.

[0110] Optionally, the method further includes:

[0111] The terminal receives the Session Initialization Protocol (SIP) BYE message, maps the SIP BYE to a fifth message, and sends the fifth message to the application side.

[0112] The system receives a response from the application side, maps the response to a SIP response, and sends the SIP response to the terminal.

[0113] Optionally, the method further includes:

[0114] Receive the 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;

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

[0116] Secondly, this disclosure also provides a request processing method, applied to the application side, including:

[0117] Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

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

[0119] The application's identifier in this new call;

[0120] Callee identifier;

[0121] Should we use the new call capability?

[0122] Service configuration information for this new call;

[0123] Media information regarding this new call;

[0124] Call event notification address.

[0125] Optionally, the method further includes:

[0126] Receive a second message sent by the network function, wherein the second message is used to indicate whether the first message was successful.

[0127] Optionally, the method further includes:

[0128] Receive a fifth message sent by the network function, wherein the fifth message includes the first information.

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

[0130] The application's identifier in this new call;

[0131] Callee identifier;

[0132] Should we use the new call capability?

[0133] Service configuration information for this new call;

[0134] Media information regarding this new call;

[0135] Session identifier.

[0136] Optionally, the method further includes:

[0137] Receive the call setup process event sent by the network function.

[0138] Optionally, the method further includes:

[0139] 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.

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

[0141] The application's identifier in this new call;

[0142] Callee identifier;

[0143] Should we use the new call capability?

[0144] Service configuration information for this new call;

[0145] Media information regarding this new call;

[0146] Call event notification address.

[0147] Optionally, the method further includes:

[0148] Receive the ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message was successful.

[0149] Optionally, the method further includes:

[0150] Receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

[0151] Optionally, the method further includes:

[0152] Receive the 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;

[0153] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0155] The application's identifier in this new call;

[0156] Callee identifier;

[0157] Media information regarding this new call;

[0158] Call event notification address.

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

[0160] The application side has a routable identifier in the IMS used in the new call;

[0161] SDP information.

[0162] Optionally, the method further includes:

[0163] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[0164] Receive the response sent by the network function.

[0165] Optionally, the method further includes:

[0166] Receive the fifth message sent by the network function and send a response to the network function.

[0167] Optionally, the method further includes:

[0168] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[0170] Thirdly, embodiments of this disclosure provide a request processing method applied to the application side, including:

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

[0172] A sixth message is sent to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0173] Optionally, the method further includes:

[0174] A seventh message is sent to the network function, wherein the seventh message is used to indicate whether the fourteenth message was successful.

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

[0176] The identifier of the calling terminal;

[0177] The application's identifier in this new call;

[0178] Should we use the new call capability?

[0179] Media information regarding this new call;

[0180] Session identifier.

[0181] Optionally, the method further includes:

[0182] Receive the call setup process event sent by the network function.

[0183] Optionally, the method further includes:

[0184] Receive the 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;

[0185] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0187] The application's identifier in this new call;

[0188] Callee identifier;

[0189] Media information regarding this new call;

[0190] Call event notification address.

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

[0192] The application side has a routable identifier in the IMS used in the new call;

[0193] SDP information.

[0194] Optionally, the method further includes:

[0195] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[0196] Receive the response sent by the network function.

[0197] Optionally, the method further includes:

[0198] Receive the fifth message sent by the network function and send a response to the network function.

[0199] Optionally, the method further includes:

[0200] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[0202] Fourthly, embodiments of this disclosure also provide a request processing method applied to an IMS used for a new call, including:

[0203] Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side.

[0204] Optionally, the first message includes the SDP information for this new call.

[0205] Optionally, the method further includes:

[0206] Receive the eighth message sent by the network function, wherein the eighth message includes SDP information.

[0207] Fifthly, embodiments of this disclosure also provide a request processing method applied to a terminal, including:

[0208] Send an INVITE request to the IMS used for the new call, so that the IMS used for the new call can send a first message to the network function;

[0209] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[0210] Optionally, the method further includes:

[0211] Receive the SIP BYE sent by the network function and send a response to the network function.

[0212] Optionally, the method further includes:

[0213] Send a SIP BYE to the network function and receive a SIP response from the network function.

[0214] Sixthly, embodiments of this disclosure also provide a request processing apparatus applied to network functions, including:

[0215] The first receiving module is used to receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal;

[0216] The first processing module is used to establish a new call between the application side and the terminal based on the first message.

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

[0218] The application's identifier in this new call;

[0219] Callee identifier;

[0220] Should we use the new call capability?

[0221] Service configuration information for this new call;

[0222] Media information regarding this new call;

[0223] Call event notification address.

[0224] Optionally, the device further includes:

[0225] A 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 was successful.

[0226] Optionally, the device further includes:

[0227] The second sending module is used to send the service configuration information of this new call to the first network element; and to receive the third message sent by the first network element.

[0228] or,

[0229] The second processing module is used to determine the information of the mini-program that the application side can use in this new call based on the subscription information of the application side.

[0230] Optionally, the first processing module is further configured to:

[0231] Send an invitation INVITE message 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.

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

[0233] The application-side routable identifier within the new call IMS;

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

[0235] Callee identifier.

[0236] Optionally, the device further includes:

[0237] The second receiving module is used to receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information;

[0238] The first generation module is used to generate first information based on the fourth message;

[0239] The third sending module is used to send a fifth message to the application side, wherein the fifth message includes the first information;

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

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

[0242] The application's identifier in this new call;

[0243] Callee identifier;

[0244] Should we use the new call capability?

[0245] Service configuration information for this new call;

[0246] Media information regarding this new call;

[0247] Session identifier.

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

[0249] Optionally, the first processing module is further configured to:

[0250] Generate second information based on the first message;

[0251] Send 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;

[0252] Receive a sixth message sent by the application side, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0253] Optionally, the device further includes:

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

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

[0256] The identifier of the calling terminal;

[0257] The application's identifier in this new call;

[0258] Should we use the new call capability?

[0259] Media information regarding this new call;

[0260] Session identifier.

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

[0262] Should we use the new call capability?

[0263] Service configuration information for this new call;

[0264] Media information regarding this new call;

[0265] Call event notification address.

[0266] Optionally, the device further includes:

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

[0268] Optionally, the device further includes:

[0269] The fifth processing module is used for data channel-related event notification and media reservation with the home network;

[0270] The fifth sending module is used to send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

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

[0272] Optionally, the device further includes:

[0273] The fifth sending module is used to send call setup process events to the application side.

[0274] Optionally, the device further includes:

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

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

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

[0278] The application's identifier in this new call;

[0279] Callee identifier;

[0280] Should we use the new call capability?

[0281] Service configuration information for this new call;

[0282] Media information regarding this new call;

[0283] Call event notification address;

[0284] Session identifier.

[0285] Optionally, the device further includes:

[0286] 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 was successful.

[0287] Optionally, the eighth processing module is further configured to:

[0288] 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.

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

[0290] The application side has a routable identifier in the IMS used in the new call;

[0291] SDP information for this new call;

[0292] Session identifier.

[0293] Optionally, the routable identifier in the IMS used by the application side in the new call is determined by the network function according to a first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[0294] Optionally, the device further includes:

[0295] The fifth receiving module is used to receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

[0296] The second generation module is used to generate third information based on the tenth message;

[0297] The seventh sending module is used to send an eleventh message to the application side, wherein the eleventh message includes the third information, which is used to indicate the result of the application data channel establishment;

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

[0299] Optionally, 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 this new call.

[0300] Optionally, the eighth processing module is further configured to:

[0301] Generate the fourth information based on the fifteenth message;

[0302] Send 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;

[0303] Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0305] The application's identifier in this new call;

[0306] Callee identifier;

[0307] Media information regarding this new call;

[0308] Call event notification address.

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

[0310] The application side has a routable identifier in the IMS used in the new call;

[0311] SDP information.

[0312] Optionally, the device further includes:

[0313] The sixth receiving module is used to receive 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;

[0314] The first mapping module is used to map the seventeenth message to a SIP BYE and send the SIP BYE to the terminal.

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

[0316] Optionally, the device further includes:

[0317] The eighth receiving module is used to receive the SIP BYE sent by the terminal, map the SIP BYE to the fifth message, and send the fifth message to the application side.

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

[0319] Optionally, the device further includes:

[0320] The ninth receiving module is used to receive the 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;

[0321] The 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.

[0322] In a seventh aspect, embodiments of this disclosure also provide a request processing apparatus, applied to the application side, comprising:

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

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

[0325] The application's identifier in this new call;

[0326] Callee identifier;

[0327] Should we use the new call capability?

[0328] Service configuration information for this new call;

[0329] Media information regarding this new call;

[0330] Call event notification address.

[0331] Optionally, the device further includes:

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

[0333] Optionally, the device further includes:

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

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

[0336] The application's identifier in this new call;

[0337] Callee identifier;

[0338] Should we use the new call capability?

[0339] Service configuration information for this new call;

[0340] Media information regarding this new call;

[0341] Session identifier.

[0342] Optionally, the device further includes:

[0343] The third receiving module is used to receive the call setup process event sent by the network function.

[0344] Optionally, the device further includes:

[0345] The second sending module is used to 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.

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

[0347] The application's identifier in this new call;

[0348] Callee identifier;

[0349] Should we use the new call capability?

[0350] Service configuration information for this new call;

[0351] Media information regarding this new call;

[0352] Call event notification address.

[0353] Optionally, the device further includes:

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

[0355] Optionally, the device further includes:

[0356] The fifth receiving module is used to receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

[0357] Optionally, the device further includes:

[0358] The sixth receiving module is used to receive the 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;

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

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

[0361] The application's identifier in this new call;

[0362] Callee identifier;

[0363] Media information regarding this new call;

[0364] Call event notification address.

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

[0366] The application side has a routable identifier in the IMS used in the new call;

[0367] SDP information.

[0368] Optionally, the device further includes:

[0369] The fourth sending module is used 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;

[0370] The seventh receiving module is used to receive the response sent by the network function.

[0371] The eighth receiving module is used to receive the fifth message sent by the network function and send a response to the network function.

[0372] The fifth sending module is used to 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;

[0373] The ninth receiving module is used to receive the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

[0374] Eighthly, embodiments of this disclosure also provide a request processing apparatus, applied to the application side, including:

[0375] The first receiving module 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 second information;

[0376] 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 the establishment of this new call.

[0377] Optionally, the device may further include:

[0378] 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 was successful.

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

[0380] The identifier of the calling terminal;

[0381] The application's identifier in this new call;

[0382] Should we use the new call capability?

[0383] Media information regarding this new call;

[0384] Session identifier.

[0385] Optionally, the device further includes:

[0386] The second receiving module is used to receive the call setup process event sent by the network function.

[0387] Optionally, the device further includes:

[0388] The third receiving module is used to receive the 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 fourth information;

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

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

[0391] The application's identifier in this new call;

[0392] Callee identifier;

[0393] Media information regarding this new call;

[0394] Call event notification address.

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

[0396] The application side has a routable identifier in the IMS used in the new call;

[0397] SDP information.

[0398] Optionally, the device further includes:

[0399] The fifth sending module is used 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;

[0400] The fourth receiving module is used to receive the response sent by the network function.

[0401] Optionally, the device further includes:

[0402] The fifth receiving module receives the fifth message sent by the network function and sends a response to the network function.

[0403] Optionally, the device further includes:

[0404] The sixth sending module is used to 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;

[0405] The sixth receiving module receives the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

[0406] Ninthly, embodiments of this disclosure also provide a request processing apparatus for use in an IMS for a new call, comprising:

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

[0408] Optionally, the first message includes the SDP information for this new call.

[0409] Optionally, the device further includes:

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

[0411] In a tenth aspect, embodiments of this disclosure also provide a request processing apparatus applied to a terminal, comprising:

[0412] The first sending module 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.

[0413] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[0414] Optionally, the device further includes:

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

[0416] Optionally, the device further includes:

[0417] 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.

[0418] Eleventhly, embodiments of this disclosure also provide a request processing apparatus applied to network functions, including: a processor and a transceiver;

[0419] The transceiver is used to receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal;

[0420] The processor is used to establish a new call between the application side and the terminal based on the first message.

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

[0422] The application's identifier in this new call;

[0423] Callee identifier;

[0424] Should we use the new call capability?

[0425] Service configuration information for this new call;

[0426] Media information regarding this new call;

[0427] Call event notification address.

[0428] Optionally, the transceiver is also used for:

[0429] A second message is sent to the application side, wherein the second message is used to indicate whether the first message was successful.

[0430] Optionally, the processor is further configured to:

[0431] Send the service configuration information for this new call to the first network element; receive the third message sent by the first network element;

[0432] or,

[0433] Based on the subscription information of the application side, the information of the mini-program that the application side can use in this new call is determined.

[0434] Optionally, the processor is further configured to:

[0435] Send an invitation INVITE message 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.

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

[0437] The application-side routable identifier within the new call IMS;

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

[0439] Callee identifier.

[0440] Optionally, the processor is further configured to:

[0441] Receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information;

[0442] First information is generated based on the fourth message;

[0443] Send a fifth message to the application side, wherein the fifth message includes the first information;

[0444] Execute the mini-program list and / or mini-program download process.

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

[0446] The application's identifier in this new call;

[0447] Callee identifier;

[0448] Should we use the new call capability?

[0449] Service configuration information for this new call;

[0450] Media information regarding this new call;

[0451] Session identifier.

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

[0453] Optionally, the processor is further configured to:

[0454] Generate second information based on the first message;

[0455] Send 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;

[0456] Receive a sixth message sent by the application side, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0457] Optionally, the transceiver is also used for:

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

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

[0460] The identifier of the calling terminal;

[0461] The application's identifier in this new call;

[0462] Should we use the new call capability?

[0463] Media information regarding this new call;

[0464] Session identifier.

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

[0466] Should we use the new call capability?

[0467] Service configuration information for this new call;

[0468] Media information regarding this new call;

[0469] Call event notification address.

[0470] Optionally, the transceiver is also used for:

[0471] Send the service configuration information for this new call to the first network element.

[0472] Optionally, the processor is further configured to:

[0473] Notify the network of data channel-related events and reserve media access with the home network;

[0474] Send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

[0475] Execute the mini-program list and / or mini-program download process.

[0476] Optionally, the transceiver is also used for:

[0477] Send a call setup process event to the application side.

[0478] Optionally, the processor is further configured to:

[0479] Receive the fifteenth message, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal;

[0480] The application data channel between the application side and the terminal is established according to the fifteenth message.

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

[0482] The application's identifier in this new call;

[0483] Callee identifier;

[0484] Should we use the new call capability?

[0485] Service configuration information for this new call;

[0486] Media information regarding this new call;

[0487] Call event notification address;

[0488] Session identifier.

[0489] Optionally, the transceiver is also used for:

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

[0491] Optionally, the processor is further configured to:

[0492] 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.

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

[0494] The application side has a routable identifier in the IMS used in the new call;

[0495] SDP information for this new call;

[0496] Session identifier.

[0497] Optionally, the routable identifier in the IMS used by the application side in the new call is determined by the network function according to a first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[0498] Optionally, the transceiver is also used for:

[0499] Receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

[0500] Generate third information based on the tenth message;

[0501] Send an eleventh message to the application side, wherein the eleventh message includes the third information, used to indicate the result of the application data channel establishment;

[0502] Establish an application data channel with the terminal.

[0503] Optionally, 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 this new call.

[0504] Optionally, the processor is further configured to:

[0505] Generate the fourth information based on the fifteenth message;

[0506] Send 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;

[0507] Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0509] The application's identifier in this new call;

[0510] Callee identifier;

[0511] Media information regarding this new call;

[0512] Call event notification address.

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

[0514] The application side has a routable identifier in the IMS used in the new call;

[0515] SDP information.

[0516] Optionally, the transceiver is also used for:

[0517] Receive 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;

[0518] The seventeenth message is mapped to a SIP BYE, and the SIP BYE is sent to the terminal.

[0519] The system receives the response sent by the terminal, maps the response to a new response, and sends the response to the application side.

[0520] Optionally, the transceiver is also used for:

[0521] Receive the SIP BYE sent by the terminal, map the SIP BYE to a fifth message, and send the fifth message to the application side;

[0522] The system receives a response from the application side, maps the response to a SIP response, and sends the SIP response to the terminal.

[0523] Optionally, the transceiver is also used for:

[0524] Receive the 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;

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

[0526] In a twelfth aspect, embodiments of this disclosure also provide a request processing apparatus applied to an application side, comprising: a processor and a transceiver;

[0527] The transceiver is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

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

[0529] The application's identifier in this new call;

[0530] Callee identifier;

[0531] Should we use the new call capability?

[0532] Service configuration information for this new call;

[0533] Media information regarding this new call;

[0534] Call event notification address.

[0535] Optionally, the transceiver is also used for:

[0536] Receive a second message sent by the network function, wherein the second message is used to indicate whether the first message was successful.

[0537] Optionally, the transceiver is also used for:

[0538] Receive a fifth message sent by the network function, wherein the fifth message includes the first information.

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

[0540] The application's identifier in this new call;

[0541] Callee identifier;

[0542] Should we use the new call capability?

[0543] Service configuration information for this new call;

[0544] Media information regarding this new call;

[0545] Session identifier.

[0546] Optionally, the transceiver is also used for:

[0547] Receive the call setup process event sent by the network function.

[0548] Optionally, the transceiver is also used for:

[0549] 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.

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

[0551] The application's identifier in this new call;

[0552] Callee identifier;

[0553] Should we use the new call capability?

[0554] Service configuration information for this new call;

[0555] Media information regarding this new call;

[0556] Call event notification address.

[0557] Optionally, the transceiver is also used for:

[0558] Receive the ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message was successful.

[0559] Optionally, the transceiver is also used for:

[0560] Receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

[0561] Optionally, the transceiver is also used for:

[0562] Receive the 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;

[0563] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0565] The application's identifier in this new call;

[0566] Callee identifier;

[0567] Media information regarding this new call;

[0568] Call event notification address.

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

[0570] The application side has a routable identifier in the IMS used in the new call;

[0571] SDP information.

[0572] Optionally, the transceiver is also used for:

[0573] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[0574] Receive the response sent by the network function.

[0575] Optionally, the transceiver is also used for:

[0576] Receive the fifth message sent by the network function and send a response to the network function.

[0577] Optionally, the transceiver is also used for:

[0578] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[0580] In a thirteenth aspect, embodiments of this disclosure also provide a request processing apparatus applied to an application side, comprising: a processor and a transceiver;

[0581] The transceiver is 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; and to send a sixth message to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0582] Optionally, the transceiver is also used for:

[0583] A seventh message is sent to the network function, wherein the seventh message is used to indicate whether the fourteenth message was successful.

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

[0585] The identifier of the calling terminal;

[0586] The application's identifier in this new call;

[0587] Should we use the new call capability?

[0588] Media information regarding this new call;

[0589] Session identifier.

[0590] Optionally, the transceiver is also used for:

[0591] Receive the call setup process event sent by the network function.

[0592] Optionally, the transceiver is also used for:

[0593] Receive the 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;

[0594] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0596] The application's identifier in this new call;

[0597] Callee identifier;

[0598] Media information regarding this new call;

[0599] Call event notification address.

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

[0601] The application side has a routable identifier in the IMS used in the new call;

[0602] SDP information.

[0603] Optionally, the transceiver is also used for:

[0604] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[0605] Receive the response sent by the network function.

[0606] Optionally, the transceiver is also used for:

[0607] Receive the fifth message sent by the network function and send a response to the network function.

[0608] Optionally, the transceiver is also used for:

[0609] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[0611] In a fourteenth aspect, embodiments of this disclosure also provide a request processing apparatus for use in IMS for new calls, comprising: a processor and a transceiver;

[0612] The transceiver is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side.

[0613] Optionally, the first message includes the SDP information for this new call.

[0614] Optionally, the transceiver is also used for:

[0615] Receive the eighth message sent by the network function, wherein the eighth message includes SDP information.

[0616] In a fifteenth aspect, embodiments of this disclosure also provide a request processing apparatus for a terminal, comprising: a processor and a transceiver;

[0617] 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.

[0618] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[0619] Optionally, the transceiver is also used for:

[0620] Receive the SIP BYE sent by the network function and send a response to the network function.

[0621] Optionally, the transceiver is also used for:

[0622] Send a SIP BYE to the network function and receive a SIP response from the network function.

[0623] In a sixteenth aspect, embodiments of this disclosure also provide a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the request processing method described above.

[0624] In a seventeenth aspect, embodiments of this disclosure also provide a readable storage medium storing a program that, when executed by a processor, implements the steps in the request processing method described above.

[0625] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network. Attached Figure Description

[0626] Figure 1a is one of the system architecture diagrams of an embodiment of this disclosure;

[0627] Figure 1b is a second system architecture diagram of an embodiment of this disclosure;

[0628] Figure 2 is a flowchart of one of the request processing methods provided in the embodiments of this disclosure;

[0629] Figure 3 is a second flowchart of the request processing method provided in an embodiment of this disclosure;

[0630] Figure 4 is a flowchart of the request processing method provided in the embodiment of this disclosure;

[0631] Figure 5 is a flowchart of the request processing method provided in the embodiments of this disclosure;

[0632] Figure 6 is a flowchart of the request processing method provided in the embodiments of this disclosure;

[0633] Figure 7 is a flowchart of the request processing method provided in the embodiments of this disclosure;

[0634] Figure 8 is a flowchart of the request processing method provided in the embodiment of this disclosure;

[0635] Figure 9 is a flowchart of the request processing method provided in an embodiment of this disclosure;

[0636] Figure 10 is a flowchart of the request processing method provided in the embodiment of this disclosure;

[0637] Figure 11a is a flowchart of the request processing method provided in the embodiment of this disclosure;

[0638] Figure 11b is an eleventh flowchart of the request processing method provided in the embodiments of this disclosure;

[0639] Figure 12 is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure;

[0640] Figure 13 is a second structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0641] Figure 14 is a third structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0642] Figure 15 is a fourth structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0643] Figure 16 is a fifth structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0644] Figure 17 is a sixth structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0645] Figure 18 is a seventh structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0646] Figure 19 is an eighth structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0647] Figure 20 is a structural diagram of the request processing apparatus provided in an embodiment of this disclosure;

[0648] Figure 21 is a structural diagram of the request processing apparatus provided in an embodiment of this disclosure. Detailed Implementation

[0649] In this disclosure, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0650] In this disclosure, the term "multiple" refers to two or more, and other quantifiers are similar.

[0651] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.

[0652] Referring to Figures 1a and 1b, which are schematic diagrams of the system architecture supporting 5G new third-party calling functions in embodiments of this disclosure, the application server in Figure 1b corresponds to the application provider in Figure 1a.

[0653] This architecture is based on the international standard 5G New Voice System architecture. It adds network functions (e.g., 5G New Voice Enabler or MMTel Enabler) to the 5G New Voice System for third-party applications or vertical industries. These network functions connect to the interface between the 5G New Voice System and the application server (DC Application Server) (including signaling-related interfaces DC3 (N33) exposed through Network Exposure Function (NEF), as well as DC4 and media-related interfaces MDC2 and MDC3). Through network function processing, the network element function-level interfaces exposed by these interfaces are encapsulated into service application-level interfaces and exposed to third-party applications or vertical industry users through the network function capability exposure interface (eMMTel-2 or MMTel-2). Simultaneously, the network functions can integrate mini-program management functions, connecting to DCSF through the DC5 interface.

[0654] In the embodiments disclosed herein, the network function may be a standalone device, or it may be a module or unit set within a device. It may be an IMS application service (AS) or an application function (AF) in a 5G network. Furthermore, the network function may access the new voice IMS network as an application server or as a terminal.

[0655] The network function may include one or more of the following functions (not limited to):

[0656] 1) Mini Program Management: Used by mini program developers to upload and download new calling mini programs, with functions such as mini program storage and management.

[0657] 2) Session / Media Management: As a related communication terminal for 5G new calls, it is used to terminate 5G new call sessions and media sent to the application side, and generate corresponding Application Programming Interface (API) requests / responses based on the 5G new call sessions and media, or initiate 5G new call sessions and media to the terminal side based on API requests from third-party applications or vertical industry users. Simultaneously, it maintains session-related states and the correspondence between sessions and network function capability opening requests / responses, allocates and maintains routable identifiers for third-party applications or vertical industry users in IMS, and maintains the mapping relationship between third-party application or vertical industry user identifiers and routable identifiers in IMS. Session / Media Management can refer to managing sessions, managing media, or managing both sessions and media.

[0658] 3) Call profile management: Based on specific session information of a certain type of session (such as a specific session or sessions related to each user), distribute relevant information about the mini-program that can be used in that specific session.

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

[0660] 5) Capability Management: Used to manage network functional capabilities, including capability discovery, capability access authentication and authorization, etc.

[0661] 6) Data Channel Proxy: As a data channel proxy, establish a data channel between third-party applications or vertical industry users and the Data Channel Signaling Function (DCSF) / Data Channel Media Function (DCMF) / terminal.

[0662] Referring to Figure 2, which is a flowchart of a request processing method in an embodiment of this disclosure, applied to network functions, it includes:

[0663] Step 201: Receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

[0664] In this embodiment of the disclosure, the new call is an upgrade of the call service. Based on audio and video calls, it combines artificial intelligence (AI) technology, extended reality (XR) technology, media processing technology and other technologies to provide users with a series of innovative call services that are high-definition, intelligent and interactive.

[0665] The new calling services are divided into two categories. The first category is value-added services based on Voice over New Radio (VoNR) / VoLTE video calls, providing services to users with VoLTE and VoNR video calling terminals, offering a "visualized" and "intelligent" calling experience, such as intelligent translation. The second category is value-added services based on IMSDC technology, providing services to 5G new calling terminal users. Users can interact with the other party in real-time via a new calling mini-program, bringing an "interactive" calling experience.

[0666] In practical applications, the new call may be called enhanced call, real-time communication, next-generation real-time communication (NG_RTC or NGRTC), enhanced multimedia telephony (eMMTel), etc. Alternatively, the new call may still be called MMTel, but it supports data channel capabilities.

[0667] Step 202: Establish a new call between the application side and the terminal based on the first message.

[0668] In this disclosed embodiment, the application side (third-party applications or users in vertical industries such as APP, application server, web page, enterprise user-level switch (Private Branch eXchange, IPPBX) and other devices, third-party application server that does not support IMS) or the terminal side can actively initiate the process of establishing a new call.

[0669] I. Application-side proactive initiation

[0670] 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:

[0671] The application-side identifier in this new call (which may be a private identifier, etc.);

[0672] The called party's identifier (such as a phone number);

[0673] Should we use the new call capability?

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

[0675] Media information for this new call (e.g., the audio, video, and data channel receiving addresses and ports to be used in this call);

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

[0677] Optionally, the network function can also send a second message to the application side, wherein the second message is used to indicate whether the first message was successful.

[0678] Optionally, the network function can also send service configuration information for the new call to the first network element (such as DCSF) and receive a third message from the first network element. This response may include call profile setting results, a list of successfully set mini-programs, etc. DCSF can also be called a new call media capability platform, or it may be part of the call AS. Alternatively, the network function can also determine the information of the mini-programs that the application side can choose to use in the new call based on the application side's subscription information; that is, the information of the mini-programs that can be selected for use in subsequent processes.

[0679] In this scenario, the network function can 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 and the terminal. The INVITE message includes one or more of the following:

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

[0681] SDP information for this new call;

[0682] Callee identifier.

[0683] The routable identifier of the application side within the IMS used in the new call is determined by the network function according to a first correspondence, which is the correspondence between the application side's identifier and the routable identifier within the IMS used in the new call. The routable identifier of the application side within the IMS of the new call can be assigned by the network function, such as by randomly selecting from a number pool possessed by the network function, or by generating a routable third-party ID by the network function according to a specific algorithm.

[0684] The SDP information for this new call can be generated by the network function based on media information such as the audio, video, and data channel receiving address and port used in this call plan. This SDP information can be an SDP offer.

[0685] In this embodiment of the application, the telephone number may include a SIP Uniform Resource Identifier (URI), Tel URI, etc.

[0686] Optionally, establishing a new call between the application side and the terminal based on the first message may include:

[0687] Send a message or request to the IP Multimedia Subsystem (IMS) used by the new call, where the message or request can be an INVTIE, API, or other type of message or request.

[0688] Optionally, the network function can also receive a fourth message sent by IMS for the new call, wherein the fourth message includes SDP information. The fourth message can be something like 200 OK, and the SDP information can be an 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 can be an Application Programming Interface (API) or a capability open interface, or implemented using other protocols. Afterwards, the network function can execute the mini-program list and / or mini-program download process.

[0689] The first information includes one or more of the following:

[0690] The application-side identifier in this new call (which may be a private identifier, etc.);

[0691] The called party's identifier (such as a phone number);

[0692] Should we use the new call capability?

[0693] The service configuration information for this new call (such as a list of mini-programs that can be used in this call or subsequent calls of the same type);

[0694] Media information for this new call (audio, video, and data channel receiving address and port of the called terminal A in this call, etc.);

[0695] Session ID.

[0696] II. Terminal-side proactive initiation

[0697] In this scenario, the terminal executes the standard new call setup procedure. The initial INVITE request sent by the terminal to the IMS used for the new call (also referred to as the new call IMS) includes an SDP offer generated based on media information such as the audio, video, and data channel receive address ports planned for this session. In this case, the IMS used for the new call establishes the new call based on this INVITE request. The first message is sent by the IMS used for the new call, and this first message includes the SDP information for this new call, such as the SDP offer.

[0698] When establishing a new call, the network function generates second information based on the first message and sends a fourteenth message to the application side. This fourteenth message establishes a new call between the terminal and the application side and includes the second information. Subsequently, the network function may receive a sixth message sent by the application side, indicating the result of this new call establishment.

[0699] 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 was successful.

[0700] The second piece of information may be an API or capability open interface, or implemented using other protocols, including one or more of the following:

[0701] The identifier of the calling terminal (such as telephone number);

[0702] The identifier on the application side in this new call (an identifier that can be routed in IMS, such as a phone number);

[0703] Should we use the new call capability?

[0704] Media information for this new call (audio, video, and data channel receiving address and port of the calling terminal in this call, etc.).

[0705] The sixth message includes one or more of the following:

[0706] Should we use the new call capability?

[0707] The service configuration information for this new 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 when the caller A is 10086, etc.).

[0708] Media information regarding this new call;

[0709] Call event notification address.

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

[0711] Optionally, the network function can also notify the home network of data channel-related events and reserve media, and send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information, such as an SDP answer. Afterwards, the network function executes the mini-program list and / or mini-program download process.

[0712] In both of these methods, the network function can send call setup process events, such as the called party's ringing information, to the application side.

[0713] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network.

[0714] Optionally, based on the above embodiments, the network function can also establish an Application Data Channel (ADC) between the application side and the terminal. The network function can receive a fifteenth message, wherein the fifteenth message is used to request the establishment of the application data channel between the application side and the terminal. Subsequently, the network function can establish the application data channel between the application side and the terminal according to the fifteenth message.

[0715] Similarly, the establishment of this ADC can be initiated by the application side or by the terminal side.

[0716] I. Application side initiates the establishment of a new call ADC

[0717] 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:

[0718] The application-side identifier in this new call (which may be a private identifier, etc.);

[0719] The called party's identifier (such as a phone number);

[0720] Should we use the new call capability?

[0721] The service configuration information for this new call (such as a list of mini-programs that can be used in this call or subsequent calls of the same type);

[0722] Media information for this new call (media information such as the audio, video, and data channel receiving address and port to be used in this call);

[0723] Call event notification address (used for various event notifications related to call establishment on the application side);

[0724] Session ID.

[0725] 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 was successful.

[0726] During the process of initiating the establishment of the ADC on the application side, the network function can send a re-INVITE message to the IMS used for the new call. 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:

[0727] The application side uses routable identifiers (such as phone numbers, routable third-room IDs, etc.) within the IMS used in the new call;

[0728] The SDP information for this new call, such as the SPP offer, is generated based on media information such as the audio, video, and data channel receiving address and port used by this application's data channel plan.

[0729] Session ID.

[0730] The routable identifier in the IMS used by the application side in the new call is determined by the network function according to the first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[0731] Optionally, the network function can also receive a tenth message (e.g., 200 OK) sent by IMS for a new call, wherein the tenth message includes SDP information (e.g., SDP answer). The network function can 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, used to indicate the result of the application data channel establishment and to establish an application data channel with the terminal.

[0732] This third piece of information can be an API or capability open interface, or implemented using other protocols.

[0733] II. The process of the terminal initiating the establishment of ADC

[0734] In this process, the fifteenth message is the fifteenth message sent by the IMS used for the new call. The fifteenth message includes the SDP information of this new call (such as the SDP offer generated based on the media information such as audio, video, and data channel receive address ports to be used by this application data channel, carried according to the application data channel request). When establishing the ADC between the application side and the terminal based on the fifteenth message, the network function generates the fourth information based on the fifteenth message and sends the sixteenth message to the application side. The sixteenth message is used to establish the application data channel between the terminal and the application side and includes the fourth information. The network function also receives the twelfth message sent by the application side, which indicates the result of the data channel establishment.

[0735] The fourth piece of information may be an API or capability open interface, or implemented using other protocols, including one or more of the following:

[0736] The application-side identifier in this new call (which may be a private identifier, etc.);

[0737] The called party's identifier (such as a phone number);

[0738] Media information for this new call (media information such as audio, video, and data channel receiving address and port to be used in this application data channel plan);

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

[0740] The twelfth message includes one or more of the following:

[0741] The application-side routable identifier (such as phone number, routable application-side ID, etc.) is used in the IMS for the new call;

[0742] SDP information, such as the SDP answer, is generated based on media information such as the audio, video, and data channel receive address and port that the application data channel plans to use, as carried in the application data channel request.

[0743] In this embodiment of the disclosure, the application side or the network side may also terminate the new call.

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

[0745] When a new call is terminated on the terminal side, the network function receives a SIP BYE sent by the terminal, maps the SIP BYE to a fifth message, and sends the fifth message to the application side. Subsequently, the network function receives a response sent by the application side, maps the response to a SIP response, and sends the SIP response to the terminal.

[0746] In this embodiment of the disclosure, the network function may also 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. Subsequently, 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, this response may include the query result of the new call session (success, failure, etc., including the reason for failure if it is a failure), the two parties to the new call, a list of available mini-programs, the call setup time, etc.

[0747] Referring to Figure 3, which is a flowchart of a request processing method in an embodiment of this disclosure, applied to the application side, it includes:

[0748] Step 301: Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal. The meaning and interpretation of the first message can be found in the description of the foregoing method embodiments.

[0749] 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 was successful.

[0750] Optionally, the application side may also receive a fifth message sent by the network function, wherein the fifth message includes first information. The meaning and interpretation of the first information can be found in the description of the foregoing method embodiments.

[0751] Optionally, the application side may also receive call setup process events sent by the network function.

[0752] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network.

[0753] Optionally, based on the above embodiments, during the process of the application side actively initiating the establishment of the ADC between itself 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 explanation of the fifteenth message can be referred to the description of the foregoing method embodiments. 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 was successful.

[0754] 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 the establishment of the application data channel.

[0755] Optionally, based on the above embodiments, during the process of the terminal actively initiating the establishment of the ADC between itself and 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 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 data channel establishment.

[0756] The fourth piece of information includes one or more of the following:

[0757] The application's identifier in this new call;

[0758] Callee identifier;

[0759] Media information regarding this new call;

[0760] Call event notification address.

[0761] The twelfth message includes one or more of the following:

[0762] The application side has a routable identifier in the IMS used in the new call;

[0763] SDP information.

[0764] For further explanation of the fourth and twelfth messages, please refer to the description of the foregoing method embodiments.

[0765] Optionally, the application can also initiate the termination of the new call. Specifically, the application can send a seventeenth message to the network function, wherein the seventeenth message is used to terminate the new call between the application and the terminal, and the application receives a response from the network function.

[0766] Optionally, the terminal can also initiate the 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.

[0767] 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. Subsequently, 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.

[0768] Referring to Figure 4, which is a flowchart of a request processing method in an embodiment of this disclosure, applied to the application side, it includes:

[0769] Step 401: 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 second information.

[0770] The second information includes one or more of the following:

[0771] The identifier of the calling terminal;

[0772] The application's identifier in this new call;

[0773] Should we use the new call capability?

[0774] Media information regarding this new call;

[0775] Session ID.

[0776] For further explanation of the second information, please refer to the description of the foregoing method embodiments.

[0777] Step 402: Send a sixth message to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0778] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network.

[0779] 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 the establishment of the application data channel.

[0780] Optionally, based on the above embodiments, the application side may also send a seventh message to the network function, wherein the seventh message is used to indicate whether the fourteenth message was successful. The application side may also receive a call setup process event sent by the network function.

[0781] Optionally, based on the above embodiments, 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. This sixteenth message is used to establish an application data channel between the terminal and the application side and includes 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 the data channel establishment.

[0782] The fourth piece of information includes one or more of the following:

[0783] The application's identifier in this new call;

[0784] Callee identifier;

[0785] Media information regarding this new call;

[0786] Call event notification address.

[0787] The twelfth message includes one or more of the following:

[0788] The application side has a routable identifier in the IMS used in the new call;

[0789] SDP information.

[0790] Optionally, during 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.

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

[0792] 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.

[0793] Referring to Figure 5, which is a flowchart of a request processing method in an embodiment of this disclosure, applied to an IMS used for a new call, it includes:

[0794] Step 501: Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side. The first message includes SDP information for this new call. For an explanation of the SDP information, please refer to the description in the foregoing embodiments.

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

[0796] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network.

[0797] Referring to Figure 6, which is a flowchart of a request processing method in an embodiment of this disclosure, applied to a terminal, it includes:

[0798] Step 601: Send an INVITE request to the IMS used for the new call, so that the IMS used for the new call can send a first message to the network function.

[0799] The meaning of the first message can be found in the description of the aforementioned method embodiments.

[0800] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[0801] In this embodiment of the disclosure, the network function can establish a new call between the application side and the network based on the first message, thereby realizing the establishment of a new call between the application side and the network.

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

[0803] Optionally, during 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.

[0804] The following describes the specific implementation process of the embodiments of this disclosure in detail with reference to the system shown in Figure 1. The application side is described using third-party applications or users in vertical industries as examples, and the network function is described using the 5G new voice enablement layer as an example.

[0805] Under this system architecture, when third-party applications or users in vertical industries initiate a new call with a terminal by calling the 5G new call enablement layer capability open interface, the bootstrap data channel (BDC) process is shown in Figure 7. This process may include:

[0806] 1) Third-party applications or users in vertical industries (such as APP, application server, web page, enterprise IPPBX and other devices) call the 5G new call enablement layer capability open interface to send a new call establishment request (eMMTel API request) to the 5G new call enablement layer.

[0807] The request may include the caller's identifier (which may be a private identifier, etc.) of the user in the call from a third-party application or vertical industry, the called terminal (A) user identifier (such as a phone number, etc.), whether new call capabilities are being used, the call profile (such as a list of mini-programs that can be used in this call or subsequent calls of the same type), media information such as the audio, video and data channel receiving address and port to be used in this call, and the call event notification address (used for various event notifications related to the establishment of third-party calls), etc.

[0808] 1')(Optional) The 5G new call enabling layer replies to users such as third-party applications or vertical industries with a new call establishment response. This response includes information such as whether the new call establishment request was successful. (This only indicates that the call request was successful, and does not mean that the call has been finally established).

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

[0810] 3) The new call enablement layer initiates a call session, generates an SDP, and maintains the session state.

[0811] The 5G New Call Enablement Layer generates an INVITE request based on the parameters carried in the new call establishment request. This request is sent by a third-party application or vertical industry user whose caller ID (which may be a private identifier) ​​for this call is converted into a routable identifier within the IMS (such as a phone number or a routable third-party ID). The 5G New Call Enablement Layer maintains the mapping between the caller ID (which may be a private identifier) ​​and the routable identifiers within the IMS. Routable identifiers within the IMS can be assigned by the 5G New Call Enablement Layer, such as by randomly selecting from its number pool or by generating routable third-party IDs according to a specific algorithm. The INVITE request also includes an SDP offer generated based on media information such as the audio, video, and data channel receive address ports used in this call plan, as carried in the new call establishment request. Additionally, it may carry other information that should be included in the new call signaling.

[0812] 4) The 5G New Call Enablement Layer sends the INVITE request generated in step 3 to the 5G New Call IMS.

[0813] 5) If the IMS determines that a new call needs to use a DC, it will perform DCSF discovery.

[0814] If the IMS identifies that the INVITE request contains media information related to the new call, and that users such as third-party applications or vertical industries have subscribed to the new call service, then it determines that the call needs to be established as a new call, and the INVITE request needs to be routed to DCSF.

[0815] Steps 6-13 follow a standard procedure for DC-related event notifications and media reservations. In this step, DCSF and DCMF determine which mini-programs terminal A and third-party applications or vertical industry users can use during this call based on the call profile obtained in step 2.

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

[0817] 14) After completing the DC-related event notification and media reservation processes, the new call IMS will send an INVITE request containing the SDP offer to the called terminal A's home network.

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

[0819] 16) The called network and the calling side complete the necessary 18X / PRACK / UPDATE / 200OK procedures.

[0820] 17) The called network replies with a 200 OK to the calling side. The 200 OK includes an SDP answer from the called side, containing media information such as the audio, video and data channel receiving address ports to be used by the called terminal A in this call.

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

[0822] 20) The new call IMS will reply with 200 OK to the 5G new call enablement layer.

[0823] 21) The 5G new call enabling layer generates corresponding API content based on the previously maintained 5G new call session information, the received 200 OK and the SDP answer contained therein, and sends an eMMTel API called success request to users such as third-party applications or vertical industries. This API includes the caller's identifier (which may be a private identifier, etc.), the called terminal (A) user identifier (such as a phone number), whether the new call capability is used, the call profile (such as a list of mini-programs that can be used in this call or subsequent similar calls), and media information such as the audio, video and data channel receiving addresses and ports of the called terminal A in this call.

[0824] If step 1') did not exist previously, the above information is included in the new called success request generated by the 5G new call enablement layer. If step 1') did exist previously, the above information is included in the new call response. If the above information is included in the called success request, users such as third-party applications or vertical industries reply with a called success response, which includes whether the called success request was successful.

[0825] 22) Establishment of DC1 from the 5G new call enablement layer to the local network, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 2 can be retrieved here to determine which mini-programs terminal A can use for this call. If the enablement layer uses a Hypertext Transfer Protocol (HTTP) proxy method, DC1 can be directly established between third-party applications or vertical industry users and the local network.

[0826] 23) Establish a connection between terminal A and DC2 on the local network, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 2 can be retrieved here to determine which mini-programs terminal B can use in this call.

[0827] 24) Establishment of DC3 from the 5G new call enablement layer to the remote network, including the corresponding list of mini-programs and the 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 in this call. If the enablement layer uses an HTTP proxy method, DC3 can be directly established between the user and the remote network, such as third-party applications or vertical industries.

[0828] 25) Establish connection between terminal A and the remote network DC4, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 2 can be retrieved here to determine which mini-programs terminal B can use in this call.

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

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

[0831] 1-10) Standard new call setup procedure, used for calling party DC related event notifications and media reservations, etc. The initial INVITE request contains an SDP offer generated based on media information such as the audio, video, and data channel receive address ports to be used in this session.

[0832] 1) The terminal sends an INVITE request to the New Call IMS; 2) The New Call IMS determines that a DC (Digital Channel) needs to be used and performs DCSF (Digital Channel Default Search) discovery; 3) The New Call IMS sends Nimsas_SessionEventControl_Notify to the DCSF; 4) The DCSF determines whether 5G New Call can be used and the 5G New Call control policy; 5) The DCSF generates DC media information for the local and remote networks, including a list of mini-programs; 6) The 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 the DCMF / eMRF to reserve media resources required by the local and remote networks, and the DCMF / Enhance MRF to allocate media resources for the local and remote networks; 9) The New Call IMS sends a Nimsas_MediaControl_MediaInstruction response to the DCSF.

[0833] 11) The new call IMS routes the INVITE request to the 5G new call enablement layer based on the called number.

[0834] 12) The 5G New Call Enablement Layer generates corresponding API content based on the received INVITE and its contained SDP answer, and sends an eMMTel API request to users such as third-party applications or vertical industries. This API includes the calling terminal (A) identifier (e.g., phone number), the called party identifier for this call (an identifier that can be routed in IMS, such as a phone number), whether the new call capability is used, and media information such as the audio, video, and data channel receiving address ports of the called terminal A in this call. This API content is included in the new call request generated by the 5G New Call Enablement Layer. The 5G New Call Enablement Layer maintains this INVITE state and maintains subsequently established sessions. The 5G New Call Enablement Layer maintains the mapping relationship between the called party identifier (an identifier that can be routed in IMS, such as a phone number) and the calling party identifier (which may be a private identifier) ​​for this call. Third-party applications or vertical industry users can immediately return a new call response. If a new call response is returned, this response only indicates whether the new call request was successful, and does not mean that the new call was ultimately successfully established.

[0835] 13) The 5G new call enablement layer acts as a session endpoint, maintains session state, and generates APIs.

[0836] 14) After a call is established between the 5G New Call Enablement Layer and users such as third-party applications or vertical industries, the third-party application or vertical industry user requests a successful call establishment request, or if no new call response is returned in step 12), the result of this call establishment is carried in the returned new call response. This successful call establishment request or new call response contains relevant information about this call, including whether the new call capability is used, the call profile (such as a list of mini-programs that can be used in this call or subsequent calls of the same type), media information such as the audio, video, and data channel receiving address ports to be used in this call, and the call event notification address (used for various event notifications related to the establishment of third-party calls), etc.

[0837] 15)(Optional) Based on the steps 12 and 13, the 5G new call enabling layer notifies the DCSF of the call profile related to this call (such as a list of mini-programs that can be used by number A, or a list of mini-programs that can be used for a certain type of call, such as when the caller A is 10086). It should be noted that the DCSF response can be omitted here; this response may contain the call profile setting result, a list of successfully set mini-programs, etc. If this step is not performed, the normal new call establishment process will proceed, determining the mini-programs that can be used in this third-party call based on the caller A's and the subscription information of third-party applications or vertical industry users.

[0838] 16) The 5G new call enabling layer and the home network shall notify DC-related events and reserve media, etc.

[0839] 17) The called network and the calling side complete the necessary 18X / PRACK / UPDATE / 200OK procedures.

[0840] 18) The 5G new call enabling layer replies to the calling side with a 200 OK response 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 audio, video and data channel receiving address ports, etc., which are planned to be used by users such as third-party applications or vertical industries.

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

[0842] 21) The new call IMS will reply with 200 OK to the calling terminal A.

[0843] 22) Establish connection between terminal A and DC1 on the local network, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 15 can be retrieved here to determine which mini-programs terminal A can use in this call.

[0844] 23) Establishment of DC2 between the 5G new call enablement layer and the local network, including the corresponding list of mini-programs and the mini-program download process. Here, only the call profile obtained in step 15 can be retrieved to determine which mini-programs terminal B can use for this call. If the enablement layer uses an HTTP proxy, DC2 can be directly established between third-party applications or vertical industry users and the local network.

[0845] 24) Establish connection between terminal A and the remote network DC3, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 15 can be retrieved here to determine which mini-programs terminal A can use in this call.

[0846] 25) Establishment of DC4 from the 5G new call enablement layer to the remote network, including the corresponding list of mini-programs and the mini-program download process. Only the call profile obtained in step 15 can be retrieved here to determine which mini-programs terminal B can use in this call. If the enablement layer uses an HTTP proxy, DC4 can be directly established between the user (e.g., a third-party application or a vertical industry user) and the remote network.

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

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

[0849] 1) Third-party applications or users in vertical industries (such as APP, application server, web page, enterprise IPPBX and other devices) have established new call sessions using the method shown in Figure 7 or Figure 8 above.

[0850] 2) Third-party applications or vertical industry users call the 5G New Call Enablement Layer capability open interface to send an application data channel establishment request (eMMTel API ADC establishment request) to the 5G New Call Enablement Layer. This request may include the caller's identifier (which may be a private identifier, etc.), the called terminal (A) user identifier (such as a phone number, etc.), whether the new call capability is used, the call profile (such as a list of mini-programs that can be used in this call or subsequent calls of the same type), the media information such as the audio, video and data channel receiving address and port to be used in this call, and the call event notification address (used for various event notifications related to the establishment of third-party calls), etc.

[0851] 1')(Optional) The 5G New Call Enablement Layer replies to third-party applications or vertical industry users with an API response to establish an application data channel. This response includes information such as whether the application data channel establishment request was successful (this only indicates that the call request was successful, and does not mean that the application data channel has been finally established).

[0852] 3) The 5G new call enablement layer updates the call session, generates SDP, and maintains the session state.

[0853] The 5G new call enabling layer generates a re-INVITE request based on the parameters carried in the new call establishment request. The sender of this request converts the caller's identifier (which may be a private identifier) ​​from a third-party application or vertical industry user for this call into a routable identifier within IMS (such as a phone number or a routable third-party room ID), based on the mapping relationship saved during new call establishment. This re-INVITE request also includes an SDP offer generated based on media information such as audio, video, and data channel receive address ports planned for use by the application data channel, as carried in the application data channel request. Additionally, it may carry other information that should be included in the new call signaling.

[0854] 4-16) The setup process is the same as for a standard ADC. Wherein:

[0855] In step 4), the 5G New Call Enablement Layer sends a reINVITE request to the New Call IMS; in step 5), the New Call IMS determines that a DC needs to be used and performs DCSF discovery; in step 6), the New Call IMS sends Nimsas_SessionEventControl_Notify to the DCSF; in step 7), the DCSF determines whether 5G New Call can be used and the 5G New Call control policy; in step 8), the DCSF generates DC media information for both the local and remote networks, including a list of mini-programs; in step 9), the DCSF sends Nimsas_SessionEventControl_Notify_response to the New Call IMS; in step 10), the New Call IMS sends a re-INVITE (SDP with audio / video and Bootstrap DC offer) to the terminal; in step 11), the called network negotiates; in step 12), the terminal sends a 200 OK (SDP with audio / video and Bootstrap DC) to the New Call IMS. 13) The new call IMS sends Nimsas_SessionEventControl_Notify to the DCSF; 14) The DCSF sends Nimsas_SessionEventControl_Notify response to the new call IMS; 15) Execute QoS flow; 16) The new call IMS sends 200 OK to the 5G new call enablement layer.

[0856] 17) The 5G new call enablement layer acts as a session endpoint, maintains session state, and generates APIs.

[0857] 18) After a call is established between the 5G New Call Enablement Layer and users such as third-party applications or vertical industries, the 5G New Call Enablement Layer will send an Application Data Channel Establishment Success Request (eMMTel API Call Success Request) or, if no new call response is returned in step 2), the Application Data Channel Establishment Response will include the result of this Application Data Channel establishment. This Application Data Channel Establishment Success Request or Application Data Channel Establishment Response contains relevant information about this call, such as media information like the audio, video, and data channel receiving address and port used by this Application Data Channel.

[0858] (19-20) The setup process is the same as that of a standard ADC.

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

[0860] 1-8) The setup process is the same as that of a standard ADC.

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

[0862] 9) The 5G new call enablement layer acts as a session endpoint, maintains session state, and generates APIs.

[0863] 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 this request converts a routable identifier (such as a phone number, routable third-party room ID, etc.) that can be within IMS into the caller's identifier (which may be a private identifier, etc.) for the user of a third-party application or vertical industry, based on the mapping relationship saved during the new call establishment. This data channel establishment request also includes an SDP offer generated based on the media information such as audio, video, and data channel receiving address ports planned for use by this application data channel, carried in the application data channel request. In addition, it may carry other information that should be carried in the new call signaling.

[0864] 11) Third-party applications or vertical industry users call the 5G New Call Enablement Layer Capability Open Interface and send a data channel establishment response (eMMTel API response) to the 5G New Call Enablement Layer. This response may include the caller's identifier (which may be a private identifier, etc.), the called terminal (A) user identifier (such as a telephone number), the media information such as the audio, video and data channel receiving address port to be used by the application's data channel, and the call event notification address (used for various event notifications related to the establishment of third-party calls), etc.

[0865] 12) The 5G new call enablement layer generates SDP answers to update and maintain the session.

[0866] The 5G new call enabling layer generates a 200 OK response based on the parameters carried in the data channel establishment response. The sender of this response converts the caller's identifier (which may be a private identifier) ​​from a third-party application or vertical industry user for this call into a routable identifier within IMS (such as a phone number or a routable third-party ID), based on the mapping relationship saved during the new call establishment. This 200 OK request also includes an SDP answer generated based on media information such as audio, video, and data channel receive address and port information planned for use by the application data channel, as carried in the application data channel request. Additionally, it carries other information that should be included in the new call signaling.

[0867] (13-20) The setup process is the same as that of a standard ADC.

[0868] In step 13), the 5G New Call Enablement Layer negotiates; in step 14), the 5G New Call Enablement Layer sends 200 OK to the New Call IMS; in step 15), the New Call IMS sends Nimsas_SessionEventControl_Notify to the DCSF; in step 16), the DCSF sends Nimsas_SessionEventControl_Notify response to the New Call IMS; in step 17), the QoS flow is executed; in step 18), the New Call IMS sends 200 OK to the terminal; in step 19), the terminal and the 5G New Call Enablement Layer ACK; in step 20), the ADC is established, and data exchange occurs within the ADC.

[0869] Optionally, in this embodiment of the disclosure, the application side can terminate the new call. Specifically, when the application side terminates the new call, third-party applications or users in vertical industries call the 5G New Call Enablement Layer Capability Open Interface to send a call termination request. This request includes the session identifier to be terminated (such as Session ID). The 5G New Call Enablement Layer maps this to SIP BYE, and when the terminal returns a response, it maps it to the corresponding capability open interface API response.

[0870] Optionally, in this embodiment of the disclosure, the terminal terminates the new call. Specifically, the terminal terminates the new call process the same as the general call termination process. When the SIP BYE sent to a user such as a third-party application or vertical industry reaches the 5G new call enablement layer, the enablement layer maps it to the corresponding API, and the reverse confirmation is mapped from the API to the corresponding SIP response.

[0871] Optionally, in this embodiment, third-party applications or users in vertical industries can also query the status of new calls. The process of querying the new call flow between the terminal and the application by calling the 5G new call enablement layer capability open interface is shown in Figure 11a. This process may include:

[0872] 1) Third-party applications or users in vertical industries (such as APP, application server, web page, enterprise IPPBX and other devices) call the 5G new call enablement layer capability open interface to send a query new call request (eMMTel API request) to the 5G new call enablement layer. This request may include information such as call session ID.

[0873] 2) The 5G new call enabling layer replies to the response corresponding to the query for the new call to users such as third-party applications or vertical industries. The response may include the result of the query for the new call session (success, failure, etc., and if it is a failure, the reason for the failure), the two parties to the call (terminal A and third-party applications or vertical industry users), the list of available mini-programs (obtained from the response of step 2 in Figure 7 or step 14 in Figure 8), the call establishment time, and other information.

[0874] Optionally, as shown in FIG11b, the request processing method in this embodiment of the present disclosure may include the following process:

[0875] 1) The Application sends an application call establishment request to the MMTel Enabler Server; for details of this step, please refer to step 1 in Figure 7.

[0876] 2) The MMTel Enabler Server and IMS Core Network process requests.

[0877] 3) The MMTel Enabler Server returns an application call establishment response to the Application. For details on this step, please refer to step 1 in Figure 7.

[0878] As can be seen from the above description, the solution of this disclosure embodiment realizes the establishment of a new call between the application side and the terminal, the establishment of the ADC process, etc. For the terminal, this disclosure embodiment is also applicable to terminals that do not support IMS or mobile number codes to use 5G new calls through the solution of this disclosure embodiment.

[0879] Referring to Figure 12, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to network functions. As shown in Figure 12, the request processing apparatus includes:

[0880] The first receiving module 1201 is used to receive a first message, wherein the first message is used to request the establishment of 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.

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

[0882] The application's identifier in this new call;

[0883] Callee identifier;

[0884] Should we use the new call capability?

[0885] Service configuration information for this new call;

[0886] Media information regarding this new call;

[0887] Call event notification address.

[0888] Optionally, the device further includes:

[0889] A 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 was successful.

[0890] Optionally, the device further includes:

[0891] The second sending module is used to send the service configuration information of this new call to the first network element; and to receive the third message sent by the first network element.

[0892] or,

[0893] The second processing module is used to determine the information of the mini-program that the application side can use in this new call based on the subscription information of the application side.

[0894] Optionally, the first processing module is further configured to:

[0895] Send an invitation INVITE message 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.

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

[0897] The application-side routable identifier within the new call IMS;

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

[0899] Callee identifier.

[0900] Optionally, the device further includes:

[0901] The second receiving module is used to receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information;

[0902] The first generation module is used to generate first information based on the fourth message;

[0903] The third sending module is used to send a fifth message to the application side, wherein the fifth message includes the first information;

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

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

[0906] The application's identifier in this new call;

[0907] Callee identifier;

[0908] Should we use the new call capability?

[0909] Service configuration information for this new call;

[0910] Media information regarding this new call;

[0911] Session identifier.

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

[0913] Optionally, the first processing module is further configured to:

[0914] Generate second information based on the first message;

[0915] Send 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;

[0916] Receive a sixth message sent by the application side, wherein the sixth message is used to indicate the result of the establishment of this new call.

[0917] Optionally, the device further includes:

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

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

[0920] The identifier of the calling terminal;

[0921] The application's identifier in this new call;

[0922] Should we use the new call capability?

[0923] Media information regarding this new call;

[0924] Session identifier.

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

[0926] Should we use the new call capability?

[0927] Service configuration information for this new call;

[0928] Media information regarding this new call;

[0929] Call event notification address.

[0930] Optionally, the device further includes:

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

[0932] Optionally, the device further includes:

[0933] The fifth processing module is used for data channel-related event notification and media reservation with the home network;

[0934] The fifth sending module is used to send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

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

[0936] Optionally, the device further includes:

[0937] The fifth sending module is used to send call setup process events to the application side.

[0938] Optionally, the device further includes:

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

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

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

[0942] The application's identifier in this new call;

[0943] Callee identifier;

[0944] Should we use the new call capability?

[0945] Service configuration information for this new call;

[0946] Media information regarding this new call;

[0947] Call event notification address;

[0948] Session identifier.

[0949] Optionally, the device further includes:

[0950] 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 was successful.

[0951] Optionally, the eighth processing module is further configured to:

[0952] 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.

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

[0954] The application side has a routable identifier in the IMS used in the new call;

[0955] SDP information for this new call;

[0956] Session identifier.

[0957] Optionally, the routable identifier in the IMS used by the application side in the new call is determined by the network function according to a first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[0958] Optionally, the device further includes:

[0959] The fifth receiving module is used to receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

[0960] The second generation module is used to generate third information based on the tenth message;

[0961] The seventh sending module is used to send an eleventh message to the application side, wherein the eleventh message includes the third information, which is used to indicate the result of the application data channel establishment;

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

[0963] Optionally, 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 this new call.

[0964] Optionally, the eighth processing module is further configured to:

[0965] Generate the fourth information based on the fifteenth message;

[0966] Send 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;

[0967] Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[0969] The application's identifier in this new call;

[0970] Callee identifier;

[0971] Media information regarding this new call;

[0972] Call event notification address.

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

[0974] The application side has a routable identifier in the IMS used in the new call;

[0975] SDP information.

[0976] Optionally, the device further includes:

[0977] The sixth receiving module is used to receive 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;

[0978] The first mapping module is used to map the seventeenth message to a SIP BYE and send the SIP BYE to the terminal.

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

[0980] Optionally, the device further includes:

[0981] The eighth receiving module is used to receive the SIP BYE sent by the terminal, map the SIP BYE to the fifth message, and send the fifth message to the application side.

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

[0983] Optionally, the device further includes:

[0984] The ninth receiving module is used to receive the 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;

[0985] The 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.

[0986] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0987] Referring to Figure 13, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to the application side. As shown in Figure 13, the request processing apparatus includes:

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

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

[0990] The application's identifier in this new call;

[0991] Callee identifier;

[0992] Should we use the new call capability?

[0993] Service configuration information for this new call;

[0994] Media information regarding this new call;

[0995] Call event notification address.

[0996] Optionally, the device further includes:

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

[0998] Optionally, the device further includes:

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

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

[1001] The application's identifier in this new call;

[1002] Callee identifier;

[1003] Should we use the new call capability?

[1004] Service configuration information for this new call;

[1005] Media information regarding this new call;

[1006] Session identifier.

[1007] Optionally, the device further includes:

[1008] The third receiving module is used to receive the call setup process event sent by the network function.

[1009] Optionally, the device further includes:

[1010] The second sending module is used to 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.

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

[1012] The application's identifier in this new call;

[1013] Callee identifier;

[1014] Should we use the new call capability?

[1015] Service configuration information for this new call;

[1016] Media information regarding this new call;

[1017] Call event notification address.

[1018] Optionally, the device further includes:

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

[1020] Optionally, the device further includes:

[1021] The fifth receiving module is used to receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

[1022] Optionally, the device further includes:

[1023] The sixth receiving module is used to receive the 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;

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

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

[1026] The application's identifier in this new call;

[1027] Callee identifier;

[1028] Media information regarding this new call;

[1029] Call event notification address.

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

[1031] The application side has a routable identifier in the IMS used in the new call;

[1032] SDP information.

[1033] Optionally, the device further includes:

[1034] The fourth sending module is used 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;

[1035] The seventh receiving module is used to receive the response sent by the network function.

[1036] The eighth receiving module is used to receive the fifth message sent by the network function and send a response to the network function.

[1037] The fifth sending module is used to 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;

[1038] The ninth receiving module is used to receive the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

[1039] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1040] Referring to Figure 14, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to the application side. As shown in Figure 14, the request processing apparatus includes:

[1041] The first receiving module 1401 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 second information;

[1042] 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 the establishment of this new call.

[1043] Optionally, the device may further include:

[1044] 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 was successful.

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

[1046] The identifier of the calling terminal;

[1047] The application's identifier in this new call;

[1048] Should we use the new call capability?

[1049] Media information regarding this new call;

[1050] Session identifier.

[1051] Optionally, the device further includes:

[1052] The second receiving module is used to receive the call setup process event sent by the network function.

[1053] Optionally, the device further includes:

[1054] The third receiving module is used to receive the 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 fourth information;

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

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

[1057] The application's identifier in this new call;

[1058] Callee identifier;

[1059] Media information regarding this new call;

[1060] Call event notification address.

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

[1062] The application side has a routable identifier in the IMS used in the new call;

[1063] SDP information.

[1064] Optionally, the device further includes:

[1065] The fifth sending module is used 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;

[1066] The fourth receiving module is used to receive the response sent by the network function.

[1067] Optionally, the device further includes:

[1068] The fifth receiving module receives the fifth message sent by the network function and sends a response to the network function.

[1069] Optionally, the device further includes:

[1070] The sixth sending module is used to 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;

[1071] The sixth receiving module receives the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

[1072] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1073] Referring to Figure 15, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to IMS for new calls. As shown in Figure 15, the request processing apparatus includes:

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

[1075] Optionally, the first message includes the SDP information for this new call.

[1076] Optionally, the device further includes:

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

[1078] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1079] Referring to Figure 16, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to a terminal. As shown in Figure 16, the request processing apparatus includes:

[1080] 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.

[1081] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[1082] Optionally, the device further includes:

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

[1084] Optionally, the device further includes:

[1085] 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.

[1086] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1087] Referring to Figure 17, which is a structural diagram of a request processing device provided in an embodiment of this disclosure, applied to a terminal. As shown in Figure 17, the request processing device includes: a processor 1701 and a transceiver 1702;

[1088] The transceiver 1702 is used to receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal;

[1089] The processor 1701 is used to establish a new call between the application side and the terminal based on the first message.

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

[1091] The application's identifier in this new call;

[1092] Callee identifier;

[1093] Should we use the new call capability?

[1094] Service configuration information for this new call;

[1095] Media information regarding this new call;

[1096] Call event notification address.

[1097] Optionally, the transceiver 1702 is further configured to:

[1098] A second message is sent to the application side, wherein the second message is used to indicate whether the first message was successful.

[1099] Optionally, the processor 1701 is further configured to:

[1100] Send the service configuration information for this new call to the first network element; receive the third message sent by the first network element;

[1101] or,

[1102] Based on the subscription information of the application side, the information of the mini-program that the application side can use in this new call is determined.

[1103] Optionally, the processor 1701 is further configured to:

[1104] Send an invitation INVITE message 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.

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

[1106] The application-side routable identifier within the new call IMS;

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

[1108] Callee identifier.

[1109] Optionally, the processor 1701 is further configured to:

[1110] Receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information;

[1111] First information is generated based on the fourth message;

[1112] Send a fifth message to the application side, wherein the fifth message includes the first information;

[1113] Execute the mini-program list and / or mini-program download process.

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

[1115] The application's identifier in this new call;

[1116] Callee identifier;

[1117] Should we use the new call capability?

[1118] Service configuration information for this new call;

[1119] Media information regarding this new call;

[1120] Session identifier.

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

[1122] Optionally, the processor 1701 is further configured to:

[1123] Generate second information based on the first message;

[1124] Send 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;

[1125] Receive a sixth message sent by the application side, wherein the sixth message is used to indicate the result of the establishment of this new call.

[1126] Optionally, the transceiver 1702 is further configured to:

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

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

[1129] The identifier of the calling terminal;

[1130] The application's identifier in this new call;

[1131] Should we use the new call capability?

[1132] Media information regarding this new call;

[1133] Session identifier.

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

[1135] Should we use the new call capability?

[1136] Service configuration information for this new call;

[1137] Media information regarding this new call;

[1138] Call event notification address.

[1139] Optionally, the transceiver 1702 is further configured to:

[1140] Send the service configuration information for this new call to the first network element.

[1141] Optionally, the processor 1701 is further configured to:

[1142] Notify the network of data channel-related events and reserve media access with the home network;

[1143] Send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information;

[1144] Execute the mini-program list and / or mini-program download process.

[1145] Optionally, the transceiver 1702 is further configured to:

[1146] Send a call setup process event to the application side.

[1147] Optionally, the processor 1701 is further configured to:

[1148] Receive the fifteenth message, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal;

[1149] The application data channel between the application side and the terminal is established according to the fifteenth message.

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

[1151] The application's identifier in this new call;

[1152] Callee identifier;

[1153] Should we use the new call capability?

[1154] Service configuration information for this new call;

[1155] Media information regarding this new call;

[1156] Call event notification address;

[1157] Session identifier.

[1158] Optionally, the transceiver 1702 is further configured to:

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

[1160] Optionally, the processor 1701 is further configured to:

[1161] 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.

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

[1163] The application side has a routable identifier in the IMS used in the new call;

[1164] SDP information for this new call;

[1165] Session identifier.

[1166] Optionally, the routable identifier in the IMS used by the application side in the new call is determined by the network function according to a first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

[1167] Optionally, the transceiver 1702 is further configured to:

[1168] Receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information;

[1169] Generate third information based on the tenth message;

[1170] Send an eleventh message to the application side, wherein the eleventh message includes the third information, used to indicate the result of the application data channel establishment;

[1171] Establish an application data channel with the terminal.

[1172] Optionally, 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 this new call.

[1173] Optionally, the processor 1701 is further configured to:

[1174] Generate the fourth information based on the fifteenth message;

[1175] Send 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;

[1176] Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[1178] The application's identifier in this new call;

[1179] Callee identifier;

[1180] Media information regarding this new call;

[1181] Call event notification address.

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

[1183] The application side has a routable identifier in the IMS used in the new call;

[1184] SDP information.

[1185] Optionally, the transceiver 1702 is further configured to:

[1186] Receive 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;

[1187] The seventeenth message is mapped to a SIP BYE, and the SIP BYE is sent to the terminal.

[1188] The system receives the response sent by the terminal, maps the response to a new response, and sends the response to the application side.

[1189] Optionally, the transceiver 1702 is further configured to:

[1190] Receive the SIP BYE sent by the terminal, map the SIP BYE to a fifth message, and send the fifth message to the application side;

[1191] The system receives a response from the application side, maps the response to a SIP response, and sends the SIP response to the terminal.

[1192] Optionally, the transceiver 1702 is further configured to:

[1193] Receive the 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;

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

[1195] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1196] Referring to Figure 18, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to the application side. As shown in Figure 18, the request processing apparatus includes: a processor 1801 and a transceiver 1802;

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

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

[1199] The application's identifier in this new call;

[1200] Callee identifier;

[1201] Should we use the new call capability?

[1202] Service configuration information for this new call;

[1203] Media information regarding this new call;

[1204] Call event notification address.

[1205] Optionally, the transceiver 1802 is further configured to:

[1206] Receive a second message sent by the network function, wherein the second message is used to indicate whether the first message was successful.

[1207] Optionally, the transceiver 1802 is further configured to:

[1208] Receive a fifth message sent by the network function, wherein the fifth message includes the first information.

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

[1210] The application's identifier in this new call;

[1211] Callee identifier;

[1212] Should we use the new call capability?

[1213] Service configuration information for this new call;

[1214] Media information regarding this new call;

[1215] Session identifier.

[1216] Optionally, the transceiver 1802 is further configured to:

[1217] Receive the call setup process event sent by the network function.

[1218] Optionally, the transceiver is also used for:

[1219] 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.

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

[1221] The application's identifier in this new call;

[1222] Callee identifier;

[1223] Should we use the new call capability?

[1224] Service configuration information for this new call;

[1225] Media information regarding this new call;

[1226] Call event notification address.

[1227] Optionally, the transceiver 1802 is further configured to:

[1228] Receive the ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message was successful.

[1229] Optionally, the transceiver 1802 is further configured to:

[1230] Receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

[1231] Optionally, the transceiver 1802 is further configured to:

[1232] Receive the 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;

[1233] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[1235] The application's identifier in this new call;

[1236] Callee identifier;

[1237] Media information regarding this new call;

[1238] Call event notification address.

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

[1240] The application side has a routable identifier in the IMS used in the new call;

[1241] SDP information.

[1242] Optionally, the transceiver 1802 is further configured to:

[1243] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[1244] Receive the response sent by the network function.

[1245] Optionally, the transceiver 1802 is further configured to:

[1246] Receive the fifth message sent by the network function and send a response to the network function.

[1247] Optionally, the transceiver 1802 is further configured to:

[1248] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[1250] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1251] Referring to Figure 19, which is a structural diagram of a request processing apparatus provided in an embodiment of this disclosure, applied to the application side. As shown in Figure 19, the request processing apparatus includes: a processor 1901 and a transceiver 1902;

[1252] The transceiver 1902 is 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; and to send a sixth message to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

[1253] Optionally, the transceiver 1902 is further configured to:

[1254] A seventh message is sent to the network function, wherein the seventh message is used to indicate whether the fourteenth message was successful.

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

[1256] The identifier of the calling terminal;

[1257] The application's identifier in this new call;

[1258] Should we use the new call capability?

[1259] Media information regarding this new call;

[1260] Session identifier.

[1261] Optionally, the transceiver 1902 is further configured to:

[1262] Receive the call setup process event sent by the network function.

[1263] Optionally, the transceiver 1902 is further configured to:

[1264] Receive the 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;

[1265] Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

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

[1267] The application's identifier in this new call;

[1268] Callee identifier;

[1269] Media information regarding this new call;

[1270] Call event notification address.

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

[1272] The application side has a routable identifier in the IMS used in the new call;

[1273] SDP information.

[1274] Optionally, the transceiver 1902 is further configured to:

[1275] Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal;

[1276] Receive the response sent by the network function.

[1277] Optionally, the transceiver 1902 is further configured to:

[1278] Receive the fifth message sent by the network function and send a response to the network function.

[1279] Optionally, the transceiver 1902 is further configured to:

[1280] Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal;

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

[1282] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1283] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

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

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

[1286] Optionally, the first message includes the SDP information for this new call.

[1287] Optionally, the transceiver 2002 is further configured to:

[1288] Receive the eighth message sent by the network function, wherein the eighth message includes SDP information.

[1289] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1290] Referring to Figure 21, which is a structural diagram of a request processing device provided in an embodiment of this disclosure, applied to a terminal. As shown in Figure 21, the request processing device includes: a processor 2101 and a transceiver 2102;

[1291] 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.

[1292] The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

[1293] Optionally, the transceiver 2102 is further configured to:

[1294] Receive the SIP BYE sent by the network function and send a response to the network function.

[1295] Optionally, the transceiver 2102 is further configured to:

[1296] Send a SIP BYE to the network function and receive a SIP response from the network function.

[1297] The apparatus provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[1298] It should be noted that the division of units in the embodiments of this disclosure is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[1299] If the integrated unit is implemented as 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 this disclosure, in essence, or the part that contributes to related technologies, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[1300] This disclosure provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program from the memory to implement the steps in the request processing method described above.

[1301] This disclosure also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described request processing method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., compact discs (CDs), digital video discs (DVDs), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor storage (e.g., ROMs, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND FLASH), solid-state drives (SSDs), etc.).

[1302] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[1303] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[1304] The embodiments of this disclosure have been described above with reference to the accompanying drawings. However, this disclosure is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this disclosure without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this disclosure.

Claims

1. A request processing method applied to a network function, the method comprising: Receive a first message, wherein the first message is used to request the establishment of a new call between the application side and the terminal; A new call is established between the application and the terminal based on the first message.

2. The method of claim 1, wherein, The first message is a message sent by the application side; wherein, the first message includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Call event notification address.

3. The method according to claim 2, further comprising: A second message is sent to the application side, wherein the second message is used to indicate whether the first message was successful.

4. The method according to claim 2, further comprising: Send the service configuration information for this new call to the first network element; Receive the third message sent by the first network element; or, Based on the subscription information of the application side, the information of the mini-program that the application side can use in this new call is determined.

5. The method of claim 2, wherein, The step of establishing a new call between the application side and the terminal based on the first message includes: Send an invitation INVITE message 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.

6. The method of claim 5, wherein, The INVITE message includes one or more of the following: The application-side routable identifier within the new call IMS; Session Description Protocol (SDP) information for this new call; Callee identifier.

7. The method according to claim 2, further comprising: Receive a fourth message sent by IMS for a new call, wherein the fourth message includes SDP information; First information is generated based on the fourth message; Send a fifth message to the application side, wherein the fifth message includes the first information; Execute the mini-program list and / or mini-program download process.

8. The method of claim 7, wherein, The first information includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Session identifier.

9. The method of claim 1, wherein, 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.

10. The method of claim 9, wherein, The step of establishing a new call between the application side and the terminal based on the first message includes: Generate second information based on the first message; Send 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 the result of the establishment of this new call.

11. The method according to claim 10, further comprising: Receive a seventh message from the application side, wherein the seventh message is used to indicate whether the first message was successful.

12. The method of claim 10, wherein, The second information includes one or more of the following: The identifier of the calling terminal; The application's identifier in this new call; Should we use the new call capability? Media information regarding this new call; Session identifier.

13. The method of claim 10, wherein, The sixth message includes one or more of the following: Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Call event notification address.

14. The method according to claim 12, further comprising: Send the service configuration information for this new call to the first network element.

15. The method according to claim 10, further comprising: Notify the network of data channel-related events and reserve media access with the home network; Send an eighth message to the IMS used by the new call, wherein the eighth message includes SDP information; Execute the mini-program list and / or mini-program download process.

16. The method according to any one of claims 2-15, wherein the method further comprises: Send a call setup process event to the application side.

17. The method according to claim 1, further comprising: Receive the fifteenth message, wherein the fifteenth message is used to request the establishment of an application data channel between the application side and the terminal; The application data channel between the application side and the terminal is established according to the fifteenth message.

18. The method of claim 17, wherein, The fifteenth message is the fifteenth message sent by the application side; wherein, the fifteenth message includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Call event notification address; Session identifier.

19. The method according to claim 18, further comprising: A ninth message is sent to the application side, wherein the ninth message is used to indicate whether the fifteenth message was successful.

20. The method of claim 18, wherein, The step of establishing an application data channel between the application side and the terminal according to the fifteenth message includes: 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.

21. The method of claim 20, wherein, The re-INVITE message includes one or more of the following: The application side has a routable identifier in the IMS used in the new call; SDP information for this new call; Session identifier.

22. The method of claim 6 or 21, wherein, The routable identifier in the IMS used by the application side in the new call is determined by the network function according to the first correspondence, which is the correspondence between the identifier of the application side and the routable identifier in the IMS used by the new call.

23. The method according to claim 18, further comprising: Receive the tenth message sent by the IMS used for the new call, wherein the tenth message includes SDP information; Generate third information based on the tenth message; Send an eleventh message to the application side, wherein the eleventh message includes the third information, which is used to indicate the result of the application data channel establishment; Establish an application data channel with the terminal.

24. The method of claim 17, wherein, 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 this new call.

25. The method of claim 24, wherein, The step of establishing an application data channel between the application side and the terminal according to the fifteenth message includes: Generate the fourth information based on the fifteenth message; Send 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; Receive the twelfth message sent by the application side, wherein the twelfth message is used to indicate the result of the data channel establishment.

26. The method of claim 25, wherein, The fourth piece of information includes one or more of the following: The application's identifier in this new call; Callee identifier; Media information regarding this new call; Call event notification address.

27. The method of claim 25, wherein, The twelfth message includes one or more of the following: The application side has a routable identifier in the IMS used in the new call; SDP information.

28. The method according to claim 1, further comprising: Receive 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; The seventeenth message is mapped to an Initial Session Protocol Goodbye (SIP BYE) message, and the SIP BYE message is sent to the terminal. The system receives the response sent by the terminal, maps the response to a new response, and sends the response to the application side.

29. The method according to claim 1, further comprising: Receive the SIP BYE sent by the terminal, map the SIP BYE to a fifth message, and send the fifth message to the application side; The system receives a response from the application side, maps the response to a SIP response, and sends the SIP response to the terminal.

30. The method according to claim 1, further comprising: Receive the 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; A thirteenth message is sent to the application side, wherein the thirteenth message is used to indicate the query result of the new call.

31. A request processing method, applied on the application side, the method comprising: Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

32. The method of claim 31, wherein, The first message includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Call event notification address.

33. The method according to claim 31, further comprising: Receive a second message sent by the network function, wherein the second message is used to indicate whether the first message was successful.

34. The method according to claim 31, further comprising: Receive a fifth message sent by the network function, wherein the fifth message includes the first information.

35. The method of claim 34, wherein, The first information includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Session identifier.

36. The method according to claim 31, further comprising: Receive the call setup process event sent by the network function.

37. The method according to claim 31, further comprising: 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.

38. The method of claim 37, wherein, The fifteenth message includes one or more of the following: The application's identifier in this new call; Callee identifier; Should we use the new call capability? Service configuration information for this new call; Media information regarding this new call; Call event notification address.

39. The method according to claim 37, further comprising: Receive the ninth message sent by the network function, wherein the ninth message is used to indicate whether the fifteenth message was successful.

40. The method of claim 37, further comprising: Receive the eleventh message sent by the network function, wherein the eleventh message is used to indicate the result of the establishment of the application data channel.

41. The method according to claim 31, further comprising: Receive the 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; Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

42. The method of claim 41, wherein, The fourth piece of information includes one or more of the following: The application's identifier in this new call; Callee identifier; Media information regarding this new call; Call event notification address.

43. The method of claim 41, wherein, The twelfth message includes one or more of the following: The application side has a routable identifier in the IMS used in the new call; SDP information.

44. The method according to claim 31, further comprising: Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal; Receive the response sent by the network function.

45. The method according to claim 31, further comprising: Receive the fifth message sent by the network function and send a response to the network function.

46. ​​The method according to claim 31, further comprising: Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal; Receive the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

47. A request processing method, applied on the application side, the method comprising: The fourteenth message sent by the network function is received, wherein the fourteenth message is used to establish a new call between the terminal and the application side and includes second information; A sixth message is sent to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

48. The method of claim 47, further comprising: A seventh message is sent to the network function, wherein the seventh message is used to indicate whether the fourteenth message was successful.

49. The method of claim 47, wherein, The second information includes one or more of the following: The identifier of the calling terminal; The application's identifier in this new call; Should we use the new call capability? Media information regarding this new call; Session identifier.

50. The method of claim 47, further comprising: Receive the call setup process event sent by the network function.

51. The method according to claim 47, further comprising: Receive the 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; Send a twelfth message to the network function, wherein the twelfth message is used to indicate the result of the data channel establishment.

52. The method of claim 51, wherein, The fourth piece of information includes one or more of the following: The application's identifier in this new call; Callee identifier; Media information regarding this new call; Call event notification address.

53. The method of claim 51, wherein, The twelfth message includes one or more of the following: The application side has a routable identifier in the IMS used in the new call; SDP information.

54. The method according to claim 47, further comprising: Send a seventeenth message to the network function, wherein the seventeenth message is used to terminate a new call between the application and the terminal; Receive the response sent by the network function.

55. The method of claim 47, further comprising: Receive the fifth message sent by the network function and send a response to the network function.

56. The method according to claim 47, further comprising: Send an eighteenth message to the network function, wherein the eighteenth message is used to query new calls between the application and the terminal; Receive the thirteenth message sent by the network function, wherein the thirteenth message is used to indicate the query result of the new call.

57. A request processing method applied to an IMS used for a new call, the method comprising: Send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side.

58. The method of claim 57, wherein, The first message includes the SDP information for this new call.

59. The method according to claim 57, further comprising: Receive the eighth message sent by the network function, wherein the eighth message includes SDP information.

60. A request processing method applied to a terminal, the method comprising: Send an INVITE request to the IMS used for the new call, so that the IMS used for the new call can send a first message to the network function; The INVITE request includes the SDP information for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

61. The method according to claim 60, further comprising: Receive the SIP BYE sent by the network function and send a response to the network function.

62. The method according to claim 60, further comprising: Send a SIP BYE to the network function and receive a SIP response from the network function.

63. A request processing apparatus for network functions, the apparatus comprising: The first receiving module is used to receive a first message, wherein the first message is used to request the establishment of 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 based on the first message.

64. A request processing apparatus, applied on an application side, the apparatus comprising: The first sending module is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

65. A request processing apparatus, applied on an application side, the apparatus comprising: The first receiving module 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 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 the establishment of this new call.

66. A request processing apparatus for use in an IMS for a new call, the apparatus comprising: The first sending module is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side.

67. A request processing apparatus applied to a terminal, the apparatus comprising: The first sending module 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 for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

68. A request handling apparatus, applied to a network function, the apparatus comprising: Processor and transceiver; The transceiver is used to receive a first message, wherein the first message is used to request the establishment of 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 based on the first message.

69. A request processing apparatus applied to an application side, the apparatus comprising: Processor and transceiver; The transceiver is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the application side and the terminal.

70. A request processing apparatus applied to an application side, the apparatus comprising: Processor and transceiver; The transceiver is 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; and to send a sixth message to the network function, wherein the sixth message is used to indicate the result of the establishment of this new call.

71. A request handling apparatus, for use in an IMS for a new call, the apparatus comprising: Processor and transceiver; The transceiver is used to send a first message to the network function, wherein the first message is used to request the establishment of a new call between the terminal and the application side.

72. A request processing apparatus applied to a terminal, the apparatus comprising: Processor and 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 for this new call, and the first message is used to request the establishment of a new call between the terminal and the application side.

73. A communication device, comprising: Memory, processor, and programs stored in the memory and executable on the processor; The processor is configured to read a program from memory to implement the steps of the request processing method as described in any one of claims 1 to 62.

74. A readable storage medium for storing a program, which, when executed by a processor, implements the steps in the request processing method of any one of claims 1 to 62.

Images