System and method for message management across a network

• US 10,235,226 B1
• Filed: 08/21/2018
• Issued: 03/19/2019
• Est. Priority Date: 07/24/2018
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Shekhar, Ravi, Ghosh, Ameo, Campbell, Ian McDowell
• Primary Examiner(s): Mudrick, Timothy A
• Application Number:
  US16/107,794
• Time in Patent Office: 210 Days
• Field of Search: 719330
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/52 Multiprotocol routers
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering
• CPC Class Codes: H04L 49/70 Virtual switches
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.

Claims

1. A method for managing service calls across a network, the method comprising:

retrieving, by a global source routing engine (SRE) and from a network repository function (NRF), a list comprising network functions (NFs) and endpoint addresses associated with respective NFs, the global SRE comprising a forwarding table;

storing, in the forwarding table, the retrieved list;

transmitting, by the global SRE and to a target SRE, a portion of the list, a portion of the list related to a network slice for which the target SRE is responsible;

receiving, by the target SRE and from an access function (AMF), a request for slice information, the request for slice information including a user equipment (UE) identifier; and

providing, by the target SRE and to the AMF, a response including the slice information for attaching the UE to a network slice identified by the slice information.

2. The method of claim 1, further comprising retrieving, by the target SRE and from a network slice selection function (NSSF), slice information in response to the request for slice information.

3. The method of claim 1, further comprising:

transmitting, by the AMF and to a session management function (SMF), a command for creating a protocol data unit (PDU) context; and

receiving, by the AMF and from the SMF, a PDU context for attaching the UE to the network slice identified by the slice information.

4. The method of claim 3, further comprising:

receiving, by a second target SRE and from the SMF, a request for quality of service (QOS) information;

retrieving, by the second target SRE, QOS information from a policy control function (PCF) based on the received request for QOS information; and

transmitting, to the SMF, the retrieved QOS information for creating the PDU context.

5. The method of claim 1, further comprising:

receiving, by the target SRE, an application programming interface (API) call directed to a NF of the list comprising NFs and endpoint addresses, the API call formatted in a web protocol;

converting, by the target SRE, the API call from the web protocol format to a micro-services protocol format; and

transmitting, by the target SRE and to the NF, the converted API call based on an endpoint address associated with the NF, the endpoint address from the list comprising NFs and endpoint addresses.

6. The method of claim 5, further comprising:

receiving, by the target SRE and from the NF, a response to the transmitted converted API call, the response in a micro-services protocol format;

converting, by the target SRE, the received response to the transmitted API call into web protocol format; and

transmitting, by the target SRE and to a destination service, the web protocol formatted response to the transmitted API call.

7. The method of claim 5, wherein the micro-services protocol format is gRPC and the web protocol format is HTTP/2.

8. A system for managing service calls across a network, the system comprising:

a global source routing engine (SRE) comprising a forwarding table;

a network repository function (NRF) in communication with the global SRE, the global SRE retrieving from the NRF a list comprising network functions (NFs) and endpoint addresses associated with respective NFs;

a target SRE in communication with the global SRE, the global SRE transmitting to the target SRE a portion of the list related to a network slice for which the target SRE is responsible; and

an access function (AMF) in communication with the target SRE, the target SRE receiving from the AMF a request for slice information, the request for slice information including a user equipment (UE) identifier;

wherein the target SRE provides to the AMF a response including the slice information for attaching the UE to a network slice identified by the slice information.

9. The system of claim 8, further comprising a network slice selection function (NSSF), wherein the target SRE retrieves from the NSSF slice information in response to the request for slice information.

10. The system of claim 8, further comprising a session management function (SMF) in communication with the AMF, the AMF transmitting to the SMF a command for creating a protocol data unit (PDU) context, wherein the AMF receives from the SMF a PDU context for attaching the UE to the network slice identified by the slice information.

11. The system of claim 10, further comprising:

a second target SRE in communication with the SMF, the second target SRE receiving from the SMF a request for a quality of service (QOS) information; and

a policy control function (PCF) in communication with the second target SRE, the second target SRE retrieving from the PCF QOS information based on the received request for QOS information, and the SMF receives the retrieved QOS information for creating the PDU context.

12. The system of claim 8, wherein:

the target SRE receives an application programming interface (API) call directed to a NF of the list comprising NFs and endpoint addresses, the API call formatted in a web protocol; and

the target SRE converts the API call from the web protocol format to a micro-services protocol format and transmits to the NF the converted API call based on an endpoint address associated with the NF, the endpoint address from the list comprising NFs and endpoint addresses.

13. The system of claim 12, further comprising a destination service and wherein:

the target SRE receives from the NF a response to the transmitted converted API call, the response in a micro-services protocol format; and

the target SRE converts the received response to the transmitted API call into web protocol format and transmits to the destination service the web protocol formatted response to the transmitted API call.

14. The system of claim 12, wherein the micro-services protocol is gRPC and the web protocol is HTTP/2.

15. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to:

retrieve, by a global source routing engine (SRE) and from a network repository function (NRF), a list comprising network functions (NFs) and endpoint addresses associated with respective NFs, the global SRE comprising a forwarding table;

store, in the forwarding table, the retrieved list;

transmit, by the global SRE and to a target SRE, a portion of the list, a portion of the list related to a network slice for which the target SRE is responsible;

receive, by the target SRE and from an access function (AMF), a request for slice information, the request for slice information including a user equipment (UE) identifier; and

provide, by the target SRE and to the AMF, a response including the slice information for attaching the UE to a network slice identified by the slice information.

16. The non-transitory computer readable medium of claim 15, further comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to retrieve, by the target SRE and from a network slice selection function (NSSF), slice information in response to the request for slice information.

17. The non-transitory computer readable medium of claim 15, further comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to:

transmit, by the AMF and to a session management function (SMF), a command for creating a protocol data unit (PDU) context; and

receive, by the AMF and from the SMF, a PDU context for attaching the UE to the network slice identified by the slice information.

18. The non-transitory computer readable medium of claim 17, further comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to:

receive, by a second target SRE and from the SMF, a request for quality of service (QOS) information;

retrieve, by the second target SRE, QOS information from a policy control function (PCF) based on the received request for QOS information; and

transmit, to the SMF, the retrieved QOS information for creating the PDU context.

19. The non-transitory computer readable medium of claim 15, further comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to:

receive, by the target SRE, an application programming interface (API) call directed to a NF of the list comprising NFs and endpoint addresses, the API call formatted in a web protocol;

convert, by the target SRE, the API call from the web protocol format to a micro-services protocol format; and

transmit, by the target SRE and to the NF, the converted API call based on an endpoint address associated with the NF, the endpoint address from the list comprising NFs and endpoint addresses.

20. The non-transitory computer readable medium of claim 19, further comprising instructions that, when executed by one or more processors configured for network management, cause the one or more processors to:

receive, by the target SRE and from the NF, a response to the transmitted converted API call, the response in a micro-services protocol format;

convert, by the target SRE, the received response to the transmitted API call into web protocol format; and

transmit, by the target SRE and to a destination service, the web protocol formatted response to the transmitted API call.