# US 12,003,361 B2 · Data-powered shipwright for network cloud maintenance > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,361 B2 - Document ID: US12003361B2 - Status: Granted - Kind: B2 - Application number: 18/179,086 - Filed: 2023-03-06 - Published: 2023-06-29 - Granted: 2024-06-04 - Earliest claimed: 2020-11-30 - Assignees: AT&T Intellectual Property I, L.P. - Applicants: AT&T Intellectual Property I, L.P. - Inventors: Zhiqiang Qian; Soumyajit Chakraborty - Web page: https://patentgrep.com/patent/US12003361B2 ## CPC - H04L 41/06: Management of faults, events, alarms or notifications - H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] - H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis - H04L 41/0661: {by reconfiguring faulty entities} - H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV] - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV - H04L 43/50: Testing arrangements - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 41/0894: Policy-based network configuration management - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system comprising a network cloud configured for a point of deployment containerized environment, a plurality of servers in communication with the network cloud, configured to establishing a point of deployment (POD) in one of the plurality of servers, receiving a determination that the POD is not operational, mapping the topology of the POD, and based on the mapping step, troubleshooting the POD in accordance with a set of rules. ## Claims ### Claim 1 A system, comprising: a network cloud that is configured for a point of deployment (POD) containerized environment; a plurality of servers in communication with the network cloud; an input-output interface; a processor coupled to the input-output interface wherein the processor is further coupled to a memory, the memory having stored thereon executable instructions that when executed by the processor cause the processor to effectuate operations comprising: mapping a topology of connections to and from a POD that is not operational; based on the mapping, testing the connections of the POD; responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection; responsive to a second determination of failing to automatically repair the connection, generating a trouble ticket; and responsive to a third determination of no failure of the connections of the POD, troubleshooting a configuration of the POD in accordance with a set of rules. ### Claim 2 (depends on 1) The system of claim 1, wherein the network cloud is configured in one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration. ### Claim 3 (depends on 1) The system of claim 1, wherein the operations further comprise correcting errors in the configuration of the POD based on the troubleshooting. ### Claim 4 (depends on 3) The system of claim 3, wherein the set of rules comprises verifying the operations of one of a platform, a VM status, a proxy service, and a performance. ### Claim 5 (depends on 1) The system of claim 1, wherein the POD is a network POD. ### Claim 6 (depends on 1) The system of claim 1, wherein the POD is a compute POD. ### Claim 7 (depends on 6) The system of claim 6, wherein the troubleshooting further comprises testing a Kubernetes configuration and an OpenStack configuration. ### Claim 8 (depends on 7) The system of claim 7, wherein the operations further comprise receiving a physical alarm and a virtual alarm and correlating the virtual alarm to the physical alarm. ### Claim 9 (depends on 8) The system of claim 8, wherein the operations further comprise verifying link aggregation interfaces and issuing an alert of P-function/access network failure responsive to verifying the link aggregation interfaces. ### Claim 10 (depends on 9) The system of claim 9, wherein correlating the virtual alarm to the physical alarm comprises correlating a compute node alarm to a C_Leaf alarm, the C_Leaf alarm to OAM switches, the C_Leaf alarm to a R_Leaf alarm, the C_Leaf alarm to a Spine, the C_Leaf alarm to an AGC_Leaf, the AGC_Leaf to network side management switches, the network side management switches to a terminal server, or a combination thereof. ### Claim 11 A method comprising: mapping, by a processing system comprising a processor, a topology of connections of a point of deployment (POD) that is not operational in one of a plurality of servers; based on the mapping, testing, by the processing system, the connections of the POD; responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection by the processing system; responsive to a second determination of failing to automatically repair the connection, generating, by the processing system, a trouble ticket and responsive to a third determination of no failure of the connections of the POD, troubleshooting, by the processing system, a configuration of the POD in accordance with a set of rules. ### Claim 12 (depends on 11) The method of claim 11, further comprising verifying link aggregate interfaces. ### Claim 13 (depends on 11) The method of claim 11, wherein the configuration is one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration. ### Claim 14 (depends on 11) The method of claim 11, further comprising correcting errors in the POD based on the troubleshooting. ### Claim 15 (depends on 11) The method of claim 11, further comprising correlating virtual alarms to physical alarms. ### Claim 16 A non-transitory, machine-readable medium, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, comprising: mapping a topology of connections of a point of deployment (POD) that is not operational; based on the mapping, testing the connections of the POD; responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection; responsive to a second determination of failing to automatically repair the connection, generating a trouble ticket; and responsive to a third determination of no failure of the connections of the POD, troubleshooting a configuration of the POD in accordance with a set of rules. ### Claim 17 (depends on 16) The non-transitory, machine-readable medium of claim 16, wherein the operations further comprise issuing an alert of P-function/access network failure responsive to verifying all link aggregation interfaces. ### Claim 18 (depends on 16) The non-transitory, machine-readable medium of claim 16, wherein the configuration is one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration. ### Claim 19 (depends on 16) The non-transitory, machine-readable medium of claim 16, wherein the operations further comprise correcting errors in the POD based on the troubleshooting. ### Claim 20 (depends on 16) The non-transitory, machine-readable medium of claim 16, wherein the operations further comprise correlating virtual alarms to physical alarms.