Communication method, device, network function, calling entity, storage medium and computer program product

Abstract

Disclosed are a communication method and apparatus, a network function, a calling entity, a storage medium and a computer program product, the method comprising: a first network function receiving first information, and deciding whether to allow or not allow a terminal to register an IMS DC based on the first information; wherein the first information indicates whether the terminal supports IMS DC or not, and / or indicates whether the terminal can guarantee a new call DC service or not.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method, device, network function, call entity, storage medium and computer program product. Background Art

[0002] The new call services are divided into two categories. The terminals provide video call capabilities based on the new air interface voice bearer (VoNR) and long-term evolution voice bearer (VOLTE), and the network enhances the audio and video artificial intelligence (AI) processing capabilities to carry out services. Based on the IP Multimedia Subsystem (IMS) data channel (DC) technology, the terminals and networks are upgraded to support the real-time interaction of various types of data between users. After the new call is commercialized, there are some devices that cannot support DC services well. Such devices can complete DC registration and DC negotiation, but there are many problems when using DC services during calls. Summary of the invention

[0003] To solve related technical problems, embodiments of the present application provide a communication method, device, network function, call entity, storage medium and computer program product.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] An embodiment of the present application provides a communication method, which is applied to a first network function, and the method includes:

[0006] Receive first information; wherein the first information indicates whether the terminal supports IP Multimedia Subsystem Data Channel (IMSDC) and / or indicates whether the terminal can guarantee a new call DC service;

[0007] Based on the first information, it is determined whether to allow or not to allow the terminal to register with IMSDC.

[0008] In the above solution, determining whether to allow or not to allow the terminal to register IMSDC based on the first information includes:

[0009] When the first information indicates that the terminal supports IMSDC and / or can guarantee the new call DC service, allowing the terminal to register IMSDC; or

[0010] When the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the new call DC service, the terminal is not allowed to register for IMSDC.

[0011] In the above solution, the receiving the first information includes:

[0012] Receive a first request sent by the terminal through a second network function; wherein the first request indicates that the terminal requests registration of IMSDC, and the first request carries at least the first information.

[0013] In the above scheme, the method further comprises:

[0014] Sending a first response to the terminal through the second network function; wherein,

[0015] In the case where the first information indicates that the terminal supports IMSDC or can guarantee a new call DC service, the first response indicates that the terminal is allowed to register IMSDC and carries a first identifier, where the first identifier indicates that the network provides the terminal with a DC capability;

[0016] When the first information indicates that the terminal does not support IMSDC or cannot guarantee the new call DC service, the first response indicates that the terminal is not allowed to register for IMSDC and does not carry the first identifier.

[0017] In the above solution, the first information is carried in a User-Agent (UA) header field of the first request; and / or

[0018] The Contact header field of the first request carries a second identifier, where the second identifier indicates whether the terminal has IMSDC capability.

[0019] The embodiment of the present application also provides a communication method, which is applied to a calling entity, and the method includes:

[0020] Receiving first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0021] It is determined whether to allow or not to allow a setting operation to be performed based on the first information, where the setting operation represents a DC-related operation.

[0022] In the above solution, the setting operation includes one or more of the following:

[0023] Negotiating IMSDC media with the terminal;

[0024] Trigger new call DC service.

[0025] In the above solution, the receiving the first information includes:

[0026] A second request is received, which is sent by the terminal through the second network function and the first network function; wherein the second request represents that the terminal initiates a call for video media and data channel media, and the second request carries at least the first information.

[0027] In the above scheme, the method further comprises:

[0028] If the setting operation is not allowed, perform one or more of the following:

[0029] Reporting a call start event that does not include DC media information to the service application entity;

[0030] receiving a first instruction sent by a service application entity, wherein the first instruction does not carry DC media information;

[0031] Sending a second response to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero;

[0032] Not reporting a call start event about a first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication;

[0033] Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service represents a new call DC service triggered by the setting operation indication;

[0034] A second instruction regarding a second service sent by the service application entity is received, where the second service represents a new call DC service triggered by the setting operation indication.

[0035] In the above solution, the receiving the first information includes:

[0036] A first message sent by the terminal through the second network function and the first network function is received, where the first message indicates that the terminal has received a call request for video media and data channel media, and the first message carries the first information.

[0037] In the above scheme, the method further comprises:

[0038] If the setting operation is not allowed, perform one or more of the following:

[0039] Sending a third request to the media entity, the third request carrying the audio and video session description (SDP, Session Description Protocol) information of the terminal, used to request audio and video media, and instructing to delete the DC media information of the terminal;

[0040] receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information;

[0041] Sending a second message to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero;

[0042] Reporting a control result failure notification message about the first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication.

[0043] In the above solution, the first information is carried in the User-Agent header field of the second request.

[0044] In the above solution, the first information is carried in the service Server header field of the first message.

[0045] The present application also provides a communication device, including:

[0046] A first receiving unit, configured to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0047] The first processing unit is configured to determine whether to allow or not to allow the terminal to register with the IMSDC based on the first information.

[0048] The present application also provides a communication device, including:

[0049] A second receiving unit, configured to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0050] The second processing unit is used to decide whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

[0051] The embodiment of the present application further provides a first network function, including: a first processor and a first communication interface; wherein,

[0052] The first communication interface is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0053] The first processor is configured to determine whether to allow or not to allow the terminal to register with the IMSDC based on the first information.

[0054] The embodiment of the present application further provides a calling entity, comprising: a second processor and a second communication interface; wherein,

[0055] The second communication interface is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0056] The second processor is used to determine whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

[0057] The embodiment of the present application further provides a first network function, including a first processor and a first memory for storing a computer program that can be run on the first processor.

[0058] Wherein, the first processor is used to execute the steps of any method on the first network function side when running the computer program.

[0059] The embodiment of the present application further provides a call entity, including a second processor and a second memory for storing a computer program that can be run on the second processor.

[0060] Wherein, the second processor is used to execute the steps of any method on the calling entity side when running the computer program.

[0061] An embodiment of the present application also provides a storage medium on which a computer program is stored, characterized in that when the computer program is executed by a processor, the computer program implements the steps of any method on the first network function side, or implements the steps of any method on the call entity side.

[0062] An embodiment of the present application also provides a computer program product, including a computer program, characterized in that the computer program implements the steps of any of the above methods when executed by a processor.

[0063] In the communication method, device, network function, call entity, storage medium and computer program product provided in the embodiment of the present application, the first information indicates whether the terminal supports IMSDC, or indicates whether the terminal can guarantee the new call DC service; the first network function decides to allow or not allow the terminal to register IMSDC based on the received first information, and the call entity decides to allow or not allow the execution of DC-related operations based on the received first information. It can be seen that in the embodiment of the present application, the first network function and the call entity can identify whether the terminal supports IMSDC or can guarantee the new call DC service based on the first information. In the case where the terminal does not support IMSDC or cannot guarantee the new call DC service, the first network function does not allow the terminal to register IMSDC, and the call entity does not allow the execution of DC-related operations. Even if the terminal completes the IMSDC registration, the call entity can also decide not to allow the terminal to perform DC-related operations based on the first information, thereby ensuring that the terminal that does not support IMSDC or cannot guarantee the new call DC service cannot complete IMSDC registration and / or DC media negotiation and / or cannot trigger the new call DC service, and only allows the terminal that supports IMSDC or can guarantee the new call DC service to trigger the new call DC service, thereby improving the reliability of the new call system. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 This is an example of the communication system architecture of the embodiment of the present application;

[0065] Figure 2 A schematic diagram of a DC registration process of a communication method according to an embodiment of the present application;

[0066] Figure 3 A schematic diagram of the DC media negotiation process of the communication method according to an embodiment of the present application;

