Audio parameter negotiation method and communication device

Abstract

An audio parameter negotiation method and a communication device, the method comprising: a second communication entity negotiates an audio parameter based on an IVAS encoded audio format and an IVAS decoded audio format supported by a first communication entity, and an IVAS encoded audio format and an IVAS decoded audio format supported by the second communication entity; transmitting fifth audio format information indicating at least one fifth audio format and sixth audio format information indicating at least one sixth audio format to the first communication entity, the fifth audio format information indicating at least one fifth audio format, and the sixth audio format information indicating at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity during IVAS decoding and / or the second communication entity during IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity during IVAS encoding and / or the second communication entity during IVAS decoding. According to the method, the negotiation of the IVAS coding and decoding audio format with finer granularity can be realized.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and a communication device for negotiating audio parameters. Background Art

[0002] Traditional voice codecs such as adaptive multiRate (AMR) and enhanced voice services (EVS) only support mono audio and cannot support the immersive voice experience required by extended reality (XR) services. Immersive voice and audio services (IVAS) voice codec is a new immersive voice codec that supports more audio format types and a wider range of rates than traditional voice codecs. It also includes additional rendering features to bring a better voice call experience. IVAS voice codec supports multiple audio formats, each of which includes an audio format type and the rate supported by the audio format type. For example, according to the complexity of the audio format type from low to high, the audio format type can include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo, and multi-channel. The main technologies include high-definition ambisonics (FOA), higher-order ambisonics (HOA), metadata-assisted spatial audio (MASA), etc.

[0003] Currently, when negotiating voice codec parameters, terminal #1 and terminal #2 will negotiate the codec type and rate. In a possible scenario, terminal #1 and terminal #2 determine that the voice codec type used in subsequent audio communications is the IVAS voice codec. Since the IVAS voice codec is a complex codec that supports multiple audio formats, how to achieve more fine-grained IVAS codec audio format negotiation based on the determination to use the IVAS codec becomes an urgent problem to be solved. Summary of the invention

[0004] The present application provides a method and a communication device for audio parameter negotiation, which can achieve more fine-grained negotiation of IVAS codec audio formats.

[0005] In a first aspect, a method for negotiating audio parameters is provided. The method may be executed by a second communication entity or by a component (such as a chip or a circuit) of the second communication entity.

[0006] The method includes: receiving first audio format information and second audio format information, the first audio format information indicating at least one first audio format, the second audio format information indicating at least one second audio format, the first audio format being an audio format that can be adopted by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format being an audio format that can be adopted by the first communication entity when performing IVAS decoding; based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, sending fifth audio format information and sixth audio format information, wherein the third audio format information indicates at least one third audio format, the fourth The audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0007] In the above technical scheme, a more fine-grained IVAS voice codec negotiation mechanism is provided. On the basis of the use of IVAS voice codec by the first communication entity and the second communication entity, the IVAS encoding audio format and IVAS decoding audio format used by the first communication entity and the second communication entity during audio communication are further negotiated, so that the first communication entity and the second communication entity can use appropriate IVAS encoding audio format and IVAS decoding audio format for audio communication according to the IVAS codec capabilities actually supported by the first communication entity and the second communication entity.

[0008] In the above technical solution, through the negotiation of IVAS codec audio format with finer granularity, power consumption and bandwidth waste can also be avoided. Specifically explain the beneficial effect, at present, the audio format used for IVAS encoding and the audio format used for IVAS decoding of a terminal can be different, for example, the audio formats used for IVAS encoding and IVAS decoding of terminal #1 are audio format #1 and audio format #2, respectively, and the audio formats used for IVAS encoding and IVAS decoding of terminal #2 are audio format #3 and audio format #4, respectively. Then, in the process of audio data transmission between terminal #1 and terminal #2, terminal #1 and terminal #2 will perform encoding and decoding processing according to the audio format corresponding to the maximum IVAS encoding and decoding capability currently supported by themselves, for example, the maximum IVAS encoding capability of terminal #1 is greater than the maximum IVAS decoding capability of terminal #2, terminal #1 encodes the voice content to be sent based on the maximum IVAS encoding capability supported by itself to generate audio data #1 and send it to terminal #2, terminal #2 can only use its maximum IVAS decoding capability to decode audio data #1, due to the unequal encoding and decoding capabilities of terminal #1 and terminal #2, it will lead to the waste of encoding power consumption of terminal #1. In addition, the higher the IVAS coding capability, the more bandwidth the generated audio data needs to occupy during transmission. Therefore, encoding according to the coding capability of terminal #1 will also cause a waste of bandwidth. Based on the method proposed in this application, the second communication entity and the first communication entity perform IVAS coding and IVAS decoding based on the fifth audio format information, respectively. Therefore, the IVAS coding capability of the second communication entity and the IVAS decoding capability of the first communication entity are equal. Then, no matter whether the second communication entity encodes based on any fifth audio format indicated in the fifth audio format information, the first communication entity can use the equal IVAS decoding capability for decoding, and therefore, no power consumption and bandwidth waste will be caused. Similarly, the second communication entity and the first communication entity perform IVAS decoding and IVAS coding based on the sixth audio format information, respectively, that is, the IVAS decoding capability of the second communication entity and the IVAS coding capability of the first communication entity are equal. Then, no matter whether the first communication entity encodes based on any sixth audio format indicated in the sixth audio format information, the second communication entity can use the equal IVAS decoding capability for decoding, thereby avoiding power consumption and bandwidth waste.

[0009] It should be noted that in a possible scenario, if the first communication entity and the second communication entity only perform one-way audio communication. For example, between the first communication entity and the second communication entity, only the first communication entity can send audio data to the second communication entity. Then, the first audio format information and the second audio format information can carry the audio format that the first communication entity can adopt when performing IVAS encoding. The first audio format information and the second audio format information can only carry the first audio format information without carrying the second audio format information. For another example, between the first communication entity and the second communication entity, only the second communication entity can send audio data to the first communication entity. Then, the first audio format information and the second audio format information can only carry the second audio format information without carrying the first audio format information.

[0010] In certain implementations of the first aspect, at least one fifth audio format is an intersection of at least one second audio format and at least one third audio format; and at least one sixth audio format is an intersection of at least one first audio format and at least one fourth audio format.

[0011] In certain implementations of the first aspect, receiving first audio format information and second audio format information includes: receiving the first audio format information and the second audio format information from a first communication entity; sending fifth audio format information and sixth audio format information includes: sending the fifth audio format information and the sixth audio format information to the first communication entity.

[0012] In certain implementations of the first aspect, receiving first audio format information and second audio format information from a first communication entity includes: receiving a first request message from the first communication entity, the first request message being an invite request message or a re-invite request message, the first request message including the first audio format information and the second audio format information; sending fifth audio format information and sixth audio format information to the first communication entity includes: sending a response message to the first request message to the first communication entity, the response message including the fifth audio format information and the sixth audio format information.

[0013] In certain implementations of the first aspect, the first communication entity is a calling terminal device and the second communication entity is a called terminal device, or the first communication entity is a calling terminal device and the second communication entity is a media resource function network element, or the first communication entity is a media resource function network element and the second communication entity is a called terminal device.

[0014] In certain implementations of the first aspect, receiving first audio format information and second audio format information from a first communication entity includes: receiving a first response message from the first communication entity, the first response message is a 18X response message or a 200 response message, the first response message includes the first audio format information and the second audio format information, the 18X response message is a 180 response message or a 183 response message; sending fifth audio format information and sixth audio format information to the first communication entity includes: sending a confirmation message of the first response message to the first communication entity, the confirmation message includes the fifth audio format information and the sixth audio format information.

[0015] In certain implementations of the first aspect, the first communication entity is a called terminal device and the second communication entity is a calling terminal device, or the first communication entity is a called terminal device and the second communication entity is a media resource function network element, or the first communication entity is a media resource function network element and the second communication entity is a calling terminal device.

[0016] In certain implementations of the first aspect, receiving first audio format information and second audio format information includes: receiving first audio format information and second audio format information from a third communication entity; sending fifth audio format information and sixth audio format information includes: sending the fifth audio format information and sixth audio format information to the third communication entity.

[0017] In certain implementations of the first aspect, receiving first audio format information and second audio format information from a third communication entity includes: receiving a first request message from the third communication entity, the first request message being an invite request message or a re-invite request message, the first request message including the first audio format information and the second audio format information; sending fifth audio format information and sixth audio format information to the third communication entity includes: sending a response message to the first request message to the third communication entity, the response message including the fifth audio format information and the sixth audio format information.

[0018] In some implementations of the first aspect, the third communication entity is a proxy call session control function network element, the second communication entity is a called terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

[0019] In certain implementations of the first aspect, receiving first audio format information and second audio format information from a third communication entity includes receiving a first response message from the third communication entity, the first response message is a 18X response message or a 200 response message, the first response message includes the first audio format information and the second audio format information, the 18X response message is a 180 response message or a 183 response message; sending fifth audio format information and sixth audio format information to the third communication entity includes: sending a confirmation message of the first response message to the third communication entity, the confirmation message includes the fifth audio format information and the sixth audio format information.

[0020] In some implementations of the first aspect, the third communication entity is a proxy call session control function network element, the second communication entity is a calling terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

[0021] In certain implementations of the first aspect, the method further includes: sending first audio data to the first communication entity, where the first audio data is generated by performing IVAS encoding based on the fifth audio format information.

[0022] In certain implementations of the first aspect, the method further includes: receiving second audio data from the first communication entity; and performing IVAS decoding on the second audio data based on the sixth audio format information.

[0023] In certain implementations of the first aspect, any audio format information from the first audio format information to the fourth audio format information includes a type and a rate of each audio format indicated accordingly.

[0024] In certain implementations of the first aspect, sending fifth audio format information and sixth audio format information based on first audio format information and second audio format information and third audio format information and fourth audio format information includes: determining the fifth audio format information and sixth audio format information based on the first audio format information and second audio format information and the third audio format information and fourth audio format information.

[0025] In certain implementations of the first aspect, determining fifth audio format information and sixth audio format information based on first audio format information and second audio format information and third audio format information and fourth audio format information includes: determining fifth audio format information and sixth audio format information based on a first strategy, first audio format information and second audio format information and third audio format information and fourth audio format information, wherein the first strategy is to search from high to low complexity of at least one third audio format type, or the first strategy is to search from high to low complexity of at least one fourth audio format type.

[0026] In certain implementations of the first aspect, the types of audio formats supported by the IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, higher-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA.

[0027] In a second aspect, a method for negotiating audio parameters is provided. The method may be executed by a first communication entity or by a component (such as a chip or a circuit) of the first communication entity.

[0028] The method includes: sending first audio format information and second audio format information to a second communication entity, the first audio format information indicating at least one first audio format, the second audio format information indicating at least one second audio format, the first audio format being an audio format that can be adopted by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format being an audio format that can be adopted by the first communication entity when performing IVAS decoding; receiving fifth audio format information and sixth audio format information from the second communication entity, wherein the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information indicating at least one fifth audio format, the sixth audio format information indicating at least one sixth audio format, the fifth audio format being an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format being an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0029] For the beneficial effects of the second aspect, please refer to the description of the first aspect and will not be repeated here.

[0030] In certain implementations of the second aspect, sending first audio format information and second audio format information includes: sending the first audio format information and the second audio format information to a second communication entity; receiving fifth audio format information and sixth audio format information includes: receiving the fifth audio format information and the sixth audio format information from the second communication entity.

[0031] In certain implementations of the second aspect, the method further includes: receiving first audio data from a second communication entity; and performing IVAS decoding on the first audio data based on the first audio format.

[0032] In certain implementations of the second aspect, the method further includes: sending second audio data to a second communication entity, where the second audio data is generated by IVAS encoding based on a second audio format.

[0033] In certain implementations of the second aspect, sending first audio format information and second audio format information to a second communication entity includes: sending a first request message to the second communication entity, the first request message being an invite request message or a re-invite request message, the first request message including the first audio format information and the second audio format information; receiving fifth audio format information and sixth audio format information from the second communication entity includes: receiving a response message to the first request message from the second communication entity, the response message including the fifth audio format information and the sixth audio format information.

[0034] In certain implementations of the second aspect, the first communication entity is a calling terminal device and the second communication entity is a called terminal device, or the first communication entity is a calling terminal device and the second communication entity is a media resource function network element, or the first communication entity is a media resource function network element and the second communication entity is a called terminal device.

[0035] In certain implementations of the second aspect, sending first audio format information and second audio format information to a second communication entity includes: sending a first response message to the second communication entity, the first response message being a 18X response message or a 200 response message, the first response message including the first audio format information and the second audio format information, the 18X response message being a 180 response message or a 183 response message; receiving fifth audio format information and sixth audio format information from the second communication entity, including: receiving a confirmation message of the first response message from the second communication entity, the confirmation message including the fifth audio format information and the sixth audio format information.

[0036] In certain implementations of the second aspect, the first communication entity is a called terminal device and the second communication entity is a calling terminal device, or the first communication entity is a called terminal device and the second communication entity is a media resource function network element, or the first communication entity is a media resource function network element and the second communication entity is a calling terminal device.

[0037] In certain implementations of the second aspect, the audio format types supported by the IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, higher-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA.

[0038] According to a third aspect, a method for negotiating audio parameters is provided. The method may be executed by a third communication entity or by a component (such as a chip or a circuit) of the third communication entity.

[0039] The method includes: sending first audio format information and second audio format information to a second communication entity, the first audio format information indicating at least one first audio format, the second audio format information indicating at least one second audio format, the first audio format being an audio format that can be adopted by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format being an audio format that can be adopted by the first communication entity when performing IVAS decoding; receiving fifth audio format information and sixth audio format information from the second communication entity, wherein the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information indicating at least one fifth audio format, the sixth audio format information indicating at least one sixth audio format, the fifth audio format being an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format being an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0040] For the beneficial effects of the third aspect, please refer to the description of the first aspect and will not be repeated here.

[0041] In certain implementations of the third aspect, sending first audio format information and second audio format information includes: sending the first audio format information and the second audio format information to a second communication entity; receiving fifth audio format information and sixth audio format information includes: receiving the fifth audio format information and the sixth audio format information from the second communication entity.

[0042] In some implementations of the third aspect, the fifth audio format information and the sixth audio format information are sent to the first communication entity.

[0043] In certain implementations of the third aspect, sending first audio format information and second audio format information to a second communication entity includes: sending a first request message to the second communication entity, the first request message being an invite request message or a re-invite request message, the first request message including the first audio format information and the second audio format information; receiving fifth audio format information and sixth audio format information from the second communication entity includes: receiving a response message to the first request message from the second communication entity, the response message including the fifth audio format information and the sixth audio format information.

[0044] In certain implementations of the third aspect, the second communication entity is a called terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

[0045] In certain implementations of the third aspect, sending first audio format information and second audio format information to a second communication entity includes: sending a first response message to the second communication entity, the first response message is a 18X response message or a 200 response message, the first response message includes the first audio format information and the second audio format information, the 18X response message is a 180 response message or a 183 response message; receiving fifth audio format information and sixth audio format information from the second communication entity includes: receiving a confirmation message of the first response message from the second communication entity, the confirmation message includes the fifth audio format information and the sixth audio format information.

[0046] In some implementations of the third aspect, the second communication entity is a calling terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

