Event notification

According to an example aspect of the present invention, there is provided an apparatus comprising at least one processing core, at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the apparatus at least to provide to a storage entity information relating to pairing an accessory with the apparatus, and determine an event and at least partly responsive to the event, notify the storage entity, the apparatus and/or the accessory of the event.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national phase entry of International Application No. PCT/EP2018/070983, filed Aug. 2, 2018, which claims priority to European Patent Application No. 17184887.2, filed Aug. 4, 2017, the entire contents of which are incorporated herein by reference.

FIELD

The present invention relates to management of notifications that relate to events, such as communication events or alarms.

BACKGROUND

User devices may be used with accessories, which may be engineered to enhance a utility a user may obtain from the user device, for example, headphones or ear plugs may be used with a cellular telephone to enable the user to use the telephone while jogging, driving a car or when otherwise unable or willing to hold the telephone to the user's ear.

SUMMARY OF THE INVENTION

According to some aspects, there is provided the subject-matter of the independent claims. Some embodiments are defined in the dependent claims.

According to a first aspect of the present invention, there is provided an apparatus comprising at least one processing core, at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the apparatus at least to provide to a storage entity information relating to use of an accessory with the apparatus, and determine an event and at least partly responsive to the event, notify the storage entity, the apparatus and/or the accessory of the event.

Various embodiments of the first aspect may comprise at least one feature from the following bulleted list:the at least one memory and the computer program code are configured to, with the at least one processing core, cause the apparatus to determine whether the accessory is of a first type, and to notify the storage entity if the accessory is of the first typethe event comprises an incoming call and the accessory comprises at least one of the following: headphones, ear plugs and a virtual reality headsetthe at least one memory and the computer program code are configured to, with the at least one processing core, cause the apparatus to query from the storage entity, whether the accessory or an another accessory is in use with a second apparatus, and to notify the storage entity if the accessory or the another accessory is in use with the second apparatusthe at least one memory and the computer program code are configured to, with the at least one processing core, cause the apparatus to notify the storage entity of at least one characteristic of the event.The information relating to use of the accessory with the apparatus may comprise information relating to pairing of the accessory with the apparatus.

According to a second aspect of the present invention, there is provided an apparatus comprising at least one processing core, at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processing core, cause the apparatus at least to notify a storage entity that the apparatus is using an accessory, receive from the storage entity an indication of an event relating to a second apparatus, and provide a sensory indication of the event via the apparatus, the accessory, or a combination thereof.

Various embodiments of the first aspect may comprise at least one feature from the following bulleted list;the at least one memory and the computer program code are configured to, with the at least one processing core, cause the apparatus to provide at least one characteristic of the event via the accessorythe event comprises an incoming call and the accessory comprises at least one of the following: headphones, ear plugs and a virtual reality headsetthe at least one memory and the computer program code are configured to, with the at least one processing core, cause the apparatus to provide contents of the event via the accessory, the contents being routed to the apparatus from the second apparatus.

According to a third aspect of the present invention, there is provided a method comprising providing to a storage entity information relating to use of an accessory with an apparatus performing the method, and determining an event and at least partly responsive to the event, notifying the storage entity, the apparatus and/or the accessory of the event.

Various embodiments of the third aspect may comprise at least one feature from the following bulleted list:determining whether the accessory is of a first type, and notifying the storage entity if the accessory is of the first typequerying from the storage entity, whether the accessory or another accessory is in use with a second apparatus, and notifying the storage entity if the accessory or the another accessory is in use with the second apparatus.

According to a fourth aspect of the present invention, there is provided a method comprising notifying a storage entity that an apparatus performing the method is using an accessory, receiving from the storage entity an indication of an event relating to a second apparatus, and providing a sensory indication of the event via the apparatus, the accessory, or a combination thereof.

According to a fifth aspect of the present invention, there is provided a method, comprising receiving, from a first apparatus, information relating to pairing an accessory with the first apparatus and receiving, from a second apparatus, an indication the second apparatus is using the accessory, receiving from the first apparatus a notification of an event relating to the first apparatus, and notifying the second apparatus the accessory, or a combination thereof of the event.

