Patent Description:
Communication within an enterprise environment (e.g. at companies, education sites, hospitals, entertainment locations, etc.) has changed and is moving away from location-specific behaviour where a dedicated local device with a specific phone or video calling number was present. Wireless connections enable an employee to have access to the digital infrastructure almost anywhere within or in proximity of the enterprise building. However, while this technology can offer freedom, many solutions result in a complex user workflow when a user wants to connect to the resources at the present location. In many cases it is required of the user to book a meeting beforehand or to use a meeting room control panel in order to get access to the room resources, or to call a specific meeting room number to get connected.

The present invention can allow any enterprise room (for meetings, trainings, stage presentations, etc.) to become user centric with preferably very limited action from the user. Communication can be centralized e.g. within standardized Unified Communications (UC) system or tools environments, and using meeting rooms then becomes a different experience. Embodiments of the present invention can provide standardized and unified workflows to a collaboration environment. Hence, embodiments of the present invention may overcome at least one of the above mentioned deficiencies,.

For example, a user can walk into a room, be connected and start a UC meeting right from his laptop. Also, the users can augment their capabilities with that of the meeting room (e.g. resources such as a room display, camera, microphones, etc.). Thus, a user may use the room display to share locally, and use video and/or audio equipment to enhance communication quality in the meeting. By using embodiments of the present invention, sharing can be implemented both remotely and locally. The experience can be compared to what a user may have at his/her desk, so using room resources may not require any additional training or hurdles. Ultimately the user and his/her guests can enter a UC session in any room without having to follow or change pre-bookings, pre-configurations or other predetermined constraints.

Thus, when a BYOD (Bring Your Own Device) is brought within a beacon system range the detected proximity can trigger an automatic set-up of configuring the room resource to become an extended resource to the user/BYOD or the UC session.

Consequently, the connection to the room resources may also be automatically terminated when there is no more BYOD within the proximity range of the local network device (while the ongoing UC session does not need to be terminated). Hence, the user/BYOD could enter another meeting room and connect ad-hoc to a network device and corresponding room resources of that room. There is no need to pre-allocate rooms or resources or consult a calendar tool to collect information on participants, but the connection authorization is based on that at least one of the BYODs participating in a UC session, is located within the proximity range of a network device (beacon system).

Devices participating in a meeting can comprise BYODs located in the related meeting room, room resources in the meeting room and remote BYODs connecting via a UC (Unified Communications system or tools) session. There may also be BYODs inside the meeting room that are not connected to the UC session. Embodiments of the present invention allow to synchronize the connectivity status of the UC session between the UC session, a BYOD app and a network device app such that an action executed within the BYOD app can be subsequentially executed within the BYOD UC session. For example, a BYOD operator can request a sharing action by performing an action with the BYOD app (e.g. pushing an icon), the BYOD app can then automatically communicate this request to the UC client and trigger the launch of the sharing action within the UC session.

It is an objective of the present invention to provide a room for meetings, trainings, stage presentations, etc. and a method of operating the room so that collaboration becomes more user centric with preferably very limited action from the user.

This has the advantage of changing the way meeting rooms and meetings are perceived by the users. The collaboration becomes more efficient because the time consuming procedures to join an electronic meeting are reduced.

In one embodiment of the present invention there can be provided a method for joining a network device UC client to a UC session connected to at least one BYOD UC client, the network device and the BYOD each can comprise a beacon transmitter configured to periodically or continuously transmit a beacon signal, or a beacon receiver configured to receive the beacon signal within its range, so that they can exchange the beacon signal, the beacon signal having a range, the network device can comprise an ID, a network device application (app) and a UC client, and the BYOD can comprise a BYOD app and a UC client, the method can comprise the steps of bringing the BYOD and the network device within the beacon signal range so that the BYOD and the network device can exchange a beacon signal comprising the network device ID, and generate and register an authentication-ID key, the exchanged beacon signal can trigger the BYOD app and the network device app to configure a data channel between them, the configured data channel can trigger the BYOD app to check if the BYOD UC client is connected to a UC session, if so, the BYOD app can send an invitation comprising the authentication-ID key to the network device app instructing the UC client to connect to the UC session, the network device app can check if at least one BYOD app that has a configured data channel to the network device app is also in the UC session, if so, the network device app can accept the invitation and instruct the network device UC client to connect to the UC session.

This has the advantage that a BYOD can be joined to a UC session without first starting the UC session or starting a login procedure (possibly on an additional device) but the UC session information transfer is enabled in the connection procedure itself.

Additionally, the method can comprise a second BYOD, the network device and the second BYOD each can comprise a beacon transmitter configured to periodically or continuously transmit a beacon signal, or a beacon receiver configured to receive the beacon signal within its range, so that they can exchange the beacon signal, the beacon signal having a range, the second BYOD can comprise a second BYOD app and a second UC client,.

