IP Library › Granted Patent US 12,604,216
Granted Patent B2
US 12,604,216 · App. 18/300,114 · Granted Apr 14, 2026

Allocating resource entities for trace

Inventors: Kiran Sathyanarayanamurthy (Tumakuru, IN); Anatoly Andrianov (Schaumburg, IL)
Assignee: Nokia Solutions and Networks Oy
H04W24/04H04W4/20H04W28/08H04W72/52
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,604,216
App. No.
18/300,114
Granted
Apr 14, 2026
Kind
B2
Abstract

There is provided receiving, at a network entity, a message from at least one peer network entity, determining, if the received message comprises information indicating a trace, at least one trace capable resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities, allocating the received message or the subsequent messages of a session of the received message to the determined at least one trace capable resource entity.

Claims (35)

1 . A method comprising:

receiving, at a network entity, a message from at least one peer network entity;

determining, at the network entity, if the received message comprises information indicating a trace, at least one trace capable resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities;

allocating, at the network entity, the received message or the subsequent messages of a session of the received message to the determined at least one trace capable resource entity.

2 . The method according to claim 1 , comprising:

determining, at the network entity, if the received message does not comprise information indicating a trace, at least one trace disabled resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities;

allocating, at the network entity, the received message or the subsequent messages of a session of the received message to the determined at least one trace disabled resource entity.

3 . The method according to claim 1 , comprising:

determining, at the network entity, at least one tracing load;

scaling, at the network entity, if the tracing load level exceeds a load threshold, the set of resource entities based on the tracing load.

4 . The method according to claim 1 , wherein the trace capable resource entities are dedicated for traces and the trace disabled resource entities are dedicated for session processing.

5 . The method according to claim 1 , comprising:

receiving, at the network entity, from an operations, administration and management, OAM, system one or more identity values and/or uniform resource indicators to one or more identity values; and

determining, at the network entity, if the received message comprises information indicating a trace, based on the received one or more identity values and/or uniform resource indicators to one or more identity values.

6 . The method according to claim 1 , wherein the information indicating a trace is a trace indication information element, IE, of: a Diameter Base Protocol, a header of a HTTP message, a payload of a HTTP message or an ASN.1 message.

7 . A network entity comprising one or more processors, and memory storing instructions that, when executed by the one or more processors, the network entity is caused to:

receive, at the network entity, a message from at least one peer network entity;

determine, at the network entity, if the received message comprises information indicating a trace, at least one trace capable resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities;

allocate, at the network entity, the received message or the subsequent messages of a session of the received message to the determined at least one trace capable resource entity.

8 . The network entity according to claim 7 , comprising:

determine, at the network entity, if the received message does not comprise information indicating a trace, at least one trace disabled resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities;

allocate, at the network entity, the received message or the subsequent messages of a session of the received message to the determined at least one trace disabled resource entity.

9 . The network entity according to claim 7 , comprising:

determine, at the network entity, at least one tracing load;

scale, at the network entity, if the tracing load level exceeds a load threshold, the set of resource entities based on the tracing load.

10 . The network entity according to claim 7 , comprising:

wherein the trace capable resource entities are dedicated for traces and the trace disabled resource entities are dedicated for session processing.

11 . The network entity according to claim 7 , comprising:

receiving at the network entity, from an operations, administration and management, OAM, system one or more identity values and/or uniform resource indicators to one or more identity values; and

determining, at the network entity, if the received message comprises information indicating a trace, based on the received one or more identity values and/or uniform resource indicators to one or more identity values.

12 . The network entity according to claim 7 , wherein the information indicating a trace is a trace indication information element, IE, of: a Diameter Base Protocol, a header of a HTTP message, a payload of a HTTP message or an ASN.1 message.

13 . A non-transitory computer readable medium comprising program instructions for causing a network entity to perform at least the following:

receive, at the network entity, a message from at least one peer network entity;

determine, at the network entity, if the received message comprises information indicating a trace, at least one trace capable resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities;

allocate, at the network entity, the received message or the subsequent messages of a session of the received message to the determined at least one trace capable resource entity.

Assignments (5)
CORRECTIVE ASSIGNMENT TO CORRECT THE INCORRECT ASSIGNMENT DOCUMENT PREVIOUSLY RECORDED ON REEL 064460 FRAME 0432. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 19, 2023
From: NOKIA SOLUTIONS AND NETWORKS INDIA PRIVATE LIMITED
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 065239/0874 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: ANDRIANOV, ANATOLY
To: NOKIA OF AMERICA CORPORATION
Reel/Frame 064460/0396 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: SATHYANARAYANAMURTHY, KIRAN
To: NOKIA SOLUTIONS AND NETWORKS INDIA PRIVATE LIMITED
Reel/Frame 064460/0415 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: NOKIA OF AMERICA CORPORATION
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 064460/0418 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: NOKIA SOLUTIONS AND NETWORKS INDIA PRIVATE LIMITED
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 064460/0432 →
Priority Claims (1)
FI 20225345 · Apr 25, 2022 · national
Continuity (1)
Related Publication 20230345272A1 · Oct 26, 2023
References Cited (22)
US 9119080B2 · Jactat et al. · 2015 [cited by applicant]
US 10567245B1 · Patil et al. · 2020 [cited by applicant]
US 20050276386A1 · Ethier et al. · 2005 [cited by applicant]
US 20120059869A1 · Seo · 2012 [cited by examiner]
US 20120089876A1 · Racz et al. · 2012 [cited by applicant]
US 20130114446A1 · Liu · 2013 [cited by examiner]
US 20130275606A1 · Lyer · 2013 [cited by examiner]
US 20170346675A1 · Prokofiev · 2017 [cited by applicant]
US 20210144082A1 · Bisht et al. · 2021 [cited by applicant]
US 20230370344A1 · Lee · 2023 [cited by examiner]
CN 103747468A · 2014 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements (Release 17)”, 3GPP TS 32.421… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace data definition and management (Release 17)”, 3GPP TS 3… [cited by applicant]
Fajardo et al., “Diameter Base Protocol”, RFC 6733, Internet Engineering Task Force (IETF), Oct. 2012, pp. 1-152. [cited by applicant]
“New SID on further Enhancements of Management of Trace/MDT”, 3GPP TSG-SA5 Meeting #141-e, S5-221514, Agenda: 6.2, Nokia, Jan. 17 -26, 2022, 3 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17)”, 3GPP TS 23.502, V17.3.0, Dec. 2021, pp. 1-727. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17)”, 3GPP TS 29.510, V17.3.0, Sep. 2021, pp. 1-271. [cited by applicant]
Office action received for corresponding Finnish U.S. Appl. No. 20/225,345, dated Oct. 27, 2022, 10 pages. [cited by applicant]
“Rel-17 draftCR 32.422 Add metric identifier for trace metrics”, 3GPP TSG-SA5 Meeting #142-e, S5-222635, Nokia, Apr. 4-12, 2022, 6 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace control and configuration management (Release 17)”, 3GP… [cited by applicant]
Action received for corresponding Finnish Patent Application No. 20225345, dated Mar. 30, 2023, 11 pages. [cited by applicant]
Extended European Search Report received for corresponding European Patent Application No. 23168847.4, dated Sep. 15, 2023, 8 pages. [cited by applicant]