[0047] In certain implementations of the third aspect, any audio format information from the first audio format information to the sixth audio format information includes a type and a rate of each audio format indicated accordingly.

[0048] In some implementations of the third aspect, the audio format types supported by the IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, high-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA. In some implementations of the third aspect, the audio format includes an audio format type and a rate set corresponding to the audio format type.

[0049] In a fourth aspect, a method for negotiating audio parameters is provided. The method may be executed by a first communication entity or by a component (such as a chip or a circuit) of the first communication entity.

[0050] The method includes: receiving fifth audio format information and sixth audio format information, wherein the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing immersive voice and audio service IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; and transmitting audio data with the second communication entity based on the fifth audio format information and the sixth audio format information.

[0051] Regarding the beneficial effects of the fourth aspect, please refer to the description in the first aspect and will not be repeated here.

[0052] In certain implementations of the fourth aspect, audio data transmission is performed with a first communication entity based on fifth audio format information and sixth audio format information, including: receiving first audio data from a second communication entity; and performing IVAS decoding on the first audio data based on the fifth audio format information.

[0053] In certain implementations of the fourth aspect, audio data transmission is performed with a first communication entity based on fifth audio format information and sixth audio format information, including: sending second audio data to a second communication entity, the second audio data being generated by IVAS encoding based on the sixth audio format information.

[0054] In some implementations of the fourth aspect, receiving the fifth audio format information and the sixth audio format information includes: receiving the fifth audio format information and the sixth audio format information from a third communication entity.

[0055] In certain implementations of the fourth aspect, the third communication entity is a proxy call session control function network element, the second communication entity is a called terminal device, and the first communication entity is a network protocol multimedia subsystem access gateway; or, the third communication entity is a proxy call session control function network element, the second communication entity is a calling terminal device, and the first communication entity is a network protocol multimedia subsystem access gateway.

[0056] In certain implementations of the fourth aspect, any one of the fifth audio format information and the sixth audio format information includes a type and a rate of each audio format indicated accordingly.

[0057] In some implementations of the fourth aspect, the audio format types supported by the IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, high-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA. In some implementations of the fourth aspect, the audio format includes an audio format type and a rate set corresponding to the audio format type.

[0058] In a fifth aspect, a method for negotiating audio parameters is provided. The method may be executed by a third communication entity or by a component (such as a chip or a circuit) of the third communication entity.

[0059] The method includes: receiving first audio format information and second audio format information, wherein the first audio format information indicates at least one first audio format, the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, sending fifth audio format information and sixth audio format information, wherein the third audio format information indicates at least one third audio format, the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one fifth ... fifth audio format information indicates at least one fifth audio format, the fifth audio format information indicates at least one fifth audio format, the fifth audio format information indicates at least one fifth audio format, the fifth audio format information indicates at least one fifth audio format, the fifth audio format information indicates at least one fifth audio format, The four audio format information indicates at least one fourth audio format, the third audio format is the audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is the audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is the audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is the audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0060] In certain implementations of the fifth aspect, receiving first audio format information and second audio format information includes: receiving first audio format information and second audio format information from a first communication entity; sending fifth audio format information and sixth audio format information includes: sending fifth audio format information and sixth audio format information to the first communication entity and the second communication entity.

[0061] In certain implementations of the fifth aspect, receiving first audio format information and second audio format information from a first communication entity includes: receiving a first request message from the first communication entity, the first request message being an invite request message or a re-invite request message, the first request message including the first audio format information and the second audio format information; sending fifth audio format information and sixth audio format information to the first communication entity includes: sending a response message to the first request message to the first communication entity, the response message including the fifth audio format information and the sixth audio format information.

[0062] In some implementations of the fifth aspect, the third communication entity is a proxy call session control function network element, the first communication entity is a calling terminal device, and the second communication entity is an Internet Protocol Multimedia Subsystem access gateway.

[0063] In a sixth aspect, a communication device is provided, which is used to execute the method provided in the first aspect. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method in any possible implementation of the first aspect.

[0064] In a seventh aspect, a communication device is provided, the device being used to execute the method provided in the second aspect or the fourth aspect. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method in any aspect of the second aspect or the fourth aspect or any possible implementation of the second aspect or the fourth aspect.

[0065] In an eighth aspect, a communication device is provided, the device being used to execute the method provided in the third aspect or the fifth aspect. Specifically, the device may include a unit and / or module, such as a processing unit and / or a communication unit, for executing the method in any aspect of the third aspect or the fifth aspect or any possible implementation of the third aspect or the fifth aspect.

[0066] In a ninth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the first aspect or any possible implementation of the first aspect. Optionally, the device also includes a memory. Optionally, the device also includes a communication interface, and the processor is coupled to the communication interface.

[0067] In one implementation, the device is a second communication entity. When the device is a second communication entity, the communication interface may be a transceiver, or an input / output interface.

[0068] In another implementation, the device is a chip configured in the second communication entity. When the device is a chip configured in the second communication entity, the communication interface may be an input / output interface.

[0069] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0070] In a tenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in any of the second aspect or the fourth aspect or any possible implementation of the second aspect or the fourth aspect. Optionally, the device also includes a memory. Optionally, the device also includes a communication interface, and the processor is coupled to the communication interface.

[0071] In one implementation, the device is a first communication entity. When the device is a first communication entity, the communication interface may be a transceiver, or an input / output interface.

[0072] In another implementation, the device is a chip configured in the first communication entity. When the device is a chip configured in the first communication entity, the communication interface may be an input / output interface.

[0073] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0074] In an eleventh aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in any of the third aspect or the fifth aspect or any possible implementation of the third aspect or the fifth aspect. Optionally, the device further comprises a memory. Optionally, the device further comprises a communication interface, and the processor is coupled to the communication interface.

[0075] In one implementation, the device is a third communication entity. When the device is a third communication entity, the communication interface may be a transceiver, or an input / output interface.

[0076] In another implementation, the device is a chip configured in the third communication entity. When the device is a chip configured in the third communication entity, the communication interface may be an input / output interface.

[0077] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0078] In a twelfth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any one of the first to fourth aspects above.

[0079] In a thirteenth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer executes the method provided in any one of the first to fourth aspects.

[0080] In a fourteenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface to execute the method provided in any one of the first to fourth aspects above.

[0081] Optionally, as an implementation method, the chip may also include a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the method provided in any one of the first to fourth aspects above.

[0082] In a fifteenth aspect, a communication system is provided, which includes at least one communication entity among a second communication entity for executing the method shown in the first aspect, a first communication entity for executing the method shown in the second aspect or the fourth aspect, and a third communication entity for executing the method shown in the third aspect or the fifth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] Figure 1 It is a schematic diagram of a communication system applicable to the method provided in an embodiment of the present application.

[0084] Figure 2 It is a schematic diagram of a communication system applicable to the method provided in an embodiment of the present application.

[0085] Figure 3 3 is a schematic diagram of a method 300 for two parties in a call to negotiate a voice codec.

[0086] Figure 4 It is a schematic diagram of a method 400 for audio parameter negotiation provided in an embodiment of the present application.

[0087] Figure 5 It is a schematic diagram of a method 500 for audio parameter negotiation provided in an embodiment of the present application.

[0088] Figure 6 It is a schematic diagram of a method 600 for audio parameter negotiation provided in an embodiment of the present application.

[0089] Figure 7 It is a schematic diagram of a method 700 for audio parameter negotiation provided in an embodiment of the present application.

[0090] Figure 8 It is a schematic diagram of a method 800 for audio parameter negotiation provided in an embodiment of the present application.

[0091] Fig. 9 It is a schematic diagram of a method 900 for audio parameter negotiation provided in an embodiment of the present application.

[0092] Fig.10 It is a schematic diagram of a communication device 1100 provided in an embodiment of the present application.

[0093] Fig.11 It is a schematic diagram of another communication device 1200 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings.

[0095] Before introducing the embodiments of the present application, the following points are first explained.

[0096] 1. In the description of the embodiments of the present application, unless otherwise specified, “plurality” means two or more.

[0097] 2. In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0098] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate so that the embodiments described here can be implemented in an order other than that illustrated or described here.

[0099] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0100] 5. The terms “send” and “receive” in the embodiments of the present application indicate the direction of signal transmission. For example, “send information to XX” can be understood as the destination of the information is XX, which can include direct sending through the air interface, and indirect sending through the air interface by other units or modules. “Receive information from YY” can be understood as the source of the information is YY, which can include direct receiving from YY through the air interface, and indirect receiving from YY through the air interface from other units or modules. “Send” can also be understood as the “output” of the chip interface, and “receive” can also be understood as the “input” of the chip interface.

[0101] In other words, sending and receiving can be performed between devices, for example, between terminal device #1 and terminal device #2, or can be performed within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.

[0102] 6. In the embodiments of the present application, "indication" can be understood as "enablement", and "enablement" can include direct enabling and indirect enabling. When describing that a certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, but it does not mean that the information must carry A.

[0103] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as but not limited to, the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association relationship between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, the enabling of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified by the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0104] 7. In this application, "pre-configuration" may include pre-definition, for example, protocol definition. Among them, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including each network element), and this application does not limit its specific implementation method.

[0105] 8. The "storage" or "saving" involved in the embodiments of the present application may refer to storage in one or more memories. The one or more memories may be set separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, which is not limited by the present application.

[0106] 9. The “protocol” involved in the embodiments of the present application may refer to a standard protocol in the field of communications, for example, it may include a fourth generation (4G) network / fifth generation (5G) network protocol, a new radio (NR) protocol, and related protocols used in future communication systems. This application does not limit this.

[0107] 10. The dotted arrows or boxes in the schematic diagrams of the drawings in the specification of this application represent optional steps or optional modules.

[0108] The technical solution provided in this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) communication system (or called the new radio (new radio, NR) system), the fourth generation (4th generation, 4G) communication system (or called the long term evolution (long term evolution, LTE) system), LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc. The technical solution provided in this application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.

[0109] Figure 1 It is a schematic diagram of a communication system applicable to the method provided in the embodiment of the present application. It should be understood that the communication system described in the present application is only an example and should not constitute any limitation to the present application.

[0110] exist Figure 1 In the communication system shown, the first communication device and the second communication device communicate via an IP multimedia subsystem (IMS) network, wherein the first communication device and the second communication device may be any electronic device with voice interaction capability.

[0111] For example, the first communication device or the second communication device is a user equipment (UE), and the UE may be any device capable of accessing a network, and may also be referred to as terminal equipment, terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. UE may be a device that provides voice / data connectivity to a user, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals may be: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile Internet devices (MID), virtual reality (VR) devices, AR devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 4G / 5G networks, or public land mobile communication networks that will evolve in the future. In addition, UE can also be a UE in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.In addition, UE can also include smart printers, train detectors, etc. Its main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment.

[0112] For another example, the first communication device or the second communication device is a network device in a communication network, such as an application server.

[0113] In one example, the first communication device is a calling device (i.e., a device initiating a call), and the second communication device is a called device (i.e., a called device); in another example, the first communication device is a called device, and the second communication device is a calling device.

[0114] In one example, the IMS network includes an IMS core network (IMS Core) and an application server (AS), and the first communication device and the second communication device can be connected to the AS through the IMS Core, wherein the IMS Core includes a call session control function (CSCF) network element and an IMS access media gateway (AGW). The specific architecture is as follows: Figure 2 As shown. It is understandable that the IMS network may also include other network devices, for example, a media resource function (MRF) network element, which is not limited in this application. The network elements involved in the IMS network are described in an exemplary manner in turn.

[0115] 1. CSCF network element: CSCF is a functional entity within IMS and is the core of the entire IMS. It is mainly responsible for processing signaling control during multimedia call sessions. It manages IMS user authentication, IMS bearer plane quality of service (QoS), cooperates with other network elements to control session initiation protocol (SIP) sessions, as well as service negotiation and resource allocation. For the sake of convenience, the CSCF network element in this application is referred to as "CSCF".

[0116] The CSCF may communicate with the terminal device, and the CSCF may communicate with the gateway device. For example, the CSCF may select a gateway device to communicate with the terminal device, and the CSCF may allocate routing information, such as an IP address or port, to the terminal device and the gateway device.

[0117] As an example but not limitation, CSCF is divided into proxy CSCF (P-CSCF), interrogating CSCF (I-CSCF), serving CSCF (S-CSCF), etc. according to function.

[0118] Among them, P-CSCF is the entry point for users to access the IMS network, and is mainly responsible for forwarding SIP signaling between IMS users and their home networks. I-CSCF is the unified entry point for IMS users' home networks, and is responsible for allocating or querying S-CSCFs that serve users. S-CSCF is the unified entry point for IMS users' home networks, and is responsible for allocating or querying S-CSCFs that serve users.

[0119] It can be understood that the above-mentioned P-CSCF, S-CSCF, and I-CSCF can be independently configured in different entities or integrated in the same entity, and this application does not limit this.

[0120] 2. IMS-access media gateway (AGW): IMS-AGW can provide IMS network access gateway and media gateway functions.

[0121] It is understandable that CSCF and IMS-AGW can be collectively referred to as IMS core. This application does not limit the signaling interaction mode between network elements in the IMS core.

[0122] 3. AS: AS is an application layer device located at the upper layer of the IMS system, providing basic and supplementary services, such as multimedia conferencing, video ringback tone, video ringback tone, converged communication, SMS gateway, standard attendant console and other services.

[0123] 4. MRF network element: responsible for the control and processing of media resources, serving the business process of AS. AS can achieve functions such as playing, collecting numbers, and conferencing by controlling MRF.

[0124] The above-mentioned network architecture applied to the embodiment of the present application is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application, that is, the network architecture and business scenarios described in the embodiment of the present application are for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0125] It can be understood that the network elements or devices listed in the above network architecture are only exemplary, and the network architecture applicable to the present application may also include other network elements or devices, which is not limited in the present application.

[0126] It is also understandable that the naming of the above network elements or devices is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other names in 4G networks, 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 4G / 5G, or may use other names.

[0127] IVAS voice codec is a new immersive voice codec that supports more audio formats and additional rendering features compared to traditional voice codecs, which can bring a better voice call experience. The parameters corresponding to an audio format supported by IVAS voice codec include the type of the audio format and the rate that the type of audio format can adopt. For example, according to the complexity of the audio format type from low to high, the types of audio formats include mono, stereo, multi-channel, multi-objects, first-order ambisonics (FOA), higher-order ambisonics (HOA), metadata-assisted spatial audio (MASA), etc. Among them, multi-channel can support up to 7.1.4 channel format, that is, 12 channels, and HOA supports up to 3 orders, that is, 16 channels. In addition, the IVAS voice codec supports a rate range from 5.9kbps for mono to 768kbps for 3rd order HOA, and its rendering supports various audio formats to binaural and standard speaker array rendering.

[0128] More signal channels, a larger rate range, and additional rendering features make the computational complexity and storage complexity of IVAS codec significantly increased compared to traditional speech codecs. In the design of IVAS speech codec standard, three levels of different complexity are specified, namely level 1 (less than 3 times the EVS computational complexity), level 2 (less than 6 times the EVS computational complexity) and level 3 (less than 10 times the EVS computational complexity). For ease of description, level 1, level 2, and level 3 are referred to as L1, L2, and L3, respectively, in this application. Among them, L1 supports the encoding and decoding of audio formats corresponding to mono, stereo, FOA, and MASA, L2 supports the encoding and decoding of audio formats corresponding to multi-channel and multi-object on the basis of L1, and L3 supports the encoding and decoding of audio formats corresponding to up to 3rd order HOA on the basis of L2.

