Network exposure node, application node, subscriber data node, IMS application server and methods performed thereby in a communication system

Abstract

A method performed by a network exposure node (140) for handling events in a communication network (100) is provided. The network exposure node (140) receives a first status request for a current status related to an event type from an application node (130). The request comprises the event type. The network exposure node (140) requests the current status related to the requested event type. The network exposure node (140) receives a status response for the requested event type. The status response indicates the current status related to the requested event type. The network exposure node (140) sends the status response the application node (130).

Description

[0001] NETWORK EXPOSURE NODE, APPLICATION NODE, SUBSCRIBER DATA NODE, IMS APPLICATION SERVER AND METHODS PERFORMED THEREBY IN A COMMUNICATION SYSTEM

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to a network exposure node and methods performed thereby for handling events and event status retrieval. The present disclosure also relates generally to an application node, subscriber data node, Internet Protocol Multimedia Subsystem (IMS) application server and methods performed thereby for handling events and event status retrieval.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) 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.

[0006] 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).

[0007] 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 buthave 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.

[0008] 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.

[0009] 3GPP TS 23.502 v19.3.0 defines an event exposure framework in 5G Core (5GC) which has been taken as a base to define a similar framework for Internet Protocol Multimedia Subsystem (IMS) events in 3GPP TS 23.228 v19.2.0.

[0010] The IMS Subscribe / Notity Framework enables third party Application Functions (AF) and network functions to subscribe to and being notified about IMS events.

[0011] The framework supports Subscribe / Notify type of operations and includes Event Reporting Information defined in 3GPP TS 23.502 v19.3.0 by which the AF consumer can request e.g. the current status related to the requested event type in the response to the subscription request and a maximum number of event report notifications.

[0012] For example, in the context of event types such as International Mobile Equipment Identity (IMEI) change, roaming status change or call status change, the corresponding current status related to the event type are the current IMEI, whether the user is roaming or not or whether the user is idle or busy in a call.

[0013] SUMMARY

[0014] An object of embodiments herein is to handle events in a communication network in an efficient manner and improve the performance of the wireless communication network.

[0015] According to an aspect of embodiments herein, the object is achieved by a methodperformed by a network exposure node e.g., for handling events in a communication network. The network exposure node receives a first status request for current status related to an event type from an application node. The request comprises the event type.

[0016] The network exposure node requests the current status related to the requested event type.

[0017] The network exposure node receives a status response for the requested event type indicating the current status related to the requested event type.

[0018] The network exposure node sends the status response the application node.

[0019] According to another aspect of embodiments herein, the object is achieved by a method performed by an application node e.g., for handling events in a communication network.

[0020] The application node sends a first status request to a network exposure node. The request requesting the current event status related to an event type.

[0021] The application node receives the current status related to the requested event type from the network exposure node.

[0022] According to another aspect of embodiments herein, the object is achieved by a method performed by a subscriber data node e.g., for handling events in a communication network.

[0023] The subscriber data node receives a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node. The second request comprising at least one of the event type and an IMS subscriber identity (ID).

[0024] The subscriber data node obtains an IMS application server associated with the subscriber ID.

[0025] The subscriber data node performs an action associated with the second request.

[0026] According to another aspect of embodiments herein, the object is achieved by a method performed by an IMS application server e.g., for handling events in a communication network.

[0027] The IMS application server receives a request for current event status related to an event type from a subscriber data node or a network exposure node.

[0028] The IMS application server sends a response indicating the current event status to the subscriber data node or the network exposure node.

[0029] It is furthermore provided herein a computer program, which, when executed on at least one processor, causes the at least one processor to carry out the methods herein, as performed by the network exposure node, the application node, the subscriber data node and the IMS applications server, respectively. It is additionally provided herein a carrier, having stored there on a computer program comprising instructions which, when executed on at leastone processor, causes at least one processor to carry out the methods herein, as performed by the UE and the radio network node, respectively.

[0030] According to another aspect, the object is achieved by providing a network exposure node e.g., configured to handle events in a communication network. The network exposure node is further configured to:

[0031] - receive a first status request for current status related to an event type from an application node, the request comprising the event type,

[0032] - request the current status related to the requested event type,

[0033] - receive a status response for the requested event type indicating the current status related to the requested event type,

[0034] - send the status response the application node.

[0035] According to another aspect, the object is achieved by providing an application node e.g., configured to handle events in a communication network. The application node is further configured to:

[0036] - send a first status request to a network exposure node, the request adapted to request the current event status related to an event type, and

[0037] - receive the current status related to the requested event type from the network exposure node.

[0038] According to another aspect the object is achieved by providing a subscriber data node e.g., configured to handle events in a communication network. The subscriber data node is further configured to:

[0039] - receive a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node, the second request adapted to comprise at least one of the event type and an IMS subscriber ID.

[0040] - obtain an IMS application server associated with the subscriber ID, and

[0041] - perform an action associated with the second request.

[0042] According to another aspect the object is achieved by providing an IMS application server e.g., configured to handle events in a communication network. The IMS application server is further configured to:

[0043] - receive a request for current event status related to an event type from a subscriber data node or a network exposure node, and

[0044] - send a response adapted to indicate the current event status to the subscriber data node or the network exposure node.BRIEF DESCRIPTION OF THE DRAWINGS

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

[0046] Figure 1 is a schematic diagram illustrating a non-limiting example of a communication network, according to embodiments herein.

[0047] Figure 2 is a flowchart depicting embodiments of a method in a network exposure node, according to embodiments herein.

[0048] Figure 3 is a flowchart depicting embodiments of a method in an application node, according to embodiments herein.

[0049] Figure 4 is a flowchart depicting embodiments of a method in a subscriber data node, according to embodiments herein.

[0050] Figure 5 is a flowchart depicting embodiments of a method in an IMS application server, according to embodiments herein.

[0051] Figure 6 is a schematic diagram illustrating a non-limiting example according to embodiments herein.

[0052] Figure 7 is a schematic diagram illustrating a non-limiting example according to embodiments herein.

[0053] Figure 8 is a schematic block diagram illustrating a non-limiting example of a network exposure node, according to embodiments herein.

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

[0055] Figure 10 is a schematic block diagram illustrating a non-limiting example of a subscriber data node, according to embodiments herein.

[0056] Figure 11 is a schematic block diagram illustrating a non-limiting example of an IMS application server, according to embodiments herein.

[0057] DETAILED DESCRIPTION