According to a sixth aspect of the present invention, there is provided a computer program configured to cause a method in accordance with at least one of the third, fourth and fifth aspects to be performed.

According to a seventh aspect of the present invention, there is provided an apparatus comprising means for providing to a storage entity information relating to use of an accessory with the apparatus, and means for determining an event and at least partly responsive to the event, notifying the storage entity, the apparatus and/or the accessory of the event.

According to an eighth aspect of the present invention, there is provided an apparatus comprising means for notifying a storage entity that the apparatus is using an accessory, means for receiving from the storage entity an indication of an event relating to a second apparatus, and means for providing a sensory indication of the event via the apparatus, the accessory, or a combination thereof.

According to a ninth aspect of the present invention, there is provided a non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least provide to a storage entity information relating to use of an accessory with the apparatus, and determine an event and at least partly responsive to the event, notify the storage entity, the apparatus and/or the accessory of the event.

According to a tenth aspect of the present invention, there is provided a non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least notify a storage entity that the apparatus is using an accessory, receive from the storage entity an indication of an event relating to a second apparatus, and provide a sensory indication of the event via the apparatus, the accessory, or a combination thereof.

According to an eleventh aspect of the present invention, there is provided a non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, cause an apparatus to at least receive, from a first apparatus, information relating to pairing an accessory with the first apparatus and receiving, from a second apparatus, an indication the second apparatus is using the accessory, receive from the first apparatus a notification of an event relating to the first apparatus, and notify the second apparatus, the accessory, or a combination thereof of the event.

EMBODIMENTS

The present invention is directed to conveying notifications via accessories that are not in use with the device determining an event that triggers the notifications. For example, a device may have previously been paired with an accessory capable of conveying a notification, but the accessory may, when the event occurs, be in use with a different, second, device. The devices may be correlated with each other via a storage entity, such as, for example, a cloud storage storing a subscription or account. The device determining the event may send a notification to the storage entity, which may be capable of notifying the second device. The second device may, in turn, notify the user via the accessory.

The inventor has realised that certain aspects of communication and operation may be improved upon. To this effect, the following describes several aspects and embodiments, which may be implemented in isolation or in combination with each other, for achieving the advantages described hereunder.

Accessories in general cover a wide range of devices designed for different purposes, for example, a detachable lens mechanism may enhance optical performance of a user camera, a virtual reality headset may enable virtual immersion of a surgeon into a blood vessel of a patient, based on image data obtained from a video sensor inserted in the blood vessel.

To enable interoperation of generic accessories with devices produced by a diverse set of manufacturers, industry standards have been developed. Such standards may define physical and/or operational characteristics of accessories that are to be capable of interoperation in accordance with these standards. For example, a standard headphone connection may define a 3.5 millimetre physical connector, as well as electrical characteristics of an audio signal that is to be provided via the physical connector. Other type connectors exist too.

Certain accessories enable notification of a user concerning an event. For example, when a user listens to a radio broadcast with headphones, the headphones may relay information concerning an incoming telephone call, in case the software radio is comprised in a cellular telephone apparatus. The user may handle the incoming call, and then return to the software radio broadcast, without removing his headphones. Likewise a user driving a car may receive and even initiate telephone calls or social media updates using a hands-free accessory, which may be voice-directed, for example, without letting go of the steering wheel.

FIG.1illustrates an example system in accordance with at least some embodiments. Device110, which may comprise, for example, a user device, user equipment, mobile phone, smartphone, tablet device, laptop computer, desktop computer or another suitable device, may be in wireless communication with base station120.

In some embodiments the user may have different devices registered as his own devices like one or more smart phones, laptops or tablets. The user may have a control or a limited control of some other smart phones, laptops or tablets or some other electronic devices which are registered in different accounts.

To achieve interoperability, mobile110and base station120may be configured to operate in accordance with a same communication technology, such as, for example, a cellular or non-cellular technology. Examples of cellular communication technologies include wideband code division multiple access, WCDMA, long term evolution, LTE, and fifth generation, 5G, also known as new radio, NR. Examples of non-cellular communication technologies include wireless local area network, WLAN, and worldwide interoperability for microwave access, WiMAX, technologies. However, in some embodiments, the base station may also operate under different radio access technologies, RATs, such as LTE and 5G.