[0067] Figure 4 The DC service process for suppressing new calls in the communication method of the embodiment of the present application;

[0068] Figure 5 A flow chart of a communication method according to an embodiment of the present application;

[0069] Figure 6 A flow chart of a communication method according to an embodiment of the present application;

[0070] Figure 7 This is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

[0071] Figure 8 This is a schematic diagram of another communication device structure according to an embodiment of the present application;

[0072] Fig. 9 This is a schematic diagram of the first network function structure of an embodiment of the present application;

[0073] Fig.10 This is a schematic diagram of the call entity structure of an embodiment of the present application. DETAILED DESCRIPTION

[0074] As a basic communication service for information exchange, audio and video calls have had relatively simple functions for many years. The communication network has insufficient stickiness for users and has lagged far behind the Internet industry.

[0075] For users, the need to express themselves is becoming increasingly strong. They hope to convey their true feelings more accurately and vividly during calls. The new call solution can meet diverse social needs such as real-time communication, interactive experience, and content sharing.

[0076] The new call services are divided into two categories: providing video call capabilities based on VoNR and VOLTE terminals, and conducting services based on network-enhanced audio and video AI processing capabilities. Based on IMSDC technology, terminals and networks are upgraded to support the ability to interact with various types of data between users in real time.

[0077] The relevant technology defines the use of IMSDC on the terminal and Internet sides. In practice, IMS DC is created separately from the audio and video channels. It does not restrict the actual transmitted content and can transmit information such as text, photos, videos, locations, interactive information, etc.

[0078] After the new call is put into commercial use, some devices cannot support DC services well. Such devices can complete DC registration and DC negotiation, but there are many problems when using DC services during calls.

[0079] Based on this, in each embodiment of the present application, the first information indicates whether the terminal supports IMSDC, or indicates whether the terminal can guarantee the new call DC service; the first network function decides whether to allow or not to allow the terminal to register IMSDC based on the received first information, and the call entity decides whether to allow or not to perform DC-related operations based on the received first information. It can be seen that in the embodiment of the present application, the first network function and the call entity can identify whether the terminal supports IMSDC or whether it can guarantee the new call DC service based on the first information. In the case where the terminal does not support IMSDC or cannot guarantee the new call DC service, the first network function does not allow the terminal to register IMSDC, and the call entity does not allow the DC-related operations to be performed. Even if the terminal completes the IMSDC registration, the call entity can also decide not to allow the terminal to perform DC-related operations based on the first information, thereby ensuring that the terminal that does not support IMSDC or cannot guarantee the new call DC service cannot complete IMSDC registration and / or DC media negotiation and / or cannot trigger the new call DC service, and only allows the terminal that supports IMSDC or can guarantee the new call DC service to trigger the new call DC service, thereby improving the reliability of the new call system.

[0080] The present application is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0081] First, in order to better illustrate the communication method provided in the embodiment of the present application, Figure 1 An example of the communication system architecture of the present application embodiment. Figure 1 In the system architecture shown: the new call system includes an interrogating-Call Session Control Function (I-CSCF) / serving-Call Session Control Function (S-CSCF) 103, a call entity 104, a media entity 105 and a business application entity 106; a terminal 101 interacts with the new call system through a session border controller (SBC) / proxy-Call Session Control Function (P-CSCF) 102; the I / S-CSCF 103 in the new call system can also interact with a home subscriber server (HSS); the terminal includes one or more of a mobile phone, a user equipment (UE), and a handheld augmented reality (AR) device.

[0082] The call entity 104 is used to receive call requests, report call events, receive control instructions, and perform processing such as Session Initialization Protocol (SIP) or Hypertext Transfer Protocol (HTTP) signaling control to apply for or update media resources from the media entity, forward call signaling negotiation, etc.

[0083] The media entity 105 is used to interact with the call entity 104 etc. to complete the application or update of media resources, establish data channels and audio and video channels, and receive instructions from the business application entity to perform media operations, such as media copying, media playback, etc.

[0084] The service application entity 106 is used to interact with the call entity 104 , the media entity 105 , etc. to complete the new call DC service and send control instructions to the call entity 104 and the media entity 105 .

[0085] The new call system supports DC registration process, DC media negotiation process and suppression of new call DC service process, which are described in detail one by one below; in each process, the terminal is UE, the first network function is I / S-CSCF, and the second network function is SBC / P-CSCF as an example for explanation.

[0086] 1. DC Registration Process

[0087] like Figure 2 As shown, the DC registration process includes the following steps:

[0088] Step 1: The UE initiates registration and sends a first request to the SBC / P-CSCF of the IMS system.

[0089] Here, the first request carries the first information, and the first request may be a registration request, such as a Register message; the first information indicates whether the UE supports IMSDC, and / or indicates whether the UE can guarantee the new call DC service; the UE cannot guarantee the new call DC service, which can be understood as not being able to well support the new call DC service, and the new call includes the IMS call. The first information is carried in the User-Agent header field of the first request, and / or the Contatc header field of the first request carries the second identifier, and the second identifier indicates whether the UE has the IMS DC capability.

[0090] The first information can be understood as terminal information or UE-related information, which may include terminal model, operating system version, etc. The second identifier can be called a DC capability tag. An example of a DC capability tag in the Contact header field can be: Contact:*;+sip.app-subtype="webrtc-datachannel" or, Contact:*;+g.3gpp.datachannel. WebRTC is an application programming interface (AP, Application Programming Interface).

[0091] Step 2: The SBC / P-CSCF forwards the received first request to the I / S-CSCF of the IMS system.

[0092] Step 3: The I / S-CSCF queries the HSS / UDM for authentication information through a Multimedia-Auth-Request (MAR).

[0093] Here, MAR is used to request authentication information, and the authentication information includes an authentication vector (AV, Authorization Vector).

[0094] Step 4: HSS / UDM receives the MAR and replies a Multimedia-Auth-Answer (MAA) to the I / S-CSCF.

[0095] Here, the MAA carries authentication information.

[0096] Step 5: The I / S-CSCF receives the MAA and replies a 401 message to the SBC / P-CSCF requesting UE authentication.

[0097] Here, the 401 message carries authentication information, and the 401 message is also called a 401 response.

[0098] Step 6: The SBC / P-CSCF forwards the 401 message to the UE for authentication.

[0099] Step 7: The UE initiates registration again and sends a first request to the SBC / P-CSCF of the IMS system.

[0100] Here, when the UE receives the 401 message, the UE authenticates the network, initiates registration again, and sends a first request to the SBC / P-CSCF of the IMS system, where the first request carries the first information. The first information is carried in the User-Agent header field of the first request, and / or the Contact header field of the first request carries the second identifier.

[0101] Step 8: The SBC / P-CSCF forwards the first request to the I / S-CSCF of the IMS system.

[0102] Step 9: The I / S-CSCF queries the HSS / UDM for the server through a Server-Assignment-Request (SAR).

[0103] Step 10: The HSS / UDM receives the SAR and sends a Server-Assignment-Answer (SAA) to the I / S-CSCF.

[0104] Here, the SAA carries the identifier of the server, which can be understood as a server that provides services for IMS calls, or a server that provides services for new call DC services.

[0105] Step 11: The I / S-CSCF decides whether to allow or not to allow the UE to register with the IMSDC according to the first information carried in the first request, and sends a first response to the SBC / P-CSCF.

[0106] Here, the first response may be a 200OK message or a 200OK response. The decision may be described as determining, judging or identifying. Wherein, determining whether to allow or not to allow the UE to register for IMSDC according to the first information includes:

[0107] When the first information indicates that the UE supports IMSDC and / or can guarantee the new call DC service, allowing the UE to register for IMSDC; or