[0058] As part of the development of embodiments herein, one or more challenges with the existing technology will first be identified and discussed.

[0059] The Subscribe / Notify Framework enables third party AF and network functions to subscribe to and be notified about IMS events.

[0060] The framework inherits the Event Reporting Information defined in 5GC by which the AF consumer can request e.g. the current status related to the subscribed event type in the response to the subscription request and a maximum number of event report notifications.However, the framework does not currently enable an explicit procedure to retrieve the current status related to the requested event type. This can be critical if the AF requires the knowledge of the current status related to an event type e.g. before taking the decision to subscribe to that particular event type or when just the current status is relevant for the AF.

[0061] Neither 5GC nor IMS event exposure frameworks provides an explicit procedure to retrieve the current status related to a requested event type.

[0062] However, there are many use cases where the applications are not really interested in the event itself but rather on the status. For example, some Use Cases require to know just the current IMEI or whether the user is busy in a call right now, e.g. for bank fraud prevention.

[0063] The knowledge of the status can be also useful if the AF consumer requires the knowledge of the current status related to an event type e.g. before taking the decision to subscribe to a particular event type. For example, an application checks if UE is reachable before executing a procedure and if not reachable then subscribes for reachability event.

[0064] It has been observed already in 5GC deployments realizing exposure use cases, that the lack of this explicit event status retrieval procedure, makes developers misuse the subscribe operation to serve the purpose of a status retrieval operation. Subscribe request includes the Immediate Reporting Flag to receive the current status in the response to the subscribe request and maximum number of event report notifications is set to its minimum value of 1.

[0065] Given that the consumer does not know whether the current status is available in 5GC at the moment of subscription for certain subscribed event types, if the consumer is interested in a one-time notification upon event detection, there is no deterministic way for the consumer to ensure that it will receive a first (and unique) event detection if additionally the current related status of the subscribed event is detected.

[0066] While this can serve the purpose of the AF to become aware of the current status related to an event type, the use of the subscribe request / response in this way is far from optimal from a protocol and resource management point of view.

[0067] This is also creating interoperability issues as at least one notification is provided to the Network Exposure Function (NEF) / AF as requested by the maximum number of reports while some implementations interpret that the current status in the response of the subscribe request serves already as the only notification report requested.

[0068] An explicit and optimized procedure for event status retrieval is therefore required to avoid the misuse of the subscribe operations and avoid interoperability issues.

[0069] Embodiments herein relate to events and event status and handling thereof.As mentioned above, an object of embodiments herein is to handle events in a communication network in an efficient manner and improve the performance of the communication network.

[0070] Embodiments herein provides methods for an explicit and optimized procedure for event status retrieval.

[0071] According to examples of embodiments herein, new service operations under the NEF, Home Subscriber Server (HSS) and IMS Application Server (AS) ImsEventExposure service set of the IMS event exposure framework are provided so that an AF can get the current status related to an IMS event. The new service operation may e.g., be referred to as a GetStatus service operation. The same would apply to the EventExposure service set of the NEF, Unified Data Management (UDM) and other NFs of the 5GC event exposure framework.

[0072] Examples of embodiments herein, provide the advantage of an explicit procedure for event status retrieval that optimizes protocol interactions and resource handling and avoids interoperability issues. Thus, the performance of the communication network is improved.

[0073] Embodiments herein relate to wireless communication networks in general. Figure 1 is a schematic overview depicting a communication network 100. The communication network 100 comprises one or more RANs and one or more CNs. The communication network 100 may be a 5G system, or a newer system supporting similar functionality, such as for example, a Sixth Generation (6G) system. In some examples, the wireless communication network may support, additionally or alternatively, a Long-Term Evolution (LTE) network and may support other technologies such as a for example, LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), and LTE operating in an unlicensed band. The telecommunications system may also support other technologies, such as Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communications (GSM) network, GSM / Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising any combination of Radio Access Technologies (RATs) such as e.g. MultiStandard Radio (MSR) base stations, multi-RAT base stations etc., any 3rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network / s (WLAN) or WiFi network / s, Worldwide Interoperability for Microwave Access (WiMax), IEEE 802.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system. The telecommunications system may for example support a Low Power Wide AreaNetwork (LPWAN). LPWAN technologies may comprise Long Range physical layer protocol (LoRa), Haystack, SigFox, LTE-M, and Narrow-Band loT (NB-loT).

[0074] A number of network nodes operate in the communication network 100 such as e.g. a radio network node 101. These nodes provide radio coverage in a number of cells which may also be referred to as a beam or a beam group of beams.

[0075] The radio network node 101 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), a 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 standalone access point, a network controlled repeater or any other network unit capable of communicating with a wireless device within the service area served by the radio network node 101 depending e.g. on the first radio access technology and terminology used. The radio network node 101 may be referred to as a serving radio network node and communicates with a UE 121 with Downlink (DL) transmissions to the UE 121 and Uplink (UL) transmissions from the UE 121.

[0076] In some examples, the communication network 100 may comprise an access network, such as a radio access network (RAN), and a core network, which may include one or more core network nodes. The access network may include one or more access network nodes, such as the radio network node 101, e.g., which may be generally referred to as network nodes, 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 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network may include one or more Open-RAN (ORAN) network nodes. An ORAN network node may be understood as a node in the telecommunication network that may support 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, including one or more network nodes and / or core network nodes.

[0077] 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, theadjective “open” designating support of an ORAN specification. The radio network node 140 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, in which one or more network functions may be virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The radio network node 140 may facilitate direct or indirect connection of user equipment (UE), such as by connecting the device 130 to the core network over one or more wireless connections.

[0078] In the communication network 100, one or more wireless devices operate, such as e.g. a UE 121. The UE 121 may be also known as a e.g., device, wireless device, mobile terminal, wireless terminal and / or mobile station, mobile telephone, cellular telephone, or laptop with wireless capability, an Internet of Things (loT) device, or a Customer Premises Equipment (CPE), just to mention some further examples. The device 130 in the present context may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via a RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, a Machine-to-Machine (M2M) device, an Internet of Things (loT) device, e.g., a sensor or a camera, a device equipped with a wireless interface, such as a printer or a file storage device, modem, Laptop Embedded Equipped (LEE), Laptop Mounted Equipment (LME), USB dongles, CPE or any other radio network unit capable of communicating over a radio link in the communication network 100. The UE 121 may be wireless, i.e., it may be enabled to communicate wirelessly in the communication network 100 and, in some particular examples, may be able support transmission using beamforming. The communication may be performed e.g., between two devices, between a device and a radio network node, and / or between a device and a server. The communication may be performed e.g., via a RAN and possibly one or more core networks, comprised, respectively, within the communication network 100.

