First network node, second network node and methods performed thereby for handling triggers

By exchanging trigger and limit information between network nodes, the method optimizes CHF-CHF communication, reducing resource wastage and processing load, and ensuring aligned trigger configurations.

WO2026233540A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2025/062420
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing methods for handling charge requests in communications networks lead to resource wastage due to bandwidth requirements and processing load, with potential misalignment of trigger limits between producer and consumer CHFs, resulting in frequent interrogations and unnecessary communication.

Method used

Implement a method where network nodes exchange information on supported triggers and trigger limits, aligning their capabilities through a computer-implemented approach, thereby optimizing CHF-CHF communication by adjusting and aligning trigger configurations.

Benefits of technology

This method reduces unnecessary communication and processing load by ensuring aligned trigger and limit configurations, preventing unwanted trigger arming or ignoring, and optimizing resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2025062420_12112026_PF_FP_ABST
    Figure EP2025062420_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method performed by a first network node (111) in a first communications network (101). The first network node (111) receives (301) a first indication from a second network node (112) in a second communications network (102). The first indication indicates first information indicating first triggers of charging events supported by the second network node (112). The first network node (111) adjusts (302), based on the first information, second information indicating second triggers of the charging events supported by the first network node (111). The first network node (111) sends (303), responsive to the first indication, a second indication to the second network node (112) indicating third information indicating third triggers of the charging events supported by the first network node (111). At least a subset of the second information has been adjusted by the first network node (111) in the third information, according to the first information. Publ.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] FIRST NETWORK NODE, SECOND NETWORK NODE AND METHODS PERFORMED THEREBY FOR HANDLING TRIGGERS

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to a first network node and methods performed thereby for handling triggers. The present disclosure further relates generally to a second network node and methods performed thereby, for handling triggers. The present disclosure also relates generally to computer programs and computer-readable storage mediums, having stored thereon the computer programs to carry out these methods.

[0004] BACKGROUND

[0005] Computer systems in a communications network or communications system may comprise one or more network nodes. A network node may comprise one or more processors which, together with computer program code may perform different functions and actions, a memory, a receiving port, and a sending port. A network node may be, for example, a server. Network nodes may perform their functions entirely on the cloud.

[0006] The communications network may cover a geographical area which may be divided into cell areas, each cell area being served by a type of network node in the Radio Access Network (RAN), radio network node or Transmission Point (TP), for example, an access node such as a Base Station (BS), e.g., a Radio Base Station (RBS), which sometimes may be referred to as e.g., gNB, evolved Node B (“eNB”), “eNodeB”, “NodeB”, “B node”, or Base Transceiver Station (BTS), depending on the technology and terminology used. The base stations may be of different classes such as e.g., Wide Area Base Stations, Medium Range Base Stations, Local Area Base Stations and Home Base Stations, based on transmission power and thereby also cell size. A cell may be understood to be the geographical area where radio coverage may be provided by the base station at a base station site. One base station, situated on the base station site, may serve one or several cells. Further, each base station may support one or several communication technologies. The telecommunications network may also comprise network nodes which may serve receiving nodes, such as user equipments, with serving beams.

[0007] The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a New Radio Interface called Next Generation Radio or New Radio (NR), as well as a Fifth Generation (5G) Packet Core Network, which may be referred to as 5G Core Network (5GC). The advantages of 5G NR may include higher bandwidth, more resources, low latency and network slicing. 5G may provide services tovarious applications, such as enhanced Mobile Broad Band (eMBB), machine to Machine type communication (mMTC), Ultra Reliable Low Latency Communication (URLLC), etc.

[0008] Figure 1 is a schematic diagram depicting a particular example of a 5G reference architecture of a policy and charging control framework, as defined by 3GPP, which may be used as a reference for the present disclosure. An Application Function (AF) 1 may provide a service in the communications system and may interact with the 3GPP Core Network through a Network Exposure Function (NEF) 2. The AF 1 may allow external parties to use the Exposure Application Programming Interfaces (APIs) offered by the network operator. In case the AF 1 is trusted, e.g., internal to the network operator, the AF 1 may interact with the 3GPP Core Network directly, with no NEF 2 involved. The NEF 2 may support different functionality. Specifically, the NEF 2 may support different Exposure APIs. A Session Management Function (SMF) 3 may support different functionalities and may configure a User Plane function (UPF) 4. The UPF 4 may support handling of user plane traffic, including packet inspection, packet routing and forwarding, traffic usage reporting, Quality of Service (QoS) handling based on the rules received from the SMF 3. A Unified Data Repository (UDR) 5 may store data grouped into distinct collections of subscription-related information: subscription data, policy data, structured data for exposure, and application data. A Charging Function (CHF) 6 may support charging related functionality, specifically online and offline charging. A Policy Control Function (PCF) 7 may support a unified policy framework to govern the network behavior. Specifically, the PCF 7 may provide Policy and Charging Control (PCC) rules to the Policy and Charging Enforcement Function (PCEF), that is, the SMF 3 / UPF 4 that may enforce policy and charging decisions according to provisioned Policy and Charging Control (PCC) rules. The SMF 3 may receive PCC rules from the PCF 7 and may configure the UPF 4 accordingly. The PCF 7 may provide policy rules to a User Equipment (UE) through an Access and Mobility Function (AMF) 8. The AMF 8 may manage access of the UE. For example, when the UE may be connected through different access networks, and mobility aspects of the UE. A Network Data Analytics Function (NWDAF) 9 may be understood to represent an operator managed network analytics logical function. The NWDAF 9 may be part of the 5GC architecture and may use the mechanisms and interfaces specified for 5GC and Operations, Administration and Maintenance (QAM).

[0009] The NWDAF 9 may interact with different entities for different purposes. A first purpose may be data collection based on event subscription, provided by AMF 8, SMF 3, PCF 7, Unified Data Management (UDM), AF 1, directly or via NEF 2, and QAM. Another purpose may be retrieval of information from data repositories, e.g., UDR 5 via UDM for subscriber-related information. A further purpose may be retrieval of information about Network Functions (NFs), e.g., Network Repository Function (NRF) for Network Function (NF)-related information, and Network Slice Selection Function (NSSF) for slice-related information). Yetanother purpose may be on demand provision of analytics to consumers. Another purpose may be storage in an Analytics Data Repository Function (ADRF) for two types of data: collected Data, e.g., Event Exposure data, and Analytics reports. Each of the UDR 5, the NEF 2, the NWDAF 9, the AF 1 , the PCF 7, the CHF 6, the AMF 8, the SMF 3 and the UPF 4 may have an interface through which they may be accessed, which as depicted in the Figure, may be, respectively: Nudr 10, Nnef 11, Nnwdaf 12, Naf 13, Npcf 14, Nchf 15, Namf 16, Nsmf 17 and N418.

[0010] N107 and N108 may be understood to be, respectively, the interface where the charging requests handshakes between two CHFs may take place. N107 and N108 may be understood to be part of the Nchf interface.

[0011] Some of the use cases of CHF-CHF communications may comprise a Consumer-CHF (C-CHF) via a Business-CHF (B-CHF) interaction, through the N107 interface. An NF, a Charging Trigger Function (CTF), may collect and report charging information per consumer to a B-CHF, and the B-CHF may report the charging information per consumer to the C-CHF. In a Local Breakout roaming scenario, a visited SMF (vSMF) may connect to a local CHF, that is, a visited CHF (vCHF) only, and the vCHF may take care of charging interaction with a home CHF (hCHF) responsible for charging the end user. The vCHF may handle as Business CHF, which may take care of partner charging and the hCHF may handle the charging of the end user. A business CHF may be used for Business to Business (B2B). The B-CHF may be understood to perform charging functionalities for the business. The B2B may be understood to describe a type of business relationship in which businesses may provide goods or services to other businesses.

[0012] A Mobile Virtual Network Operator (MVNO) may be understood to be responsible to provide mobile communications to its subscribers without having its own mobile network infrastructure. A Mobile Network Operator (MNO) may be understood to have the ability to provide a mobile communication service that may be completely owned and controlled by the MNO itself. It may possess its own radio network license and all the required elements along with the capability of providing end-to-end solutions to the end user. An MNO may typically own a full-fledged mobile network infrastructure, customer care, marketing, billing, and also radio spectrum allocation such as 3G, 4G, 5G & LTE.

[0013] In an MNO-MVNO scenario, an SMF may be connected with a Local CHF which may takes care of MNO charging. The MNO CHF may connect with the MVNO CHF, which may be referred to as Actor-CHD or A-CHF. The MVNO CHF may be managed by the MVNO and may take care of the end user charging.

[0014] Another use case may concern a B-CHF via C-CHF interaction, through the N108 interface. The NF, that is, the CTF, may collect and report the charging information per consumer to a C-CHF, and the C-CHF may report the charging information per consumer tothe B-CHF. A network slice charging scenario may involve an inter CHF interaction to support a converged charging for tenant (B-CHF) and UEs (C-CHF) belonging to the tenant at same time. A Time-Sensitive Network (TSN) charging scenario may involve an inter CHF interaction to support converged charging for Time-Sensitive Communication (TSC) traffic, via a C-CHF, belonging to the same Time-Sensitive Network (TSN) bridge, managed by a corresponding B-CHF. A TSN bridge may be understood to refer to the integration of a 5G system (5GS) with a TSN allowing 5G to support time-sensitive applications. A TSN bridge may facilitate communication and ensure that data packets may be transmitted with minimal delay and maximum reliability across network segments.

