Distributor functionality, locator functionality and method in communication network

Abstract

A method performed by a dispatcher function is provided for handling a subscription to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network. The open data relates to a user equipment (UE) connected to an IMS network included in the wireless communication network. The dispatcher function is included in either the first network node or the first IMS node. The dispatcher function receives (1001) a request to request a subscription to open IMS open data related to the UE. The request originates from a second network node operating outside the IMS network. The distributor function obtains (1002), from the locator function, data identifying a second IMS node that supports the open capability and serves the UE. A locator function is included in either the first IMS node or the third network node. The dispatcher function sends (1003) a subscription request to the identified second IMS node to open data related to the UE. The subscription request indicates that the second IMS node notifies the network open function of the occurrence of the trigger meeting the trigger condition when the second IMS node detects the occurrence of the trigger meeting the trigger condition, so as to open the open data. A network open function is located in a first network node. The notification enables the network open function to notify the second network node that the detected trigger has occurred.

Description

Technical Field

[0001] Embodiments herein relate to a locator function, a distributor function and methods therein. In certain aspects, they relate to handling subscriptions to open IMS open data in a communication network. Background Art

[0002] In a typical wireless communication network, wireless devices, also referred to as wireless communication devices, mobile stations, stations (STAs) and / or user equipment (UEs), communicate via a wide area network or a local area network (e.g., a Wi-Fi network) or a cellular network including a radio access network (RAN) portion and a core network (CN) portion. The RAN covers a geographical area, which is divided into service areas or cell areas, which may also be referred to as beams or beam groups, each of which is served by a radio network node such as a radio access node (e.g., a Wi-Fi access point or a radio base station (RBS)), which in some networks may also be represented as a NodeB, an eNodeB (eNB), or a gNB as represented in fifth generation (5G) telecommunications. A service area or cell area is a geographical area where wireless coverage is provided by a radio network node. A radio network node communicates with wireless devices within the range of the radio network node over an air interface operating on radio frequencies.

[0003] 3GPP is a standardization organization for specifying standards for cellular system evolutions, including, for example, 3G, 4G, 5G, and future evolutions. Specifications for the Evolved Packet System (EPS), also known as the fourth generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP). As a continuing network evolution, new releases of 3GPP specify 5G networks, also known as 5G New Radio (NR).

[0004] Multiple antenna technology can significantly increase the data rate and reliability of wireless communication systems. Performance is particularly improved if both the transmitter and receiver are equipped with multiple antennas, resulting in a multiple-input multiple-output (MIMO) communication channel. Such systems and / or related technologies are generally referred to as MIMO.

[0005] In addition to faster peak Internet connection speeds, 5G plans aim to have higher capacity than current 4G, allowing a higher number of mobile broadband users per unit of area and allowing each user to consume a greater or unlimited amount of data per month (measured in GB). This will enable a large portion of the population to stream high-definition media for several hours per day using their mobile devices when Wi-Fi hotspots are not available. 5G development also aims to improve support for machine-to-machine communications (also known as the Internet of Things), aiming for lower cost, lower battery consumption and lower latency than 4G devices.

[0006] The Internet Protocol Multimedia Subsystem (IMS) is a well-known 3GPP standard that allows sessions to be established between two or more parties for a wide variety of services, such as voice or video calls, interactive messaging sessions or third-party specific applications. The protocol chosen by 3GPP is the Session Initiation Protocol (SIP). SIP provides a mechanism for registration of UEs and for establishing multimedia sessions. The SIP REGISTER method enables registration of the current location of the user agent and the INVITE method enables establishment of a session. Public Land Mobile Network (PLMN) operators are implementing IMS as an architectural framework for providing IP multimedia services to their users.

[0007] The Open Mobile Alliance (OMA) and the Global System for Mobile Communications Association (GSMA) have specified a RESTful-based application programming interface (API) for managing event subscriptions for call notifications, call direction notifications, and media interaction notifications (CallNotification-V1_0-20190510-D). Applications can subscribe to the server via the API to provide notifications of specific call events, such as "call busy". When an event that meets the specified conditions occurs, the server notifies the application, such as Figure 1 shown.

[0008] Service-based architecture (SBA) was defined for 5GC in 3GPP Release 15 and has evolved in 3GPP Release 16. Figure 2 The 5G system architecture from 3GPP TS23.501 on a 5GC SBA is shown, which uses a service-based interface (SBI) in the control plane.

[0009] NSSF stands for Network Slice Selection Function.

[0010] NEF stands for Network Exposure Function.

[0011] NRF stands for Network Repository Function.

[0012] PCF stands for Policy Control Function.

[0013] UDM stands for Unified Data Management.

[0014] AF stands for Application Function.

[0015] NSSAAF stands for Network Slice Specific Authentication and Authorization Function.

[0016] AUSF stands for Authentication Server Function.

[0017] AMF stands for Access and Mobility Function.

[0018] SMF stands for Session Management Function.

[0019] SCP stands for Service Communication Proxy.

[0020] UPF stands for User Plane Function.

[0021] DN stands for Data Network.

[0022] In 3GPP Release 16, the IMS interface to 5GC is also defined as SBI. Figure 3 The IMS interface specified using services from 3GPP TS 23.228 is shown.

[0023] According to the current process in IMS, at IMS registration, the Serving Call Session Control Function (S-CSCF) will interact with the IMS Home Subscriber Server (HSS) and register itself as the serving S-CSCF instance for the subscriber. Although the IMS Application Server (AS) has HSS interaction, it does not create any binding information in the HSS and only downloads the subscriber profile from the HSS.

[0024] P-CSCF stands for Proxy Call Session Control Function.

[0025] I-CSCF stands for Query / Service Call Session Control Function.

[0026] based on Figure 2 As shown in the architecture, 5GC has specified detailed procedures and APIs for managing subscription and notification of events between network functions (NFs) and between network functions (NFs) and external application functions (AFs). Figure 4a and 4b The service operation information flow exemplifying this from 3GPP TS23.502 is shown in FIG, where a subscription is sent from an external AF to a network open function (NEF) to obtain information about a specific event occurring in the network. Using standard defined procedures, the NEF forwards the request to the correct NF serving the event via a unified data management function (UDM).

[0027] UDR stands for Unified Data Repository.

[0028] The Bound Session Function (BSF) is defined in the 5GC architecture. Currently, at IMS PDU session establishment, see 3GPP TS23.502, §4.3.2, a Policy Control Function (PCF) will be selected. The PCF registers the UE to the PCF instance ID binding in the BSF. Later, when the UE performs an IMS registration, the Proxy CSCF (P-CSCF) will have to find the same instance of the PCF that was selected during the IMS PDU session establishment and will thus query the BSF before selecting the PCF, e.g. Figure 5 as shown in . Summary of the invention

[0029] As part of developing the embodiments herein, a problem has been identified by the inventors and will be discussed first.

[0030] Currently, there is no standard defined mechanism in IMS, such as 3GPP TS23.228, to dynamically locate a serving NF that can provide specific RESTful-based events / data related to subscriptions that a specific subscriber, subscriber group, and / or AF has subscribed to, as exists today in 5GC. As mentioned above, OMA and GSMA have specified a set of protocols as part of the RESTfulOne API (which is implemented by some IMS providers), namely an API for managing event subscriptions for call notifications, call direction notifications, and media interaction notifications. However, no guidance is provided on locating the specific server and / or NF that serves the subscription, such as Figure 6 as shown in .