[0079] The communication network 100 may further comprise an IMS network 105. The IMS network 105 may e.g., comprise an IMS application server 160 providing services to IMS subscriber.

[0080] The communication network further comprises a subscriber data node 150, such as an HSS 150, a network exposure node 140, such as a NEF 140, and an application node 130, such as an AF 130.

[0081] Methods herein may be performed by the network exposure node 140, the application node 130, the subscriber data node 150 and the IMS application server 160 respectively. Asan alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 1, may be used for performing or partly performing the methods herein.

[0082] The above-described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0083] A method according to embodiments will now be described from the view of the network exposure node 140 together with Figure 2. Figure 2 shows example embodiments of a method performed by the network exposure node 140 for handling events in the communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 2.

[0084] Action 201

[0085] The network exposure node 140 receives a first status request for current status related to an event type from an application node 130. The request comprises the event type. In other words, the first request indicates the event type the application node 130 is requesting the current status for. The first request message may also be referred to as a status request message. The first request may e.g., be a Nnef_imsEE_GetStatus Request message. The first request message may e.g., be a service operation in the IMS event exposure framework.

[0086] In some embodiments, the event type comprises any one out of a subscriber specific IMS event type, or a non-subscriber specific IMS event type. A subscriber specific event type may e.g., be understood as an event type that is related to a subscriber. An example of a subscriber specific event, or event type, may e.g., comprise a registration status of a subscriber. A non-subscriber specific event type may e.g., be understood as an event type that is not related to a subscriber.

[0087] In some embodiments, the first status request may indicate one or more IMS subscriber IDs for which the current status related to the event type is requested. Thus, the first status request may indicate the subscribers that the application node 130 requests the current status related to the event type for. The one or more IMS subscriber IDs are included in the message when the event type is a subscriber specific event type. That is the application node 130 may request event status for more than one subscribers, then the network exposure node 140 may split that one request per subscriber.

[0088] Action 202The network exposure node 140 requests the current status of the requested event type. Requesting the current status of the event type may be performed in different ways, e.g., depending on whether the event type is subscriber specific or non-subscriber specific.

[0089] In some embodiments, requesting the status of the requested event type comprises sending a second request indicating the event type to the subscriber data node 150 or one or more IMS application servers 160.

[0090] In some examples, the network exposure node 140 may send a respective second request for each IMS subscriber ID indicated in the first status request. The respective second request is sent to the subscriber data node 150. The respective second request requests the current status for the event type for the subscriber ID indicated in the second request. The respective second request indicates the IMS subscriber ID for the current status requested. The respective second request may also be referred to as a status request message. The respective second request may be a GetStatus or GET message, e.g., a Nhss_imsEE_GetStatus Request message. The respective second request may e.g., be a service operation in the IMS event exposure framework. The respective second request may further comprise, such as indicate, the event type.

[0091] In some examples, the network exposure node 140 may send a second request to the subscriber data node 150. The second request requests a respective IMS application server address for the one or each IMS subscriber ID. The IMS application server address may comprise the address to an IMS application server 160 assigned to an IMS subscriber ID. The second request may e.g., be a Nhss_UECM_AslnfoGet Request message. The network exposure node 140 may send a respective second request for each IMS subscriber ID to the subscriber data node 150. Alternatively, the network exposure node 140 may send one second request to the subscriber data node 150, where the second request comprises all IMS subscriber IDs in the first status request.

[0092] In some examples, the network exposure node 140 may send a second request to one or more IMS application servers 160 supporting the requested event type. In this example, prior to sending the second request, the network exposure node 140 NEF obtains the IMS application servers 160, such as IMS application server instances, that support the requested event type. The network exposure node 14 may e.g., be configured with this information, or IMS application servers 160 may be obtained from a network repository function (NRF).

[0093] In some embodiments, requesting the current status of the requested event type may further comprise receiving the respective IMS application server 160 address for each IMS subscriber ID. The respective IMS application server 160 address may be received from the subscriber data node 150. The IMS application server 160 address may e.g., be received in a Nhss_UECM_AslnfoGet Response message. The network exposure node 140 may receiveone message for each IMS subscriber ID, or one message comprising the IMS application server 160 addresses for all IMS subscriber IDs.

[0094] In some embodiments, the network exposure node 140 may send a respective third request for each IMS subscriber ID to the IMS application server 160 assigned to each IMS subscriber respectively. The respective third request may also be referred to as a status request message. The respective third request may e.g., be a Nimsas_imsEE_GetStatus Request message. The respective third request may e.g., be a service operation in the IMS event exposure framework. The respective third request may further comprise, such as indicate, the event type and the IMS subscriber ID the current status of the event type is requested for.

[0095] Action 203

[0096] The network exposure node 140 receives a status response. The status response indicates the current status related to requested event type. The status response may e.g., be a Nhss_imsEE_GetStatus Response message or a Nimsas_imsEE_GetStatus Response message, depending on whether the status response is received from the subscriber data node 150 or the IMS application server 160. The status response may e.g., be a service operation in the IMS event exposure framework.

[0097] In some embodiments, the status response may be received from the subscriber data node 150 or the one or more IMS application servers 160. The network exposure node 140 may e.g., receive one status response for each of the one or more IMS subscriber IDs from the subscriber data node 150 when the event type is a subscriber specific event type.

[0098] Alternatively, the network exposure node 140 may receive one status response from each IMS application server 160 when the event type is a non-subscriber specific event type.

[0099] Action 204

[0100] The network node 140 sends the status response to the application node 130. The status response may e.g., be a Nnef_imsEE_GetStatus Response message. The status response may e.g., be a service operation in the IMS event exposure framework. The network exposure node 140 may e.g., send one status response for each of the one or more IMS subscriber IDs. Alternatively, the network exposure node 140 may send one status response received from each IMS application server 160 when the event type is a non-subscriber specific event type.

[0101] A method according to embodiments will now be described from the view of the application node 130 together with Figure 3. Figure 3 shows example embodiments of a method performed by application node 130 for handling events in the communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 3.Action 301