Radio link112connects device110with base station120. Radio link112may be arranged in accordance with a same communication technology as device110and base station120, to achieve interoperability. As said, base station120, as well as device110, may be capable of communicating also with other communication technologies. The expression “base station” is a terminological choice by which it is not intended to limit the present disclosure to any specific technology. Depending on a communication technology used, the expression “access point” may be used alternatively to “base station”. The expression “access node” may comprise either a base station or an access point. Base station120may be a virtual base station, or function as a virtual base station.

Base station120is operably connected, via connection124, with network node141, which may comprise, for example, a mobility management entity, MME, switch or base station controller. Network node141may communicate with further networks via connection147, an example of such a network being provided in the system ofFIG.1as network170.

Although described herein in connection withFIG.1as a wirelessly connected device, in general device110may comprise, for example, a desktop computer with a wire-line Ethernet connection to the Internet. Such a desktop computer may receive, for example, incoming internet protocol telephony calls as events.

Accessory140may be, in the system ofFIG.1, in one of two positions, A or B. In position A, accessory140is in use with device110via connection114, and in position B, it is in use with unit150via connection154. Accessory140may comprise, for example, a headset, earplugs or a virtual reality headset. A headset, and likewise earplugs, is usable in emitting sound to the user's ear or ears, such that the user may listen to music, for example, without disturbing persons around him. A virtual reality headset enables at least partial immersion in a virtual landscape by providing a visual experience of being in the virtual landscape. A virtual reality headset may comprise an audio headset. A common factor in these three kinds of accessory is that they decrease the user's concentration in audio cues present in his surroundings. The virtual reality headset decreases the user's concentration also concerning visual cues, since the virtual landscape provided thereby obscures the real surroundings of the user. Connection114between accessory140and device110may comprise an electrically conductive wire or a low-power wireless connection, such as Bluetooth, BLE, or corresponding technologies, for example.

The system ofFIG.1further comprises a storage entity160. Storage entity160may comprise, for example, a cloud storage or cloud server farm configured to store account or subscription information. For example, a service provider providing or coordinating a device ecosystem may gather information on devices in use by a specific user, to facilitate access to a cloud data storage directory from different devices of the user, for example. A subscription account may be physically at storage entity160, for example. Transmitting information to storage entity160may thus comprise transmitting information for storage in the account of the user, the account comprising information of devices the user has in use. Storage entity160may communicate with device110via connection167and network170, and storage entity160may communicate with unit150via connection186, network180and connection158. Networks170and180may be optional, they may be the same network and/or storage entity160may be disposed in at least one of these networks.

When in use with device110, accessory140may be used by device110to notify the user concerning an event of device110, such as an incoming telephone call or social media update, for example. A further example of an event is a carbon monoxide alarm, in embodiments where device110is interfaced with an optional carbon monoxide sensor111. In general, the event may be determined in device110independently of other network nodes, as in the case of carbon monoxide or carbon dioxide level alarm, or the event may be determined in device110responsive to a signal received in device110from another network node, for example network node141, as in the case of an incoming call.

When in use with unit150, accessory140may be used to provide sensory inputs relating to operating unit150, which may comprise, for example, a gaming console or radio. Connection154between accessory140and unit150may comprise an electrically conductive wire or a wireless connection, such as Bluetooth, BLE, for example.

When initially paired with device110, accessory140may participate, together with device110, in generation of pairing information. Pairing information may comprise identifiers of paired devices and, optionally, encryption keys used, such that when the devices are subsequently used together, the initial pairing process need not be repeated, which facilitates using the accessory. Alternatively, device110may simply inform storage entity160that accessory140is paired or in use with device110.

Device110may provide the pairing information to storage entity160, which may store it in connection with an account of the user. When the user later uses accessory140with unit150, the pairing information may be retrieved from storage entity160, for example, to facilitate taking accessory140into use with unit150. Unit150may inform storage entity160that accessory140is being used with unit150, when accessory140is being used with unit150.

As accessory140is used with unit150, the user may have a reduced concentration to receiving notifications from device110. For example, an audible alarm from device110may be difficult to hear over a sound level produced by earplugs used with unit150. Thus the user may miss events that are notified by device110.

