IP Library › Granted Patent US 12,592,892
Granted Patent B2
US 12,592,892 · App. 17/960,800 · Granted Mar 31, 2026

Methods, systems, and computer readable media for adjusting and using priorities of service/notification request messages at network functions with multiple slice support

Inventor: Rajiv Krishan (Cary, NC)
Assignee: ORACLE INTERNATIONAL CORPORATION
H04L47/2458H04L47/11
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,592,892
App. No.
17/960,800
Granted
Mar 31, 2026
Kind
B2
Abstract

A method for adjusting priorities of messages at a network function (NF) with multiple network slice support includes, at a first NF that supports multiple network slices, storing a database of rules specifying network-slice-based priority adjustment parameters. The method further includes receiving a message from a second NF. The method further includes determining that a congestion or overload condition exists, and, in response. determining network slice information associated with the message, determining, using the network slice information and the database of network-slice-based priority adjustment parameters, a network-slice-adjusted priority value for the message, and discarding or processing the message based on the network-slice-adjusted priority value for the message.

Claims (50)

1 . A method for adjusting and using priorities of messages at a network function (NF) with multiple network slice support, the method comprising:

at a first NF that supports multiple network slices:

storing a database of rules specifying network-slice-based priority adjustment parameters;

receiving a message from a second NF;

determining that a congestion or overload condition exists, and, in response:

determining network slice information associated with the message;

determining, using the network slice information and the database of network-slice-based priority adjustment rules, a network-slice-adjusted priority value for the message, wherein determining the network-slice-adjusted priority includes calculating an adjusted priority value using an equation that includes as a parameter a 3gpp-Sbi-Message-Priority value carried in the message or using a default priority value specified in an interface and network slice-based priority rule in the database when the 3gpp-Sbi-Message-Priority value is not present in the message, wherein the equation includes as parameters minimum and maximum network-slice-adjusted priority values configured for a network slice associated with the message, and wherein the equation comprises

A =floor(( R/ 31*(Mx−Mn)))+Mn,

where A is the network-slice-adjusted priority value, R is the 3gpp-Sbi-Message-Priority value in the message, Mx is the maximum network-slice-adjusted priority value defined for the network slice, and Mn is the minimum network-slice-adjusted priority value defined for the network slice; and

discarding or processing the message based on the network-slice-adjusted priority for the message.

2 . The method of claim 1 wherein storing the database of network-slice-based message priority adjustment rules includes storing, on a per-interface basis, rules that specify ranges of network-slice-adjusted priority values for the network slices.

3 . The method of claim 2 wherein storing the rules on a per-interface basis includes storing a first rule specifying a first range of network-slice-adjusted priority values for a first network slice and interface and storing a second rule specifying a second range of network-slice adjusted priority values for a second network slice and the interface, where the first range of network-slice-adjusted priority values is different from the second range of network-slice-adjusted priority values.

4 . The method of claim 1 wherein receiving the message includes receiving an initial service request and further comprising:

reading a network slice identifier from the initial service request;

generating a response to the initial service request;

inserting the network slice identifier or a value that is mapped to the network slice identifier in a resource or association identifier;

including the resource or association identifier in a location header of the response; and

sending the response to the second NF.

5 . The method of claim 1 wherein receiving the message includes receiving a service request associated with an existing resource and wherein determining a network slice associated with the message includes reading a network slice identifier from a resource or association identifier of the service request.

6 . The method of claim 1 wherein receiving the message includes receiving a notification request and wherein determining a network slice associated with the message includes reading a network slice identifier from a notification uniform resource locator of the notification request.

7 . The method of claim 1 wherein processing or discarding the message based on the network-slice-adjusted priority value includes determining that the network-slice-adjusted priority value is greater than a threshold, and, in response to determining that the network-slice-adjusted priority value is greater than the threshold, discarding the message.

8 . A system for adjusting and using priorities of messages at a network function (NF) with multiple network slice support, the system comprising:

a first NF that supports multiple network slices, the first NF including at least one processor and a memory;

a network slice priority adjustment rules database embodied in the memory for storing rules specifying network-slice-based priority adjustment parameters; and

a network-slice-adjusted priority determiner/message throttler implemented by the at least one processor for receiving a message from a second NF, determining that a congestion or overload condition exists, and, in response:

determining network slice information associated with the message;