This has the advantage that a second BYOD user entering a meeting room can automatically be joined by merely walking into the meeting room. The UC session moderator does not need to invite the second person or BYOD.

Additionally, the network device and the BYOD can comprise a second beacon system having a range for proximity detection and comprising a beacon transmitter configured to periodically or continuously transmit a second beacon signal, the method can comprise bringing the network device and the BYOD within the range for proximity detection, the second beacon system can exchange a second beacon signal, which can trigger the transmitter of the first beacon system to periodically or continuously send out a first beacon signal during a limited amount of time or until a data channel has been configured between the network device and the BYOD.

This provides the possibility to not continuously transmit the warble (the first beacon signal).

Additionally, the method can comprise a step of registering a data channel between the BYOD and the network device which can be preceded by the BYOD confirming to connect with the network device.

This makes sure the BYOD connects to the correct network device.

Additionally, the BYOD can comprise a BYOD identity, and the method can comprise a step of registering a data channel, the method can comprise the BYOD app requesting authentication with the network device app for the BYOD identity.

Additionally, the method can comprise a step of registering a data channel, the method can comprise the network device computer program product generating and registering an authentication code with the BYOD identity.

Additionally or alternatively, the network device can be connected to a room resource having input and output signals, and the method can comprise the step of the network device app controlling the input and output signals of the room resource.

Additionally or alternatively, the BYOD app can adopt a BYOD app state and the BYOD UC client can adopt a BYOD UC client state, the method can comprise the step of the BYOD app bringing the BYOD UC client state equal to the BYOD app state.

This has the advantage that the BYOD operator may share content via a UC session or via local sharing but the same outcome will be obtained, e.g. that the content is shown on a room display.

Additionally, there can be another BYOD present of a third type, having a BYOD app and no BYOD UC client, the method can comprise when the network device is connected to a UC session, the BYOD app of the another BYOD of the third type can share content to the network device app, the network device app can share the content to the network device UC client which then can share the content in the UC session.

This enables a BYOD having no UC client to still participate in the UC call if the BYOD is located within a meeting room that has a network device connected to the UC session. The content can be shared in the UC session and the UC session can be shared via the room display.

In another embodiment of the present invention there is provided a system for joining a network device UC client to a UC session connected to at least one BYOD UC client, the network device and the BYOD each can comprise a beacon transmitter configured to periodically or continuously transmit a beacon signal, or a beacon receiver configured to receive the beacon signal within its range, so that they can exchange the beacon signal, the beacon signal having a range, the network device can comprise an ID, a network device app and a UC client, and the BYOD comprises a BYOD app and a UC client, if the BYOD and the network device are positioned within the beacon signal range, there can be an exchange of a beacon signal between the network device and the BYOD, wherein the beacon signal can comprise a network device ID and a corresponding authentication-ID for authorizing the BYOD UC client to connect to the UC session.

The system enables a procedure where a BYOD can be joined to a UC session without first starting the UC session or starting a login procedure (perhaps on an additional device) but the UC session information transfer is enabled in the connection procedure itself.

Additionally the system can comprise a second BYOD, the network device and the second BYOD each comprising a beacon transmitter configured to periodically or continuously transmit a beacon signal, or a beacon receiver configured to receive the beacon signal within its range, so that they can exchange the beacon signal, the beacon signal can have a range, the second BYOD can comprise a second BYOD app and a second UC client, the system can be configured to.

The system can enable a second BYOD user entering a meeting room to automatically be joined by merely walking into the meeting room. The moderator does not need to invite the second person or BYOD.

Additionally, the system can comprise a BYOD confirmation to connect to the network device and a registered data channel between the BYOD and the network device.

Additionally, the system can comprise the BYOD having a BYOD identity, and the system can comprise a registered data channel and a BYOD app request for authentication of the BYOD identity with the network device app.

Additionally, the system can comprise a registered data channel and the network device app can comprise an authentication code with the BYOD identity.

Additionally or alternatively, the system can comprise that the network device can be connected to a room resource having input and output signals which can be controlled by the network device.

Additionally or alternatively, the system can comprise the BYOD app having a BYOD app state and the BYOD UC client having a BYOD UC client state and the system can be configured to have the BYOD app bringing the BYOD UC client state equal to the BYOD app state.

Additionally, the system can comprise another BYOD of a third type having a BYOD app and no BYOD UC client, the system can be configured so that the network device can be connected to a UC session, content of the BYOD app of the another BYOD of the third type can be shared to the network device app, the content can be shared by the network device app to the network device UC client which can share the content in the UC session.