[0015] With the existing interface today, Nchf converged charging, a C-CHF may share the information in a charging data request towards a provider CHF in the below InterCHFInformation structure. The InterCHFInformation structure may be understood to be the structure which may be part of a ChargingDataRequest and a ChargingDataResponse. The InterCHFInformation may contain the information when CHF-CHF may communicate. Also, the same structure may be used in response as well for sharing the information from provider to consumer.

[0016] The InterCHFInformation may contain information such as the originaINFConsumerld which may be passed by a consumer CHF towards the producer. Similarly, the same structure may be used in response. A remoteCHFResource may be populated by a producer CHF towards the consumer CHF.

[0017] schemas :

[0018] ChargingDataRequest :

[0019] type : obj ect

[0020] properties :

[0021] InterCHFInformation :

[0022] $ref : ’ # / components / schemas / InterCHFInformation ’

[0023] InterCHFInformation :

[0024] type : obj ect

[0025] properties :

[0026] remoteCHFResource :

[0027] $ref : ’ TS29571 Common Data . yaml # / components / schemas / Uri ’

[0028] originaINFConsumerld :

[0029] $ref : ’ # / components / schemas / NFIdenti fication ’

[0030] Existing methods to handle charge requests may involve bandwidth requirements and processing load that may lead to waste of resources in a communications network.

[0031] SUMMARY

[0032] According to the foregoing, it is an object of embodiments herein to improve the handling of triggers in a communications network.According to a first aspect of embodiments herein, the object is achieved by a computer-implemented method, performed by a first network node. The method is for handling triggers. The first network node operates in a first communications system. The first network node receives a first indication from a second network node operating in a second communications network. The first indication indicates first information. The first information indicates one or more first respective triggers of one or more respective charging events supported by the second network node in respect to one or more services provided in the second communications network. The first network node adjusts, based on the indicated first information, second information. The second information is configured at the first network node. The second information indicates one or more second respective triggers of the one or more respective charging events supported by the first network node. The first network node sends, responsive to the received first indication, a second indication to the second network node. The second indication indicates third information. The third information indicates one or more third respective triggers of the one or more respective charging events supported by the first network node. At least a subset of the second information has been adjusted by the first network node in the third information, according to the indicated first information.

[0033] According to a second aspect of embodiments herein, the object is achieved by a computer-implemented method, performed by a second network node. The method is for handling triggers. The second network node operates in the second communications network. The second network node sends the first indication to the first network node operating in a first communications network. The first indication indicates the first information indicating the one or more first respective triggers of the one or more respective charging events supported by the second network node in respect to the one or more services provided in the second communications network. The second network node receives, responsive to the sent first indication, the second indication from the first network node. The second indication indicates the third information indicating the one or more third respective triggers of the one or more respective charging events supported by the first network node. At least a subset of the second information configured at the first network node has been adjusted by the first network node in the third information, according to the indicated first information. The second information indicates the one or more second respective triggers of the one or more respective charging events supported by the first network node.

[0034] According to a third aspect of embodiments herein, the object is achieved by the first network node. The first network node may be understood to be for handling the triggers. The first network node is configured to operate in the first communications system. The first network node is configured to receive the first indication from the second network node configured to operate in the second communications network. The first indication is configured to indicate the first information configured to indicate the one or more first respective triggersof the one or more respective charging events configured to be supported by the second network node in respect to the one or more services configured to be provided in the second communications network. The first network node is also configured to adjust, based on the first information configured to be indicated, the second information configured at the first network node. The second information is configured to indicate the one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node. The first network node is further configured to send, responsive to the first indication configured to be received, the second indication to the second network node. The second indication is configured to indicate the third information configured to indicate the one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node. At least the subset of the second information is configured to have been adjusted by the first network node in the third information, according to the first information configured to be indicated.

[0035] According to a fourth aspect of embodiments herein, the object is achieved by the second network node. The second network node may be understood to be for handling the triggers. The second network node is configured to operate in the second communications network. The second network node is further configured to send the first indication to the first network node configured to operate in the first communications network. The first indication is configured to indicate the first information configured to indicate the one or more first respective triggers of the one or more respective charging events configured to be supported by the second network node in respect to the one or more services configured to be provided in the second communications network.

[0036] The second network node 112 is further configured to receive, responsive to the first indication configured to be sent, the second indication from the first network node. The second indication is configured to indicate the third information configured to indicate the one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node. At least the subset of the second information configured at the first network node is configured to have been adjusted by the first network node in the third information, according to the first information configured to be indicated. The second information is configured to indicate the one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node.

[0037] According to a fifth aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the first network node.

[0038] According to a sixth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprisinginstructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the first network node.

[0039] According to a seventh aspect of embodiments herein, the object is achieved by a computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the second network node.

[0040] According to an eighth aspect of embodiments herein, the object is achieved by a computer-readable storage medium, having stored thereon the computer program, comprising instructions which, when executed on at least one processing circuitry, cause the at least one processing circuitry to carry out the method performed by the second network node.

[0041] By receiving the first indication, the first network node may be enabled to obtain information on the triggers and the trigger limits, e.g., minimum limits, supported by the second network node, that may need to be granted by the first network node.

[0042] By adjusting the second information based on the first information, the first network node may enable to find the trigger or triggers, and / or trigger limits, the first network node may support from the request and may thereby be enabled to only respond with the common trigger or triggers, and / or trigger limits, supported by the first network node, e.g., that may need to be granted by the first network node. This may enable the first network node to become aligned with respect to the triggers and limit triggers with the second network node. This may in turn enable that an NF Consumer may be also aligned with the triggers and limit triggers through the communication via second network node. The frequent interrogation between the first communications network and the second communications network may be avoided. Either unwanted trigger arming or ignoring of triggers may be also advantageously avoided.

[0043] By sending the second indication indicating the third indication, the first network node may enable triggers based on the common triggers or triggers, and / or trigger limits in the response, supported by the first network node, that may need to be granted by the first network node. As stated earlier, this may enable the first network node to become aligned with respect to the triggers and limit triggers with the second network node. The frequent interrogation between the first communications network and the second communications network 102 may be avoided. Either unwanted trigger arming or ignoring of triggers may be also advantageously avoided.

[0044] BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.Figure 1 is a schematic diagram illustrating an example of a 5G Network Architecture, according to existing methods.

[0046] Figure 2 is a schematic diagram illustrating two non-limiting examples, in panels a) and b), of a communications network, according to embodiments herein.

[0047] Figure 3 is a flowchart depicting a method in a first network node, according to embodiments herein.

[0048] Figure 4 is a flowchart depicting a method in a second network node, according to embodiments herein.

[0049] Figure 5 is a signalling diagram depicting a non-limiting example of the methods performed according to embodiments herein.

[0050] Figure 6 is a signalling diagram depicting particular aspects of a non-limiting example of the method performed according to embodiments herein.

[0051] Figure 7 is a schematic block diagram illustrating an embodiment of a first network node, according to embodiments herein.

[0052] Figure 8 is a schematic block diagram illustrating an embodiment of a second network node, according to embodiments herein.

[0053] DETAILED DESCRIPTION

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

[0055] As per 3GPP TS 32.290, v. 18.7.0, an NF Consumer may connect with a consumer CHF. A consumer CHF may connect with the producer CHF. As per 3GPP 32.290, v. 18.7.0, the consumer CHF may: a) send a Charging Data Request, whether it may be an initial request or an update, to a producer CHF, with or without the amount of quota, dependent on the NF consumer requested, or b) send the Charging Data Request, whether it may be an initial request or an update, to the producer CHF with the amount of quota larger than the amount from the NF Consumer, e.g., a CTF, or c) allocate the quota based on previous granted quota from the producer CHF, dependent on whether the consumer CHF has available quota.

[0056] An end user may initiate the data session with quota. For example, the NFConsumer may request a quota of 1GB from the consumer CHF, representing the limit up to which the end-user may consume data. Once the usage may reach 1GB, the NFConsumer may request a new quota, and this cycle may continue. When a session is initiated by the NFConsumer, the consumer CHF may request a quota from the producer CHF. This quota may be 1GB or more. If a larger quota is requested, such as 5GB, the consumer CHF may manage the session until the 5GB limit is reached. Once the usage reaches 5GB, the consumer CHF may report the usage and may request additional quota from the producer CHF.Quota management may be understood to be the process of tracking and controlling the consumption of allocated resources, such as data or service usage, to ensure compliance with predefined limits. It may be understood to involve monitoring usage levels and requesting additional quota when the current allocation may be exhausted.

[0057] An end user may initiate the data session without quota. A session may be initiated by the NFConsumer solely for authentication purposes, without an initial quota. In these scenarios, the consumer CHF may choose to request a quota or proceed without one.

[0058] Based on the above, it may be understood that the consumer CHF may have its own logic in handling a session with or without communication with a producer CHF. A session may be understood to refer to a period for an end-user, e.g., a mobile user, during which the NFConsumer may interact with the consumer CHF to consume data or services.

[0059] With this understanding, the below issues may be found with the existing or published technology.

[0060] One issue concerns limit triggers. It may be possible that limits may be configured in the producer CHF lower than the consumer CHF or NFConsumer, e.g., the CTF. This may break the independency of the quota management due to low limit values. Independency in quota management may be understood to refer to the ability of the consumer CHF to autonomously manage and control resource consumption without frequent interaction with the producer CHF. When the producer CHF may set limits for sessions, such as volume, time, or service-specific quotas, these limits may restrict the consumer CHF or NFConsumer before fully utilizing the allocated quota.