determining, using the network slice information and the network slice priority adjustment rules database, a network-slice-adjusted priority value for the message, wherein the network-slice-adjusted priority determiner/message throttler is configured determine the network-slice-adjusted priority value by calculating the network-slice-adjusted priority value using an equation that includes as a parameter a 3gpp-Sbi-Message-Priority value carried in the message or using a default priority value specified in an interface and network slice based priority rule in the database when the 3gpp-Sbi-Message-Priority value is not present in the message, wherein the equation includes as parameters minimum and maximum network-slice-adjusted priority values configured for a network slice associated with the message, and wherein the equation comprises

A =floor(( R/ 31*(Mx−Mn)))+Mn,

where A is the network-slice-adjusted priority value, R is the 3gpp-Sbi-Message-Priority value in the message, Mx is the maximum network-slice-adjusted priority value defined for the network slice, and Mn is the minimum network-slice-adjusted priority value defined for the network slice; and

discarding or processing the message based on the network-slice-adjusted priority value for the message.

9 . The system of claim 8 wherein the network slice priority adjustment rules database stores, on a per-interface basis, rules that specify ranges of network-slice-adjusted priority values for the network slices, wherein storing the rules on a per-interface basis includes storing a first rule specifying a first range of network-slice-adjusted priority values for a first network slice and interface and storing a second rule specifying a second range of network-slice-adjusted priority values for a second network slice and the interface, where the first range of network-slice-adjusted priority values is different from the second range of network-slice-adjusted priority values.

10 . The system of claim 8 wherein the message includes an initial service request and priority wherein the network-slice-adjusted determiner/message throttler is configured to:

read a network slice identifier from the initial service request;

generate a response to the initial service request;

insert the network slice identifier or a value that is mapped to the network slice identifier in a resource or association identifier;

include the resource or association identifier in a location header of the response; and

send the response to the second NF.

11 . The system of claim 8 wherein the message includes a service request associated with an existing resource and wherein the network-slice-adjusted priority determiner/message throttler is configured to determine a network slice associated with the message by reading a network slice identifier from a resource or association identifier of the service request.

12 . The system of claim 8 wherein the message includes a notification request and wherein the network-slice-adjusted priority determiner/message throttler is configured to determine a network slice associated with the message by reading a network slice identifier from a notification uniform resource locator of the notification request.

13 . The system of claim 8 wherein network-slice-adjusted priority determiner/message throttler is configured to discard the message in response to determining that the network-slice-adjusted priority value is greater than a threshold.

14 . A non-transitory computer readable medium having stored thereon executable instructions that when executed by a processor of a computer control the computer to perform steps comprising:

at a first network function (NF) that supports multiple network slices:

storing a database of rules specifying network-slice-based priority adjustment parameters for network slices;

receiving a message from a second NF;

determining that a congestion or overload condition exists, and, in response:

determining network slice information associated with the message;

determining, using the network slice information and the database of network-slice-based priority adjustment parameters, a network-slice-adjusted priority for the message, wherein determining the network-slice-adjusted priority includes calculating an adjusted priority value using an equation that includes as a parameter a 3gpp-Sbi-Message-Priority value carried in the message or using a default priority value specified in an interface and network slice-based priority rule in the database when the 3gpp-Sbi-Message-Priority value is not present in the message, wherein the equation includes as parameters minimum and maximum network-slice-adjusted priority values configured for a network slice associated with the message, and wherein the equation comprises

A =floor(( R/ 31*(Mx−Mn)))+Mn,

where A is the network-slice-adjusted priority value, R is the 3gpp-Sbi-Message-Priority value in the message, Mx is the maximum network-slice-adjusted priority value defined for the network slice, and Mn is the minimum network-slice-adjusted priority value defined for the network slice; and