[0108] In the case where the first information indicates that the UE does not support IMSDC and / or the new call DC service cannot be guaranteed, the UE is not allowed to register for IMSDC.

[0109] It should be noted that, when the first information indicates that the UE supports IMSDC, the UE is allowed to register for any new call DC service; when the first information indicates that the new call DC service can be guaranteed, the UE is allowed to register for IMSDC for the new call DC service that can be guaranteed; when the first information indicates that the UE supports IMSDC and can guarantee the new call DC service, the UE is allowed to register for IMSDC or the UE is allowed to register for any new call DC service. When the first information indicates that the UE does not support IMSDC, the UE is not allowed to register for all new call DC services; when the first information indicates that the new call DC service cannot be guaranteed, the UE is not allowed to register for IMSDC for the new call DC service that cannot be guaranteed; when the first information indicates that the UE does not support IMSDC and the new call DC service cannot be guaranteed, the UE is not allowed to register for IMSDC or the UE is not allowed to register for any new call DC service; when the first information indicates that the UE supports IMSDC and the new call DC service cannot be guaranteed, the UE is not allowed to register for IMSDC for the new call DC service that cannot be guaranteed, and the UE is allowed to register for the new call DC service that can be guaranteed.

[0110] When the I / S-CSCF allows the UE to register for IMSDC, the first response indicates that the UE is allowed to register for IMSDC and carries a first identifier, and the first identifier indicates that the network provides DC capability to the UE. When the I / S-CSCF does not allow the UE to register for IMSDC, the first response indicates that the UE is not allowed to register for IMSDC and does not carry the first identifier. The first identifier is carried in the Feature-Caps header field of the first response, and the first identifier can be called a DC capability tag. For example, an example of a DC capability tag in the Feature-Caps header field is: Feature-Caps:*;+sip.app-subtype="webrtc-datachannel" or Feature-Caps:*;+g.3gpp.datachannel.

[0111] Step 12: The SBC / P-CSCF forwards the first response to the UE, and the DC registration process ends.

[0112] It should be noted that in the DC registration process, when the terminal (such as UE) initiates registration, it is necessary to incrementally carry the second identifier (DC capability tag) in the Contact header field of the first request (registration request). After receiving the first request, the I / S-CSCF first identifies whether the terminal is allowed to register with IMSDC based on the first information carried in the User-Agent header field; if the terminal is allowed to register with IMSDC, it enters the normal DC registration process; if the terminal is not allowed to register with IMSDC, it replies with a normal response message to the terminal. In subsequent third-party registrations, the I / S-CSCF does not carry the first identifier (DC capability tag). The purpose of this is to prevent the terminal from participating in DC media negotiations in DC calls, so as to improve the reliability of successful negotiations for new calls.

[0113] 2. DC Media Negotiation Process

[0114] Considering that if the User-Agent header field of the first request sent by the terminal in the DC registration process does not carry the first information, the I / S-CSCF completes the DC registration process of this terminal; but during the DC call, the DC media negotiation will be abnormal or the DC service cannot be executed after the negotiation is successful. The calling call entity can identify that this terminal does not allow DC media negotiation based on the first information carried in the User-Agent header field of the call request sent by the calling UE, and delete the DC media information in the subsequent reply response message (second response / 183 message); in this way, the DC call initiated by this terminal will not perform DC media negotiation. Similarly, if this terminal is called, the called call entity first forwards the call request to the called UE. When the called call entity receives the first information carried in the Server header field of the called response message (first message / 183 message), it identifies that this terminal does not allow DC media negotiation based on the first information carried in the Server header field, and the subsequent call request message sent to the called UE will delete the DC media information.

[0115] In the embodiment of the present application, whether to allow or not allow DC media negotiation is determined based on the first information carried in the User-Agent header field of the calling UE and the first information carried in the Server header field of the called UE, specifically including two scenarios: Scenario 1, media negotiation of the calling network when the calling UE initiates a DC call; Scenario 2, media negotiation of the called network after the called S-CSCF receives a call request from the calling network A. The DC media negotiation processes of Scenario 1 and Scenario 2 are introduced below.

[0116] like Figure 3 As shown, in scenario 1, when the calling UE initiates a DC call, the media negotiation of the calling network includes the following steps:

[0117] Step 1: The calling UE (eg, UE A) sends a second request to the SBC / P-CSCF of the IMS system.

[0118] Here, the second request represents that the terminal initiates a call of video media and data channel media, and the second request carries at least first information, and the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee the new call DC service.

[0119] The second request sent by the calling UE represents that the calling UE initiates a call for video media and data channel media, and the first information is carried in the User-Agent header field of the second request. An example of the User-Agent header field may be: ZTE_ZTEA2322_SKQ1.220213.001. The second request may be understood as a call request, such as INVITE signaling or an INVITE message, and the INVITE signaling or the INVITE message is used to initiate a call for video media and data channel media.

[0120] It should be noted that the second request also carries the audio and video SDP information of the terminal, which is used to request audio and video media, such as SDP-audio and video A, where audio and video A refers to the audio and video media of the calling UE. If the calling UE is in the DC registration process, and the I / S-CSCF completes the DC registration process of this terminal because the first request initiated by the calling UE does not carry the first information, then the second request initiated by the calling UE can also carry the DC of the calling UE, such as DC-A, where DC-A refers to the DC of the calling UE.

[0121] Step 2: The SBC / P-CSCF forwards the second request to the I / S-CSCF of the IMS system.

[0122] Step 3: The I / S-CSCF forwards the second request to the calling entity through routing.

[0123] Step 4: The calling entity decides not to allow DC media negotiation according to the first information carried in the second request.

[0124] Here, when the first information indicates that the terminal does not support IMSDC and / or indicates that the terminal cannot guarantee the DC service for new calls, it is decided not to allow DC media negotiation; when the first information indicates that the terminal supports IMS DC and / or indicates that the terminal can guarantee the DC service for new calls, it is decided to allow DC media negotiation.

[0125] The decision not to allow DC media negotiation may be understood as a decision not to allow IMSDC media negotiation with the calling UE, or not to allow negotiation of DC media of the calling UE. In this case, the calling entity may be the calling calling entity.

[0126] Step 5: The calling entity reports a call start event that does not include DC media information to the service application entity.

[0127] Step 6: The service application entity sends a first instruction to the calling entity.

[0128] Here, the first instruction does not carry DC media information, and the first instruction can be understood as a media anchoring control instruction.

[0129] Step 7: The calling entity receives the first instruction and applies for audio and video media from the media entity.

[0130] Here, the request for applying for audio and video media from the media entity carries the audio and video media information of the calling user and the media template of the called side, etc. The audio and video media information of the calling user includes SDP-audio and video A.

[0131] Step 8: The media entity returns the media streaming media to the calling entity.

[0132] Here, media streaming media includes audio and video media. Please refer to the description of related technologies for the interaction process between the calling entity and the called network, which will not be described here.

[0133] Step 9: The calling entity sends a second response to the I / S-CSCF.

[0134] Here, the second response carries the first media information, and the DC media port in the first media information is zero, that is, the DC media port is set to 0. For example, the first media information may be SDP-audio and video+DC(0), and SDP-audio and video is the audio and video media requested by the calling entity. The first response may be 183, 183 message, or 183 response message.

[0135] Step 10: The I / S-CSCF forwards the second response to the SBC / P-CSCF.

[0136] Step 11: The SBC / P-CSCF forwards the second response to the calling UE.

[0137] Here, after receiving the second response, the calling UE completes the initial media negotiation, and then continues the media negotiation according to the resource reservation situation until the media negotiation is completed.

[0138] Step 12: The calling entity sends a media anchoring success notification message to the service application entity.

[0139] Here, after the I / S-CSCF forwards the second response, the audio and video negotiation continues; after the initial media negotiation is completed, the calling entity sends a media anchoring success notification message to the service application entity.