[0102] The application node 130 sends a first status request to the network exposure node 140. The request requests the current event status related to an event type. In other words, the first request indicates the event type the application node 130 is requesting the current status for. The first request message may also be referred to as a status request message. The first request may e.g., be a Nnef_imsEE_GetStatus Request message. The first request message may e.g., be a service operation in the IMS event exposure framework. The first request may further comprise the event type.

[0103] In some embodiments, the event type may comprise any one out of a subscriber specific IMS event type, or a non-subscriber specific IMS event type. A subscriber specific event type may e.g., be understood as an event type that is related to a subscriber. An example of a subscriber specific event, or event type, may e.g., comprise a registration status of a subscriber. A non-subscriber specific event type may e.g., be understood as an event type that is not related to a subscriber.

[0104] In some embodiments, the first status request may indicate one or more IMS subscriber IDs for which the current status related to the event type is requested. Thus, the first status request may indicate the subscribers that the application node 130 request the current status related to the event type for. The one or more IMS subscriber IDs are included in the message when the event type is a subscriber specific event type.

[0105] Action 302

[0106] The application node 130 receives the current status, such as the status response, related to the requested event type from the network exposure node 140. The status response may e.g., be a Nnef_imsEE_GetStatus Response message. The status response may e.g., be a service operation in the IMS event exposure framework. The application node 130 may e.g., receive one status response for each of the one or more IMS subscriber IDs. Alternatively, the application node 130 may receive one status response from each IMS application server 160 when the event type is a non-subscriber specific event type.

[0107] A method according to embodiments will now be described from the view of the subscriber data node 150 together with Figure 4. Figure 4 shows example embodiments of a method performed by the subscriber data node 150 for handling events in the communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 4.

[0108] Action 401

[0109] The subscriber data node 150 receives a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node 140. The second request comprises at least one of the event type and a subscriber ID.In some examples, the second request requests the current status related to the event type for the subscriber ID indicated in the second request. The respective second request indicates the IMS subscriber ID for the current status that is requested. The second request may also be referred to as a status request message. The second request may e.g., be a Nhss_imsEE_GetStatus Request message. The second request may e.g., be a service operation in the IMS event exposure framework. The second request may further comprise, such as indicate, the event type.

[0110] In some examples, the second request requests an IMS application server address for the IMS subscriber ID. The IMS application server address may comprise the address to an IMS application server 160 assigned to the IMS subscriber ID. The second request may e.g., be a Nhss_UECM_AslnfoGet Request message.

[0111] In some embodiments, the second request may comprise a notification address associated with the network exposure node 140. The notification address may e.g., allow an IMS application server 160 to provide the current status directly to the network exposure node 140.

[0112] In some embodiments, the event type comprises any one out of a subscriber specific IMS event type, or a non-subscriber specific IMS event type. A subscriber specific event type may e.g., be understood as an event type that is related to a subscriber. An example of a subscriber specific event, or event type, may e.g., comprise a registration status of a subscriber. A non-subscriber specific event type may e.g., be understood as an event type that is not related to a subscriber.

[0113] Action 402

[0114] The subscriber data node 150 obtains an IMS application server 160 associated with the subscriber ID. The IMS application server 160 associated with the subscriber ID may e.g., be an IMS application server 160 instance assigned to the subscribed ID during registration. The IMS application server 160 instance is stored in the context associated with the subscriber ID. The context is stored in the subscriber data node 150.

[0115] Action 403

[0116] The subscriber data node 150 performs an action associated with the second request. The action may depend on the second request received from the network exposure node 140.

[0117] In some embodiments, performing the action may comprise sending a respective address of the respective obtained IMS application servers 160 to the network exposure node 140. The IMS application server 160 address may e.g., be sent in a Nhss_UECM_AslnfoGet Response message. The subscriber data node 150 may send one message for each IMS subscriber ID, or one message comprising the IMS application server 160 addresses for all IMS subscriber IDs.Alternatively, or additionally, performing the action may comprise requesting a current status related to the requested event type from the respective obtained IMS application server 160. Requesting the current status may e.g., comprise sending a status request to the obtained IMS application server 160. The status request requests the current status related to the event type for the subscriber ID indicated in the second request. The status request indicates the IMS subscriber ID for the current status that is requested. The status request may also be referred to as a status request message. The status request may e.g., be a Nimsas_imsEE_GetStatus Request message. The status request may e.g., be a service operation in the IMS event exposure framework. The status request may further comprise, such as indicate, the event type. The status request may in some examples indicate, such as comprise, the notification address of the network exposure node 140.

[0118] Requesting the current status related to the requested event type may further comprise receiving the current event status from the IMS application servers 160. The current status may e.g., be received in a status response message, such as a Nimsas_imsEE_GetStatus Response message.

[0119] Alternatively, or additionally, performing the action may comprise sending a response for the event type to the network exposure node 140. The response indicates the current event status related to the requested event type for the subscriber ID. The status response may e.g., be a Nhss_imsEE_GetStatus Response message. The status response may e.g., be a service operation in the IMS event exposure framework.

[0120] A method according to embodiments will now be described from the view of the IMS application server 160 together with Figure 5. Figure 5 shows example embodiments of a method performed by the IMS application server 160 for handling events in the communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 5.

[0121] Action 501

[0122] The IMS application server 160 receives a request for current event status related to an event type from the subscriber data node 150 or the network exposure node 140.

[0123] In some examples, the request may e.g., comprise the third request received from the network exposure node 140. The third request may also be referred to as a status request message. The third request may e.g., be a Nimsas_imsEE_GetStatus Request message. The third request may e.g., be a service operation in the IMS event exposure framework. The third request may further comprise, such as indicate, the event type and the IMS subscriber ID the current status of the event type is requested for.

[0124] In some examples, the request may e.g., comprise the second request received from the network exposure node 140. The second request may also be referred to as a status requestmessage. The second request may e.g., be a Nimsas_imsEE_GetStatus Request message. The second request may e.g., be a service operation in the IMS event exposure framework. The third request may further comprise, such as indicate, the event type the current status of the event type is requested for.

[0125] In some examples, the request may e.g., comprise a status request received from the subscriber data node 150. The status request requests the current status related to the event type for the subscriber ID indicated in the status request. The status request indicates the IMS subscriber ID for the current status is requested for. The status request may also be referred to as a status request message. The status request may e.g., be a Nimsas_imsEE_GetStatus Request message. The status request may e.g., be a service operation in the IMS event exposure framework. The status request may further comprise, such as indicate, the event type. The status request may in some examples indicate, such as comprise, the notification address of the network exposure node 140.