[0061] Another consequence of the limits configured in the producer CHF being lower than the consumer CHF or NFConsumer, e.g., the CTF, may be that the NF Consumer may be armed to report the consumed units, e.g., volume, time, service specific, number of short message system (SMS), Multimedia Messaging Service (MMS), events, etc., based on the limit value, resulting in frequent interrogation and thereby more processing load on NFConsumer and consumer CHF. Interrogation may be understood as the communication between two NF. A Communication may occur when the limits may be exhausted, quota exhausted or any trigger e.g., network event, may have occurred. For example, the lesser limit value, e.g., Time_LIMIT may be 300s, provided by a producer CHF, whenever the limit may be crossed, e.g., 300s is reached, the consumer CHF may be expected to report to the producer CHF. This may be understood to mean that the communication may be expected at every LIMIT expiry. On the other hand, if, for example, a trigger is applicable in the consumer CHF and not in producer CHF, then the consumer CHF may report to the producer CHF when the event(trigger) may occur.Yet another consequence of the limits configured in the producer CHF being lower than the consumer CHF or NFConsumer, e.g., the CTF, may be that, since the CHF-CHF communication may be across territories, this may lead to a higher bandwidth requirement.

[0062] Another issue with the existing or published technology may be that it may also be possible that certain triggers may not be supported in the NFConsumer, e.g., the CTF. The C-CHF may be configured in such way these may be not armed towards the NFConsumer. But this information may not be available for the producer CHF, which may be not in control by local operation. This may cause the producer CHF to arm the triggers based on the supported releases between CHF and CHF.

[0063] The producer CHF may support a certain trigger which the C-CHF may not support and vice versa. Although the CHF may communicate based on releases and feature negotiated, still certain triggers may not be feature dependent. This may lead to either unwanted triggers being armed, or triggers being ignored.

[0064] Certain aspects of the present disclosure and their embodiments address the challenges identified with the existing methods and provide solutions to the challenges discussed.

[0065] Embodiments herein may be understood to provide an optimized handling of trigger and limits in CHF-CHF communication. Embodiments herein may be understood to relate to making a producer CHF aware of the supported trigger and minimum limits that may be expected by a consumer CHF and its NFConsumer network.

[0066] Particularly, examples of embodiments herein may introduce the Information Elements (lEs) which may be provided the information of supported triggers and the minimum limits to be granted by the producer CHF. This information may be added under the existing Information Element (IE), interCHFInformation.

[0067] Some of the embodiments contemplated will now be described more fully hereinafter with reference to the accompanying drawings, in which examples are shown. In this section, the embodiments herein will be illustrated in more detail by a number of exemplary embodiments. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. It should be noted that the exemplary embodiments herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments.

[0068] Several embodiments and examples are comprised herein. It should be noted that the embodiments and / or examples herein are not mutually exclusive. Components from one embodiment or example may be tacitly assumed to be present in another embodiment orexample and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments and / or examples.

[0069] Figure 2 depicts two non-limiting examples, in panels “a” and “b”, respectively, of a first communications network 101 and a second communications network 102, in which embodiments herein may be implemented. In some example implementations, any of the first communications network 101 and the second communications network 102 may be, respectively, a first computer network and a second computer network, such as that depicted in the non-limiting examples of Figure 2 a) for both of the first communications network 101 and the second communications network 102. In other example implementations, any of the first communications network 101 and the second communications network 102 may be implemented, respectively, in a first telecommunications system and a second telecommunications system, sometimes also referred to as a cellular radio system, cellular network or wireless communications system, as that depicted in panel b) of Figure 2 for both of the first communications network 101 and the second communications network 102. In some examples, any of the first telecommunications system and the second telecommunications system may comprise network nodes which may serve receiving nodes, such as wireless devices, with serving beams.

[0070] In some examples, any of the first telecommunications system and the second telecommunications system may be, for example, a communications network, such as 5G system, or Next Gen network. In other examples, the wireless communications network 100 may be a newer system, e.g., a Sixth Generation (6G) system, with similar functionality. Yet in other examples, any of the first telecommunications system and the second telecommunications system may additionally, or alternatively, support other technologies, such as LTE, e.g., LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex (HD-FDD), LTE operating in an unlicensed band, Wideband Code Division Multiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD, Global System for Mobile communication (GSM) / Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, network comprising of any combination of Radio Access Technologies (RATs) such as e.g., Multi-Standard Radio (MSR) base stations, multi-RAT base stations etc., any 1 rd Generation Partnership Project (3GPP) cellular network, Wireless Local Area Network / s (WLAN) or WiFi network / s, Worldwide Interoperability for Microwave Access (WiMax), Internet of Things (loT), Machine Type Communication (MTC), IEEE 802.15.4-based low-power short-range networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave, Bluetooth Low Energy (BLE), or any cellular network or system.

[0071] Any of the first communications network 101 and the second communications network 102 may respectively comprise a plurality of nodes, whereof a first network node 111 isdepicted in Figure 2 as being comprised in the first communications network 101, and a second network node 112 is depicted in Figure 2 as being comprised in the second communications network 102. Any of the first communications network 101 and the second communications network 102 100 may comprise additional nodes.

[0072] Any of the first network node 111 and the second network node 112 may be understood, respectively, as a first computer system or server and a second computer system or server. Any of the first network node 111 and the second network node 112 may be implemented as a standalone server in e.g., a host computer in a respective cloud 115, 116, as depicted in the non-limiting example of Figure 2b). In other examples, any of the first network node 111 and the second network node 112 may be a distributed node or distributed server, such as a virtual node in the respective cloud 115, 116, and may perform some of its respective functions locally, e.g., by a client manager, and some of its functions in the respective cloud 115, 116, by e.g., a server manager. In other examples, any of the first network node 111 and the second network node 112 may perform its functions entirely on the respective cloud 115, 116, or partially, in collaboration or collocated with a radio network node. Yet in other examples, any of the first network node 111 and the second network node 112 may also be implemented as processing resources in a server farm. Any of the first network node 111 and the second network node 112 may be under the ownership or control of a respective service provider or may be operated by the respective service provider, or on behalf of the respective service provider.

[0073] In some embodiments, any of the first network node 111 and the second network node 112 may be a core network node, such as, e.g., a CHF. Particularly, the first network node 111 may be a first CHF, e.g., a producer CHF, and the second network node 112 may be a second CHF, e.g., a consumer CHF.

[0074] Any of the first communications network 101 and the second communications network 102 may respectively comprise radio network nodes, such a first radio network node 121, depicted in Figure 2 b) as comprised in the first communications network 101 and a second radio network node 122, depicted in Figure 2 b) as comprised in the second communications network 102. Any of the first radio network node 121 and the second radio network node 122 may be, e.g., comprised in a Radio Access Network of the telecommunications system. That is, any of the first radio network node 121 and the second radio network node 122 may be a transmission point such as a radio base station, for example a gNB, an eNB, or any other network node with similar features capable of serving a wireless device, such as a user equipment or a machine type communication device, in the communications system 100. In typical examples, any of the first radio network node 121 and the second radio network node 122 may be a base station, such as a gNB or an eNB. In other examples, any of the first radio network node 121 and the second radio network node 122 may be a distributed node, such asa virtual node in the cloud 115, and may perform its functions entirely on the respective cloud 115, 116 or partially, in collaboration with a radio network node.

[0075] Any of the first radio network node 121 and the second radio network node 122, in some examples, may be, or comprise, a central unit (CU), e.g., a CU control plane (CLI-CP).

[0076] In some examples, any of the first communications network 101 and the second communications network 102 may include an access network, such as a radio access network (RAN), and a core network, which may include one or more core network nodes. The access network may include one or more access network nodes, such as any of the first radio network node 121 and the second radio network node 122, e.g., which may be generally referred to as network nodes, or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node may not necessarily be limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it may be understood that network nodes may include disaggregated implementations or portions thereof. For example, in some embodiments, any of the first communications network 101 and the second communications network 102 may include one or more Open-RAN (ORAN) network nodes. An ORAN network node may be understood to be a node in any of the first communications network 101 and the second communications network 102 that may support an ORAN specification, e.g., a specification published by the O-RAN Alliance, or any similar organization, and may operate alone or together with other nodes to implement one or more functionalities of any node in any of the first communications network 101 and the second communications network 102, including one or more network nodes and / or core network nodes.

[0077] Examples of an ORAN network node may include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller, near-real time or non-real time, hosting software or software plug-ins, such as a near-real time control application, e.g., xApp, or a non-real time control application, e.g., rApp, or any combination thereof, the adjective “open” designating support of an ORAN specification. Any of the first network node 111 and the second network node 112 may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node.

[0078] Furthermore, an ORAN network node may be implemented in a virtualization environment, in which one or more network functions may be virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a ServiceManagement and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

[0079] Any of the first telecommunications system and the second telecommunications system may cover a geographical area, which in some embodiments may be divided into cell areas, wherein each cell area may be served by a respective radio network node, although, one radio network node may serve one or several cells. In the example of panel b) of Figure 2, the first radio network node 121 serves a first cell 131 and the second radio network node 122 serves a second cell 132. Any of the first radio network node 121 and the second radio network node 122 may be of different classes, such as, e.g., macro eNodeB, home eNodeB or pico base station, based on transmission power and thereby also cell size. In some examples, any of the first radio network node 121 and the second radio network node 122 may serve receiving nodes with serving beams. Any of the first radio network node 121 and the second radio network node 122 may be directly connected to one or more core networks.