[0031] The problem is further exacerbated by the fact that subscriptions to many of these IMS open events and reporting of these events are based on short-lived sessions (e.g., Session Initiation Protocol (SIP) sessions) and may be served by different NFs and different types of NFs. To illustrate this situation, Figure 7 A situation is shown whereby an external AF has dynamically subscribed to a The order The communication status of the subscriber (e.g. busy, idle, unregistered, etc.) plus the relevant KPI call status information with the specific subscriber ( Figure 7 The subscriber is currently served by S-CSCF x, Multimedia Telephony Service (MMTel) x, and Interconnect Border Control Function (IBCF) x. Information related to the requested subscription events about Subscriber 1 requires the NF to provide notification to the AF. The current IMS architecture does not provide any dynamic method for the AF and / or API GW to locate the relevant NF that can provide the relevant required information.

[0032] The purpose of the embodiments herein is to improve the performance of a communication network using the opening of IMS open data.

[0033] According to an aspect of embodiments herein, the object is achieved by a method for handling a subscription to open IMS open data in a communication network, performed by a distributor function. The open data is related to a UE connected to an IMS network included in the communication network. The distributor function is included in any of the following: a first network node or a first IMS node.

[0034] The distributor function receives a request requesting to open a subscription to IMS open data related to the UE. The request originates from a second network node operating outside the IMS network.

[0035] The distributor function obtains data from the locator function, the data identifying a second IMS node supporting open capabilities and serving the UE.The locator function is comprised in any of: the first IMS node or the third network node.

[0036] The distributor function sends a subscription request to the identified second IMS node (132) to open data related to the UE. The subscription request instructs the second IMS node to notify the network opening function of the occurrence of the trigger that meets the trigger condition when the second IMS node detects the occurrence of the trigger that meets the trigger condition, so as to open the open data. The network opening function is located in the first network node.

[0037] The notification enables the network opening function to inform the second network node of the detected trigger occurrence.

[0038] According to another aspect of the embodiments herein, the object is achieved by a method performed by a locator function, the method being used to process a subscription to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network. The open data is related to a UE connected to an IMS network included in the communication network. The locator function is included in any one of the following: a first IMS node or a third network node.

[0039] The locator function receives, from the second IMS node, mapping information related to the registration of the UE in the second IMS node.

[0040] According to a request from a distributor function, the locator function locates data identifying a second IMS node serving the UE based on the mapping information, the distributor function being included in any one of: the first network node or the first IMS node.

[0041] The locator function provides the distributor function with data identifying the second IMS node serving the UE.

[0042] The data identifying the second IMS node enables the distributor function to send a subscription request to the second IMS node to open data related to the UE. The subscription request instructs the second IMS node to notify the network opening function of the occurrence of a trigger that satisfies the trigger condition when the second IMS node detects the occurrence of a trigger that satisfies the trigger condition, so as to open the open data. The network opening function is located in the first network node.

[0043] According to another aspect of the embodiments herein, the object is achieved by a distributor function configured to handle subscriptions to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network. The open data is suitable for being associated with a UE connected to an IMS network, which is suitable for being included in the communication network. The distributor function is suitable for being included in any one of the first network node or the first IMS node. The distributor function is further configured to:

[0044] - receiving a request, the request being adapted to request opening a subscription for IMS open data related to the UE, the request being adapted to originate from a second network node being adapted to operate outside the IMS network,

[0045] - obtaining data suitable for identifying a second IMS node suitable for supporting open capabilities and serving the UE from a locator function, the locator function being suitable for being included in any of: the first IMS node or the third network node, and

[0046] - sending a subscription request to the identified second IMS node to open data related to the UE, the subscription request being adapted to instruct the second IMS node to notify a network open function of the occurrence of a trigger satisfying the trigger condition when the second IMS node detects the occurrence of a trigger satisfying the trigger condition, so as to open the open data, the network open function being adapted to be located in the first network node,

[0047] The notification is suitable for enabling the network openness function to notify the second network node of the detected trigger occurrence.

[0048] According to another aspect of the embodiments herein, the object is achieved by a locator function, the locator function being configured to handle subscriptions to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network. The open data is suitable for being associated with a UE connected to an IMS network included in the communication network. The locator function is suitable for being included in any one of the following: a first IMS node or a third network node, the locator function being further configured to:

[0049] - receiving from the second IMS node mapping information suitable for registration of the UE in the second IMS node,

[0050] - locating, based on a request from a distributor function, data suitable for identifying a second IMS node serving the UE based on the mapping information, the distributor function being suitable for being included in any of: the first network node or the first IMS node, and

[0051] - providing the Distributor Function with data suitable for identifying the second IMS node serving the UE,

[0052] The data suitable for identifying the second IMS node is suitable for enabling the distributor function to send a subscription request to the second IMS node to open data related to the UE, and the subscription request is suitable for instructing the second IMS node to notify the network opening function of the occurrence of the trigger that meets the trigger condition when the second IMS node detects that the trigger that meets the trigger condition occurs, so as to open the open data, and the network opening function is suitable for being located in the first network node.

[0053] In this way, an open and flexible framework for IMS data is achieved. This is because the distributor function and the locator function handle the open subscription for IMS data related to the UE by locating the second IMS node serving the UE, distributing the subscription request received from the second network node to the correct second IMS node, and opening the open data to the second network node when a trigger that satisfies the trigger condition occurs. This results in that the application domain can contribute to the support of open use cases in the IMS domain. This in turn results in improved performance of the open communication network using IMS open data.

[0054] The embodiments herein bring the advantage of achieving IMS agnostic and flexible opening of IMS data to application functions (eg, second network nodes), for example, by using SBI interaction, which uses an architecture similar to that used in 5GC. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, in which:

[0056] Figure 1 is a schematic sequence diagram illustrating the prior art.

[0057] Figure 2 is a schematic block diagram illustrating the prior art.

[0058] Figure 3 is a schematic block diagram illustrating the prior art.

[0059] Figure 4a and Figure 4b is a schematic sequence diagram illustrating the prior art.

[0060] Figure 5 is a schematic sequence diagram illustrating the prior art.

[0061] Figure 6 is a schematic block diagram illustrating the prior art.

[0062] Figure 7 is a schematic sequence diagram illustrating the prior art.

[0063] Figure 8 is a schematic block diagram illustrating an IMS open framework according to embodiments herein.

[0064] Fig. 9 is a schematic block diagram illustrating an embodiment of a communication network.

[0065] Fig.10 is a flow chart depicting an embodiment of a method in a distributor function.

[0066] Fig.11 is a flow chart depicting an embodiment of a method in a locator function.

[0067] Fig.12 is a schematic block diagram illustrating an IMS open framework according to embodiments herein.

[0068] Fig.13 is a schematic sequence diagram illustrating an example of embodiments herein.

[0069] Fig.14 is a schematic sequence diagram illustrating an example of embodiments herein.

[0070] Fig.15a and Fig.15b is a schematic block diagram illustrating an embodiment of the distributor functionality.

[0071] Fig.16a and Fig.16b is a schematic block diagram showing an embodiment of the locator function

[0072] Fig.17 A telecommunications network is schematically shown connected to a host computer via an intermediary network.

[0073] Fig.18 It is a general block diagram of a host computer communicating with a user device via a base station over a partially wireless connection.

[0074] Figures 19 to 22 is a flow chart illustrating a method implemented in a communication system including a host computer, a base station, and a user equipment. DETAILED DESCRIPTION

[0075] Embodiments herein relate to a communication network and handling subscriptions to open IMS open data.

[0076] By introducing the IMS real-time event data open framework, the embodiments herein enable consumers of IMS events and / or open data (e.g., AF) to ensure that their event subscriptions are served by the correct IMS NF. This does not require knowledge of the underlying network. The framework is built on the SBA principle and provides SBI to enable consumers of IMS open data to utilize the service.

[0077] like Figure 8As shown in , the framework according to the example of the embodiment in this article includes an IMS locator processing function, such as a locator function, which provides binding and / or mapping information and / or data for NFs supporting IMS data opening. This binding and / or mapping information and / or data is provided by the relevant IMS NF to the repository function (such as the locator function). The information includes the identity of the subscriber currently served by the NF, such as an IMS private identity (IMPI) and / or an IMS public user identity (IMPU), and the NF instance address.

[0078] The IMS HSS may provide binding and / or mapping information and procedures associated with it to the IMS registration aware NFs (e.g. S-CSCF and IMS AS) in the role of "Locator Handler" (e.g. Locator Function). This means that at IMS registration time, the S-CSCF and IMS AS (e.g. MMTel AS) perform registration of the current service subscriber in the HSS using the SBI interface towards the HSS, Nhss_IMS service, over the N70 and N71 reference points.

[0079] For an IMS registration-aware P-CSCF, there are three options:

[0080] 1. Introduce the Nhss_IMS registration process from P-CSCF to HSS, which will result in the following event subscription flow: AF->NEF->HSS->P-CSCF for event subscription. Currently, P-CSCF lacks any interaction with HSS.

[0081] 2. Let the S-CSCF be responsible for distributing events to the serving P-CSCF, which will result in the following event subscription flow: AF->NEF->HSS->S-CSCF->P-CSCF.

[0082] 3. Enable the P-CSCF to register the subscriber binding in the BSF at the time of IMS registration, which will result in the following event subscription flow: AF->NEF->P-CSCF, while the NEF will be notified and / or query the BSF to find the correct P-CSCF.

[0083] For IMS NFs that are not aware of IMS registration, such as e.g. IBCF and Multimedia Resource Function (MRF), and registration of a given subscriber binding will only take place during a call, and such NFs lack HSS interaction, the recommended solution is to create such bindings in the BSF in the role of a "Locator Handler" (e.g. Locator Function). The event subscription flow would then be as follows, which is similar to option 3 for P-CSCF, but would take place at call setup: AF->NEF->IMS NF. The NEF would subscribe to subscriber availability in the BSF and would be notified at call setup, as the specific IMS NF would register its bindings in the BSF.

[0084] The framework also introduces a "distribution handler", such as a distributor function, which distributes the IMS event subscription to the relevant IMS NFs that serve the requested event after locating the correct IMS NF using the locator function.

[0085] The examples of embodiments herein satisfy current IMS customer requests, such as call notification events, such as subscriber "call status" - busy / idle, typically provided by the MMTel AS, and also satisfy future higher level requests whereby event open information and / or data is required from various IMS NF types.

[0086] Fig. 9 1 is a schematic diagram showing a communication network 100 in which embodiments herein may be implemented. The communication network 100 includes one or more RANs, one or more IMS networks, such as IMS network 102, and one or more CNs, such as CN 104. The communication network 100 may use many different technologies, such as Wi-Fi, Long Term Evolution (LTE), Advanced LTE, 5G, New Radio (NR), 6G, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications / Enhanced Data Rates for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), to name just a few possible implementations. The embodiments herein relate to recent technology trends of particular interest in the context of 5G, however, the embodiments are also applicable to further developments of existing wireless communication systems, such as WCDMA and LTE.