[0129] Figure 3 3 is a schematic diagram of a method 300 for two parties to negotiate a voice codec. During the voice call establishment process, the two parties need to negotiate a voice codec. The parameters involved in the voice codec negotiation mainly include the voice codec type and rate. Figure 3 As shown, the method 300 includes the following steps.

[0130] S310, the first communication entity sends information #1 to the second communication entity. Correspondingly, the second communication entity receives information #1 from the first communication entity.

[0131] The information #1 carries parameters such as the type of speech codec supported by the first communication entity (eg, AMR, EVS, etc.) and the corresponding rate.

[0132] S320, the second communication entity determines result #1 according to its own speech coding and decoding capability.

[0133] Result #1 includes the speech codec types and corresponding rate information supported by both the first communication entity and the second communication entity.

[0134] For example, the first communication entity may be regarded as an offerer, and the second communication entity may be regarded as an answerer.

[0135] S330, the second communication entity sends information #2 to the first communication entity, where the information #2 includes result #1. Correspondingly, the first communication entity receives information #2 from the second communication entity.

[0136] Currently, when negotiating voice codec parameters, Terminal #1 and Terminal #2 will only negotiate the codec type and rate. In a possible scenario, Terminal #1 and Terminal #2 determine that the voice codec type used in subsequent audio communications is the IVAS voice codec. Since the IVAS voice codec is a complex codec that supports multiple audio formats, how to achieve more fine-grained IVAS codec audio format negotiation based on the determination to use the IVAS codec becomes an urgent problem to be solved.

[0137] In view of this, the present application proposes a method for audio parameter negotiation, which can effectively solve the above technical problems. The method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0138] Figure 4 4 is a schematic diagram of a method 400 for audio parameter negotiation provided in an embodiment of the present application. The method 400 may include the following steps.

[0139] S410, the second communication entity receives first audio format information and second audio format information, wherein the first audio format information indicates at least one first audio format, the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding.

[0140] For example, in the embodiment of the present application, a parameter corresponding to an audio format includes an audio format type (hereinafter referred to as an audio format type) and a rate. For example, the audio format parameters corresponding to audio format #1 include {FOA, 24}, which means that the audio format type corresponding to audio format #1 is FOA, and the rate supported by FOA is 24kbps.

[0141] It should be understood that the unit of the rate supported by the audio format type in the embodiment of the present application is kbps, and the relevant parts will not be repeated one by one in the following text.

[0142] Based on the above examples, the audio format type corresponding to at least one first audio format indicated by the first audio format information may be the same or different. For example, if the first audio format information indicates three first audio formats, the audio format parameters corresponding to the three first audio formats are {MONO, 5.9}, {MONO, 7.2}, {MONO, 9.6}, or the audio format parameters corresponding to the three first audio formats are {MONO, 5.9}, {MONO, 7.2}, {FOA, 24}, or the audio format parameters corresponding to the three first audio formats are {MONO, 5.9}, {STEREO, 13}, {FOA, 24}, and the present application does not make specific limitations on this. Similarly, the audio format type corresponding to at least one second audio format indicated by the second audio format information may be the same or different, and examples are not given one by one here.

[0143] For ease of description, in the embodiment of the present application, the audio format that can be used by communication entity #1 when performing IVAS encoding is referred to as the IVAS encoding audio format supported by communication entity #1, and the audio format that can be used by communication entity #1 when performing IVAS decoding is referred to as the IVAS decoding audio format supported by communication entity #1.

[0144] The following is an example of indicating the first audio format information and the second audio format information.

[0145] Example 1: The first audio format information and the second audio format information may be indicated by a table as shown in Table 1.

[0146] It should be noted that, in practice, since the encoding and decoding computing power of the first communication entity is limited, the encoding audio format and decoding audio format supported by the first communication entity will only provide fixed combinations. Combination 1, combination 2 and combination 3 in Table 1 can be regarded as 3 groups of audio format information, each group of audio format information includes corresponding first audio format information and second audio information. Here, combination 1 is taken as an example to illustrate the meaning of each parameter in Table 1. The parameter information corresponding to the encoded audio format in combination 1 (i.e., an example of the first audio format information) indicates 9 encoded audio formats (i.e., an example of 9 first audio formats), and the parameter information corresponding to the decoded audio format in combination 1 (i.e., an example of the second audio format information) indicates 3 decoded audio formats (i.e., an example of 3 second audio formats), wherein the audio format types of the 3 decoded audio formats are all MONO, and the supported rates are 5.9, 7.2, and 9.6 respectively. Among the 9 encoded audio formats, the audio format types of 3 encoded audio formats are all MONO, and the audio format types of 3 encoded audio formats are all STEREO. The audio format types of the remaining 3 encoded audio formats are FOA, wherein MONO supports rates of 5.9, 7.2, and 9.6 respectively, STEREO supports rates of 13.2, 24, and 32 respectively, and FOA supports rates of 24, 32, and 48 respectively.

[0147] Table 1

[0148]

[0149] Here, in conjunction with Table 1, the reason why only a fixed combination of coded audio formats and decoded audio formats is provided is explained. There are three types of decoded audio formats supported by the first communication entity, namely MONO in combination 1, STEREO in combination 2, and FOA in combination 3, wherein the rate set supported by decoding MONO is {5.9, 7.2, 9.6}, the rate set supported by decoding STEREO is {13.2, 24, 32}, and the rate set supported by decoding FOA is {24, 32, 48}. It can be seen that when the decoded audio format type supported by the first communication entity in combination 1 is MONO, the coded audio format types it can support are MONO, STEREO and FOA, and the maximum rates that these three audio format types can support are 9.6kbps, 32kbps and 48kbps respectively. When the decoded audio format type supported by the first communication entity in combination 2 is STEREO, the encoded audio format types it can support are still MONO, STEREO and FOA. However, since the overhead of decoding STEREO is greater than that of decoding MONO, the remaining computing power for encoding will decrease. At this time, the rate of encoding FOA cannot be supported to 48kbps, and can only support a maximum of 24kbps (the higher the rate, the greater the overhead). When the decoded audio format type supported by the first communication entity in combination 3 is FOA, since the overhead of decoding FOA is greater, the remaining computing power for encoding will be less than that of combination 2, and the remaining computing power can no longer support encoding FOA. At this time, the only two types of encoded audio formats that the first communication entity can support are MONO and STEREO, and the maximum supported rates are 9.6kbps and 32kbps, respectively. From the above description, it can be seen that the codec combination of the audio format is limited by the codec computing power of the first communication entity. If the encoding overhead is large, the decoding overhead must be reduced, and vice versa.

[0150] Example 2: The first audio format information and the second audio format information may be indicated together by tables such as those shown in Table 2 and Table 3.

[0151] As shown in Table 2, Table 2 includes combination 1, combination 2 and combination 3. Combination 1 is taken as an example to illustrate the meaning of each parameter in Table 1. Combination 1 includes a decoding audio format type MONO and three encoding audio format types MONO, STEREO and FOA supported by the first communication entity, wherein the maximum rate supported by decoding MONO is 9.6, the maximum rate supported by encoding MONO is 9.6, the maximum rate supported by encoding STEREO is 32, and the rate set supported by encoding FOA is 48. The meaning of each parameter in Table 2 for combination 2 and combination 3 is the same as that of combination 1, and will not be repeated here.

[0152] For example, in the present application, any one of combination 1, combination 2 and combination 3 can be understood as a set of IVAS codec audio format combinations supported by the first communication entity.

[0153] Table 2

[0154]

[0155] Table 3 gives the rate information supported by MONO, STEREO and FOA. As shown in Table 3, all rates supported by MONO are {5.9, 7.2, 9.6, 13.2}, all rates supported by STEREO are {13.2, 24, 32}, and all rates supported by FOA are {24, 32, 48}.

[0156] It should be understood that the rates supported by MONO, STEREO and FOA in Table 3 are the rates supported by preconfigured MONO, STEREO and FOA, and the corresponding maximum rates in Table 2 are the maximum rates that the first communication entity can actually support in the corresponding combination.

[0157] Table 3

[0158]

[0159] Then, the rate set corresponding to all the encoded audio format types and all the decoded audio format types in Table 2 can be jointly determined based on Table 2 and Table 3, that is, the first capability can be jointly determined based on Table 2 and Table 3. For example, the maximum rate supported by the decoded MONO in combination 1 in Table 2 is 9.6, and all the rates that can be supported by MONO in Table 3 are {5.9, 7.2, 9.6, 13.2}, then the rate that the decoded MONO in combination 1 can actually support is {5.9, 7.2, 9.6}. For another example, the maximum rate supported by the encoded FOA in combination 2 in Table 2 is 24, and all the rates that can be supported by FOA in Table 3 are {24, 32, 48}, then the rate that the encoded FOA in Table 2 can actually support is {24}.

[0160] For example, it can be understood that the rate that the decoded MONO in combination 1 can actually support is {5.9, 7.2, 9.6}, which means that the first communication entity supports three encoded audio formats, and the parameters corresponding to the three encoded audio formats are {MONO, 5.9}, {MONO, 7.2}, and {MONO, 9.6}.

[0161] It can be seen that in Example 2, Table 2 and Table 3 jointly indicate the first audio format information and the second audio format information. Compared with Table 1 in Example 1, it is not necessary to indicate all the rates actually supported by each audio format type, thereby saving signaling overhead.

[0162] S420: The second communication entity sends fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information.

[0163] Among them, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the third audio format information and the fourth audio format information contain third audio format information and fourth audio format information, the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format is an audio format that the first communication entity will adopt when performing IVAS decoding and / or the second communication entity will adopt when performing IVAS encoding, and the sixth audio format is an audio format that the first communication entity will adopt when performing IVAS encoding and / or the second communication entity will adopt when performing IVAS decoding.

[0164] It can be understood that the first audio format information and the second audio format information reflect the IVAS codec capability of the first communication entity, and the third audio format information and the fourth audio format information reflect the IVAS codec capability of the second communication entity.

[0165] The third audio format information and the fourth audio format information may also be indicated by the two corresponding examples of the first audio format information and the second audio format information in S410, which will not be described in detail here.

[0166] For example, since the first audio format information and the second audio format information are information sent to the second communication entity for audio parameter negotiation, the first audio format information and the second audio format information in the embodiment of the present application may also be referred to as audio parameter proposal information. Similarly, since the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information and the sixth audio format information in the embodiment of the present application may also be referred to as audio parameter response information.

[0167] It should be understood that the fifth audio format information and the sixth audio format information are audio parameter negotiation results obtained based on the audio formats supported by the first communication entity and the second communication entity, and the first communication entity and the second communication entity will then perform audio data transmission based on the audio parameter negotiation results. The description will not be expanded here for the time being, and the following will specifically describe how the first communication entity and the second communication entity use the audio parameter negotiation results in audio communication.

[0168] It can be understood that the fifth audio format is the audio format that the first communication entity will adopt when performing IVAS decoding and / or the second communication entity will adopt when performing IVAS encoding, and includes the following three descriptions. The first: the fifth audio format is the audio format that the first communication entity will adopt when performing IVAS decoding; the second: the fifth audio format is the audio format that the second communication entity will adopt when performing IVAS encoding; the third: the fifth audio format is the audio format that the first communication entity will adopt when performing IVAS decoding and the second communication entity will adopt when performing IVAS encoding. Since the fifth audio format and the sixth audio format are the audio parameter negotiation results corresponding to the first communication entity and the second communication entity, the first description can be considered to imply that the fifth audio format indicates the audio format that the second communication entity will adopt when performing IVAS encoding, and the second description can be considered to imply that the fifth audio format indicates the audio format that the first communication entity will adopt when performing IVAS decoding.

[0169] Similarly, the sixth audio format indicates that the audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding has a similar understanding and will not be elaborated here.

[0170] Optionally, at least one fifth audio format is the intersection of at least one second audio format and at least one third audio format; at least one sixth audio format is the intersection of at least one first audio format and at least one fourth audio format. The following takes the example that the parameters corresponding to the audio format include the type and rate of the audio format as an example to illustrate the intersection of 3 second audio formats and 4 third audio formats.

[0171] In example 1, the audio format parameters corresponding to the three second audio formats are {MONO, 5.9}, {MONO, 7.2}, and {MONO, 9.6}, and the parameters corresponding to the four third audio formats are {MONO, 5.9}, {MONO, 7.2}, {MONO, 9.6}, and {STEREO, 13.2}. In this example, the intersection of the three second audio formats and the four third audio formats is three fifth audio formats, and the parameters corresponding to the three fifth audio formats are {MONO, 5.9}, {MONO, 7.2}, and {MONO, 9.6}.

[0172] In example 2, the audio format parameters corresponding to the three second audio formats are {MONO, 5.9}, {MONO, 7.2}, and {STEREO, 13.2}, and the parameters corresponding to the four third audio formats are {MONO, 5.9}, {MONO, 7.2}, {STEREO, 13.2}, and {STEREO, 24}. In this example, the intersection of the three second audio formats and the four third audio formats is three fifth audio formats, and the parameters corresponding to the three fifth audio formats are {MONO, 5.9}, {MONO, 7.2}, and {STEREO, 13.2}.

[0173] Regarding the at least one sixth audio format being the intersection of at least one first audio format and at least one fourth audio format, please refer to the above description, and examples are not given one by one here.

[0174] It should be noted that the audio format type of at least one fifth audio format may be the same, or the audio format type of at least one fifth audio format may not be completely the same. For example, the audio format types of the three fifth audio formats obtained in Example 1 are all MONO, and the audio format types of the three fifth audio formats obtained in Example 2 are not completely the same, wherein the audio format types of two fifth audio formats are MONO, and the remaining fifth audio format type is STEREO.

[0175] In one possible scenario, when the audio format types of at least one fifth audio format are the same, such as MONO, the second communication entity can only perform IVAS encoding based on MONO, and the first communication entity can only perform decoding based on MONO. As in Example 1, since the audio format types of the three fifth audio formats are all MONO, the second communication entity can perform IVAS encoding on the voice content to be sent to the first communication entity based on one of the three fifth audio formats, generate audio data #1, and send audio data #1 to the first communication entity. Correspondingly, the second communication entity receives audio data #1 from the first communication entity and performs IVAS decoding on audio data #1 based on MONO.

[0176] For example, the second communication entity may perform IVAS encoding based on a fifth audio format selected from three fifth audio formats in the current network environment.

[0177] In another possible scenario, when the audio format types of at least one fifth audio format are not completely identical, for example, the second communication entity may perform IVAS encoding based on the audio format type with the highest complexity among at least one fifth audio format, and the first communication entity may perform IVAS encoding based on the audio format type with the highest complexity among at least one fifth audio format. As in Example 2, the audio format types of the three fifth audio formats are not completely identical, and the audio format type with the highest complexity among the three fifth audio formats is STEREO, then the second communication entity may perform IVAS encoding on the voice content to be sent to the first communication entity based on the fifth audio format corresponding to {STEREO, 13.2}, generate audio data #1, and send audio data #1 to the first communication entity, and correspondingly, the second communication entity receives audio data #1 from the first communication entity, and performs IVAS decoding on audio data #1 based on the fifth audio format corresponding to {STEREO, 13.2}.