[0080] Any of the first network node 111 , the second network node 112, the first radio network node 121, the second radio network node 122, and / or any of the nodes comprised in any of the first communications network 101 and the second communications network 102 may support one or several communication technologies, and its name may depend on the technology and terminology used.

[0081] Any of the first communications network 101 and the second communications network 102 may comprise one or more devices. The first communications network 101 may comprise a first device 141, and the second communications network 102 may comprise a second device 142, as depicted in the example of panel b) of Figure 2. Any of the first device 141 and the second device 142 comprised in the first communications network 101 and the second communications network 102 may be a wireless communication device such as a 5G UE, or a UE, which may also be known as e.g., mobile terminal, wireless terminal and / or mobile station, a Customer Premises Equipment (CPE) a mobile telephone, cellular telephone, or laptop with wireless capability, just to mention some further examples. Any of the first device 141 and the second device 142 comprised in the first communications network 101 and the second communications network 102 may be, for example, portable, pocket-storable, hand-held, computer-comprised, or a vehicle-mounted mobile device, enabled to communicate voice and / or data, via the RAN, with another entity, such as a server, a laptop, a Personal Digital Assistant (PDA), or a tablet, Machine-to-Machine (M2M) device, device equipped with a wireless interface, such as a printer or a file storage device, modem, sensor, loT device, or any other radio network unit capable of communicating over a radio link in a communications system. Any of the first device 141 and the second device 142 comprised in the first communications network 101 and the second communications network 102 may be enabled to communicate wirelessly in the telecommunications system. The communication may beperformed e.g., via a RAN, and possibly the one or more core networks, which may be comprised within the telecommunications system.

[0082] It may be understood that any of the first communications network 101 and the second communications network 102 may comprise additional radio network nodes 131, 132 and / or additional devices 141, 142.

[0083] The first network node 111 may be configured to communicate with the second network node 112 over a first link 151, e.g., a wired link. The first network node 111 may be configured to communicate within the first communications network 101 with the first radio network node 121 over a second link 152, e.g., a radio link, or a wired link. The first device 141 may be configured to communicate within the first communications network 101 with the first radio network node 121 over a third link 153, e.g., a radio link. The second network node 112 may be configured to communicate within the second communications network 102 with the second radio network node 122 over a fourth link 154, e.g., a radio link, or a wired link. The second device 142 may be configured to communicate within the second communications network 102 with the second radio network node 122 over a fifth link 155, e.g., a radio link.

[0084] Any of the first link 151, the second link 152, the third link 153, the fourth link 154 and the fifth link 155 may be a direct link or may be comprised of a plurality of individual links, wherein it may go via one or more computer systems or one or more core networks in any of the first communications network 101 and the second communications network 102, or it may go via an optional intermediate network. The intermediate network may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network, if any, may be a backbone network or the Internet; in particular, the intermediate network may comprise two or more sub-networks, which is not shown in Figure 2.

[0085] In general, the usage of “first”, “second”, “third”, “fourth” and / or “fifth”, herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify.

[0086] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0087] Embodiments of a computer-implemented method, performed by the first network node 111, will now be described with reference to the flowchart depicted in Figure 3. The method is for handling triggers. The first network node 111 operates in the first communications network 101.Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description.

[0088] Action 301

[0089] In this Action 301 , the first network node 111 receives a first indication from the second network node 112 operating in the second communications network 102.

[0090] The first indication indicates first information. The first information indicates one or more first respective triggers of one or more respective charging events supported by the second network node 112 in respect to one or more services provided in the second communications network 102.

[0091] The first network node 111 may be a producer CHF. The second network node 112 may be a consumer CHF.

[0092] A charging event may be, for example, a charging session, which may be, for example, when an end user may initiate a voice call, send a text message, or use mobile data. These activities may initiate a session where an NFConsumer(CHF) or the second network node 112, may request a quota from a NFProducer (CHF) or the first network node 111, which may then allocate the quota based on factors such as volume, time, or specific services. During this process, triggers and limit triggers may be configured to monitor the session. As the session progresses, the NFConsumer or the second network node 112 may keep track of consumed units. When the quota is depleted, limits may be reached, or any trigger may be activated, the NFConsumer or the second network node 112 may report the usage and may request additional quota. This cycle may continue until the session may be terminated or the user may cease the activity, ensuring e.g., that usage may be efficiently tracked and managed according to the subscription plan of the user and network policies.

[0093] A trigger may be understood herein as a predefined condition or event that may initiate an action or communication between the second network node 112 and the first network node 111. Triggers may be based on network events or limits. When a network event may occur, such as a user changing the radio access technology (RAT) from 4G to 5G or shifting locations, the NFConsumer or the second network node 112, such as CHF / SMF, may initiate a request to the NFProducer (CHF) or the first network node 111. Limit triggers may be activated when the specified limit for volume, time, or service-specific units may be reached, prompting communication from the NFConsumer or the second network node 112 to the NFProducer or the first network node 111.In some embodiments, the first indication may indicate a request for charging data. The first indication may be, e.g., an interCHFInformation.pdu

[0094] The first information may be indicated by one or more information elements (lEs). The one or more lEs may comprise, e.g., a ChargingDataRequest Information Element (IE).

[0095] The one or more first respective triggers may comprise a first list of triggers, for example T1 , T2, T3 and T5, as the triggers supported by the second network node 112. Any of T1 , T2, T3 and T5 may be for example, a user location change, a RAT change, etc.

[0096] In some embodiments, the first indication may indicate one or more first respective trigger limits, which may also be referred to as limit triggers, that may be supported by the second network node 112.

[0097] A trigger limit may be understood herein as a predefined threshold that, when reached, may prompt a specific action or communication between network functions, such as the second network node 112 and the first network node 111. This threshold may relate to usage metrics such as volume, time, or service-specific units, and its activation may ensure efficient resource management and adherence to subscription or policy constraints.

[0098] The one or more first respective trigger limits may comprise one or more of: a first minimal and a first maximal value, of: one or more first limits of: time, volume, event, and limit of number of charging condition changes.

[0099] A limit of time may be understood herein as a predefined duration, e.g., in seconds, during which a particular service or network function may be available or active. Once this time limit may be reached, it may trigger specific actions, such as notifying the user, adjusting service parameters, or initiating communication between network functions to manage resources or enforce policies.

[0100] The limit of time may be e.g., timeLimit.

[0101] A limit of volume may be understood herein as a predefined threshold for the amount of data, e.g., in bytes, or resources that may be consumed within a given period or session. Once this volume limit may be reached, it may trigger specific actions, such as notifying the user, throttling data speeds, or initiating communication between network functions to request additional resources, enforce policies, or adjust service parameters.

[0102] The limit of volume may be e.g., volumeLimit64.

[0103] A limit of event may be understood herein as a predefined threshold related to the frequency or number of specific activities or transactions within a network, such as the number of SMS messages sent, MMS messages transmitted, or Application Programming Interfaces (API) requests made. When this event limit may be reached, it may trigger actions such as notifying the user, restricting further activity, or initiating communication between network functions to manage resources, enforce policies, or adjust service settings to ensure compliance with subscription plans or operational guideline.An event may be understood herein as a specific occurrence or action within a network or system that may trigger a response or initiate communication between components.

[0104] Examples of events may include sending an SMS, transmitting an MMS, making an API request, changing network location, or altering connection type. Events may be often monitored to manage resources, enforce policies, and adjust service parameters according to predefined conditions or thresholds.

[0105] The limit of event may be e.g., eventLimit.

[0106] A minimal value may be understood herein as the lowest acceptable threshold for a limit set by the second network node 112 for the first network node 111. The first network node 111 may be expected to arm the limit at a level not less than this specified minimal value, ensuring that the network may operate efficiently and avoid unnecessary resource usage or frequent interrogations.

[0107] The minimal value may be referred to as Min. The first minimal value may be understood to be the minimal value to be considered by the first network node 111, e.g., the producer CHF. Min may be understood to be the minimum expected value from the first network node 111, e.g., producer CHF, to avoid the frequent interrogations in the network, e.g., NFConsumer to second network node 112, and second network node 112 to first network node 111, and avoid more resource usage. The second network node 112 may be well-informed about the network conditions and may possess knowledge of optimized limit values for parameters such as time, volume, event, etc . When a producer CHF, according to existing methods, may set a limit below these optimized values, it may lead to more frequent interrogations within the network, resulting in increased resource consumption. By the first network node 111 adhering to the optimized limits provided by the second network node 112, unnecessary interrogations may be minimized according to embodiments herein, thereby enhancing network efficiency and reducing resource usage.

[0108] A maximal value may be understood herein as the highest acceptable threshold for a limit established by the second network node 112 for the first network node 111. The first network node 111 may be expected to set or arm the limit at a level not exceeding this specified maximum value, ensuring that the network may operate within safe and efficient boundaries.

[0109] The maximal value may be referred to as max. The first maximal value, “max”, may be understood to be where the second network node 112, e.g., consumer CHF, may state that it may limit any possible loss of data. When a limit is armed with a higher value, any downtime or failure of a consumer CHF or NFConsumer according to existing methods may lead to the loss of limit monitoring and counters. As a result, usage that may occur during this period may not be accurately tracked or charged, potentially leading to unaccounted resource consumption. Maximum limit value may control such loss by limiting to a value.A “default” value may may be used in the case the first network node 111, e.g., the producer CHF may not set any limits. The second network node 112 may send the default to the first network node 111. This may bring the existing behaviour of the first network node 111 on arming the limit triggers values, e.g., as per the first network node 111 configuration. The second network node 112 may not enforce any trigger or limits.

