Immersive communication sessions
By using a negotiation parameter to enable devices to transmit bitstreams at their own computational levels, the patent addresses the challenge of varying capabilities in immersive audio systems, enhancing user experience and reducing unnecessary transcoding.
Patent Information
- Application Number
- GB2025005372
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-04-10
- Publication Date
- 2026-11-11
AI Technical Summary
Existing immersive audio communication systems struggle with establishing sessions that accommodate participants with varying computational capabilities, leading to suboptimal audio quality and inefficient transcoding or downmixing due to intermediate network devices constraining session links based on their own capabilities rather than those of the end-devices.
Implementing a negotiation parameter that allows devices to provide bitstreams based on their own computational capabilities, exceeding those of the receiving devices, enabling flexible session establishment and optimizing audio quality by allowing passthrough or transcoding modes according to the sender's capabilities.
Enhances user experience by allowing devices to transmit bitstreams at their maximum capabilities, reducing unnecessary transcoding, and ensuring optimal immersive audio quality across diverse computational levels.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNOLOGICAL FIELD Examples of the disclosure relate to immersive communication sessions. Some relate to session negotiations for immersive communication sessions. BACKGROUND In immersive communication sessions participants within the session can have different computational capability levels. A mutually acceptable level is needed for the session so as to enable immersive audio outputs to be provided to the participants. BRIEF SUMMARY According to various, but not necessarily all, examples of the disclosure there may be provided an apparatus for immersive audio communication comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least: receiving a negotiation parameter for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus within the immersive audio communication session; determining a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus; and providing the at least one bitstream with the determined computational capability level. The negotiation parameter may comprise an indication of a constraint based on a further computational capability level wherein the further computational capability level refers to a computational capability level of a media receiver. Determining the computational capability level for the at least one bitstream may comprise determining a computational capability level that exceeds the computational capability level of the media receiver. The processor and memory may be arranged to cause the apparatus to perform providing the at least one bitstream with the determined computational capability level wherein the determined computational capability level exceeds the computational capability level of the media receiver. The determined computational capability level may comprise at least one computational level that equals or is lower than the maximum computational capability level of the apparatus. The negotiation parameter may comprise an indication of at least one of: a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the apparatus without transcoding; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the apparatus without decoding; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the apparatus with parsing or processing or extracting in a compressed domain; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the apparatus with lightweight processing that is less complex than decoding and / or transcoding; and a transcoding mode of the media receiver indicating a capability of the media receiver to receive at least one bitstream in a first format from the apparatus and to provide at least one transcoded bitstream in a second different format. Different formats may comprise different one or more of: coded formats; bitrate; bitstream level; coded subformat; coded minor format; bandwidth; immersive / mono mode or format; number of channels; and split rendering operation. The negotiation parameter may be received in a session negotiation offer for the immersive audio communication session. The immersive audio communication session may be established by: constructing an answer to the session negotiation offer wherein the answer is based on the negotiation parameter; and transmitting the answer to the media receiver. The at least one processor and the at least one memory may also be configured to cause the apparatus to perform: constructing a session negotiation offer for the immersive audio communication session and sending the session negotiation offer to the media receiver wherein the negotiation parameter is received in a response to the session negotiation offer. The apparatus may be arranged to establish the immersive audio communication session with the media receiver. The at least one processor and the at least one memory may also be configured to cause the apparatus to perform: detecting the negotiation parameter in a received message relating to session negotiation. The apparatus may comprise a user equipment or the apparatus is comprised within a user equipment. The media receiver may comprise at least one of: multiparty conferencing unit; selective forwarding unit; a receiving unit of a user equipment; intermediate network device. According to various, but not necessarily all, examples of the disclosure there may be provided a method comprising: receiving a negotiation parameter for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus within the immersive audio communication session; determining a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus; and providing the at least one bitstream with the determined computational capability level. According to various, but not necessarily all, examples of the disclosure there may be provided a computer program comprising computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: receiving a negotiation parameter for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus within the immersive audio communication session; determining a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus; and providing the at least one bitstream with the determined computational capability level. According to various, but not necessarily all, examples of the disclosure there may be provided an apparatus for immersive audio communication comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least: sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and receiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. The negotiation parameter may comprise an indication of a constraint based on a computational capability level of the apparatus. The negotiation parameter may be configured to enable a media sender to provide at least one bitstream with a computational capability level determined based at least on a computational capability level of the media sender within the immersive audio communication session The computational capability level for the at least one received bitstream may exceed the computational capability level of the apparatus. The negotiation parameter may comprise an indication of at least one of: a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender without transcoding; a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender without decoding; a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender with parsing or processing or extracting in a compressed domain; a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender with lightweight processing that is less complex than decoding and / or transcoding; and a transcoding mode of the apparatus indicating a capability of the apparatus to receive at least one bitstream in a first format from the media sender and to provide a at least one transcoded bitstream in a second different format. Different formats may comprise different one or more of: coded formats; bitrate; bitstream level; coded subformat; coded minor format; bandwidth; immersive / mono mode or format; number of channels; and split rendering operation. The negotiation parameter may be sent in a session negotiation offer for the immersive audio communication session. The immersive audio communication session may be established by: receiving an answer to the session negotiation offer from the media sender wherein the answer is based, at least in part, on the negotiation parameter; and establishing the immersive audio communication session based on the answer. The at least one processor and the at least one memory may also be configured to cause the apparatus to perform: receiving a session negotiation offer for an immersive audio communication session from the media sender and: sending the negotiation parameter in response to the session negotiation offer. The at least one processor and the at least one memory may also be configured to cause the apparatus to perform negotiations with multiple media senders to cause the multiple media senders to participate in the immersive audio communication session. The apparatus may comprise at least one of: multiparty conferencing unit; selective forwarding unit; a receiving unit of a user equipment; intermediate network device. The media sender may comprise a user equipment or the media sender is comprised within a user equipment. According to various, but not necessarily all, examples of the disclosure there may be provided a method comprising: sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and receiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. According to various, but not necessarily all, examples of the disclosure there may be provided a computer program comprising computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and receiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. According to various, but not necessarily all, embodiments there is provided an apparatus comprising: at least one processor; and at least one memory; the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least a part of one or more methods described herein. According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for performing at least part of one or more methods described herein. The description of a function and / or action should additionally be considered to also disclose any means suitable for performing that function and / or action. Functions and / or actions described herein can be performed in any suitable way using any suitable method. According to various, but not necessarily all, embodiments there is provided examples as claimed in the appended claims. While the above examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all the features described in respect of other examples of the disclosure, and vice versa. Also, it is to be appreciated that any one or more or all the features, in any combination, may be implemented by / comprised in / performable by an apparatus, a method, and / or instructions as desired, and as appropriate. The description of a function should additionally be considered to also disclose any means suitable for performing that function BRIEF DESCRIPTION Some examples will now be described with reference to the accompanying drawings in which: FIG. 1 shows an example packet structure; FIGS. 2A and 2B show example methods; FIG. 3 shows an example transmission scenario; FIG. 4 shows an example transmission scenario; FIG. 5 shows an example codec mode request sequence; FIG. 6 shows an example transmission scenario; FIG. 7 shows an example transmission scenario; FIG. 8 shows an example transmission scenario; FIG. 9 shows an example transmission scenario; FIG. 10 shows an example transmission scenario; FIG. 11 shows an example transmission scenario; FIG. 12 shows an example method; and FIG. 13 shows an example controller. The figures are not necessarily to scale. Certain features and views of the figures can be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aid explication. Corresponding reference numerals are used in the figures to designate corresponding features. For clarity, all reference numerals are not necessarily displayed in all figures. DETAILED DESCRIPTION Immersive audio communication sessions can be implemented using codecs such as 3GPP IVAS (Immersive Voice and Audio Services) or other spatial audio codecs. The spatial audio codecs can support at least three degrees of rotation freedom (yaw, pitch, roll) for all spatial inputs. The IVAS codec, or other suitable spatial audio codecs, can be used in a variety of scenarios. The scenario cannot always be known beforehand. The spatial audio codecs can have many supported input formats and output formats. The main supported input formats for IVAS are stereo, multichannel (MC), objectbased audio (for example, independent streams with metadata (ISM)), scene-based audio (SBA), and Metadata-assisted spatial audio (MASA). In addition, the following combinations are supported: Objects with MASA (OMASA) and Objects with SBA (OSBA). IVAS furthermore includes the EVS (enhanced voice services) codec for mono input operation. The IVAS output formats comprise mono, stereo, multi-channel (including custom loudspeaker layouts), FOA (first order Ambisonic), HOA2 (higher order Ambisonic 2), HOA3, and binaural (with optional head-tracking and optional room effect). In addition, the IVAS decoder allows decoding of an output format corresponding to the input format, including ISM and MASA, for each input. The IVAS codec bitstream contains information on the contents of each bitstream frame. This information includes the input format and additional information on the present format, for example sub format signaling, (for instance, order of Ambisonics, channel layout of MC, number of transport channels, or any other suitable information). This format information is in addition to the encoded audio signal and possible metadata. Furthermore, IVAS bitstream frames are designed to be standalone so that an IVAS decoder can start decoding from any valid IVAS frame (containing full data for the format specified in the bitstream) and produce good quality output. Real-time transport protocol (RTP) is used to carry multiple multimedia formats. This permits the transport of new formats without revising the RTP standard. To this end, the information required by a specific application of the protocol is not included in the generic RTP header. For a class of applications (such as audio or video), an RTP profile can be defined. For a media format (such as, a specific video coding format), an associated RTP payload format can be defined. Every instantiation of RTP in a particular application can require a profile and payload format specifications. The profile defines the codecs used to encode the payload data and their mapping to payload format codes in the protocol field Payload Type (PT) of the RTP header. For example, the RTP profile for audio and video conferences with minimal control is defined in RFC 3551. The profile defines a set of static payload type assignments, and a dynamic mechanism for mapping between a payload format, and a PT value using Session Description Protocol (SDP). The latter mechanism is used for newer video codecs such as RTP payload format for H.264 Video defined in RFC 6184 or RTP Payload Format for High Efficiency Video Coding (HEVC) defined in RFC 7798. An RTP session can be established for respective multimedia streams. Audio and video streams can use separate RTP sessions. This enables a receiver to selectively receive components of a particular stream. The RTP specification recommends even port numbers for RTP, and the use of the next odd port number for the associated realtime transport control protocol (RTCP) session. A single port can be used for RTP and RTCP in applications that multiplex the protocols. Each RTP stream consists of RTP packets, which in turn comprise an RTP header and payload pairs. Fig. 1 shows an example IVAS RTP packet structure 100. The packet structure 100 comprises an RTP header 102 and an IVAS payload 104. The RTP Header 102 (and any possible RTP Header Extension) follow the common RTP design. The IVAS payload 104 comprises a payload header 106, frame data 108 and processing information (PI) data 110. The payload header 106 comprises different types of header bytes: ToC (Table of Content) and E-bytes (Extra bytes). The ToC bytes describe the content of the frame data 108 (by indicating the size / bitrate for the data frames). The ToC bytes also differentiate IVAS frames from EVS frames, in case the IVAS is operating in mono EVS mode. The E-bytes signal additional information, such as Codec Mode Requests (CMR) which indicate a request to change the bitrate (and possibly other configurations like format and bandwidth) of an incoming IVAS stream. E-bytes can also be used to explicitly indicate the presence of the PI data 110 at the end of the IVAS payload 104. The frame data 108 comprises the IVAS data frames (and EVS data frames in a case of using IVAS in mono mode). The data frames represent the encoded IVAS bitstreams. The bitstreams comprise the encoded IVAS audio data with possible additional metadata. The bitstreams can also comprise information about the input / coded format and sub-format of the encoded data (e.g., multichannel 5.1 format). EVS frames do not include such format data. The PI data 110 comprises the processing information data and related headers. PI data can be used to transmit any (non-audio) data that can be used to assist the rendering or processing of the audio data, such as, scene and device orientation data, or any other suitable information. In some examples the PI data 110 can also be used to request something from other participants in a communication session. For instance, the PI data 110 could be used to mute an incoming stream or increase noise suppression. Feedback data can also be transmitted, for example, the head orientation of a listener. The computational capability of devices or apparatus within an immersive communication session can be defined in terms of a level. The different levels enable rendering with different complexity, memory requirements, and functionality. The different levels can be built on each other so that a higher level comprises all features and functionalities of lower levels but with some additional features. For example, level one could be a core level, level two can comprise all of the features of level one and some additional features. Level three can comprise all of the features of level two and some additional features. Level three can be the highest level. Respective levels can be constrained by a bitrate limit for the bitstream. For example all bitrates up to 80 kbps for level 1, all bitrates up to 192 kbps for level 2 and all bitrates (up to 512 kbps) for level 3. For the encoding, if an apparatus or device supports a certain level this means that it has the capability to encode all coded formats or coding modes at all bitrates of that level. For example, a level 1 compliant encoder is able to encode all IVAS coded formats up to 80 kbps. For the decoding, if an apparatus or device supports a certain level this means that it has the capability to decode all coded formats or coding modes at all bitrates of that level to an immersive output format (any output other than mono), to render (with the internal renderer) the decoded bitstream to all output formats and to support external processing output for the decoded bitstream. A compliant decoder of a certain level is also able to provide at least mono or stereo decoding for bitstreams corresponding to a higher level than the defined level of the IVAS compliant decoder. For example, a level 1 compliant decoder is able to decode and render all coded formats up to 80 kbps into an immersive output format (such as binaural). A level 1 compliant decoder is also able to decode, for example, a bitstream of 128 kbps into a stereo output. In IVAS, or other similar codecs the level capability of a session can be determined by the participants of the session. For example, if a level 1 device is communicating with a level 3 device, it may be beneficial to negotiate the session level to 1 or to a mutually acceptable level. This will avoid providing audio bitstreams at a level that is higher than supported by one of the devices and will enable immersive output to users of both devices. This approach is suitable in an end-to-end communication scenario between single participant devices. However, in a network environment, the data transmission path from one device to the other device can contain also other entities, such as MCUs (Multiparty Conferencing Unit), SFUs (Selective Forwarding Unit), or any other suitable entity. These entities can be connected to multiple different participant devices or other devices. The end-devices (such as a user equipment (UE) or mobile device) might not have a direct communication path between them. If there is no direct communication path then there is not a direct session link between the respective devices. The respective end-devices can be obscured by multiple media session (such as, session initiation protocol (SIP) session) links between the end-devices and the network elements. In some examples the communication session can comprise a splitrendering scenario where the receiving device (pre-rendering entity) is a lower-level (or lower complexity or lower power) device than the presentation device (postrendering entity). As one entity of the full communication path, MCU capabilities are defined to serve a specific level of IVAS session. As the MCU may need to perform transcoding or bitstream remixing, the MCU could limit the overall IVAS session even though the end devices could support higher levels. If an MCU is only forwarding the IVAS bitstreams, it would be beneficial to not limit the session link between a UE and the MCU based on the capability level of the MCU but based on the end UE. This is because the MCU is not performing rendering or other computationally heavy operations, but only forwarding the bitstreams. Such MCU (or other network or transmission path element) specific session negotiation aspects are lacking for IVAS (and immersive audio in general). Figs. 2A and 2B show example methods that address these issues. In these examples the computational capability level of an intermediate network device such as an MCU does not need to be taken into account. Instead the bitstreams can be provided at a level appropriate for the end-devices. The method of Fig. 2A can be implemented by any suitable apparatus. The apparatus could be a media sender. The media sender could be a User Equipment (UE) or any other device within a communication network. The apparatus that implements the method of Fig. 2A can establish an immersive audio communication session with another apparatus. The immersive audio communication session could be an IVAS session or any other suitable type of session. The immersive audio communication session can be established with a media receiver. In this case the media receiver could be an intermediate network device such as an MCU, SFU, or could be a receiving unit of another UE or could be any other suitable type of apparatus. Establishing the immersive audio communication session can comprise an offer-answer-acknowledge process. Any signals received after that process can be considered to be sent within the immersive communication session. The bitstream transmission might change at the start of the session or at any other time during the session. The changes could be in the computational level of the bitstream, the format of the bitstream or any other suitable changes. At block 200 the apparatus receives a negotiation parameter for the immersive audio communication session. The negotiation parameter can be received from the media receiver. The negotiation parameter can be received in any suitable signalling or messages. The apparatus can be arranged to detect a negotiation parameter in a received message relating to session negotiation. The negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus. The bitstream can be sent within the immersive audio communication session. The negotiation parameter can comprise an indication of a constraint based on a further computational capability level. The further computational capability level can refer to a computational capability level of a media receiver. The media receiver could be a forwarding device or intermediate network device. Enabling the apparatus to provide a bitstream based on a computational capability level of the apparatus means that the computational capability of the bitstream does not have to be restricted by the computational capability level of the media receiver. This can enable the apparatus to have a greater degree of freedom when selecting computational capability levels. At block 202 the method comprises determining a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus. The use of the negotiation parameter gives the apparatus the freedom to consider the computational capability of the apparatus when determining a computational capability level for use for bitstreams in the immersive audio communication session. This can enable the apparatus to determine a computational capability level for the bitstream that exceeds the computational capability level of the media receiver. The determined computational capability level can comprise at least one computational level that equals or is lower than the maximum computational capability level of the apparatus. At block 204 the method comprises providing the at least one bitstream with the determined computational capability level. The apparatus can send a bitstream to the media receiver with the determined computational capability level. As the negotiation parameter enables the apparatus to determine a computational capability level for the bitstream that exceeds the computational capability level of the media receiver this bitstream can be provided with a computational capability level that exceeds the computational capability level of the media receiver. The media receiver could then forward the bitstream to other UEs or other devices within the immersive audio communication session. The negotiation parameter can be received in any suitable signalling. In some examples the media receiver can send the offer for the immersive audio communication session and the apparatus can provide an answer. In such examples the negotiation parameter can be received in a session negotiation offer for the immersive audio communication session. In such examples establishing the immersive audio communication session can comprise constructing an answer to the session negotiation offer wherein the answer is based on the negotiation parameter and transmitting the answer to the media receiver. In other examples the apparatus can send the offer for the immersive audio communication session and the media receiver can provide an answer. In such examples establishing the immersive audio communication session can comprise constructing a session negotiation offer for the immersive audio communication session and sending the session negotiation offer to the media receiver. The negotiation parameter can then be received in a response to the session negotiation offer. The method of Fig. 2B can be implemented by another apparatus. The apparatus could be a media receiver. The media receiver could be an intermediate network device such as an MCU, SFU, or could be a receiving unit of another UE or could be any other suitable type of device. The method of Fig. 2B corresponds to the method of Fig. 2A in that an apparatus such as a media receiver that implements the method of Fig. 2B can be in an immersive audio communication session with an apparatus such as a media sender that implements the method of Fig. 2A. The apparatus that implements the method of Fig. 2B can establish an immersive audio communication session with another apparatus. The immersive audio communication session could be an IVAS session or any other suitable type of session. The immersive audio communication session can be established with a media sender. In this case the media sender could be a UE or any other suitable type of device. The media sender could be a device that implements the method of Fig. 2A or any other suitable method. At block 210 the apparatus sends the negotiation parameter for the immersive audio communication session. The negotiation parameter can be sent to the media sender. The negotiation parameter can be sent in any suitable signalling or messages. The negotiation parameter can be sent in any suitable signalling. In some examples the apparatus can send the offer for the immersive audio communication session and the media sender can provide an answer. In such examples the negotiation parameter can be sent in a session negotiation offer for the immersive audio communication session. In such examples establishing the immersive audio communication session can comprise receiving an answer to the session negotiation offer from the media sender. The answer is based, at least in part, on the negotiation parameter. The immersive audio communication session can then be established based on the answer. In other examples the media sender can send the offer for the immersive audio communication session and the apparatus can provide an answer. In such examples the apparatus can receive a session negotiation offer for an immersive audio communication session from the media sender and sending the negotiation parameter in response to the session negotiation offer. The negotiation parameter can be configured to enable a media sender to provide at least one bitstream with a computational capability level determined based at least on a computational capability level of the media sender within the immersive audio communication session The negotiation parameter can comprise an indication of a constraint based on a computational capability level of the apparatus. The negotiation parameter enables the media sender to provide a bitstream based on a computational capability level of the media sender so that the computational capability of the bitstream does not have to be restricted by the computational capability level of the apparatus. This can enable the media sender to have a greater degree of freedom when selecting computational capability levels. At block 212 the method comprises receiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. The computational capability level for the at least one received bitstream can exceed the computational capability level of the apparatus. In some examples the apparatus can perform negotiations with multiple media senders. This can enable the multiple media senders to participate in the immersive audio communication session. In some examples the negotiation parameter can provide an indication of a mode of operation of the media receiver. This can indicate that the media receiver is capable of forwarding or transcoding bitstreams with a higher computational capability level than the computational capability level of the media receiver. For example, the 18 negotiation parameter can provide an indication of a passthrough mode of operation of the media receiver and / or a transcoding mode of operations of the media receiver. The negotiation parameter could indicate at least one of: a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the media sender without transcoding; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the media sender without decoding; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the media sender with parsing or processing or extracting in a compressed domain; a passthrough mode of the media receiver indicating a capability of the media receiver to provide at least one bitstream from the media sender with lightweight processing that is less complex than decoding and / or transcoding; and a transcoding mode of the media receiver indicating a capability of the media receiver to receive at least one bitstream in a first format from the media sender and to provide at least one transcoded bitstream in a second different format; and / or any other suitable mode of operation. The different formats that the media receiver can transcode between can comprise one or more of: coded formats; bitrate; bitstream level; coded subformat; coded minor format; bandwidth; immersive / mono mode or format; number of channels; and split rendering operation, or any other suitable type of format. Fig. 3 shows an example transmission scenario in a network environment. In this example the network comprises a first user equipment (UE) 300_1 and a second UE 300_2. An MCU 302 is provided in the data transmission path between the first UE 300_1 and the second UE 300_2. Other types of intermediate network devices could be used in other examples such as an SFU or any other suitable device. The respective UEs 300_1, 300_2 can be media senders. The UEs 300_1, 300_2 could be arranged to implement the method of Fig. 2A or any other suitable method. The MCU 302 can be a media receiver that can implement the method of Fig. 2B or any other suitable method. Fig. 3 shows one data transmission path from the first UE 300_1 to the second UE 300_2. This enables the first UE 300_1 to send a bitstream to the second UE 300_2 via the MCU 302. There would also be a data transmission path in the reverse direction from the second UE 300_2 to the first UE 300_1. This would enable the second UE 300_2 to send a bitstream to the first UE 300_1. The data transmission path in the reverse direction is not shown for clarity. In this example the first UE 300_1 has computational capability level 2 and the second UE 300_2 has computational capability level 3. The MCU 302 has computational capability level 1. The transmission scenario of Fig. 3 requires two negotiations. The negotiations would occur at the beginning of the communication session. The first negotiation would be between the first UE 300_1 and the MCU 302 and the second negotiation would be between the second UE 300_2 and the MCU 302. In these negotiations the UEs 300_1, 300_2 only see the MCU 302. The UEs 300_1, 300_2 are not aware of other participants within the network. Therefore, in the example of Fig. 3 the first UE 300_1 is unaware of the second UE 300_2 and is also unaware of the computational capability level of the second UE 300_2. Similarly the second UE 300_2 is unaware of the first UE 300_1 and is also unaware of the computational capability level of the first UE 300_1. Without the use of a negotiation parameter both the first UE 300_1 and the MCU 302 constrain the transmission session based on the lower computation capability level of the two devices. This helps to avoid transcoding or downmixing operations at the MCU 302. Therefore, the session 306_1 between the first UE 300_1 and the MCU 302 is constrained to level 1 because that is the maximum computational capability level of the MCU 302. The bitstream 304_1 transmitted from the first UE 300_1 is also constrained to level 1. Similarly, the session 306_2 between the second UE 300_2 and the MCU 302 is constrained to level 1 and the bitstream 304_2 transmitted from the MCU 302 to the second UE 300_2 is also constrained to level 1 even though the second UE 300_2 could receive bitstreams up to level 3 and the first UE 300_1 could transmit bitstreams up to level 2. The quality of experience of a user of the second UE 300_2 is therefore not optimal because of the constraints of the computational capability level of the MCU 302. Fig. 4 shows another example transmission similar to that shown in Fig. 3. In this example the MCU 302 can provide a negotiation parameter 400. The negotiation parameter enables the UEs 300_1, 300_2 to provide bitstreams based on the computational capability level of the UEs 300_1,300_2 (media senders). For example, the negotiation parameter 400 can indicate a capability of the MCU 302 to operate in a passthrough or transcoding mode. This means that the computational capability level of the bitstreams from the UEs 300_1, 300_2 do not have to be restricted to the computational capability level of the MCU 302 (media receiver). This can enable the UEs 300_1, 300_2 to provide bitstreams of a computational capability level that exceeds the computational capability level of the MCU 302. The negotiation parameter 400 can be provided during the session negotiation or during any other suitable signalling. In the example of Fig. 4 the negotiation parameter 400 indicates that the MCU 302 can operate in a passthrough manner. When the MCU 302 operates in the passthrough manner the MCU 302 passes the bitstream from the first UE 300_1 to the second UE 300_2 without decoding and / or transcoding and / or rendering of the bitstream. In some examples the MCU 302 could perform some lightweight processing of the bitstream. The lightweight processing can be less complex than decoding and / or transcoding. In some examples the MCU 302 could perform some parsing of processing in the compressed domain. The negotiation parameter 400 can be a target-format (tf) parameter. The negotiation parameter 400 can be provided during the SDP negotiation. The use of the negotiation parameter 400 enables the session 306_1 between first UE 300_1 and the MCU 302 to be negotiated based on the computational capability of the first UE 300_1 instead of the computational capability of the MCU 302. Therefore, the session 306_1 between the first UE 300_1 and the MCU 302 can be negotiated to level 2 because that is the maximum computational capability level of the first UE 300_1. The bitstream 304_1 transmitted from the first UE 300_1 to the MCU 302 can be a level 2 bitstream. The session 306_2 between the second UE 300_2 and the MCU 302 can be negotiated to level 3 because that is the maximum computational capability level of the second UE 300_2. The bitstream 304_2 transmitted from the MCU 302 to the second UE 300_2 can be a level 2 bitstream. The use of the negotiation parameter 400 therefore enables the transmission scenario to be arranged so that the first UE 300_1 can send a level 2 bitstream to the second UE 300_2. The second UE 300_2 is capable of generating immersive rendering for received level 2 bitstreams. This improves the quality of experience of a user of the second UE 300_2 compared to the scenario shown in Fig. 3. Fig. 5 shows an example request sequence for a network environment similar to that shown in Figs. 3 and 4. The network environment comprises a first UE 300_1, a second UE 300_2 and an MCU 302. The MCU 302 is provided in the transmission path between the first UE 300_1 and the second UE 300_2. The respective UEs 300_1, 300_2 can be media senders however only the transmission path from the first UE 300_1 to the second UE 300_2 is shown in Fig. 5. The MCU 302 can be a media receiver. In this example the first UE 300_1 has computational capability level 2 and the second UE 300_2 has computational capability level 3. The MCU 302 has computational capability level 1. The requests can be codec mode requests (CMR) or any other suitable type of requests. At time instance T=0, the transmitted bitstream 304_1 from the first UE 300_1 is of level 1. The transmitted bitstream 304_2 from the MCU 302 to the second UE 300_2 is also of level 1. The session 306_1 between the first UE 300_1 and the MCU 302 is a level 2 session and the session 306_2 between the MCU 302 and the second UE 300_2 is a level 3 session. The scenario shown for T=0 could be the case at the beginning of the communication session, where a lower level bitstream is used initially. At time instance T=1, the second UE 300_2 sends a request 500 to increase the bitrate of the received bitstream 304_2. The request 500 can be sent from the second UE 300_2 to the MCU 302. The request 500 can indicate a bitrate that can be accepted by the second UE 300_2. This bitrate can be of a higher level than the current level of the received bitstream 304_2. For example, the bitrate indicated in the request 500 could be 128 kbps, for example which is above level 1 definition (> 80 kbps), but below level 3 definition (> 192 kbps). Therefore, in this case the request 500 is a level 2 request. The bitrate request is provided as a CMR from the second UE 300_2 to the first UE 300_1 via the MCU 302. The request 500 is possible because both sessions 306_1, 306_2 support level 2 bitrates. At time instance T=2, the first UE 300_1 has changed the bitrate of the bitstream 304_1 to the requested bitrate (128 kbps) and is transmitting the bitstream 304_1 to the MCU 302. The MCU 302 then provides the bitstream 304_2 to the second UE 300_2. The bitstreams 304_1, 304_2 are now a level 2 bitstreams. The scenario shown in Fig. 5 is only possible, when the respective sessions 306_1, 306_2 are negotiated to support the capabilities of the UEs 300_1, 300_2 or other end user devices and the respective bitrates for the levels (that is <192 kbps for session 306_1 and all bitrates for session 306_2) rather than the capabilities of the MCU 302. This can be achieved, through the use of the negotiation parameter 400. In this case the negotiation parameter 400 indicates a passthrough mode for the MCU 302. Without the use of the negotiation parameter both of the sessions 306_1, 306_2 would be limited to level 1 because that is the computational capability of the MCU 302. Without the negotiation parameter 400 the CM Rs would also be limited to level 1 (that is, <80 kbps). Fig. 6 shows another example transmission scenario in another network environment. In this example the network comprises a first UE 300_1, a second UE 300_2 and a third UE 300_3. The MCU 302 is provided in the data transmission paths between the respective UEs 300_1, 300_2, 300_3. Only the data transmission paths from the first UE 300_1 are shown in Fig. 6. Data transmission paths from the other UEs 300_2, 300_3 could also be provided. In the example of Fig. 6 the network comprises three UEs 300_1, 300_2, 300_3. The network can comprise more than three UEs in other examples. In this example the first UE 300_1 has computational capability level 2, the second UE 300_2 has computational capability level 3, and the third UE 300_3 has computational capability level 1. The MCU 302 has computational capability level 1. The media receiver can provide a negotiation parameter 400. The negotiation parameter enables the UEs 300_1, 300_2, 300_3 to provide bitstreams based on the computational capability level of the UEs 300_1, 300_2, 300_3 (media senders). For example, the negotiation parameter 400 can indicate a capability of the MCU 302 to operate in a passthrough or transcoding mode. This means that the computational capability level of the bitstreams from the UEs 300_1, 300_2, 300_3 do not have to be restricted to the computational capability level of the MCU 302 (media receiver). This can enable the UEs 300_1, 300_2, 300_3 to provide bitstreams of a computational capability level that exceeds the computational capability level of the MCU 302. The negotiation parameter 400 can be provided during the session negotiation. In the example of Fig. 6 the negotiation parameter 400 indicates that the MCU 302 can operate in a passthrough manner and also that the MCU 302 can perform some transcoding or downmixing of the bitstream. When the MCU 302 operates in the passthrough manner the MCU 302 passes the bitstream from the first UE 300_1 to the second UE 300_2 without decoding and / or transcoding and / or rendering of the bitstream. In some examples, when the MCU 302 operates in the passthrough manner the MCU 302 can perform some limited processing on the bitstream. The limited processing can be as described above. When the MCU 302 performs transcoding of the bitstream the MCU 302 can output a transcoded bitstream ata lower computational capability level than the computational capability level of the received bitstream. The negotiation parameter 400 can be a target-format (tf) parameter. The negotiation parameter 400 can be provided during the SDP negotiation. The use of the negotiation parameter 400 enables the session 306_1 between the first UE 300_1 and the MCU 302 to be negotiated to level 2 because that is the maximum computational capability level of the first UE 300_1. The bitstream 304_1 transmitted from the first UE 300_1 to the MCU 302 can also be a level 2 bitstream. The session 306_2 between the second UE 300_2 and the MCU 302 can be negotiated to level 3 because that is the maximum computational capability level of the second UE 300_2. The bitstream 304_2 transmitted from the MCU 302 to the second UE 300_2 can be a level 2 bitstream. The third UE 300_3 is only capable of generating immersive rendering for received level 1 bitstreams. The session 306_3 between the third UE 300_3 and the MCU 302 can be negotiated to level 1 because that is the maximum computational capability level of the third UE 300_3. The bitstream 304_3 transmitted from the MCU 302 to the third UE 300_3 can be a level 1 bitstream. To accommodate this, the level 2 bitstream from the first UE 300_1 is transcoded (ordownmixed) to a level 1 bitstream at the MCU 302. The transcoded level 1 bitstream 304_3 is transmitted to the third UE 300_3. In this scenario, the user of the second UE 300_2 receives the highest quality of experience because level 2 is the maximum level that the first UE 300_1 can send. The user of the third UE 300_3 may have a slightly lowered quality of experience because the transcoding operations may reduce the rendering quality of the bitstream. The computational load at the MCU 302 is also increased due to the transcoding operations. Fig. 7 shows another example transmission scenario. This shows the same network as shown in Fig. 6. However in this example the negotiation parameter 400 indicates a passthrough mode and does not indicate a transcoding mode. As there is no transcoding mode the first UE 300_1 sends a level 1 bitstream 304_1 to the MCU 302. The MCU 302 then relays a level 1 bitstream 304_2 to the second UE 300_2 even though the session 306_2 between the second UE 300_2 and the MCU 302 is a level 3 session. The MCU 302 also relays a level 1 bitstream 304_3 to the third UE 300_3. The session 306_3 between the third UE 300_3 and the MCU 302 is a level 1 session. In the example of Fig. 7 the quality of experience of a user of the second UE 300_2 is not optimal because the bitstream level is lower than could be provided by the first UE 300_1 and rendered to immersive output by the second UE 300_2. However, the quality of experience of a user of the third UE 300_3 is optimal in this example. The example of Fig. 7 has a lower computational load for the MCU 302 compared to that shown in Fig. 6, because there is no need for transcoding operations. The transmission scenario shown in Fig. 7 could occur in the beginning of a communication session, for example, when the initially transmitted bitstream from the first UE 300_1 is of low complexity. The transmission scenario shown in Fig. 6 could also occur, if the first UE 300_1 is determined to have low battery, in which case the first UE 300_1 reduces the level of the transmitted bitstream to save battery life. Fig. 8 shows another example transmission scenario. This shows a similar network environment as shown in Figs. 6 and 7. In this example the negotiation parameter 400 indicates a passthrough mode and does not indicate a transcoding mode. In this example the UEs 300_1, 300_2, 300_3 can send multiple bitstreams. In the example of Fig. 8 the first UE 300_1 sends two bitstreams 304_1, 304_4 to the MCU 302. The first bitstream 304_1 is a level 1 bitstream and the second bitstream 304_4 is a level 2 bitstream. The MCU 302 then provides a level 2 bitstream 304_2 for the second UE and also provides a level 1 bitstream 304_3 for the third UE 300_3. The quality of experience of both a user of the second UE 300_2 and a user of the third UE 300_3 is optimal in this example. The computational load at the MCU 302 is not affected as there is no transcoding operations added there. The computational load at the first UE 300_1 is increased, because two bitstreams 304_1, 304_4 are created instead of one. The bitstreams 304_1, 304_4 could be created by two separate encoders at the first UE 300_ 1 or the lower level bitstream 304_1 could be obtained from the higher level bitstream 304_4 via transcoding or downmixing operations (in which case the third UE 300_3 may experience slightly reduced quality of experience). The total bitrate for the link between the first UE 300_1 and the MCU 302 is also increased because two bitstreams 304_1, 304_4 are transmitted instead of one. The transmission scenario shown in Fig. 8 could be used where the first UE 300_1 is a general broadcaster or a streaming provider, or any other suitable type of media sender that sends media to many end users. In such cases it may be beneficial for the first UE 300_1 to send multiple bitstreams to accommodate the different capabilities of the many devices of the end users. The decision to generate and send multiple bitstreams can be based on negotiation parameter 400 provided by the MCU 302 or other media receiver. Fig. 9 shows another example transmission scenario. This shows a similar network environment as shown in Figs. 6 to 8. In this example the negotiation parameter 400 indicates a passthrough mode and does not indicate a transcoding mode. In the example of Fig. 6 the bitstream 304_3 that is sent from the MCU 302 to the third UE 300_3 is transcoded from level 2 to level 1 at the MCU 302. The transcoding is performed to achieve higher immersion at the third UE 300_3, because the third UE 300_3 can provide higher immersive output for a received level 1 bitstream than for a level 2 bitstream. This is because the third UE 300_3 only has computational capability level 1. In the example of Fig. 9 the transcoding operation at the MCU 302 is disabled. The first UE 300_1 provides a level 2 bitstream 304_1 and the third UE 300_3 receives a level 2 bitstream 304_3. The third UE 300_3 can still decode this level 2 bitstream 304_3 (by IVAS levels definition), but it can only provide lower immersive output (for example, only mono or stereo). Such behavior may be useful in some cases because this can reduce computational resources at the MCU 302 or can simplify the relaying operations at the MCU 302. In some cases, the IVAS coded format of the bitstream may affect the decoding and rendering complexity of the incoming bitstream. For example, in general, MASA bitstreams are less complex to decode and render to binaural than other coded formats such as HOA3 bitstreams. Therefore, if the coded format of a session is negotiated and limited to only some formats (for example MASA), a UE may be able to decode and render the specific format bitstreams of higher levels into more immersive outputs than other format bitstreams of the same level. For example, in Error! Reference source not found., if the bitstream 304_3 received by the third UE 300_3 is a MASA bitstream of level 2, the third UE 300_3 may be able to decode and render the bitstream into binaural output even though the session 306_3 only indicates support for level 1. This format-specific decoding / rendering approach can be possible due to the IVAS levels definition. A UE might not be level 2 compliant, for example, because it does not support immersive output for all the IVAS formats (for example, due to significantly different complexities of different formats). However, the UE might be able to decode and render a specific format (for example, MASA) to any or at least the UE’s preferred immersive output (for example, based on availability of an output device such as head-tracked headphones). In the negotiation phase, this could be indicated by the UE by only requesting a specific format and a bitrate range that the UE can support to produce immersive output. For example, the UE can specifically request MASA at a higher level (bitrate). In this case the explicit level negotiation could be left out, or then the level negotiation would only consider the support for all formats and not for single formats. Additionally, the UE can indicate in the session negotiation that it does not want transcoded streams from the MCU 302. This could be achieved by negotiating the negotiation parameter 400 accordingly. For example, by negotiating that the parameter does not indicate a transcoding mode. If the MCU 302 has willingness or capability for a transcoding operation the MCU 302 could indicate this during the negotiation. For example, a negotiation parameter 400 of tf=transcoding or similar could be set during the negotiation by the MCU 302 to indicate that it can perform transcoding during the communication session. Fig. 10 shows another example transmission scenario. This shows a network environment comprising multiple MCUs 302_1, 302_2 and multiple UEs 300_1 to 300_3. In this example the network comprises two MCUs 302_1, 302_2 and three UEs 300_1 to 300_3. Other numbers of MCUs and UEs could be used in other examples. In this example the first UE 300_1 has computational capability level 3, the second UE 300_2 has computational capability level 3, and the third UE 300_3 has computational capability level 1. The first MCU 302_1 has computational capability level 1 and the second MCU 302_2 has computation capability level 2. The respective MCUs 302_1, 302_2 can provide negotiation parameters 400_1, 400_2. The negotiation parameters enable the UEs 300_1, 300_2, 300_3 to provide 28 bitstreams based on the computational capability level of the UEs 300_1, 300_2, 300_3 (media senders). This can enable the UEs 300_1, 300_2, 300_3 to provide bitstreams of a computational capability level that exceeds the computational capability level of the MCUs 302_1, 302_2. The negotiation parameters 400_1, 400_2 can be provided during the session negotiation. In this example the MCUs 302_1, 302_2 are media receivers. The first MCU 302_1 provides a first negotiation parameter 400_1 and the second MCU 302_2 provides a second negotiation parameter 400_2. In this case the negotiation parameters 400_1, 400_2 indicate that the respective MCUs 302_1, 302_2 can operate in a passthrough manner. In this example a first session 306_1 is established between the first UE 300_1 and the first MCU 302_1. A second session 306_2 is established between the first MCU 302_1 and the second MCU 302_2. A third session 306_3 is established between the first MCU 302_1 and the third UE 300_3. A fourth session 306_4 is established between the second MCU 302_2 and the second UE 300_2. All of the sessions are level 3 sessions except for the third session 306_3 which is a level 1 session. The levels or the sessions are set based on the levels of the respective UEs. A first bitstream 304_1 is provided from the first UE 300_1 to the first MCU 302_1. A second bitstream 304_2 is provided from the first MCU 302_1 to the second MCU 302_2. A third bitstream 304_3 is provided from the first MCU 302_1 to the third UE 300_3. A fourth bitstream 304_4 is provided from the second MCU 302_2 to the second UE 300_2. All of the bitstreams are level 3 bitstreams. In the example of Fig. 10 there is no level restriction between the first MCU 302_1 and the second MCU 302_2. If there was a restriction, for example if the session 306_2 was limited to level 2 because the second MCU 302_2 has level 2, this could negatively impact the performance of the network. For instance, the first MCU 302_1 might lower the bitstream 304_2 to level 2. The bitstream 304_2 could be lowered to level 2 by transcoding at the first MCU 302_1 or by requesting a lower level bitstream 304_1 from the first UE 300_1. However the second MCU 302_2 is only providing the bitstream 304_4 to the second UE 300_2 which has level 3 and so there is no need to lower the bitstream level. In the example of Fig. 10 the third UE 300_3 receives a level 3 bitstream 304_3 even though it is a level 1 device. The third UE 300_3 can still decode the level 3 bitstream 304_3 but the output may be less immersive. In complex network environments an MCU 302 can use passthrough and transcoding capabilities as part of complexity load management. For example, an MCU 302 can have a defined capability of transcoding a single level 2 bitstream or transcoding two separate level 1 bitstreams. In a multi-party conference or other similar communication session it can be possible for new participants to join the communication session. When new participants join the communication session the MCU 302 can negotiate the new session links based on the current status of the whole multi-party communication session. For example, if the maximum transcoding capability of the MCU 302 is already in use, the new participants might only be offered passthrough operation from the MCU 302 instead of offering both transcoding and passthrough. In this scenario, the complexity of the MCU 302 is prioritized in the multi-party communication session. In another scenario, the quality of experience or immersion for the participants in a multi-party communication session can be prioritized over the complexity of the MCU 302. For example, if there are multiple level 2 and multiple level 1 UEs, the level 2 bitstreams can always be set to be transcoded to level 1 participants to maximize the immersion for all participants. In either of the above scenarios, the negotiation parameters can be used to control the complexity load for the MCU 302 and for the UEs within the communication session and also to control the quality of experience for each participant. Fig. 11 shows an example transmission scenario where there is no MCU 302. Instead the second UE 300_2 is a split rendering entity. In this case the second UE 300_2 comprises a receiving device 1100 and a rendering device 1102. In the example of Fig. 11 the receiving device 1100 is a level 1 device. The receiving device 1100 could be a mobile phone or other similar lower level device. The rendering device 1102 in this example is a level 3 device. The receiving device 1100 controls the communication between the first UE 300_1 and the second UE 300_2. In this example the receiving device 1100 is a media receiver. The rendering device 1102 is the main rendering device for the second UE 300_2. The rendering device 1102 can be a higher level device with a higher level of computational capabilities compared to the receiving device 1100. For example, the rendering device 1102 could comprise a car with immersive audio presentation hardware, or any other suitable type of device. A first session 306_1 is established between the first UE 300_1 and the receiving device 1100. A second session 306_2 is established between the receiving device 1100 and the rendering device 1102. As shown in Fig. 11 the first UE 300_1 sends a bitstream 304_1 to the receiving device 1100. The receiving device 1100 pre-renders or performs any other suitable processing on the received bitstream 304_1 to generate a split rendering bitstream 304_2. The receiving device 1100 can then provide the split rendering bitstream 304_2 for the rendering device 1102. In order to benefit from the higher level of computational capabilities of the rendering device 1102 the first session 306_1 between the first UE 300_1 and the receiving device 1100 should not be limited by the low level of the receiving device 1100 because in the split rendering arrangement most or the majority of the calculations are performed by the rendering device 1102. To achieve this the media receiver can provide a negotiation parameter 400. The negotiation parameter enables the UEs 300_1, 300_2 to provide bitstreams based on the computational capability level of the UE 300_1 (media sender). For example, the negotiation parameter 400 can indicate a capability of the receiving device 1100 to operate in a passthrough or transcoding mode. The negotiation parameter 400 can be provided during the session negotiation. In this example the receiving device 1100 is the media receiver. In the example of Fig. 11 the negotiation parameter 400 indicates that the receiving device 1100 can operate in a passthrough manner. In this example the negotiation parameter 400 can have a form tf=split_rendering or similar to indicate the use of split rendering at the receiving device and to bypass the level restriction of the receiving device 1100. In this case the session 306_1 between the first UE 300_1 and the receiving device 1100 can be negotiated to level 2 because that is the maximum computational capability level of the first UE 300_1. The bitstream 304_1 transmitted from the first UE 300_1 to the receiving device 1100 can be a level 2 bitstream. The session 306_2 between the receiving device 1100 and the rendering device 1102 can be negotiated to level 3 because that is the maximum computational capability level of the rendering device 1102. The split rendering bitstream 304_2 transmitted from the receiving device 1100 to the rendering device 1102 can be a level 2 bitstream. The split rendering between the receiving device 1100 and the rendering device 1102 can be achieved in any suitable way. For example, in some cases the receiving device 1100 can be configured to decode and pre-render the level 2 bitstream 304_1 received from the first UE 300_1. This results in a level 2 split rendering bitstream 304_2 that the receiving device 1100 can then provide to the rendering device 1102. The rendering device 1102 can perform post-rendering based on the split-rendering bitstream for presentation. In some cases the receiving device 1100 can be configured to decode the level 2 bitstream 304_1 received from the first UE 300_1 and provide an external output signal to the rendering device 1102. The audio format of the external output signal can correspond to the audio input of the first UE 300_1. The rendering device 1102 then performs the final rendering for presentation. In some cases the receiving device 1100 provides the received level 2 bitstream 304_1 to the rendering device 1102 and the rendering device 1102 then both decodes and renders the bitstream for presentation. Fig. 12 shows an example method that can be used in some examples of the disclosure. This shows a method between a first UE 300_1 and an MCU 302. In this case the first UE 300_1 is a media sender and the MCU 302 is a media receiver. Other types of devices could be the media sender and the media receiver in other examples. In this case the first UE 300_1 has computational capability level 2 and the MCU 302 has computational capability level 1. This could be as shown in any of Figs. 3 to 11. At block 1200 the first UE 300_1 makes an SDP offer to the MCU 302. In the offer the first UE 300_1 indicates level 2 capability. The level 2 capability can be indicated via a level parameter in the SDP offer. At block 1202 the MCU 302 provides an answer to the SDP offer. In the answer, the MCU 302 indicates the capability of the MCU 302. The MCU 302 can also provide a negotiation parameter such as a tf-parameter (target format). The negotiation parameter enables the UE 300_1 to provide bitstreams based on the computational capability level of the UE 300_1 instead of being restricted by the computational capability level of the MCU 302. For example, the negotiation parameter 400 can indicate a capability of the MCU 302 to operate in a passthrough or transcoding mode. In the example of Fig. 12 the negotiation parameter could be set to passthrough which indicates that the MCU 302 is only passing through incoming bitstreams. This can indicate that the MCU 302 is not processing the bitstreams or only performs limited processing on the bitstreams. At block 1204 the first UE 300_1 accepts the answer from the MCU 302 and a session with level 2 capability is established between the first UE 300_1 and MCU 302. The use of the negotiation parameter allows the setting of the session between first UE 300_1 and MCU 302 to level 2. After the session has been established, RTP traffic can begin between the first UE 300_1 and MCU 302 at block 1206. Fig. 12 shows an example method between a first UE 300_1 and the MCU 302. Corresponding methods can also be performed between the other UEs and the MCUs within the network environment. Table 1 presents different SDP offer-answer scenarios between a UE (level 2) and an MCU 302 (level 1). In the initial offer, the UE indicates the support for level 2 and bitrates ranging from 13.2 kbps to 128 kbps for the session. Table 1 presents different answers for the MCU 302. In the first scenario (Answer 1), the MCU 302 is not negotiating passthrough or transcoding modes. Answer 1 indicates the supported level for the MCU 302 (level 1) and the maximum bitrate for the session (80 kbps, as limited by IVAS levels definition). There is no negotiation parameter 400 used in the Answer 1. This could reflect the session link between the first UE 300_1 and the MCU 302 in Error! Reference source not found., for example. In this example the session 306_1 is limited to level 1. In Answer 2, the MCU 302 indicates passthrough mode with the tf-parameter. In this case the level of the MCU 302 is indicated in the answer (level 1), but the passthrough indication is to be understood as to overrule the level limitation. Therefore, even though the answer indicates level 1, the UE can send higher level bitstreams (up to the limitation of the UE) because the tf=passthrough parameter is set. This indication that the UE can send higher level bitstreams is also present in the bitrate limits of the answer (up to 128 kbps), which is higher than the bitrates supported in level 1 (up to 80 kbps). Answer 3 is similar to Answer 2, but instead of indicating the level capability of the MCU 302 (level 1) in the answer, a lvl=* is indicated. This can be understood as “no restrictions” for the level from the MCU 302. This allows the UE to decide the level for the session. A similar approach is present in Answer 4, where the Ivl-parameter is removed from the answer. This can be understood as “no restrictions” for the level from the MCU 302 This allows the UE to decide the level for the session. In general, there may not be an explicit level parameter introduced for IVAS negotiation. In such cases the level can be implicitly determined from the other parameters, such as from the bitrate. For example, if the lvl=2 parameter is removed from the initial offer from the UE, the level could be determined from the offered bitrate (128 kbps), which is above 80 kbps (level 1 limit) but below 192 kbps (level 2 limit) and therefore the capability level of the UE can be determined to be level 2. Answers 2, 3 and 4 could be used in the example shown in Error! Reference source not found. 4 where the session 306_1 between the first UE 300_1 and the MCU 302 is negotiated to be level 2 and the MCU 302 is operating in passthrough mode. In Answer 5, the MCU 302 is indicating transcoding operation mode. This can be understood that the MCU 302 is capable and willing to transcode the incoming bitstreams when necessary (for example, when forwarding higher level bitstreams to lower-level UEs or other devices). This could also be understood that passthrough is additionally supported, as passthrough is generally less complex than transcoding. Answer 5 could correspond to, for example, Fig. 6 where the level 2 bitstream from the first UE 300_1 is transcoded by the MCU 302 to a level 1 bitstream 304_3 for the third UE 300_3. Example SDP Offer (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=2 Example SDP Answer 1 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-80, lvl=l Example SDP Answer 2 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=l, tf=passthrough Example SDP Answer 3 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=*, tf=passthrough Example SDP Answer 4 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, tf=passthrough Example SDP Answer 5 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=l, tf=transcoding Table 1 - Example offer-answer scenarios between UE and MCU where the UE initiates the offer. Table 2 presents another offer-answer example between a UE (level 3) and an MCU 302 (level 1). In the initial offer the UE indicates level 3 capability and all the bitrates 10 up to 512 kbps. In the answer, the MCU 302 indicates passthrough and transcoding modes. The transcoding is limited to level 2 bitstreams (transcoding_l2), which can be understood that bitstreams that are level 1 or level 2 can be transcoded by the MCU 302 if needed. For level 3 bitstreams, only passthrough mode is used. This could be the case, for example, to save computational resources at the MCU 302, because in general higher level bitstreams are more complex to transcode than lower level bitstreams. The transcoding limits could be indicated with transcodingjl (for up-to level 1 bitstreams), transcoding_l2 (for up-to level 2 bitstreams) and transcodingJ3 (for all level bitstreams). Example SDP Offer (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=3 Example SDP Answer (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, tf=passthrough,transcoding 12 Table -2 Example offer-answer scenario between UE and MCU for level 3 offer. Table 3 presents offer-answer examples between an MCU (level 1) and a UE (level 2), where the initial offer is made by the MCU 302. In Offer 1, the MCU 302 is not indicating passthrough or transcoding modes, and the bitrate for the session is therefore limited to MCU 302 capability level (level 1, up to 80 kbps). Answer 1 from the UE indicates a reply to Offer 1, where the offer is mirrored in the answer. This could reflect the session link between the first UE 300_1 and the MCU 302 in Fig. 3, for example, where the session is limited to level 1, if the MCU 302 initiated the offer-answer. Offers 2, 3, and 4 all indicate similar offers with varying Ivl-parameter syntax. In Offer 2 the Ivl-parameter is explicitly indicated in the offer (as lvl=1), in Offer 3 a lvl=* approach is used and in Offer 4 the Ivl-parameter is not included in the offer. In all of these approaches, the level of the MCU 302 in the offer should not be taken into account by the UE, because the offered tf=passthrough parameter indication overrules the MCU level. Additionally, this is indicated by the offered bitrate range, which covers all IVAS bitrates (up to 512 kbps). Answer 2 from the UE indicates a reply to Offers 2, 3 or 4, where the bitrate range is limited according to the UE (up to 128 kbps), and the capability level of the UE is explicitly indicated in the answer (lvl=2). The tf-parameter is removed from the answer as the offered tf=passthrough is an indication for the MCU operating mode and it does not need to be mirrored in the answer. If a tf=passthrough would be included in the answer, it could give implication that the UE is also using a passthrough mode. Answers 3 and 4 indicate replies to Offers 2, 3 and 4, where the UE also indicates their target format (IMMERSIVE1). In Answer 3, simply tf=IMMERSIVE1 is present in the answer to indicate the target format of the UE. In this case the tf=passthrough from the MCU is not included in the answer. In Answer 4, a directional variantof the tf-parameter is used, tf-recv parameter is used to indicate the target format of the receiver UE (IMMERSIVE1) and the tf-send parameter is used to mirror the target format of the MCU that was present in the offer (passthrough). Answers 2 and 3 could also be replies to Offers 5 and 6, where transcoding is offered. Answers 2, 3 and 4 could be used in the example of Fig. 4 where the session 306_1 between the first UE 300_1 and the MCU 302 is negotiated to be level 2 and the MCU is operating in passthrough mode, if the MCU initiated the offer-answer. Example SDP Offer 1 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-80, lvl=l Example SDP Offer 2 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=l, tf=passthrough Example SDP Offer 3 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=*, tf=passthrough Example SDP Offer 4 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, tf=passthrough Example SDP Offer 5 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=l, tf=transcoding Example SDP Offer 6 (from MCU to UE) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=l, tf=passthrough,transcoding 12 Example SDP Answer 1 (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-80, lvl=l Example SDP Answer 2 (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=2 Example SDP Answer 3 (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=2, tf=IMMERSIVEl Example SDP Answer 4 (from UE to MCU) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-128, lvl=2, tf-recv=IMMERSIVEl, tf-send=passttrough Table 3 - Example offer-answer scenarios between UE and MCU where the MCU initiates the offer. Table 4 presents an offer-answer example between two MCUs. In the initial offer from 5 a first MCU 302_1 (level 1), a passthrough operating mode is indicated, as well as the capability level of the first MCU 302_1. The bitrate is set to cover all IVAS bitrates (up to 512 kbps). The answer from the second MCU 302_2 (level 2) also indicates a passthrough mode, as well as the capability level of the second MCU 302_2. The bitrate is set to cover all IVAS bitrates (up to 512 kbps). In some cases, the Ivl-parameter could be left out from the offer-answers. The tf=passthrough in both offer and answer indicate the operating mode of the respective MCUs 302_1, 302_2. In the offer, the tf=passthrough indicates that the offerer, in this case first MCU 302_1 is operating in passthrough mode. In the answer, the tf=passthrough indicates that the answerer, in this case the second MCU 302_2, is operating in passthrough mode. In some cases, directional variants of the tf-parameter could be used (tf-send and tf-recv) to indicate the passthrough operation modes of the respective MCUs 302_1, 302_2. This offer-answer example could be used to establish the session 306_2 between the MCUs 302_1, 302_2 in Error! Reference source not found., for example. Example SDP Offer (from MCU1 to MCU2) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=l, tf=passthrough Example SDP Answer (from MCU2 to MCU1) m=audio 49152 RTP / AVP 96 a=rtpmap:96 IVAS / 16000 a=fmtp:96 br=13.2-512, lvl=2, tf=passthrough Table 4 - Example offer-answer scenarios between two MCUs. In some examples setting a negotiation parameter, such as the the tf-parameter, to “passthrough” or “transcoding” can be restricted only to MCU 302 or similar entities. That is, the related negotiation and session behaviors described herein would only be allowed for MCUs 302 and not for UEs or other end devices. In some examples split rendering devices, or any other devices, could also be configured to use the “passthrough” and “transcoding” values in a negotiation parameter. In some examples, the “passthrough” and “transcoding” modes could be indicated through other means. For example, separate SDP parameters could be introduced for both as PASSTHROUGH and TRANSCODING or similar. These SDP parameters could have values of 0 to disable and 1 to enable the respective operating mode. In some examples, “passthrough” could be named differently, for example, as “forwarding”, “forward”, “selective forwarding”, “sfu-mode” (selective forwarding unit), “bypass”, “relay” or any other suitable nomenclature could be used. In some examples, to avoid the level limitations introduced by an MCU 302, MCUs 302 could always be negotiated as level 3 (maximum capability) entities. In this approach the session links to any further devices would always be limited by the capabilities of the further devices and not the MCUs 302. On the other hand, this approach would not allow for the MCU 302 to negotiate level capabilities as the MCU 302 would always be indicated to support maximum capability. In some examples, the tf-parameter could be named differently, for example, as targetformat, output-format, of, relay-format, rf, intermediate-operating-mode, iom or any other suitable parameter. In some examples, the tf-parameter can be a declarative negotiation parameter. That is, in a session offer the tf-parameter declares the operating mode of the offerer to the answerer. In a session answer the tf-parameter declares the operating mode of the answerer to the offerer. Fig. 13 shows an example controller 1300. The controller 1300 could be provided within a media sender, a media receiver, or any other suitable entity that enables immersive communication sessions. Implementation of the controller 1300 may be as controller circuitry. The controller 1300 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware). The controller 1300 can provide an apparatus for implementing the disclosure of could be provided as part of an apparatus that implements the disclosure. As illustrated in Fig. 13 the controller 1300 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 1306 in a general-purpose or special-purpose processor 1302 that may be stored on a machine readable storage medium (disk, memory etc.) to be executed by such a processor 1302. The processor 1302 is configured to read from and write to the memory 1304. The processor 1302 may also comprise an output interface via which data and / or commands are output by the processor 1302 and an input interface via which data and / or commands are input to the processor 1302. The memory 1304 stores instructions, program 1306, or code that controls the operation of the apparatus when loaded into the processor 1302. The instructions, program 1306, or code provide the logic and routines that enables the apparatus to perform the methods illustrated in the Figs. The processor 1302 by reading the memory 1304 is able to load and execute the instructions, program 1306, or code. In some examples where the controller 1300 is provided within an apparatus such as a media sender, the controller therefore comprises means for: receiving 200 a negotiation parameter for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus within the immersive audio communication session; determining 202 a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus; and providing 204 the at least one bitstream with the determined computational capability level. In some examples where the controller 1300 is provided within an apparatus such as a media receiver, the controller therefore comprises means for: sending 210 a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and receiving 212 the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. The instructions, program 1306, or code may arrive at the apparatus via any suitable delivery mechanism 1308. The delivery mechanism 1308 may be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid-state memory, an article of manufacture that comprises or tangibly embodies the computer program 1306. The delivery mechanism may be a signal configured to reliably transfer the computer program 1306. The apparatus may propagate or transmit the computer program 1306 as a computer data signal. The term “non-transitory” as used herein, is a limitation of the medium itself that is, tangible, not a signal ) as opposed to a limitation on data storage persistency (for example, RAM vs. ROM). The computer program 1306 can comprise computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: receiving 200 a negotiation parameter for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to provide at least one bitstream based at least on a computational capability level of the apparatus within the immersive audio communication session; determining 202 a computational capability level for the at least one bitstream based at least in part on the negotiation parameter and the computational capability of the apparatus; and providing 204 the at least one bitstream with the determined computational capability level. The computer program 1306 can comprise computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: sending 210 a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and receiving 212 the at least one bitstream with a computational capability level based at least in part on the negotiation parameter. The computer program instructions may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine-readable medium. In some but not necessarily all examples, the computer program instructions may be distributed over more than one computer program. Although the memory 1304 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable and / or may provide permanent / semi-permanent / dynamic / cached storage. Although the processor 1302 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable. The processor 1302 may be a single core or multi-core processor. References to “computer-readable storage medium”, “computer program product”, “tangibly embodied computer program” etc. or a “controller”, “computer”, “processor” etc. should be understood to encompass not only computers having different architectures such as single / multi- processor architectures and sequential (Von Neumann) / parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry including quantum processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc. As used in this application, the term “circuitry” can refer to one or more or all of the following: (a) hardware-only circuitry implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device or server, to perform various functions and (c) any or all portions of hardware circuit(s) such as a microprocessor(s) and / or quantum processor(s) that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device. The blocks illustrated in the Figs, can represent steps in a method and / or sections of code in the computer program 1306. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block can be varied. Furthermore, it can be possible for some blocks to be omitted. Where a structural feature has been described, it may be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described. The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility. The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X may comprise only one Y or may comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning then it will be made clear in the context by referring to ‘comprising only one...’ or by using ‘consisting.’ In this description, the wording ‘connect’, ‘couple’ and ‘communication’ and their derivatives mean operationally connected / coupled / in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e., to provide direct or indirect connection / coupling / communication. Any such intervening components can include hardware and / or software components. As used herein, the term "determine / determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database, or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory), obtaining and the like. Also, "determine / determining" can include resolving, selecting, choosing, establishing, and the like. In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ‘example’ or ‘for example’ or ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some of or all other examples. Thus ‘example’, ‘for example’, ‘can’, or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible be used in that other example as part of a working combination but does not necessarily have to be used in that other example. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims. Features described in the preceding description may be used in combinations other than the combinations explicitly described above. Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not. The description of a feature, such as an apparatus or a component of an apparatus, configured to perform a function, or for performing a function, should additionally be considered to also disclose a method of performing that function. For example, description of an apparatus configured to perform one or more actions, or for 46 performing one or more actions, should additionally be considered to disclose a method of performing those one or more actions with or without the apparatus. Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not. The term ‘a’, ‘an’ or ‘the’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a / an / the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’, ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning. The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result. In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described. As used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or more” respectively. The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein above and which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such 5 alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure. Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance the Applicant may seek protection via the claims in 10 respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not emphasis has been placed thereon. l / we claim:
Claims
1. An apparatus for immersive audio communication comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least:sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; andreceiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter.
2. The apparatus of claim 1 wherein the negotiation parameter comprises an indication of a constraint based on a computational capability level of the apparatus.
3. The apparatus of any of claims 1 to 2 wherein the negotiation parameter is configured to enable a media sender to provide at least one bitstream with a computational capability level determined based at least on a computational capability level of the media sender within the immersive audio communication session4. The apparatus of any of claims 1 to 3 wherein the computational capability level for the at least one received bitstream exceeds the computational capability level of the apparatus.
5. The apparatus of any of claims 1 to 4 wherein the negotiation parameter comprises an indication of at least one of:a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender without transcoding;a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender without decoding;a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender with parsing or processing or extracting in a compressed domain;a passthrough mode of the apparatus indicating a capability of the apparatus to provide at least one bitstream from the media sender with lightweight processing that is less complex than decoding and / or transcoding; anda transcoding mode of the apparatus indicating a capability of the apparatus to receive at least one bitstream in a first format from the media sender and to provide a at least one transcoded bitstream in a second different format.
6. The apparatus of claim 5 wherein different formats comprise different one or more of:coded formats;bitrate;bitstream level;coded subformat;coded minor format;bandwidth;immersive / mono mode or format;number of channels; andsplit rendering operation.
7. The apparatus of any of claims 1 to 6 wherein the negotiation parameter is sent in a session negotiation offer for the immersive audio communication session.
8. The apparatus of claim 7 wherein the immersive audio communication session is established by:receiving an answer to the session negotiation offer from the media sender wherein the answer is based, at least in part, on the negotiation parameter; andestablishing the immersive audio communication session based on the answer.
9. The apparatus of any of claims 1 to 8 wherein the at least one processor and the at least one memory are also configured to cause the apparatus to perform:receiving a session negotiation offer for an immersive audio communication session from the media sender and:sending the negotiation parameter in response to the session negotiation offer.
10. The apparatus of any of claims 1 to 9 wherein the at least one processor and the at least one memory are also configured to cause the apparatus to perform negotiations with multiple media senders to cause the multiple media senders to participate in the immersive audio communication session.
11. The apparatus of any of claims 1 to 10 wherein the apparatus comprises at least one of:multiparty conferencing unit;selective forwarding unit;a receiving unit of a user equipment;intermediate network device.
12. The apparatus of any preceding of claims 1 to 11 wherein the media sender comprises a user equipment or the media sender is comprised within a user equipment.
13. A method comprising:sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter is configured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; andreceiving the at least one bitstream with a computational capability level based at least in part on the negotiation parameter.
14. A computer program comprising computer program instructions for causing an apparatus to perform at least the following or for performing at least the following:sending a negotiation parameter relating to a session negotiation for an immersive audio communication session wherein the negotiation parameter isconfigured to enable the apparatus to receive, within the immersive audio communication session, at least one bitstream with a computational capability level based at least in part on the negotiation parameter that exceeds the computational capability level of the apparatus; and5 receiving the at least one bitstream with a computational capability level basedat least in part on the negotiation parameter.
Citation Information
Patent Citations
ViewWO2025/039844A1onEspacenetopensinnewtab
ViewGB2631478AonEspacenetopensinnewtab
ViewWO2024/253459A1onEspacenetopensinnewtab
ViewUS11695826B2onEspacenetopensinnewtab
