IP Library › Granted Patent US 12,556,901
Granted Patent B2
US 12,556,901 · App. 18/555,995 · Granted Feb 17, 2026

Methods, network function nodes and computer readable media for event report management

Inventors: Yingjiao He (Shanghai, CN); Hong Zhang (Gothenburg, SE); Susana Fernandez Alonso (Madrid, ES); Fuencisla Garcia Azorero (Madrid, ES); Yunjie Lu (Shanghai, CN)
Assignee: Telefonaktiebolaget LM Ericsson (Publ)
H04W8/08
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,556,901
App. No.
18/555,995
Granted
Feb 17, 2026
Kind
B2
Abstract

Methods for event report management in a network comprising a set of NF nodes, and corresponding NF nodes. The A method is implemented at a first NF node for providing an event exposure service for a User Equipment, UE, to a second NF node which subscribes the event exposure service includes starting a report mute guard timer upon receiving a first presence status report for the UE from a third NF node. The method includes avoiding a transmission of an event report to the second NF node while the report mute timer is running and transmitting an event report corresponding to a latest presence status report received during the running of the report mute guard timer to the second NF node when the report mute guard timer expires. The present disclosure further provides corresponding NF nodes and computer readable medium.

Claims (53)

1 . A method implemented at a first Network Function, NF, node for providing an event exposure service for a User Equipment, UE, to a second NF node which subscribes the event exposure service, the method comprising:

starting a report mute guard timer upon receiving a first presence status report for the UE from a third NF node;

avoiding a transmission of an event report to the second NF node while the report mute timer is running; and

transmitting an event report corresponding to a latest presence status report received during the running of the report mute guard timer to the second NF node when the report mute guard timer expires, transmitting the event report corresponding to a latest presence status report received during the running of the report mute guard timer to the second NF node comprising:

transmitting an event report comprising a number of suppressed event reports, the number of suppressed event reports being equal to a number of presence status reports for the UE received during the running of the report mute guard timer.

2 . The method of claim 1 , wherein before the step of starting a report mute guard timer, the method further comprises:

receiving an indicator indicating a value of the report mute guard timer from the second NF node.

3 . The method of claim 1 , wherein before the step of starting a report mute guard timer, the method further comprises:

configuring the report mute guard timer at the first NF node locally.

4 . The method of claim 1 ,

wherein the step of starting a report mute guard timer upon receiving a first presence status report for the UE comprises:

transmitting an event report corresponding to the first presence status report to the second NF node upon receiving the first presence status report for the UE;

wherein the step of avoiding a transmission of an event report to the second NF node while the report mute timer is running comprises:

resetting the report mute guard timer upon receiving another presence status report for the event when the report mute guard timer is running, and

avoiding a transmission of an event report corresponding to the other presence status report to the second NF node; and

wherein the step of transmitting an event report corresponding to a latest presence status report received during the running of the report mute guard timer to the second NF node when the report mute guard timer expires comprises:

transmitting the event report corresponding to the latest presence status report received during the running of the report mute guard timer to the second NF node when the first presence status report and the latest presence status report indicate different presence states of the UE.

5 . The method of claim 4 , wherein the step of transmitting an event report corresponding to a latest presence status report received during the running of the report mute guard timer to the second NF node comprises:

transmitting an event report comprising an event report stable time, wherein the event report stable time is a length of time from starting of the report mute guard timer to expiration of the report mute guard timer.

6 . The method of claim 2 , wherein when more than one indicator indicating a different value of the report mute guard timer is received from more than one second NF node, the value of the report mute guard timer used for the event report is the smallest one of the values.

7 . The method of claim 1 , wherein when an indicator indicating a value of the report mute guard timer is received from the second NF node, and a report mute guard timer is locally configured at the first NF node, which timer is used for the event report is determined at least partially based on an operator policy if configured in the first NF node.

8 . The method of claim 3 , wherein the report mute guard timer locally configured at the first NF node is used when the first NF node receives an indication from the second NF node that the event report shall be performed when a presence state for the UE is stabilized.

9 . The method of claim 1 , wherein the presence status report indicates a presence state of the UE in a Presence Reporting Area, PRA, and is received when the presence state of the UE in a PRA changes, and the event report is a PRA report.

10 . The method of claim 9 , wherein the report mute guard timer is provided for:

each PRA;

all PRAS;

per UE or a group or UE; or

per Public Data Network, PDN.

11 . A method implemented at a first Network Function, NF, node for providing an event exposure service for a User Equipment, UE, to a second NF node which subscribes the event exposure service, the method comprising:

receiving from the second NF node an event filtering indicator indicating a presence state of the UE which triggers an event report to the second NF node, the event filtering indicator being an event filtering list listing more than one presence state of the UE which triggers an event report to the second NF node;

in response to receiving a presence status report of the UE from a third NF node, matching a presence state of the UE indicated by the presence status report with the presence state of the UE indicated by the event filtering indicator; and

transmitting the event report corresponding to the presence status report to the second NF when the present state of the UE indicated by the presence status report matches with the presence state of the UE indicated by the event filtering indicator.

12 . The method of claim 11 , wherein the presence status report indicates a presence state of the UE in a Presence Reporting Area, PRA, and the presence state of the UE comprises one or more of the following:

the UE is inside or enters the PRA;

the UE is outside or leaves the PRA;

it is unknown whether or not the UE is in the PRA; or

the PRA is inactive in the third NF node.

13 . A method at a second Network Function, NF, node for managing an event report for an event exposure service for a User Equipment, UE, from a first NF node which provides the event exposure service, the method comprising:

transmitting an indicator to the first NF node indicating that the second NF node supports a report mute feature; and

receiving from the first NF node an event report comprising a number of suppressed event reports, the number of suppressed event reports being equal to a number of event reports for the UE that otherwise would be transmitted from the first NF without the report mute feature, the event report further comprising an event report stable time, the event report stable time being a length of time from the time when the first NF node transmits a previous event report to the time when the first NF node transmits the current event report.

14 . The method of claim 13 , wherein the step of transmitting an indicator to the first NF node indicating that the second NF node supports a report mute feature comprises:

transmitting an indicator indicating a value of a report mute guard timer for the event report to the first NF node.

15 . The method of claim 13 , wherein the step of transmitting an indicator to the first NF node indicating that the second NF node supports a report mute feature comprises:

transmitting an indication that the event report shall be performed when a presence state for the UE is stabilized.

16 . The method of claim 14 , wherein the report mute guard timer is provided for:

each PRA;

all PRAs;

per UE or a group or UE; or

per Public Data Network, PDN.

17 . A method implemented at a second Network Function, NF, node for managing an event report for an event exposure service for a User Equipment, UE, from a first NF node which provides the event exposure service, the method comprising:

transmitting to the first NF node an event filtering indicator indicating a presence state of the UE which triggers the event report to the second NF node; and

receiving from the first NF node an event report comprising a number of suppressed event reports, the number of suppressed event reports being equal to a number of event reports for the UE that otherwise would be transmitted from the first NF without the report mute feature, the event report further comprising an event report stable time, the event report stable time being a length of time from the time when the first NF node transmits a previous event report to the time when the first NF node transmits the current event report.

18 . The method of claim 11 , further comprising receiving an indicator from the second NF node indicating a value of a report mute guard timer for the event report.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2023
From: HE, YINGJIAO; ZHANG, HONG; FERNANDEZ ALONSO, SUSANA; GARCIA AZORERO, FUENCISLA; LU, YUNJIE
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 065276/0495 →
Priority Claims (1)
WO PCT/CN2021/088535 · Apr 20, 2021 · international
Continuity (1)
Related Publication 20240292203A1 · Aug 29, 2024
References Cited (36)
US 8254929B2 · Funabiki · 2012 [cited by examiner]
US 11411755B2 · Gardella · 2022 [cited by examiner]
US 11595797B2 · Zhang · 2023 [cited by examiner]
US 11729661B2 · Iwai · 2023 [cited by examiner]
US 11963167B2 · Ahmed · 2024 [cited by examiner]
US 12028931B2 · Zhou · 2024 [cited by examiner]
US 20090119564A1 · Sagfors · 2009 [cited by examiner]
US 20100254321A1 · Kim · 2010 [cited by examiner]
US 20130053055A1 · Kumar · 2013 [cited by examiner]
US 20130159511A1 · Backholm · 2013 [cited by examiner]
US 20170012829A1 · Skaaksrud · 2017 [cited by examiner]
US 20190253873A1 · Shi · 2019 [cited by examiner]
US 20190253917A1 · Dao · 2019 [cited by examiner]
US 20200107182A1 · Chen · 2020 [cited by examiner]
US 20200229069A1 · Chun · 2020 [cited by examiner]
US 20210007166A1 · Liao · 2021 [cited by examiner]
US 20220209903A1 · Zhang · 2022 [cited by examiner]
CN 101199195A · 2008 [cited by examiner]
CN 104995867A · 2015 [cited by applicant]
CN 108012260A · 2018 [cited by applicant]
CN 111586583A · 2020 [cited by applicant]
EP 3627862A1 · 2020 [cited by applicant]
EP 3876637A1 · 2021 [cited by examiner]
KR 20200107182A · 2020 [cited by examiner]
WO WO2005076884A2 · 2005 [cited by examiner]
WO WO2014086431A1 · 2014 [cited by examiner]
International Search Report and Written Opinion dated Jun. 2, 2022 for International Application No. PCT/CN2022/086578 filed Apr. 13, 2022, consisting of 7-pages. [cited by applicant]
3GPP TS 29.512 V17.2.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 17); Mar. 2021, consisting of … [cited by applicant]
3GPP TS 32.291 V16.10.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G system, charging service; Stage 3 (Release 16… [cited by applicant]
3GPP TS 29.518 V17.1.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Access and mobility Management Services; Stage 3 (Release 17); Mar. 2021, consisting of 31… [cited by applicant]
3GPP TS 29.571 V17.1.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Common Data Types for Service Based Interfaces; Stage 3 (Release 17); Mar. 2021, consistin… [cited by applicant]
SA WG2 Meeting #125 S2-180274 (revision of S2-18); Change Request; Title: Clarification on the PRA support; Source to WG: Nokia, Nokia Shanghai Bell; Source to TSG: SA2; Work Item Code: 5GS_Ph1; Date and Location: Jan. … [cited by applicant]
3GPP TS 32.255 V17.1.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 (Re… [cited by applicant]
Extended European Search Report dated Sep. 12, 2024 for Application No. 22790931.4, consisting of 17 pages. [cited by applicant]
ETSI TS 123 501 V16.5.1; 5G; System architecture for the 5G System (5GS) (3GPP TS 23.501 version 16.5.1 Release 16); Sep. 2020, consisting of 443 pages. [cited by applicant]
SA WG2 Meeting # 125 S2-180274; Title: Clarification on the PRA support; Source to WG: Nokia, Nokia Shanghai Bell; Date And Location: Jan. 22-26, 2018, Gothenburg, Sweden, consisting of 11 pages. [cited by applicant]