[0178] It should be noted that the audio format type of at least one sixth audio format may be the same, and the audio format type of at least one sixth audio format may not be completely the same. For a specific description, refer to the description when the audio format type of at least one fifth audio format is the same or not completely the same, and examples are not given here one by one.

[0179] In a possible implementation, the second communication entity receiving the first audio format information and the second audio format information in S410 includes: the second communication entity receiving the first audio format information and the second audio format information from the first communication entity; and the second communication entity sending the fifth audio format information and the sixth audio format information in S420 includes: the second communication entity sending the fifth audio format information and the sixth audio format information to the first communication entity. The specific process of this implementation will be described in Figure 5 The method 500 shown is described in detail and will not be described in detail here.

[0180] In another possible implementation, the second communication entity receiving the first audio format information and the second audio format information in S410 includes: the second communication entity receiving the first audio format information and the second audio format information from the third communication entity; the second communication entity sending the fifth audio format information and the sixth audio format information in S410 includes: the second communication entity sending the fifth audio format information and the sixth audio format information to the third communication entity. The specific process of this implementation will be described in Figure 8 The method 800 shown is described in detail and will not be described in detail here.

[0181] For example, in a possible scenario, if the first communication entity and the second communication entity only conduct one-way audio communication, for example, the audio data can only be sent from the second communication entity to the first communication entity between the first communication entity and the second communication entity, then in S410, the first audio format information and the second audio format information can only carry the second audio format information without carrying the first audio format information, and in S420, the second communication entity can send the fifth audio format information based on the second audio format information and the third audio format information. In other words, in a one-way communication scenario, according to the transmission direction of the audio data between the first communication entity and the second communication entity, it is only necessary to determine the fifth audio format information or the sixth audio format information.

[0182] Optionally, before the second communication entity sends the fifth audio format information and the sixth audio format information, the method further includes:

[0183] S430: The second communication entity determines fifth audio format information and sixth audio format information based on the first audio format information and the second audio format information and the third audio format information and the fourth audio format information.

[0184] For example, the second communication entity can determine the fifth audio format information and the sixth audio format information based on the first strategy, the first audio format information and the second audio format information, as well as the third audio format information and the fourth audio format information, wherein the first strategy is to search from high to low according to the complexity of the audio format types that can be used when the second communication entity performs IVAS encoding (i.e., the complexity of at least one third audio format type), or the first strategy is to search from high to low according to the complexity of the audio format types that can be used when the second communication entity performs IVAS decoding (i.e., the complexity of at least one fourth audio format type).

[0185] The following is an example of how to determine the fifth audio format information and the sixth audio format information based on the first strategy with reference to specific examples. For example, the first audio format information and the second audio format information corresponding to the first communication entity are shown in Table 1, and the third audio format information and the fourth audio format information corresponding to the second communication entity are shown in Table 4. Among them, combination 1, combination 2 and combination 3 in Table 1 can be regarded as the first audio format information and the second audio format information including 3 groups of audio format information, and each group of audio format information includes the corresponding first audio format information and the second audio information. Combination 1, combination 2 and combination 3 in Table 4 can be regarded as the third audio format information and the fourth audio format information including 3 groups of audio format information, and each group of audio format information includes the corresponding third audio format information and the sixth audio information.

[0186] Table 4

[0187]

[0188] Example 1: The first strategy is to search and determine the fifth audio format information and the sixth audio format information according to the complexity of the audio format types that can be used by the second communication entity when performing IVAS encoding from high to low. The implementation method includes the following steps.

[0189] ① It can be seen from Table 4 that the highest encoding audio format type supported by the second communication entity is FOA, and it can be seen from Table 1 that the decoding audio format type of the first communication entity also includes FOA, so it is temporarily determined that the encoding audio format type of the second communication entity and the decoding audio format type of the first communication entity are FOA.

[0190] Optionally, if there are coded FOAs in multiple combinations of Table 4, the coded FOA in the combination with the largest coded FOA rate is selected. For example, both combination 1 and combination 2 in Table 4 include coded FOAs, but the maximum rate of the coded FOA in combination 1 is 32, which is greater than the maximum rate of the coded FOA in combination 2, which is 24. Therefore, the coded FOA in combination 1 is selected in this example.

[0191] Optionally, if there are decoding FOAs in multiple combinations in Table 1, the decoding FOA in the combination with the largest decoding FOA rate is selected. In this example, only combination 3 in Table 1 includes decoding FOA, so the decoding FOA in combination 3 is selected.

[0192] ② Determine that the intersection of the rate {24, 32} of the encoding FOA supported by the second communication entity in combination 1 of Table 4 and the rate {24, 32, 48} of the decoding FOA supported by the first communication entity in combination 3 of Table 1 is {24, 32}.

[0193] It can be understood that the fifth audio format information obtained in this example indicates two fifth audio formats, and the parameters corresponding to the two fifth audio formats are {FOA, 24} and {FOA, 32} respectively.

[0194] It should be noted that since any combination in Table 1 and Table 4 is a fixed combination, it is still necessary to subsequently select the decoding audio format type supported by the second communication entity from combination 1 in Table 4 and the encoding audio format type supported by the first communication entity from combination 3 in Table 1.

[0195] ③ In combination 1 of Table 4, the decoding audio format type supported by the second communication entity is MONO, and in combination 3 of Table 1, the encoding audio format type supported by the first communication entity includes MONO, and it is determined that the decoding audio format type of the second communication entity and the encoding audio format type of the first communication entity are MONO.

[0196] ④ Determine that the intersection of the decoding MONO rate {5.9, 7.2, 9.6, 13.2} supported by the second communication entity in combination 1 of Table 4 and the encoding MONO rate {5.9, 7.2, 9.6} supported by the first communication entity in combination 3 of Table 1 is {5.9, 7.2, 9.6}.

[0197] It can be understood that the sixth audio format information obtained in this example indicates three sixth audio formats, and the parameters corresponding to the three sixth audio formats are {MONO, 5.9}, {MONO, 7.6}, and {MONO, 9.6}, respectively.

[0198] For example, if the coded audio format type in combination 3 of Table 1 in step ③ does not include MONO, it is considered that the sixth audio format information cannot be obtained based on the information in combination 1 of Table 4 and combination 3 of Table 1. Then, the second communication entity can continue to search Table 1 and Table 4 according to the first strategy until the suitable fifth audio format information and sixth audio format information are found.

[0199] Optionally, after the second communication entity searches all combinations in Table 1 and Table 4 according to the first strategy in this example and still cannot determine suitable fifth audio format information or sixth audio format information, the IVAS voice codec will not be used between the first communication entity and the second communication entity.

[0200] Example 2: The first strategy is to search from high to low according to the complexity of the audio format types that can be used when the second communication entity performs IVAS decoding. This implementation includes the following steps.

[0201] ① It can be seen from Table 4 that the highest decoding audio format type supported by the second communication entity is FOA, and it can be seen from Table 1 that the encoding audio format type of the first communication entity also includes FOA, so it is temporarily determined that the decoding audio format type of the second communication entity and the encoding audio format type of the first communication entity are FOA (i.e., an example of the sixth audio format type).

[0202] Optionally, if there are decoding FOAs in multiple combinations in Table 4, the decoding FOA in the combination with the largest decoding FOA rate is selected. In this example, only combination 3 in Table 4 includes decoding FOA, so the decoding FOA in combination 3 is selected.

[0203] Optionally, if there are coded FOAs in multiple combinations of Table 1, the coded FOA in the combination with the largest coded FOA rate is selected. For example, both combination 1 and combination 2 in Table 1 include coded FOAs, but the maximum rate of the coded FOA in combination 1 is 48, which is greater than the maximum rate of the coded FOA in combination 2, which is 24. Therefore, the coded FOA in combination 1 is selected in this example.

[0204] ② Determine that the intersection of the decoding FOA rate {24, 32, 48} supported by the second communication entity in combination 3 of Table 4 and the encoding FOA rate {24, 32, 48} supported by the first communication entity in combination 1 of Table 1 is {24, 32, 48} (i.e., an example of the second rate set).

[0205] It should be noted that since any combination in Table 1 and Table 4 is a fixed combination, it is still necessary to subsequently select the encoded audio format type supported by the second communication entity from combination 3 in Table 4 and the decoded audio format type supported by the first communication entity from combination 1 in Table 1.

[0206] ③ It can be seen from Table 4 that the encoded audio format types supported by the second communication entity in combination 3 of Table 4 include MONO and STEREO, but since the decoded audio format types supported by the first communication entity in combination 1 of Table 1 only include MONO, the encoded audio format type of the second communication entity and the decoded audio format type of the first communication entity are determined to be MONO (i.e., an example of the fifth audio format type).

[0207] ④ Determine that the intersection of the encoding MONO rate {5.9, 7.2, 9.6, 13.2} supported by the second communication entity in combination 3 of Table 4 and the decoding MONO rate {5.9, 7.2, 9.6} supported by the first communication entity in combination 1 of Table 1 is {5.9, 7.2, 9.6} (i.e., an example of the second rate set).

[0208] For example, if combination 1 of Table 1 in step ③ does not include the coded audio format type including MONO, it is considered that the fifth audio format type cannot be obtained based on the information in combination 3 of Table 4 and combination 1 of Table 1. Then, the second communication entity can continue to search in Table 1 and Table 4 according to the first strategy until suitable fifth audio format information and sixth audio format information are found.

[0209] Optionally, after the second communication entity searches all combinations in Table 1 and Table 4 according to the first strategy in this example and still cannot determine suitable fifth audio format information or sixth audio format information, the IVAS voice codec will not be used between the first communication entity and the second communication entity.

[0210] It should be understood that the above first strategy is only an exemplary embodiment of two specific implementation methods for determining the fifth audio format and the sixth audio format, and the present application does not limit the implementation method for determining the fifth audio format and the sixth audio format. For example, the second communication entity can determine multiple available groups of fifth audio formats and sixth audio formats based on Table 1 and Table 4, and select a suitable group of fifth audio formats and sixth audio formats from the multiple groups of fifth audio formats and sixth audio formats based on actual needs.

[0211] In the above technical scheme, a more fine-grained IVAS voice codec negotiation mechanism is provided. On the basis of the use of IVAS voice codec by the first communication entity and the second communication entity, the IVAS encoding audio format and IVAS decoding audio format used by the first communication entity and the second communication entity during audio communication are further negotiated, so that the first communication entity and the second communication entity can use appropriate IVAS encoding audio format and IVAS decoding audio format for audio communication according to the IVAS codec capabilities actually supported by the first communication entity and the second communication entity.

[0212] The method can also avoid power consumption and bandwidth waste by negotiating the IVAS codec audio format with finer granularity. Specifically explain the beneficial effect, at present, the audio format used for IVAS encoding and the audio format used for IVAS decoding of a terminal can be different, for example, the audio formats used for IVAS encoding and IVAS decoding of terminal #1 are audio format #1 and audio format #2, respectively, and the audio formats used for IVAS encoding and IVAS decoding of terminal #2 are audio format #3 and audio format #4, respectively. Then, in the process of audio data transmission between terminal #1 and terminal #2, terminal #1 and terminal #2 will perform encoding and decoding processing according to the audio format corresponding to the maximum IVAS encoding and decoding capability currently supported by themselves, for example, the maximum IVAS encoding capability of terminal #1 is greater than the maximum IVAS decoding capability of terminal #2, terminal #1 encodes the voice content to be sent based on the maximum IVAS encoding capability supported by itself to generate audio data #1 and send it to terminal #2, terminal #2 can only use its maximum IVAS decoding capability to decode audio data #1, due to the unequal encoding and decoding capabilities of terminal #1 and terminal #2, it will lead to the waste of encoding power consumption of terminal #1. In addition, the higher the IVAS encoding capability, the more bandwidth the generated audio data will occupy during transmission. Therefore, encoding according to the encoding capability of terminal #1 will also cause a waste of bandwidth. Taking the parameters corresponding to the audio format including the audio format type as an example to illustrate this technical problem, the maximum IVAS encoding capability supported by terminal #1 corresponds to audio format #1 and the audio format type in audio format #1 is FOA. The maximum IVAS decoding capability supported by terminal #2 corresponds to audio format #4 and the audio format type in audio format #4 is MONO. If terminal #1 and terminal #2 do not negotiate the audio format, then terminal #1 will currently encode and generate audio data #1 based on the FOA in audio format #4 corresponding to the maximum IVAS encoding capability it supports, and then send audio data #1 to terminal #2. After receiving the audio data #1, terminal #2 can only decode based on MONO in the audio format #4 corresponding to the maximum IVAS decoding capability supported by itself, that is, terminal #1 encodes based on high capability, while terminal #2 can only decode based on low capability, which wastes the encoding power consumption of terminal #1 and also causes bandwidth waste. By using the method proposed in the present application, by negotiating the audio formats of terminal #1 and terminal #2, for example, after negotiation, it is determined that terminal #1 and terminal #2 use FOA for encoding and decoding respectively, that is, terminal #1 and terminal #2 encode and decode based on the same capability, thereby avoiding waste of power consumption and bandwidth.

[0213] Figure 5 is a schematic diagram of a method 500 for audio parameter negotiation provided in an embodiment of the present application. The method 500 may include the following steps.

[0214] S510, the first communication entity sends first audio format information and second audio format information to the second communication entity. Correspondingly, the second communication entity receives the first audio format information and the second audio format information from the first communication entity, wherein the first audio format information indicates at least one first audio format, the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding.

[0215] S520, the second communication entity sends fifth audio format information and sixth audio format information to the first communication entity based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information. Correspondingly, the first communication entity receives the fifth audio format information and the sixth audio format information from the second communication entity.

[0216] Among them, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format is an audio format that the first communication entity will adopt when performing IVAS decoding and / or the second communication entity will adopt when performing IVAS encoding, and the sixth audio format is an audio format that the first communication entity will adopt when performing IVAS encoding and / or the second communication entity will adopt when performing IVAS decoding.

[0217] For the description of each information or each audio format in S510 and S520, please refer to the description in S410 and S420, which will not be repeated here.

[0218] It can be understood that the first audio format information and the second audio format information reflect the IVAS codec capability of the first communication entity, and the third audio format information and the fourth audio format information reflect the IVAS codec capability of the second communication entity.

[0219] Optionally, before the second communication entity sends the fifth audio format information and the sixth audio format information to the first communication entity, the method further includes:

[0220] S530: The second communication entity determines fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information. For S530, refer to the description in S430, which will not be repeated here.

[0221] It can be understood that after S520, the first communication entity and the second communication entity clarify the audio parameter negotiation result, and the first communication entity and the second communication entity can transmit audio data based on the audio parameter negotiation result (i.e., the fifth audio format information and the sixth audio format information). Therefore, the method also includes S540~S550 and / or S560~S570.

[0222] S540, the second communication entity sends first audio data to the first communication entity, where the first audio data is generated by IVAS encoding based on the fifth audio format information. Correspondingly, the first communication entity receives the first audio data from the second communication entity.

[0223] Specifically, the first audio data is generated by IVAS encoding by the second communication entity based on one of the at least one fifth audio formats indicated by the fifth audio format information. As to which audio format of the at least one fifth audio format indicated by the fifth audio format information is specifically used, refer to the description in S420, which will not be repeated here.

[0224] S550: The first communication entity performs IVAS decoding on the first audio data based on the fifth audio format information.

