Subscriber node, internet protocol multimedia subsystem node, event subscriber node and methods in a communication network

Abstract

A method performed by a subscriber node for handling events in a communication network is provided The subscriber node receives (401) an event subscription request for subscribing to one or more event types. The event subscription request indicates an event category associated with the one or more event types. The subscriber node sends (403) the event subscription request to an Internet Protocol Multimedia Subsystem node.

Description

[0001] SUBSCRIBER NODE, INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM NODE,

[0002] EVENT SUBSCRIBER NODE AND METHODS IN A COMMUNICATION NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a subscriber node, an IMS node an event subscriber node and methods therein. In some aspects, they relate to handling events in a communications network.

[0005] BACKGROUND

[0006] Subscriber node, Internet Protocol Multimedia Subsystem node, event subscriber node and method in a communication network

[0007] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (ST A) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0008] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC). Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0009] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0010] In a service-based architecture, Network Function (NF) service providers may support subscriptions to expose relevant events to interested service consumers. When subscribed events are fulfilled, notifications, including relevant event data, are sent to the subscribing consumers. Such events are varied but are often in the context of a UE or in the context of Internet Protocol Multimedia Subsystem (IMS) subscriber, i.e., event is related to subscribe, for example “Subscriber-State”.

[0011] A network function service consumer interested in an event, sends a request to subscribe to the event. The request includes an event identification and a UE or subscriber identification.

[0012] Currently in 5GC, as outlined in TS 23.502 v18.4.0, a network function service consumer subscribes to an event of interest directly with the Network function producer supporting such an event or via Unified Data Manager (UDM) which subscribes on behalf of the service consumer to the relevant NF service producer. UDM in this instance having received such a subscription request needs to:

[0013] Find the NF type providing the event identified in the request. - Find the NF provider node instance which serves the UE or subscriber identified in the request.

[0014] The NF type identification is based on the event identity (ID). The NF supporting such an event is known to the service consumer due to pre-determined assignment of NF to event ID, see e.g., table 4.15.3.1-1 in TS 23.502 v18.4.0. For example: Loss of connectivity event is provided by Access and Mobility Management Function (AMF) in a 5GC network.

[0015] Table 4.15.3.1-1 : List of events for monitoring capability

[0016] The NF service provider node instance which serves the UE or subscriber identified in the subscription request is determined by using prior registration of bindings of UEs and / or subscriber identities to node instances addresses. This is, in the 5GC exposure paradigm defined in 3GPP TS 23.502 v18.4.0, this is determined based on the registration of NFs in UDM, e.g., AMF, SMF, for specific subscribers.

[0017] As part of an ongoing SA2 work item for NG-RTC studied in TR 23.700-77 v0.2.0, Key Issue #1 (Kl#1), similar mechanisms are being discussed to support subscription to and notification of IMS related events to NF service consumers from IMS based NF service providers. The mechanisms outlined in Kl#1 are referred to as an “IMS event exposure framework”.

[0018] SUMMARY

[0019] An object of embodiments herein is to improve the performance of a communication network by a more efficient and flexible event subscription.

[0020] According to an aspect of embodiments herein, the object is achieved by a method performed by a subscriber node for handling events in a communication network.

[0021] The subscriber node receives an event subscription request for subscribing to one or more event types. The event subscription request indicates an event category associated with the one or more event types.

[0022] The subscriber node sends the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node.

[0023] According to an aspect of embodiments herein, the object is achieved by a method performed by an Internet Protocol Multimedia Subsystem, IMS, node for handling events in a communication network.

[0024] The IMS node receives, from a subscriber node, an event subscription request for subscribing to one or more event types. The event subscription request indicates an event category associated with the one or more events to be monitored.

[0025] The IMS node sends, to an event subscriber node, a notification message. The notification message notifies the event subscriber node that an event corresponding to the event category has been triggered.

[0026] According to an aspect of embodiments herein, the object is achieved by a method performed by an event subscriber node for handling events in a communication network.

[0027] The event subscriber node sends, towards a subscriber node, an event subscription request for subscribing to one or more event. The event subscription request indicates an event category associated with the one or more event types.

[0028] The event subscriber node receives, from an Internet Protocol Multimedia Subsystem, IMS, node, a notification message. The notification message notifies the event subscriber node that an event corresponding to the event category that has been triggered.

[0029] According to an aspect of embodiments herein, the object is achieved by a subscriber node configured to handle events in a communication network.

[0030] The subscriber node is configured to receive an event subscription request for subscribing to one or more event types. The event subscription request is adapted to indicate an event category associated with the one or more event types.

[0031] The subscriber node is configured to send the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node.

[0032] According to an aspect of embodiments herein, the object is achieved by an Internet Protocol Multimedia Subsystem, IMS, node configured to handle events in a communication network.

[0033] The IMS node is configured to receive, from a subscriber node, an event subscription request for subscribing to one or more event types. The event subscription request is adapted to indicate an event category associated with the one or more events to be monitored.

[0034] The IMS node is configured to send, to an event subscriber node, a notification message. The notification message is adapted to notify the event subscriber node that an event corresponding to the event category has been triggered.

[0035] According to an aspect of embodiments herein, the object is achieved by an event subscriber node configured to handle events in a communication network.

[0036] The event subscriber node is configured to send, towards a subscriber node, an event subscription request for subscribing to one or more event. The event subscription request is adapted to indicate an event category associated with the one or more event types.

[0037] The event subscriber node is configured to receive, from an Internet Protocol Multimedia Subsystem, IMS, node, a notification message. The notification message is adapted to notify the event subscriber node that an event corresponding to the event category that has been triggered.

[0038] Embodiments herein target to handle events. The event subscriber node requests subscription to events by indicating, in an event subscription request, an event category associated with one or more events. A subscriber node receiving the request send the request to an IMS node associated with the one or more events.

[0039] Embodiments herein bring the advantage of an efficient and flexible mechanism for handling events and event subscriptions. This is achieved by introducing an event category framework, enabling an event subscriber node to subscribe to events by selecting an event category associated with one or more events, resulting in a more efficient and flexible event handling, resulting in an improved performance of the communication network.

[0040] BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0042] Figure 1 is a schematic diagram illustrating an event category framework according to embodiments herein.

[0043] Figures 2a-b shows examples according to embodiments herein.

[0044] Figure 3 is a schematic block diagram illustrating embodiments of a communications network.

[0045] Figure 4 is a flowchart depicting embodiments of a method in a subscriber node.

[0046] Figure 5 is a flowchart depicting embodiments of a method in an IMS node.

[0047] Figure 6 is a flowchart depicting embodiments of a method in at event subscriber node.

[0048] Figure 7 is a combined signalling diagram and flowchart according to embodiments herein.