Device110may be configured to notify storage entity160of an event in device110. Storage entity160may, responsive to the notification from device110, determine whether an accessory140is in use with another device than device110, and responsive to a determination in storage entity160that accessory140is in use with unit150, storage entity160may notify unit150concerning the event in device110.

The notifications from device110and from storage entity160may comprise information concerning the event, for example, at least one characteristic of the event. Such a characteristic may comprise an event type and/or data concerning the event. For example, the characteristics may comprise an event type “Alarm” and associated data “carbon monoxide”. Another example is an event type “Incoming call”, which may be accompanied by a caller-ID of the calling party, and/or a picture of the face of the caller.

Unit150may be configured to notify the user, via accessory140, responsive to the notification from storage entity160. For example, in case of carbon monoxide alarm, an alarm sound may be played, accompanied by a spoken notification “Carbon monoxide danger”. As another example, a spoken notification “Your phone is ringing, Joe is calling” may be provided. As a yet further example, an e-mail message incoming in an email account associated with device110may be notified using a same audio signal as device110uses to notify an incoming e-mail.

In some embodiments, device110is configured to query, for example responsive to determining the event, from storage entity160, whether accessory140, or more generally any accessory, is in use. Device110may then be configured to notify storage entity160responsive to an indication from storage entity160that an accessory is indeed in use.

In some embodiments storage entity160may have a status information of the accessory140, for example in the form “in use” or “free”. In other embodiments storage entity160may have also information that accessory140is in use with unit150. In yet further embodiments the storage entity160can have information about the time stamp of last used of accessory140and by which device, such as, for example, unit150, used at that time. That might help user to find accessory faster. That information can be shown in connection with a call to or from device140or by a request of the device140as a way of notification, icon or so.

In some, embodiments, device110will refrain from notifying storage entity160of the event in case device110has not been paired with an accessory of a first type in the past. In other embodiments, device110is configured to attempt to find out, if an accessory of the first type is in use with another device of the user regardless of whether one has been in use with device110before.

The first type may comprise a type which decreases a user's concentration in audio and/or video cues present in his surroundings, for example. Accessories may comprise, in an identifying data field, an indication as to whether they are accessories of the first type. This indication may be provided to device110and/or unit150when the accessory is taken into use with them. The indication may be provided onward to storage entity160in connection with informing the storage entity the accessory is in use, to enable the storage entity to advise other devices that an accessory of the first type is in use, and/or in deciding whether to provide a notification to a specific device. In detail, the storage entity may be configured to decide to notify a device that is using an accessory of the first type.

In some of these embodiments, device110will refrain from notifying storage entity160of the event in case device110is currently using the accessory of the first type with which it has been paired.

In some embodiments, device110is configured to query, for example responsive to determining the event, from storage entity160, whether an accessory of the first type is in use by the user, and to notify storage entity160of the event responsive to being informed that an accessory of the first type is in use by the user. Thus the accessory that is in use need not necessarily be one that has been paired with device110in the past.

In some embodiments, device110is configured to notify storage entity160without querying from storage entity160responsive to the event. For example, device110may notify storage entity160simply responsive to the event occurring at a time when the user is not using an accessory of the first type with device110itself.

Once storage entity160has been notified by device110, it may decide on a further apparatus, such as unit150, to notify. In detail, storage entity160may decide to notify a further apparatus that is using an accessory, for example an accessory of the first type. In case storage entity160cannot determine any suitable apparatus to notify, it may discard the notification it has received from device110.

Device110may be configured to provide contents of the event to unit150, via storage entity160or by otherwise routing it. For example, storage entity160may, in addition to notifying unit150of the event, advise device110concerning an internet protocol address of unit150to enable device110to forward contents of the event to unit150. The internet protocol address may comprise an IPv4 or IPv6 address, for example. In detail, where the event is an incoming call, device110and unit150may be configured to route the call to unit150, such that accessory140is used with unit150to convey the call.

