Patent Description:
A conference session as described herein may be a communications session set-up between multiple devices, and therefore between users or parties associated with respective devices. At a time a conference session is invoked, or set-up, one or more communications channels may be established between the devices, possibly via a conference server. Thereafter, audio and/or video data may be transmitted between devices over the one or more established communications channels as part of the conference session that may be managed by the conference server. For example, in a conference session comprising first, second and third devices, audio and/or video data transmitted from the first device may be received and processed for output by each of the second and third devices in real-time or near real-time, and likewise audio and/or video data transmitted from, e.g. the linked user device, may be received and processed for output by each of the first and third devices in real-time or near-real-time.

A conference session may be an audio-only conference session or a videoconference session. In a videoconference session, video data may be captured by one or more cameras of a particular device and transmitted over the one or more established communications channels to the other devices for displaying the video data as a video feed. The video data may be accompanied by audio data captured by one or more microphones of the particular device.

<CIT> discloses a method and system for conducting a sub-videoconference from a main videoconference.

According to a first aspect, this specification describes an apparatus, as defined in claim <NUM>.

According to a second aspect, this specification describes a method, as defined in claim <NUM>.

Example embodiments will now be described, by way of non-limiting example, with reference to the accompanying drawings, in which:.

Example embodiments relate to apparatuses, methods and computer programs for enabling communications actions in, e.g. during, a conference session such as a videoconference session.

As described herein, a conference session may comprise one or more communications channels set-up between two or more devices over a communications network, and therefore between users or parties associated with the respective devices. A conference session may comprise, for example, one or more channels set up between two or more devices which are participants of the conference session, although their respective users may more commonly be referred to as the participants.

A device or user may be a host participant or an invited participant. The one or more communications channels may be established at the time of establishing the conference session to provide, typically, a multicast data feed from a given participant to each of the other participants in real-time or near real-time. The one or more communications channels may be bi-directional communications channels.

A device may comprise a user device, being a device operable by one or more users and configured to transmit and receive data over a communications network. The term "user device" will be used hereafter. The user device may comprise processing functionality for executing one or more applications, for example a conference application. The user device may also comprise one or more input modules and one or more output modules. For example, the user device may comprise one or more input transducers and one or more output transducers. For example, the one or more input transducers may comprise one or more microphones for converting sound waves to electrical signals which may be stored, processed and transmitted as audio data. For example, the one or more output transducers may comprise one or more loudspeakers for converting electrical signals into sound waves.

For example, the user device may also comprise one or more cameras for capturing video images which can be stored, processed and transmitted as video data. For example, the user device may comprise one or more displays, which may comprise any form of electronic display which may or may not be a touch-sensitive display. In the case of a touch-sensitive display, the display may also provide a form of input module, for example to receive and invoke selection commands based on detecting a touch input corresponding to a particular user interface element being displayed by the touch-sensitive display.

The user device may also comprise one or more other input modules, such as one or more of an accelerometer and gyroscope for generating motion data from which can be determined motion characteristics of the user device. The user device may also comprise one or more positioning receivers, such as a GNSS (Global Navigation Satellite System) receiver, for determining the geographic position of the user device.

A user device may comprise, but is not limited to, a smartphone, a digital assistant, a digital music player, a personal computer, a laptop, a tablet computer or a wearable device such as a smartwatch. The user device may be capable of establishing a communication session with one or more other user devices via a communications network, e.g. an audio or videoconference session. The user device may be configured to transmit and receive data using protocols for <NUM>, <NUM>, LTE, <NUM> or any future generation communication protocol. The user device may comprise means for short-range communications using, for example, Bluetooth, Zigbee or WiFi. The user device may comprise one or more antennas for communicating with external devices.

Referring to <FIG>, an example first user device is shown in the form of a smartphone <NUM>.