[0049] Figure 8 is a schematic block diagram illustrating a non-limiting example of a subscriber node according to embodiments herein.

[0050] Figure 9 is a schematic block diagram illustrating a non-limiting example of an IMS node according to embodiments herein.

[0051] Figure 10 is a schematic block diagram illustrating a non-limiting example of an event subscriber node according to embodiments herein. Figure 11 shows an example of a communication system QQ100 in accordance with some embodiments.

[0052] Figure 12 shows a UE QQ200 in accordance with some embodiments.

[0053] Figure 13 shows a network node QQ300 in accordance with some embodiments.

[0054] Figure 14 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 11 , in accordance with various aspects described herein.

[0055] Figure 15 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.

[0056] Figure 16 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0057] DETAILED DESCRIPTION

[0058] As a part of developing embodiments herein the inventors identified a problem which first will be discussed.

[0059] Following currently published technology, e.g., within the 5GC exposure paradigm, to enable service consumers to gain knowledge of available events, e.g., in a multi-vendor environment, it is necessary to pre-determine the assignment of NFs to event identities, i.e. , document which NF detects a specific event. It is also necessary to describe the event, i.e., all possible events that may be offered by NFs in the network, in detail. The documentation of these events must be pre-determined in 3GPP technical specifications on all reference points / interfaces from the external Application Function (AF), e.g., N33 offered via the NEF, to Home Subscriber Server (HSS), acting as “event registrar”, to the NF providing the service. This introduces a dependency to 3GPP specification release lifecycle management when it is deemed necessary to introduce and support new IMS events in an IMS-multivendor deployment. This limitation will adversely affect Time To Market (TTM) and innovation possibilities for consumers of the provided information. This approach also introduces the risk for event fragmentation related to communication sessions, whereby granular events would need to be defined and standardized related to “the same” communication session. These granular events will require a subscription mechanism per event which raise network capacity concerns. According to embodiments herein, an Event Category (EC) and Event Category- Information (EC-1) framework with minimal reliance on 3GPP standardization life cycles is provided to enable network service consumers to gain knowledge on, subscribe to, and receive info on events of interest. An overview the EC and EC-1 framework is depicted in Figure 1 . The EC may be used as event identifier and defined in 3GPP. EC-I, or EC-Info, may be an optional element and more granular than the EC. An Event Category Report (EC-Report) may e.g., comprise a report notification of individual events, such as IMS events, within the EC. The EC-report may e.g., be optional in subscribe response message, such as during immediate reporting, and may be mandatory in an notify message.

[0060] According to embodiments herein, The EC framework builds on the concept of grouping IMS network exposure events at a coarse-grain level. These coarse grain / high- level events may be standardized, e.g., once, in 3GPP, thus ensuring multi-vendor interaction and service consumer guidance.

[0061] The framework may be extensible by using an event category-information (EC-Info) construct. This may be an optional attribute / information element which is used to convey information related to the EC which is “understood” by the NF service consumer and NF service provider only. EC-Info may be subject to standardization, if deemed sufficiently critical from a multi-vendor interworking perspective. EC-Info is transparent to the IMS event exposure framework. If it is decided to standardize EC-Info this attribute may be defined as an extensible property, enabling it to be easily extended or augmented.

[0062] Furthermore, the EC framework also entails an Event Category-Report property. This comprises reporting of the notification of individual IMS events, i.e., EC-Info, within the EC. It is deemed to be optional in the case of “Subscribe Responses” where immediate reporting was requested but is mandatory in the case of Notify. Figures 2a-b shows EC and EC-I example values.

[0063] An EC may e.g., mean a coarse-grain level grouping of IMS network exposure events, that may be deemed a meta-event, that can be subscribed to.

[0064] Service consumers, such as AFs, both external to the Communication Service provider's (CSP) security domain and internal, may subscribe to standardized events using for example the EC, such as “Telephony_Event”, as “EventID” in the subscription towards the IMS event exposure framework. If N33 is used then the service will be offered by the NF NEF. The EC may be used by entities, e.g., consumers like an AF, to determine what events are supported by the network, but also by the IMS event exposure framework, e.g., NEF and / or HSS, to determine what producer provides the events.

[0065] An EC-1 may be an optional attribute and / or information element (IE) which may be used to convey extra information related to the EC which may be subscribed to. The attribute may be defined as an extensible property.

[0066] The EC-1 may be standardized, again if deemed necessary, as for example part of N33, see e.g., 3GPP TS 29.522 v.18.4.0. An extension, i.e., EC-I, may be added to the EC “Telephony_Event” namely,” User_Status_ onitoring”, e.g., status = busy I idle etc. EC-I provides service consumers, such as AFs, with more granular information on the coarse-grain event type category “Telephony-Event” on which it may subscribe.

[0067] EC-I may be used by service providers, e.g., IMS AS NFs, to provide more detailed subscription information towards service consumers that have subscribed to the corresponding EC.

[0068] EC-I is transparent to the IMS event exposure framework, e.g., the NEF & HSS. Thus, the IMS event exposure framework entities, e.g., NEF and HSS, does not need to be updated with EC-I information, it is sufficient with EC.

[0069] EC-I may also be defined on a “coarser grain” level, in much the same fashion as EC is proposed to be defined. For example, an EC-I “Monitor_events” may be defined in association with EC “Telephony_events”. Thus, it may also be standardized, concurrently to EC events, as a singular and / or once off occurrence. This will ensure that the framework is extensible and may be used for different “monitoring_events” by both consumers and producers, without dependency on the 3GPP standardization lifecycles.

[0070] An Event Category-Report EC-R may be an optional attribute and / or IE which is used to convey notification information on the specific EC-I events that were subscribed to.

[0071] EC-R will always be delivered by the service producer, e.g., IMS AS NFs, to the service consumer, e.g., AFs, as part of the event Notify, e.g., if the service consumer has subscribed to EC-I. In this case it is transparent to the IMS event exposure framework, i.e., NEF & HSS. In the case of “Subscribe-Response” where immediate reporting is requested, e.g., notification of subscribed events sent “immediately” as part of the subscribe response, EC-R will be sent via the exposure framework however EC-I is optional Embodiments herein may bring the advantage of independence, and / or decoupling, from the 3GPP specification release lifecycle where it is currently often deemed necessary to standardized newly introduced exposure events.

[0072] Further embodiments herein may bring the advantage of an improved interworking in a multivendor deployment by introducing to 3GPP in a singular occurrence the EC & EC-1 framework. The framework is extensible, without requiring further standardization.

[0073] Yet further, embodiments herein may bring the advantage of an improved TTM and innovation possibilities in the IMS event exposure paradigm, and embodiments herein may also be used in the existing 5GC exposure paradigm.

