# US 12,604,216 B2 · Allocating resource entities for trace > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,604,216 B2 - Document ID: US12604216B2 - Status: Granted - Kind: B2 - Application number: 18/300,114 - Filed: 2023-04-13 - Published: 2023-10-26 - Granted: 2026-04-14 - Earliest claimed: 2022-04-25 - Assignees: Nokia Solutions and Networks Oy - Applicants: Nokia Solutions and Networks Oy - Inventors: Kiran Sathyanarayanamurthy; Anatoly Andrianov - Web page: https://patentgrep.com/patent/US12604216B2 ## CPC - H04L 41/14: Network analysis or design - H04W 24/04: Arrangements for maintaining operational condition - H04L 43/02: Capturing of monitoring data - H04W 4/20: Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel - H04W 28/08: Load balancing or load distribution (transferring a connection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12) - H04W 72/52: based on load - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 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. ### Claim 8 (depends on 7) 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. ### Claim 9 (depends on 7) 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. ### Claim 10 (depends on 7) 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. ### Claim 11 (depends on 7) 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. ### Claim 12 (depends on 7) 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. ### Claim 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.