The smartphone <NUM> may comprise a touch-sensitive display (hereafter "display") <NUM>, a microphone <NUM>, a loudspeaker <NUM> and a front-facing camera <NUM>. The smartphone <NUM> may additionally comprise a rear-facing camera (not shown) on a rear side of the smartphone. The front-facing camera <NUM> may be enabled during, for example, enablement of a videoconference application whereby video data captured by the front-facing camera may be transmitted over an established videoconference session.

Also shown in <FIG> is another user device <NUM> which is linked to the smartphone <NUM>. Said other user device <NUM> is hereafter referred to as a "linked user device". In this context, the term "linked" means that the linked user device <NUM> comprises data communications functionality such that it may connect via, for example, one or more short-range communications channels to the first user device <NUM> using, for example, Bluetooth, Zigbee or WiFi as part of a local area network (LAN). In the context of Bluetooth, for example, the linked user device <NUM> may be "paired" with the first user device <NUM> in a conventional manner such that data may be transmitted between the first user device <NUM> and the linked user device <NUM>, and vice versa. However, it will be appreciated that other methods of establishing short-range communications channels may enable data transmissions between the first user device <NUM> and the linked user device <NUM>.

The linked user device <NUM> may comprise a wearable user device, such as a smartwatch or similar.

The term "linked" or "paired" in this context is not intended to imply that the linked user device <NUM> is the only device with which the first user device <NUM> can connect or link using short-range communications channels. Nor should the term "linked" or "paired" imply the necessity for a short-range communications channel for communications between the first user device <NUM> and the linked user device <NUM>. For example, each of the first user device <NUM> and the linked user device <NUM> may communicate with a server which may forward data from one of the devices to the other and vice versa.

The linked user device <NUM> may alternatively comprise one or more of another smartphone, a digital assistant, a digital music player, a personal computer, a laptop, or a tablet computer, to give some examples.

The linked user device <NUM> may comprise a display <NUM> which may or may not be a touch-sensitive display. The linked user device <NUM> may also comprise one or more microphones and/or one or more loudspeakers (not shown). The linked user device <NUM> may also comprise one or more cameras (not shown).

Referring to <FIG>, a videoconference system <NUM> is shown. It should be appreciated that example embodiments are also applicable to audio-only, e.g. voice-only, conference systems although example embodiments relate to the shown videoconference system.

The videoconference system <NUM> may comprise a first user device <NUM> (here, the smartphone of <FIG> is assumed to be the first user device), a second user device <NUM>, a third user device <NUM> and a conference server <NUM>. The first user device <NUM> is shown connected to the linked user device <NUM> using an established short-range channel <NUM>.

For the sake of illustration, the videoconference system <NUM> shown in <FIG> only comprises two remote devices, namely the second user device <NUM> and the third user device <NUM>, but the videoconference system may comprise any number of user devices involved in a videoconference session.

A first user <NUM> may use the first user device <NUM>, a second user <NUM> may use the second user device <NUM> and one (or more) third users <NUM> may use the third user device <NUM>. The user devices <NUM>, <NUM>, <NUM> may, as is typical, be in different remote places.

The second and third user devices <NUM> may comprise any of, for example, a smartphone, a digital assistant, a digital music player, a personal computer, a laptop, a tablet computer or a wearable device such as a smartwatch. The second and third user devices <NUM> may comprise the same or similar functionality to the first user device <NUM>, respectively comprising, for example, a display screen, one or more microphones, one or more loudspeakers and one or more front-facing cameras.

Each of the first, second and third user devices <NUM>, <NUM>, <NUM> may communicate streams of captured audio and video data with the other user devices via the conference server <NUM> as part of a conference session, in this example a videoconference session.