[0074] Yet further, embodiments herein may bring the advantage of reducing the number of subscriptions by the event consumer when the consumer interest is for example for all events in a category, e.g., all events in IMS DC session Control EC. The alternative would be for the consumer to subscribe to each event separately. Thus, embodiments may improve the capacity and performance of the communication network, e.g., since there is no need for multiple subscriptions.

[0075] Yet further, embodiments herein may bring the advantage of avoiding of the risk of event fragmentation related to communication sessions or IMS DC, whereby numerous events related to a session would be required per subscription for each subscriber / UE. Again, this ensures that the solution is capacity adapted.

[0076] Figure 3 is a schematic overview depicting a communication network 100, wherein embodiments herein may be implemented. The communication network 100 comprises one or more RANs, one or more IMS networks, e.g. an IMS network 105, and one or more CNs. The IMS network 105 may comprise several network entities, some of which are discussed here. The communication network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE- Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0077] Network nodes, such as a base station 101 , operate in the communication network 100. Each of the network nodes e.g. provides a number of cells and may use these cells for communicating with other network nodes. Each of the network nodes may be a transmission and reception point e.g. a network node, a radio access network node such as a base station, a radio base station, a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR / g Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE served by the network node depending e.g. on the radio access technology and terminology used.

[0078] An IMS node 140 operates in the IMS network 105. The IMS network 105 is an architecture for delivering media content over an IP packet switched transport. The IMS node 110 may e.g., comprise an IMS AS or an IMS NF or similar.

[0079] A subscriber node 110 operates in the IMS network 105, or is connected to the IMS network 105. The subscriber node 110 may e.g., comprise an HSS. The subscriber node 110 is a subscriber database which provides details of the subscribers to other entities within the network.

[0080] An event subscriber node 150 operates in the communications network 110. The event subscriber node may e.g., comprise a NF. The subscriber node 150 subscribes to events in the IMS network 105.

[0081] UEs, such as a UE 121 , operate in the communication network 100. The UE 121 may e.g. be a wireless device, an NR device, a mobile station, a wireless terminal, an internet of things (loT) device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to-everything (V2X) device, Vehicle-to-Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to- Infrastructure (V2I) device, a Veh i cl e-to- Network (V2N) device, a Wi-Fi device, an LTE device, a non-access point (non-AP) STA, a STA, that communicates via a base station, and one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN) or the IMS network 105. It should be understood by the skilled in the art that the term UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0082] Methods herein may in one aspect be performed by the subscriber node 110, the IMS node 140 and / or the event subscriber node 150. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 1 , may be used for performing or partly performing the methods of embodiments herein.

[0083] The cloud 190 may comprise a cloud network infrastructure. A cloud network infrastructure may e.g. be a collection of hardware and software elements such as computing power, networking, storage, and virtualization resources needed to enable cloud computing in a wireless communications network such as e.g. a communications network.

[0084] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0085] A method according to embodiments will now be described from the view of the subscriber node 110 together with Figure 4. Figure 4 depicts example embodiments of a method performed by the subscriber node 110 e.g., for handling events in the communication network 100. The subscriber node 110 may e.g., comprise an HSS. though the method is described in view of the subscriber node 110, such as an HSS, the method is applicable for the exposure node 130, such as an NEF. The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0086] Action 401

[0087] The subscriber node 110 receives, an event subscription request for subscribing to one or more event types. The event subscription request indicates an event category associated with the one or more event types. As mentioned above, the event category may be associated with one or more event types. Thus, by subscribing to the event category, the event subscriber, such as the event subscriber node 150, subscribes to the event types associated with the event category. In other words, the subscription request indicates the one or more event types to subscribe to by including the event category in the subscription request.

[0088] In some embodiments, the event subscription request originates from the event subscriber node 150 and is received from the exposure node 130. Thus, the event subscription request may be received from the event subscriber 150 via the exposure node 130.

[0089] In some embodiments, the event subscription request further indicates an event category information parameter associated with the event category. The event category information parameter may e.g., more granular data related to the event types associated with the event category. E.g., the event category information parameter may indicate specific event types. As an example, an event category may be “Telephony_Event”. The event category “Telephony_Event” may e.g., be associated with, such as comprise, the event types “User_Status_Monitoring” and “User_Location_Roaming_Monitoring”. In such an example, the event subscription request may indicate the event category “Telephony_Event” and the event category information parameter may indicate the event type “User_Status_Monitoring”. This may mean that the event subscriber requests to subscribe to the event “User_Status_Monitoring”. In other words, the event category information parameter may indicate one or more specific event types associated with the event category.

[0090] In some embodiments, the event subscription request further indicates, such as comprise, the UE 121 associated with the event subscription. The event subscription request may e.g., indicate an ID of the UE 121. The ID may e.g., comprise the IMS Public User Identity (IMPU) or the Subscription Permanent Identifier (SUPI) of the UE 121.

[0091] In some embodiments, the event subscription request further indicates that immediate reporting is requested. The immediate reporting may mean that a notification of subscribed events is to be sent by the IMS node receiving the event subscription response in an event subscription response message. The event subscription response message is to be sent in response the event subscription request message.

[0092] Action 402

[0093] In some embodiments, the subscriber node 110 determines the IMS node 140 associated with the event category. Determining the IMS node 140 associated with the event category further comprises determining an instance ID of the IMS node 140 associated with the UE 121. The instance ID may e.g., be needed in order to determine where to the send the event subscription request. The IMS node 140 may e.g., comprise an IMS AS and / or an IMS NF.

[0094] In some embodiments, the subscriber node 110 further determines an address associated with the instance ID. The address may e.g., be obtained from the repository node 160.

[0095] Action 403

[0096] The subscriber node 110 sends the event subscription request to the IMS node 140. The event subscription request indicates the event category associated with the one or more event types. The event subscription request may further comprise the event category information parameter.

[0097] In some embodiments, sending the event subscription request may e.g., comprise sending the event subscription request to the determined address associated with the instance ID of the IMS node 140. In some embodiments, the event subscription request further indicates that immediate reporting is requested. As mentioned above, the immediate reporting may mean that a notification of subscribed events is to be sent by the IMS node receiving the event subscription response in an event subscription response message. The event subscription response message is to be sent in response the event subscription request message.

[0098] Action 404

[0099] In some embodiments, the subscriber node 110 receives an event subscription response from the IMS node 140. The event subscription response may comprise an event category report related to the event category. The event subscription response message may be received in response to the event subscription request, e.g., when the event subscription request indicated that immediate reporting is requested. The event category report comprises data related to the events subscribed to. As mentioned above, the event subscription request may comprise the event category information parameter related to the event category. Thus, the event subscription report may further be related to the event category information parameter.

[0100] Action 405

[0101] In some embodiments, the subscriber node 110 sends the event subscription response towards an event subscriber node 150. The event subscription response may comprise event category report. The event category report comprises data related to the events subscribed to.