The system enables a BYOD having no UC client to still participate in the UC call if the BYOD is located within a meeting room that has a network device connected to the UC session. The content can be shared in the UC session and the UC session can be shared via the room display.

In another embodiment of the present invention there is provided a processing device comprising a processing unit, an operating system, a memory, and a beacon transmitter or receiver, the memory can comprise at least one pre-installed executable computer program product providing a communication protocol for communication between the processing device and a standard class of BYOD devices, the processing device can be configured to.

A computer program product can also be provided which when executed on a processing engine can perform any of the methods according to the present invention. A non-transitory storage means can be used to store the computer program product. The computer program product can be compiled for a processing engine in any of the electronic devices or is written in an interpretive language such as Java that runs on a virtual machine such as the Java virtual machine. The non-transitory signal storage medium can be for example, an optical disk (CD-ROM or DVD-ROM), a digital magnetic tape, a magnetic disk, a solid state memory such as a USB flash memory, a ROM, etc..

A "BYOD" (Bring Your Own Device) can be computational processing devices comprising laptops, mobile phones, smartphones, tablets, palm pads and the like. In the present context it may also include a stationary computer. The computational processing device has means for providing content that can be outputted on an internal or external display device.

In accordance with the present invention the term "network device" relates to a network enabled digital processing device such as a Personal Computer (PC) or a work station having some form of display of information such as a display screen or one or more of a projector or other visible, audio or tactile displaying device. A network device has a processing engine, i.e. digital processor such as an FPGA or a microprocessor, having e.g. a Central Processing Unit (CPU) and/or a Graphical Processing Unit (GPU) and memory as well as interfaces such as a serial port or a network interface. A network device in operation is connected to a network, can access this network and use the facilities of the network as well as having local capabilities, applications, functions etc. For example, a network device in a meeting room can control access and manipulation of resources connected to it. Example of such resources can be displays, loudspeakers, microphones, furniture, lighting, temperature, etc. The network can be a shared resource network such as a Local Area network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), or a data network such as the Internet or can include combinations of these.

A network device as used with respect to the present invention generally does not relate to hardware that only mediates data in a computer network such as gateways, routers, bridges, switches, hubs, repeaters, multilayer switches, protocol converters, bridge routers, pure proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, modems, ISDN terminal adapters, line drivers, pure wireless access points, networking cables and other related hardware.

A network device can make use of a Network Access Device (or NAD) being an electronic circuit that automatically connects the network device to a network such as a preferred network. A NAD is any device that, when connected to, provides access to a larger communication network of some sort.

"Unified Communications system or tools" or UC refers to audio or audio visual communications such as provided by "SkypeTM" or "SkypeTM for business". Such software can take over audio and/or visual data provided from a host processing device. Unified communication tool can be described as a collection of tools to do VOIP, (web) conferencing, shared whiteboarding, message exchange (e.g. chat), file transfer, or presence. Unified Communications system or tools can make use of a protocol- or standard defined or specific communication session or interaction, such as Voice-Over-Internet-Protocol ("VoIP), text or instant messaging (e.g., AIM, Blauk, eBuddy, Gadu-Gadu, IBM Lotus Sametime, ICQ, iMessage, IMVU, Lync, MXit, Paltalk, Skype, Tencent QQ, Windows Live Messenger™ or MSN Messenger™, Wireclub, Xfire, and Yahoo! Messenger™ email, Twitter (e.g., tweeting), Digital Service Protocol (DSP), and the like. Unified Communications system or tools can make use of video conferencing cloud service including a video conferencing node to allow one or more users located at the first video conferencing endpoint to communicate with one or more users located at the second video conferencing endpoint in a video conference.

UC can be implemented as central computer program products on one or more remote servers connected with local computational devices. Local computational devices can comprise a local computer program product (a so-called client) that can access a central UC. Thus, a "UC session" can run on the remote server and be accessed by one or more local "UC clients" which can hereby exchange content. In the present context the term "UC" also comprises variants such as e.g. "Unified Communications & Collaboration (UC&C), Unified Communications as a Service (UCaaS), Video conferencing solutions or similar solutions that allow audio and video communication both locally and remote.

A "beacon system" can comprise a beacon transmitter and a beacon receiver configured to send and receive a beacon signal. A beacon transmitter or transceiver is a device designed to attract attention to itself and/or its capabilities by means of sending wireless signals that can be read and parsed by any suitable transceiver or receiver within range or distance. Beacons can be low power transmitters that and unlike full communication with a base unit or station, do not need to carry traffic data. For example, pilot signals can operate as beacons, such pilots only transmitting in the pilot channel of a wireless telecommunication system. A beacon can transmit and receive signalling information including access requests and grants. Some beacons can also transmit and receive traffic data. For example a video stream captured by a camera associated with a network device can be sent to a mobile device over the beacon channel, or by other means such as over a network via the at least one server. Hence, if the beacon is reserved for signalling only this transfer of traffic, i.e. video stream) would not go via the beacon but via another wireless channel.

