IP Library Granted Patent US 12,355,913
Granted Patent B2
US 12,355,913 · App. 18/012,265 · Granted Jul 8, 2025

Using subscriber event data to control release operations related to communication session in communications network

Inventors: Amit Kalra (Gurgaon Haryana, IN); Robert Törnkvist (Karlskrona, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04M15/60H04M15/8228H04W76/38
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,355,913
App. No.
18/012,265
Granted
Jul 8, 2025
Kind
B2
Abstract

A network node of a communications network performs operations to determine a data traffic inactivity timer value based on subscriber event data, which identifies a subscriber and service characteristics using a communication session, being processed through a predictive model which uses historical usage data indicating idle times previously measured by charging trigger functions (CTFs) for the subscriber and the service characteristics. The operation further communicate the data traffic inactivity timer value to a CTF to configure monitoring of inactivity of the service using the communication session and to trigger a release operation related to the communication session when a data traffic inactivity timer using the data traffic inactivity timer value is determined to expire based on the monitored inactivity of the service.

Claims (44)

1. A method by a network node of a communications network, the method comprising:

determining a data traffic inactivity timer value based on subscriber event data, which identifies a subscriber and service characteristics using a communication session, being processed through a predictive model which uses historical usage data indicating idle times previously measured by charging trigger functions, CTFs, for the subscriber and the service characteristics; and

communicating the data traffic inactivity timer value to a CTF to configure monitoring of inactivity of the service using the communication session and to trigger a release operation related to the communication session when a data traffic inactivity timer using the data traffic inactivity timer value is determined to expire based on the monitored inactivity of the service.

2. The method of claim 1 , wherein the network node comprises a charging function, CHF, network node and wherein:

the communicating comprises sending from the CHF network node to the CTF in a charging data response message the data traffic inactivity timer value and configuration data that configures idle time measurements by the CTF and reporting by the CTF of the idle time measurements to the CHF network node.

3. The method of claim 1 , wherein the data traffic inactivity timer is a unit count inactivity timer, UCIT, for which expiration of the UCIT triggers the release operation that releases reservation of network resources for the communication session and terminates the communication session.

4. The method of claim 1 , wherein the data traffic inactivity timer is a quota holding timer, QHT, used for Diameter protocol communications for the communication session for which expiration of the QHT triggers the release operation that releases reservation of a charge quota that has been maintained against a subscriber account for the service using the communication session.

5. The method of claim 1 , wherein the network node comprises a charging function, CHF, network node and wherein the determining of the data traffic inactivity timer value comprises:

sending a request message containing the subscriber event data identifying the subscriber and the service characteristics to a network analytics function, NWDAF, network node containing the predictive model, wherein the request message requests the NWDAF network node determine an idle score based on processing the subscriber event data identifying the subscriber and the service characteristics through the predictive model; and

determining the data traffic inactivity timer value based on the idle score received from the NWDAF network node.

6. The method of claim 5 , wherein the determining of the data traffic inactivity timer value based on the idle score received from the NWDAF network node comprises:

using the idle score to obtain the data traffic inactivity timer value from a data structure which maps a set of idle scores to a corresponding set of data traffic inactivity timer values.

7. The method of claim 5 , wherein the determining of the data traffic inactivity timer value based on the idle score received from the NWDAF network node comprises:

processing the idle score through a defined historical relationship between previous idle scores received from the NWDAF network node and corresponding previously determined data traffic inactivity timer values, wherein the defined historical relationship is adapted over time based on how accurately the previously determined data traffic inactivity timer values determined from the previous idle scores predicted what the CTFs measured as idle time operational behavior for the identified subscriber and service characteristics.

8. The method of claim 1 , the network node comprises a charging function, CHF, network node containing the predictive model, and wherein:

the determining of the data traffic inactivity timer value comprises processing the subscriber event data identifying the subscriber and the service characteristics through the predictive model to generate the data traffic inactivity timer value.

9. The method of claim 8 , further comprising:

adapting the predictive model based on subscriber event data received over time in reports from CTFs containing measurements of idle times for identified subscribers and types of services.

10. The method of claim 9 , wherein:

the adapting of the predictive model is based on how accurately data traffic inactivity timer values generated for identified subscribers and types of services correspond to subsequently received reports from the CTFs of measurements of idle times for the identified subscriber and service characteristics.

11. A method by a charging trigger function, CTF, of a communications network, the method comprising:

sending a charging data request message to a charging function, CHF, network node;

receiving a charging data response message containing a data traffic inactivity timer value and configuration data;

generating idle time measurements of communication session idle times for a subscriber being provided a service through the communication session, wherein the idle time measurements are performed according to the configuration data to generate reports containing data characterizing the idle time measurements and identifying the subscriber and the service characteristics;

sending the reports to the CHF network node or to another network node; and

sending a release message to the CHF network node to trigger a release operation related to the communication session when a data traffic inactivity timer using the data traffic inactivity timer value is determined to expire based on the idle time measurements of the communication session.

12. The method of claim 11 , wherein the configuration data received in the charging data response message controls what idle threshold time needs to expire to trigger an idle counter to start a count of idle time, once the idle counter is started the configuration data controls what repeating time threshold period needs to expire during continuing idle to incrementally increase the count of idle time, and controls how many counts are collected before triggering sending of the report to the CHF network node.

13. A network node of a communications network, the network node comprising:

at least one processor; and

at least one memory coupled to the at least one processor and storing computer readable program code that when executed by the at least one processor causes the at least one processor to perform operations configured to:

determine a data traffic inactivity timer value based on subscriber event data, which identifies a subscriber and service characteristics using a communication session, being processed through a predictive model which uses historical usage data indicating idle times previously measured by charging trigger functions, CTFs, for the subscriber and the service characteristics; and

communicate the data traffic inactivity timer value to a CTF to configure monitoring of inactivity of the service using the communication session and to trigger a release operation related to the communication session when a data traffic inactivity timer using the data traffic inactivity timer value is determined to expire based on the monitored inactivity of the service.

14. The network node of claim 13 , wherein the network node comprises a charging function, CHF, network node and the communication of the data traffic inactivity timer value to a CTF comprises sending from the CHF network node to the CTF in a charging data response message the data traffic inactivity timer value and configuration data that configures idle time measurements by the CTF and reporting by the CTF of the idle time measurements to the CHF network node.

15. The network node of claim 13 , wherein the data traffic inactivity timer is a unit count inactivity timer, UCIT, for which expiration of the UCIT triggers a release operation that releases reservation of network resources for the communication session and terminates the communication session.

16. The network node of claim 13 , wherein the data traffic inactivity timer is a quota holding timer, QHT, used for Diameter protocol communications for the communication session for which expiration of the QHT triggers a release operation that releases reservation of a charge quota that has been maintained against a subscriber account for the service using the communication session.

17. The network node of claim 13 , wherein the network node comprises a charging function, CHF, network node and wherein the operations to determine the data traffic inactivity timer value are further configured to:

send a request message containing the subscriber event data identifying the subscriber and the service characteristics to a network analytics function, NWDAF, network node containing the predictive model, wherein the request message requests the NWDAF network node determine an idle score based on processing the subscriber event data identifying the subscriber and the service characteristics through the predictive model; and

determine the data traffic inactivity timer value based on the idle score received from the NWDAF network node.

18. The network node of claim 17 , wherein the operations to determine the data traffic inactivity timer value based on the idle score received from the NWDAF network node are further configured to:

use the idle score to obtain the data traffic inactivity timer value from a data structure which maps a set of idle scores to a corresponding set of data traffic inactivity timer values.

19. The network node of claim 17 , wherein the operations to determine the data traffic inactivity timer value based on the idle score received from the NWDAF network node are further configured to:

process the idle score through a defined historical relationship between previous idle scores received from the NWDAF network node and corresponding previously determined data traffic inactivity timer values, wherein the defined historical relationship is adapted over time based on how accurately the previously determined data traffic inactivity timer values determined from the previous idle scores predicted what the CTFs measured as idle time operational behavior for the identified subscriber and service characteristics.

20. The network node of claim 13 , the network node comprises a charging function, CHF, network node containing the predictive model, and wherein:

the determination of the data traffic inactivity timer value comprises processing the subscriber event data identifying the subscriber and the service characteristics through the predictive model to generate the data traffic inactivity timer value.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 22, 2022
From: KALRA, AMIT; TÖRNKVIST, ROBERT
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 062180/0127 →
Continuity (1)
Related Publication 20230262170A1 · Aug 17, 2023
References Cited (19)
US 10091008B2 · Sharma et al. · 2018 [cited by applicant]
US 20100144363A1 · De Rosa et al. · 2010 [cited by applicant]
US 20120124196A1 · Brisebois et al. · 2012 [cited by applicant]
US 20140211676A1 · Chhabra · 2014 [cited by applicant]
US 20150271342A1 · Gupta et al. · 2015 [cited by applicant]
US 20160135247A1 · Ozturk et al. · 2016 [cited by applicant]
US 20170180978A1 · Iwai et al. · 2017 [cited by applicant]
US 20190254104A1 · Gurumoorthy et al. · 2019 [cited by applicant]
US 20190387490A1 · Li et al. · 2019 [cited by applicant]
US 20200100088A1 · Kim · 2020 [cited by examiner]
US 20220007456A1 · Bao · 2022 [cited by examiner]
WO 2019219619A1 · 2019 [cited by applicant]
Extended European Search Report for European Patent Application No. 20943155.0 dated Jul. 17, 2023, 16 pages. [cited by applicant]
3GPP TS 23.288 V1.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16… [cited by applicant]
3GPP TS 32.291 V15.5.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G system, charging service; Stage 3 (Release 15… [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority for PCT International Application No. PCT/SE2020/050692 dated Apr. 1, 2021. [cited by applicant]
3GPP TR 23.700-91 V17.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enablers for network automation for the 5G System (5GS); Phase 2 (Release 17),” Dec. 20… [cited by applicant]
3GPP TS 32.255 V16.4.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G data connectivity domain charging; stage 2 (R… [cited by applicant]
3GPP TS 32.290 V16.3.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G system; Services, operations and procedures o… [cited by applicant]
Cited By (1)
US 12,652,225