[0126] In some embodiments, the event type comprises any one out of a subscriber specific IMS event type, or a non-subscriber specific IMS event type. A subscriber specific event type may e.g., be understood as an event type that is related to a subscriber. An example of a subscriber specific event, or event type, may e.g., comprise a registration status of a subscriber. A non-subscriber specific event type may e.g., be understood as an event type that is not related to a subscriber.

[0127] Action 502

[0128] The IMS application server 160 sends a response indicating the current event status related to the event type to the subscriber data node 150 or the network exposure node 140. The status response may e.g., be an Nimsas_imsEE_GetStatus Response message. The status response may e.g., be a service operation in the IMS event exposure framework.

[0129] The status response may e.g., be sent to the subscriber data node 150 in response to receiving the status request from the subscriber data node 150.

[0130] Alternatively, the status response may be sent to the network exposure node 140 in response to the second request or third request received from the network exposure node 140. Additionally, the status response may be sent to the network exposure node 140 in response to receiving the status request from the subscriber data node 150, when the status request comprises the notification address of the network exposure node 140.

[0131] 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.Embodiments here propose a new operation to request the current status related to an IMS event type. This allows an AF consumer, such as the application node 130, to retrieve the current status of an event type, e.g. before taking the decision to subscribe to a particular event.

[0132] For subscriber specific events, the NEF, such as the network exposure node 140 retrieves the current status related to the requested IMS event type to the IMS AS via the HSS. For non-subscriber specific events, the NEF retrieves the current status related to the requested IMS event type directly from the IMS AS.

[0133] Examples of embodiment herein describe the event status retrieval procedure for subscriber specific IMS events and for non-subscriber specific events. Similar procedure applies for the event exposure framework in 5GC.

[0134] Figure 6 shows an example of a signalling flow diagram for requesting the retrieval of the current status related to a subscriber specific IMS event type according to examples of embodiments herein.

[0135] 5601. A UE 121, such as the wireless device 121, performs an initial IMS Registration and is assigned an IMS AS 160, such as the IMS application server 160, instance that is registered in an HSS 150, such as the subscriber data node 150.

[0136] 5602. An AF 130, such as the application node 130, requests the current status related to a subscriber specific IMS event type from a NEF 140, such as the network exposure node 140. This may e.g., be performed by initiating, such as sending, a Nnef_imsEE_GetStatus Request. The AF may include one or more IMS subscriber IDs in the request, as well as the event type.

[0137] 5603. The NEF 140 initiates, such as sends, for each IMS subscriber, indicated by the one or more IMS subscriber IDs, in the incoming event status request a separate event status request towards the HSS 150 for the requested event type, e.g., via a Nhss_lmsEE_GetStatus Request service operation.

[0138] 5604. The HSS 150 locates the IMS AS 160 instance serving the UE 121 based on the IMS AS registration in HSS executed in S601. The HSS 150 determines if the IMS AS instance for the IMS subscriber, such as the IP Multimedia Public Identity (IMPU) supports the requested IMS event based on the NF profile of the registered IMS AS 160 instances stored in NRF.

[0139] If the UE 121 is not IMS registered in HSS 150, S605 and S606 are skipped.

[0140] 5605. The HSS 150 sends the event status request to the IMS AS 160 instance serving the UE 121 and supporting the requested IMS event, e.g., using Nimsas_lmsEE_GetStatus Request for the requested IMS event including the IMPU. Alternatively, the HSS 150 may usean Sh interface to send the event status request to the IMS AS 160 instance assigned to the UE 121.

[0141] 5606. The IMS AS 160 returns to HSS 150 the current status related to the requested subscriber specific IMS event type, e.g., with an Nimsas_lmsEE_GetStatus Response or via Sh interface.

[0142] 5607. The HSS 150 returns to the NEF 140 the current status related to the requested subscriber specific IMS event type, e.g., with an Nhss_lmsEE_GetStatus Response.

[0143] 5608. The NEF 140 returns to the AF 130 the current status related to the requested subscriber specific IMS event type, e.g., with an Nnef_lmsEE_GetStatus Response.

[0144] Figure 7 shows an example of a signalling flow diagram for requesting the retrieval of the current status related to a non-subscriber specific IMS event type according to examples of embodiments herein.

[0145] 5701. The AF 130 requests the current status related to a non-subscriber specific IMS event type from the NEF 140. This may e.g., be performed by initiating, such as sending, a Nnef_imsEE_GetStatus Request. The AF 130 may include the event type in the request.

[0146] 5702. The NEF 140 locates the IMS AS 160 instances that support the requested IMS event, e.g., via NRF or by local configuration.

[0147] 5703. For each IMS AS 160 instance that supports the requested IMS event, the NEF 140 initiates a separate event status request, e.g., using an Nimsas_lmsEE_GetStatus Request, for the requested IMS event.

[0148] 5704. The IMS AS 160 returns to NEF 140 the current status related to the requested non-subscriber specific IMS event type, e.g., with the Nimsas_lmsEE_GetStatus Response.

[0149] 5705. The NEF 140 returns to the AF 130 the current status related to the requested non-subscriber specific IMS event type, e.g., with the Nnef_lmsEE_GetStatus Response.

[0150] According to some examples of embodiments herein, for the retrieval of the current status related to a subscriber specific IMS event type depicted in Figure 6, the NEF 140 may include in the request to the HSS 150 a NEF notification address. The HSS 150 forwards this NEF 140 notification address in the request to the IMS AS 160 so that the IMS AS 160 may send the event status report directly to the NEF 140.

[0151] Alternatively, the NEF 140 could first retrieve from the HSS 150 the IMS AS 160 instance address assigned to the UE 121, e.g., via Nhss_UECM_AslnfoGet service operation, as currently defined in 3GPP TS 23.228 v19.2.0, and then request the current event status directly from the IMS AS 160 instances provided by the HSS 150.Figure 8 depicts an example of the arrangement that the network exposure node 140 may comprise to perform the method described with reference to Figure 2. The network exposure node 140 may be understood to be for handling Sounding Reference Signal (SRS) events. The network exposure node 140 is configured to operate in the communication network 100.

[0152] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0153] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the network exposure node 140 and will thus not be repeated here to simplify the description.