In any of the embodiments of the present invention it is specifically disclosed by this paragraph that a beacon can be a means for short distance communication, for example Bluetooth, Bluetooth Low energy, Near Field Communication, Zigbee, Li-fi.

A simple means for short distance communication related to proximity detection can be implemented with a loudspeaker (beacon transmitter) and a microphone (beacon receiver). The exchanged audio signal can be referred to as a "warble".

The proximity- or beacon range of a beacon system can be expressed in a distance and such range may additionally be limited e.g. by the walls of a room.

A software application or "app" can be a computer program product which is configured to handle exchange of data between devices in a digital or computerized system.

An app can be located on a remote application server and accessed via local clients. Apps can execute dedicated tasks on computerized devices.

A BYOD app, a network device app or a UC client can adopt a "state" related to e.g. connection- or sharing status. For example a BYOD app state or just BYOD state can be "not connected" to a network device, or it can be "connected" and "sharing UC content", etc.. The present invention allows to synchronize the connectivity and sharing status between a device app and a UC client on either type of device. For example, if content is shared from a BYOD app, the app automatically triggers the BYOD UC client to share the same content in a UC session. Since a room display can be participant in the UC session (via the network device UC client) and share its content to all participants in the UC session, both those participants within the meeting room and remotely located participants can receive the shared content.

A "media data stream" comprises visual and/or audible content, for example images, recorded videos, real-life camera streams, documents, etc., that can be inspected on any display device in a collaboration platform. Additionally or alternatively, a data stream may contain audio data or meta data such as keyboard and mouse events.

A "room" is a space inside a structure or building, e.g. usually, a room is separated from both other rooms and the outside by walls and a ceiling. Each room usually has a specified purpose, in the present case a meeting room or conference room, defined by its use and the equipment therein to achieve this purpose. A room can have a 15dB attenuation of wireless signals passing through the walls of the room.

In the present context, a user is an operator or person using a BYOD. For convenience, the following text may use a "room display" as example of a room resource, but the present invention is not limited hereto but can comprise any resource that can be controlled by a network device such as e.g. loudspeakers, video cameras, microphones, lighting, thermostats, projector devices, electronic white boards, room furniture, etc..

<FIG> shows an embodiment of the present invention comprising a confined space or room <NUM>. Inside the room <NUM> there is a BYOD <NUM> and a network device <NUM> which can control a room display <NUM>. The network device <NUM> can be connected to the room display <NUM> via channel <NUM>, which may be wireless or cabled. The BYOD <NUM> can comprise a beacon receiver <NUM> which can receive a beacon signal <NUM>. Further the BYOD <NUM> can comprise a UC client <NUM> which can be connected to an active UC session on a UC server <NUM>. The UC server <NUM> can be located elsewhere on an off-premise server (often "in the cloud").

The network device <NUM> can comprise a UC client <NUM> that can connect to a UC session at the UC server <NUM>. The network device <NUM> can further comprise a beacon transmitter <NUM> which can transmit the beacon signal <NUM>. The beacon transmitter <NUM> and beacon receiver <NUM> can be referred to as a beacon system <NUM> having a proximity range. The proximity range may be the largest value of the distance <NUM> that the transmitter and receiver can be separated and still exchange a signal. The largest value of the distance <NUM> may also be limited by the walls of a room. This can occur when the walls and ceiling of a room provide an attenuation of wireless signals such that the signal outside a room does not have sufficient energy for communications to be sustained. If a multiple of BYODs are participating in the UC session (the BYODs may be located within the room <NUM> or connecting remotely) it may be desirable to share the content of the UC session to the room display <NUM>.

It may also be desirable to share the content of the room display <NUM> to all participating BYODs. For example, if one participant is sharing to the room display <NUM> without using the UC session , it's advantageous if the all BYODs can also receive that content. This may be implemented by making the network device <NUM>, which the room display <NUM> is controlled by, participant of the UC session , so that content can be shared from the room display <NUM> to all participants, independent of the channel used to provide the content to the room display <NUM>.

The present invention comprises a software application or "app" in the form of a network device app <NUM> and a BYOD app <NUM>. The apps <NUM> and <NUM> can be configured to monitor and perform actions related to the exchange of data between the BYOD and the network device. The apps <NUM> and <NUM> can be configured so that certain data transfers can trigger the apps to perform an action. In this way the BYOD can receive necessary data for e.g. establishing a connection to a resource device, with limited need of input from the BYOD operator. The present invention can provide a user-centric approach where the environment can react to the presence of a BYOD and be configured to adapt hereto.