[0102] A method according to embodiments will now be described from the view of the subscriber node 110 together with Figure 5. Figure 5 depicts example embodiments of a method performed by the IMS node 140 e.g., for handling events in the communication network 100. The IMS node 140 may e.g., comprise an IMS AS and / or an IMS NF. The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0103] Action 501

[0104] The IMS node 140 receives, e.g., from the subscriber node 110, an event subscription request for subscribing to one or more event types. The event subscription request indicates an event category associated with the one or more event types to be monitored. As mentioned above, the event category may be associated with one or more event types. Thus, by subscribing to the event category, the event subscriber, such as the event subscriber node 150, subscribes to the event types associated with the event category. In other words, the subscription request indicates the one or more event types to subscribe to by including the event category in the subscription request.

[0105] In some embodiments, the event subscription request further indicates an event category information parameter associated with the event category. The event category information parameter may e.g., more granular data related to the event types associated with the event category. E.g., the event category information parameter may indicate specific event types. As an example, an event category may be “Telephony_Event”. The event category “Telephony_Event” may e.g., be associated with, such as comprise, the event types “User_Status_Monitoring” and “User_Location_Roaming_Monitoring”. In such an example, the event subscription request may indicate the event category “Telephony_Event” and the event category information parameter may indicate the event type “User_Status_Monitoring”. This may mean that the event subscriber requests to subscribe to the event “User_Status_Monitoring”. In other words, the event category information parameter may indicate one or more specific event types associated with the event category.

[0106] In some embodiments, the event subscription request further indicates that immediate reporting is requested. As mentioned above, the immediate reporting may mean that a notification of subscribed events is to be sent by the IMS node receiving the event subscription response in an event subscription response message. The event subscription response message is to be sent in response the event subscription request message.

[0107] Action 502

[0108] In some embodiments, the IMS node 140 sends an event subscription response to the subscriber node 110. The event subscription response may comprise an event category report. The event subscription response message may be sent in response to the event subscription request, e.g., when the event subscription request indicated that immediate reporting is requested. The event category report comprises data related to the events subscribed to. As mentioned above, the event subscription request may comprise the event category information parameter related to the event category. Thus, the event subscription report may further be related to the event category information parameter.

[0109] Action 503

[0110] In some embodiments, The IMS node 140 detects that an event corresponding to the event category has been triggered. The IMS node 140 may detect that that the event is triggered based on the monitoring of the event types associated with event category.

[0111] Action 504 The IMS AS 140 sends, to the event subscriber node 150, a notification message. The notification message notifies the event subscriber node 150 that an event corresponding to the event category has been triggered. In other words, when an event associated with the event category has been triggered, the event subscriber node 150 is notified about the triggering by the IMS node 140.

[0112] In some embodiments, the notification message comprises an event category report related to the triggered event. The event category report comprises data related to the events subscribed to.

[0113] A method according to embodiments will now be described from the view of the subscriber node 110 together with Figure 6. Figure 6 depicts example embodiments of a method performed by the event subscriber node 150 e.g., for handling events in the communication network 100. The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0114] Action 601

[0115] The event subscriber node 150 sends, towards a subscriber node 110, an event subscription request for subscribing to one or more event. The event subscription request indicates an event category associated with the one or more event types. As mentioned above, the event category may be associated with one or more event types. Thus, by subscribing to the event category the event subscriber node 150 subscribes to the event types associated with the event category. In other words, the subscription request indicates the one or more event types to subscribe to by including the event category in the subscription request.

[0116] In some embodiments, the event subscription request may be sent towards the subscriber node 110 via the exposure node 130.

[0117] In some embodiments, the event subscription request further indicates an event category information parameter associated with the event category. The event category information parameter may e.g., more granular data related to the event types associated with the event category. E.g., the event category information parameter may indicate specific event types. As an example, an event category may be “Telephony_Event”. The event category “Telephony_Event” may e.g., be associated with, such as comprise, the event types “User_Status_Monitoring” and “User_Location_Roaming_Monitoring”. In such an example, the event subscription request may indicate the event category “Telephony_Event” and the event category information parameter may indicate the event type “User_Status_Monitoring”. This may mean that the event subscriber requests to subscribe to the event “User_Status_Monitoring”. In other words, the event category information parameter may indicate one or more specific event types associated with the event category.

[0118] In some embodiments, the event subscription request further indicates that immediate reporting is requested. As mentioned above, the immediate reporting may mean that a notification of subscribed events is to be sent by the IMS node receiving the event subscription response in an event subscription response message. The event subscription response message is to be sent in response the event subscription request message.

[0119] Action 602

[0120] In some embodiments, the event subscriber node 150 receives an event subscription response from the subscriber node 110. The event subscription response may comprise an event category report related to the event category. The event subscription response message may be received in response to the event subscription request, e.g., when the event subscription request indicated that immediate reporting is requested. The event category report comprises data related to the events subscribed to. As mentioned above, the event subscription request may comprise the event category information parameter related to the event category. Thus, the event subscription report may further be related to the event category information parameter.

[0121] Action 603

[0122] The event subscriber node 150 receives, from the IMS node 140, a notification message. The notification message notifies the event subscriber node 150 that an event corresponding to the event category has been triggered. In other words, when an event associated with the event category has been triggered, the event subscriber node 150 is notified about the triggering by the IMS node 140.

[0123] In some embodiments, the notification message comprises an event category report related to the triggered event. The event category report comprises data related to the events subscribed to.

[0124] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0125] Figure 7 shows an example of embodiments herein. The example describes a conceptual call flow according to embodiments herein. The example involves a UE, such as the UE 121 , a service consumer, such as the event subscriber node 150, an HSS, such as the subscriber node 110, an IMS AS, such as the IMS node 140, a NEF, such as the exposure node 130, an NRF, such as the repository node 160 and an IMS NF, such as the IMS node 170.

[0126] Note: not all interactions are shown (for simplicity).

[0127] 571. The UE 121 may initiate an IMS registration, e.g., by sending a registration request to the IMS NF, such as the IMS node 170.

[0128] 572. The IMS NF, such as the IMS node 170, may send the register request, for the UE 121 , towards the HSS, such as the subscriber node 110. The IMS NF 170, e.g., an S- CSCF, may include one or more Event Categories it supports and its IDs.

[0129] 573. The HSS, such as the subscriber node 110, may send a response to the registration request registration request, e.g., the IMS NF, such as the IMS node 170.

[0130] 574. A 200 OK message may be sent to the UE 121 in response to the registration request.

[0131] 575. A 3rd party registration request may be sent from the IMS NF, such as the IMS node 170, to the IMS AS, such as the IMS node 140.

[0132] 576. The IMS AS, such as the IMS node 140, may send a 200 OK message to the IMS NF, such as the IMS node 170, in response to the 3rd party registration request.

