IP Library › Granted Patent US 12,192,878
Granted Patent B2
US 12,192,878 · App. 17/488,793 · Granted Jan 7, 2025

Methods, systems, and computer readable media for identifying alternate delivery endpoints for mobile originated data and monitoring reports in a communications network

Inventor: Rajiv Krishan (Bangalore, IN)
Assignee: ORACLE INTERNATIONAL CORPORATION
H04W40/34H04W40/02
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,192,878
App. No.
17/488,793
Granted
Jan 7, 2025
Kind
B2
Abstract

A method for identifying alternate delivery endpoints for mobile originated data and monitoring reports in a communications network includes establishing, by a network exposure function (NEF) in a communications network, priority rules in a priority configuration database that define routing priority indicators corresponding to a plurality of applications functions (AFs) and receiving a service request or notification request message directed to one of the plurality of AFs from a consumer network function (NF) in the communications network. The NEF accesses a context database to validate context information associated with a destination AF belonging to the plurality of AFs. If the destination AF is unavailable or is not in proximity to the NEF, an event notification request message associated with the service request or notification request message is directed to a prioritized AF specified in the priority configuration database, wherein the prioritized AF is a peer of the destination AF.

Claims (35)

1. A method comprising:

establishing, by a network exposure function (NEF) in a communications network, priority rules in a priority configuration database that define routing priority indicators corresponding to a plurality of applications functions (AFs), wherein the routing priority indicators include a priority order of the plurality of AFs, specific to an identity of the NEF, that designate an order in which the NEF attempts to utilize the plurality of AFs for establishing a session;

receiving, by the NEF, a service request or notification request message directed to one of the plurality of AFs from a network function (NF) in the communications network;

accessing, by the NEF, a context database to validate context information associated with a destination AF belonging to the plurality of AFs; and

in response to determining that the destination AF is unavailable or is not in proximity to the NEF, directing, by the NEF, an event notification request message associated with the service request or notification request message to a prioritized AF specified in the priority configuration database, wherein the prioritized AF is a peer of the destination AF.

2. The method of claim 1 wherein the NF request message received from the NF is a mobile originated (MO) deliver request message received from a session management function (SMF) in the communications network.

3. The method of claim 1 wherein the service request or notification request message received from the NF is a monitoring report message received from a Access and Mobility Management Function (AMF) or Unified Data Management (UDM) in the communications network.

4. The method of claim 1 wherein the notification request message is directed to the prioritized AF if an entry identifying the prioritized AF in the priority configuration database further includes a parameter indicating an override condition.

5. The method of claim 1 wherein the priority configuration database is auto-replicated among a plurality of NEFs in a NF set or NF service set related to the NEF.

6. The method of claim 1 comprising providing, by the NEF, priority binding information associated with the priority rules via request messages directed to a plurality of consumer NFs in the communications network.

7. The method of claim 1 wherein entries of the priority configuration database maps each of a plurality of NEF instances to a plurality of application functions, wherein each application function is identified by a context identifier and a priority identifier.

8. A system comprising:

at least one processor;

a memory; and

a network exposure function (NEF) in a communications network that is implemented using the at least one processor and the memory, the NEF configured for:

establishing priority rules in a priority configuration database that define routing priority indicators corresponding to a plurality of applications functions (AFs), wherein the routing priority indicators include a priority order of the plurality of AFs, specific to an identity of the NEF, that designate an order in which the NEF attempts to utilize the plurality of AFs for establishing a session;

receiving a service request or notification request message directed to one of the plurality of AFs from a consumer network function (NF) in the communications network;

accessing a context database to validate context information associated with a destination AF belonging to the plurality of AFs; and

in response to determining that the destination AF is unavailable or is not in proximity to the NEF, directing, by the NEF, an event notification request message associated with the service request or notification request message to a prioritized AF specified in the priority configuration database, wherein the prioritized AF is a peer of the destination AF.

9. The system of claim 8 wherein the NF request message received from the NF is a mobile originated (MO) deliver request message received from a session management function (SMF) in the communications network.

10. The system of claim 8 wherein the Service request or notification request message received from the NF is a monitoring report request message received from a Access and Mobility Management Function (AMF) or Unified Data Management (UDM) in the communications network.

11. The system of claim 8 wherein the notification request message is directed to the prioritized AF if an entry identifying the prioritized AF in the priority configuration database further includes a parameter indicating an override condition.

12. The system of claim 8 wherein the priority configuration database is auto-replicated among a plurality of NEFs in a NF set or NF service set related to the NEF.

13. The system of claim 8 wherein the NEF is further configured for providing priority binding information associated with the priority rules via request messages directed to a plurality of consumer NFs in the communications network.

14. The system of claim 8 wherein entries of the priority configuration database maps each of a plurality of NEF instances to a plurality of application functions, wherein each application function is identified by a context identifier and a priority identifier.

15. A non-transitory computer readable medium having stored thereon executable instructions that when executed by at least one processor of a computer cause the computer to perform steps comprising:

establishing, by a network exposure function (NEF) in a communications network, priority rules in a priority configuration database that define routing priority indicators corresponding to a plurality of applications functions (AFs), wherein the routing priority indicators include a priority order of the plurality of AFs, specific to an identity of the NEF, that designate an order in which the NEF attempts to utilize the plurality of AFs for establishing a session;

receiving, by the NEF, a service request or notification request message directed to one of the plurality of AFs from a consumer network function (NF) in the communications network;

accessing, by the NEF, a context database to validate context information associated with a destination AF belonging to the plurality of AFs; and

in response to determining that the destination AF is unavailable or is not in proximity to the NEF, directing, by the NEF, an event notification request message associated with the service request or notification request message to a prioritized AF specified in the priority configuration database, wherein the prioritized AF is a peer of the destination AF.

