Abstract: The technology disclosed herein enables continuity of a call recording when a recording system restarts. In a particular example, a method includes establishing a recording session between a session recording client and a session recording system. The recording session is associated with a communication session being recorded. The method also includes periodically transmitting requests for counter values from the session recording system. The counter value indicates a number of times the session recording system has restarted. The method further includes receiving a first counter value of the counter values from the session recording system and receiving subsequent counter values of the counter values from the session recording system after receiving the first counter value. In response to determining that one of the subsequent counter values does not match the first counter value, the method includes ending the recording session.

Abstract: Systems and methods are disclosed for implementing a virtual IP for a container pod. In certain embodiments, a method may comprise operating a cloud based network system in a containerized software environment to assign a virtual internet protocol (VIP) address to an application pod of a containerized software environment, the VIP being directly reachable from a network external to the containerized software environment. The method may include reserving a range of internet protocol (IP) addresses for use as VIP addresses, assigning a first fixed IP address to a first application pod, assigning a first VIP address from the range of IP addresses to the first application pod, and routing traffic directed to the first VIP address to the first fixed IP address.

Abstract: The technology disclosed herein enables continuity of a call recording when a recording system restarts. In a particular example, a method includes establishing a recording session between a session recording client and a session recording system. The recording session is associated with a communication session being recorded. The method also includes periodically transmitting requests for counter values from the session recording system. The counter value indicates a number of times the session recording system has restarted. The method further includes receiving a first counter value of the counter values from the session recording system and receiving subsequent counter values of the counter values from the session recording system after receiving the first counter value. In response to determining that one of the subsequent counter values does not match the first counter value, the method includes ending the recording session.

Abstract: Methods, systems, and computer readable media for triggering a session initiation protocol (SIP) re-invite message are disclosed. One example method for triggering a SIP re-invite message occurs at a SIP node. The method comprises: determining that the SIP node is not needed as an intermediary node for facilitating SIP communications between a first SIP user agent and a second SIP user agent; generating a SIP message comprising information in a SIP extension header field for triggering an endpoint to generate a SIP re-invite message; and sending the SIP message toward the first SIP user agent.

Abstract: Systems and methods are disclosed for implementing a virtual IP for a container pod. In certain embodiments, a method may comprise operating a cloud based network system in a containerized software environment to assign a virtual internet protocol (VIP) address to an application pod of a containerized software environment, the VIP being directly reachable from a network external to the containerized software environment. The method may include reserving a range of internet protocol (IP) addresses for use as VIP addresses, assigning a first fixed IP address to a first application pod, assigning a first VIP address from the range of IP addresses to the first application pod, and routing traffic directed to the first VIP address to the first fixed IP address.

Abstract: Various embodiments of the present technology generally relate to systems and methods for managing configuration data in a virtual or containerized software environment. A configuration data management system may enable ConfigMaps to be added to an application pod of a virtual software environment without restarting the application pod, a ConfigMap including a data object containing configuration data. The configuration data management process may monitor for creation of a first ConfigMap in the virtual software environment, append a name of the first ConfigMap to a data element name from the first ConfigMap to produce an appended data element, and store the appended data element to a super ConfigMap, the super ConfigMap including a specialized ConfigMap configured to contain data elements from multiple ConfigMaps.

Abstract: The technology disclosed herein enables a service manager of a container orchestration platform to handle failovers of pods executing an application in a high availability mode. In a particular example, a method includes receiving pod information including unique application identifiers generated by the application and indications of which of the pods are active and standby. The method further includes configuring service objects provided by the container orchestration platform of the pods to each correspond to respective ones of the pods based on the unique application identifiers. The method also includes receiving updated pod information indicating a first pod of the pods, which was on standby, is now active having first application identifier of the unique application identifiers previously assigned to a second pod that failed. Additionally, the method includes reconfiguring a service object associated with the first application identifier to correspond to the first pod instead of the second pod.

Abstract: Systems and methods are disclosed for implementing cloud network service management. In certain embodiments, a method may comprise operating a cloud native application (CnApp) custom operator in a containerized software environment to dynamically manage cloud native network service on a target application pod via a persistent network interface to an external network. The method may include obtaining a first resource definition data, for a first custom resource, to define attributes for a bundle of resources used to implement the cloud native network service, and creating the first custom resource based on the first resource definition data, including initializing the target application pod. The method may include generating a second resource definition data, derived from the first resource definition data, to define attributes for a virtual network interface to associate with the target application pod, and applying the second resource definition data to initialize creation of a second custom resource.

Abstract: Systems and methods are disclosed for implementing a cloud based network function. In certain embodiments, a method may comprise operating a custom operator in a containerized software environment such as Kubernetes to manage a virtual network interface controller (Vnic) on an application pod, the Vnic being reachable directly from a network external to the containerized software environment. The method may include identifying the application pod to which to add the Vnic, determining a worker node in the containerized software environment on which the application pod is running, creating the Vnic on the worker node, and executing a job on the worker node to inject the Vnic into the application pod.

Abstract: Various embodiments of the present technology generally relate to systems and methods for provisional response handling in session initiation protocol (SIP) calls, to maintain performance during directed denial of service (DDoS) attacks or bursts of response messages. A proxy server for SIP calls may initiate processing of a first SIP response, receive a second SIP response, and add the second SIP response to a message queue. The proxy server may then receive a third SIP response having a response identifier, compare the response identifier to responses in the message queue, and drop the third SIP response based on the response identifier matching a response in the message queue.