[0225] S560, the first communication entity sends second audio data to the second communication entity, where the second audio data is generated by IVAS encoding based on the sixth audio format information. Correspondingly, the second communication entity receives the second audio data from the first communication entity.

[0226] Specifically, the second audio data is generated by IVAS encoding by the first communication entity based on one of the at least one sixth audio formats indicated by the sixth audio format information. As to which audio format of the at least one sixth audio format indicated by the sixth audio format information is specifically used, refer to the description in S420, which will not be repeated here.

[0227] S570: The second communication entity performs IVAS decoding on the second audio data based on the sixth audio format information.

[0228] It can be understood that the embodiments of the present application do not limit the manner in which information is exchanged between the first communication entity and the second communication entity. For example, the second communication entity can send information directly to the first communication entity (such as the first audio format information and the second audio format information mentioned above), or it can send information to the first communication entity through other network elements or devices. This application does not limit this.

[0229] In the above technical solution, a more fine-grained codec negotiation mechanism is provided. On the basis of the first communication entity and the second communication entity using the IVAS voice codec, the IVAS encoding audio format and the IVAS decoding audio format are further negotiated, so that the first communication entity and the second communication entity can use appropriate encoding audio formats and decoding audio formats for audio communication based on the IVAS codec capabilities actually supported by the first communication entity and the second communication entity, thereby avoiding power consumption and bandwidth waste.

[0230] Combine the following Figure 6 and Figure 7 The method 500 is illustrated by taking a specific scenario in FIG.

[0231] Figure 6 It is a schematic diagram of a method 600 for audio parameter negotiation provided in an embodiment of the present application. It can be understood that method 600 is a possible implementation method applied to an IMS call scenario, wherein in method 600, in mode 1 of the initial voice call process and the negotiation process after the IVAS codec capability update, the second communication entity is the called UE and the first communication entity is the calling UE for example; in mode 2 of the initial voice call process of method 600, the second communication entity is the calling UE and the first communication entity is the called UE for example. Figure 6 The various steps in the method 600 are exemplarily described.

[0232] Mode 1 of initiating a voice call process: the calling device initiates the audio parameter negotiation process.

[0233] S601, the calling UE sends an invite request message to the IMS network device. Correspondingly, the IMS network device receives the invite request message from the calling UE.

[0234] S602: The IMS network device sends an invite request message to the called UE. Correspondingly, the called UE receives the invite request message from the IMS network device.

[0235] It can be understood that the calling UE sends an invite request message to the called UE through the IMS network device, and the invite request message is used to request to establish an audio call connection between the calling UE and the called UE.

[0236] It can be understood that the IMS network device here refers to one or more network elements within the IMS network, and the figure omits the information interaction process of the network elements within the IMS network.

[0237] Optionally, the invite request message includes capability information #1, wherein the capability information #1 includes audio format information #1 (i.e., an example of first audio format information) and audio format information #2 (i.e., an example of second audio format information), the audio format information #1 indicates an audio format that can be adopted by at least one calling UE when performing IVAS encoding, and the audio format information #2 indicates an audio format that can be adopted by at least one calling UE when performing IVAS decoding.

[0238] Optionally, the invite request message includes a session description protocol (SDP) offer#1, and the SDP offer#1 includes audio media information supported by the calling UE. For example, the capability information#1 may be carried in the SDP offer#1.

[0239] For example, several possible ways of carrying capability information #1 in SDP offer #1 are given below. To facilitate understanding of carrying capability information #1 in SDP offer #1, a specific example of capability information #1 is given here. For example, capability information #1 can be indicated by the tables shown in Table 5 and Table 3. For the specific determination method, refer to the description of Example 2 in S410, which will not be repeated here.

[0240] Table 5

[0241]

[0242]

[0243] Example 1:

[0244] m=audio 49152RTP / AVP 100 96

[0245] a=rtpmap:100IVAS / 8000

[0246] a=fmtp:100bit-rate-list={(mono,5.9|7.2|9.6),(stereo,13.2|24|32),(foa,24|32|48)};

[0247] dec-format-list={[mono / 9.6,stereo / 24]}; enc-format-list={[mono / 9.6,stereo / 32,foa / 48]}

[0248] The following is a description of the parameters in this method:

[0249] bit-rate-list={(mono,5.9|7.2|9.6),(stereo,13.2|24|32),(foa,24|32|48)}, indicating the rate information supported by mono, stereo and foa (i.e., the information indicated in Table 3).

[0250] (mono,5.9|7.2|9.6) means that the rates supported by mono are 5.9kpbs, 7.2kpbs and 9.6kpbs, that is, (mono,5.9|7.2|9.6) indicates three audio formats, and the audio format parameters corresponding to the three audio formats are {mono,5.9}, {mono,7.2}, and {mono,9.6} respectively.

[0251] It should be noted that the names of the audio format types in the embodiments of the present application are not case sensitive. For example, mono and MONO have the same meaning in the present application, and the related parts will not be repeated one by one in the following text.

[0252] For example, dec-format-list = [mono / 9.6,stereo / 24] indicates that two types of decoding audio formats, mono and stereo, are supported, and the maximum rates supported by mono and stereo are 9.6 kbps and 24 kbps respectively.

[0253] For example, enc-format-list = [mono / 9.6,stereo / 32,foa / 48], which means that three coded audio formats, mono, stereo, and foa, are supported, and the maximum rates supported by mono, stereo, and foa are 9.6 kbps, 32 kbps, and 48 kbps, respectively.

[0254] It should be understood that dec-format-list only contains one set of maximum rates corresponding to the decoded audio format type and the encoded audio format type, and multiple sets of maximum rates corresponding to the decoded audio format type and the encoded audio format type are separated by []. Similarly, enc-format-list only contains one set of maximum rates corresponding to the encoded audio format type and the encoded audio format type, and multiple sets of maximum rates corresponding to the encoded audio format type and the encoded audio format type are separated by []. The information in a [] in dec-format-list and a [] in the corresponding position in enc-format-list constitutes a set of codec audio format combinations (such as combination 1 in Table 5).

[0255] Example 2:

[0256] m=audio 49152RTP / AVP 100 96

[0257] a=rtpmap:100IVAS / 8000

[0258] a=fmtp:100bit-rate-list={(mono,5.9|7.2|9.6),(stereo,13.2|24|32),(foa,24|32|48)};

[0259] format-list={[(mono / 9.6,stereo / 24),(mono / 9.6,stereo / 32,foa / 48)]}

[0260] The following is a description of the parameters in this method:

[0261] The meaning of bit-rate-list is the same as that of method 1 and is not repeated here.

[0262] It can be understood that in this example, the relevant information of the corresponding codec audio format in a set of codec audio format combinations and the relevant information of the corresponding coded audio format are separated by (). For example, format-list = {[(mono / 9.6,stereo / 24), (mono / 9.6,stereo / 32,foa / 48)]} indicates that two decoding audio format types, mono and stereo, are supported, and the maximum rates supported by mono and stereo are 9.6kbps and 24kbps respectively, and three coded audio format types, mono, stereo and foa, are supported, and the maximum rates supported by mono, stereo and foa are 9.6kbps, 32kbps and 48kbps respectively.

[0263] It should be understood that the format-list example only includes relevant information of one set of codec audio format combinations. For example, if multiple sets of relevant information of codec audio format combinations are included, the multiple sets of relevant information of codec audio format combinations are separated by [].

[0264] Example 3:

[0265] m=audio 49152RTP / AVP 100 96

[0266] a=rtpmap:100IVAS / 8000

[0267] a=fmtp:100dec-format-list={[mono / (5.9,7.2,9.6),stereo / (13.2,24)]};

[0268] enc-format-list={[mono / (5.9,7.2,9.6),stereo / (13.2,24,32),foa / (24,32,48)]}

[0269] The following is a description of the parameters in this method:

[0270] dec-format-list indicates the decoding audio formats supported by the calling UE. For example, dec-format-list = {[mono / (5.9,7.2,9.6),stereo / (13.2,24)]}, which means that both mono and stereo decoding audio formats are supported, and the rates supported by mono are 5.9kpbs, 7.2kpbs, and 9.6kpbs, and the rates supported by stereo are 13.2kpbs and 24kpbs.

[0271] enc-format-list indicates the coded audio formats supported by the calling UE. For example, enc-format-list = {[mono / (5.9,7.2,9.6),stereo / (13.2,24,32),foa / (24,32,48)]}, which means that the three coded audio formats of mono, stereo and foa are supported, and the rates supported by mono are 5.9kpbs, 7.2kpbs, 9.6kpbs, the rates supported by stereo are 13.2kpbs, 24kpbs and 32kpbs, and the rates supported by foa are 24kpbs, 32kpbs and 48kpbs.

[0272] It should be understood that dec-format-list contains only one set of decoded audio formats, and multiple sets of decoded audio formats are separated by []. Similarly, enc-format-list contains only one set of encoded audio formats, and multiple sets of encoded audio formats are separated by []. The information in a [] in dec-format-list and a [] in the corresponding position in enc-format-list constitutes a set of codec audio format combinations (such as combination 1 in Table 5).

[0273] Example 4:

[0274] m=audio 49152RTP / AVP 100 96

[0275] a=rtpmap:100IVAS / 8000

[0276] a=fmtp:100format-list={[(mono / (5.9,7.2,9.6),stereo / (13.2,24)),

[0277] (mono / (5.9,7.2,9.6),stereo / (13.2,24,32),foa / (24,32,48))]}

[0278] It can be understood that in this example, the decoded audio format and the encoded audio format in a set of codec audio format combinations are separated by (). format-list = {[(mono / 9.6,stereo / 24), (mono / 9.6,stereo / 32,foa / 48)]} indicates that two decoded audio format types, mono and stereo, are supported, and the maximum rates supported by mono and stereo are 9.6 kbps and 24 kbps respectively, and three encoded audio format types, mono, stereo and foa, are supported, and the maximum rates supported by mono, stereo and foa are 9.6 kbps, 32 kbps and 48 kbps respectively.

[0279] It should be understood that the format-list example only contains one set of codec audio format combinations. For example, if multiple sets of codec audio format combinations are supported, multiple combinations are separated by [].

[0280] S603: The called UE determines audio format information #3 and audio format information #4 based on capability information #1 and capability information #2.

[0281] It should be understood that capability information #2 includes audio format information #5 (i.e., an example of the third audio format information) and audio format information #6 (i.e., an example of the fourth audio format information), wherein audio format information #5 indicates an audio format that can be adopted by at least one called UE when performing IVAS encoding, and audio format information #6 indicates an audio format that can be adopted by at least one called UE when performing IVAS decoding.

[0282] It should also be understood that audio format information #3 (i.e., an example of the fifth audio format information) indicates the audio format to be adopted by the called UE when performing IVAS encoding and / or the calling UE when performing IVAS decoding, and audio format information #4 (i.e., an example of the sixth audio format information) indicates the audio format to be adopted by the called UE when performing IVAS decoding and / or the calling UE when performing IVAS encoding.

[0283] Exemplarily, after receiving the invite request message from the calling UE, the called UE obtains capability information #1 from the invite request message, and then determines audio format information #3 and audio format information #4 based on capability information #1 and capability information #2.

[0284] S604, the called UE sends an 18X / 200 response message to the IMS network device. Correspondingly, the IMS network device receives the 18X / 200 response message from the called UE.

[0285] It should be noted that the 18X response message in the present application is a 180 response message or a 183 response message. Whether it is a 180 response message or a 183 response message can be determined based on the interacting network element, and the relevant parts will not be repeated in the following text.

[0286] S605, the IMS network device sends an 18X / 200 response message to the calling UE. Correspondingly, the calling UE receives the 18X / 200 response message from the IMS network device.

[0287] Optionally, the 18X / 200 response message includes indication information #1, and the indication information #1 includes audio format information #3 and audio format information #4.

[0288] Optionally, the 18X / 200 response message carries SDP answer#1, and the SDP answer#1 includes audio media information supported by the called UE. For example, the indication information #1 may be carried in SDP answer#1 of the 18X / 200 response message.

[0289] As an example, two possible ways of carrying indication information #1 in SDP answer #1 are given below. To facilitate understanding of the indication information #1 carried in SDP answer #1, a specific example of indication information #1 is given here. Indication information #1 includes audio format information #3 and audio format information #4, where audio format information #3 indicates two audio formats, and the parameters corresponding to the two audio formats are {STEREO, 24} and {STEREO, 32}, respectively. Audio format information #4 indicates two audio formats, and the parameters corresponding to the two audio formats are {FOA, 24} and {FOA, 32}, respectively.

[0290] Method 1: Audio format information #3 and audio format information #4 are carried using different parameters

[0291] m=audio 49154RTP / AVP 100 96

[0292] a=rtpmap:101IVAS / 8000

[0293] a=fmtp:101enc-format=(foa,24|32); dec-format=(stereo,13.2|24)

[0294] The following is a description of the parameters in this method:

[0295] enc-format=(foa,24|32) indicates that the encoding signal type of the receiver is foa, and the rate set corresponding to foa is 24kbps and 32kbps.

[0296] dec-format=(stereo,13.2|24) indicates that the decoded signal type of the receiver is stereo, and the rate set corresponding to stereo is 13.2 kbps and 24 kbps.

[0297] Method 2: Audio format information #3 and audio format information #4 are carried using the same parameters

[0298] m=audio 49154RTP / AVP 100 96

[0299] a=rtpmap:101IVAS / 8000

[0300] a=fmtp:101format-result={(foa,24|32),(stereo,13.2|24)}

[0301] The following is a description of the parameters in this method:

[0302] format-result={(foa,24|32),(stereo,13.2|24)} indicates that the encoding signal type of the receiver is foa, and the rate set corresponding to foa is 24 kbps and 32 kbps, and that the decoding signal type of the receiver is stereo, and the rate set corresponding to stereo is 13.2 kbps and 24 kbps.

[0303] S606: The called party picks up the phone, and the calling UE and the called UE enter into an audio call, and the audio call is performed according to the instruction information #1.

[0304] For a detailed description of this step, please refer to the description in S540 to S550 and / or S560 to S570, which will not be repeated here.

[0305] Mode 2 of initiating a voice call process: the negotiation process is triggered by the called device (i.e., the called UE)

[0306] S607, the calling UE sends an invite request message to the IMS network device. Correspondingly, the IMS network device receives the invite request message from the calling UE.

[0307] S608, the IMS network device sends an invite request message to the called UE. Correspondingly, the called UE receives the invite request message from the IMS network device.

[0308] Exemplarily, the calling UE sends an invite request message to the called UE through the IMS network to initiate an audio call to the called UE. In addition, the calling UE does not carry capability information #1 in the invite request message.

[0309] S609, the called UE sends an 18X / 200 response message to the IMS network device. Correspondingly, the IMS network device receives the 18X / 200 response message from the called UE.

[0310] S610, the IMS network device sends an 18X / 200 response message to the calling UE. Correspondingly, the calling UE receives the 18X / 200 response message from the IMS network device.

[0311] After ringing or after picking up the phone, the called UE sends an 18X / 200 response message to the calling UE through the IMS network device, and carries capability information #2 in the 18X / 200 response message. For the description of capability information #2, refer to the description in method 1, which will not be repeated here.

[0312] Optionally, the called UE carries SDP offer#2 in the 18X / 200 response message, and the SDP offer#2 includes audio media information supported by the called UE. For example, capability information#2 may be carried in SDP offer#2.