<FIG> shows a flow chart of an embodiment of the present invention describing the event of how to automatically join a network device (and hereby a room resource) to a UC session.

In step <NUM> the BYOD <NUM> is brought into the meeting room <NUM>. The beacon transmitter <NUM> can periodically or continuously send out a signal, for example a signal that cannot be perceived by human beings such as an ultrasound signal, e.g. a warble, a UV or infrared signal such as a diverse UV or infrared signal or an optical light signal which is modulated at such a high frequency that the human eye cannot detect it. The signal is broadcast within a room awaiting that a suitable receiver enters within the proximity or beacon range.

In step <NUM> the beacon system <NUM> detects that BYOD <NUM> and the network device <NUM> are located within the proximity or beacon range of the beacon system <NUM>. The proximity detection (e.g. comprising that a beacon signal has been received by the beacon receiver) can trigger the BYOD app <NUM> to connect with the network device app <NUM>. This step may be preceded by the BYOD app <NUM> receiving a confirmation to connect from the BYOD <NUM>, e.g. the user of the BYOD <NUM> may be requested to confirm that he/she wants to connect to the network device <NUM>. The event of connecting the BYOD app <NUM> with the network device app <NUM>, can trigger the BYOD app <NUM> to check if there's an active UC session connected to the BYOD UC client <NUM> (step <NUM>). If an active UC session is confirmed, the BYOD app <NUM> can send an invitation to the network device UC client <NUM> to join the UC session (step <NUM>). In step <NUM>, the network device app <NUM> can check for each BYOD connected to it if at least one of the connected BYOD also have a UC client connected to the UC session. (If a UC session has no BYODs in a room, there is no use connecting the room display or other room resource to the UC session. ) If this is confirmed, the network device app <NUM> accepts the invitation to join the UC session (step <NUM>). With the procedure described in <FIG>, the room display <NUM> can be made available as participant so that any content displayed on it can be shared to all participants in the UC session. This is independent of how the content was provided to the room display <NUM>.

It would be possible to have a local BYOD, which is not connected to the UC session, in the meeting room of a network device. The network device (and related room resources) could be connected to a UC session via a remote BYOD which is in the UC session. The local BYOD could connect locally to the room display (and other room resources) and hereby participate in the UC session without having a UC client.

<FIG> shows an embodiment of the present invention comprising rooms <NUM> and <NUM> within the same premise and a remote room <NUM>. All devices in <FIG> can transmit or receive a beacon signal and comprise a beacon transmitter or receiver respectively (c. <FIG>), however the latter have been left out for clarity. The room <NUM> comprises a network device <NUM> which can transmit a beacon signal <NUM>, and a network device app <NUM> and a UC client <NUM>. The BYOD <NUM> can receive the beacon signal <NUM>, and comprises a BYOD app <NUM>. The BYODs <NUM>, <NUM> can receive the beacon signal <NUM> and comprise a BYOD app <NUM>, <NUM> and a UC client <NUM>, <NUM>, respectively. Room <NUM> comprises a network device <NUM>, which can transmit a beacon signal <NUM>, a network device app <NUM> and a UC client <NUM>. The BYOD <NUM> can receive the beacon signal <NUM>, and comprises a BYOD app <NUM> and a UC client <NUM>. The remote room <NUM> comprises a BYOD <NUM> which in turn comprises a UC client <NUM>. All device apps <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> communicates with one or more servers hosting the application cloud <NUM> via a signalling channel <NUM>, which can comprise a LAN, Wireless or any similar network. Each UC client can connect to a UC session (not shown) on the UC server, and communicates with a UC server <NUM> via a UC channel <NUM>, which can comprise LAN, Wireless or any similar network. Content, such as media data streams, can be shared among the BYODs via a data stream channel <NUM> which can comprise LAN, Wireless or any similar network.

<FIG> shows a flow chart of an exemplary embodiment of the present invention comprising the different actions carried out by a BYOD operator <NUM>, the BYOD <NUM> (from <FIG>), the network device <NUM> (from <FIG>) and a UC server <NUM> during a connection scenario. For this case there is not yet any other BYOD connected to the network device <NUM>. While the flow chart in <FIG> gives an overview, the present flow chart emphasizes the interaction between the different devices.

The BYOD <NUM> and the network device <NUM> each comprises a beacon system <NUM> and an app <NUM> and <NUM> respectively. The operator <NUM> and the BYOD <NUM> enters the room or location where the network device <NUM> is located, and turns on the BYOD <NUM>. The beacon systems sends out periodically or continuously a beacon signal, for example a signal that cannot be perceived by human beings such as an ultrasound signal, e.g. a warble, a UV or infrared signal such as a diverse UV or infrared signal or an optical light signal which is modulated at such a high frequency that the human eye cannot detect it. In the present scenario, the beacon system can comprise a loudspeaker on the network device <NUM> for periodically sending out a sound signal such as an ultrasound signal e.g. a warble <NUM> which can be detected by the BYOD <NUM> via its app in step <NUM>.