[0133] 577. The IMS AS, such as the IMS node 140, may register towards HSS. The IMS AS may include one or more ECs is supports in the registration request. This may e.g., comprise “Telephony_Events”.

[0134] 578. The HSS, such as the subscriber node 110 may send a registration response to the IMS AS, such as the IMS node 140.

[0135] 579. The HSS, such as the subscriber node 110, in its role as an “event registrar” may save the received event exposure information including the EC.

[0136] 5710. The service consumer, such as the event subscriber node 150, sends a subscription request towards the HSS, such as the subscriber node 110, e.g., via the NEF, such as the exposure node 130, using e.g., the N33 reference point. N33. The subscription request comprises the EC, e.g., “Telephony_Events”, the service consumer wants to subscribe to. The subscription request may comprise EC-I if deemed necessary. This step may be combined with e.g., Action 304.

[0137] 5711. The NEF, such as the exposure node 130, may forward the subscription request towards HSS, such as the subscriber node 110. The subscription request comprises the EC, and optionally the EC-I. the EC-I is transparent to the NEF. 5712. If dynamic registration is supported, the HSS, such as the subscriber node 110, in its role of “Event registrar1’, may use the received EC to locate, e.g., via its earlier saved data, the correct IMS AS instance ID, such as the IMS node 140 instance ID, serving the UE 121 , e.g., using the IMPU of the UE 121. If dynamic registration is not supported, then a mechanism based on pre-determined procedures using the newly introduced EC may be used.

[0138] 5713. The HSS, such as the subscriber node 110, may use the NRF, such as the repository node 160, to locate, such as obtain, the correct IMS AS address associated to the instance ID of the IMS AS, such as the IMS node 140.

[0139] 5714. The HSS, such as the subscriber node 110, may receive the address to the IMS AS, such as the IMS node 140, from the NRF, such as the repository node 160.

[0140] 5715. The HSS, such as the subscriber node 110, forwards, such as sends the subscription request to the correct IMS AS address, such as the IMS node 140 address. The subscription request comprises the EC, and optionally the EC-I. The EC-Info may be transparent to HSS.

[0141] S716a. If immediate reporting is requested the IMS AS, such as the IMS node 140, may, based on the subscription request, send in a subscription-response comprising an EC-Report. The EC-Report may comprise specific information on requested EC-I subscribed event.

[0142] S716b. The HSS, such as the subscriber node 110, may forward, such as send, the subscription-response comprising the EC-Report towards the service consumer, such as the event subscriber node 150, e.g., via the NEF, such as the exposure node 160.

[0143] S716c. The NEF, such as the exposure node 160 may forward, such as send, the subscription-response comprising EC-Report to the service consumer, such as the event subscriber node 150.

[0144] 5717. If immediate reporting is not requested, then the IMS AS, such as the IMS node 140, notifies the occurrence, such as sends a notification massage, of the subscribed event when it occurs and / or is triggered, e.g., by sending a Nims_IMSEE_Notify. The notification is sent towards the service consumer, such as the event subscriber node 150, e.g., via the NEF, such as the exposure node 160. The notification may comprise the EC-Report. The EC-Report may be to the IMS event exposure framework.

[0145] 5718. The NEF, such as the exposure node 160, may send the notification, such as a Nnef_IMSEE_Notify, to the service consumer, such as the event subscriber node 150. The notification may comprise the EC-Report. To perform the method actions above, the subscriber node 110 is e.g., configured to handle events in the communications network 100. The subscriber node 110 may comprise an arrangement depicted in Figure 8.

[0146] The subscriber node 110 may comprise an input and output interface 800 configured to communicate with each other. The input and output interface 800 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0147] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 810 of a processing circuitry in the subscriber node 110 depicted in Figure 8, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the subscriber node 110. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the subscriber node 110.

[0148] The subscriber node 110 and / or the processor 810 is e.g., configured to handle events in the communication network 100.

[0149] The subscriber node 110 and / or the processor 810 is configured to receive an event subscription request for subscribing to one or more event types. The event subscription request is adapted to indicate an event category associated with the one or more event types.

[0150] The subscriber node 110 and / or the processor 810 is configured to send the event subscription request to the IMS node 140.

[0151] In some embodiments, the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0152] In some embodiments, the subscriber node 110 and / or the processor 810 may further be configured to send the event subscription request to the IMS node 140 associated with the UE 121 indicated in the event subscription request.

[0153] In some embodiments, the event subscription request further indicates the UE 121 associated with the event subscription. The subscriber node 110 and / or the processor 810 may further be configured to determine the IMS node 140 associated with the event category. To determine the IMS node 140 associated with the event category is further adapted to comprise to determine an ID of the IMS node 140 associated with the UE 121.

[0154] In some embodiments, the subscriber node 110 and / or the processor 810 may further be configured to receive an event subscription response from the IMS node 140.

[0155] In some embodiments, the event subscription response is adapted to comprise an event category report related to the event category. The subscriber node 110 and / or the processor 810 may be configured to send the event subscription response towards an event subscriber node 150.

[0156] In some embodiments, the event category report is further related to the event category information parameter.

[0157] The subscriber node 110 may further comprise respective a memory 820 comprising one or more memory units. The memory 820 comprises instructions executable by the processor 810 in the subscriber node 110.

[0158] The memory 820 is arranged to be used to store instructions, data, configurations, identifiers, indications, parameters, event categories, event category information parameters, event category reports, and applications to perform the methods herein when being executed in the subscriber node 110.

[0159] In some embodiments, a computer program 830 comprises instructions, which when executed by the at least one processor 810, cause the at least one processor 810 of the subscriber node 110 to perform the actions above.

[0160] In some embodiments, a respective carrier 840 comprises the respective computer program 830, wherein the carrier 840 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0161] Thus, embodiments herein may disclose the subscriber node 110 e.g., configured to handle events in the communications network 100. The subscriber node 110 comprises the processor 810 and the memory 820, said memory 820 comprising instructions executable by said processor 810 whereby said subscriber node 110 is operative to perform any of the methods herein.

[0162] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0163] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0164] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0165] To perform the method actions above, the IMS node 140 is e.g., configured to handle events in the communications network 100. The IMS node 140 may comprise an arrangement depicted in Figure 9.

[0166] The IMS node 140 may comprise an input and output interface 900 configured to communicate with each other. The input and output interface 900 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown). The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 910 of a processing circuitry in the IMS node 140 depicted in Figure 9, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the I S node 140. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the IMS node 140.

[0167] The IMS node 140 and / or the processor 910 is e.g., configured to handle events in the communication network 100.

[0168] The IMS node 140 and / or the processor 910 is configured to receive, from a subscriber node 110, an event subscription request for subscribing to one or more event types. The event subscription request is adapted to indicate an event category associated with the one or more events to be monitored.