[0154] The network exposure node 140 may comprise an input and output interface 10 configured to communicate with each other. The input and output interface 10 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0155] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 11 of a processing circuitry in the network exposure node 140 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 network exposure 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 network exposure node 140.

[0156] The network exposure node 140 and / or processor 11 is configured to handle events in the communication network 100.

[0157] The network exposure node 140 and / or processor 11 is configured to receive a first status request for current status related to an event type from an application node 130. The request comprises the event type.

[0158] The network exposure node 140 and / or processor 11 is configured to request the current status related to the requested event type.

[0159] The network exposure node 140 and / or processor 11 is configured to receive a status response for the requested event type indicating the current status related to the requested event type.The network exposure node 140 and / or processor 11 is configured to send the status response to the application node 130.

[0160] In some embodiments, the event type is adapted to comprise any one out of:

[0161] - a subscriber specific Internet Protocol Multimedia Subsystem, IMS, event type, or - a non-subscriber specific IMS event type.

[0162] In some embodiments, the network exposure node 140 and / or processor 11 may further be configured to request the status of the requested event type by further being configured to send a second request indicating the event type to a subscriber data node 150 or one or more IMS application servers 160.

[0163] In some embodiments, to send the second request is adapted to comprise any one out of:

[0164] - send a respective second request for each IMS subscriber ID indicated in the first status request to a subscriber data node 150, the respective second request is adapted to request the current status related to the event type for a subscriber ID,

[0165] - send a second request to the subscriber data node 150, the second request is adapted to request a respective IMS application server address for each IMS subscriber ID,

[0166] - send a second request to one or more IMS application servers 160 supporting the requested event type.

[0167] In some embodiments, the network exposure node 140 and / or processor 11 may further be configured to request the current status related to the requested event type by further being configured to obtain the one or more IMS application servers 160 supporting the requested event types.

[0168] In some embodiments, the network exposure node 140 and / or processor 11 may further be configured to request the current status related to the requested event type by further being configured to receive the respective IMS application server 160 address for each IMS subscriber ID, and send a respective third request for each IMS subscriber ID to the IMS application server 160 assigned to each IMS subscriber respectively.

[0169] In some embodiments, the network exposure node 140 and / or processor 11 may further be configured to receive the status response from any one out of the subscriber data node 150 or the one or more IMS application servers 160.

[0170] In some embodiments, the first status request is adapted to indicate one or more IMS subscriber IDs for which the current status related to the event type is requested.

[0171] The network exposure node 140 may further comprise a memory 12 comprising one or more memory units. The memory 12 comprises instructions executable by the processor 11 in the network exposure node 140.

[0172] The memory 12 is arranged to be used to store instructions, data, configurations, packets, identities, events, event types, addresses, IMS application servers, event status, andapplications to perform the methods herein when being executed in the network exposure node 140.

[0173] In some embodiments, a computer program 13 comprises instructions, which when executed by the at least one processor 11 , cause the at least one processor 11 of the network exposure node 140 to perform the actions above.

[0174] In some embodiments, a respective carrier 14 comprises the respective computer program 13, wherein the carrier 14 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.

[0175] Thus, embodiments herein may disclose the network exposure node 140 configured to handle events. The network exposure node 140 is configured to operate in the communication network 100. The network exposure node 140 comprises the processor 11 and the memory 12, said memory 12 comprising instructions executable by said processor 11 whereby said network exposure node 140 is operative to perform any of the methods herein.

[0176] 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 applicationspecific 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 radio network node, for example.

[0177] 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 non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receiverswill appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0178] 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 digitalsignal 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.

[0179] Figure 9 depicts an example of the arrangement that the application node 130 may comprise to perform the method described with reference to Figure 3. The application node 130 may be understood to be for handling events. The application node 130 is configured to operate in the communication network 100.

[0180] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0181] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the application node 130 and will thus not be repeated here to simplify the description.

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

[0183] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 21 of a processing circuitry in the application node 130 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 application node 130. 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 application node 130.

[0184] The application node 130 and / or processor 21 is configured to handle events in the communication network 100.The application node 130 and / or processor 21 send a first status request to a network exposure node 140. The request is adapted to request the current event status related to an event type.

[0185] The application node 130 and / or processor 21 receive the current status related to the requested event type from the network exposure node 140.

[0186] In some embodiments, the event type is adapted to comprise any one out of:

[0187] - a subscriber specific Internet Protocol Multimedia Subsystem, IMS, event type, or - a non-subscriber specific IMS event type.

[0188] In some embodiments, the first request is adapted to comprise one or more IMS subscriber identities, ID, the event status is requested for.

[0189] The application node 130 may further comprise a memory 22 comprising one or more memory units. The memory 22 comprises instructions executable by the processor 21 in the application node 130.

[0190] The memory 12 is arranged to be used to store instructions, data, configurations, packets, identities, events, event types, addresses, IMS application servers, event status, and applications to perform the methods herein when being executed in the application node 130.

[0191] In some embodiments, a computer program 23 comprises instructions, which when executed by the at least one processor 21 , cause the at least one processor 21 of the application node 130 to perform the actions above.

[0192] In some embodiments, a respective carrier 24 comprises the respective computer program 23, wherein the carrier 24 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.

[0193] Thus, embodiments herein may disclose the application node 130 configured to handle events. The application node 130 is configured to operate in the communication network 100. The application node 130 comprises the processor 21 and the memory 22, said memory 22 comprising instructions executable by said processor 21 whereby said application node 130 is operative to perform any of the methods herein.

[0194] 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 applicationspecific 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 radio network node, for example.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 non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receiverswill appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0195] 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.

[0196] Figure 10 depicts an example of the arrangement that the subscriber data node 150 may comprise to perform the method described with reference to Figure 4. The subscriber data node 150 may be understood to be for handling events. The subscriber data node 150 is configured to operate in communication network 100.

[0197] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0198] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the subscriber data node 150 and will thus not be repeated here to simplify the description.The subscriber data node 150 may comprise an input and output interface 30 configured to communicate with each other. The input and output interface 30 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0199] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 31 of a processing circuitry in the subscriber data 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 subscriber data 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 subscriber data node 150.

[0200] The subscriber data node 150 and / or processor 31 is configured to handle events in communication network 100.

[0201] The subscriber data node 150 and / or processor 31 is configured to receive a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node 140. The second request is adapted to comprise at least one of the event type and an IMS subscriber ID.