Abstract: Various embodiments of the present technology generally relate to systems and methods for managing secrets in a virtual or containerized software environment. A secret management system may enable secrets to be added to an application pod of a virtual software environment without restarting the application pod, wherein a secret may include a data object containing sensitive data. The secret management process may monitor for creation of a first secret in the virtual software environment, append a name of the first secret to a key file from the first secret to produce an appended key file, and store the appended key file to a super secret, the super secret including a specialized secret configured to contain key files from multiple secrets.

Abstract: Methods, systems, and computer readable media for triggering a session initiation protocol (SIP) re-invite message are disclosed. One example method for triggering a SIP re-invite message occurs at a SIP node. The method comprises: determining that the SIP node is not needed as an intermediary node for facilitating SIP communications between a first SIP user agent and a second SIP user agent; generating a SIP message comprising information in a SIP extension header field for triggering an endpoint to generate a SIP re-invite message; and sending the SIP message toward the first SIP user agent.

Abstract: The subject matter described herein includes a method for enhanced signaling gateway status detection and selection for emergency calls. The method includes, in a mobility management entity (MME) including at least one processor, detecting that a signaling gateway is in a risky state using a combination of echo request and call setup signaling timeouts. The method further includes marking the signaling gateway as risky in a signaling gateway status database maintained by the MME. The method further includes performing signaling gateway selection for an emergency call in a manner that excludes signaling gateways marked as risky. The method further includes routing the emergency call to a signaling gateway selected by the signaling gateway selection.

Abstract: The subject matter described herein includes a method for enhanced signaling gateway status detection and selection for emergency calls. The method includes, in a mobility management entity (MME) including at least one processor, detecting that a signaling gateway is in a risky state using a combination of echo request and call setup signaling timeouts. The method further includes marking the signaling gateway as risky in a signaling gateway status database maintained by the MME. The method further includes performing signaling gateway selection for an emergency call in a manner that excludes signaling gateways marked as risky.

Abstract: Methods, systems, and computer readable media for suppressing redundant packet filter installation on user equipment in a mobile network are disclosed. In some examples, a method includes installing a first packet filter on user equipment (UE) for the mobile network. The method includes receiving a filter installation instruction from a policy rules node for the policy enforcement node to install at least a second packet filter on the UE. The method includes determining that the second packet filter is redundant to the first packet filter and, in response to determining that the second packet filter is redundant to the first packet filter, disregarding the filter installation instruction to install the second packet filter on the UE.

Abstract: A method for multiple BFD session optimization includes receiving a request for establishing a BFD session and in response, establishing a first BFD session for monitoring a link to a remote node over a first network interface. The type of the first BFD session is set to normal. BFD control packets are exchanged with the remote node as part of the first session for monitoring status of link to the remote node. A request for establishing a second BFD session to monitor the status of the same link is received. In response, the type of the first BFD session is changed to master. A second BFD session is established, and the type of the second BFD session is set to slave. For the second BFD session, BFD session state is obtained from the first BFD session without exchanging BFD control packets for the second BFD session with the remote node.

Abstract: A method for multiple BFD session optimization includes receiving a request for establishing a BFD session and in response, establishing a first BFD session for monitoring a link to a remote node over a first network interface. The type of the first BFD session is set to normal. BFD control packets are exchanged with the remote node as part of the first session for monitoring status of link to the remote node. A request for establishing a second BFD session to monitor the status of the same link is received. In response, the type of the first BFD session is changed to master. A second BFD session is established, and the type of the second BFD session is set to slave. For the second BFD session, BFD session state is obtained from the first BFD session without exchanging BFD control packets for the second BFD session with the remote node.

Abstract: The subject matter described herein includes methods, systems, and computer readable media for supporting end-to-end priority service in LTE or subsequent generation networks. One method for supporting such priority occurs at a network node configured to operate in an LTE or subsequent generation network. The method includes receiving an incoming message associated with a communications session or transaction in the network. The message includes an end-to-end priority user indicator identifying a user associated with the session or transaction as a priority user. The method optionally includes storing an association between the end-to-end priority user indicator and the session or transaction. The method further includes treating the session with a priority corresponding to the end-to-end priority user indicator.

Abstract: According to one aspect, the subject matter described herein includes a system for suppressing message flooding during access note-Gateway (AN-GW) unavailability and/or after AN-GW restoration. The system includes a network node including at least one processor and a memory. The network node includes an interface for receiving an indication of unavailability of an AN-GW. An AN-GW status maintainer maintains, in the memory, a node-level AN-GW status indicator indicating availability or unavailability of the AN-GW and setting the node-level AN-GW status indicator to unavailable in response to receiving the indication of unavailability of the AN-GW. An AN-GW status checker checks status of the AN-GW using the node-level AN-GW status indicator and suppresses, based on the status of the AN-GW determined from the node-level AN-GW status indicator, messaging for plural sessions involving the AN-GW.

Abstract: Methods, systems, and computer readable media for efficient mapping of rule precedence values and filter priority values are disclosed. In some examples, a method occurs at a policy rules node for determining policies in a mobile network. The method may include generating a rule installation request including a rule precedence value, at least one packet filter associated with the rule precedence value, and a filter priority value indicating a first value of a filter priority value range associated with the at least one packet filter. The method may also include sending the rule installation request to a policy enforcement node for installation on user equipment (UE).