For example, the first user device <NUM> may communicate an audio stream and an accompanying video stream of the first user <NUM> talking, e.g. when the first user is facing the front-facing camera <NUM>. The audio and video streams may be transmitted over a first channel <NUM> established between the first user device <NUM> and the conference server <NUM>. The audio and video streams may then be transmitted by the conference server <NUM> to the second and third user devices <NUM>, <NUM> over respective second and third channels <NUM>, <NUM> using, or in the manner of, a multi-cast transmission protocol established between the conference server and the second and third user devices. Although the first, second and third channels <NUM>, <NUM>, <NUM> are represented by single lines, indicative of bidirectional channels, there may be separate channels, one for transmission and one for reception. The same principles of operation apply to the second and third user devices <NUM>, <NUM> when communicating audio and video streams as part of a videoconference session.

The conference server <NUM> may be configured to establish a conference session upon receipt of a request from one of the first, second or third user devices <NUM>, <NUM>, <NUM>. The request may identify the first user device <NUM> as a host device or participant and the second and third user devices <NUM>, <NUM> as invited user device(s) or participants. The conference server <NUM> may thereafter forward a signal to the second and third user devices <NUM>, <NUM>, inviting them to join the conference session. Upon acceptance by, for example, the second user device <NUM>, the second channel <NUM> may be established. The same process may apply to the third user device <NUM> for establishing the third channel <NUM>. One or more further user devices (not shown) may subsequently be invited to join the conference session.

The audio and video streams may comprise audio packets and associated video packets. The audio packets and the video packets may comply with any suitable conference standard, such as the Real Time Protocol (RTP). The audio packets and the video packets may, for example, comprise a packet header comprising control information and a packet body comprising the audio or video data content. The packet header may, for example, comprise a sequence number, which indicates the sequential position of a packet in a stream of transmitted packets. The packet header may also comprise a timestamp which indicates the timing of transmitting the packet. The packet body may comprise encoded audio or video data which was captured during a time slot before transmitting the packet. For example, video data of a packet may comprise a sequence of images representing encoded pixels and spatial coordinates.

Each of the first, second and third user devices <NUM>, <NUM>, <NUM> may comprise an apparatus such as that shown and described below with reference to <FIG>. Each of the first, second and third user devices <NUM>, <NUM>, <NUM> may be configured by means of hardware, software, firmware or a combination thereof to perform operations described below, for example with reference to <FIG>.

For ease of explanation, example embodiments will be described in relation to the first user device <NUM> which may be configured to perform operations based on execution of a conference application, e.g. a videoconference application.

The videoconference application, when executed by the first user device <NUM>, may be used by to establish a videoconference session via the conference server <NUM>, e.g. at a current time or at a future time, and to identify a list of participants for the videoconference session including the second and third user devices <NUM>, <NUM>. The videoconference application may also be used by the first user device <NUM> to join an existing videoconference session. The videoconference application may be stored on the first user device <NUM> or may comprise an applet or plug-in that is temporarily executed by the first user device upon connection to the conference server <NUM> via a web browser interface.

The videoconference application, when executed, may provide a user interface on a display of the first, second and third user devices <NUM>, <NUM>, <NUM> during a videoconference session.

For example, with reference to <FIG>, an example user interface <NUM> is shown on the display <NUM> of the first user device <NUM>.

The user interface <NUM> may comprise a plurality of display portions <NUM>, <NUM>, <NUM>. A first display portion <NUM> may show a video feed of the first user <NUM> i.e. video data captured by the front-facing camera <NUM>. In some example embodiments, the first display portion <NUM> may not be shown or may be disabled or removed by the first user <NUM>. A second display portion <NUM> may show a video feed of the second user <NUM> and a third display portion <NUM> may show a video feed of the one or more third users <NUM>. Audio data received from microphones of the second and third user devices <NUM>, <NUM> may be output via the loudspeaker <NUM> of the first user device <NUM>.

The user interface <NUM> may also comprise one or more interactive user interface elements (hereafter "UI elements") <NUM>, <NUM> corresponding to one or more conference actions.