[0313] S611, the calling UE determines audio format information #3 and audio format information #4 based on capability information #1 and capability information #2.

[0314] Exemplarily, after receiving the 18X / 200 response message from the called UE, the calling UE obtains capability information #2 from the 18X / 200 response message, and then determines audio format information #3 and audio format information #4 based on capability information #2 and capability information #1. For the capability information #2, audio format information #3 and audio format information #4, refer to the description in the first method, which will not be repeated here.

[0315] S612: The calling UE sends a PRACK / ACK message to the IMS network device. Correspondingly, the IMS network device receives the PRACK / ACK message from the calling UE.

[0316] S613, the IMS network device sends a PRACK / ACK message to the called UE. Correspondingly, the called UE receives the PRACK / ACK message from the IMS network device.

[0317] Exemplarily, after completing S611, the calling UE sends a PRACK / ACK message to the called UE through the IMS network device, and the PRACK / ACK message includes indication information #2, and the indication information #2 indicates audio format information #3 and audio format information #4. Exemplarily, the indication information #2 can be carried in SDP answer #2 of the PRACK / ACK message.

[0318] S614, the calling UE and the called UE enter into an audio call, and conduct the audio call according to the instruction information #2.

[0319] For a detailed description of this step, please refer to the description in S540 to S550 and / or S560 to S570, which will not be repeated here.

[0320] Optionally, if the IVAS codec capability of the calling UE or the called UE changes (for example, when the battery is low, the codec of certain high-complexity audio format types may be restricted), resulting in the last audio parameter negotiation result being no longer applicable to the current audio data transmission, the negotiation process needs to be re-executed, including S615 to S620.

[0321] S615, the calling UE sends a re-invite request message to the IMS network device. Correspondingly, the IMS network device receives the re-invite request message from the calling UE.

[0322] S616: The IMS network device sends a re-invite request message to the called UE. Correspondingly, the called UE receives the re-invite request message from the IMS network device.

[0323] Exemplarily, the calling UE sends a re-invite request message to the called UE through the IMS network device, and carries capability information #3 in the re-invite request message, wherein the capability information #3 includes audio format information #7 (i.e., an example of the first audio format information) and audio format information #8 (i.e., an example of the second audio format information), the audio format information #7 indicates the audio format that can be adopted by at least one calling UE when performing IVAS encoding, and the audio format information #8 indicates the audio format that can be adopted by at least one calling UE when performing IVAS decoding.

[0324] S617: The called UE determines audio format information #9 and audio format information #10 based on capability information #3 and capability information #4.

[0325] It should be understood that capability information #4 includes audio format information #11 (i.e., an example of the third audio format information) and audio format information #12 (i.e., an example of the fourth audio format information), wherein audio format information #1 indicates an audio format that can be adopted by at least one called UE when performing IVAS encoding, and audio format information #2 indicates an audio format that can be adopted by at least one called UE when performing IVAS decoding.

[0326] It should also be understood that audio format information #9 (i.e., an example of the fifth audio format information) indicates the audio format to be adopted by the called UE when performing IVAS encoding and / or the calling UE when performing IVAS decoding, and audio format information #10 (i.e., an example of the sixth audio format information) indicates the audio format to be adopted by the called UE when performing IVAS decoding and / or the calling UE when performing IVAS encoding.

[0327] Exemplarily, after receiving the invite request message from the calling UE, the called UE obtains capability information #3 from the invite request message, and then determines audio format information #9 and audio format information #10 based on capability information #3 and capability information #4.

[0328] S618: The called UE sends a 200 response message to the IMS network device. Correspondingly, the IMS network device receives the 200 response message from the called UE.

[0329] S619, the IMS network device sends a 200 response message to the calling UE. Correspondingly, the calling UE receives the 200 response message from the IMS network device.

[0330] Exemplarily, the called UE sends a 200 response message to the calling UE through the IMS network device, and the 200 response message carries indication information #3, where the indication information #3 indicates audio format information #9 and audio format information 10.

[0331] S620: The calling UE and the called UE conduct an audio call according to the instruction information #3.

[0332] For a detailed description of this step, please refer to the description in S540 to S550 and / or S560 to S570, which will not be repeated here.

[0333] In the above technical solution, a more fine-grained codec negotiation mechanism is provided. On the basis of the negotiation between the calling UE and the called UE to use the IVAS voice codec, the IVAS encoding audio format and the IVAS decoding audio format are further negotiated. According to the IVAS codec capabilities actually supported by both parties of the audio communication, appropriate encoding audio formats and decoding audio formats are used for audio communication, thereby avoiding power consumption and bandwidth waste.

[0334] Figure 7 It is a schematic diagram of a method 700 for audio parameter negotiation provided in an embodiment of the present application. It can be understood that method 700 is another possible implementation of method 500 applied to an IMS call scenario, in which the second communication entity is an MRF and the first communication entity is a calling UE as an example. In this scenario, when the calling UE initiates a voice call, the IMS triggers the playback service and requests the MRF to use IVAS codec to play the voice to the calling UE. Figure 7 The various steps in the method 700 are exemplarily described.

[0335] S701, the calling UE sends an invite request message to the IMS Core. Correspondingly, the IMS Core receives the invite request message from the calling UE.

[0336] S702, the IMS Core sends an invite request message to the AS. Correspondingly, the AS receives the invite request message from the IMS Core.

[0337] S703, the AS sends an invite request message to the MRF. Correspondingly, the MRF receives the invite request message from the AS.

[0338] Optionally, the invite request message includes capability information #1, wherein the capability information #1 includes audio format information #1, and the audio format information #1 indicates an audio format that the calling UE can adopt when performing IVAS decoding.

[0339] Optionally, the invite request message includes SDP offer#1, and the SDP offer#1 includes audio media information supported by the calling UE. For example, the capability information#1 may be carried in a session description protocol (SDP) offer#1 of a response message to the invite request message.

[0340] S704, MRF determines audio format information #3 based on capability information #1 and capability information #2.

[0341] The capability information #2 indicates the audio format that the MRF can use when performing IVAS encoding. The audio format information #3 indicates the audio format that the MRF will use when performing IVAS encoding and / or the calling UE will use when performing IVAS decoding.

[0342] It should be understood that when the MRF plays audio data, the transmission is a one-way code stream (sent from the MRF to the calling UE), so the MRF only needs to determine the audio format information #3.

[0343] S705, the MRF sends a 200 response message to the AS. Correspondingly, the AS receives the 200 response message from the MRF.

[0344] Optionally, the 200 response message includes indication information #1, and the indication information #1 includes audio format information #3.

[0345] S706, the AS sends an 18X response message to the IMS Core. Correspondingly, the IMS Core receives the 18X response message from the AS.

[0346] S707, the IMS Core sends an 18X response message to the calling UE. Correspondingly, the calling UE receives the 18X response message from the IMS Core.

[0347] Optionally, the 18X response message includes the indication information #1. For example, the indication information #1 may be carried in SDP answer #1 of the 18X response message.

[0348] S708: The calling UE sends a PRACK / ACK message to the IMS Core. Correspondingly, the IMS Core receives the PRACK / ACK message from the calling UE.

[0349] S709, the IMS Core sends a PRACK / ACK message to the AS. Correspondingly, the AS receives the PRACK / ACK message from the IMS Core.

[0350] S710, the AS sends an INFO message to the MRF. Correspondingly, the MRF receives the INFO indication from the AS.

[0351] The INFO message instructs the MRF to play the voice message for the calling UE.

[0352] It can be understood that S708 to S711 are signaling interactions between the calling UE and the IMS network device for playing audio.

[0353] S711, the called UE sends a 200 response message to the AS. Correspondingly, the AS receives the 18X response message from the AS.

[0354] The 200 response message is used to instruct the MRF to use IVAS codec to play the voice for the calling UE.

[0355] S712, the MRF sends audio data #1 to the calling UE. Correspondingly, the calling UE receives the audio data #1 from the MRF.

[0356] The audio data #1 is audio data generated by encoding the content that the MRF needs to play to the calling UE based on the audio format information #3.

[0357] It should be understood that method 700 is based on the scenario of MRF playing a message to the calling UE. Figure 5 The method shown is described in detail, wherein the second communication entity is an MRF and the first communication entity is a calling UE. Based on the scenario in which the MRF plays audio for the calling UE, in another possible implementation, the second communication entity may be the calling UE and the first communication entity may be the MRF. For example, the MRF may send the IVAS coded audio format supported by itself to the AS through a 200 response message, and the AS may send the IVAS coded audio format supported by the MRF to the IMS Core through an 18X response message. The IMS Core may send the IVAS coded audio format supported by the MRF to the calling UE through an 18X response message. The calling UE determines the audio format information #3 based on the IVAS decoded audio format supported by itself and the IVAS coded audio format supported by the MRF, and then sends the indication information #2 to the MRF through a PRACK / ACK message. The indication information #2 includes the audio format information #3. When the AS triggers the MRF to play audio for the calling UE, the MRF plays audio for the calling UE based on the coded audio format information #3. The specific process will not be repeated here.

[0358] In another possible scenario, in which the MRF plays audio for the called UE, the second communication entity may be the MRF, and the first communication entity may be the called UE. For example, the called UE may send the IVAS decoding audio format supported by itself to the MRF via an 18X / 200 response message. The MRF determines the audio format information #4 based on the IVAS encoding audio format supported by itself and the IVAS decoding audio format supported by the called UE. The audio format information #4 is the audio format that the MRF will use when performing IVAS encoding and / or the called UE will use when performing IVAS decoding. Afterwards, the MRF sends the audio format information #4 to the called UE via a PRACK / ACK message. When the AS triggers the MRF to play audio for the called UE, the MRF encodes the content that the MRF needs to play to the called UE based on the audio format information #4, generates audio data #2, and sends the audio data #2 to the called UE. Based on the scenario where the MRF plays audio for the called UE, in another possible implementation, the second communication entity may be the called UE, and the first communication entity may be the MRF. For example, the MRF may send the IVAS encoded audio format supported by itself to the called UE through an invite request message, and the called UE determines the audio format information #4 based on the IVAS decoded audio format supported by itself and the IVAS encoded audio format supported by the MRF. After that, the called UE may send the audio format information #4 to the AS through an 18X / 200 response message, and the AS sends the audio format information #4 to the MRF through an ACK message. When the AS triggers the MRF to play audio for the called UE, the MRF encodes the content that the MRF needs to play to the called UE based on the audio format information #4, generates audio data #2, and sends the audio data #2 to the called UE. The specific process will not be repeated here.

[0359] In the above technical solution, when AS triggers MRF to play audio for the calling UE / called UE, MRF can encode the playback content in the IVAS audio format supported by both parties determined by negotiation based on the IVAS codec capabilities actually supported by MRF and UE (calling UE or called UE), thereby avoiding power consumption and bandwidth waste.

[0360] Understandably, Figures 5 to 7 The second communication entity determines the audio parameters (i.e., the fifth audio format information and the sixth audio format information) used by the second communication entity for audio data transmission with the first communication entity based on the third audio format information and the fourth audio format information of the second communication entity and the first audio format information and the second audio format information of the first communication entity. In a possible implementation, the third communication entity may also send the first audio format information and the second audio format information of the first communication entity to the second communication entity, so that the second communication entity determines the audio parameters used by the first communication entity and the second communication entity for audio calls. Figure 8This method is introduced.

[0361] Figure 8 FIG. 8 is a schematic diagram of a method 800 for negotiating audio parameters provided in an embodiment of the present application. The method 800 may include the following steps.

[0362] S810, the third communication entity sends first audio format information and second audio format information to the second communication entity. Correspondingly, the second communication entity receives the first audio format information and the second audio format information from the third communication entity, wherein the first audio format information indicates at least one first audio format, the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding.

[0363] For details about the first audio format information and the second audio format information, please refer to the description in S410, which will not be repeated here.

[0364] S820, the second communication entity sends fifth audio format information and sixth audio format information to the third communication entity based on the first audio format information, the second audio format information, the third audio format information, and the fourth audio format information. Correspondingly, the third communication entity receives the fifth audio format information and the sixth audio format information from the second communication entity.

[0365] Among them, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format is an audio format that the first communication entity will adopt when performing IVAS decoding and / or the second communication entity will adopt when performing IVAS encoding, and the sixth audio format is an audio format that the first communication entity will adopt when performing IVAS encoding and / or the second communication entity will adopt when performing IVAS decoding.

[0366] For the description of each information or each audio format in S810 and S820, please refer to the description in S410 and S420, which will not be repeated here.

[0367] It can be understood that the first audio format information and the second audio format information reflect the IVAS codec capability of the first communication entity, and the third audio format information and the fourth audio format information reflect the IVAS codec capability of the second communication entity.

[0368] Optionally, before the second communication entity sends the fifth audio format information and the sixth audio format information to the third communication entity, the method further includes:

[0369] S830: The second communication entity determines fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information, and the fourth audio format information.

[0370] For S830, please refer to the description in S430, which will not be repeated here.

[0371] S840: The third communication entity sends fifth audio format information and sixth audio format information to the first communication entity. Correspondingly, the first communication entity receives the fifth audio format information and sixth audio format information from the third communication entity.

[0372] S850: The second communication entity and the first communication entity perform audio data transmission based on the fifth audio format information and the sixth audio format information.

[0373] For example, in S850, the first communication entity performs audio data transmission with the second communication entity based on the fifth audio format information and the sixth audio format information, which may specifically include S860 to S870 and / or S880 to S890.

[0374] For S860 to S870, please refer to the description in S540 to S550; for S880 to S890, please refer to the description in S560 to S570, which will not be repeated here.

[0375] In the above technical solution, a more fine-grained codec negotiation mechanism is provided. On the basis of the second communication entity and the first communication entity using the IVAS voice codec, the second communication entity and the third communication entity further negotiate the IVAS encoding audio format and the IVAS decoding audio format to be used by the second communication entity and the first communication entity for audio communication, so that the second communication entity and the first communication entity can use appropriate encoding audio formats and decoding audio formats for audio communication based on the actual IVAS codec capabilities of the second communication entity and the first communication entity, thereby avoiding power consumption and bandwidth waste.

[0376] Combine the following Fig. 9 The method 800 is illustrated by using a specific scenario in FIG.

[0377] Fig. 9It is a schematic diagram of a method 900 for audio parameter negotiation provided in an embodiment of the present application. It can be understood that method 900 is a possible implementation method of method 800 applied to an IMS call scenario, in which the second communication entity is the called UE, the third communication entity is the P-CSCF, and the first communication entity is the IMS-AGW as an example for explanation. In this scenario, the calling UE does not support IVAS codec, and the calling UE initiates an audio call with non-IVAS codec. The IMS-AGW, as a codec conversion gateway, adds the IVAS codec function and completes the negotiation of the IVAS codec audio format with the called UE. The following is combined with Figure 8 The various steps in the method 800 are exemplified. For the convenience of description, the interaction between the S-CSCF and the AS is omitted in the process, and only the main steps related to the method proposed in this application are described.

[0378] S901, the calling UE sends an invite request message to the P-CSCF. Correspondingly, the P-CSCF receives the invite request message from the calling UE.

[0379] S902, the P-CSCF determines that the IMS-AGW as a codec conversion gateway needs to add IVAS codec, and the P-CSCF and the IMS-AGW apply to the IMS-AGW to add IVAS codec. Correspondingly, the IMS-AGW adds IVAS codec.