FIG.2illustrates example notifications. The notifications may be transmitted from device110ofFIG.1, for example. In some embodiments, storage entity160forwards the notifications it receives from device110to unit150, or in general to an apparatus that is using an accessory, such as, for example, an accessory of the first type. Notification201comprises two characteristics, event type210and event information220. As described above, the event type may comprise an incoming call and event information may comprise a caller identity.

Notification202comprises three characteristics, event type230, event information240and a media part250. Event type230may be similar to event type210and event information240may be similar to event information220. Media part250may comprise, for example, a media file, such as audio clip, the user of device110has selected for notifying an event of event type230. This enables the user to be notified of an incoming e-mail, for example, with the same chime as usually, from device110. Alternatively, in case the user is of impaired hearing and has configured device110to notify himself with a visual flash, unit150may provide the same visual flash, enabling successful notification. Media part250may comprise information describing the visual flash. Media part250may comprise an image of the face of the caller associated with a caller ID. In one embodiment, media part250may comprise an Internet address. In some embodiments media part250may comprise a request to open a chat or messaging window.

Storage entity160may comprise plural accounts of users. The users may be linked to send messages or video calls through one or more applications in devices110, or units150, when connected to a suitable communication network. Thus, for example, in case of incoming call which is notified by storage entity160, the storage entity may start an application for communication between users, that is, between a caller and a called person.

In some embodiments storage entity160may work together with other entities which are administrated by other entity owners. In one embodiment the interface between different storage entities may be interoperable to facilitate communication, for example, to exchange relevant user information.

FIG.3illustrates an example apparatus capable of supporting at least some embodiments. Illustrated is device300, which may comprise, for example, device110, unit150or, in suitable parts, a server of storage entity160ofFIG.1. Comprised in device300is processor310, which may comprise, for example, a single- or multi-core processor wherein a single-core processor comprises one processing core and a multi-core processor comprises more than one processing core. Processor310may comprise, in general, a control device. Processor310may comprise more than one processor. A processing core may comprise, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Steamroller processing core produced by Advanced Micro Devices Corporation. Processor310may comprise at least one Qualcomm Snapdragon and/or Intel Atom processor. Processor310may comprise at least one application-specific integrated circuit, ASIC. Processor310may comprise at least one field-programmable gate array, FPGA. Processor310may be means for performing method steps in device300. Processor310may be configured, at least in part by computer instructions, to perform actions.

Device300may comprise memory320. Memory320may comprise random-access memory and/or permanent memory. Memory320may comprise at least one RAM chip. Memory320may comprise solid-state, magnetic, optical and/or holographic memory, for example. Memory320may be at least in part accessible to processor310. Memory320may be at least in part comprised in processor310. Memory320may be means for storing information. Memory320may comprise computer instructions that processor310is configured to execute. When computer instructions configured to cause processor310to perform certain actions are stored in memory320, and device300overall is configured to run under the direction of processor310using computer instructions from memory320, processor310and/or its at least one processing core may be considered to be configured to perform said certain actions. Memory320may be at least in part comprised in processor310. Memory320may be at least in part external to device300but accessible to device300.

Device300may comprise a transmitter330. Device300may comprise a receiver340. Transmitter330and receiver340may be configured to transmit and receive, respectively, information in accordance with at least one cellular or non-cellular standard. Transmitter330may comprise more than one transmitter. Receiver340may comprise more than one receiver. Transmitter330and/or receiver340may be configured to operate in accordance with global system for mobile communication, GSM, wideband code division multiple access, WCDMA, 5G, long term evolution, LTE, IS-95, wireless local area network, WLAN, Ethernet and/or worldwide interoperability for microwave access, WiMAX, standards, for example.

Device300may comprise a local and/or near-field communication, NFC, transceiver350. Transceiver350may support at least one technology, such as NFC, Bluetooth, Bluetooth Low Energy or similar technologies. Device300may comprise more than one transceiver.

Device300may comprise user interface, UI,360. UI360may comprise at least one of a display, a keyboard, a touchscreen, a vibrator arranged to signal to a user by causing device300to vibrate, a speaker and a microphone. A user may be able to operate device300via UI360, for example to accept incoming telephone calls, to originate telephone calls or video calls, to browse the Internet, to manage digital files stored in memory320or on a cloud accessible via transmitter330and receiver340, or via transceiver350, and/or to play games. In one embodiment the user can be provided a notification regarding an incoming call or communication connection in the user interface, and the user may be provided a selectable option to accept or reject the call, and/or to initiate a request to change to another communication connection in the user interface.