For example, a first UI element <NUM> may correspond to a muting action, whereby selection of the first UI element causes the application to disable the microphone of the first user device <NUM> and/or prevents sending of audio data from the first user device to the second and third user devices <NUM>, <NUM> as part of the conference session. Re-selection of first UI element <NUM> may undo the muting action. For example, a second UI element <NUM> may correspond to a hang-up or leave action, whereby selection of the second UI element may cause the first user device <NUM> to leave the conference session.

<FIG> is another example user interface <NUM> which is similar to the <FIG> user interface save for the spatial arrangement of first, second and third display portions <NUM>, <NUM>, <NUM> (which may correspond to the first, second and third display portions <NUM>, <NUM>, <NUM> shown in <FIG>. ) For example, a background of the user interface <NUM> may comprise a map (not shown), and the spatial arrangement of the first, second and third display portions <NUM>, <NUM>, <NUM> may indicate in relation to the map where the respective first, second and third user devices <NUM>, <NUM>, <NUM> are located.

<FIG> is a flow diagram indicating processing operations that may be performed by the first user device <NUM> according to one or more example embodiments. As mentioned above, the processing operations may be performed by means of hardware, software, firmware or a combination thereof.

A first operation <NUM> may comprise communicating with a plurality of remote devices in a conference session.

A second operation <NUM> may comprise outputting, on a display, a user interface comprising a plurality of display portions respectively associated with the plurality of remote devices.

A third operation <NUM> may comprise receiving user selection of one or more of the remote devices.

A fourth operation <NUM> may comprise causing display of a display portion associated with the one or more selected remote devices on a linked user device which is linked to the apparatus. A fifth operation <NUM> may comprise enabling one or more communications actions for use with the one or more selected remote devices.

The fourth and fifth operations <NUM>, <NUM> may be performed in any order or simultaneously. In the case that the conference session is an audio-only conference session, each of the plurality of display portions may comprise some representation of the respective remote devices or their associated user(s). For example, each of the display portions may comprise a photograph, an icon or one or more initials associated with the respective remote devices or their associated user(s).

According to the invention, the conference session is a videoconference session, wherein the display portions comprise video feeds from the respective remote devices, e.g. a plurality of video feeds respectively associated with the plurality of remote devices.

In this way, the first user device <NUM> operates in what may be termed a "dual device mode" in which, a subset of the second and third user devices <NUM>, <NUM> currently connected to a conference session can be selected to enable one or more communications actions that may be specific to those selected device(s). Also, selection causes their respective video feed(s) to be displayed by the linked user device <NUM> to indicate which of the user devices are enabled for the one or more communications actions. This may also serve to free-up user interface space, which may become cluttered as more user devices participate in a videoconference session.

In terms of enabling or more communications actions for use with the one or more selected remote devices, this comprises enabling audio communications with the selected one or more remote user devices over a private communications channel which is not part of the conference session.

The term "private communications channel" refers to a channel which is established so that audio and/or video communications over the private communications channel are not sent to the non-selected user device(s) as part of the conference session.

Additionally, one or more UI elements may be enabled. The one or more UI elements may correspond to one or more other communications actions for the one or more selected remote devices, as distinct from those for the non-selected user device(s). The other communications actions may comprise, for example, a muting action and/or a hang-up or leave action.

Example embodiments will now be described in more detail with reference to <FIG>.

<FIG> shows the first user device <NUM> and the linked user device <NUM> as previously described with reference to <FIG>. The first user device <NUM> may be joined to a videoconference session with the second and third user devices <NUM>, <NUM> using the videoconference system <NUM> shown in <FIG>.

The first user device <NUM> may display a user interface <NUM> similar to that shown in <FIG>. The user interface <NUM> may comprise a plurality of display portions <NUM>, <NUM>, <NUM>. Optionally, a first display portion <NUM> may show a video feed of the first user <NUM> i.e. video data captured by the front-facing camera <NUM>. A second display portion <NUM> may show a video feed of the second user <NUM> and a third display portion <NUM> may show a video feed of the one or more third users <NUM>.