[0202] The subscriber data node 150 and / or processor 31 is configured to obtain an IMS application server 160 associated with the subscriber ID.

[0203] The subscriber data node 150 and / or processor 31 is configured to perform an action associated with the second request.

[0204] In some embodiments, the subscriber data node 150 and / or processor 31 may further be configured to perform the action associated with second request by further being configured to any one out of:

[0205] - send an address of the obtained IMS application server 160 to the network exposure node 140, or

[0206] - request a current status related to the requested event type from the obtained IMS application server 160, and

[0207] - send a status response for the event type to the network exposure node 140, the status response adapted to indicate the current event status related to the requested event type for the subscriber ID.

[0208] In some embodiments, the second request is adapted to comprise a notification address associated with the network exposure node 140, and wherein to request the current statusrelated to the requested event type is adapted to comprise to indicate the notification address to the IMS application server 160.

[0209] In some embodiments, the subscriber data node 150 and / or processor 31 may further be configured to request the current status related to the requested event type by further being configured to receive the current event status from the IMS application server 160.

[0210] The subscriber data node 150 may further comprise a memory 32 comprising one or more memory units. The memory 32 comprises instructions executable by the processor 31 in the subscriber data node 150.

[0211] The memory 12 is arranged to be used to store instructions, data, configurations, packets, identities, events, event types, addresses, IMS application servers, event status, and applications to perform the methods herein when being executed in the subscriber data node 150.

[0212] In some embodiments, a computer program 33 comprises instructions, which when executed by the at least one processor 31 , cause the at least one processor 31 of the subscriber data node 150 to perform the actions above.

[0213] In some embodiments, a respective carrier 34 comprises the respective computer program 33, wherein the carrier 34 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.

[0214] Thus, embodiments herein may disclose the subscriber data node 150 configured to handle events. The subscriber data node 150 is configured to operate in the communication network 100. The subscriber data node 150 comprises the processor 31 and the memory 32, said memory 32 comprising instructions executable by said processor 31 whereby said subscriber data node 150 is operative to perform any of the methods herein.

[0215] 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 applicationspecific 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 radio network node, for example.

[0216] Alternatively, several of the functional elements of the processing means discussed may be provided using 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 non-volatile 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.

[0217] 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.

[0218] Figure 11 depicts an example of the arrangement that the IMS application server 160 may comprise to perform the method described in Figure 5. The IMS application server 160 may be understood to be for handling events. The IMS application server 160 is configured to operate in the communication network 100.

[0219] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0220] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the IMS application server 160 and will thus not be repeated here to simplify the description.

[0221] The IMS application server 160 may comprise an input and output interface 40 configured to communicate with each other. The input and output interface 40 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0222] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 41 of a processing circuitry in the IMSapplication server 160 depicted in Figure 11, 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 IMS application server 160. 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 application server 160.

[0223] The IMS application server (160) and / or processor 41 is configured to handle events in the communication network (100).

[0224] The IMS application server (160) and / or processor 41 is configured to receive a request for current event status related to an event type from a subscriber data node (150) or a network exposure node (140).

[0225] The IMS application server (160) and / or processor 41 is configured to send a response adapted to indicate the current event status to the subscriber data node (150) or the network exposure node (140).

[0226] In some embodiments, the event type is adapted to comprise any one out of:

[0227] - a subscriber specific IMS event type, or

[0228] - a non-subscriber specific IMS event type.

[0229] In some embodiments, the request is adapted to indicate the event type.

[0230] In some embodiments, the request is adapted to indicate a subscriber identity, ID, the current event status is requested for. The response is adapted to indicate the current event status for the subscriber ID.

[0231] In some embodiments, the request is adapted to comprise a notification address associated with the network exposure node 140. The IMS application server 160 and / or processor 41 is configured to send the response by further being configured to send the response to the network exposure node 140 using the notification address.

[0232] The IMS application server 160 may further comprise a memory 42 comprising one or more memory units. The memory 42 comprises instructions executable by the processor 41 in the IMS application server 160.

[0233] The memory 42 is arranged to be used to store instructions, data, configurations, packets, identities, events, event types, addresses, IMS application servers, event status, and applications to perform the methods herein when being executed in the IMS application server 160.

[0234] In some embodiments, a computer program 43 comprises instructions, which when executed by the at least one processor 41 , cause the at least one processor 41 of the IMS application server 160 to perform the actions above.In some embodiments, a respective carrier 44 comprises the respective computer program 43, wherein the carrier 44 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.

[0235] Thus, embodiments herein may disclose the IMS application server 160 configured to handle events. The IMS application server 160 is configured to operate in the communication network 100. The IMS application server 160 comprises the processor 41 and the memory 42, said memory 42 comprising instructions executable by said processor 41 whereby said IMS application server 160 is operative to perform any of the methods herein.

[0236] 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 applicationspecific 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 radio network node, for example.

[0237] 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 non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receiverswill appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0238] 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 / ordata 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.

[0239] When using the word "comprise" or “comprising”, it shall be interpreted as non- limiting, i.e., meaning "consist at least of'.

[0240] The embodiments herein are not limited to the above-described preferred embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the invention.

[0241] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0242] As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

[0243] Any of the terms processor and circuitry may be understood herein as a hardware component.

[0244] As used herein, the expression “in some embodiments” has been used to indicate that the features of the embodiment described may be combined with any other embodiment or example disclosed herein.

[0245] As used herein, the expression “in some examples” has been used to indicate that the features of the example described may be combined with any other embodiment or example disclosed herein.

Claims

CLAIMS1. A method performed by a network exposure node (140) for handling events in a communication network (100), wherein the method comprises:receiving (201) a first status request for a current status related to an event type from an application node (130), wherein the first status request comprises the event type, requesting (202) the current status related to the requested event type from a subscriber data node (150) or from one or more IMS application servers (160) based on the event type,receiving (203) a status response for the requested event type indicating the current status related to the requested event type from the subscriber data node (150) or from the one or more IMS application servers (160),sending (204) the status response to the application node (130).

2. The method according to claim 1 , wherein the event type comprises any one out of:- a subscriber specific Internet Protocol Multimedia Subsystem, IMS, event type, or - a non-subscriber specific IMS event type.

3. The method according to any of claims 1-2, wherein the first status request indicates one or more IMS subscriber IDs for which the current status related to the event type is requested.