[0110] A number of charging condition changes may be understood herein as the count of deferred triggers that may be held before being reported to the first network node 111 or an NFProducer. In the context of network charging mechanisms, immediate triggers may be processed as soon as the relevant network event may occur, leading to instantaneous updates in charging conditions. Conversely, deferred triggers may be those that accumulate over time and may be reported at a later stage, typically when communication with the first network node 111 or the NFProducer may be established. This count may specify the maximum number of deferred triggers that may be held in the system before they may have to be processed and reported.

[0111] A limit of the number of charging condition changes may be understood herein as a predefined threshold that may govern how many alterations to the charging criteria or parameters may occur during a communication session or service usage period. Once the threshold may be reached, the second network node 112 or a NFConsumer, may report towards the second network node 112 or the NFConsumer.

[0112] The limit of the number of charging condition changes may be e.g., maxNumberOfccc. In some examples, the trigger limits, or limit triggers, may be e.g., timeLimit, volumeLimit64, eventLimit and maxNumberOfccc.

[0113] In some examples, the first information may comprise a parameter indicating a trigger limit rule, e.g., paramerer “triggerLimitRule”, that may indicate the Limit to be considered as minimal or maximal value. Values allowed may be Min, Max, and / or Default Min.

[0114] The second network node 112, e.g., the consumer CHF, e.g., may send the default, min and max limits in the triggerLimitRule.

[0115] The first indication may comprise a further indication indicating that the first indication may apply to one or more of: a session and a rating group.

[0116] A session may be understood as a temporal period during which a user or device may engage in a communication or data exchange with the network, characterized by a sequence of related interactions. This session may encompass activities such as the setup, maintenance, and termination of a connection, allowing for the delivery of services such as voice calls, data transmission, or multimedia streaming.

[0117] A rating group may be understood as a logical grouping of service units or events that may share common charging characteristics, enabling the application of a specific tariff or pricing policy to all items within that group.Table 1 shows the changes that may be introduced to 3GPP TS 32.291, v. 18.7.0 according to examples of embodiments herein.

[0118] The interCHFInformation structure shown in Table 1 may be understood to be an example of the first indication.

[0119] The ChargingDataRequest shown in Table 1 may be understood to indicate an example of the first information.

[0120] The first information may comprise a new attribute that may be added in the interCHFInformation structure under ChargingDataRequest to make the first network node 111, e.g., a producer CHF, be aware of the triggers and minimum limits applicable in the second network node 112, e.g., the consumer nodes, consumer CHF and NF Consumer. Applicable here may be understood to mean that the triggers and limits defined in the second network node 112 may be relevant and enforceable within the operational context of the first network node 111. This may ensure that both, the first network node 111 and the second network node 112 may be synchronized with respect to appliable triggers and limits.

[0121] In Table 1 , the attribute names “supported triggers” and “triggerLimitRule” may be understood to be examples of the first information.

[0122]

[0123]

[0124] Table 1.

[0125] The introduced IE supportedTriggers may be understood to be the first list of Triggers. The second network node 112, e.g., a consumer CHF, may be required to send the first list of supported Triggers as each element to the list along with a respective category of every trigger, e.g., triggercategory.

[0126] Table 2 may be understood to depict the existing structure of Trigger. This may be understood to be added herein for information and no change may be understood to be proposed.

[0127]

[0128] " "

[0129] " "

[0130] " "

[0131] " "

[0132] "

[0133] "

[0134]

[0135] Table 2.

[0136] By receiving the first indication in this Action 301 , the first network node 111 may be enabled to obtain information on the triggers and the trigger limits, e.g., minimum limits, supported by the second network node 112, that may need to be granted by the first network node 111. This may give an opportunity to the first network node 111 to become aligned with respect to the triggers and limit triggers with the second network node 112. This may in turnenable that an NF Consumer may be also aligned with the triggers and limit triggers through the communication via second network node 112. The frequent interrogation between the first communications network 101 and the second communications network 102 may therefore be avoided.

[0137] Either unwanted trigger arming or ignoring of triggers may be also advantageously avoided.

[0138] Action 302

[0139] In this Action 302, the first network node 111 adjusts, based on the indicated first information, second information. The second information is configured at the first network node 111. The second information indicates one or more second respective triggers of the one or more respective charging events supported by the first network node 111.

[0140] The one or more second respective triggers may comprise a second list of triggers, for example, T1 , T2, T4 and T5, as the triggers supported by the first network node 111.

[0141] In some embodiments, the adjusting in this Action 302 may comprise selecting as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that may be also supported by the first network node 111.

[0142] In some embodiments wherein the first indication may indicate the one or more first respective trigger limits, the adjusting in this Action 302 may comprise changing one or more second respective trigger limits configured by default at the first network node 111.

[0143] By, in this Action 302, adjusting the second information based on the first information, the first network node 111 may enable to find the trigger or triggers, and / or trigger limits, the first network node 111 may support from the request and may be thereby be enabled, in the next Action 303, to only respond with the common trigger or triggers, and / or trigger limits, supported by the first network node 111, e.g., the producer CHF, that may need to be granted by the first network node 111. As stated earlier, this may enable the first network node 111 to become aligned with respect to the triggers and limit triggers with the second network node 112. This may in turn enable that an NF Consumer may be also aligned with the triggers and limit triggers through the communication via second network node 112. The frequent interrogation between the first communications network 101 and the second communications network 102 may be avoided. Either unwanted trigger arming or ignoring of triggers may be also advantageously avoided.

[0144] Action 303

[0145] In this Action 303, the first network node 111 sends, responsive to the received first indication, a second indication to the second network node 112. The second indication indicates third information. The third information indicates one or more third respectivetriggers of the one or more respective charging events supported by the first network node 111. At least a subset of the second information has been adjusted by the first network node 111 in the third information, according to the indicated first information.

[0146] The first network node 111 may the use only a subset of the common triggers, between the first network node 111 and the second network node 112, applicable for the current chargeable event.

[0147] The one or more third respective triggers may comprise a third list, for example, T1, T2, and T5, as the triggers supported by the first network node 111 that may also be supported by the second network node 112.

[0148] In some embodiments one of the following may apply. According to a first option, the one or more second respective triggers may be different than the one or more third respective triggers. According to a second option, the one or more second respective triggers may be the same as the one or more third respective triggers.

[0149] In some embodiments, the one or more second respective triggers may be different than the one or more third respective triggers, and the adjusting in Action 302 may comprise selecting as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that are also supported by the first network node 111.

[0150] The the first network node 111, e.g., producer CHF, may be required to find the supported trigger or triggers from the request and may be required to only respond with the common trigger or triggers supported by the first network node 111 , e.g., producer CHF.

[0151] In case no triggers may be sent by the first network node 111, e.g., the producer CHF, then the second network node 112, e.g., the consumer CHF, may enable and disable triggers based on its configuration.

[0152] In some embodiments, the one or more second respective triggers may be the same as the one or more third respective triggers. In some of these embodiments, the first indication may indicate one or more first respective trigger limits. In some of such embodiments, the adjusting in Action 302 may comprise changing one or more second respective trigger limits configured by default at the first network node 111 . The second indication may indicate one or more third respective trigger limits resulting from the adjusting in Action 302 of the one or more second respective trigger limits.

[0153] In some embodiments, the one or more third respective trigger limits may comprise one or more of: a minimal and a maximal value, of: one or more limits of: time, volume, event, and limit of number of charging condition changes.

[0154] In an illustrative non-limiting example, the second network node 112, e.g., the consumer CHF, may ask, in Action 301, for a minimal allocation of 3600 s time limit and 1GB volumelimit. The first network node 111, e.g., the producer CHF may, in this Action 303, send the second indication with 7200 s as time limit and 2GB as volume limit.

[0155] If the first network node 111, e.g., the producer CHF sends, in this Action 303, a value below “min”, then the second network node 112, e.g., the consumer CHF, may override this with the min value. Also, in case no limit may be set by the first network node 111, e.g., the producer CHF, then the second network node 112, e.g., the consumer CHF may as well override with a default or a min value.

[0156] It may be noted that in case, trigger Category information, an IE that may be mandatory as part of the existing structure, from the first network node 111 may be not applicable for limit triggers.

[0157] In some embodiments, one or more of the following may apply: a) the first indication may indicate a request for charging data, b) the first network node 111 may be a producer Charging Function and the second network node 112 may be a consumer Charging Function, and c) the second indication may comprise a third indication indicating that the second indication may apply to one or more of: a session and a rating group.

[0158] By, in this Action 303, sending the second indication indicating the third indication, the first network node 111 may enable triggers based on the common triggers or triggers, and / or trigger limits in the response, supported by the first network node 111, e.g., the producer CHF, that may need to be granted by the first network node 111. As stated earlier, this may enable the first network node 111 to become aligned with respect to the triggers and limit triggers with the second network node 112. This may in turn enable that an NF Consumer may be also aligned with the triggers and limit triggers through the communication via second network node 112. The frequent interrogation between the first communications network 101 and the second communications network 102 may be avoided.

[0159] Either unwanted trigger arming or ignoring of triggers may be also advantageously avoided.