Audio data received from microphones of the second and third user devices <NUM>, <NUM> may be output via the loudspeaker <NUM>, or a connected earphones device, or similar, connected to the first user device <NUM>.

The user interface <NUM> may also comprise one or more UI elements <NUM> corresponding to one or more conference actions for the conference session, for example the muting and hang-up/leave actions described above with reference to <FIG>.

Selection of one of the second and third user devices <NUM>, <NUM> may be received via the user interface <NUM>.

For example, user selection of the third user device <NUM> may be received by means of a touch input, e.g. via a user's finger <NUM>, corresponding with the third display portion <NUM>. Alternatively, user selection may be received by means of a swipe input or any other predetermined gesture which corresponds with selecting a remote device for the purposes described herein.

For example, selection of the third user device <NUM> may be received by means of a swipe input substantially in the direction of the linked user device <NUM>.

Alternatively, or additionally, selection of the third user device <NUM> may be received by means other than a touch input. For example, selection of the third user device <NUM> may be by means of a voice command received by the first user device <NUM>, e.g. via the microphone <NUM> shown in <FIG>. For example, selection of the third user device <NUM> may be by means of detecting that the linked user device <NUM> is positioned proximate to the third display portion <NUM> on the user interface <NUM>.

It will be appreciated that the above-described methods for selecting the third user device <NUM> are applicable also for selecting the second user device <NUM> and indeed any other user device that may join the videoconference session.

Referring to <FIG>, it is seen that selection of the third user device <NUM> is effective to cause the third display portion <NUM> to be displayed on the display <NUM> of the linked user device <NUM>.

The third display portion <NUM>, when displayed on the display <NUM> of the linked user device <NUM>, may be identical to that displayed on the user interface <NUM> of the first user device <NUM>. However, in some example embodiments, the third display portion <NUM> may be modified for display on the display <NUM> of the linked user device <NUM>, for example to reduce or enlarge its size.

In some example embodiments, the third display portion <NUM> may also be removed from the user interface <NUM> of the first user device <NUM> to free-up space. Although not shown in <FIG>, the remaining first and second display portions <NUM>, <NUM> may automatically enlarge in response to removal of the third display portion <NUM>.

In response to selection of the third user device <NUM>, the first user device <NUM> may be configured to enable audio and/or video communications with the selected third user device over a private communications channel which is not part of the conference session. This means that audio and/or video data communicated over the private communications channel will not be received by the second user device <NUM>.

The private communications channel may be established automatically responsive to the received selection of the third user device <NUM>. Alternatively, further user input may be required to establish the private communications channel and/or to initiate communications over the private communications channel.

In response to selection of the third user device <NUM>, the videoconference application may also enable one or more UI elements <NUM> for display on the user interface <NUM> of the first user device <NUM>. The one or more interactive UI elements <NUM> may correspond to one or more other communications actions such as, for example, a muting action and/or a hang-up or leave action.

The one or more interactive user interface elements <NUM>, when selected, may be applicable only to communications with the third user device <NUM> over the private communications channel. For example, selection of a muting action via one of the UI elements <NUM> may mute audio data transmitted over the private communications channel. For example, selection of a hang-up or leave action via one of the UI elements <NUM> may end or terminate the private communications channel.

The one or more UI elements <NUM> may be distinguished from the other UI elements <NUM> associated with the videoconference session by means of, for example, a graphical indicator <NUM>. The one or more UI elements <NUM> may be displayed on the user interface <NUM> of the first user device <NUM> instead of on the display <NUM> of the linked user device <NUM> in order to take advantage of what is, generally, a larger display area meaning that the UI elements can be larger in size and therefore incorrect selections are avoided.

<FIG> is a block diagram indicating the videoconference system <NUM> of <FIG> after a private communications channel <NUM> is established between the first user device <NUM> and the third user device <NUM>.