[0169] The IMS node 140 and / or the processor 910 is configured to send, to an event subscriber node 150, a notification message. The notification message is adapted to notify the event subscriber node 150 that an event corresponding to the event category has been triggered.

[0170] In some embodiments, the wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0171] In some embodiments, the notification message is adapted to comprise an event category report related to the triggered event.

[0172] In some embodiments, the IMS node 140 and / or the processor 910 may further be configured to send an event subscription response to the subscriber node 110.

[0173] In some embodiments, the event subscription response is adapted to comprise an event category report related to the event category.

[0174] In some embodiments, the event category report is further related to the event category information parameter.

[0175] In some embodiments, the IMS node 140 and / or the processor 910 may further be configured to detect that an event corresponding to the event category has been triggered. The IMS node 140 may further comprise respective a memory 920 comprising one or more memory units. The memory 920 comprises instructions executable by the processor 910 in the IMS node 140.

[0176] The memory 920 is arranged to be used to store instructions, data, configurations, identifiers, indications, parameters, event categories, event category information parameters, event category reports, and applications to perform the methods herein when being executed in the IMS node 140.

[0177] In some embodiments, a computer program 920 comprises instructions, which when executed by the at least one processor 910, cause the at least one processor 910 of the IMS node 140 to perform the actions above.

[0178] In some embodiments, a respective carrier 940 comprises the respective computer program 930, wherein the carrier 940 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0179] Thus, embodiments herein may disclose the IMS node 140 e.g., configured to handle events in the communications network 100. The IMS node 140 comprises the processor 910 and the memory 920, said memory 920 comprising instructions executable by said processor 910 whereby said IMS node 140 is operative to perform any of the methods herein.

[0180] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0181] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0182] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0183] To perform the method actions above, the event subscriber node 150 is e.g., configured to handle events in the communications network 100. The event subscriber node 150 may comprise an arrangement depicted in Figure 10.

[0184] The event subscriber node 150 may comprise an input and output interface 1000 configured to communicate with each other. The input and output interface 1000 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0185] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1010 of a processing circuitry in the event subscriber node 150 depicted in Figure 10, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the event subscriber node 150. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the event subscriber node 150.

[0186] The event subscriber node 150 and or the processor 1010 is e.g., configured to handle events in the communication network 100.

[0187] The event subscriber node 150 and / or the processor 1010 is configured to send, towards a subscriber node 110, an event subscription request for subscribing to one or more event. The event subscription request is adapted to indicate an event category associated with the one or more event types.

[0188] The event subscriber node 150 and / or the processor 1010 is configured to receive, from the IMS node 140, a notification message. The notification message is adapted to notify the event subscriber node 150 that an event corresponding to the event category has been triggered.

[0189] In some embodiments, the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0190] In some embodiments, the notification message is adapted to comprise an event category report related to the triggered event.

[0191] In some embodiments, the event subscriber node 150 and / or the processor 1010 may further be configured to receive an event subscription response from the subscriber node 110.

[0192] In some embodiments, the event subscription response is adapted to comprise an event category report related to the event category.

[0193] In some embodiments, the event category report is further related to the event category information parameter.

[0194] The event subscriber node 150 may further comprise respective a memory 1020 comprising one or more memory units. The memory 1020 comprises instructions executable by the processor 1010 in the event subscriber node 150.

[0195] The memory 1020 is arranged to be used to store instructions, data, configurations, identifiers, indications, parameters, event categories, event category information parameters, event category reports, and applications to perform the methods herein when being executed in the event subscriber node 150.

[0196] In some embodiments, a computer program 1020 comprises instructions, which when executed by the at least one processor 1010, cause the at least one processor 1010 of the event subscriber node 150 to perform the actions above.

[0197] In some embodiments, a respective carrier 1040 comprises the respective computer program 1030, wherein the carrier 1040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0198] Thus, embodiments herein may disclose the event subscriber node 150 e.g., configured to handle events in the communications network 100. The event subscriber node 150 comprises the processor 1010 and the memory 1020, said memory 1020 comprising instructions executable by said processor 1010 whereby said event subscriber node 150 is operative to perform any of the methods herein.

[0199] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a base station, for example.

[0200] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and nonvolatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0201] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0202] Embodiments

[0203] Below, some example Embodiments 1-34 are shortly described. See e.g., Figures 2-7.

[0204] Embodiment 1. A method performed by a subscriber node 110 e.g., for handling events in a communication network 100, the method comprising any one or more out of: receiving 401 an event subscription request for subscribing to one or more event types, wherein the event subscription request indicates an event category associated with the one or more event types, sending 403 the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node 140.

[0205] Embodiment 2. The method according to embodiment 1, wherein the event subscription request further indicates an event category information parameter associated with the event category.

[0206] Embodiment 3. The method according to any of embodiments 1-2, wherein the event subscription request is sent 403 to the IMS node 140 associated with a User Equipment, UE, 121 indicated in the event subscription request.

[0207] Embodiment 4. The method according to any of embodiments 1-3, wherein the event subscription request further indicates a User Equipment, UE, 121 associated with the event subscription, wherein the method further comprises: determining 402 the IMS node 140 associated with the event category, wherein determining the IMS node 140 associated with the event category further comprises determining an instance identity, ID, of the IMS node 140 associated with the UE 121.

[0208] Embodiment 5. The method according to any of embodiments 1-4, wherein the method further comprises: receiving 404 an event subscription response from the IMS node 140, which event subscription response comprises an event category report related to the event category, and sending 405 the event subscription response towards an event subscriber node 150.

[0209] Embodiment 6. A computer program 830 comprising instructions, which when executed by a processor 810, causes the processor 810 to perform actions according to any of the embodiments 1-5.

[0210] Embodiment 7. A carrier 840 comprising the computer program 830 of embodiment 6, wherein the carrier 840 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0211] Embodiment 8. A method performed by an Internet Protocol Multimedia Subsystem, IMS, node 140 e.g., for handling events in a communication network 100, the method comprising any one or more out of: receiving 501, from a subscriber node 110, an event subscription request for subscribing to one or more event types, wherein the event subscription request indicates an event category associated with the one or more events to be monitored, sending 504, to an event subscriber node 150, a notification message, the notification message notifying the event subscriber node 150 that an event corresponding to the event category has been triggered.

[0212] Embodiment 9. The method according to claim 8, wherein the event subscription request further indicates an event category information parameter associated with the event category.

[0213] Embodiment 10. The method according to any of embodiments 8-9, wherein the notification message comprises an event category report related to the triggered event.

[0214] Embodiment 11. The method according to any of embodiments 8-10, wherein the method further comprises: sending 502 an event subscription response to the subscriber node 110, which event subscription response comprises an event category report.