Alternatively there can be a second beacon system for proximity detection present which can detect that BYOD devices are located within its beacon range and trigger the network device to send out a warble with connection details (using the first beacon system). The warble could then be transmitted e.g. during a limited amount of time, or until all BYODs within the range of the proximity beacon system have connected to the network device. This solution provides the possibility to not continuously transmit the warble.

The BYOD <NUM> displays an invitation to the operator <NUM> to confirm that the BYOD <NUM> should be connected to the network device <NUM>. The operator <NUM> confirms the BYOD <NUM> should be connected (step <NUM>). The BYOD app connects to the network device <NUM> (step <NUM>), the network device <NUM> confirms the connection (step <NUM>). The user interface communicates the confirmed connection (step <NUM>). The operator <NUM> clicks on a UC call (or session) invitation displayed on the BYOD <NUM>, and the UC client requests the UC server <NUM> to start a UC session (step <NUM>), and the UC server <NUM> confirms the UC client of the BYOD <NUM> is connected to the UC session (step <NUM>). The app of the BYOD <NUM> detects the active UC session (step <NUM>), and this triggers the app of the BYOD <NUM> to invite the network device UC client to the connect to the UC session (step <NUM>). The UC client of the network device <NUM> request to the UC server <NUM> to connect to the UC session (step <NUM>), and the UC server <NUM> confirms the request (step <NUM>) and the network device <NUM> connects to the UC session (step <NUM>).

Once (the UC client of) the network device <NUM> is connected to the UC session, further BYODs can connect directly to the network device <NUM> via their UC clients. <FIG> illustrates an exemplary scenario hereof comprising a second operator <NUM> of a second BYOD <NUM>, and the same network device <NUM>. The second BYOD <NUM> and the network device <NUM> each comprises the same type of beacon system as in the scenario of <FIG>, and the second BYOD comprises a BYOD app.

The second operator <NUM> and the second BYOD <NUM> enters the room or location where the network device <NUM> and the BYOD <NUM> are located (step <NUM>), and turns on the second BYOD <NUM> (step <NUM>). The app detects the warble <NUM> of the beacon system (step <NUM>). The second BYOD <NUM> displays an invitation to the operator <NUM> to get confirmed that the second BYOD <NUM> should be connected to the network device <NUM> (step <NUM>). The operator <NUM> confirms the second BYOD <NUM> should be connected (step <NUM>). The BYOD app connects to the network device <NUM> (step <NUM>), the network device <NUM> confirms the connection (step <NUM>). The network device <NUM> sends the UC session details to the second BYOD app (step <NUM>), which starts the BYOD UC client (step <NUM>) and connects to the UC session.

<FIG> shows flow charts <NUM> and <NUM> of embodiments of the present invention where the UC client of a BYOD is initially connected to a UC session and the BYOD is connected to a network device and where the BYOD disconnects from the UC session or disconnects from the network device.

The flow chart <NUM> illustrates a scenario when one BYOD leaves the beacon range so that the connection to the network device is broken, or closes the connection to the UC session (step <NUM>), but there is still another BYOD within the beacon range connected to the network device. The UC client stops accessing the UC session (step <NUM>). The stopped call is detected by the BYOD app (<NUM>) and the BYOD app disconnects the BYOD from the network device (<NUM>).

The flow chart <NUM> illustrates a scenario when the last BYOD within the beacon range moves out of the beacon range. The BYOD app detects that the BYOD is no longer within the range (step <NUM>). The BYOD app disconnects the BYOD from the network device (step <NUM>) and the network device UC client disconnects from the UC session (step <NUM>).

<FIG> show state diagrams of embodiments of the present invention. In each state diagram, the black dot is the start point and each arrow is an event. A rectangular block represents the state of the device after an event; several events can lead to the same state. A diamond symbol represents a point of choice where several events can be possible, often depending on the environmental conditions.

In the text describing <FIG>, the simplified expression "join a UC session" will be used for a BYOD or a network device. This can comprise (as described in <FIG> and related text):.

A BYOD or a network device can "leave a UC session" by no longer accessing the UC session.

Further, the "beacon range" is the range of the beacon system, described in <FIG> and related text. "Local content" is shared by means other than via the UC session. "UC content" is shared within the UC session.