The private communications channel <NUM> may be set-up via the conference server <NUM>, and may effectively comprise two channels with the conference server receiving data over a first channel and relaying the data over the second channel. Logically, however, they may be considered as one private communications channel <NUM>. Alternatively, the private communications channel <NUM> may be set up directly between the first user device <NUM> and the third user device <NUM>, for example via some other communications network.

At a time when the private communications channel <NUM> is enabled, the first user device <NUM> may be configured to detect a user input for initiating audio and/or video communications over the private communications channel. Based on detecting the user input, the first user device <NUM> may be configured to cause capture and sending of the audio and/or video data over the private communications channel <NUM>.

Different user inputs may be respectively associated with initiating only audio, only video, and audio and video communications over the private communications channel <NUM>.

For example, based on detecting a first user input for initiating only audio communications over the private communications channel <NUM>, the first user device <NUM> may be configured to cause capture of audio data by one or more microphones of the linked user device <NUM> for sending over the private communications channel.

The first user device <NUM> may also be configured to disable sending of the audio data as part of the conference session such that the captured audio data is not heard at the second user device <NUM>. The first user device <NUM> may also be configured to pause or disable sending of video data captured by, for example, the front-facing camera <NUM> of the first user device as part of the conference session. In this way, the second user <NUM> cannot see that the first user <NUM> is engaged in a private conversation with the one or more third users <NUM> nor lip-read part of the private conversation.

The first user input may be received via, for example, the user interface <NUM> of the first user device <NUM>.

Alternatively, or additionally, the first user input may be received based on an action at the linked user device, such as a detected motion of the linked user device <NUM>. The linked user device <NUM> may comprise one or more sensors, such as one or more of an accelerometer and gyroscope, for generating motion data which is receivable by the first user device <NUM> using the established short-range channel <NUM>. The first user device <NUM> may be configured to detect, from the received motion data, a determined motion of the linked user device <NUM> that corresponds to a predetermined gesture associated with the first user input. Alternatively, or additionally, a motion sensor of the first user device <NUM> may be configured to detect the determined motion of the linked user device <NUM>.

Alternatively, or additionally, the first user device <NUM> may be configured to determine a position of the linked user device <NUM> and to detect that the determined position corresponds to a predetermined position associated with the first user input. The position of the linked user device <NUM> may be determined using any known method. For example, if the linked user device <NUM> comprises a positioning receiver, positioning data generated by the linked user device may be transmitted to the first user device <NUM> using the established short-range channel <NUM>.

Alternatively, or additionally, if a distance between the linked user device <NUM> and the first user device <NUM> can be computed, positioning data generated by a positioning receiver of the first user device <NUM> can be modified using the computed distance to estimate the position of the linked user device. The distance between the linked user device <NUM> and the first user device <NUM> may be computed based on, for example, received signal strength indication (RSSI) signals or data.

In some example embodiments, the first user device <NUM> may be configured to detect that the linked user device <NUM> is within a predetermined distance d<NUM> of a user's mouth, i.e. that of the first user <NUM>. The predetermined distance may be in the order of <NUM> - <NUM> centimetres but may be varied using, for example, settings associated with the videoconference application. Detection may be based on one or a combination of the above-mentioned motion data and position data. Alternatively, or additionally, the first user device <NUM> may be configured to detect that the linked user device <NUM> is within the predetermined distance d<NUM> of the user's mouth based on the amplitude of audio signals received from the linked user device <NUM> being above a predetermined threshold.

Where the first user device <NUM> is configured to pause or disable sending of video data, this may occur prior to the linked user device <NUM> being within the predetermined distance d<NUM> of the user's mouth, for example by detecting a certain acceleration and/or direction of motion of the linked user device towards the user's mouth. This may avoid the second user <NUM> noticing that the communications channel <NUM> is about to be used.