[0215] Embodiment 12. The method according to any of embodiments 8-11 , wherein the method further comprises: detecting 503 that an event corresponding to the event category has been triggered.

[0216] Embodiment 13. A computer program 930 comprising instructions, which when executed by a processor 910, causes the processor 910 to perform actions according to any of the embodiments 8-12.

[0217] Embodiment 14. A carrier 940 comprising the computer program 930 of embodiment 13, wherein the carrier 940 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0218] Embodiment 15. A method performed by an event subscriber node 150 e.g., for handling events in a communication network 100, the method comprising any one or more out of: sending 601 , towards a subscriber node 110 an event subscription request for subscribing to one or more event, wherein the event subscription request indicates an event category associated with the one or more event types, receiving 603, from an Internet Protocol Multimedia Subsystem, IMS, node 140, a notification message, the notification message notifying the event subscriber node 150 that an event corresponding to the event category that has been triggered.

[0219] Embodiment 16. The method according to embodiment 15, wherein the event subscription request further indicates an event category information parameter associated with the event category.

[0220] Embodiment 17. The method according to any of embodiments 15-16, wherein the notification message comprises an event category report related to the triggered event.

[0221] Embodiment 18. The method according to any of embodiments 15-17, wherein the method further comprises: receiving 602 an event subscription response from the subscriber node 110, which event subscription response comprises an event category report related to the event category.

[0222] Embodiment 19. A computer program 1030 comprising instructions, which when executed by a processor 1010, causes the processor 1010 to perform actions according to any of the embodiments 15-18.

[0223] Embodiment 20. A carrier 1040 comprising the computer program 1030 of embodiment 19, wherein the carrier 1040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0224] Embodiment 21. A subscriber node 110 e.g., configured to handle events in a communication network 100, the subscriber node 110 further being configured to any one or more out of: receive an event subscription request for subscribing to one or more event types, wherein the event subscription request is adapted to indicate an event category associated with the one or more event types, send the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node 140.

[0225] Embodiment 22. The subscriber node 110 according to embodiment 21, wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0226] Embodiment 23. The subscriber node 110 according to any of embodiments 21-22, wherein the subscriber node 110 is configured to send the event subscription request to the IMS node 140 associated with a User Equipment, UE, 121 indicated in the event subscription request.

[0227] Embodiment 24. The subscriber node 110 according to any of embodiments 21-23, wherein the event subscription request further indicates a UE 121 associated with the event subscription, wherein the subscriber node 110 is further configured to: determine the IMS node 140 associated with the event category, wherein to determine the IMS node 140 associated with the event category is further adapted to comprise to determine an instance identity, ID, of the IMS node 140 associated with the UE 121.

[0228] Embodiment 25. The subscriber node 110 according to any of embodiments 21-24, wherein the subscriber node 110 is further configured to: receive an event subscription response from the IMS node 140, which event subscription response is adapted to comprise an event category report related to the event category, and send the event subscription response towards an event subscriber node 150.

[0229] Embodiment 26. An Internet Protocol Multimedia Subsystem, IMS, node 140 e.g., configured to handle events in a communication network 100, the IMS node 140 further being configured to any one or more out of: receive, from a subscriber node 110, an event subscription request for subscribing to one or more event types, wherein the event subscription request is adapted to indicate an event category associated with the one or more events to be monitored, send, to an event subscriber node 150, a notification message, the notification message being adapted to notify the event subscriber node 150 that an event corresponding to the event category has been triggered.

[0230] Embodiment 27. The IMS node 140 according to the embodiment 26, wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0231] Embodiment 28. The IMS node 140 according to any of embodiments 26-27, wherein the notification message is adapted to comprise an event category report related to the triggered event.

[0232] Embodiment 29. The IMS node 140 according to any of embodiments 26-28, wherein the IMS node 140 is further configured to: send an event subscription response to the subscriber node 110, which event subscription response is adapted to comprise an event category report. Embodiment 30. The IMS node 140 according to any of embodiments 26-29, wherein the IMS node 140 is further configured to: detect that an event corresponding to the event category has been triggered.

[0233] Embodiment 31. An event subscriber node 150 e.g., configured to handle events in a communication network 100, the subscriber node 150 being configured to any one or more out of: send, towards a subscriber node 110, an event subscription request for subscribing to one or more event, wherein the event subscription request is adapted to indicate an event category associated with the one or more event types, receive, from an Internet Protocol Multimedia Subsystem, IMS, node 140, a notification message, the notification message being adapted to notify the event subscriber node 150 that an event corresponding to the event category that has been triggered.

[0234] Embodiment 32. The subscriber node 150 according to embodiment 31, wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

[0235] Embodiment 33. The subscriber node 150 according to any of embodiments 31-32, wherein the notification message is adapted to comprise an event category report related to the triggered event.

[0236] Embodiment 34. The subscriber node 150 according to any of embodiments 31-33, wherein the subscriber node 150 is further configured to: receive an event subscription response from the subscriber node 110, which event subscription response is adapted to comprise an event category report related to the event category.

[0237] ADDITIONAL EXPLANATION

[0238] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0239] Figure 11 shows an example of a communication system QQ100 in accordance with some embodiments. In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108 (being examples of the network node 110). The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 being examples of the network node 110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0240] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112 being examples of the UE 121) to the core network QQ106 over one or more wireless connections.

[0241] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0242] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0243] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF). The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0244] As a whole, the communication system QQ100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0245] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0246] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0247] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0248] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0249] Figure 12 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0250] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0251] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0252] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0253] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the U QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0254] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0255] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0256] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0257] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0258] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0259] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0260] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

[0261] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0262] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0263] Figure 13 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0264] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cel l / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0265] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0266] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0267] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0268] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0269] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0270] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0271] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0272] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0273] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0274] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0275] Figure 14 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0276] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0277] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0278] Figure 15 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O- Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0279] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0280] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0281] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0282] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0283] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0284] Figure 16 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 11 and / or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure 11 and / or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure 11 and / or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.

[0285] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0286] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0287] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0288] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0289] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0290] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

[0291] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0292] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0293] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0294] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0295] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1. A method performed by a subscriber node (110) for handling events in a communication network (100), the method comprising any one or more out of: receiving (401) an event subscription request for subscribing to one or more event types, wherein the event subscription request indicates an event category associated with the one or more event types, sending (403) the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node (140).

2. The method according to claim 1, wherein the event subscription request further indicates an event category information parameter associated with the event category.

3. The method according to any of claims 1-2, wherein the event subscription request is sent (403) to the IMS node (140) associated with a User Equipment, UE, (121) indicated in the event subscription request.