[0140] It should be noted that for the subsequent media operation instructions from the service application entity to the media entity, please refer to the description in the relevant technology, which will not be repeated here.

[0141] It should be noted that in Figure 3 In scenario 1, the UE can be referred to as the calling UE, the calling entity can be referred to as the calling calling entity, the SBC / P-CSCF can be referred to as the calling SBC / P-CSCF, and the I / S-CSCF can be referred to as the calling I / S-CSCF; Figure 3 In scenario 2, the UE can be called the called UE, the calling entity can be called the called calling entity, the SBC / P-CSCF can be called the called SBC / P-CSCF, and the I / S-CSCF can be called the called I / S-CSCF. The calling SBC / P-CSCF and the called SBC / P-CSCF can be the same or different. The calling I / S-CSCF and the called I / S-CSCF can be the same or different. The calling calling entity and the called calling entity can be the same or different.

[0142] like Figure 3 As shown in scenario 2, after the called I / S-CSCF receives the call request from the calling network A, the media negotiation of the called network includes the following steps:

[0143] Step B1: The called I / S-CSCF receives the second request sent by the calling network A.

[0144] The second request carries SDP-audio-video A and DC-A.

[0145] Step B2: The called I / S-CSCF forwards the second request to the calling entity through routing.

[0146] Step B3: The calling entity reports a call start event including DC media information to the service application entity.

[0147] Step B4: the service application entity sends a media anchoring control instruction to the calling entity, where the media anchoring control instruction carries DC media information.

[0148] Step B5: The calling entity receives the media anchoring control instruction and applies for all media (audio, video and DC media) from the media entity.

[0149] Here, the request for applying for audio and video media from the media entity carries the calling side user audio and video media information and DC media information, as well as the called side audio and video media template and DC media template, etc. The calling side user audio and video media information includes SDP-audio and video A, and the calling side DC media information includes DC media A.

[0150] Step B6: The media entity returns all media streaming media to the calling entity.

[0151] Here, the media streaming media returned by the media entity to the calling entity includes the audio and video media and DC media of the calling side, and the audio and video media and DC media of the called side.

[0152] Step B7: The calling entity sends a fourth request to the I / S-CSCF.

[0153] Here, the fourth request may be a call request, such as an Invite message; the fourth request carries the applied audio and video media and DC media, such as SDP-audio and video+DC.

[0154] Step B8: The I / S-CSCF forwards the fourth request to the SBC / P-CSCF.

[0155] Step B9: The SBC / P-CSCF forwards the fourth request to the called UE (eg, UEB).

[0156] Step B10: The called UE receives the fourth request and sends a first message to the SBC / P-CSCF.

[0157] Here, the first message represents that the terminal receives a call request for video media and data channel media, and the first message carries the first information; the first information indicates whether the terminal supports IMSDC, and / or indicates whether the terminal can guarantee the new call DC service. Among them, the first information is carried in the Server header field of the first message. In other words, the first message includes a Server header field, and the Server header field carries the first information. The first information carried by the first message sent by the called UE indicates whether the called UE supports IMSDC, or indicates whether the called UE can guarantee the new call DC service.

[0158] An example of the Server header field could be: ZTE_ZTE A2322_SKQ1.220213.001.

[0159] The first message also carries media information of the called UE, such as SDP-audio-video B+DC-B.

[0160] Step B11: The SBC / P-CSCF forwards the first message to the I / S-CSCF.

[0161] Step B12: The I / S-CSCF forwards the first message to the calling entity.

[0162] Step B13: The calling entity decides not to allow DC media negotiation according to the first information carried in the first message, and only carries the user audio and video SDP to update the media entity media, and at the same time instructs to delete the DC information.

[0163] Here, when the first message carries the first information indicating that the called UE does not support IMSDC and / or indicates that the called UE cannot guarantee the DC service for the new call, the calling entity decides not to allow DC media negotiation based on the first information carried in the Server header field of the first message, that is, not to allow negotiation of DC media with the called UE, or not to allow negotiation of the DC media of the called UE.

[0164] Among them, when the first information indicates that the terminal does not support IMSDC and / or indicates that the terminal cannot guarantee the DC service for new calls, it is decided not to allow DC media negotiation; when the first information indicates that the terminal supports IMS DC and / or indicates that the terminal can guarantee the DC service for new calls, it is decided to allow DC media negotiation.

[0165] Step B14: When the calling entity decides not to allow DC media negotiation, it sends a third request to the media entity.

[0166] Here, the third request carries the audio and video SDP information of the called UE, is used to request audio and video media, and indicates to delete the DC media information of the called UE. The third request can be a media update request, such as a media Update message; the third request can carry SDP-audio and video B and indicate to delete the DC media information, and deleting the DC media information can be to set the DC media port to zero.

[0167] Step B15: The media entity sends the second media information to the calling entity.

[0168] Here, the second media information includes audio and video media information but does not include DC media information. The second media information can be understood as audio and video media streaming media. The second media information can be SDP-audio and video+DC(0), that is, the second media information only includes the audio and video media of the calling UE and the called UE, and does not include DC media. The media entity continues to perform signaling and media negotiation processes with the calling network, which will not be repeated here.

[0169] Step B16: The calling entity receives the second media information and sends a second message to the I / S-CSCF.

[0170] Here, the second message carries the third media information, and the DC media port in the third media information is 0. For example, the third media information is SDP-audio and video+DC(0).

[0171] Step B17: The I / S-CSCF forwards the second message to the SBC / P-CSCF.

[0172] Step B18: The SBC / P-CSCF forwards the second message to the called UE.

[0173] Step B19: After the calling entity and the media entity continue to complete the audio and video negotiation, they send a media anchoring success notification message to the service application entity.

[0174] Here, after the calling entity sends the second message, the calling entity and the media entity continue to complete the audio and video negotiation; when the audio and video negotiation is completed, a media anchoring success notification message is sent to the service application entity, and the media anchoring success notification message can carry the Uniform Resource Locator (URL) of the audio and video media stream.

[0175] The media operation instructions from the service application entity to the media entity will not be described in detail later.

[0176] 3. Suppressing new call DC service process

[0177] In an embodiment of the present application, whether to allow or not to trigger a specific new call DC service is determined based on the first information carried in the User-Agent header field of the calling UE and the first information carried in the Server header field of the called UE. The new call DC service can be understood as a new call service involving DC, which specifically includes two scenarios: Scenario 1, the calling network suppresses the new call DC service process when the calling UE initiates a DC call.

[0178] like Figure 4 As shown, in scenario 1, when the calling UE initiates a DC call, the calling network suppresses the new call DC service process, including the following steps:

[0179] Step 1 to Step 3: The calling UE sends a second request to the calling entity through the SBC / P-CSCF and I / S-CSCF of the IMS system. For specific implementation, please refer to Figure 3 See steps 1 to 3 in the documentation for details.

[0180] Step 4: The calling entity decides not to allow triggering of the first service according to the first information carried in the second request, and does not report a call start event about the first service to the service application entity.

[0181] Here, the first service represents a new call DC service that the terminal cannot guarantee, or a new call DC service that is not allowed to be triggered. For example, when the first information carried in the second request indicates that the terminal does not support IMSDC, and / or indicates that the terminal cannot guarantee the new call DC service, it is decided not to trigger the first service, and the first service can be understood as any new call DC service; and the call start event about the first service is not reported to the service application entity. When the first information indicates that the terminal supports IMSDC and cannot guarantee the first service, the first service can be understood as any new call DC service that cannot be guaranteed. At this time, the second service can be triggered.

[0182] The second service includes one or more of the following: a new call DC service other than the first service, a new call DC service other than the first service, a new call service not involving DC, and a non-new call DC service.