[0380] S903, the P-CSCF sends an invite request message to the I / S-CSCF. Correspondingly, the I / S-CSCF receives the invite request message from the P-CSCF.

[0381] S904, the I / S-CSCF sends an invite request message to the called UE. Correspondingly, the called UE receives the invite request message from the I / S-CSCF.

[0382] It can be understood that the calling UE sends an invite request message to the called UE through a network element in the IMS network device, and the invite request message is used to request to establish an audio call connection between the calling UE and the called UE.

[0383] Optionally, the invite request message in S901 to S903 includes SDP offer#1, and the SDP offer#1 includes audio media information supported by the calling UE.

[0384] Optionally, the invite request message in S902 and S903 includes capability information #1, wherein capability information #1 includes audio format information #1 and audio format information #2, audio format information #1 indicates an audio format that can be used by at least one IMS-AGW when performing IVAS encoding, and audio format information #2 indicates an audio format that can be used by at least one IMS-AGW when performing IVAS decoding. For example, the capability information #1 can be carried in SDP offer #1.

[0385] For example, the P-CSCF may determine the IVAS encoding audio format and the IVAS decoding audio format supported by the IMS-AGW based on the configuration information of the IMS-AGW.

[0386] S905: The called UE determines audio format information #3 and audio format information #4 based on capability information #1 and capability information #2.

[0387] It should be understood that capability information #2 includes audio format information #5 and audio format information #6, audio format information #5 indicates the audio format that the called UE can adopt when performing IVAS encoding, and audio format information #6 indicates the audio format that the called UE can adopt when performing IVAS decoding.

[0388] It should also be understood that audio format information #3 is the audio format that the called UE will adopt when performing IVAS encoding and / or the IMS-AGW will adopt when performing IVAS decoding, and audio format information #4 indicates the audio format that the called UE will adopt when performing IVAS decoding and / or the IMS-AGW will adopt when performing IVAS encoding.

[0389] Exemplarily, after receiving the invite request message from the I / S-CSCF, the called UE obtains capability information #1 from the invite request message, and then determines audio format information #3 and audio format information #4 based on capability information #1 and capability information #2.

[0390] S906: The called UE sends an 18X / 200 response message to the I / S-CSCF. Correspondingly, the I / S-CSCF receives the 18X / 200 response message from the called UE.

[0391] S907, the I / S-CSCF sends an 18X / 200 response message to the P-CSCF. Correspondingly, the P-CSCF receives the 18X / 200 response message from the I / S-CSCF.

[0392] Optionally, the 18X / 200 response message includes indication information #1, where the indication information #1 indicates audio format information #3 and audio format information #4.

[0393] Optionally, the 18X / 200 response message carries SDP answer#1, and the SDP answer#1 includes audio media information supported by the called UE. For example, the indication information #1 may be carried in the SDP answer#1 of the 18X / 200 response message.

[0394] S908, the P-CSCF sends message #1 to the IMS-AGW. Correspondingly, the IMS-AGW receives message #1 from the P-CSCF, wherein message #1 includes indication information #1.

[0395] S909, the P-CSCF sends an 18X / 200 response message to the calling UE.

[0396] S910, the called party picks up the phone, and the calling UE and the called UE enter into an audio call.

[0397] S911, the called UE sends audio data #1 to the IMS-AGW. Correspondingly, the IMS-AGW receives the audio data #1 from the called UE.

[0398] It should be understood that the audio data #1 is generated by performing IVAS encoding on the voice content that the called UE needs to send to the called UE based on the audio format information #3.

[0399] S912, the IMS-AGW decodes the audio data #1 based on the audio format information #3 and converts the audio data #2.

[0400] Specifically, the IMS-AGW decodes the audio data #1 based on the audio format information #3, and encodes the decoded audio content based on the voice codec type applicable between the IMS-AGW and the calling UE to generate audio data #2.

[0401] S913, the IMS-AGW sends audio data #2 to the calling UE. Correspondingly, the calling UE receives audio data #2 from the IMS-AGW.

[0402] S914: The calling UE sends audio data #3 to the IMS-AGW. Correspondingly, the IMS-AGW receives audio data #3 from the calling UE.

[0403] It should be understood that the audio data #3 is the voice content that the calling UE needs to send to the called UE.

[0404] S915, the IMS-AGW decodes the audio data #3 and converts it into audio data #4 based on the audio format information #4.

[0405] Specifically, the IMS-AGW decodes the audio data #3 based on the voice codec type applicable between the IMS-AGW and the calling UE, and further encodes the decoded audio content based on the audio format information #4 to generate audio data #4.

[0406] S916, the IMS-AGW sends audio data #4 to the called UE. Correspondingly, the called UE receives audio data #4 from the IMS-AGW.

[0407] S917: The called UE decodes the audio data #4 based on the audio format information #4.

[0408] In the above technical solution, on the basis of the IVAS voice codec used by the called UE and the IMS-AGW, the IVAS encoding audio format and the IVAS decoding audio format are further negotiated, so that the called UE and the IMS-AGW can use appropriate encoding audio format and decoding audio format for audio communication according to the IVAS codec capabilities actually supported by the called UE and the IMS-AGW, thereby avoiding power consumption and bandwidth waste.

[0409] Optionally, the present application also provides a method for negotiating audio parameters. Figure 8In the architecture diagram shown, the first communication entity sends first audio format information and second audio format information to the third communication entity, and correspondingly, the third communication entity receives the first audio format information and second audio format information from the first communication entity, wherein the first audio format information indicates at least one first audio format, the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; the third communication entity sends a fifth audio format to the first communication entity and the second communication entity based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information. Information and sixth audio format information, wherein the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that the second communication entity can adopt when performing IVAS encoding, the fourth audio format is an audio format that the second communication entity can adopt when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format that the first communication entity will adopt when performing IVAS decoding and / or the second communication entity will adopt when performing IVAS encoding, and the sixth audio format is an audio format that the first communication entity will adopt when performing IVAS encoding and / or the second communication entity will adopt when performing IVAS decoding. Afterwards, the first communication entity and the second communication entity can conduct an audio call based on the fifth audio format information and the sixth audio format information.

[0410] For example, based on this method, in a scenario where the called UE does not support IVAS codec, the calling UE can initiate an audio call with IVAS codec, and the IMS-AGW adds the IVAS codec function as a codec conversion gateway, and the P-CSCF completes the negotiation of the IVAS codec audio format with the calling UE. For example, the calling UE can send the IVAS codec audio format it supports to the P-CSCF through an invite request message, and the P-CSCF sends the IVAS codec audio format supported by the calling UE to the I / S-CSCF through an invite request message. The I / S-CSCF sends the IVAS codec audio format supported by the calling UE to the called UE through an invite request message. Since the called UE does not support IVAS codec, the called UE sends an 18X / 200 response message to the I / S-CSCF. Since the called UE does not negotiate the IVAS codec audio format, the 18X / 200 response message does not contain the negotiation result of the IVAS codec audio format. After that, the I / S- CSCF sends an 18X / 200 response message to P-CSCF. P-CSCF determines that IMS-AGW needs to add IVAS codec as a codec conversion gateway. P-CSCF applies to IMS-AGW to add IVAS codec, and determines audio format information #3 and audio format information #4 based on the IVAS codec audio format supported by the calling UE and the IVAS codec audio format supported by IMS-AGW, wherein audio format information #3 indicates the audio format that the calling UE will use when performing IVAS encoding and / or IMS-AGW will use when performing IVAS decoding, and audio format information #4 indicates the audio format that the calling UE will use when performing IVAS decoding and / or IMS-AGW will use when performing IVAS encoding. Afterwards, P-CSCF can send audio format information #3 and audio format information #4 to IMS-AGW and calling UE. Afterwards, when the calling UE and the called UE enter an audio call, IMS-AGW performs audio data conversion between the calling UE and the called based on audio format information #3 and audio format information #4. The specific process will not be described here.

[0411] It is understood that the steps in the above figures are only exemplary and not strictly limited. In addition, the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0412] It can also be understood that some message names are involved in the various embodiments of the present application, and their naming does not limit the protection scope of the embodiments of the present application.

[0413] It can also be understood that some optional features in the embodiments of the present application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0414] It can also be understood that in the above-mentioned various method embodiments, the methods and operations implemented by the device can also be implemented by components that can be implemented by the device (such as chips or circuits), without limitation.

[0415] Corresponding to the methods given in the above-mentioned method embodiments, the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments.

[0416] Fig.10 1 is a schematic diagram of a communication device 1100 provided in an embodiment of the present application. The device 1100 includes a communication unit 1110 and a processing unit 1120. The communication unit 1110 can be used to implement corresponding communication functions. The communication unit 1110 can also be called a communication interface or a communication unit. The processing unit 1120 can be used to perform processing operations.

[0417] Optionally, the device 1100 also includes a storage unit, which can be used to store instructions and / or data, and the processing unit 1120 can read the instructions and / or data in the storage unit so that the device implements the actions of the first terminal or media network element in the aforementioned method embodiments.

[0418] In a first design, the apparatus 1100 may be the second communication entity (eg, Figures 4 to 9 The second communication entity in the method embodiment) may also be a component of the second communication entity (such as a chip). The device 1100 may implement the steps or processes performed by the second communication entity in the above method embodiment. Among them, the communication unit 1110 may be used to perform the operations related to the transmission and reception of the second communication entity in the above method embodiment (such as the operations of sending and / or receiving data or messages). For example, the communication unit 1110 may be used to perform Figure 4 The processing unit 1120 may be used to perform operations related to data and / or information processing of the second communication entity in the above method embodiment, or operations other than sending and receiving (such as operations other than sending and / or receiving data or messages).

[0419] In a possible implementation, the communication unit 1110 receives first audio format information and second audio format information, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format, the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; the communication unit 1110 is also used to send fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information, and the fourth audio format information, wherein the third audio format information indicates to at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0420] Optionally, the communication unit 1110 is specifically used to receive first audio format information and second audio format information from the first communication entity; the communication unit 1110 is specifically used to send fifth audio format information and sixth audio format information to the first communication entity.

[0421] Optionally, the communication unit 1110 is specifically used to receive first audio format information and second audio format information from a third communication entity; the communication unit 1110 is specifically used to send fifth audio format information and sixth audio format information to the third communication entity.

[0422] Optionally, the communication unit 1110 is further configured to send first audio data to the first communication entity, where the first audio data is generated by performing IVAS encoding based on the fifth audio format information.

[0423] Optionally, the communication unit 1110 is further configured to receive second audio data from the first communication entity; and the processing unit 1120 is configured to perform IVAS decoding on the second audio data based on the sixth audio format information.

[0424] Optionally, the processing unit 1120 is further configured to determine fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information.

[0425] Optionally, the processing unit 1120 is specifically used to determine the fifth audio format information and the sixth audio format information based on the first strategy, the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, wherein the first strategy is to search from high to low according to the complexity of at least one third audio format type, or the first strategy is to search from high to low according to the complexity of at least one fourth audio format type.

[0426] In the second design, the device 1100 may be the first communication entity in the aforementioned embodiment, or may be a component (such as a chip) of the first communication entity. The device 1100 may implement the steps or processes performed by the first communication entity in the above method embodiment. The communication unit 1110 may be used to perform the operations related to the transmission and reception of the first communication entity in the above method embodiment (such as the operations of sending and / or receiving data or messages). For example, the communication unit 1110 may be used to perform Figure 5 The processing unit 1120 may be used to perform operations related to the processing of the first communication entity in the above method embodiment, or operations other than sending and receiving (such as operations other than sending and / or receiving data or messages).

[0427] In a possible implementation, a communication unit 1110 is used to send first audio format information and second audio format information to a second communication entity, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format. The first audio format is an audio format that can be adopted by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be adopted by the first communication entity when performing IVAS decoding; the communication unit 1110 is also used to receive fifth audio format information and sixth audio format information from the second communication entity, wherein the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information indicates at least one fifth audio format, and the sixth audio format information indicates at least one sixth audio format. The fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

[0428] Optionally, the communication unit 1110 is further configured to receive first audio data from a second communication entity; and the processing unit 1120 is configured to perform IVAS decoding on the first audio data based on the fifth audio format information.

[0429] Optionally, the communication unit 1110 is further configured to send second audio data to the second communication entity, where the second audio data is generated by performing IVAS encoding based on the sixth audio format information.

[0430] Another possible implementation method is that the communication unit 1110 is used to receive fifth audio format information and sixth audio format information from a third communication entity, wherein the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; the communication unit 1110 is also used to transmit audio data with the second communication entity based on the fifth audio format information and the sixth audio format information.

[0431] Optionally, the communication unit 1110 is further configured to receive first audio data from a second communication entity; and the processing unit 1120 is configured to perform IVAS decoding on the first audio data based on the fifth audio format information.

[0432] Optionally, the communication unit 1110 is further configured to send second audio data to the second communication entity, where the second audio data is generated by performing IVAS encoding based on the sixth audio format information.

[0433] In the third design, the device 1100 may be the third communication entity in the aforementioned embodiment, or may be a component (such as a chip) of the third communication entity. The device 1100 may implement the steps or processes corresponding to those performed by the third communication entity in the above method embodiment. The communication unit 1110 may be used to perform the operations related to the transmission and reception of the third communication entity in the above method embodiment (such as the operations of sending and / or receiving data or messages). For example, the communication unit 1110 may be used to perform Figure 8 The processing unit 1120 may be used to perform operations related to the processing of the third communication entity in the above method embodiment, or operations other than sending and receiving (such as operations other than sending and / or receiving data or messages).

[0434] In a possible implementation, a communication unit 1110 is used to send first audio format information and second audio format information to a second communication entity, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format. The first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; the communication unit 1110 is also used to receive fifth audio format information and sixth audio format information from the second communication entity, wherein the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be used by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be used by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; the communication unit 1110 is used to send the fifth audio format information and the sixth audio format information to the first communication entity.

[0435] It can be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0436] It can also be understood that the device 1100 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit, and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 1100 can be specifically the first communication entity in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the first communication entity in the above-mentioned method embodiments. Alternatively, the device 1100 can be specifically the second communication entity in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the second communication entity in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.

[0437] The apparatus 1100 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the first communication entity in the above-mentioned method, or the apparatus 1100 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the second communication entity in the above-mentioned method, and the apparatus 1100 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the third communication entity in the above-mentioned method. The functions can be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the communication unit can be replaced by a transceiver (for example, the sending unit in the communication unit can be replaced by a transmitter, and the receiving unit in the communication unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0438] In addition, the communication unit 1110 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0439] It should be pointed out that Fig.10 The device in the embodiment may be a communication entity in the foregoing embodiment, or may be a chip or a chip system, such as a system on chip (SoC). The communication unit may be an input / output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0440] Fig.11 1 is a schematic diagram of another communication device 1200 provided in an embodiment of the present application. The device 1200 includes a processor 1210, and the processor 1210 is used to execute a computer program or instruction stored in a memory 1220, or read data stored in the memory 1220, to execute the method in each method embodiment above. Optionally, there are one or more processors 1210.

[0441] Alternatively, if Fig.11 As shown, the device 1200 also includes a memory 1220, which is used to store computer programs or instructions and / or data. The memory 1220 can be integrated with the processor 1210, or can also be separately set. Optionally, there are one or more memories 1220.