[0087] A plurality of RAN nodes operate in the communication network 100, such as, for example, a RAN node 105. The RAN node 105 provides radio coverage in a plurality of cells, which may also be referred to as beams or beam groups, such as, for example, the cell 10 provided by the RAN node 105.

[0088] The RAN node 105 may be any of the following: an NG-RAN node, a transmission and reception point (e.g., a base station), a radio access network node (e.g., a wireless local area network (WLAN) access point or access point station (AP STA), an access controller, a base station (e.g., a radio base station such as 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 device of a radio base station, a standalone access point, or any other network element capable of communicating with a UE 121 within a service area served by the RAN node 105, e.g., depending on the first radio access technology and terminology used. The RAN node 105 may be referred to as a serving RAN node and communicates with a UE such as the UE 121 using a downlink (DL) transmission to the UE 121 and in an uplink (UL) transmission from the UE 121.

[0089] A plurality of UEs operate in the communication network 100, such as, for example, UE 121. UE 121 may also be referred to as an IoT device, a mobile station, a non-access point (non-AP), a STA, and / or a wireless terminal. It should be understood by those skilled in the art that "UE" is a non-restrictive term that refers to any terminal, wireless communication terminal, user equipment, machine type communication (MTC) device, device to device (D2D) terminal, radio equipment in a vehicle, or node, such as a smartphone, a laptop, a mobile phone, a sensor, a repeater, a mobile tablet, or a small base station that communicates even within a cell.

[0090] The first network node 111 operates in the communication network 100. The first network node 111 may be, for example, a NEF node operating in the CN 104. The first network node 111 may be, for example, a functional node within the CN network 104 (e.g., 5GC), and may be responsible for securely opening NF capabilities, events, and open data to AFs outside the 5GC.

[0091] The second network node 112 operates in the wireless communication network 100. The second network node 112 may be, for example, an AF node. The second network node 112 may, for example, operate in the CN 104, or in an external / untrusted network.

[0092] The third network node 112 operates in the wireless communication network 100. The third network node 113 may be, for example, a BSF node. The third network node 112 may operate in the CN 104, for example.

[0093] The first IMS node 131 and the second IMS node 132 operate in the IMS network 102. The IMS network 102 is an architecture for delivering media content through IP packet switching transmission. The first IMS node 131 may be, for example, an HSS node, and the second IMS node 132 may be, for example, a P-CSCF node, an S-CSCF node, and an IMS AS node or any other type of node or NF operating in the IMS network 102.

[0094] The method herein may be performed by a distributor function (such as, for example, the first network node 111 and / or the first IMS node 121) and a locator function (such as, for example, the second IMS node 132 and / or the third network node 113). As an alternative, a distributed node (DN) and a function (such as, for example, Figure 8 , as shown in , included in the cloud 150 ) can be used to perform or partially perform the methods described herein.

[0095] The examples of embodiments herein may provide a framework and / or architecture and services to allow a second network node 112 (e.g., an AF node) to subscribe to IMS events and / or data related to a specific subscriber (e.g., UE 121), a subscriber group (e.g., one or more UEs), and / or a subscription. In addition, according to the examples of embodiments herein, a distributor function and a locator function may be provided. The locator function may provide a positioning function for locating a NF serving UE 121, such as a second IMS node 132. The distributor function may provide a distribution function for distributing subscription requests to the located second IMS node 132, and distributing notifications from the second IMS node 132 to the second network node 112. The examples of embodiments herein are consistent with the current open principles in 5GC, while also being extended to meet IMS use cases, and may solve the main problem of locating an IMS NF serving a specific UE.

[0096] Furthermore, examples of embodiments herein may provide the following advantages:

[0097] - Ensuring that consumers (eg AF nodes, such as the second network node 112) are IMS agnostic, ie do not need to have a detailed view of the IMS NF topology.

[0098] - Ensure that the consumer (e.g., AF node, such as the second network node 112) does not need to implement IMS-specific business logic to handle, for example, subscribers (e.g., UE 121) that are not registered, unregistered, and unallocated (2G / 3G allocated but not registered) within the IMS domain, IMS-specific identity management, for example, mapping the identity used by the consumer to a specific IMS identity that can be associated with multiple devices and / or multiple roles of the subscriber, etc.

[0099] -Flexible and scalable framework and architecture from a deployment perspective.

[0100] - Flexible and extensible framework and architecture from an architectural perspective. Functions in the open framework (e.g., distributor function and locator function) can be implemented as part of and / or used by existing NFs (such as, for example, HSS / UDM, BSF, NEF).

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

[0102] First, combine Fig.10 Embodiments of the method are generally described from the perspective of the distributor function and then combined with Fig.11 Embodiments of the method are generally described from the perspective of the locator function. This section will be followed by a more detailed description.

[0103] Now combine Fig.10 The method according to the embodiment is described from the perspective of the distributor function. Fig.10 An example embodiment of a method performed by a distributor function for handling subscriptions to open IMS open data in a wireless communication network 100 is depicted. The open data is related to a UE 121 connected to an IMS network 105 included in the wireless communication network 100. The distributor function is included in any of: the first network node 111 or the first IMS node 131.

[0104] The first network node 111 may be, for example, a NEF node, and the first IMS node 131 may be, for example, a HSS.

[0105] The method comprises the following actions, which may be performed in any suitable order. Fig.10 Optional actions are shown in the dashed box.

[0106] Action 1001

[0107] The distributor function receives a request requesting to open a subscription to IMS open data related to the UE 121. The request originates from the second network node 112. The second network node 112 operates outside the IMS network 105.

[0108] The second network node 112 may be, for example, an AF node, and may operate in the CN 104, or may operate in an external / untrusted network. The open data may be any one or more of the following: event data (e.g., data related to an event), the location of the UE 121, the roaming state of the UE 121, the communication state of the UE 121 (e.g., idle, busy, unregistered, the number of failed and / or successful calls in a specific geographic area, etc.).

[0109] In some embodiments, the subscription request includes any one or more of the following: a trigger condition, and the type of open data to be opened.

[0110] The received subscription request may be communicated (e.g., received) using the SBI. When the distributor function is included in the first network node 111, the SBI may be a new SBI service, such as the SBI service Nnef_IMS_EE_subscribe. When the distributor function is included in the first IMS node 131, the SBI may be, for example, another new SBI service, such as the SBI service Nhss_IMS_EE_subscribe.

[0111] Action 1002

[0112] The distributor function obtains from the locator function data identifying the second IMS node 132. The second IMS node 132 supports open capabilities and serves the UE 121. The locator function is included in any of: the first IMS node 131 or the third network node 113. The third network node 113 may be, for example, a BSF node.

[0113] In some embodiments, the distributor function obtains data identifying the second IMS node 132 by sending a request for data identifying the second IMS node 132 to the locator function. The request includes a first identification (ID) identifying the UE 121. The distributor function may then receive data identifying the second IMS node (132), for example, from the locator function. The data identifying the second IMS node 132 may include any one or more of the following: a second ID identifying the second IMS node 132 and an address of the second IMS node 132.

[0114] According to some embodiments, when both the distributor function and the locator function are included in the same node (e.g., the first IMS node 131), a data request for identifying the second IMS node 132 and data identifying the second IMS node 132 are sent and received internally in the first IMS node 131.

[0115] Action 1003

[0116] The distributor function sends a subscription request to the identified second IMS node 132 to open data related to the UE 121. The subscription request instructs the second IMS node 132 to notify the network open function of the occurrence of a trigger that satisfies the trigger condition when the second IMS 132 node detects the occurrence of a trigger that satisfies the trigger condition to open the open data. The network open function is located in the first network node 111. The notification enables the network open function to notify the second network node 112 of the detected occurrence of the trigger.

[0117] The sent subscription request may be communicated using an SBI, such as sending the SBI. The SBI may be a new or updated SBI service, such as a Nims (NF_IMS)_EE service.

[0118] The notification may include open data.

[0119] Action 1004

[0120] In some embodiments, the distributor function receives a notification from the second IMS node 132. The notification informs the distributor function of a satisfied trigger occurrence detected by the second IMS node 132. The trigger occurrence is associated with the UE 121. As described above, the notification may include open data.

[0121] The received notification may be communicated using an SBI, such as received. The SBI may be a new or updated SBI service, such as a Nims (NF_IMS)_EE service.

[0122] Action 1005

[0123] In some embodiments, the distributor function sends the received notification to the second network node 112. The distributor function thereby opens the IMS open data to the second network node 112. The notification is communicated using the SBI. As described above, the notification may include open data.

[0124] The notification sent may be communicated using the SBI, such as sending. The SBI may be a new or updated SBI service, such as a Nims (NF_IMS)_EE service.

[0125] Now combine Fig.11 The method according to the embodiment is described from the perspective of a locator function. Fig.11An example embodiment of a method performed by a locator function for handling a subscription to IMS open data in a communication network 100, the open data being related to a UE 121 connected to an IMS network 102 included in the communication network 100, is depicted. The locator function is included in any of the following: a first IMS node 131 or a third network node. The first IMS node 131 may be, for example, an HSS, and the third network node 113 may be, for example, a BSF node. The open data may be any one or more of the following: event data (e.g., data related to an event), a location of the UE 121, a roaming state of the UE 121, a communication state of the UE 121 (e.g., idle, busy, unregistered, the number of failed and / or successful calls in a certain geographical area, etc.).

[0126] The method includes the following actions, which may be performed in any suitable order. Fig.11 Indicated by a dotted box.

[0127] Action 1101

[0128] The locator function receives mapping information related to the registration of UE 121 in the second IMS node 132. The mapping information is received from the second IMS node 132. The second IMS node 132 may be, for example, an IMS NF node, such as, for example, a P-CSCF node, an S-CSCF node, an IMS AS node, or any other type of node or NF operating in the IMS network 102.

[0129] The mapping information may include any one or more of the following: a first ID identifying the UE 121 , a second ID identifying the second IMS node 132 , and an address of the second IMS node 132 .

[0130] The mapping information is received via the SBI. The SBI may be a new or updated SBI service, for example, when the locator function is included in the third network node 113, the SBI may be the Nbsf_mgmt service, or when the locator function is included in the first IMS node 131, the SBI may be the Nhss_ims

[0131] Action 1102

[0132] According to the request from the distributor function, the locator function locates data identifying the second IMS node 132 serving the UE 121 based on the mapping information. The distributor function is included in any of the following: the first network node 111 or the first IMS node 131. As described above, the first network node 111 may be, for example, a NEF node, and the first IMS node 131 may be, for example, a HSS.

[0133] In some embodiments, the locator function locates the data identifying the second IMS node 132 by receiving a request from the distributor function. The request may include the first ID identifying the UE 121. In this embodiment, the locator function further locates the data identifying the second IMS node 132 based on the first ID.

[0134] According to some embodiments, when both the distributor function and the locator function are included in the same node (eg the first IMS node 131 ), the request for data identifying the second IMS node 132 is sent and received internally in the first IMS node 131 .

[0135] Action 1103

[0136] The locator function provides data identifying the second IMS node 132 serving the UE 121 to the distributor function.

[0137] The data identifying the second IMS node 132 enables the distributor function to send a subscription request to the second IMS node 132 to open data related to the UE 121. The subscription request instructs the second IMS node 132 to notify the network opening function of the occurrence of a trigger that satisfies the trigger condition when the second IMS 132 node detects the occurrence of a trigger that satisfies the trigger condition to open the open data. The network opening function is included in the first network node 111.

[0138] In some embodiments, the locator function provides information identifying the second IMS node 132 by sending data identifying the second IMS node 132 to the distributor function. The information identifying the second IMS node 132 may include any one or more of the following: a second ID identifying the second IMS node 132, and an address of the second IMS node 132.

[0139] According to some embodiments, when both the distributor function and the locator function are included in the same node (eg, the first IMS node 131 ), data identifying the second IMS node 132 is internally sent and received in the first IMS node 131 .

[0140] The above embodiments will now be further described and exemplified.The following embodiments apply to any suitable embodiments above and can be combined with any suitable embodiments above.

[0141] Fig.12 An example of an architectural overview of how the IMS real-time event data open framework can be implemented is shown. The distributor function is represented by a dotted circle. The locator function is represented by a solid circle.

[0142] The IMS locator processing function provides binding and / or mapping information for NFs supporting IMS event data opening, and the IMS locator processing function can be implemented by UDM / HSS functions or 5GC BSF. For example, the IMS locator processing (repository) function (such as, for example, a locator function) provides binding and / or mapping information for NFs supporting IMS event data opening, such as the above referred to as open capabilities, and the IMS locator processing (repository) function (such as, for example, a locator function) can be implemented by UDM / HSS functions (such as, for example, the first IMS node 131) or 5GC BSF (such as, for example, the third network node 131), such as being implemented in being included therein.

[0143] As described above, the placement of the locator function may depend on the nature of the event and / or open data being requested.

[0144] For events and / or open data related to IMS registration, NF allocation, registration or allocation lifetime of a subscriber and provided by an IMS NF having an interface to the HSS, the UDM / HSS may host a locator function. For example, for events and / or open data related to IMS registration, NF allocation, registration or allocation lifetime of a subscriber (e.g., UE 121) or a group of subscribers (e.g., a UE group) and provided by an IMS NF (e.g., the second IMS node 132) (e.g., an S-CSCF or an IMS AS) having an interface to the HSS, the UDM / HSS may host (e.g., include) a locator function.

[0145] For events and / or open data related to call states provided by an IMS NF that currently has no interface to the HSS and is not part of the "IMS registration flow", the BSF may host a locator function. For example, for events and / or open data related to call states provided by an IMS NF (e.g., the second IMS node 132) (e.g., an IBCF or an MRF) that currently has no interface to the HSS (e.g., the first IMS node 131) and is not part of the "IMS registration flow", the BSF (such as, for example, the third network node 113) may host (e.g., include) a locator function.

[0146] When a P-CSCF that is aware of the “IMS registration flow” but currently has no HSS interface is an IMS NF that provides events and / or open data, the UDM / HSS (e.g., as mentioned in Option 3 above) or the BSF may host the locator function. For example, when a P-CSCF that is aware of the “IMS registration flow” but currently has no HSS interface is an IMS NF that provides events and / or open data, the UDM / HSS (such as, for example, the first IMS node 113, for example, as mentioned in Option 3 above) or the BSF (e.g., the third network node 113) may host (e.g., include) the locator function.

[0147] When the BSF provides a locator function or plays the role of a locator handler, the existing 5GC function can be updated to provide IMS specific services, and the IMS consumers (e.g., IMS NF) can use the IMS specific services to register their open capability bindings and / or mapping information via the update service provided by the BSF. For example, when the BSF provides (e.g., includes) a locator function or plays the role of a locator handler, the existing 5GC function can be updated to provide IMS specific services, and the IMS consumers (such as, IMS NF, e.g., the second IMS node 132) can use the IMS specific services to register their open capability bindings and / or mapping information via the update service provided by the BSF. The updated service can be, for example, an SBI service Nbsf_Management_Register service operation. For example, an IMS NF (e.g., P-CSCF or IBCF) with IMS open capabilities registers the subscribers it is currently serving and its own instance address. The consumer (e.g., NEF) uses this information to discover (e.g., by using an existing BSF service Nbsf_Management_Discovery service operation) a specific NF instance that serves the requested event and / or open data subscription. For example, the updated service may be, for example, an SBI service Nbsf_Management_Register service operation. For example, an IMS NF with IMS open capabilities (e.g., a P-CSCF or IBCF) registers the subscriber it is currently serving (e.g., UE 121) and its own instance address. This information is used by the consumer (e.g., a distributor function, such as an NEF node or the first network node 111) to discover (such as, for example, obtained by using an existing BSF service Nbsf_Management_Discovery service operation) a specific NF instance that serves the requested event and / or open data subscription (e.g., the second IMS node 132).

[0148] When the UDM / HSS provides a locator function or plays the role of a locator handler, the existing functionality may be updated to provide SBI IMS specific services, which the IMS consumer (e.g., S-CSCF or IMS AS) may use to register its open capability bindings and / or mapping information via, for example, an update service Nhss_imsUEContextManagement service operation over reference point N70 or N71. For example, when the UDM / HSS (e.g., the first IMS node 131) provides (e.g., includes) a locator function or plays the role of a locator handler, the existing functionality may be updated to provide SBI IMS specific services, which the IMS consumer (e.g., S-CSCF or IMS AS (such as the second IMS node 132)) may use to register its open capability bindings and / or mapping information via, for example, an update service Nhss_imsUEContextManagement service operation over reference point N70 or N71.

[0149] A consumer (e.g., NEF) may use this information provided by the newly introduced locator function in the HSS / UDM to locate a specific NF instance serving the requested event and / or open data subscription. Alternatively, the NEF may utilize the UDM / HSS to distribute the subscription to the relevant NFs, for example, by using the distribution logic introduced in the HSS / UDM. For example, a consumer (e.g., a distributor function, such as an NEF node or the first network node 111) may use this information or data provided by the newly introduced locator function in the HSS (e.g., a locator function) to locate (e.g., obtain) a specific NF instance serving the requested event and / or open data subscription (e.g., the second IMS node 132). Alternatively, the NEF may utilize the UDM / HSS to distribute the subscription to the relevant NFs, for example, the second IMS node 132, for example, by using the distribution logic introduced (e.g., included) in the HSS (such as, for example, a distributor function).

[0150] like Fig.12As shown in and as described above, the UDM / HSS may also include distribution handler logic, or act as a distributor, and distribute events and / or data open subscriptions on behalf of the NEF. For example, the UDM / HSS (such as the first IMS node 131) may also include distribution handler logic (e.g., distributor function), or act as a distributor, and distribute events and / or data open subscriptions on behalf of the NEF (e.g., the first network node 111). Using the locator function to locate the correct NF instance, the UDM / HSS may use the newly introduced Nims(NF_IMS)_EE_SubscribeSBI service toward the relevant IMS NF (e.g., S-CSCF or IMS AS) to subscribe to the event and / or data open. The relevant IMS NF may notify the NEF (e.g., "NotifyEndPoint=NEF") of the event occurrence via the newly introduced Nims(NF_IMS)_EE_NotifySBI service. For example, using the locator function to locate the correct NF instance (e.g., the second IMS node 132), the UDM / HSS may subscribe to the event and / or data exposure using the newly introduced Nims(NF_IMS)_EE_SubscribeSBI service toward the relevant IMSNF (e.g., S-CSCF or IMS AS, e.g., the second IMS node 132). The relevant IMS NF (e.g., S-CSCF or IMS AS, e.g., the second IMS node 132) may notify the NEF (e.g., the first network node 111) (e.g., "NotifyEndPoint=NEF") of the event occurrence, e.g., the detected trigger occurrence satisfying the trigger condition as mentioned above, via the newly introduced Nims(NF_IMS)_EE_Notify SBI service.

[0151] The NEF may also include distribution handler logic or act as a distributor, and distribute the event and / or open data subscription to the relevant IMS NFs based on the information provided by the locator function in the UDM / HSS or BSF. For example, the NEF (e.g., the first network node 111) may also include distribution handler logic (e.g., a distributor function), or act as a distributor, and distribute the event and / or open data subscription to the relevant IMS NFs (e.g., the second IMS node 132) based on the information (e.g., data identifying the second IMS node 132) provided by (e.g., obtained from) the locator function in the UDM / HSS or BSF (e.g., the first IMS node 131 or the third network node 113). As described above, the NEF may use the newly introduced Nims(NF_IMS)_EE_Subscribe SBI service towards the relevant IMS NFs (e.g., P-CSCF or IBCF) to subscribe to the event and / or open data. The relevant IMS NF (e.g., P-CSCF or IBCF) may notify the NEF of the event occurrence via the newly introduced Nims(NF_IMS)_EE_NotifySBI service. For example, the NEF (e.g., the first network node 111) may use the newly introduced Nims(NF_IMS)_EE_Subscribe SBI service towards the relevant IMS NF (e.g., P-CSCF or IBCF, such as the second IMS node 132) to subscribe to the event and / or open data. The relevant IMS NF (e.g., P-CSCF or IBCF, such as the second IMS node 132) may notify the NEF (e.g., the first network node 111) of the event occurrence, such as the occurrence of a detected trigger satisfying the trigger condition as mentioned above, via the newly introduced Nims(NF_IMS)_EE_Notify SBI service.

[0152] Fig.13 A sequence diagram of an example according to an embodiment herein is shown. According to the example, the P-CSCF 132 (e.g., the second IMS node 132 or the IMF NF) uses a locator function included in the BSF 113 (e.g., the BSF node or the third network node 113). Furthermore, according to the example, the distributor function is included in the NEF 111 (e.g., the first network node 111).

[0153] S1301. UE 121 may perform an initial registration with IMS network 102 by sending, for example, a registration request to IMS network (102). The request may be sent via P-CSCF 132 (e.g., second IMS node 132). UE 121 may receive a confirmation message (e.g., a 200 OK message) from IMS network (102) via P-CSCF 132.

[0154] S1302. The BSF 113 (such as a locator function, e.g., the third network node 113) may receive (e.g., obtain) mapping and / or binding information from a P-CSCF 132 (e.g., the second IMS node 132) that supports IMS open capabilities. The mapping and / or binding information may be related to the UE 121. As described above, the mapping and / or binding information may be received using an updated SBI (e.g., an SBI service Nbsf_Management_Register service operation).

[0155] S1303. NEF 111 (such as a distributor function, e.g., first network node 111) may receive an IMS event open request, e.g., a request to open a subscription to IMS open data, from AF 112 (e.g., second network node 112). As described above, the IMS event open request may be sent using a new SBI (e.g., Nnef_IMS_EE_subscribe service operation).

[0156] S1304 . The NEF 111 (such as a distributor function, eg the first network node 111 ) may locate (eg obtain) the correct IMS NF (such as the P-CSCF 132 ), eg data identifying the second IMS node 132 serving the UE 121 .

[0157] S1305. When locating (e.g., obtaining) the IMS NF serving the UE 121, the NEF 111 (e.g., a distributor function, e.g., the first network node 111) may send a message (e.g., a discovery request message) to the BSF 113 (e.g., a locator function, e.g., the third network node 113). In response to the discovery request message, the BSF 113 may send (e.g., provide) a response (e.g., data identifying the second IMS node 132) to the NEF 111. The BSF 113 may locate the data identifying the second IMS node 132 before sending the response to the NEF 111, e.g., by checking whether it has received mapping and / or binding information related to the UE 121. As described above, the discovery request message may be sent using an updated SBI (e.g., the Nbsf_Management_Discovery service operation).

[0158] S1306. The NEF 111 (such as a distributor function, such as the first network node 111) may send a subscription request (such as the received IMS event open request) to the located IMS NF (such as the P-CSCF 132, such as the second IMS node 132) to open the IMS open data. The subscription request may include IMS trigger data, such as, for example, a trigger condition, and the P-CSCF 132 may equip the received IMS trigger. As described above, a new SBI, such as the Nims (NF_IMS)_EE_Subscribe service operation, may be used to send the subscription request.

[0159] S1307. In response to the trigger of the equipped trigger, such as the P-CSCF 132 (e.g., the second IMS node 132) detecting a trigger occurrence that satisfies the trigger condition, the NEF 111 (e.g., the distributor function, e.g., the first network node 111) may receive a notification message, such as, for example, notifying the distributor function of the detection of the satisfied trigger occurrence by the P-CSCF 132 (e.g., the second IMS node 132). The notification message may include event information related to the event associated with the trigger occurrence, such as open data. As described above, the notification message may be received using a new SBI (e.g., Nims (NF_IMS)_EE_Notify service operation).

[0160] S1308. The NEF 111 (e.g., the distributor function, e.g., the first network node 111) may send a notification message to the AF 112 (e.g., the second network node 112), such as, for example, a notification notifying the distributor function of the occurrence of a satisfied trigger detected by the P-CSCF 132 (e.g., the second IMS node 132). As described above, the notification message may include event information related to the event associated with the occurrence of the trigger, e.g., open data.

[0161] Fig.14 A sequence diagram of an example according to an embodiment of the present invention is shown. According to the example, the IMS-AS 132 (e.g., the second IMS node 132 or the IMF NF) uses a locator function included in the HSS 131 (e.g., the HSS node or the first IMS node 131). In addition, according to the example, the distributor function is included in the HSS 131 (e.g., the first IMS node 131).

[0162] S1401. UE 121 may perform an initial registration with IMS network 102 by sending a registration request, for example, to IMS network 102. The request may be sent to an IMS AS (e.g., second IMS node 132) via an S-CSCF node and may be referred to as a third-party registration. UE 121 may receive a confirmation message (e.g., a 200 OK message) from the IMS network (102) via the S-CSCF node.

[0163] S1402. The HSS 131 supporting the IMS open capability (such as a locator function, e.g., the first IMS node 131) may receive (e.g., obtain) mapping and / or binding information from the IMS AS 132 (e.g., the second IMS node 132). The mapping and / or binding information may be related to the UE 121. As described above, the mapping and / or binding information may be received using an updated SBI (e.g., an SBI service Nhss_imsUEContextManagement service operation).

[0164] S1403. In some examples, HSS 131 (such as a locator function, such as first IMS node 131) may receive (e.g., obtain) mapping and / or binding information from an IMS AS 132 (e.g., second IMS node 132) that supports IMS open capabilities. The mapping and / or binding information may be related to UE 121. As described above, the mapping and / or binding information may be received using an updated SBI (e.g., an SBI service Nhss_imsUEContextManagement service operation).

[0165] S1404. NEF 111 (such as first network node 111) may receive an IMS event open request from AF 112 (such as second network node 112), such as a request to open a subscription to IMS open data. As described above, the IMS event open request may be sent using a new SBI (such as Nnef_IMS_EE_subscribe service operation).

[0166] S1405. The NEF 111 (e.g., the first network node 111) may forward an IMS event open request (e.g., a request to open a subscription to IMS open data) from the AF 112 (e.g., the second network node 112) to the HSS 131 (e.g., a distributor function, e.g., the first IMS node 131). The IMS event open request may be sent using a new SBI (e.g., Nhss_IMS_EE_subscribe service operation).

[0167] S1406.HSS111 (such as a distributor function, e.g., first IMS node 131) may locate (e.g., obtain) a correct IMS NF, such as IMS AS132, e.g., data identifying second IMS node 132 serving UE 121. Since HSS131 also includes a locator function, HSS131 may locate (e.g., obtain) data identifying second IMS node 132 serving UE 121 using the locator function included in HSS131.

[0168] S1407.HSS131 (such as a distributor function, e.g., first IMS node 131) may forward (e.g., send) a subscription request (e.g., a received IMS event open request) to a located IMS NF (such as IMS AS132, e.g., second IMS node 132). The subscription request may be forwarded on behalf of NEF 111. The subscription request may include IMS trigger data (such as, for example, a trigger condition), and IMS AS132 may arm the received IMS trigger. As described above, the subscription request may be sent using a new SBI (e.g., Nims(NF_IMS)_EE_SubscribeSBI service). Also as described above, the subscription request may be sent to IMS AS132 along with an instruction to notify NEF 111 that the satisfied trigger occurred, e.g., by including "NotifyEndPoint=NEF" in the forwarded subscription request.

[0169] S1408. In response to the triggering of the equipped trigger, such as the IMS AS 132 (e.g., the second IMS node 132) detecting a trigger occurrence that satisfies the trigger condition, the NEF 111 (e.g., the first network node 111) may receive a notification message, such as a notification that the distributor function is notified of the satisfied trigger occurrence detected by the IMS AS 132 (e.g., the second IMS node 132). The notification message may include event information related to the event associated with the trigger occurrence, such as open data. As described above, the notification message may be received using a new SBI (e.g., Nims (NF_IMS)_EE_Notify service operation).

[0170] S1409. NEF 111 (e.g., first network node 111) may send a notification message to AF 112 (e.g., second network node 112), for example, notifying the distributor function of a notification of a satisfied trigger occurrence detected by IMS AS 132 (e.g., second IMS node 132). As described above, the notification message may include event information related to the event associated with the trigger occurrence, such as open data.

[0171] To perform the method actions, the distributor function and / or a node comprising the distributor function may include Fig.15a and Fig.15b The distributor function is configured to handle subscriptions to open IMS open data in the communication network 100. The open data is suitable for being related to a UE 121 connected to an IMS network 102, which is suitable for being included in the communication network 100. The distributor function is suitable for being included in any one of the first network node 111 or the first IMS node 131.

[0172] The distributor function and / or a node containing the distributor function may include an input and output interface 1500, which is configured to communicate with, for example, the first UE 121, the first network node 111, the second network node 112, the third network node 113, the first IMS node 131 and the second IMS node 132, and with network nodes in the communication network 100 and the IMS network 102.

[0173] The distributor function is further configured to receive a request, e.g. via a receiving unit 1510 in the distributor function, for requesting to open a subscription for IMS open data related to the UE 121. The request is adapted to originate from a second network node 112 adapted to operate outside the IMS network 102.

[0174] The distributor function may also be configured to receive a notification from the second IMS node 132, e.g. by a receiving unit 1510 in the distributor function, the notification being adapted to notify the distributor function of a satisfied trigger occurrence detected by the second IMS node 132. The trigger occurrence is adapted to be related to the UE 121.

[0175] The distributor function is further configured to receive a notification from the second IMS node 132, e.g. by a receiving unit 1510 in the distributor function, the notification being adapted to notify the distributor function of a satisfied trigger occurrence detected by the second IMS node 132. The trigger occurrence is adapted to be related to the UE 121.

[0176] The distributor function is further configured to obtain, e.g. by an obtaining unit 1520 in the distributor function, from the locator function data suitable for identifying the second IMS node 132, which is suitable for supporting open capabilities and serving the UE 121. The locator function is suitable for being included in any one of the first IMS node 131 or the third network node 113.

[0177] Obtaining data suitable for identifying the second IMS node 132 may further be suitable for comprising sending a request to the locator function for data identifying the second IMS node 132. The request is suitable for comprising a first ID suitable for identifying the UE 121, and receiving data suitable for identifying the second IMS node 132.

[0178] The data adapted to identify the second IMS node 132 may be adapted to include any one or more of the following: a second ID adapted to identify the second IMS node 132 and an address of the second IMS node 132 .

[0179] The distributor function is further configured to send a subscription request to the identified second IMS node 132 to open data related to the UE 121, for example, by a sending unit 1530 in the distributor function. The subscription request is adapted to instruct the second IMS node 132 to notify the network open function of the occurrence of a trigger that satisfies the trigger condition when the second IMS node 132 detects the occurrence of a trigger that satisfies the trigger condition, so as to open the open data. The network open function is adapted to be located in the first network node 111. The notification is adapted to enable the network open function to notify the second network node 112 of the occurrence of the detected trigger.

[0180] The distributor function may also be configured to send the received notification to the second network node 112, for example via a sending unit 1530 in the distributor function, thereby opening the IMS open data to the second network node 112. The notification is suitable for communicating using the SBI.

[0181] The subscription request may be adapted to include any one or more of the following: a trigger condition and the type of open data to be opened.

[0182] Any one or more of the received subscription request and the sent subscription request may be adapted to be communicated using the SBI.

[0183] The notification may be adapted to include open data.

[0184] The embodiments herein may be implemented by a corresponding processor or one or more processors (eg Fig.15a The processor 1540 of the processing circuit in the distributor function and / or the node including the distributor function depicted in the embodiment of the present invention) and the corresponding computer program code for executing the functions and actions of the embodiments herein are realized. The above-mentioned program code can also be provided as a computer program product, for example in the form of a data carrier carrying a computer program code, when the computer program code is loaded into the distributor function and / or the node including the distributor function, the computer program code is used to execute the embodiments herein. A kind of such carrier can be in the form of a CD ROM disk. However, it is also feasible to use other data carriers (such as memory sticks). In addition, the computer program code can be provided as a pure program code on a server, and is downloaded to the distributor function and / or the node including the distributor function.

[0185] The distributor function and / or the node including the distributor function may also include a memory 1550, which includes one or more storage units. The memory stores instructions executable by the processor 1540 in the distributor function and / or the node including the distributor function. The memory 1550 is arranged to store, for example, information, messages, instructions, subscriber data, data, profile data, service requests, connections, identifications, open data, notifications, subscription requests, communication data and applications to perform the methods herein when being executed in the distributor function.

[0186] In some embodiments, the computer program 1560 includes instructions which, when executed by the corresponding at least one processor 1540, cause the distributor functionality and / or at least one processor 1540 of a node including the distributor functionality to perform the actions described above.

[0187] In some embodiments, a corresponding carrier 1570 includes a corresponding computer program 1560 , wherein the carrier 1570 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.

[0188] Those skilled in the art will appreciate that the units in the above-mentioned distributor function may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, which are, for example, stored in the distributor function and / or a node including the distributor function, and which are executed by one or more corresponding processors (e.g., the above-mentioned processors). One or more of these processors and other digital hardware may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed in multiple separate components, whether packaged separately or assembled into a system on a chip (SoC).

[0189] To perform method actions, a locator function and / or a node including a locator function may include Fig.16a and 16b The locator function is configured to handle subscriptions to IMS open data open in the communication network 100. The open data is adapted to be associated with a UE 121 connected to an IMS network 102 included in the communication network 100. The locator function is adapted to be included in any one of the first IMS node 131 or the third network node 113.

[0190] The locator function and / or a node including the locator function may include an input and output interface 1600, which is configured to communicate with, for example, the first UE 121, the first network node 111, the second network node 112, the third network node 113, the first IMS node 131 and the second IMS node 132, and with network nodes in the communication network 100 and the IMS network 102.

[0191] The locator function is further configured to receive mapping information applicable to registration of the UE 121 in the second IMS node 132 from the second IMS node 132, for example, via a receiving unit 1610 in the locator function.

[0192] The mapping information may be adapted to include any one or more of the following: a first ID adapted to identify the UE 121 , a second ID adapted to identify the second IMS node 132 , and an address of the second IMS node 132 .

[0193] The mapping information may be adapted to be received via the SBI.

[0194] The locator function is further configured to locate, based on a request from the distributor function, data suitable for identifying the second IMS node 132 serving the UE 121 based on the mapping information, e.g., by a locating unit 1620 in the locator function. The distributor function is suitable for being included in any one of the first network node 111 or the first IMS node 131.

[0195] Locating data adapted to identify the second IMS node 132 may further be adapted to include receiving a request from a distributor function. The request may be adapted to include a first ID adapted to identify the UE 121.

[0196] The locator function is further configured to provide the distributor function with data suitable for identifying the second IMS node 132 serving the UE 121, for example, by a providing unit 1630 in the locator function. The data suitable for identifying the second IMS node 132 is suitable for enabling the distributor function to send a subscription request to the second IMS node 132 to open data related to the UE 121. The subscription request is suitable for instructing the second IMS node 132 to notify the network opening function of the occurrence of a trigger that meets the trigger condition when the second IMS node 132 detects the occurrence of a trigger that meets the trigger condition, so as to open the open data. The network opening function is suitable for being located in the first network node 111.

[0197] Providing data suitable for identifying the second IMS node 132 may further be suitable for including sending data suitable for identifying the second IMS node 132 to the distributor function. The data suitable for identifying the second IMS node 132 may be suitable for including any one or more of the following: a second ID suitable for identifying the second IMS node 132 and an address of the second IMS node 132.

[0198] The embodiments herein may be implemented by a corresponding processor or one or more processors, for example Fig.16a The processor 1640 of the processing circuit in the locator function shown in and / or the node including the locator function, and the corresponding computer program code for executing the functions and actions of the embodiments herein. The above-mentioned program code can also be provided as a computer program product, such as in the form of a data carrier carrying a computer program code, when the computer program code is loaded into the locator function and / or the node including the locator function, the computer program code executes the embodiments herein. A kind of such carrier can be in the form of a CD ROM disk. However, it is also feasible to use other data carriers (such as memory sticks). In addition, the computer program code can be provided as a pure program code on a server, and is downloaded to the locator function and / or the node including the locator function.

[0199] The locator function and / or the node comprising the locator function may also include a memory 1650, which includes one or more storage units. The memory stores instructions that can be executed by the processor 1640 in the locator function and / or the node comprising the locator function. The memory 1650 is arranged to store, for example, information, messages, instructions, subscriber data, data, profile data, service requests, connections, identifications, open data, notifications, subscription requests, mapping data, communication data and applications to perform the methods herein when executed in the locator function.

[0200] In some embodiments, the computer program 1660 includes instructions that, when executed by the corresponding at least one processor 1640, cause the locator function and / or at least one processor 1660 of a node including the locator function to perform the above-described actions.

[0201] In some embodiments, a corresponding carrier 1670 includes a corresponding computer program 1660 , wherein the carrier 1670 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.

[0202] Those skilled in the art will appreciate that the units in the above-mentioned locator function may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, such as stored in the locator function and / or a node including the locator function, which is executed by the corresponding one or more processors (such as the above-mentioned processors). One or more of these processors and other digital hardware may be included in a single application-specific integrated circuit (ASIC), or multiple processors and various digital hardware may be distributed in multiple separate components, whether packaged separately or assembled into a system on a chip (SoC).

[0203] Further expansion and changes

[0204] refer to Fig.17 According to an embodiment, the communication system includes a telecommunication network 3210, such as a cellular network of the 3GPP type, which includes an access network 3211, such as a radio access network, and a core network 3214. The core network 3214 may, for example, include a first network node 111, a second network node 112, and a third network node 113. The core network 3214 may also include an IMS network, such as an IMS network 102, which may, for example, include a first IMS node 131 and a second IMS node 132, 133. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c, such as a base station 105, such as an AP STA NB, an eNB, a gNB, or other types of wireless access points, each base station defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c may be connected to the core network 3214 via a wired or wireless connection 3215. A first user equipment (UE), such as UE 121 and / or non-AP STA 3291, located in the coverage area 3213c is configured to be wirelessly connected to or paged by the corresponding base station 3212c. A second UE 3292, such as another terminal 120 and / or non-AP STA in the coverage area 3213a, can be wirelessly connected to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are also applicable to the case where a single UE is in the coverage area or a single UE is connected to the corresponding base station 3212.

[0205] The telecommunications network 3210 itself is connected to a host computer 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-enabled server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. The connections 3221, 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may extend from the core network 3214 to the host computer 3230 via an optional intermediate network 3220. The intermediate network 3220 may be one of a public, private, or managed network, or a combination of more than one of them; the intermediate network 3220 (if any) may be a backbone network or the Internet; in particular, the intermediate network 3220 may include two or more subnetworks (not shown).

[0206] Fig.17 The communication system as a whole enables a connection between one of the connected UEs 3291, 3292 and the host computer 3230. The connection can be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to use the access network 3211, the core network 3214, any intermediate networks 3220, and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 3250. The OTT connection 3250 can be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of the routing of uplink and downlink communications. For example, the base station 3212 may not be informed or need not be informed of the past routing of incoming downlink communications of data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, base station 3212 need not be aware of future routing of outgoing uplink communications originating from UE 3291 toward host computer 3230.

[0207] Now refer to Fig.18Describe the example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to the embodiments. In the communication system 3300, the host computer 3310 includes hardware 3315, the hardware 3315 includes a communication interface 3316, and the communication interface 3316 is configured to establish and maintain a wired or wireless connection with the interface of the different communication devices of the communication system 3300. The host computer 3310 further includes a processing circuit 3318, which may have storage and / or processing capabilities. In particular, the processing circuit 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 3310 further includes software 3311, which is stored in the host computer 3310 or can be accessed by the host computer 3310 and can be executed by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 is operable to provide services to a remote user, such as a UE 3330 connected via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing services to the remote user, the host application 3312 may provide user data transmitted using the OTT connection 3350.

[0208] The communication system 3300 further includes a base station 3320, which is provided in the telecommunication system and includes hardware 3325, which enables the base station 3320 to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 3300, and a communication interface 3326 for establishing and maintaining a connection with a network located in the coverage area ( Fig.18 The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Fig.18 3320) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 3320 also has software 3321 that is stored internally or accessible via an external connection.

[0209] The communication system 3300 further includes the UE 3330 already mentioned. His hardware 3335 may include a radio interface 3337, which is configured to establish and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes a processing circuit 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for running instructions. The UE 3330 further includes software 3331, which is stored in the UE 3330 or can be accessed by the UE 3330 and can be executed by the processing circuit 3338. The software 3331 includes a client application 3332. The client application 3332 can provide services to human or non-human users via the UE 3330 with the support of the host computer 3310. In the host computer 3310, the running host application 3312 can communicate with the running client application 3332 via the OTT connection 3350 terminated at the UE 3330 and the host computer 3310. In providing services to users, the client application 3332 can receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 can transmit both the request data and the user data. The client application 3332 can interact with the user to generate the user data it provides.

[0210] It should be noted that Fig.18 The host computer 3310, base station 3320 and UE 3330 shown in FIG. 33 can be respectively Fig.17 The host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 in FIG. 3293 are the same. That is, the internal workings of these entities may be as follows: Fig.18 As shown in , and independently, the surrounding network topology can be Fig.17 network topology.

[0211] exist Fig.18 33, an OTT connection 3350 is abstractly drawn to illustrate communications between a host computer 3310 and a user device 3330 via a base station 3320, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 3330 or the service provider operating the host computer 3310, or both. When the OTT connection 3350 is active, the network infrastructure may further make decisions by which the routing is dynamically changed (e.g., based on load balancing considerations or reconfiguration of the network).

[0212] The wireless connection 3370 between the UE 3330 and the base station 3320 is consistent with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of OTT services provided to the UE 3330 using the OTT connection 3350, where the wireless connection 3370 forms the last segment. More specifically, the teachings of these embodiments can improve [select applicable RAN effects: data rate, latency, power consumption], thereby providing benefits such as [select applicable corresponding effects for OTT services: reduce user waiting time, relax restrictions on file size, better responsiveness, and extend battery life].

[0213] A measurement process may be provided for the purpose of monitoring data rates, delays, and other factors to which one or more embodiments are improved. There may also be an optional network function for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 3350 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities of the above examples or providing the values ​​of other physical quantities (the software 3311, 3331 may calculate or estimate the monitoring quantities from them). The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 3320, and the base station 3320 may not know or be able to perceive the reconfiguration. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling to facilitate host computer 3310 measurements of throughput, propagation time, latency, etc. The measurements may be accomplished by software 3311, 3331 using OTT connection 3350 to cause messages (particularly empty messages or "dummy" messages) to be transmitted while software 3311, 3331 monitors propagation time, errors, etc.

[0214] Fig.19 1 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station (eg, an AP STA) and a UE (eg, a non-AP STA), which may be a reference Fig.17 and Fig.18 To simplify this disclosure, this section will only include references to Fig.19Drawing. In a first step 3410 of the method, a host computer provides user data. In an optional sub-step 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission to the UE carrying the user data. In an optional third step 3430, the base station transmits the user data carried in the host-initiated transmission to the UE in accordance with the teachings of the embodiments described throughout the present disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0215] Fig. 20 1 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station (eg, an AP STA) and a UE (eg, a non-AP STA), which may be a reference Fig.17 and Fig.18 To simplify this disclosure, this section will only include references to Fig. 20 Drawing. In a first step 3510 of the method, a host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described in the present disclosure, the transmission can be passed via a base station. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0216] Fig.21 1 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station (eg, an AP STA) and a UE (eg, a non-AP STA), which may be a reference Fig.17 and Fig.18 To simplify this disclosure, this section will only include references to Fig.21Drawing. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. In addition, or alternatively, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the running client application may further consider the user input received from the user. Regardless of the specific manner of providing the user data, the UE initiates the transmission of the user data to the host computer in an optional third sub-step 3630. In a fourth step 3640 of the method, the host computer receives the user data sent from the UE in accordance with the teachings of the embodiments described in the present disclosure.