[0183] Step 5: If triggering of the second service is allowed, the calling entity reports a call start event about the second service to the service application entity.

[0184] Here, the call start event about the second service includes DC media information, such as DC-A. That is, the call entity reports the call start event about the second service including DC media information to the service application entity. The second service characterizes the new call DC service that is allowed to be triggered.

[0185] It should be noted that different new call DC services can share a service application entity, that is, the first service and the second service correspond to the same service application entity; different new call DC services correspond to different service application entities, for example, the first service corresponds to the first service application entity, and the second service corresponds to the second service application entity, and the first service is different from the second service.

[0186] Step 6: The service application entity sends a second instruction to the calling entity.

[0187] Here, the second instruction may be understood as a media anchoring control instruction corresponding to the second service.

[0188] Step 7: The calling entity receives the second instruction and applies for all media (audio, video and DC media) from the media entity.

[0189] Here, the request for applying for audio and video media from the media entity carries the calling side user audio and video media information and DC media information, as well as the called side audio and video media template and DC media template, etc. The calling side user audio and video media information includes SDP-audio and video A, and the calling side DC media information includes DC media A.

[0190] Step 8: The media entity returns all media streaming media to the calling entity.

[0191] Here, the media streaming media returned by the media entity to the calling entity includes the audio and video media and DC media of the calling side, and the audio and video media and DC media of the called side.

[0192] Step 9: The calling entity sends a third response to the I / S-CSCF.

[0193] Here, the third response can be called a 183 message or a 183 response message, or 183 for short; the third response carries the requested audio and video media and DC media, such as SDP-audio and video+DC.

[0194] Step 10: The I / S-CSCF forwards the third response to the SBC / P-CSCF.

[0195] Step 11: The SBC / P-CSCF forwards the third response to the calling UE (eg, UE A).

[0196] Here, after receiving the third response, the calling UE continues the media negotiation according to the resource reservation situation until the media negotiation is completed.

[0197] Step 12: The calling entity sends a media anchoring success notification message to the service application entity.

[0198] Here, after the I / S-CSCF forwards the second response, the audio and video negotiation continues; after the initial media negotiation is completed, the calling entity sends a media anchoring success notification message to the service application entity.

[0199] like Figure 4 As shown, in scenario 2, after the called S-CSCF receives the call request from the calling network A, the called network's new call suppression DC service process includes the following steps:

[0200] Step B1 to step B2: The called I / S-CSCF receives the second request sent by the calling network A, and forwards the second request to the calling entity through routing.

[0201] Here, the second request carries SDP-Audio-Video-A and DC-A.

[0202] Step B3: the calling entity decides not to allow triggering of the first service according to the first information carried in the second request, does not report the call start event about the first service to the service application entity, and reports the call start event about the second service to the service application entity.

[0203] Here, if the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the first service, triggering the first service is not allowed. If the first information indicates that the terminal supports IMSDC and can guarantee the first service, triggering the first service is allowed.

[0204] The call start event about the second service includes DC media information, such as DC-A. That is, the call entity reports the call start event containing DC media information about the second service to the service application entity. The second service characterization allows the triggering of new call DC services. The second service includes one or more of the following: new call DC services other than the first service, new call DC services other than the first service, new call services not involving DC, and non-new call DC services.

[0205] Step B4: The service application entity sends a second instruction regarding the second service to the calling entity.

[0206] Here, the second instruction may be a media anchor control instruction regarding the second service.

[0207] Step B5: The calling entity receives the second instruction about the second service, and applies for all media (audio, video and DC media) from the media entity.

[0208] Here, the request for applying for audio and video media from the media entity carries the calling side user audio and video media information and DC media information, as well as the called side audio and video media template and DC media template, etc. The calling side user audio and video media information includes SDP-audio and video A, and the calling side DC media information includes DC media A.

[0209] Step B6: The media entity returns all media streaming media to the calling entity.

[0210] here, Figure 4 Steps B6 to B12 in Figure 3 The steps B6 to B12 in are the same. For the specific implementation process, please refer to the relevant description above and will not be repeated here.

[0211] Step B7: The calling entity sends a fourth request to the I / S-CSCF.

[0212] Step B8: The I / S-CSCF forwards the fourth request to the SBC / P-CSCF.

[0213] Step B9: The SBC / P-CSCF forwards the fourth request to the called UE (eg, UEB).

[0214] Step B10: The called UE receives the fourth request and sends a first message to the SBC / P-CSCF.

[0215] Step B11: The SBC / P-CSCF forwards the first message to the I / S-CSCF.

[0216] Step B12: The I / S-CSCF forwards the first message to the calling entity.

[0217] Step B13: The calling entity decides not to allow triggering of the first service according to the first information carried in the first message.

[0218] Here, when the first message carries the first information indicating that the called UE does not support IMSDC and / or indicates that the called UE cannot guarantee the new call DC service, the calling entity decides not to allow the first service to be triggered based on the first information carried in the Server header field of the first message. The first service can be understood as any new call DC service; when the first information indicates that the called UE supports IMSDC and does not support the first service, the first service can be understood as any new call DC service that cannot be guaranteed. At this time, the second service other than the first service can be triggered.

[0219] Step B14: When the calling entity decides not to allow triggering of the first service, it reports a control result failure notification message about the first service to the service application entity.

[0220] Here, the calling entity and the service application entity continue to execute the relevant processes of the second service except the first service.

[0221] Step B15: The calling entity requests the media entity to update the media.

[0222] Here, the calling entity may send a media update request, such as a media Update message, to the media entity to request to update the media; the media update request may carry the audio and video SDP information and DC media information of the called UE, and the media update request may carry SDP-audio and video B+DC-B.

[0223] Step B16: The media entity returns the updated media information to the calling entity.

[0224] Here, the media entity returns the updated audio and video media information and the DC media information of the second service to the calling entity. The updated media information includes the audio and video media of the calling UE and the called UE, as well as the DC media of the second service. The media entity continues to perform signaling and media negotiation processes with the calling network, which will not be repeated here.

[0225] Step B17: The calling entity receives the updated media information and sends a third message to the I / S-CSCF.

[0226] Here, the third message carries updated media information, such as SDP-audio and video+DC. The third message may be a 183 message or a 183 response message.

[0227] Step B18: The I / S-CSCF forwards the third message to the SBC / P-CSCF.

[0228] Step B19: The SBC / P-CSCF forwards the third message to the called UE.

[0229] Step B20: After the calling entity and the media entity continue to complete the audio and video negotiation, they send a media anchoring success notification message to the service application entity.

[0230] Here, after the calling entity sends the third message, the calling entity and the media entity continue to complete the audio and video negotiation; when the audio and video negotiation is completed, a media anchoring success notification message is sent to the service application entity, and the media anchoring success notification message can carry the media stream (URL, Uniform Resource Locator).

[0231] It should be noted that the calling entity can conditionally implement or restrict the new call DC service process based on the first information carried in the User-Agent and Server header fields. Some terminals cannot well support the DC required by the new call DC service and cannot establish the corresponding digital channel as instructed, resulting in anomalies; at this time, the calling entity can use the User-Agent header field and the Server header field to identify and avoid triggering and executing the new call DC service for this terminal, thereby enhancing the reliability of the new call system.

[0232] Based on the DC registration process, DC media negotiation process and new call suppression DC service process of the communication method shown in the above embodiment, on this basis, the embodiments of this application are described with I / S-CSCF and call entity as the execution subjects respectively. It should be noted that the communication method of the unilateral execution subject and the corresponding implementation principle can be understood in the same way as the relevant contents of the various interactive process embodiments of the above communication method, and will not be repeated below.