The state diagram <NUM> in <FIG> shows possible states for a network device. At starting point <NUM> the network device app is started or activated <NUM> and goes to "ready" <NUM>. In event <NUM>, a BYOD can "join a UC session" when it is located within the "beacon range" of the beacon system. Alternatively, the BYOD has already joined a UC session and then enters the "beacon range" of the beacon system. Event <NUM> ends with a point of choice <NUM>, comprising the possibility of the BYOD to not share content <NUM> or to share content <NUM>. Both <NUM> and <NUM> lead to state <NUM> where the network device is connected to a UC session. State <NUM> comprises the sub-states of UC content "not shared" <NUM> or "shared" <NUM>. Additionally or alternatively, the BYOD can share "local content" <NUM> to the network device. Within state <NUM> there can be a change between sub-states <NUM> to <NUM>, for example via <NUM> where the BYOD stops sharing local content or UC content, or via <NUM> where the BYOD shares UC content via the UC session, or via <NUM> where the BYOD shares local content. From state <NUM>, the BYOD can leave the beacon range or "leave the UC session" <NUM> to end up in a point of choice <NUM>. If there is still a BYOD located within the meeting room <NUM>, the network device will remain in the UC session and state <NUM>. If there is no more BYOD located within the meeting room <NUM>, the network device UC client disconnects from the UC session and returns to "ready" <NUM>. If a BYOD is located within the meeting room and connected with the network device, which is in state "ready" <NUM>, the BYOD can share local content <NUM> to the network device, which adopts the state "content shared locally" <NUM>. If a connected BYOD stops sharing locally, or leaves the beacon range <NUM>, the network device returns to "ready" <NUM>. If a connected BYOD starts a call when located within the beacon range, or brings a call into the beacon range <NUM>, the network device goes to the point of choice <NUM>, described above.

The state diagram <NUM> in <FIG> shows possible states for a BYOD. At starting point <NUM> the BYOD is located outside a beacon range related to a network device. The BYOD app is started <NUM> and the BYOD adopts the state "not in meeting room" <NUM>. The BYOD can now be connected to the network device manually <NUM> and arriving at a point of choice <NUM>. Alternatively, the BYOD can enter within the beacon range <NUM> and adopt a "detected" state <NUM>. The BYOD can now be offered to connect to the network device and adopt sub-state "connection offered" <NUM>. The BYOD may ignore the offer and adopt sub-state "ignore" <NUM>, or the BYOD can accept the connection <NUM> and arrive at the point of choice <NUM>. From the state "ignore" <NUM> it is also possible for the BYOD to request a connection <NUM> in order to arrive at the point of choice <NUM>. The BYOD can leave <NUM> the detected state <NUM> and arrive at the state "not in meeting room" <NUM>. The point of choice <NUM> may comprise "no ongoing UC session" <NUM> whereby the BYOD will adopt the state of "connected" <NUM> and its substate "not sharing" <NUM>. Alternatively, there can already be an ongoing call that the BYOD joins <NUM> whereby the BYOD adopts the connected state <NUM> and its sub-state "shared UC session" <NUM>. From the "not sharing" <NUM>, the BYOD can share locally <NUM> and adopt "sharing locally" <NUM> and again stop sharing <NUM> and return to "not sharing" <NUM>. Alternatively, the BYOD can adopt the state of "shared UC session" <NUM> by starting from "sharing locally" <NUM> and start or join a UC session <NUM>, whereby the UC sharing can be given priority over local sharing so that the local sharing is stopped. Alternatively, starting from the BYOD "sharing locally" <NUM>, the network device can stop the local sharing from the BYOD and join a UC session <NUM> so that the content from the BYOD can now be shared via the UC session. Further, from the "not sharing" <NUM>, the BYOD can start a UC session or join an ongoing UC call (or session) and adopt "shared UC session" <NUM>. Alternatively, the network device can join an ongoing UC session <NUM> and adopt "shared UC session" <NUM>. From the "shared UC session" <NUM>, the BYOD can leave the UC session <NUM> and return to "ignore" <NUM>. From any of the "connected" <NUM> states, the BYOD can disconnect <NUM> from the network device and return to "ignore" <NUM> or the BYOD can be brought out of the beacon range <NUM> and return to the state "not in meeting room" <NUM>.

The state diagram <NUM> in <FIG> shows possible states for a BYOD which does not have a UC client installed. At starting point <NUM> the BYOD is located outside a beacon range related to a network device. The BYOD app is started <NUM> and the BYOD goes to state "not in meeting room" <NUM>. The BYOD can now be brought into the beacon range <NUM> and adopt the state "not sharing" <NUM>. If the BYOD leaves the beacon range, it will return to "not in meeting room" <NUM>. Alternatively, if the BYOD shares content locally <NUM> to the network device (which is not in a UC session) it can adopt the state "sharing locally" <NUM>. The BYOD can now stop sharing <NUM> (and another BYOD can start sharing) so it returns to the "not sharing" <NUM>. Alternatively, starting from "sharing locally" <NUM>, the BYOD can be brought out of the beacon range <NUM> and return to "not in meeting room" <NUM>.