[0217] Fig. 22 1 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station (eg, an AP STA) and a UE (eg, a non-AP STA), which may be a reference Fig.17 and Fig.18 To simplify this disclosure, this section will only include references to Fig. 22 In an optional first step 3710 of the method, the base station receives user data from the UE in accordance with the teachings of the embodiments described in the present disclosure. In an optional second step 3720, the base station initiates a transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0218] When the word “comprising” or “including” is used, it should be interpreted as non-limiting, ie meaning “consisting of at least…”

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

Claims

1. A method executed by a distributor function, the method for processing a subscription to open Internet Protocol Multimedia Subsystem IMS open data in a communication network (100), the open data being related to a user equipment UE (121) connected to an IMS network (102) included in the wireless communication network (100), wherein: The distributor function is included in any one of the following: a first network node (111) or a first IMS node (131), the method comprising: receiving (1001) a request for opening a subscription to IMS open data associated with the UE (121), the request originating from a second network node (112) operating outside the IMS network (102), obtaining (1002) data identifying a second IMS node (132) supporting open capabilities and serving the UE (121) from a locator function, the locator function being included in any one of: the first IMS node (131) or a third network node (113), and sending (1003) a subscription request to the identified second IMS node (132) to open data related to the UE (121), the subscription request instructing the second IMS node (132) to notify a network open function of the occurrence of a trigger that satisfies the trigger condition when the second IMS node (132) detects the occurrence of a trigger that satisfies the trigger condition, so as to open the data, the network open function being located in the first network node (111), The notification enables the network openness function to notify the second network node (112) of the occurrence of the detected trigger.