Device300may comprise or be arranged to accept a user identity module370. User identity module370may comprise, for example, a subscriber identity module, SIM, card installable in device300. A user identity module370may comprise information identifying a subscription of a user of device300. A user identity module370may comprise cryptographic information usable to verify the identity of a user of device300and/or to facilitate encryption of communicated information and billing of the user of device300for communication effected via device300.

Processor310may be furnished with a transmitter arranged to output information from processor310, via electrical leads internal to device300, to other devices comprised in device300. Such a transmitter may comprise a serial bus transmitter arranged to, for example, output information via at least one electrical lead to memory320for storage therein. Alternatively to a serial bus, the transmitter may comprise a parallel bus transmitter. Likewise processor310may comprise a receiver arranged to receive information in processor310, via electrical leads internal to device300, from other devices comprised in device300. Such a receiver may comprise a serial bus receiver arranged to, for example, receive information via at least one electrical lead from receiver340for processing in processor310. Alternatively to a serial bus, the receiver may comprise a parallel bus receiver.

Device300may comprise further devices not illustrated inFIG.3. For example, where device300comprises a smartphone, it may comprise at least one digital camera. Some devices300may comprise a back-facing camera and a front-facing camera, wherein the back-facing camera may be intended for digital photography and the front-facing camera for video telephony. Device300may comprise a fingerprint sensor arranged to authenticate, at least in part, a user of device300. In some embodiments, device300lacks at least one device described above. For example, some devices300may lack a transceiver350and/or user identity module370.

Processor310, memory320, transmitter330, receiver340, transceiver350, UI360and/or user identity module370may be interconnected by electrical leads internal to device300in a multitude of different ways. For example, each of the aforementioned devices may be separately connected to a master bus internal to device300, to allow for the devices to exchange information. However, as the skilled person will appreciate, this is only one example and depending on the embodiment various ways of interconnecting at least two of the aforementioned devices may be selected without departing from the scope of the present invention.

FIG.4illustrates signalling in accordance with at least some embodiments. On the vertical axes are disposed, on the left, device110, in the centre, storage entity160and on the right, unit150, each ofFIG.1. Time advances from the top toward the bottom.

In phase410, a pairing of device110with an accessory is performed, generating pairing information. The accessory may be of the first type, for example. Device110provides the pairing information to storage entity160in phase420. Phases410and420are optional. In phase430, unit150informs storage entity160it is using an accessory of the first type, which may be the same one as was paired with device110in phase410, or a different one.

In phase440, device110determines an event that triggers notification. Device110may determine the need for notification of the event from user preferences configured in device110, in storage entity160, or in both, for example. User preferences may determine which types of event are notified. In optional phase450, device110may determine whether to attempt notification via storage entity160. For example, phase450may comprise device110querying from storage entity160, whether another device associated with the user is using an accessory of the first type, and in case this is the case, phase450may comprise deciding to attempt notification via storage entity160.

Phase460comprises notifying, by device110, storage entity160concerning the event. The notification may comprise characteristics as laid out above in connection withFIG.2, for example. Phase470may comprise storage entity160deciding whether to act on the notification of phase460, and if so, which device to notify. Based on the information received in storage entity160in phase430, it may be decided to notify unit150. Unit150is notified in phase480.

FIG.5is a flow graph of a method in accordance with at least some embodiments of the present invention. The phases of the illustrated method may be performed in device110, for example, or in a control device configured to control the functioning thereof, when installed therein.

Phase510comprises providing to a storage entity information relating to use of an accessory with an apparatus performing the method. The information relating to use of the accessory with the apparatus may comprise information relating to pairing of the accessory with the apparatus, for example. Phase520comprises determining an event and at least partly responsive to the event, notifying the storage entity the apparatus and/or the accessory of the event. Pairing information may comprise identifiers of the accessory and the apparatus and, optionally, encryption keys used in the pairing. The event may comprise a communication event, such as, for example, an incoming call. Alternatively, the event may comprise an alarm. An alarm may relate to, for example, carbon monoxide or smoke. The storage entity may comprise a cloud computing entity, for example. Notifying may comprise transmitting a notification which comprises at least one characteristic of the event.