[0233] The present application embodiment provides a communication method, which is applied to a first network function, and the first network function corresponds to the I / S-CSCF mentioned above. Figure 5 As shown, the method includes:

[0234] Step 501: Receive first information.

[0235] The first information indicates whether the terminal supports IMSDC and / or whether the terminal can guarantee the new call DC service.

[0236] Step 502: Based on the first information, decide whether to allow or not to allow the terminal to register with IMSDC.

[0237] In order to facilitate the first network function to identify the first information and improve the efficiency of obtaining the first information, in one embodiment, the first information is carried in the User-Agent header field of the first request; and / or

[0238] The Contact header field of the first request carries a second identifier, where the second identifier indicates whether the terminal has IMSDC capability.

[0239] In one embodiment, determining whether to allow or not to allow the terminal to register IMSDC based on the first information includes:

[0240] When the first information indicates that the terminal supports IMSDC and / or can guarantee the new call DC service, allowing the terminal to register IMSDC; or

[0241] When the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the new call DC service, the terminal is not allowed to register for IMSDC.

[0242] In order to save signaling overhead, the first information may be carried in a call request. Based on this, in one embodiment, receiving the first information includes:

[0243] Receive a first request sent by the terminal through a second network function; wherein the first request indicates that the terminal requests registration of IMSDC, and the first request carries at least the first information.

[0244] Here, the second network function includes the above-mentioned SBC / P-CSCF.

[0245] In order to facilitate the terminal to know whether the network provides the DC capability to the terminal, in one embodiment, the method further includes:

[0246] Sending a first response to the terminal through the second network function; wherein,

[0247] In the case where the first information indicates that the terminal supports IMSDC or can guarantee a new call DC service, the first response indicates that the terminal is allowed to register IMSDC and carries a first identifier, where the first identifier indicates that the network provides the terminal with a DC capability;

[0248] When the first information indicates that the terminal does not support IMSDC or cannot guarantee the new call DC service, the first response indicates that the terminal is not allowed to register for IMSDC and does not carry the first identifier.

[0249] Correspondingly, the embodiment of the present application provides a communication method, which is applied to a calling entity, wherein the calling entity includes a calling calling entity and / or a called calling entity; the calling calling entity and the called calling entity may be the same or different. Figure 6 As shown, the method includes:

[0250] Step 601: Receive first information.

[0251] The first information indicates whether the terminal supports IMSDC and / or whether the terminal can guarantee the new call DC service.

[0252] Step 602: Based on the first information, decide whether to allow or not to allow a setting operation to be performed, where the setting operation represents a DC-related operation.

[0253] Here, when the first information indicates that the terminal supports IMSDC and / or indicates that the terminal can guarantee the new call DC service, it is decided to allow the setting operation to be executed; when the first information indicates that the terminal does not support IMSDC and / or indicates that the terminal cannot guarantee the new call DC service, it is decided not to allow the setting operation to be executed.

[0254] In one embodiment, the setting operation includes one or more of the following:

[0255] Negotiating IMSDC media with the terminal;

[0256] Trigger new call DC service.

[0257] Here, when the first information indicates that the terminal supports IMSDC and cannot guarantee the new call DC service, triggering of any new call DC service is not allowed; when the first information indicates that the terminal supports IMSDC and cannot guarantee the first service, triggering of the first service is not allowed, and the first service is the new call DC service, but triggering of the second service that the terminal can guarantee is allowed.

[0258] In the case where the terminal is the calling party, in order to facilitate the calling entity to decide whether to allow DC media negotiation for the terminal, it is necessary to carry first information in the call request. Based on this, in one embodiment, receiving the first information includes:

[0259] A second request is received, which is sent by the terminal through the second network function and the first network function; wherein the second request represents that the terminal initiates a call for video media and data channel media, and the second request carries at least the first information.

[0260] In order to improve the efficiency of the calling entity in acquiring the first information, in one embodiment, the first information is carried in the User-Agent header field of the second request.

[0261] In order to improve the reliability of the new call system, in one embodiment, the method further includes:

[0262] If the setting operation is not allowed, perform one or more of the following:

[0263] Reporting a call start event that does not include DC media information to the service application entity;

[0264] receiving a first instruction sent by a service application entity, wherein the first instruction does not carry DC media information;

[0265] Sending a second response to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero;

[0266] Not reporting a call start event about a first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication;

[0267] Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service represents a new call DC service triggered by the setting operation indication;

[0268] A second instruction regarding a second service sent by the service application entity is received, where the second service represents a new call DC service triggered by the setting operation indication.

[0269] Here, when the terminal is the calling party and DC media negotiation is not allowed, the calling entity performs one or more of the following:

[0270] Reporting a call start event that does not include DC media information to the service application entity;

[0271] receiving a first instruction sent by the service application entity, where the first instruction does not carry DC media information;

[0272] A second response is sent to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero.

[0273] When the terminal is the calling party and triggering of a new call DC service (such as the first service) is not allowed, the calling entity performs one or more of the following:

[0274] Not reporting the call start event about the first service to the service application entity, and the first service characterization does not allow the triggering of a new call DC service;

[0275] Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service characterizes a new call DC service that is allowed to be triggered;

[0276] A second instruction regarding a second service sent by the service application entity is received, wherein the second service characterizes a new call DC service that is allowed to be triggered.

[0277] When the terminal is the called party, in order to facilitate the calling entity to decide whether to allow DC media negotiation for the terminal, the first information needs to be carried in the 183 message. Based on this, in one embodiment, the receiving of the first information includes:

[0278] A first message sent by the terminal through the second network function and the first network function is received, where the first message indicates that the terminal has received a call request for video media and data channel media, and the first message carries the first information.

[0279] In order to improve the efficiency of the calling entity in acquiring the first information, in one embodiment, the first information is carried in the Server header field of the first message.

[0280] In order to improve the reliability of the new call system, in one embodiment, the method further includes:

[0281] If the setting operation is not allowed, perform one or more of the following:

[0282] Sending a third request to the media entity, where the third request carries the audio and video SDP information of the terminal, is used to request the audio and video media, and indicates to delete the DC media information of the terminal;

[0283] receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information;

[0284] Sending a second message to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero;

[0285] Reporting a control result failure notification message about the first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication.

[0286] Here, when the terminal is the called party and DC media negotiation is not allowed, the calling entity performs one or more of the following:

[0287] Sending a third request to the media entity, where the third request carries the audio and video SDP information of the terminal, is used to request the audio and video media, and indicates to delete the DC media information of the terminal;

[0288] receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information;

[0289] A second message is sent to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero.

[0290] When the terminal is the called party and triggering of a new call DC service or a first service is not allowed, the calling entity reports a control result failure notification message about the first service to the service application entity, where the first service characterizes that the setting operation indicates that triggering of a new call DC service is not allowed.

[0291] In order to implement the method on the first network function side of the embodiment of the present application, the embodiment of the present application also provides a communication device, which is arranged on the first network function, such as Figure 7 As shown, the device comprises:

[0292] The first receiving unit 701 is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service;

[0293] The first processing unit 702 is configured to determine whether to allow or not to allow the terminal to register with IMSDC based on the first information.

[0294] In one embodiment, the first processing unit 702 is specifically configured to:

[0295] When the first information indicates that the terminal supports IMSDC and / or can guarantee the new call DC service, allowing the terminal to register IMSDC; or

[0296] When the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the new call DC service, the terminal is not allowed to register for IMSDC.

[0297] In one embodiment, the first receiving unit 701 is specifically configured to receive a first request sent by the terminal through a second network function; wherein:

[0298] The first request indicates that the terminal requests to register with IMSDC, and the first request carries at least the first information.

[0299] In one embodiment, the device further comprises:

[0300] A first transceiver unit, configured to send a first response to the terminal through the second network function;

