IP Library › Granted Patent US 12,739,305
Granted Patent B2
US 12,739,305 · App. 18/550,543 · Granted Sep 15, 2026

Service execution handling

Inventors: Maria Cruz Bartolome Rodrigo (Madrid, ES); Aldo Bolle (Västra Frölunda, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04L67/51H04L67/1008H04L67/1012H04W4/20H04W28/08H04W28/084H04W28/0992
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,739,305
App. No.
18/550,543
Granted
Sep 15, 2026
Kind
B2
Abstract

There is provided a method for handling execution of a service in a network. The method is performed by a first network node. The first network node is a first network function (NF) node of a service consumer or a first service communication proxy (SCP) node that is configured to operate as an SCP between the first NF node and second NF nodes of a service producer for providing the service. The method is performed in response to an event that signals that the service is to be executed. The method comprises, if a first configuration criterion of the first NF node and/or a second configuration criterion of at least one of the second NF nodes is met, identifying ( 102 ) that network traffic for executing the service is to be distributed among the second NF nodes according to a capacity of one or more of the second NF nodes.

Claims (54)

1 . A method performed by a network node for handling execution of a service in a network that includes a first network function (NF) node of a consumer for the service and a plurality of second NF nodes of a producer for the service, the method comprising:

querying respective profiles associated with the plurality of second NF nodes for the following information:

a first indication that a respective second NF node is under testing and a predefined amount of network traffic required by the respective second NF node for the testing;

a network traffic capacity for the respective second NF node; and

an amount of network traffic currently handled by the respective second NF node; and

distributing network traffic for executing the service among the plurality of second NF nodes based on the queried information included in the respective profiles and further based on traffic distribution criteria, including the following:

distributing, to each second NF node whose profile includes the first indication, the predefined amount of network traffic required by the second NF node for the testing, after which a remaining network traffic to be distributed is determined; and

for remaining second NF nodes whose profiles do not include the first indication, the traffic distribution criteria include:

when all profiles for the remaining second NF nodes indicate the amount of network traffic currently handled, distributing the remaining network traffic among the remaining second NF nodes according to respective differences between network traffic capacities for the remaining second NF nodes and amounts of network traffic currently handled by the remaining second NF nodes.

2 . The method of claim 1 , wherein the traffic distribution criteria also include the following:

when none of the respective profiles include the first indication and at least one of the respective profiles does not indicate the amount of traffic currently handled, distributing the network traffic among the plurality of second NF nodes according to respective network traffic capacities of the plurality of second NF nodes; and

when none of the respective profiles include the first indication and all of the respective profiles indicate the amount of network traffic currently handled, distributing the network traffic among the plurality of second NF nodes according to respective differences between network traffic capacities for the plurality of second NF nodes and amounts of network traffic currently handled by the plurality of second NF nodes.

3 . The method of claim 1 , wherein the traffic distribution criteria also include the following for the remaining second NF nodes whose profiles do not include the first indication:

when one or more profiles associated with the remaining second NF nodes do not indicate the amount of network traffic currently handled, distributing the remaining network traffic among the remaining second NF nodes according to the respective network traffic capacities for the remaining second NF nodes, irrespective of the amounts of network traffic currently handled by the remaining second NF nodes.

4 . The method of claim 3 , wherein the remaining network traffic is distributed among the remaining second NF nodes irrespective of the amounts of network traffic currently handled by the remaining second NF nodes, except when the amount of network traffic currently handled by at least one of the remaining second NF nodes is at a maximum load capability.

5 . The method of claim 1 , wherein for at least one second NF node of the plurality of second NF nodes, the predefined amount of network traffic is a predefined percentage of the network traffic for executing the service.

6 . The method of claim 1 , wherein for at least one second NF node of the plurality of second NF nodes, the network traffic capacity is based on the following:

a total of network traffic capacities for all other second NF nodes of the plurality of second NF nodes, and the predefined amount of network traffic required by the at least one second NF node for testing.

7 . The method of claim 1 , further comprising identifying that the network traffic for executing the service is to be distributed among the plurality of second NF nodes based on the information queried from the respective profiles and according to traffic distribution criteria, in response to the following:

an event indicating that the service is to be executed, and

a traffic distribution configuration of the first NF node.

8 . The method of claim 7 , wherein the event is one of the following: reception of a service request for the service to be executed, or an event internal to the network node that requires the service to be executed.

9 . The method of claim 8 , wherein the traffic distribution configuration of the first NF node indicates that the first NF node is configured to distribute network traffic for executing the service according to one of the following:

respective network traffic capacities for the plurality of second NF nodes irrespective of amounts of network traffic currently handled by the plurality of second NF nodes;

the respective network traffic capacities for the plurality of second NF nodes when the amount of network traffic currently handled is unavailable in at least one of the respective profiles; or

irrespective of the amount of network traffic currently handled by the plurality of second NF nodes.

10 . The method of claim 1 , wherein the network node is the first NF node or a first service communication proxy (SCP) node configured to operate as an SCP between the first NF node and the plurality of second NF nodes.

11 . A network node configured to handle execution of a service in a network that includes a first network function (NF) node of a consumer for the service and a plurality of second NF nodes of a producer for the service, the network node comprising processing circuitry configured to:

query respective profiles associated with the plurality of second NF nodes for the following information:

a first indication that a respective second NF node is under testing and a predefined amount of network traffic required by the respective second NF node for the testing;

a network traffic capacity for the respective second NF node; and

an amount of network traffic currently handled by the respective second NF node; and

distribute network traffic for executing the service among the plurality of second NF nodes based on the queried information included in the respective profiles and further based on traffic distribution criteria including the following:

distribute, to each second NF node whose profile includes the first indication, the predefined amount of network traffic required by the second NF node for the testing, after which a remaining network traffic to be distributed is determined; and

for remaining second NF nodes whose profiles do not include the first indication, the traffic distribution criteria include:

when all profiles for the remaining second NF nodes indicate the amount of network traffic currently handled, distribute the remaining network traffic among the remaining second NF nodes according to respective differences between network traffic capacities for the remaining second NF nodes and amounts of network traffic currently handled by the remaining second NF nodes.

12 . The network node of claim 11 ,

wherein the traffic distribution criteria also include the following:

when none of the respective profiles include the first indication and at least one of the respective profiles does not indicate the amount of traffic currently handled, distribute the network traffic among the plurality of second NF nodes according to respective network traffic capacities of the plurality of second NF nodes; and

when none of the respective profiles include the first indication and all of the respective profiles indicate the amount of network traffic currently handled, distribute the network traffic among the plurality of second NF nodes according to respective differences between network traffic capacities for the plurality of second NF nodes and amounts of network traffic currently handled by the one or more plurality of second NF nodes.

13 . The network node of claim 11 , wherein the traffic distribution criteria also include the following for the remaining second NF nodes whose profiles do not include the first indication:

when one or more profiles associated with the remaining second NF nodes do not indicate the amount of network traffic currently handled, distribute the remaining network traffic among the remaining second NF nodes according to respective network traffic capacities for the remaining second NF nodes, irrespective of the amounts of network traffic currently handled by the remaining second NF nodes.

14 . The network node of claim 13 , wherein the remaining network traffic is distributed among the remaining second NF nodes irrespective of the amounts of network traffic currently handled by the remaining second NF nodes, except when an amount of network traffic currently handled by at least one of the remaining second NF nodes is at a maximum load capability.

15 . The network node of claim 11 , wherein for at least one second NF node of the plurality of second NF nodes, the predefined amount of network traffic is a predefined percentage of the network traffic for executing the service.

16 . The network node of claim 11 , wherein for at least one second NF node of the plurality of second NF nodes, the network traffic capacity is based on the following: a total of network traffic capacities for all other second NF nodes of the plurality of second NF nodes, and the predefined amount of network traffic required by the at least one second NF node for testing.

17 . The network node of claim 11 , wherein the processing circuitry is further configured to identify that the network traffic for executing the service is to be distributed among the plurality of second NF nodes based on the information queried from the respective profiles and according to traffic distribution criteria, in response to the following:

an event indicating that the service is to be executed, and

a traffic distribution configuration of the first NF node.

18 . The network node of claim 17 , wherein the eventis one of the following: reception of a service request for the service to be executed, or an event internal to the network node that requires the service to be executed.

19 . The network node of claim 18 , wherein the traffic distribution configuration of the first NF node indicates that the first NF node is configured to distribute network traffic for executing the service according to one of the following:

respective network traffic capacities for the plurality of second NF nodes irrespective of amounts of network traffic currently handled by the plurality of second NF nodes;

the respective network traffic capacities for the plurality of second NF nodes when the amount of network traffic currently handled is unavailable in at least one of the respective profiles; or

irrespective of the amount of network traffic currently handled by the one or more plurality of second NF nodes.

20 . The network node of claim 11 , wherein the network node is the first NF node or a first service communication proxy (SCP) node configured to operate as an SCP between the first NF node and the plurality of second NF nodes.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2023
From: RODRIGO, MARIA CRUZ BARTOLOME; BOLLE, ALDO
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 064904/0169 →
Priority Claims (2)
EP 21382316 · Apr 14, 2021 · regional
EP 21382317 · Apr 14, 2021 · regional
Continuity (1)
Related Publication 20240179210A1 · May 30, 2024
References Cited (41)
US 10778527B2 · Assali · 2020 [cited by examiner]
US 10791044B1 · Krishan · 2020 [cited by examiner]
US 10833938B1 · Rajput · 2020 [cited by examiner]
US 11301362B1 · John · 2022 [cited by examiner]
US 11570262B2 · Sapra · 2023 [cited by examiner]
US 20140160927A1 · Majumdar · 2014 [cited by examiner]
US 20150163131A1 · Bauer · 2015 [cited by examiner]
US 20160323145A1 · Anderson · 2016 [cited by examiner]
US 20190230012A1 · Azizullah et al. · 2019 [cited by applicant]
US 20200127916A1 · Krishan · 2020 [cited by examiner]
US 20200136960A1 · Jeuk · 2020 [cited by examiner]
US 20200177457A1 · Seenappa · 2020 [cited by examiner]
US 20200310950A1 · Mueller · 2020 [cited by examiner]
US 20200313996A1 · Krishan · 2020 [cited by examiner]
US 20200367045A1 · Jeong et al. · 2020 [cited by applicant]
US 20210067485A1 · Goel · 2021 [cited by applicant]
US 20210112443A1 · Krishan et al. · 2021 [cited by applicant]
US 20210120452A1 · Kotecha · 2021 [cited by examiner]
US 20210297896A1 · Landais · 2021 [cited by examiner]
US 20220104112A1 · Rajput et al. · 2022 [cited by applicant]
US 20220109972A1 · Jeong et al. · 2022 [cited by applicant]
US 20220124468A1 · Lu et al. · 2022 [cited by applicant]
US 20220131945A1 · Sapra · 2022 [cited by examiner]
US 20220132358A1 · Peng · 2022 [cited by examiner]
US 20220247779A1 · Rajput · 2022 [cited by examiner]
US 20220294775A1 · Singh · 2022 [cited by examiner]
US 20220330057A1 · Bratu · 2022 [cited by examiner]
CN 113508611A · 2021 [cited by applicant]
JP 2022103356A · 2022 [cited by applicant]
WO 2020202043A1 · 2020 [cited by applicant]
WO WO2021251948A1 · 2021 [cited by examiner]
“3GPP TS 29.303 V17.0.0”, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Domain Name System Procedures; Stage 3; (Release 17), Dec. 2020, pp. 1-81. [cited by applicant]
“CR Pack on Load and Overload Control of 5GC Service Based Interfaces”, 3GPP TSG-CT Meeting #87, CP-200025, Online, Mar. 16-18, 2020, 1 page. [cited by applicant]
“Default Notifications”, 3GPP TSG-CT WG4 Meeting #101e, E-Meeting, C4-205785, (was C4-205543), Nov. 3-13, 2020, pp. 1-26. [cited by applicant]
“Dynamic Load Control”, 3GPP TSG-CT WG4 Meeting #96e, E-Meeting, C4-201219, Revision of 016(316), 101, 401, 925, 1190, Feb. 17-28, 2020, pp. 1-8. [cited by applicant]
“3GPP TS 29.510 V16.5.0”, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 16), Sep. 2020, pp. 1-195. [cited by applicant]
“3GPP TS 29.500 V17.1.0”, 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17), Dec. 2020, pp… [cited by applicant]
“3GPP TS 23.501 V16.4.0”, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16), Mar. 2020, pp. 1-430. [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.4.0, Dec. 2021, pp. 1-284. [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 Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17)”, 3GPP TS 23.501 V17.3.0, Dec. 2021, pp. 1-559. [cited by applicant]