Electronic devices e.g. network devices such as described with respect to embodiments of the present invention can be standalone digital processing devices or can be embedded in another device. Such devices or methods can use a digital processing engine to carry out functions. The processing engine preferably has processing capability such as provided by one or more microprocessors, FPGA's, or a central processing unit (CPU) and/or a Graphics Processing Unit (GPU), and is adapted to carry out the respective functions by being programmed with software, i.e. one or more computer programs. References to software can encompass any type of programs in any language executable directly or indirectly by a processor, either via a compiled or interpretative language such as Java. The implementation of any of the methods of the present invention can be performed by or assisted by logic circuits, electronic hardware, processors or circuitry which can encompass any kind of logic or analog circuitry, integrated to any degree, and not limited to general purpose processors, digital signal processors, ASICs, FPGAs, discrete components or transistor logic gates and similar.

Such devices may have memory (such as non-volatile memory, non-transitory computer readable medium, RAM and/or ROM), an operating system, optionally a display such as a fixed format display, ports for data entry devices such as a keyboard, a pointer device such as a "mouse", serial or parallel ports to communicate other devices, network cards and connections to connect to any of the networks. The software can be embodied in a computer program product adapted to carry out the functions itemised below when the software is loaded onto the controller and executed on one or more processing engines such as microprocessors, ASIC's, FPGA's etc. devices for use with any of the embodiments of the present invention can incorporate a computer system capable of running one or more computer applications in the form of computer software.

When the software is loaded onto the respective device or devices and executed on one or more processing engines such as microprocessors, ASIC's, FPGA's methods of embodiments of the present invention can be performed by one or more computer programs running on an electronic device by being loaded into a memory and run on or in association with an operating system such as Windows™ supplied by Microsoft Corp, USA, Linux, Android or similar. The electronic device can include a main memory, preferably random access memory (RAM), and may also include a non-transitory hard disk drive and/or a removable non-transitory memory, and/or a non-transitory solid state memory. Non-transitory removable memory can be an optical disk such as a compact disc (CD-ROM or DVD-ROM), a magnetic tape, which is read by and written to by a suitable reader. The removable non-transitory memory can be a computer readable medium having stored therein computer software and/or data. The non-volatile storage memory can be used to store persistent information that should not be lost if the computer system is powered down. The application programs may use and store information in the non-volatile memory.

When the software is loaded onto the respective device or devices and executed on one or more processing engines such as microprocessors, ASIC's, FPGA's the following functions are carried out:
joining a network device having a UC client to a UC session connected to at least one BYOD having a BYOD UC client.

When the software is loaded onto the respective device or devices and executed on one or more processing engines such as microprocessors, ASIC's, FPGA's the following functions are carried out:.

When the software is loaded onto the respective device or devices and executed on one or more processing engines such as microprocessors, ASIC's, FPGA's the following functions are carried out:
The network device and the BYOD can comprise a second beacon system having a range for proximity detection and comprising a beacon transmitter configured to periodically or continuously transmit a beacon signal, the method comprising bringing the network device and the BYOD within the range for proximity detection, the second beacon system exchanging a beacon signal, which triggers the transmitter of the first beacon system to periodically or continuously send out a beacon signal during a limited amount of time or until a data channel has been configured between the network device and the BYOD.

Claim 1:
A method for joining a network device having a standardized Unified Communications, UC, client to a UC session connected to at least one Bring Your Own Device, BYOD having a BYOD UC client, the network device and the BYOD each comprising a beacon transmitter configured to periodically or continuously transmit a beacon signal, the beacon signal having a range, or a beacon receiver configured to receive the beacon signal within its range, so that they can exchange the beacon signal,
the network device comprising an ID, a network device application (app) and the UC client, and the BYOD comprising a BYOD app and the BYOD UC client,
the method comprising the steps of
bringing the BYOD and the network device within the beacon signal range so that the BYOD and the network device exchange a beacon signal comprising the network device ID,
generating and registering an authentication-ID key,
the exchanged beacon signal triggering the BYOD app and the network device app to configure a data channel between them,
the configured data channel triggering the BYOD app to check if the BYOD UC client is connected to a UC session,
if so, the BYOD app sending an invitation comprising the authentication-ID key to the network device app instructing the network device UC client to connect to the UC session, the network device app checking if at least one BYOD app that has a configured data channel to the network device app is also in the UC session,
if so, the network device app accepting the invitation and instructing the network device UC client to connect to the UC session.