Abstract: A system described herein may provide a technique for providing updated address mapping information associated with a service mesh via which one or more containerized instances communicate. The system may include and/or implement an application programming interface (“API”) via which the service mesh may provide address mapping information, that includes public and private addresses associated with containerized instances that communicate via the service mesh. The updated information may be received on an ongoing basis, and may be provided to another system that has subscribed to receiving updated mapping information associated with one or more containerized instances.

Abstract: Network devices may receive a Transport Control Protocol (TCP) segment from a user device. The TCP segment includes a TCP header and a payload, and the payload includes either a Hypertext Transfer Protocol (HTTP) plaintext message or a Secure HTTP (HTTPS) encrypted message. The network devices may extract a TCP Synchronization (SYN) signature from the TCP header and determine whether the payload of the TCP segment includes a HTTP plaintext message or a HTTPS encrypted message. When the payload includes a HTTP plaintext message, the network devices may extract contents of a HTTP User-Agent field from the HTTP plaintext message, determine a device type identifier (ID) and a category ID based on the extracted contents, and update a plurality of device signatures based on the TCP signature, the device type ID, and the category ID.

Abstract: A system described herein may provide a technique for selecting and configuring a capture component and a filtering and analysis component for traffic capture in a manner that suitably accounts for Service Level Agreements (“SLAs”) of traffic to be captured. A traffic capture request may indicate one or more SLAs and/or other attributes, and an orchestration system may identify a network function (such as a User Plane Function (“UPF”) of a wireless network) that handles traffic that includes the requested traffic and instantiate the capture component at a node that implements the network function. The orchestration system may select a node, from a cluster of nodes, that is able to filter and analyze the traffic in an expedient manner in accordance with SLA(s) associated with the requested traffic, and install the filtering and analysis component at the selected node.

Abstract: A system described herein may provide a technique for selecting and configuring a capture component and a filtering and analysis component for traffic capture in a manner that suitably accounts for Service Level Agreements (“SLAs”) of traffic to be captured. A traffic capture request may indicate one or more SLAs and/or other attributes, and an orchestration system may identify a network function (such as a User Plane Function (“UPF”) of a wireless network) that handles traffic that includes the requested traffic and instantiate the capture component at a node that implements the network function. The orchestration system may select a node, from a cluster of nodes, that is able to filter and analyze the traffic in an expedient manner in accordance with SLA(s) associated with the requested traffic, and install the filtering and analysis component at the selected node.

Abstract: Network devices may receive a Transport Control Protocol (TCP) segment from a user device. The TCP segment includes a TCP header and a payload, and the payload includes either a Hypertext Transfer Protocol (HTTP) plaintext message or a Secure HTTP (HTTPS) encrypted message. The network devices may extract a TCP Synchronization (SYN) signature from the TCP header and determine whether the payload of the TCP segment includes a HTTP plaintext message or a HTTPS encrypted message. When the payload includes a HTTP plaintext message, the network devices may extract contents of a HTTP User-Agent field from the HTTP plaintext message, determine a device type identifier (ID) and a category ID based on the extracted contents, and update a plurality of device signatures based on the TCP signature, the device type ID, and the category ID.

Abstract: A device may configure a centralized performance indicator data store for a plurality of network function devices included in a telecommunications system. The centralized performance indicator data store may be accessible by the plurality of network function devices on a management bus of the telecommunications system via a service-based interface. The device may subscribe the centralized performance indicator data store to a message class associated with performance indicator data that is generated by the plurality of network function devices. The device may receive, from the plurality of network function devices, one or more published communications associated with the message class. The one or more published communications may include the performance indicator data. The device may store the performance indicator data in the centralized performance indicator data store.

Abstract: A device may configure a centralized performance indicator data store for a plurality of network function devices included in a telecommunications system. The centralized performance indicator data store may be accessible by the plurality of network function devices on a management bus of the telecommunications system via a service-based interface. The device may subscribe the centralized performance indicator data store to a message class associated with performance indicator data that is generated by the plurality of network function devices. The device may receive, from the plurality of network function devices, one or more published communications associated with the message class. The one or more published communications may include the performance indicator data. The device may store the performance indicator data in the centralized performance indicator data store.