2. The method according to claim 1, further comprising: receiving (1004) a notification from the second IMS node (132), the notification notifying the distributor function of a satisfied triggering occurrence detected by the second IMS node (132), the triggering occurrence being associated with the UE (121), sending (1005) the received notification to the second network node (112), thereby opening the IMS open data to the second network node (112), and The notification is communicated using a service-based interface SBI.

3. The method according to any one of claims 1 to 2, wherein: Obtaining (1002) data identifying the second IMS node (132) further comprises: sending a request for data identifying the second IMS node (132) to the locator function, the request comprising a first identification ID identifying the UE (121), and receiving the data identifying the second IMS node (132), wherein the data identifying the second IMS node (132) comprises any one or more of the following: - a second ID identifying said second IMS node (132), and - the address of said second IMS node (132).

4. The method according to any one of claims 1 to 3, wherein: The subscription request includes any one or more of the following: - the triggering condition, and - The type of open data to be exposed.

5. The method according to any one of claims 1 to 4, wherein: Any one or more of the received subscription request and the sent subscription request are communicated using the SBI.

6. The method according to any one of claims 1 to 5, wherein: The notification includes the open data.

7. A computer program (1560) comprising instructions which, when executed by a processor (1540), cause the processor (1540) to perform the actions according to any one of claims 1-6.