discarding or processing the message based on the network-slice-adjusted priority for the message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2022
From: KRISHAN, RAJIV
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 061364/0429 →
Continuity (1)
Related Publication 20240121199A1 · Apr 11, 2024
References Cited (55)
US 10609530B1 · Patil et al. · 2020 [cited by applicant]
US 10616802B2 · Krishan et al. · 2020 [cited by applicant]
US 10833938B1 · Rajput · 2020 [cited by examiner]
US 11622293B2 · Gupta et al. · 2023 [cited by applicant]
US 12177720B2 · Krishan · 2024 [cited by applicant]
US 20120013748A1 · Stanwood · 2012 [cited by examiner]
US 20160007170A1 · Vaidya et al. · 2016 [cited by applicant]
US 20180234291A1 · Mathison et al. · 2018 [cited by applicant]
US 20180324671A1 · Palnati et al. · 2018 [cited by applicant]
US 20190069235A1 · Patil et al. · 2019 [cited by applicant]
US 20200186411A1 · Ravichandran · 2020 [cited by examiner]
US 20210067480A1 · Goel · 2021 [cited by examiner]
US 20210385283A1 · Talebi Fard et al. · 2021 [cited by applicant]
US 20210410059A1 · Talebi Fard et al. · 2021 [cited by applicant]
US 20220094740A1 · Saride · 2022 [cited by applicant]
US 20220330085A1 · Li · 2022 [cited by examiner]
US 20220400401A1 · Gupta et al. · 2022 [cited by applicant]
US 20230146433A1 · Sharma et al. · 2023 [cited by applicant]
US 20230284081A1 · Krishan · 2023 [cited by examiner]
US 20240137290A1 · Alvarez Dominguez · 2024 [cited by examiner]
EP 3496447B1 · 2024 [cited by applicant]
EP 4356588A1 · 2024 [cited by applicant]
JP 2020536434A · 2020 [cited by applicant]
JP 7674530B · 2025 [cited by applicant]
KR 20220005936A · 2022 [cited by applicant]
WO WO2017143047A1 · 2017 [cited by applicant]
WO WO2018141945A1 · 2018 [cited by applicant]
WO WO20200109853A1 · 2020 [cited by applicant]
WO WO2022265853A1 · 2022 [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/685,159, filed Aug. 15, 2024. [cited by applicant]
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/348,389 (Nov. 18, 2022). [cited by applicant]
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2022/031572 (Sep. 8, 2022). [cited by applicant]
“Ultra Cloud Core 5G Session Management Function, Release 2021.01—Configuration and Administration Guide,” Cisco, pp. 1-13 (May 13, 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16),” 3GPP TS 29.500, V16.7.0), pp. 1-91, (… [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.0.0, pp. 1-489 (Mar. 2021). [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.0.0, pp. 1-646 (Mar. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Network Slice Selection Services; Stage 3 (Release 17),” 3GPP TS 29.531, V17.0.0, pp. 1-77 (Mar. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for Next Generation Network; (Releas… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and Orchestration; Provisioning; (Release 16),” 3GPP TS 28.531, V16.9.0, pp. 1-73 (Mar. 2021). [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, pp. 1-284 (Dec. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” 3GPP TS 29.500, V17.4.0, pp. 1-109 (S… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16),” 3GPP TS 23… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Exposure Function Northbound APIs; Stage 3 (Release 16),” 3GPP TS 29.522, V16.9.0, pp. 1-185 (Sep. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 16),” 3GPP TS 29.122, V16.11.0, pp. 1-408 (Sep. 2021). [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.6.0, pp. 1-306 (Jun. 2022). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System Session Management Policy Control Service; Stage 3; (Release 17),” 3GPP TS 29.512 V17.7.0, pp. 1-255 (Jun. 2022). [cited by applicant]
Commonly-assigned, Co-pending U.S. Appl. No. 17/348,389 for “Methods, Systems, and Computer Readable Media for Establishing Message Priority in Network Slices Based on Quality of SE,” (Unpublished, filed Jun. 16, 2021). [cited by applicant]
Commonly-assigned, Co-pending U.S. Appl. No. 17/685,159 for “Methods, Systems, and Computer Readable Media for Notification Delivery,” (Unpublished, filed Mar. 2, 2022). [cited by applicant]
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/121,203, filed Nov. 18, 2019. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 15),” 3GPP TS 23… [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/685,159, filed Apr. 24, 2024. [cited by applicant]
Office Action for Japanese Patent Application Serial No. 2023577461 (Dec. 24, 2024). [cited by applicant]
Decision to Grant for Japanese Patent Application No. 2023577461 (Apr. 1, 2025). [cited by applicant]
First Examination Report for Indian Patent Application Serial No. 202347076518 (Sep. 16, 2025). [cited by applicant]
Communication pursuant to Article 94(3) for European Application No. 22738779.2 (Oct. 7, 2025). [cited by applicant]