[0160] Embodiments of a computer-implemented method, performed by the second network node 112, will now be described with reference to the flowchart depicted in Figure 4. The method is for handling triggers. The second network node 112 operates in the second communications network 102.

[0161] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. One or more embodiments may be combined, where applicable. All possible combinations are not described to simplify the description. The detailed description of some of the followingcorresponds to the same references provided above, in relation to the actions described for the first network node 111, and will thus not be repeated here. For example, the first network node 111 may be a producer CHF and the second network node 112 may be a consumer CHF.

[0162] Action 401

[0163] In this Action 401 , the second network node 112 sends the first indication to the first network node 111 operating in a first communications network 101. The first indication indicates the first information indicating the one or more first respective triggers of the one or more respective charging events supported by the second network node 112 in respect to the one or more services provided in the second communications network 102.

[0164] Action 402

[0165] In this Action 402, the second network node 112 receives, responsive to the sent first indication, the second indication from the first network node 111. The second indication indicates the third information indicating the one or more third respective triggers of the one or more respective charging events supported by the first network node 111. At least a subset of the second information configured at the first network node 111 has been adjusted by the first network node 111 in the third information, according to the indicated first information. The second information indicates the one or more second respective triggers of the one or more respective charging events supported by the first network node 111.

[0166] In some embodiments, one of the following may apply: a) the one or more second respective triggers may be different than the one or more third respective triggers, and b) the one or more second respective triggers may be the same as the one or more third respective triggers.

[0167] In some embodiments, the one or more second respective triggers may be different than the one or more third respective triggers. In some of such embodiments, the adjusting may comprise having selected as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that may also be supported by the first network node 111.

[0168] In some embodiments, the one or more second respective triggers may be the same as the one or more third respective triggers. In some of such embodiments, the first indication may indicate the one or more first respective trigger limits. In such embodiments, the adjusting may comprise changing the one or more second respective trigger limits configured by default at the first network node 111. In such embodiments, the second indication may indicate the one or more third respective trigger limits resulting from the adjusting of the one ormore second respective trigger limits.

[0169] In some embodiments, the one or more third respective trigger limits may comprise one or more of: the minimal and the maximal value, of: the one or more limits of: time, volume, event, and limit of number of charging condition changes.

[0170] In some embodiments, one or more of the following may apply: a) the first indication may indicate the request for charging data, b) the first network node 111 may be a producer Charging Function and the second network node 112 may be a consumer Charging Function, and c) the second indication may comprise the third indication indicating that the second indication may apply to the one or more of: the session and the rating group.

[0171] In some embodiments, the first information may be indicated by the one or more information elements.

[0172] Figure 5 is a signalling diagram depicting a non-limiting example of the methods performed by the first network node 111 and the second network node 112 according to embodiments herein. In Figure 5, the first network node 111 is a producer CHF and the second network node 112 is a consumer CHF. In Figure 5, it may be observed thatTI, T2, T3 and T5 are triggers supported by second network node 112, e.g., the consumerCHF.

[0173] T1,T2,T4, T5 are triggers supported by the first network node 111, e.g., the producer CHF. The common T riggers may be understood to be T1 , T2 and T5. The first network node 111, according to Action 301 and Action 401, may receive the first indication as an interCHFInformation.pdu indicating the first information, in this example, Triggers T1, T2, T3 and T5. The introduced IE supportedTriggers may be understood to be the list of Triggers. The second network node 112 may be required to send the list of supported Triggers as each element to the list along with triggercategory. The first network node 111 may be required to find the supported trigger or triggers from the request and may be required to only respond with the common trigger or triggers supported by producer CHF. According to Action 302, the first network node 111 may adjust the second information, in this example, T 1 ,T2,T4, T5, to select T1 , T2 and T5 as the one or more third respective triggers. This may be sent by the first network node 111, e.g., the producer CHF in the response as third information, according to Action 303 and Action 402. The first network node 111, e.g., the producer CHF may enable triggers based on the common triggers in the response. As depicted in Figure 5, the common triggers may be indicated, in this example, at service session level and RG level, with existing lEs. With existing structure, it may be possible to indicate the limit and triggers set by the first network node 111. The first network node 111, e.g., the producer CHF, may use only a subset of the common triggers applicable for the current chargeable event.

[0174] On the other way, in case no triggers are sent by the first network node 111, e.g., the producer CHF, then the second network node 112, e.g., the consumer CHF, may enable anddisable triggers based on its configuration. It may be noted that in case, trigger Category information, an IE that may be mandatory as part of the existing structure, from the first network node 111 may be not applicable for limit triggers.

[0175] Figure 6 is another signalling diagram depicting another non-limiting example of the methods performed by the first network node 111 and the second network node 112 according to embodiments herein. In Figure 6, the first network node 111 is a producer CHF and the second network node 112 is a consumer CHF. In Figure 6, the first network node 111, according to Action 301 and Action 401, may receive the first indication as an interCHFInformation.pdu indicating the first information, in this example, a Trigger with timeLimit=3600, volumeLimit=1073741824, and the pdu TriggerLimitRule=Min. The second network node 112 may therefore ask for a minimal allocation of 3600 s time limit and 1GB volume limit. According to Action 302, the first network node 111 may adjust the second information, and in this example, set as Min at least the same or a greater Limit Trigger. In this particular example, this may be setting a timeLimit to 7200, and a volumeLimit of 2147483648, that is, 2GB. The first network node 111, according to Action 303 and Action 402, may send the second indication with the third information indicating 7200 s as time limit and 2GB as volume limit. If the first network node 111 sends a value below “min”, then the second network node 112 may override this with the min value. Also, in case no limit may be set by the first network node 111, then the second network node 112 may as well override with a default or a min value.

[0176] As a summarized overview of the foregoing, embodiments herein may be understood to introduce lEs which may provide information on supported triggers and the minimum limits that may need to be granted by the producer CHF. This information may be added under the existing lE(interCHFInformation).

[0177] Certain embodiments herein may provide one or more of the following technical advantage(s). Embodiments herein may be understood to enable that a consumer CHF and a producer CHF may be aligned with respect to the triggers and limit triggers.

[0178] This may in turn enable that an NF Consumer may be also aligned with the triggers and limit triggers through the communication via the consumer CHF.

[0179] Embodiments herein may advantageously enable to avoid frequent interrogation between the consumer and the producer network.

[0180] Embodiments herein may also advantageously enable that either unwanted trigger arming or ignoring of triggers may be avoided.Figure 7 depicts an example of the arrangement that the first network node 111 may comprise to perform the method described in Figure 3 and / or any of Figures 5-6. The first network node 111 may be understood to be for handling the triggers. The first network node 111 is configured to operate in the first communications network 101.

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

[0182] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the first network node 111, and will thus not be repeated here. For example, the first network node 111 may be configured to be a producer CHF and the second network node 112 may be configured to be a consumer CHF.

[0183] In Figure 7, optional components are marked with dashed lines.

[0184] The first network node 111 is configured to receive the first indication from the second network node 112 configured to operate in the second communications network 102. The first indication is configured to indicate the first information configured to indicate the one or more first respective triggers of the one or more respective charging events configured to be supported by the second network node 112 in respect to the one or more services configured to be provided in the second communications network 102.

[0185] The first network node 111 is also configured to adjust, based on the first information configured to be indicated, the second information configured at the first network node 111. The second information is configured to indicate the one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node 111.

[0186] The first network node 111 is further configured to send, responsive to the first indication configured to be received, the second indication to the second network node 112. The second indication is configured to indicate the third information configured to indicate the one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node 111. At least the subset of the second information is configured to have been adjusted by the first network node 111 in the third information, according to the first information configured to be indicated.

[0187] In some embodiments, one of the following may apply: a) the one or more second respective triggers may be configured to be different than the one or more third respective triggers, and b) the one or more second respective triggers may be configured to be the same as the one or more third respective triggers.In some embodiments, the one or more second respective triggers may be configured to be different than the one or more third respective triggers, and the adjusting may be configured to comprise selecting as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that may be also configured to be supported by the first network node 111.

[0188] In some embodiments, the one or more second respective triggers may be configured to be the same as the one or more third respective triggers, the first indication may be configured to indicate the one or more first respective trigger limits, and: a) the adjusting may be configured to comprise changing the one or more second respective trigger limits configured by default at the first network node 111, and b) the second indication may be configured to indicate the one or more third respective trigger limits resulting from the adjusting of the one or more second respective trigger limits.

[0189] In some embodiments, the one or more third respective trigger limits may be configured to comprise one or more of: the minimal and the maximal value, of: the one or more limits of: time, volume, event, and limit of number of charging condition changes.

[0190] In some embodiments, one or more of the following may apply: a) the first indication may be configured to indicate the request for charging data, and b) the first network node 111 may be configured to be a producer Charging Function and the second network node 112 may be configured to be a consumer Charging Function, and c) the second indication may be configured to comprise the third indication configured to indicate that the second indication is configured to apply to one or more of: the session and the rating group.

[0191] In some embodiments, the first information may be configured to be indicated by one or more information elements.

[0192] The embodiments herein in the first network node 111 may be implemented through one or more processors, such as a processing circuitry 701 in the first network node 111 depicted in Figure 7, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first network node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node 111.