8. A carrier (1570) comprising the computer program (1560) of claim 7, wherein: The carrier (1570) is one of the following: 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.

9. A method performed by a locator function, the method for processing a subscription to open Internet Protocol Multimedia Subsystem (IMS) open data in a wireless communication network (100), the open data being related to a user equipment UE (121) connected to an IMS network (102) included in the wireless communication network (100), wherein: The locator function is included in any one of the following: a first IMS node (131) or a third network node (113), the method comprising: receiving (1101) from a second IMS node (132) mapping information related to registration of the UE (121) in the second IMS node (132), locating (1102) data identifying the second IMS node (132) serving the UE (121) based on the mapping information, according to a request from a distributor function, the distributor function being included in any of: the first network node (111) or the first IMS node (131), providing (1103) to the distributor function said data identifying the second IMS node (132) serving the UE (121), The data identifying the second IMS node (132) enables the distributor function to send a subscription request for opening data related to the UE (121) to the second IMS node (132), and the subscription request instructs the second IMS node (132) to notify the network opening function of the occurrence of the trigger that meets the trigger condition when the second IMS node (132) detects the occurrence of the trigger that meets the trigger condition, so as to open the open data, and the network opening function is located in the first network node (111).

10. The method according to claim 9, wherein: Locating (1102) data identifying the second IMS node (132) further comprises: receiving a request from the distributor function, the request comprising a first identification ID identifying the UE (121), and wherein providing (1103) the data identifying the second IMS node (132) further comprises: sending the data identifying the second IMS node (132) to the distributor function, wherein the data identifying the second IMS node (132) comprises any one or more of the following: - a second ID identifying said second IMS node (132), and - the address of said second IMS node (132).