<FIG> shows the above-described situation whereby the first user <NUM> moves the linked user device <NUM> to a position within a predetermined distance d<NUM> of their mouth for initiating audio communications over the private communications channel <NUM>. The first user <NUM> may continue to view video data associated with the ongoing conference session on the display <NUM> of the first user device <NUM>.

Alternatively, or additionally, based on detecting a second user input for initiating video communications over the private communications channel <NUM>, the videoconference application may be configured to cause capture of video data by one or more cameras of the linked user device <NUM> for sending over the private communications channel.

The second user input may be received via, for example, the user interface <NUM> of the first user device <NUM>. Alternatively, the second user input may be received based on any of the above-described motion and/or position based detection methods, provided it can be distinguished from the first user input.

<FIG> shows the above-described situation whereby the first user <NUM> provides a second user input for initiating video communications and may direct a camera of the linked user device <NUM> towards some object <NUM> that the first user wishes to show to the one or more third users <NUM> over the private communications channel <NUM>. The first user <NUM> may continue to view the ongoing conference session on the display <NUM> of the first user device <NUM>. The front-facing camera <NUM> of the first user device <NUM> may continue to provide video data as part of the videoconference session.

The first user device <NUM> may be further configured to cause capture of audio data by one or more microphones of the first user device (and/or the linked user device <NUM>) for sending over the private communications channel <NUM>.

For example, the first user device <NUM> may comprise an array of microphones, and the first user device may be configured to determine a position of the linked user device <NUM>, relative to the first user device, and to apply beamforming to the microphone array based on the determined relative position. In this way, the audio data which is communicated over the private communications channel <NUM> may comprise a directional component based on where the linked user device <NUM> is positioned relative to the first user device.

In some example embodiments, there may be received by the videoconference application selection of a plurality of remote devices.

For example, referring back to <FIG>, assuming there were further remote devices in the conference session and therefore further display portions displayed on the user interface <NUM>, the first user <NUM> may select, in addition to the third user device <NUM>, the second user device <NUM>. The first user device <NUM> may be configured, responsive to selection of the second and third remote user devices <NUM>, <NUM>, to cause either a simultaneous or sequential display of the second and third display portions <NUM>, <NUM> on the linked user device <NUM>, respectively associated with the second and third remote devices. <FIG> shows a simultaneous display of the second and third display portions <NUM>, <NUM> on the linked user device <NUM>.

If the first user device <NUM> is configured to cause a sequential display of the second and third display portions <NUM>, <NUM>, this may be performed by means of causing display, at a first time, of one of the second and third display portions, and subsequently, responsive to a user input received by the linked user device <NUM>, to cause display of the other of the second and third display portions. <FIG> show this sequential display wherein the third display portion <NUM> is first displayed (<FIG>), and then the second display portion <NUM> is displayed (<FIG>).

The user input received by the linked user device <NUM> may comprise, for example, a touch input on its display <NUM>, if touch sensitive, or a rotation of a bezel <NUM>, or any other suitable means of input.

In some example embodiments, the videoconference application may be configured to enable the one or more communication actions only for the selected user device which has its associated display portion displayed at a current time.

For example, with reference to <FIG>, the one or more communication actions such as communicating over said private communications channel <NUM> and/or enabling the muting or hang-up/ leave actions may only be used with the third user device <NUM>.

In some example embodiments, the first user device <NUM> may also be configured to receive a user input for a complementary, or switching selection of remote devices and, based on the received user input for a complementary selection, to cause (i) de-selection of one or more currently-selected remote devices such that their respective display portions are removed from the linked user device and the one or more enabled actions are disabled for said currently-selected remote devices, and (ii) to cause selection of currently non-selected remote devices such that their respective display portions are displayed on the linked user device and one or more actions are enabled for said currently non-selected remote devices.