[0442] Alternatively, if Fig.11 As shown, the device 1200 further includes a transceiver 1230, and the transceiver 1230 is used for receiving and / or sending signals. For example, the processor 1210 is used for controlling the transceiver 1230 to receive and / or send signals.

[0443] As a solution, the device 1200 is used to implement the operations performed by the first communication entity in the above method embodiments.

[0444] As another solution, the device 1200 is used to implement the operations performed by the second communication entity in the above method embodiments.

[0445] As yet another solution, the device 1200 is used to implement the operations performed by the third communication entity in the above method embodiments.

[0446] It can be understood that the processor mentioned in the embodiments of the present application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0447] It can also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. 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) or a flash memory. The volatile memory can be a random access memory (RAM). For example, RAM can be used as an external cache. As an example and not a limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous connection dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0448] It is understandable that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0449] It will also be appreciated that the memory described herein is intended to include, without being limited to, these and any other suitable types of memory.

[0450] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the first communication entity, the second communication entity, or the third communication entity in the above-mentioned method embodiments are stored.

[0451] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the method performed by the first communication entity, the second communication entity, or the third communication entity in the above-mentioned method embodiments.

[0452] An embodiment of the present application also provides a communication system, including at least one of the aforementioned first communication entity, second communication entity, and third communication entity.

[0453] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0454] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0455] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0456] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for audio parameter negotiation, characterized in that: include: Receive first audio format information and second audio format information, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format, where the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; Based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, the fifth audio format information and the sixth audio format information are sent, wherein the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is the audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is the audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

2. The method according to claim 1, characterized in that The at least one fifth audio format is an intersection of the at least one second audio format and the at least one third audio format; The at least one sixth audio format is an intersection of the at least one first audio format and the at least one fourth audio format.

3. The method according to claim 1 or 2, characterized in that: The receiving the first audio format information and the second audio format information comprises: receiving the first audio format information and the second audio format information from the first communication entity; The sending the fifth audio format information and the sixth audio format information includes: sending the fifth audio format information and the sixth audio format information to the first communication entity.

4. The method according to claim 3, characterized in that The receiving the first audio format information and the second audio format information from the first communication entity comprises: receiving a first request message from the first communication entity, where the first request message is an invite request message or a re-invite request message, and the first request message includes the first audio format information and the second audio format information; The sending the fifth audio format information and the sixth audio format information to the first communication entity comprises: A response message of the first request message is sent to the first communication entity, wherein the response message includes the fifth audio format information and the sixth audio format information.

5. The method according to any one of claims 1 to 4, characterized in that The first communication entity is a calling terminal device, and the second communication entity is a called terminal device, or, The first communication entity is a calling terminal device, and the second communication entity is a media resource function network element, or, The first communication entity is a media resource function network element, and the second communication entity is a called terminal device.

6. The method according to claim 3, characterized in that The receiving the first audio format information and the second audio format information from the first communication entity comprises: receiving a first response message from the first communication entity, where the first response message is a 18X response message or a 200 response message, where the first response message includes the first audio format information and the second audio format information, and where the 18X response message is a 180 response message or a 183 response message; The sending the fifth audio format information and the sixth audio format information to the first communication entity comprises: A confirmation message of the first response message is sent to the first communication entity, where the confirmation message includes the fifth audio format information and the sixth audio format information.

7. The method according to any one of claims 1 to 3 and 6, characterized in that: The first communication entity is a called terminal device, the second communication entity is a calling terminal device, or, The first communication entity is a called terminal device, and the second communication entity is a media resource function network element, or, The first communication entity is a media resource function network element, and the second communication entity is a calling terminal device.

8. The method according to claim 1 or 2, characterized in that: The receiving the first audio format information and the second audio format information comprises: receiving the first audio format information and the second audio format information from a third communication entity; The sending the fifth audio format information and the sixth audio format information includes: sending the fifth audio format information and the sixth audio format information to the third communication entity.

9. The method according to claim 8, characterized in that The receiving the first audio format information and the second audio format information from the third communication entity comprises: receiving a first request message from the third communication entity, where the first request message is an invite request message or a re-invite request message, and the first request message includes the first audio format information and the second audio format information; The sending the fifth audio format information and the sixth audio format information to the third communication entity comprises: A response message of the first request message is sent to the third communication entity, wherein the response message includes the fifth audio format information and the sixth audio format information.

10. The method according to claim 8 or 9, characterized in that: The third communication entity is a proxy call session control function network element, the second communication entity is a called terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

11. The method according to claim 8, characterized in that The receiving the first audio format information and the second audio format information from the third communication entity comprises: receiving a first response message from the third communication entity, where the first response message is a 18X response message or a 200 response message, where the first response message includes the first audio format information and the second audio format information, and where the 18X response message is a 180 response message or a 183 response message; The sending the fifth audio format information and the sixth audio format information to the third communication entity comprises: A confirmation message of the first response message is sent to the third communication entity, where the confirmation message includes the fifth audio format information and the sixth audio format information.

12. The method according to claim 8 or 11, characterized in that: The third communication entity is a proxy call session control function network element, the second communication entity is a calling terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: Sending first audio data to the first communication entity, where the first audio data is generated by performing IVAS encoding based on the fifth audio format information.

14. The method according to any one of claims 1 to 13, characterized in that The method further comprises: receiving second audio data from the first communication entity; The second audio data is IVAS-decoded based on the sixth audio format information.

15. The method according to any one of claims 1 to 14, characterized in that Any of the first audio format information to the fourth audio format information includes a type and a rate of each audio format indicated accordingly.

16. The method according to any one of claims 1 to 15, characterized in that The sending of fifth audio format information and sixth audio format information based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information includes: The fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information and the third audio format information and the fourth audio format information.

17. The method according to claim 16, characterized in that The determining the fifth audio format information and the sixth audio format information based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information comprises: The fifth audio format information and the sixth audio format information are determined based on a first strategy, the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, wherein the first strategy is to search from high to low complexity of the type of the at least one third audio format, or the first strategy is to search from high to low complexity of the type of the at least one fourth audio format.

18. The method according to any one of claims 1 to 17, characterized in that The types of audio formats supported by IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, higher-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA.

19. A method for audio parameter negotiation, characterized in that: include: Sending first audio format information and second audio format information, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format, where the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; Receive fifth audio format information and sixth audio format information, wherein the fifth audio format information and the sixth audio format information are determined based on the first audio format information and the second audio format information, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding.

20. The method according to claim 19, characterized in that The sending of the first audio format information and the second audio format information comprises: sending the first audio format information and the second audio format information to the second communication entity; The receiving the fifth audio format information and the sixth audio format information includes: receiving the fifth audio format information and the sixth audio format information from the second communication entity.

21. The method according to claim 20, characterized in that The method further comprises: receiving first audio data from the second communication entity; The first audio data is IVAS-decoded based on the fifth audio format information.

22. The method according to claim 20 or 21, characterized in that The method further comprises: Sending second audio data to the second communication entity, where the second audio data is generated by performing IVAS encoding based on the sixth audio format information.

23. The method according to any one of claims 20 to 22, The sending the first audio format information and the second audio format information to the second communication entity includes: Sending a first request message to the second communication entity, where the first request message is an invite request message or a re-invite request message, and the first request message includes the first audio format information and the second audio format information; The receiving the fifth audio format information and the sixth audio format information from the second communication entity comprises: A response message to the first request message is received from the second communication entity, the response message including the fifth audio format information and the sixth audio format information.

24. The method according to any one of claims 20 to 23, characterized in that: The first communication entity is a calling terminal device, and the second communication entity is a called terminal device, or, The first communication entity is a calling terminal device, and the second communication entity is a media resource function network element, or, The first communication entity is a media resource function network element, and the second communication entity is a called terminal device.

25. The method according to any one of claims 20 to 22, characterized in that The sending the first audio format information and the second audio format information to the second communication entity includes: Sending a first response message to the second communication entity, where the first response message is a 18X response message or a 200 response message, the first response message includes the first audio format information and the second audio format information, and the 18X response message is a 180 response message or a 183 response message; The receiving the fifth audio format information and the sixth audio format information from the second communication entity comprises: A confirmation message of the first response message is received from the second communication entity, the confirmation message including the fifth audio format information and the sixth audio format information.

26. The method according to any one of claims 20 to 22 and 25, characterized in that The first communication entity is a called terminal device, the second communication entity is a calling terminal device, or, The first communication entity is a called terminal device, and the second communication entity is a media resource function network element, or, The first communication entity is a media resource function network element, and the second communication entity is a calling terminal device.

27. The method according to claim 20, characterized in that The fifth audio format information and the sixth audio format information are sent to the first communication entity.

28. The method according to claim 27, The sending the first audio format information and the second audio format information to the second communication entity includes: Sending a first request message to the second communication entity, where the first request message is an invite request message or a re-invite request message, and the first request message includes the first audio format information and the second audio format information; The receiving the fifth audio format information and the sixth audio format information from the second communication entity comprises: A response message to the first request message is received from the second communication entity, the response message including the fifth audio format information and the sixth audio format information.

29. The method according to claim 28, characterized in that The second communication entity is a called terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

30. The method according to claim 27, characterized in that The sending the first audio format information and the second audio format information to the second communication entity includes: Sending a first response message to the second communication entity, where the first response message is a 18X response message or a 200 response message, the first response message includes the first audio format information and the second audio format information, and the 18X response message is a 180 response message or a 183 response message; The receiving the fifth audio format information and the sixth audio format information from the second communication entity comprises: A confirmation message of the first response message is received from the second communication entity, the confirmation message including the fifth audio format information and the sixth audio format information.

31. The method according to claim 30, characterized in that The second communication entity is a calling terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

32. The method according to any one of claims 19 to 31, characterized in that Any of the first to sixth audio format information includes a type and a rate of each audio format indicated accordingly.

33. The method according to any one of claims 19 to 32, characterized in that The types of audio formats supported by IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, higher-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA.

34. A method for audio parameter negotiation, characterized in that: include: Receive fifth audio format information and sixth audio format information, wherein the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing immersive voice and audio service IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; Audio data is transmitted with the second communication entity based on the fifth audio format information and the sixth audio format information.

35. The method according to claim 34, characterized in that The performing audio data transmission with the first communication entity based on the fifth audio format information and the sixth audio format information includes: receiving first audio data from the second communication entity; The first audio data is IVAS-decoded based on the fifth audio format information.

36. The method according to claim 34 or 35, characterized in that The performing audio data transmission with the first communication entity based on the fifth audio format information and the sixth audio format information includes: Sending second audio data to the second communication entity, where the second audio data is generated by performing IVAS encoding based on the sixth audio format information.

37. The method according to claim 36, characterized in that The receiving the fifth audio format information and the sixth audio format information includes: receiving the fifth audio format information and the sixth audio format information from a third communication entity.

38. The method according to claim 37, characterized in that The third communication entity is a proxy call session control function network element, the second communication entity is a called terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway; or, The third communication entity is a proxy call session control function network element, the second communication entity is a calling terminal device, and the first communication entity is an Internet Protocol Multimedia Subsystem access gateway.

39. The method according to any one of claims 34 to 38, characterized in that Any one of the fifth audio format information and the sixth audio format information includes a type and a rate of each audio format indicated accordingly.

40. The method according to any one of claims 34 to 39, characterized in that The types of audio formats supported by IVAS codec include mono, stereo, multi-channel, multi-object, first-order high-fidelity stereo FOA, higher-order high-fidelity stereo HOA, and metadata-assisted spatial audio MASA.

41. A method for audio parameter negotiation, characterized in that: include: Sending first audio format information and second audio format information to the second communication entity, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format, where the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; receiving the first audio format information and the second audio format information from the first communication entity; Based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, fifth audio format information and sixth audio format information are sent to the first communication entity, wherein the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; The fifth audio format information and the sixth audio format information are received from the second communication entity.

42. A method for audio parameter negotiation, characterized in that: include: Sending first audio format information and second audio format information to the second communication entity, where the first audio format information indicates at least one first audio format, and the second audio format information indicates at least one second audio format, where the first audio format is an audio format that can be used by the first communication entity when performing immersive voice and audio service IVAS encoding, and the second audio format is an audio format that can be used by the first communication entity when performing IVAS decoding; receiving the first audio format information and the second audio format information from a third communication entity; Based on the first audio format information, the second audio format information, the third audio format information and the fourth audio format information, fifth audio format information and sixth audio format information are sent to the third communication entity, wherein the third audio format information indicates at least one third audio format, the fourth audio format information indicates at least one fourth audio format, the third audio format is an audio format that can be adopted by the second communication entity when performing IVAS encoding, the fourth audio format is an audio format that can be adopted by the second communication entity when performing IVAS decoding, the fifth audio format information indicates at least one fifth audio format, the sixth audio format information indicates at least one sixth audio format, the fifth audio format is an audio format to be adopted by the first communication entity when performing IVAS decoding and / or the second communication entity when performing IVAS encoding, and the sixth audio format is an audio format to be adopted by the first communication entity when performing IVAS encoding and / or the second communication entity when performing IVAS decoding; receiving the fifth audio format information and the sixth audio format information from the second communication entity; Sending the fifth audio format information and the sixth audio format information to the first communication entity; The fifth audio format information and the sixth audio format information are received from the third communication entity.

43. The method according to claim 41 or 42, characterized in that The method further comprises: Sending first audio data to the first communication entity, where the first audio data is generated by IVAS encoding based on the fifth audio format information; receiving the first audio data from the second communication entity; The first audio data is IVAS-decoded based on the fifth audio format information.

44. The method according to any one of claims 41 to 43, characterized in that The method further comprises: Sending second audio data to the second communication entity, where the second audio data is generated by IVAS encoding based on the sixth audio format information; receiving the second audio data from the first communication entity; The second audio data is IVAS-decoded based on the sixth audio format information.

45. A communication device, characterized in that: The apparatus comprises: a module for executing the method of any one of claims 1 to 18, or a module for executing the method of any one of claims 19 to 33, or a module for executing the method of any one of claims 34 to 40.

46. ​​A communication device, characterized in that: include: A processor, configured to execute a computer program stored in a memory so that the apparatus performs the method as claimed in any one of claims 1 to 18, or so that the apparatus performs the method as claimed in any one of claims 19 to 33, or so that the apparatus performs the method as claimed in any one of claims 34 to 40.

47. A computer program product, characterized in that The computer program product comprises instructions for executing the method of any one of claims 1 to 18, or the computer program product comprises instructions for executing the method of any one of claims 19 to 33, or the computer program product comprises instructions for executing the method of any one of claims 34 to 40.

48. A computer-readable storage medium, characterized in that include: The computer-readable storage medium stores a computer program; when the computer program runs on a computer, the computer executes the method as claimed in any one of claims 1 to 18, or the computer executes the method as claimed in any one of claims 19 to 33, or the computer executes the method as claimed in any one of claims 34 to 40.

49. A communication system, characterized in that: comprising a first communication entity and a second communication entity, The second communication entity is used to execute the method according to any one of claims 1 to 7 and 13 to 18, and the first communication entity is used to execute the method according to any one of claims 19 to 26, 32 and 33.

50. A communication system, characterized in that: comprising a first communication entity, a second communication entity and a third communication entity, The second communication entity is used to execute the method as described in any one of claims 1, 2, 8 to 18, the first communication entity is used to execute the method as described in any one of claims 34 to 40, and the third communication entity is used to execute the method as described in any one of claims 19, 20, 27 to 33.

Images