11. The method according to any one of claims 9 to 10, wherein: The mapping information includes any one or more of the following: - the first ID of the UE (121), - said second ID of said second IMS node (132), - said address of said second IMS node (132).

12. The method according to any one of claims 9 to 11, wherein: The mapping information is received via a service based interface SBI.

13. A computer program (1660) comprising instructions which, when executed by a processor (1640), cause the processor (1640) to perform the actions according to any one of claims 9 to 12.

14. A carrier (1670) comprising the computer program (1660) of claim 13, wherein: The carrier (1670) is one of the following: 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.

15. A distributor function configured to handle subscriptions to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network (100), the open data being adapted to be associated with a user equipment UE (121) connected to an IMS network (102), the IMS network being adapted to be included in the communication network (100), wherein: The distributor function is adapted to be included in any of the following: a first network node (111) or a first IMS node (131), the distributor function being further configured to: receiving a request for opening a subscription to IMS open data associated with the UE (121), the request being adapted to originate from a second network node (112) adapted to operate outside the IMS network (102), obtaining data suitable for identifying a second IMS node (132) from a locator function, the second IMS node being suitable for supporting open capabilities and serving the UE (121), the locator function being suitable for being included in any one of: the first IMS node (131) or a third network node (113), and sending a subscription request for opening data related to the UE (121) to the identified second IMS node (132), the subscription request being adapted to instruct the second IMS node (132) to notify a network opening function of the occurrence of a trigger satisfying the trigger condition when the second IMS node (132) detects the occurrence of a trigger satisfying the trigger condition, so as to open the data, the network opening function being adapted to be located in the first network node (111), The notification is adapted to enable the network openness function to notify the second network node (112) of the occurrence of the detected trigger.