[0301] Wherein, when the first information indicates that the terminal supports IMSDC or can guarantee the new call DC service, the first response indicates that the terminal is allowed to register IMSDC and carries a first identifier, and the first identifier indicates that the network provides the DC capability to the terminal;

[0302] When the first information indicates that the terminal does not support IMSDC or cannot guarantee the new call DC service, the first response indicates that the terminal is not allowed to register for IMSDC and does not carry the first identifier.

[0303] In one embodiment, the first information is carried in a User-Agent header field of the first request; and / or

[0304] The Contact header field of the first request carries a second identifier, where the second identifier indicates whether the terminal has IMSDC capability.

[0305] In actual application, the first receiving unit 701 and the first transceiver unit can be implemented by a processor in a communication device in combination with a communication interface. The first processing unit 702 can be implemented by a processor in a communication device.

[0306] In order to implement the method of calling the entity side in the embodiment of the present application, the embodiment of the present application also provides a communication device, which is arranged on the calling entity, such as Figure 8 As shown, the device comprises:

[0307] The second receiving unit 801 is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee the new call DC service;

[0308] The second processing unit 802 is configured to determine whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

[0309] In one embodiment, the setting operation includes one or more of the following:

[0310] Negotiating IMSDC media with the terminal;

[0311] Trigger new call DC service.

[0312] In one embodiment, the second receiving unit 801 is specifically used to receive a second request sent by the terminal through the second network function and the first network function; wherein the second request represents that the terminal initiates a call for video media and data channel media, and the second request carries at least the first information.

[0313] In one embodiment, the device further comprises:

[0314] The second transceiver unit is configured to, when the setting operation is not allowed, perform one or more of the following:

[0315] Reporting a call start event that does not include DC media information to the service application entity;

[0316] receiving a first instruction sent by a service application entity, wherein the first instruction does not carry DC media information;

[0317] Sending a second response to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero;

[0318] Not reporting a call start event about a first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication;

[0319] Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service represents a new call DC service triggered by the setting operation indication;

[0320] A second instruction regarding a second service sent by the service application entity is received, where the second service represents a new call DC service triggered by the setting operation indication.

[0321] In one embodiment, the second receiving unit 801 is specifically used to receive a first message sent by the terminal through the second network function and the first network function, the first message indicating that the terminal has received a call request for video media and data channel media, and the first message carries the first information.

[0322] In one embodiment, the device further comprises:

[0323] The third transceiver unit is configured to, when the setting operation is not allowed, perform one or more of the following:

[0324] Sending a third request to the media entity, where the third request carries the audio and video SDP information of the terminal, is used to request the audio and video media, and indicates to delete the DC media information of the terminal;

[0325] receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information;

[0326] Sending a second message to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero;

[0327] Reporting a control result failure notification message about the first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication.

[0328] In one embodiment, the first information is carried in the User-Agent header field of the second request.

[0329] In one embodiment, the first information is carried in a Server header field of the first message.

[0330] In actual application, the second receiving unit 801, the second transceiver unit and the third transceiver unit can be implemented by a processor in a communication device in combination with a communication interface. The second processing unit 802 can be implemented by a processor in a communication device.

[0331] It should be noted that: when the communication device provided in the above embodiment performs communication, only the division of the above program modules is used as an example. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the communication device and the communication method embodiment provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0332] Based on the hardware implementation of the above program module, and in order to implement the method of the first network function side of the embodiment of the present application, the embodiment of the present application also provides a first network function, such as Fig. 9 As shown, the first network function 900 includes:

[0333] The first communication interface 901 is capable of exchanging information with other network nodes;

[0334] The first processor 902 is connected to the first communication interface 901 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the first network function side when running a computer program. The computer program is stored in the first memory 903.

[0335] Specifically, the first communication interface 901 is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee the new call DC service;

[0336] The first processor 902 is configured to determine whether to allow or not to allow the terminal to register with IMSDC based on the first information.

[0337] In one embodiment, the first processor 902 is specifically configured to:

[0338] When the first information indicates that the terminal supports IMSDC and / or can guarantee the new call DC service, allowing the terminal to register IMSDC; or

[0339] When the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the new call DC service, the terminal is not allowed to register for IMSDC.

[0340] In one embodiment, the first communication interface 901 is specifically used to receive a first request sent by the terminal through a second network function; wherein,

[0341] The first request indicates that the terminal requests to register with IMSDC, and the first request carries at least the first information.

[0342] In one embodiment, the first communication interface 901 is further used to send a first response to the terminal through the second network function;

[0343] Wherein, when the first information indicates that the terminal supports IMSDC or can guarantee the new call DC service, the first response indicates that the terminal is allowed to register IMSDC and carries a first identifier, and the first identifier indicates that the network provides the DC capability to the terminal;

[0344] When the first information indicates that the terminal does not support IMSDC or cannot guarantee the new call DC service, the first response indicates that the terminal is not allowed to register for IMSDC and does not carry the first identifier.

[0345] In one embodiment, the first information is carried in a User-Agent header field of the first request; and / or

[0346] The Contact header field of the first request carries a second identifier, where the second identifier indicates whether the terminal has IMSDC capability.

[0347] It should be noted that the specific processing process of the first processor 902 and the first communication interface 901 can be understood by referring to the above method.

[0348] Of course, in actual application, the various components in the first network function 900 are coupled together through the bus system 904. It can be understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig. 9 Various buses are labeled as bus system 904.

[0349] The first memory 903 in the embodiment of the present application is used to store various types of data to support the operation of the first network function 900. Examples of such data include: any computer program used to operate on the first network function 900.

[0350] The method disclosed in the above embodiment of the present application can be applied to the first processor 902, or implemented by the first processor 902. The first processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware or software instructions in the first processor 902. The above-mentioned first processor 902 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 902 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the first memory 903, and the first processor 902 reads the information in the first memory 903, and completes the steps of the above method in combination with its hardware.

[0351] In an exemplary embodiment, the first network function 900 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

[0352] Based on the hardware implementation of the above program module, and in order to implement the method of calling the entity side of the embodiment of the present application, the embodiment of the present application also provides a calling entity. Fig.10 As shown, the call entity 1000 includes:

[0353] The second communication interface 1001 is capable of exchanging information with other network nodes;

[0354] The second processor 1002 is connected to the second communication interface 1001 to implement information exchange with other network nodes, and is used to execute the method provided by one or more technical solutions of the calling entity side when running a computer program. The computer program is stored in the second memory 1003.

[0355] Specifically, the second communication interface 1001 is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee the new call DC service;

[0356] The second processor 1002 is used to determine whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

[0357] In one embodiment, the setting operation includes one or more of the following:

[0358] Negotiating IMSDC media with the terminal;

[0359] Trigger new call DC service.

[0360] In one embodiment, the second communication interface 1001 is specifically used to receive a second request sent by the terminal through the second network function and the first network function; wherein the second request represents that the terminal initiates a call for video media and data channel media, and the second request carries at least the first information.

[0361] In one embodiment, the second communication interface 1001 is further configured to perform one or more of the following when the setting operation is not allowed:

[0362] Reporting a call start event that does not include DC media information to the service application entity;

[0363] receiving a first instruction sent by a service application entity, wherein the first instruction does not carry DC media information;

[0364] Sending a second response to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero;

[0365] Not reporting a call start event about a first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication;

[0366] Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service represents a new call DC service triggered by the setting operation indication;

[0367] A second instruction regarding a second service sent by the service application entity is received, where the second service represents a new call DC service triggered by the setting operation indication.

[0368] In one embodiment, the second communication interface 1001 is specifically used to receive a first message sent by the terminal through the second network function and the first network function, the first message indicating that the terminal has received a call request for video media and data channel media, and the first message carries the first information.