4. The method according to any of claims 1-3, wherein the event subscription request further indicates a User Equipment, UE, (121) associated with the event subscription, wherein the method further comprises: determining (402) the IMS node (140) associated with the event category, wherein determining the IMS node (140) associated with the event category further comprises determining an instance identity, ID, of the IMS node (140) associated with the UE (121).

5. The method according to any of claims 1-4, wherein the method further comprises: receiving (404) an event subscription response from the IMS node (140), and sending (405) the event subscription response towards an event subscriber node(150).

6. The method according to claim 5, wherein the event subscription response comprises an event category report related to the event category.

7. The method according to claim 6, wherein the event category report is further related to the event category information parameter.

8. A computer program (830) comprising instructions, which when executed by a processor (810), causes the processor (810) to perform actions according to any of the claims 1-7.

9. A carrier (840) comprising the computer program (830) of claim 8, wherein the carrier (840) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

10. A method performed by an Internet Protocol Multimedia Subsystem, IMS, node (140) for handling events in a communication network (100), the method comprising any one or more out of: receiving (501), from a subscriber node (110), an event subscription request for subscribing to one or more event types, wherein the event subscription request indicates an event category associated with the one or more events to be monitored, sending (504), to an event subscriber node (150), a notification message, the notification message notifying the event subscriber node (150) that an event corresponding to the event category has been triggered.

11. The method according to claim 10, wherein the event subscription request further indicates an event category information parameter associated with the event category.

12. The method according to any of claims 10-11 , wherein the notification message comprises an event category report related to the triggered event.

13. The method according to any of claims 10-12, wherein the method further comprises: sending (502) an event subscription response to the subscriber node (110).

14. The method according to claim 13, wherein the event subscription response comprises an event category report related to the event category.

15. The method according to claim 14, wherein the event category report is further related to the event category information parameter.

16. The method according to any of claims 10-15, wherein the method further comprises: detecting (503) that an event corresponding to the event category has been triggered.

17. A computer program (930) comprising instructions, which when executed by a processor (910), causes the processor (910) to perform actions according to any of the claims 10-16.

18. A carrier (940) comprising the computer program (930) of claim 17, wherein the carrier (940) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

19. A method performed by an event subscriber node (150) for handling events in a communication network (100), the method comprising any one or more out of: sending (601), towards a subscriber node (110) an event subscription request for subscribing to one or more event, wherein the event subscription request indicates an event category associated with the one or more event types, receiving (603), from an Internet Protocol Multimedia Subsystem, IMS, node (140), a notification message, the notification message notifying the event subscriber node (150) that an event corresponding to the event category that has been triggered.

20. The method according to claim 19, wherein the event subscription request further indicates an event category information parameter associated with the event category.

21. The method according to any of claims 19-20, wherein the notification message comprises an event category report related to the triggered event.

22. The method according to any of claims 19-21 , wherein the method further comprises: receiving (602) an event subscription response from the subscriber node (110).

23. The method according to claim 22, wherein the event subscription response comprises an event category report related to the event category.

24. The method according to claim 23, wherein the event category report is further related to the event category information parameter.

25. A computer program (1030) comprising instructions, which when executed by a processor (1010), causes the processor (1010) to perform actions according to any of the claims 19-24.

26. A carrier (1040) comprising the computer program (1030) of claim 25, wherein the carrier (1040) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

27. A subscriber node (110) configured to handle events in a communication network (100), the subscriber node (110) further being configured to any one or more out of: receive an event subscription request for subscribing to one or more event types, wherein the event subscription request is adapted to indicate an event category associated with the one or more event types, send the event subscription request to an Internet Protocol Multimedia Subsystem, IMS, node (140).

28. The subscriber node (110) according to claim 27, wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

29. The subscriber node (110) according to any of claims 27-28, wherein the subscriber node (110) is configured to send the event subscription request to the IMS node (140) associated with a User Equipment, UE, (121) indicated in the event subscription request.

30. The subscriber node (110) according to any of claims 27-29, wherein the event subscription request further indicates a UE (121) associated with the event subscription, wherein the subscriber node (110) is further configured to: determine the IMS node (140) associated with the event category, wherein to determine the IMS node (140) associated with the event category is further adapted tocomprise to determine an instance identity, ID, of the IMS node (140) associated with the UE (121).

31. The subscriber node (110) according to any of claims 27-30, wherein the subscriber node (110) is further configured to: receive an event subscription response from the IMS node (140), and send the event subscription response towards an event subscriber node (150).

32. The subscriber node (110) according to claim 31 , wherein the event subscription response comprises an event category report related to the event category.

33. The subscriber node (110) according to claim 32, wherein the event category report is further related to the event category information parameter.

34. An Internet Protocol Multimedia Subsystem, IMS, node (140) configured to handle events in a communication network (100), the IMS node (140) further being configured to any one or more out of: receive, from a subscriber node (110), an event subscription request for subscribing to one or more event types, wherein the event subscription request is adapted to indicate an event category associated with the one or more events to be monitored, send, to an event subscriber node (150), a notification message, the notification message being adapted to notify the event subscriber node (150) that an event corresponding to the event category has been triggered.

35. The IMS node (140) according to the claim 34, wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

36. The IMS node (140) according to any of claims 34-35, wherein the notification message is adapted to comprise an event category report related to the triggered event.

37. The IMS node (140) according to any of claims 34-36, wherein the IMS node (140) is further configured to: send an event subscription response to the subscriber node (110), which event subscription response is adapted to comprise an event category report.

38. The IMS node (140) according to claim 37, wherein the event subscription response comprises an event category report related to the event category.

39. The IMS node (140) according to claim 38, wherein the event category report is further related to the event category information parameter.

40. The IMS node (140) according to any of claims 34-39, wherein the IMS node (140) is further configured to: detect that an event corresponding to the event category has been triggered.

41. An event subscriber node (150) configured to handle events in a communication network (100), the subscriber node (150) being configured to any one or more out of: send, towards a subscriber node (110), an event subscription request for subscribing to one or more event, wherein the event subscription request is adapted to indicate an event category associated with the one or more event types, receive, from an Internet Protocol Multimedia Subsystem, IMS, node (140), a notification message, the notification message being adapted to notify the event subscriber node (150) that an event corresponding to the event category that has been triggered.

42. The subscriber node (150) according to claim 41 , wherein the event subscription request is further adapted to indicate an event category information parameter associated with the event category.

43. The subscriber node (150) according to any of claims 41-42, wherein the notification message is adapted to comprise an event category report related to the triggered event.

44. The subscriber node (150) according to any of claims 41-23, wherein the subscriber node (150) is further configured to: receive an event subscription response from the subscriber node (110), which event subscription response is adapted to comprise an event category report related to the event category.

45. The subscriber node (150) according to claim 44, wherein the event subscription response comprises an event category report related to the event category.

46. The subscriber node (150) according to claim 45, wherein the event category report is further related to the event category information parameter.

Images