16. The distributor function of claim 15, further configured to: receiving a notification from the second IMS node (132), the notification being adapted to notify the distributor function of a satisfied triggering occurrence detected by the second IMS node (132), the triggering occurrence being adapted to be associated with the UE (121), sending the received notification to the second network node (112), thereby opening the IMS open data to the second network node (112), and in, The notification is adapted to be communicated using a service based interface SBI.

17. A distributor function according to any one of claims 15-16, wherein: Obtaining data suitable for identifying the second IMS node (132) is further suitable for comprising: sending a request for data identifying the second IMS node (132) to the locator function, the request being suitable for comprising a first identification ID suitable for identifying the UE (121), and receiving the data suitable for identifying the second IMS node (132), wherein the data suitable for identifying the second IMS node (132) is suitable for comprising any one or more of the following: - a second ID adapted to identify said second IMS node (132), and - the address of said second IMS node (132).

18. A distributor function according to any one of claims 15 to 17, wherein: The subscription request is adapted to include any one or more of the following: - the triggering condition, and - The type of open data to be exposed.

19. A distributor function according to any one of claims 15 to 18, wherein: Any one or more of the received subscription request and the sent subscription request are adapted to be communicated using the SBI.

20. A distributor function according to any one of claims 15 to 19, wherein: The notification is adapted to include the open data.

21. A locator function configured to handle subscriptions to open Internet Protocol Multimedia Subsystem (IMS) open data in a communication network (100), the open data being adapted to be associated with a user equipment UE (121) connected to an IMS network (102) included in the communication network (100), wherein: The locator function is adapted to be included in any one of: the first IMS node (131) or the third network node (113), the locator function being further configured to: receiving from a second IMS node (132) mapping information suitable for registration of the UE (121) in the second IMS node (132), locating data suitable for identifying the second IMS node (132) serving the UE (121) based on the mapping information upon a request from a distributor function, the distributor function being suitable for being included in any of: the first network node (111) or the first IMS node (131), providing said data adapted to identify said second IMS node (132) serving said UE (121) to said distributor function, The data suitable for identifying the second IMS node (132) is suitable for enabling the distributor function to send a subscription request for opening data related to the UE (121) to the second IMS node (132), and the subscription request is suitable for instructing the second IMS node (132) to notify the network opening function of the occurrence of the trigger that meets the trigger condition when the second IMS node (132) detects the occurrence of the trigger that meets the trigger condition, so as to open the open data, and the network opening function is suitable for being located in the first network node (111).

22. The locator function of claim 21, wherein: Locating data adapted to identify the second IMS node (132) is further adapted to include: receiving a request from the distributor function, the request being adapted to include a first identification ID adapted to identify the UE (121), and wherein providing the data suitable for identifying the second IMS node (132) is further suitable for comprising: sending the data suitable for identifying the second IMS node (132) to the distributor function, wherein the data suitable for identifying the second IMS node (132) is suitable for comprising any one or more of the following: - a second ID adapted to identify said second IMS node (132), and - the address of said second IMS node (132).

23. A locator function according to any one of claims 21-22, wherein: The mapping information is suitable for including any one or more of the following: - the first ID suitable for identifying the UE (121), - said second ID adapted to identify said second IMS node (132), and - said address of said second IMS node (132).

24. A locator function according to any one of claims 21 to 23, wherein: The mapping information is adapted to be received via a service based interface SBI.

Images