[0369] In one embodiment, the second communication interface 1001 is further configured to perform one or more of the following when the setting operation is not allowed:

[0370] Sending a third request to the media entity, where the third request carries the audio and video SDP information of the terminal, is used to request the audio and video media, and indicates to delete the DC media information of the terminal;

[0371] receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information;

[0372] Sending a second message to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero;

[0373] Reporting a control result failure notification message about the first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication.

[0374] In one embodiment, the first information is carried in the User-Agent header field of the second request.

[0375] In one embodiment, the first information is carried in a Server header field of the first message.

[0376] It should be noted that the specific processing process of the second processor 1002 and the second communication interface 1001 can be understood by referring to the above method.

[0377] Of course, in actual application, the various components in the call entity 1000 are coupled together through the bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.10 Various buses are labeled as bus system 1004 .

[0378] The second memory 1003 in the embodiment of the present application is used to store various types of data to support the operation of the call entity 1000. Examples of such data include: any computer program used to operate on the call entity 1000.

[0379] The method disclosed in the above embodiment of the present application can be applied to the second processor 1002, or implemented by the second processor 1002. The second processor 1002 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the second processor 1002. The above-mentioned second processor 1002 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 1002 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 1003, and the second processor 1002 reads the information in the second memory 1003 and completes the steps of the above method in combination with its hardware.

[0380] In an exemplary embodiment, the call entity 1000 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned methods.

[0381] It can be understood that the memory (first memory 903 and second memory 1003) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a ferromagnetic random access memory, a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0382] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 903 storing a computer program, and the computer program can be executed by the first processor 902 of the first network function 900 to complete the steps of the first network function side method. For another example, a second memory 1003 storing a computer program can be executed by the second processor 1002 of the call entity 1000 to complete the steps of the call entity side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.

[0383] Exemplarily, the embodiment of the present application further provides a computer program product, including a computer program, which can be executed by the first processor 902 of the first network function 900 to complete the steps of the first network function side method. The computer program can be executed by the second processor 1002 of the call entity 1000 to complete the steps of the call entity side method.

[0384] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Multi-items can be two or more items, and a plurality can be two or more. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "one or more" in this article means any combination of at least two of any one or more of a plurality. For example, including one or more of A, B, and C can mean including any one or at least two or more elements selected from the set consisting of A, B, and C.

[0385] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.

[0386] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.

Claims

1. A communication method, characterized in that: Applied to a first network function, the method comprises: Receive first information; wherein the first information indicates whether the terminal supports IP Multimedia Subsystem Data Channel IMSDC, and / or indicates whether the terminal can guarantee a new call DC service; Based on the first information, it is determined whether to allow or not to allow the terminal to register with IMSDC.

2. The method according to claim 1, characterized in that: The determining, based on the first information, whether to allow or not to allow the terminal to register with the IMSDC includes: When the first information indicates that the terminal supports IMSDC and / or can guarantee the new call DC service, allowing the terminal to register IMSDC; or When the first information indicates that the terminal does not support IMSDC and / or cannot guarantee the new call DC service, the terminal is not allowed to register for IMSDC.

3. The method according to claim 1 or 2, characterized in that: The receiving of the first information comprises: receiving a first request sent by the terminal through a second network function; wherein, The first request indicates that the terminal requests to register with IMSDC, and the first request carries at least the first information.

4. The method according to claim 3, characterized in that The method further comprises: Sending a first response to the terminal through the second network function; wherein, In the case where the first information indicates that the terminal supports IMSDC or can guarantee a new call DC service, the first response indicates that the terminal is allowed to register IMSDC and carries a first identifier, where the first identifier indicates that the network provides DC capability to the terminal; When the first information indicates that the terminal does not support IMSDC or cannot guarantee the new call DC service, the first response indicates that the terminal is not allowed to register for IMSDC and does not carry the first identifier.

5. The method according to claim 3, characterized in that: The first information is carried in a User-Agent header field of the first request; and / or The Contact header field of the first request carries a second identifier, where the second identifier indicates whether the terminal has IMSDC capability.

6. A communication method, characterized in that: Applied to a calling entity, the method comprises: Receiving first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service; It is determined whether to allow or not to allow a setting operation to be performed based on the first information, where the setting operation represents a DC-related operation.

7. The method according to claim 6, characterized in that The setting operation includes one or more of the following: Negotiating IMSDC media with the terminal; Trigger new call DC service.

8. The method according to claim 6, characterized in that The receiving of the first information comprises: A second request is received, which is sent by the terminal through the second network function and the first network function; wherein the second request represents that the terminal initiates a call for video media and data channel media, and the second request carries at least the first information.

9. The method according to any one of claims 6 to 8, characterized in that: The method further comprises: If the setting operation is not allowed, perform one or more of the following: Reporting a call start event that does not include DC media information to the service application entity; receiving a first instruction sent by a service application entity, wherein the first instruction does not carry DC media information; Sending a second response to the terminal through the first network function and the second network function, where the second response carries first media information, and a DC media port in the first media information is zero; Not reporting a call start event about a first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication; Reporting a call start event containing DC media information about a second service to a service application entity, wherein the second service represents a new call DC service triggered by the setting operation indication; A second instruction regarding a second service sent by the service application entity is received, where the second service represents a new call DC service triggered by the setting operation indication.

10. The method according to claim 6, characterized in that The receiving of the first information comprises: A first message sent by the terminal through the second network function and the first network function is received, where the first message indicates that the terminal has received a call request for video media and data channel media, and the first message carries the first information.

11. The method according to claim 6, 7 or 10, characterized in that The method further comprises: If the setting operation is not allowed, perform one or more of the following: Sending a third request to the media entity, where the third request carries the audio and video session description SDP information of the terminal, is used to request audio and video media, and instructs to delete the DC media information of the terminal; receiving second media information sent by the media entity, where the second media information includes audio and video media information but does not include DC media information; Sending a second message to the terminal through the first network function and the second network function, where the second message carries third media information, and a DC media port in the third media information is zero; Reporting a control result failure notification message about the first service to the service application entity, wherein the first service represents a new call DC service that is not allowed to be triggered by the setting operation indication.

12. The method according to claim 8, characterized in that The first information is carried in the User-Agent header field of the second request.

13. The method according to claim 10, characterized in that The first information is carried in the service Server header field of the first message.

14. A communication device, characterized in that: include: A first receiving unit, configured to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service; The first processing unit is configured to determine whether to allow or not to allow the terminal to register with the IMSDC based on the first information.

15. A communication device, characterized in that: include: A second receiving unit, configured to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service; The second processing unit is used to decide whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

16. A first network function, characterized in that: include: A first processor and a first communication interface; wherein, The first communication interface is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service; The first processor is configured to determine whether to allow or not to allow the terminal to register with the IMSDC based on the first information.

17. A calling entity, characterized in that: include: A second processor and a second communication interface; wherein, The second communication interface is used to receive first information; wherein the first information indicates whether the terminal supports IMSDC and / or indicates whether the terminal can guarantee a new call DC service; The second processor is used to determine whether to allow or not to allow a setting operation based on the first information, where the setting operation represents a DC-related operation.

18. A first network function, characterized in that: comprising a first processor and a first memory for storing a computer program capable of being executed on the first processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 5 are executed.

19. A calling entity, characterized in that: comprising a second processor and a second memory for storing a computer program executable on the second processor, Wherein, when the second processor is used to run the computer program, the steps of the method described in any one of claims 6 to 13 are executed.

20. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 5 are implemented, or the steps of the method described in any one of claims 6 to 13 are implemented.

21. A computer program product, comprising a computer program, characterized in that The computer program implements the steps of the method according to any one of claims 1 to 13 when executed by a processor.

Images