FIG.6is a flow graph of a method in accordance with at least some embodiments. The phases of the illustrated method may be performed in unit150, for example, or in a control device configured to control the functioning thereof, when installed therein.

Phase610comprises notifying a storage entity that an apparatus performing the method is using an accessory. Phase620comprises receiving from the storage entity an indication of an event relating to a second apparatus. Finally, phase630comprises providing a sensory indication of the event via the apparatus, the accessory, or a combination thereof.

In some embodiments, after the event notification has reached a current device using the accessory apparatus, a connection between the current device using the accessory apparatus is stopped and/or the presentation of a current presentation is stopped. A connection between the accessory and the second apparatus may be established. This might facilitate avoiding a missed call. After the call has been finished, the operation with the apparatus may continue as it was before the event.

FIG.7is a flow graph of a method in accordance with at least some embodiments. The phases of the illustrated method may be performed in storage entity, for example, or in a control device configured to control the functioning thereof, when installed therein.

Phase710comprises receiving, from a first apparatus, information relating to pairing an accessory with the first apparatus and receiving, from a second apparatus, an indication the second apparatus is using the accessory. Phase720receiving from the first apparatus a notification of an event relating to the first apparatus. Finally, phase730comprises notifying the second apparatus, the accessory, or a combination thereof of the event.

FIG.8illustrates signalling in accordance with at least some embodiments. On the vertical axes are disposed on the left, device110, in the centre, storage entity160and unit150, and on the right, accessory140, each ofFIG.1. Time advances from the top toward the bottom.

Phase810illustrates an ongoing media stream, for example a music stream, from unit to accessory140. Phase820is a notification from device110concerning an incoming call as described herein above. Storage entity160notifies unit150concerning the call in phase830, responsive to which unit150queries from the user840, whether he will accept or reject the call. In the illustrated example the user accepts the call, responsive to which the music may be paused, for example, and a redirection process850may be performed. The user may participate in the call via accessory140in phase850. The redirection process may comprise conveying content of the call via a packet-based connection between device110and accessory140, for example. Thus unit150provides contents of the incoming call to the user via accessory140, the contents being routed to the apparatus from device110.

Once the call ends, the redirected connection of phase850may be disconnected, after which a connection860, similar to connection810, is built, or resumed, between unit150and accessory140. The media session of phase810is continued in phase870.

While an incoming call is used as an example of an event in connection withFIG.8, other kinds of events are also applicable.

FIG.9illustrates signalling in accordance with at least some embodiments. On the vertical axes are disposed on the left, device110, in the centre, storage entity160and unit150, and on the right, accessory140, each ofFIG.1. Time advances from the top toward the bottom. The signalling ofFIG.8relates to connection redirection, as was used in the process ofFIG.8, for example. Phase910comprises a disconnect, for example relating to the media session of phase810ofFIG.8. Phases920and930may comprise a notification of the disconnection being relayed to storage entity160and device110, respectively.

Phase940may comprise a request to create a connection for the redirection, for example a packet-based connection, such as real-time transport protocol, RTP, or transmission control protocol, TCP, connection, for example. The connection is established in phase950. Establishing the connection may comprise an end-to-end handshake and/or ciphering negotiation, for example.

Phase960comprises a notification of disconnection of the call, which may be conveyed over the connection of phase950, for example. Storage entity160is notified of the disconnection on phase970, and storage entity160may notify unit150of the disconnection in phase980. Phase980may comprise a “140disconnected” message, for example. The message of phase990may trigger re-establishment of a media session between unit150and accessory140, for example.

INDUSTRIAL APPLICABILITY

At least some embodiments of the present invention find industrial application in handling event notifications.

ACRONYMS LIST

5G fifth generation

BS base station

LTE long term evolution

NFC near field communication

NR new radio

RAT radio access technology

UE user equipment

WCDMA wideband code division multiple access

WiMAX worldwide interoperability for microwave access

WLAN wireless local area network

REFERENCE SIGNS LIST