[0193] The first network node 111 may further comprise a memory 702 comprising one or more memory units. The memory 702 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first network node 111.In some embodiments, the first network node 111 may receive information from, e.g., the second network node 112, the first radio network node 131 , the first device 141 , and / or another structure in the first communications network 101 or the second communications system 102, through a receiving port 703. In some embodiments, the receiving port 703 may be, for example, connected to one or more antennas in first network node 111. In other embodiments, the first network node 111 may receive information from another structure in the first communications network 101 through the receiving port 703. Since the receiving port 703 may be in communication with the processing circuitry 701, the receiving port 703 may then send the received information to the processing circuitry 701. The receiving port 703 may also be configured to receive other information.

[0194] The processing circuitry 701 in the first network node 111 may be further configured to transmit or send information to e.g., the second network node 112, the first radio network node 131 , the first device 141 , and / or another structure in the first communications network 101 or the second communications system 102, through a sending port 704, which may be in communication with the processing circuitry 701, and the memory 702.

[0195] Those skilled in the art will also appreciate that the units comprised within the first network node 111 described above as being configured to perform different actions, may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processing circuitry 701 , perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0196] The first network node 111 may be configured to perform any of the Actions described in relation to Figure 3 and / or any of Figures 5-6, e.g., by means of the processing circuitry 701 within the first network node 111, configured to perform any of such actions.

[0197] Also, in some embodiments, different units comprised within the first network node 111 may be configured to perform the different actions described above, implemented as one or more applications running on one or more processors such as the processing circuitry 701.

[0198] Thus, the methods according to the embodiments described herein for the first network node 111 may be respectively implemented by means of a computer program 705 product, comprising instructions, i.e., software code portions, which, when executed on at least one processing circuitry 701 , cause the at least one processing circuitry 701 to carry out the actions described herein, as performed by the first network node 111. The computer program 705 product may be stored on a computer-readable storage medium 706. The computer-readable storage medium 706, having stored thereon the computer program 705, maycomprise instructions which, when executed on at least one processing circuitry 701, cause the at least one processing circuitry 701 to carry out the actions described herein, as performed by the first network node 111. In some embodiments, the computer-readable storage medium 706 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 705 product may be stored on a carrier containing the computer program 705 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 706, as described above.

[0199] The first network node 111 may comprise a communication interface configured to facilitate, or an interface unit to facilitate, communications between the first network node 111 and other nodes or devices, e.g., the second network node 112, the first radio network node 131 , the first device 141 , and / or another structure in the first communications network 101 or the second communications system 102. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0200] In other embodiments, the first network node 111 may comprise a radio circuitry 707, which may comprise e.g., the receiving port 703 and the sending port 704.

[0201] The radio circuitry 707 may be configured to set up and maintain at least a wireless connection with the second network node 112, the first radio network node 131 , the first device 141 , and / or another structure in the first communications network 101 or the second communications system 102. Circuitry may be understood herein as a hardware component.

[0202] Hence, embodiments herein also relate to the first network node 111 operative to operate in the first communications network 101. The first network node 111 may comprise the processing circuitry 701 and the memory 702, said memory 702 containing instructions executable by said processing circuitry 701 , whereby the first network node 111 is further operative to perform the actions described herein in relation to the first network node 111, e.g., in Figure 3 and / or any of Figures 5-6.

[0203] Figure 8 depicts an example of the arrangement that the second network node 112 may comprise to perform the method described in Figure 4 and / or any of Figures 5-6. The second network node 112 may be understood to be for handling triggers. The second network node 112 is configured to operate in the second communications network 102.

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

[0205] Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may beused in the other exemplary embodiments. The detailed description of some of the following corresponds to the same references provided above, in relation to the actions described for the second network node 112, and will thus not be repeated here. For example, the first network node 111 may be configured to be a producer CHF and the second network node 112 may be configured to be a consumer CHF.

[0206] In Figure 8, optional components are marked with dashed lines.

[0207] The second network node 112 is configured to send the first indication to the first network node 111 configured to operate in the first communications network 101. The first indication is configured to indicate the first information configured to indicate the one or more first respective triggers of the one or more respective charging events configured to be supported by the second network node 112 in respect to the one or more services configured to be provided in the second communications network 102.

[0208] The second network node 112 is further configured to receive, responsive to the first indication configured to be sent, the second indication from the first network node 111. The second indication is configured to indicate the third information configured to indicate the one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node 111. At least the subset of the second information configured at the first network node 111 is configured to have been adjusted by the first network node 111 in the third information, according to the first information configured to be indicated. The second information is configured to indicate the one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node 111.

[0209] In some embodiments, one of the following may apply: a) the one or more second respective triggers may be configured to be different than the one or more third respective triggers, and b) the one or more second respective triggers may be configured to be the same as the one or more third respective triggers.

[0210] In some embodiments, the one or more second respective triggers may be configured to be different than the one or more third respective triggers, and the adjusting may be configured to comprise having selected as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that may be also configured to be supported by the first network node 111.

[0211] In some embodiments, the one or more second respective triggers may be configured to be the same as the one or more third respective triggers. In some of such embodiments, the first indication may be configured to indicate the one or more first respective trigger limits, and the following may apply: a) the adjusting may be configured to comprise changing the one or more second respective trigger limits configured by default at the first network node 111, and b) the second indication may be configured to indicate the one or more third respective triggerlimits configured to result from the adjusting of the one or more second respective trigger limits.

[0212] In some embodiments, the one or more third respective trigger limits may be configured to comprise one or more of: the minimal and the maximal value, of: the one or more limits of: time, volume, event, and limit of number of charging condition changes.

[0213] In some embodiments, one or more of the following may apply: a) the first indication may be configured to indicate the request for charging data, b) the first network node 111 may be configured to be a producer Charging Function and the second network node 112 may be a consumer Charging Function, and c) the second indication may be configured to comprise the third indication configured to indicate that the second indication may be configured to apply to one or more of: the session and the rating group.

[0214] In some embodiments, the first information may be configured to be indicated by the one or more information elements.

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

[0216] The second network node 112 may further comprise a memory 802 comprising one or more memory units. The memory 802 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the second network node 112.

[0217] In some embodiments, the second network node 112 may receive information from, e.g., the first network node 111 , the second radio network node 132, the second device 142, and / or another structure in the second communications network 102 or the first communications network 101, through a receiving port 803. In some embodiments, the receiving port 803 may be, for example, connected to one or more antennas in second network node 112. In other embodiments, the second network node 112 may receive information from another structure in the second communications network 102 through the receiving port 803. Since the receiving port 803 may be in communication with the processing circuitry 801, thereceiving port 803 may then send the received information to the processing circuitry 801. The receiving port 803 may also be configured to receive other information.

[0218] The processing circuitry 801 in the second network node 112 may be further configured to transmit or send information to e.g., the second radio network node 132, the second device 142, and / or another structure in the second communications network 102 or the first communications network 101, through a sending port 804, which may be in communication with the processing circuitry 801, and the memory 802.

[0219] Those skilled in the art will also appreciate that the units comprised within the second network node 112 described above as being configured to perform different actions, may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the processing circuitry 801 , perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0220] The second network node 112 may be configured to perform any of the Actions described in relation to Figure 4 and / or any of Figures 5-6, e.g., by means of the processing circuitry 801 within the second network node 112, configured to perform any of such actions.

[0221] Also, in some embodiments, different units comprised within the second network node 112 may be configured to perform the different actions described above, implemented as one or more applications running on one or more processors such as the processing circuitry 801.

[0222] Thus, the methods according to the embodiments described herein for the second network node 112 may be respectively implemented by means of a computer program 805 product, comprising instructions, i.e., software code portions, which, when executed on at least one processing circuitry 801, cause the at least one processing circuitry 801 to carry out the actions described herein, as performed by the second network node 112. The computer program 805 product may be stored on a computer-readable storage medium 806. The computer-readable storage medium 806, having stored thereon the computer program 805, may comprise instructions which, when executed on at least one processing circuitry 801, cause the at least one processing circuitry 801 to carry out the actions described herein, as performed by the second network node 112. In some embodiments, the computer-readable storage medium 806 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the computer program 805 product may be stored on a carrier containing the computer program 805 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable storage medium 806, as described above.The second network node 112 may comprise a communication interface configured to facilitate, or an interface unit to facilitate, communications between the second network node 112 and other nodes or devices, e.g., the second radio network node 132, the second device 142, and / or another structure in the second communications network 102 or the first communications network 101. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard.

[0223] In other embodiments, the second network node 112 may comprise a radio circuitry 807, which may comprise e.g., the receiving port 803 and the sending port 804.

[0224] The radio circuitry 807 may be configured to set up and maintain at least a wireless connection with the first network node 111 , the radio network node 130, the device 140, and / or another structure in the second communications network 102. Circuitry may be understood herein as a hardware component.

[0225] Hence, embodiments herein also relate to the second network node 112 operative to operate in the second communications network 102. The second network node 112 may comprise the processing circuitry 801 and the memory 802, said memory 802 containing instructions executable by said processing circuitry 801 , whereby the second network node 112 is further operative to perform the actions described herein in relation to the second network node 112, e.g., in Figure 4 and / or any of Figures 5-6.

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

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

[0228] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.As used herein, the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “and” term, may be understood to mean that only one of the list of alternatives may apply, more than one of the list of alternatives may apply or all of the list of alternatives may apply. This expression may be understood to be equivalent to the expression “at least one of:” followed by a list of alternatives separated by commas, and wherein the last alternative is preceded by the “or” term.

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

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

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

Claims

38CLAIMS:

1. A computer-implemented method performed by a first network node (111), the method being for handling triggers, the first network node (111) operating in a first communications network (101), and the method comprising:- receiving (301) a first indication from a second network node (112) operating in a second communications network (102), the first indication indicating first information indicating one or more first respective triggers of one or more respective charging events supported by the second network node (112) in respect to one or more services provided in the second communications network (102),- adjusting (302), based on the indicated first information, second information configured at the first network node (111), the second information indicating one or more second respective triggers of the one or more respective charging events supported by the first network node (111), and- sending (303), responsive to the received first indication, a second indication to the second network node (112), the second indication indicating third information indicating one or more third respective triggers of the one or more respective charging events supported by the first network node (111), wherein at least a subset of the second information has been adjusted by the first network node (111) in the third information, according to the indicated first information.

2. The method according to claim 1 , wherein one of:- the one or more second respective triggers are different than the one or more third respective triggers, and- the one or more second respective triggers are the same as the one or more third respective triggers.

3. The method according to claim 2, wherein the one or more second respective triggers are different than the one or more third respective triggers, and wherein the adjusting (302) comprises selecting as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that are also supported by the first network node (111).

394. The method according to claim 2, wherein the one or more second respective triggers are the same as the one or more third respective triggers, wherein the first indication indicates one or more first respective trigger limits, and wherein:- the adjusting (302) comprises changing one or more second respective trigger limits configured by default at the first network node (111), and- the second indication indicates one or more third respective trigger limits resulting from the adjusting (302) of the one or more second respective trigger limits.

5. The method according to claim 4, wherein the one or more third respective trigger limits comprise one or more of: a minimal and a maximal value, of: one or more limits of: time, volume, event, and limit of number of charging condition changes.

6. The method according to any of claims 1-5, wherein one or more of:- the first indication indicates a request for charging data,- the first network node (111) is a producer Charging Function and the second network node (112) is a consumer Charging Function, and- the second indication comprises a third indication indicating that the second indication applies to one or more of: a session and a rating group.

7. The method according to any of claims 1-6, wherein the first information is indicated by one or more information elements.

8. A computer-implemented method performed by a second network node (112), the method being for handling triggers, the second network node (112) operating in a second communications network (102), and the method comprising:- sending (401) a first indication to a first network node (111) operating in a first communications network (101), the first indication indicating first information indicating one or more first respective triggers of one or more respective charging events supported by the second network node (112) in respect to one or more services provided in the second communications network (102), and - receiving (402), responsive to the sent first indication, a second indication from the first network node (111), the second indication indicating third information indicating one or more third respective triggers of the one or more respective charging events supported by the first network node (111), wherein at least a subset of second information configured at the first network node (111) has40been adjusted by the first network node (111) in the third information, according to the indicated first information, the second information indicating one or more second respective triggers of the one or more respective charging events supported by the first network node (111).

9. The method according to claim 8, wherein one of:- the one or more second respective triggers are different than the one or more third respective triggers, and- the one or more second respective triggers are the same as the one or more third respective triggers.

10. The method according to claim 9, wherein the one or more second respective triggers are different than the one or more third respective triggers, and wherein the adjusting comprises having selected as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that are also supported by the first network node (111).

11. The method according to claim 9, wherein the one or more second respective triggers are the same as the one or more third respective triggers, wherein the first indication indicates one or more first respective trigger limits, and wherein:- the adjusting comprises changing one or more second respective trigger limits configured by default at the first network node (111), and- the second indication indicates one or more third respective trigger limits resulting from the adjusting of the one or more second respective trigger limits.

12. The method according to claim 11 , wherein the one or more third respective trigger limits comprise one or more of: a minimal and a maximal value, of: one or more limits of: time, volume, event, and limit of number of charging condition changes.

13. The method according to any of claims 8-12, wherein one or more of:- the first indication indicates a request for charging data,- the first network node (111) is a producer Charging Function and the second network node (112) is a consumer Charging Function, and- the second indication comprises a third indication indicating that the second indication applies to one or more of: a session and a rating group.

14. The method according to any of claims 8-13, wherein the first information is indicated by one or more information elements.

15. A first network node (111), for handling triggers, the first network node (111) being configured to operate in a first communications network (101), and the first network node (111) being further configured to:- receive a first indication from a second network node (112) configured to operate in a second communications network (102), the first indication being configured to indicate first information configured to indicate one or more first respective triggers of one or more respective charging events configured to be supported by the second network node (112) in respect to one or more services configured to be provided in the second communications network (102), - adjust, based on the first information configured to be indicated, second information configured at the first network node (111), the second information configured to indicate one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node (111), and- send, responsive to the first indication configured to be received, a second indication to the second network node (112), the second indication being configured to indicate third information configured to indicate one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node (111), wherein at least a subset of the second information is configured to have been adjusted by the first network node (111) in the third information, according to the first information configured to be indicated.

16. The first network node (111) according to claim 15, wherein one of:- the one or more second respective triggers are configured to be different than the one or more third respective triggers, and- the one or more second respective triggers are configured to be the same as the one or more third respective triggers.

17. The first network node (111) according to claim 16, wherein the one or more second respective triggers are configured to be different than the one or more third respective triggers, and wherein the adjusting is configured to comprise selecting as the one or more third respective triggers, the one or more respective first triggers, out of the oneor more second respective triggers, that are also configured to be supported by the first network node (111).

18. The first network node (111) according to claim 16, wherein the one or more second respective triggers are configured to be the same as the one or more third respective triggers, wherein the first indication is configured to indicate one or more first respective trigger limits, and wherein:- the adjusting is configured to comprise changing one or more second respective trigger limits configured by default at the first network node (111), and- the second indication is configured to indicate one or more third respective trigger limits resulting from the adjusting of the one or more second respective trigger limits.

19. The first network node (111) according to claim 18, wherein the one or more third respective trigger limits are configured to comprise one or more of: a minimal and a maximal value, of: one or more limits of: time, volume, event, and limit of number of charging condition changes.

20. The first network node (111) according to any of claims 15-19, wherein one or more of:- the first indication is configured to indicate a request for charging data,- the first network node (111) is configured to be a producer Charging Function and the second network node (112) is configured to be a consumer Charging Function, and- the second indication is configured to comprise a third indication configured to indicate that the second indication is configured to apply to one or more of: a session and a rating group.

21. The first network node (111) according to any of claims 15-20, wherein the first information is configured to be indicated by one or more information elements.

22. A second network node (112), for handling triggers, the second network node (112) being configured to operate in a second communications network (102), and the second network node (112) being further configured to:- send a first indication to a first network node (111) configured to operate in a first communications network (101), the first indication being configured to43indicate first information configured to indicate one or more first respective triggers of one or more respective charging events configured to be supported by the second network node (112) in respect to one or more services configured to be provided in the second communications network (102), and - receive, responsive to the first indication configured to be sent, a second indication from the first network node (111), the second indication being configured to indicate third information configured to indicate one or more third respective triggers of the one or more respective charging events configured to be supported by the first network node (111), wherein at least a subset of second information configured at the first network node (111) is configured to have been adjusted by the first network node (111) in the third information, according to the first information configured to be indicated, the second information being configured to indicate one or more second respective triggers of the one or more respective charging events configured to be supported by the first network node (111).

23. The second network node (112) according to claim 22, wherein one of:- the one or more second respective triggers are configured to be different than the one or more third respective triggers, and- the one or more second respective triggers are configured to be the same as the one or more third respective triggers.

24. The second network node (112) according to claim 23, wherein the one or more second respective triggers are configured to be different than the one or more third respective triggers, and wherein the adjusting is configured to comprise having selected as the one or more third respective triggers, the one or more respective first triggers, out of the one or more second respective triggers, that are also configured to be supported by the first network node (111).

25. The second network node (112) according to claim 23, wherein the one or more second respective triggers are configured to be the same as the one or more third respective triggers, wherein the first indication is configured to indicate one or more first respective trigger limits, and wherein:- the adjusting is configured to comprise changing one or more second respective trigger limits configured by default at the first network node (111), and44- the second indication is configured to indicate one or more third respective trigger limits configured to result from the adjusting of the one or more second respective trigger limits.

26. The second network node (112) according to claim 25, wherein the one or more third respective trigger limits are configured to comprise one or more of: a minimal and a maximal value, of: one or more limits of: time, volume, event, and limit of number of charging condition changes.

27. The second network node (112) according to any of claims 22-26, wherein one or more of:- the first indication is configured to indicate a request for charging data, - the first network node (111) is configured to be a producer Charging Function and the second network node (112) is a consumer Charging Function, and - the second indication is configured to comprise a third indication configured to indicate that the second indication is configured to apply to one or more of: a session and a rating group.

28. The second network node (112) according to any of claims 22-27, wherein the first information is configured to be indicated by one or more information elements.

29. A computer program (705), comprising instructions which, when executed on at least one processing circuitry (701), cause the at least one processing circuitry (701) to carry out the method according to any of claims 1-7.

30. A computer-readable storage medium (706), having stored thereon a computer program (705), comprising instructions which, when executed on at least one processing circuitry (701), cause the at least one processing circuitry (701) to carry out the method according to any of claims 1-7.

31. A computer program (805), comprising instructions which, when executed on at least one processing circuitry (801), cause the at least one processing circuitry (801) to carry out the method according to any of claims 8-14.

32. A computer-readable storage medium (806), having stored thereon a computer program (805), comprising instructions which, when executed on at least one45processing circuitry (801), cause the at least one processing circuitry (801) to carry out the method according to any of claims 8-14.