16. The non-transitory computer readable medium of claim 15 wherein the NF request message received from the NF is a mobile originated (MO) deliver request message received from a session management function (SMF) in the communications network.

17. The non-transitory computer readable medium of claim 15 wherein the service request or notification request message received from the NF is a monitoring report request message received from a Access and Mobility Management Function (AMF) or Unified Data Management (UDM) in the communications network.

18. The non-transitory computer readable medium of claim 15 wherein the notification request message is directed to the prioritized AF if an entry identifying the prioritized AF in the priority configuration database further includes a parameter indicating an override condition.

19. The non-transitory computer readable medium of claim 15 wherein the priority configuration database is auto-replicated among a plurality of NEFs in a NF set or NF service set related to the NEF.

20. The non-transitory computer readable medium of claim 15 comprising providing, by the NEF, priority binding information associated with the priority rules via request messages directed to a plurality of consumer NFs in the communications network.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2021
From: KRISHAN, RAJIV
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 057654/0720 →
Continuity (1)
Related Publication 20230102122A1 · Mar 30, 2023
References Cited (50)
US 11012058B2 · Dubey et al. · 2021 [cited by applicant]
US 11265694B2 · Farooq · 2022 [cited by applicant]
US 11611626B1 · Srivastava et al. · 2023 [cited by applicant]
US 11825370B2 · Jayaramchar et al. · 2023 [cited by applicant]
US 20160164680A1 · Liao · 2016 [cited by examiner]
US 20170303259A1 · Lee et al. · 2017 [cited by applicant]
US 20190124572A1 · Park et al. · 2019 [cited by applicant]
US 20190223250A1 · Dao · 2019 [cited by examiner]
US 20200136715A1 · Venugopal et al. · 2020 [cited by applicant]
US 20200314615A1 · Patil · 2020 [cited by examiner]
US 20200396132A1 · Wang et al. · 2020 [cited by applicant]
US 20210058833A1 · Basu Mallick et al. · 2021 [cited by applicant]
US 20210105196A1 · Dao · 2021 [cited by examiner]
US 20210111985A1 · Mahalank et al. · 2021 [cited by applicant]
US 20210211970A1 · Lee · 2021 [cited by examiner]
US 20220053372A1 · Shekhar · 2022 [cited by examiner]
US 20220141662A1 · Liao · 2022 [cited by examiner]
US 20230007536A1 · Sharma · 2023 [cited by applicant]
US 20230032054A1 · Jayaramachar et al. · 2023 [cited by applicant]
US 20230232322A1 · Singh et al. · 2023 [cited by applicant]
US 20230385161A1 · Lu · 2023 [cited by examiner]
WO WO2020202043A1 · 2020 [cited by applicant]
WO WO2022251324A1 · 2022 [cited by applicant]
US 11,483,406 B1, 10/2022, Srivastava et al. (withdrawn) [cited by applicant]
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/386,649, (filed Jul. 18, 2023). [cited by applicant]
“5G; 5G System; Network Function Repository Services; Stage 3 (3GPP TS 29.510 V16.6.0 Release 16)” ETSI TS 129 510 V16.6.0, pp. 1-227 (Jan. 2021). [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/386,649, (filed May 23, 2023). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Exposure (NE) function services for Non-IP Data Delivery (NIDD); Stage 3 (Release 17),” 3GPP TS 29.541, V… [cited by applicant]
Commonly-Assigned, co-pending U.S. Appl. No. 17/386,649 for “Methods, Systems, and Computer Readable Media for Providing for Network Function (NF) Fallback to Recovered NF Repository Function (NRF)” (Unpublished, filed … [cited by applicant]
Commonly-Assigned, co-pending U.S. Appl. No. 17/334,268 for “Methods, Systems, and Computer Readable Media for Distributing Network Function (NF) High Availability (HA) Topology Information in a Core Network” (Unpublish… [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.1.0, pp. 1-243 (Mar. 2021). [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 (Mar. 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.2.0, pp. 1-100 (… [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]
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/334,268, (filed Nov. 9, 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/030874 (Sep. 1, 2022). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enablers for network automation for the 5G System (5GS); Phase 2 (Release 17),” 3GPP TR 23.700-91, V17.0.0, pp. 1-… [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/334,268, (filed Jun. 6, 2022). [cited by applicant]
Applicant-Initiated Interview Summary for U.S. Appl. No. 17/334,268, (filed May 5, 2022). [cited by applicant]
“5G; System architecture for the 5G System (5GS) (3GPP TS 23.501 version 16.6.0 Release 16),” ETSI TS 123 501, V16.6.0, pp. 1-449 (Oct. 2020). [cited by applicant]
“5G; 5G System; Network function repository services; Stage 3 (3GPP TS 29.510 version 16.4.0 Release 16),” ETSI TS 129 510, V16.4.0, pp. 1-208 (Jul. 2020). [cited by applicant]
VMWare, “Configure Security VNF with HA”, pp. 1-4 (Sep. 21, 2020). [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/334,268, (filed Mar. 28, 2022). [cited by applicant]
Commonly-Assigned, co-pending U.S. Appl. No. 17/578,300 for “Methods, Systems, and Computer Readable Media for Prioritizing Among Alternate Network Function (NF) Instances” (filed Jan. 18, 2022). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17),” 3GPP TS 23.003, V17.3.0, pp. 1-145 (Sep. 2021). [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Principles and Guidelines for Services Definition; Stage 3 (Release 17),” 3GPP TS 29.501, V17.3.1 pp. 1-78 (Sep. … [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 29.500, V17.4.0, pp. 1-109 (Sep.… [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.2.1, pp. 1-712 (Sep. 2021). [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.2.0 pp. 1-542 (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.3.0, pp. 1-271 (Sep. 2021). [cited by applicant]