4. The method according to any of claims 1-3, wherein requesting (202) the status of the requested event type comprises sending a second request indicating the event type to the subscriber data node (150) or one or more IMS application servers (160), wherein the sending the second request comprises any one out of:- sending a respective second request for each IMS subscriber ID indicated in the first status request to the subscriber data node (150), wherein each second request requests the current status related to the event type for a subscriber ID,- sending a second request to the subscriber data node (150), wherein the second request requests a respective IMS application server address for each IMS subscriber ID, - sending a second request to one or more IMS application servers (160) supporting the requested event type.

5. The method according to claim 4, wherein requesting (202) the current status related to the requested event type further comprises obtaining the one or more IMS application servers (160) supporting the requested event types.

6. The method according to any of claims 4-5, wherein requesting (202) the current status related to the requested event type further comprises receiving the respective IMS application server (160) address for each IMS subscriber ID, and sending a respective third request for each IMS subscriber ID to the IMS application server (160) assigned to each IMS subscriber respectively.

7. The method according to any of claims 1-6, wherein receiving (203) a status response for the requested event type indicating the current status related to the requested event type comprises receiving one status response for each of the one or more IMS subscriber IDs or receiving one status response from each IMS application server (160) when the event type is a non-subscriber specific event type .

8. The method according to any of claims 1-7, wherein sending (204) the status response to the application node (130) comprises sending one status response for each of the one or more IMS subscriber IDs or sending one status response from each IMS application server (160) when the event type is a non-subscriber specific event type.

9. A method performed by an application node (130) for handling events in a communication network (100), wherein the method comprises any one or more out of:sending (301) a first status request to a network exposure node (140), the request requesting a current event status related to an event type, andreceiving (302) the current status related to the requested event type from the network exposure node (140).

10. The method according to claim 9, wherein the event type comprises any one out of:- a subscriber specific Internet Protocol Multimedia Subsystem, IMS, event type, and - a non-subscriber specific IMS event type.

11. The method according to any of claims 9-10, wherein the first status request comprises one or more IMS subscriber identities, ID, for which the event status is requested.

12. The method according to any of claims 9-11 , wherein receiving (302) the current status related to the requested event type comprises receiving one status response for each of the one or more IMS subscriber IDs or receiving one status response from each IMS application server (160) when the event type is a non-subscriber specific event type.

13. A method performed by a subscriber data node (150) for handling events in a communication network (100), wherein the method comprises:receiving (401) a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node (140), the second request comprising at least one of the event type and an Internet Protocol Multimedia Subsystem, IMS, subscriber identity, ID,obtaining (402) an IMS application server (160) associated with the subscriber ID, performing (403) an action associated with the second request.

14. The method according to claim 13, wherein performing (403) the action associated with second request comprises any one out of:- requesting a current status related to the requested event type from the obtained IMS application server (160),- sending a status response for the event type to the network exposure node (140), the status response indicating the current event status related to the requested event type for the subscriber ID.

15. The method according to any of claims 13-14, wherein the second request comprises a notification address associated with the network exposure node (140), and wherein requesting the current status related to the requested event type comprises indicating the notification address to the IMS application server (160).

16. The method according to claim 14, wherein requesting the current status related to the requested event type comprises receiving the current event status from the IMS application server (160).

17. The method according to any one of claims 13-16, wherein the IMS application server (160) associated with the subscriber ID is an IMS application server 160 instance assigned to the subscribed ID during registration and stored in the context associated with the subscriber ID.

18. A method performed by an Internet Protocol Multimedia Subsystem, IMS, application server (160) for handling events in a communication network (100), wherein the method comprises:receiving (501) a request for a current event status related to an event type from a subscriber data node (150) or a network exposure node (140),sending (502) a response indicating the current event status to the subscriber data node (150) or the network exposure node (140).

19. The method according to claim 18, wherein the event type comprises any one out of:- a subscriber specific IMS event type, or- a non-subscriber specific IMS event type.

20. The method according to any one of claims 18-19, wherein the request indicates the event type.

21. The method according to any one of claims 18-20, wherein the request indicates a subscriber identity, ID, the current event status is requested for, and wherein the response indicates the current event status for the subscriber ID.

22. The method according to any one of claims 18-21, wherein the request comprises a notification address associated with the network exposure node (140), and wherein sending (502) the response comprises sending the response to the network exposure node (140) using the notification address.

23. A network exposure node (140) configured to handle events in a communication network (100), wherein the network exposure node (140) is further configured to:receive a first status request for a current status related to an event type from an application node (130), the request comprising the event type,request the current status related to the requested event type from a subscriber data node (150) or from one or more IMS application servers (160) based on the event type, receive a status response for the requested event type indicating the current status related to the requested event type from the subscriber data node (150) or one or more IMS application servers (160),send the status response to the application node (130).

24. The network exposure node (140) according to claim 23, wherein the network exposure node (140) is further configured to perform the method according to any one of claims 2-8.

25. An application node (130) configured to handle events in a communication network (100), wherein the application node (130) is further configured to:send a first status request to a network exposure node (140), the request is adapted to request the current event status related to an event type, andreceive the current status related to the requested event type from the network exposure node (140).

26. The application node (130) according to claim 25, wherein the application node (130) is further configured to perform the method according to any one of claims 10-12.

27. A subscriber data node (150) configured to handle events in a communication network (100), wherein the subscriber data node (150) is further configured to:receive a second request associated with a procedure for retrieving a current status related to an event type from a network exposure node (140), the second request comprising at least one of the event type and an Internet Protocol Multimedia Subsystem, IMS, subscriber identity, ID,obtain an IMS application server (160) associated with the subscriber ID,perform an action associated with the second request.

28. The subscriber data node (150) to claim 27, wherein the subscriber data node (150) is further configured to perform the method according to any one of claims 14-17.

29. An Internet Protocol Multimedia Subsystem, IMS, application server (160) configured to events in a communication network (100), wherein the IMS application server (160) is further configured to:receive a request for current event status related to an event type from a subscriber data node (150) or a network exposure node (140),send a response adapted to indicate the current event status to the subscriber data node (150) or the network exposure node (140).

30. The IMS application server (160) according to claim 29, wherein the IMS application server (160) is further configured to perform the method according to any one of claims 19-22.

31. A computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-22, as performed by the network exposure node (140), the application node (130), the subscriber data node (150), and the Internet Protocol Multimedia Subsystem, IMS, application server (160), respectively.

32. A carrier comprising the computer program of claim 27, wherein the carrier 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.

Images