With reference to <FIG>, for example, responsive to receiving a complementary selection, the third user device <NUM> may be de-selected and the second user device <NUM> may be selected and their respective display portions <NUM>, <NUM> swapped between the user interface <NUM> and the display <NUM> of the linked user device <NUM>. This may enable the first user <NUM> to toggle between different private conversations in a quick and seamless way.

Other communications actions that may be enabled for the selected subset of remote devices may include enabling recording of audio and/or video data communicated over the private communications channel <NUM>.

Example embodiments may enable a participant to a conference session, e.g. a videoconference, to select a subset of other participants to the conference session which may cause their respective display portions to be moved to a different, linked user device. This may free-up user interface space on the particular user device and may also enable one or more communications actions such as enabling or establishing a private communications channel such that user of the particular user device may converse or show information to one or more selected participants outside of the conference session. This may be in order to keep information secret and/or to avoid distracting the other, non-selected participants with irrelevant information. By showing display portions corresponding to the selected participant(s) on the linked user device, there is a clear separation between the participants. The selected participant(s) on the linked user device <NUM> may also be clearly visible compared with a potentially, much smaller display portion, if shown on the first user device <NUM> with a relatively large number of other participants.

<FIG> shows an apparatus according to an embodiment, which may comprise the first user device <NUM>, the linked user device <NUM>, and/or the second and third user devices <NUM>, <NUM>, or components thereof. The apparatus may be configured to perform the operations described herein, for example operations described with reference to any preceding process, including that of <FIG>. The apparatus comprises at least one processor <NUM> and at least one memory <NUM> directly or closely connected to the processor. The memory <NUM> includes at least one random access memory (RAM) 1301a and at least one read-only memory (ROM) 1301b. Computer program code (software) <NUM> is stored in the ROM 1301b. The apparatus may be connected to a transmitter (TX) and a receiver (RX). The apparatus may, optionally, be connected with a user interface (UI) for instructing the apparatus and/or for outputting data. The at least one processor <NUM>, with the at least one memory <NUM> and the computer program code <NUM> are arranged to cause the apparatus to at least perform at least the method according to any preceding process, including that of <FIG>.

<FIG> shows a non-transitory media <NUM> according to some embodiments. The non-transitory media <NUM> is a computer readable storage medium. It may be e.g. a CD, a DVD, a USB stick, a blue ray disk, etc. The non-transitory media <NUM> stores computer program code, causing an apparatus to perform the method of any preceding process, including that of <FIG>.

Names of network elements, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or protocols and/or methods may be different, as long as they provide a corresponding functionality. For example, embodiments may be deployed in <NUM>/ <NUM>/ <NUM>/ <NUM> networks and further generations of 3GPP but also in non-3GPP radio networks such as WiFi.

A memory may be volatile or non-volatile. It may be e.g. a RAM, a SRAM, a flash memory, a FPGA block ram, a DVD, a CD, a USB stick, and a blue ray disk.

If not otherwise stated or otherwise made clear from the context, the statement that two entities are different means that they perform different functions. It does not necessarily mean that they are based on different hardware. That is, each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software. Each of the entities described in the present description may be embodied in the cloud.

Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Some embodiments may be implemented in the cloud.

Claim 1:
An apparatus (<NUM>), comprising means for:
communicating with a plurality of remote devices (<NUM>, <NUM>) in a videoconference session;
outputting, on a display (<NUM>), a user interface (<NUM>) comprising a plurality of video feed display portions (<NUM>, <NUM>) respectively associated with the plurality of remote devices;
receiving user selection of one or more of the remote devices; and
based on the received user selection:
causing display of a video feed display portion associated with the one or more selected remote devices on a linked user device (<NUM>) which is linked to the apparatus, and
enabling one or more communications actions for use with the one or more selected remote devices over a private communications channel which is not part of the videoconference session by, responsive to detecting a user input for initiating audio communications over the private communications channel, causing capture of audio data by one or more microphones of the linked user device for sending over the private communications channel and to disable sending of audio data as part of the videoconference session.