# US 12,762,003 B2 · Panic level manager > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,762,003 B2 - Document ID: US12762003B2 - Status: Granted - Kind: B2 - Application number: 18/945,082 - Filed: 2024-11-12 - Published: 2026-05-14 - Granted: 2026-10-13 - Earliest claimed: 2024-11-12 - Assignees: T-Mobile Innovations LLC - Applicants: T-Mobile Innovations LLC - Inventors: Tyler Gothmann; Vladimir Pilipenko - Web page: https://patentgrep.com/patent/US12762003B2 ## CPC - G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)} - G06F 21/602: {Providing cryptographic facilities or services} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for managing the panic level of a device are disclosed. In one aspect, a method includes the actions of generating first diagnostic data that is associated with the computing device. The actions further include transmitting, to a server, the first diagnostic data. The actions further include receiving, from the server, an error response that indicates an error occurred because of transmitting the first diagnostic data. The actions further include, in response to receiving the error response, ceasing transmitting, to the server, second diagnostic data that is associated with the computing device. ## Claims ### Claim 1 A method that is configured to limit transmitting sensitive data to a zombie server, comprising: generating, by an application of a computing device, first sensitive data that is associated with the computing device; transmitting, by the application of the computing device and to the zombie server that is configured to transmit an error message in response to receiving any type of data, the first sensitive data; receiving, by the application of the computing device and from the zombie server, a first error response; based on receiving the first error response, incrementing, by the application of the computing device, an error response count that indicates a number of error responses received from the zombie server; comparing, by the application of the computing device, the first error response count received from the server to a first error response count threshold; based on comparing the first error response count to the first error response count threshold, determining, by the application of the computing device, that the error response count does not satisfy the first error response count threshold; based on determining that the error response count does not satisfy the first error response count threshold, generating, by the application of a computing device, second sensitive data that is associated with the computing device; transmitting, by the application of the computing device and to the zombie server, the second sensitive data; receiving, by the application of the computing device and from the zombie server, a second error response; based on receiving the second error response, generating, by the application of the computing device, first heartbeat data that is associated with the computing device; transmitting, by the application of the computing device and to the zombie server, the first heartbeat data; generating, by the application of the computing device, second heartbeat data that is associated with the computing device; and transmitting, by the application of the computing device and to the zombie server, the second heartbeat data. ### Claim 2 (depends on 1) The method of claim 1, comprising: storing, by the application of the computing device, the first sensitive data in a diagnostic data storage medium of the computing device; and storing, by the application of the computing device, the second sensitive data in the diagnostic data storage medium. ### Claim 3 (depends on 1) The method of claim 1, comprising: encrypting, by the application of the computing device, the first sensitive data, wherein transmitting, by the application of the computing device and to the zombie server, the first sensitive data comprises transmitting the encrypted first sensitive data. ### Claim 4 (depends on 1) The method of claim 1, wherein the first error message is a 400/500 failure response. ### Claim 5 A method that is configured to prevent a computing device from outputting sensitive data in response to receiving an error response from a server and while the computing device is unable to receive software updates, comprising: generating, by a headless application of the computing device, first personally identifiable information; storing, by the headless application of the computing device, the first personally identifiable information in a diagnostic data storage medium of the computing device; determining, by the headless application of the computing device, a first panic level that indicates to transmit the first personally identifiable information to a server and a first temporal frequency for the headless application to send the first personally identifiable information to the server; based on satisfying the first temporal frequency, transmitting, by the headless application of the computing device and to the server, the first personally identifiable information; receiving, by the headless application of the computing device and from the server, a first error response that indicates an error occurred because of transmitting the first personally identifiable information; based on receiving the first error response, incrementing, by the headless application of the computing device, an error response count that indicates a number of error responses received from the server; comparing, by the headless application of the computing device, the first error response count received from the server to a first error response count threshold; based on comparing the first error response count to the first error response count threshold, determining, by the headless application of the computing device, that the error response count satisfies the first error response count threshold; based on determining that the error response count satisfies the first error response count threshold, updating, by the headless application of the computing device, the first panic level to a second panic level that indicates to cease transmitting second personally identifiable information and indicates to transmit heartbeat data to the server and a second temporal frequency for the headless application to send the heartbeat data to the server; based on satisfying the second temporal frequency, transmitting, by the headless application of the computing device and to the server, the heartbeat data; receiving, by the headless application of the computing device and from the server, a second error response that indicates an error occurred because of transmitting the heartbeat data; based on receiving the second error response, incrementing, by the headless application of the computing device, the error response count; comparing, by the headless application of the computing device, the error response count received from the server to a second error response count threshold; based on comparing the error response count to the second error response count threshold, determining, by the headless application of the computing device, that the error response count satisfies the second error response count threshold; and based on determining that the error response count satisfies the second error response count threshold, updating, by the headless application of the computing device, the second panic level to a third panic level that indicates to cease transmitting additional heartbeat data to the server. ### Claim 6 (depends on 5) The method of claim 5, wherein the second panic level indicates to delete the first personally identifiable information and other personally identifiable information from the diagnostic data storage medium of the computing device. ### Claim 7 (depends on 5) The method of claim 5, comprising: encrypting, by the headless application of the computing device, the first personally identifiable information, wherein transmitting, by the headless application of the computing device and to the server, the first personally identifiable information comprises transmitting the encrypted first personally identifiable information. ### Claim 8 (depends on 5) The method of claim 5, wherein the first error message is a 400/500 failure response. ### Claim 9 A computer-implemented method comprising: generating, by an application of a computing device, first diagnostic data that is associated with the computing device; transmitting, by the application of the computing device and to a server, the first diagnostic data; receiving, by the application of the computing device and from the server, an error response that indicates an error occurred because of transmitting the first diagnostic data; and in response to receiving the error response, determining, by the application of the computing device, a panic level that indicates a type of data for the application to send to the server and a temporal frequency for the application to send the type of data to the server; and based on the panic level, ceasing, by the application of the computing device, transmitting, to the server, second diagnostic data that is associated with the computing device. ### Claim 10 (depends on 9) The method of claim 9, comprising: in response to receiving the error response, ceasing, by the application of the computing device, generation of second diagnostic data. ### Claim 11 (depends on 9) The method of claim 9, comprising: in response to receiving the error response, updating, by the application of the computing device, an error response count that indicates a number of error messages received from the server. ### Claim 12 (depends on 9) The method of claim 9, comprising: accessing, by the application of the computing device, an error response count that indicates a number of error messages received from the server; comparing, by the application of the computing device, the error response count to an error response count threshold; and determining, by the application of the computing device, that the error response count satisfies the error response count threshold, wherein ceasing transmitting, to the server, the second diagnostic data is further based on determining that the error response count satisfies the error response count threshold. ### Claim 13 (depends on 9) The method of claim 9, comprising: generating, by the application of the computing device, first heartbeat data that is associated with the computing device; transmitting, by the application of the computing device and to the server, the first heartbeat data; after receiving the error response, generating, by the application of the computing device, second heartbeat data that is associated with the computing device; and transmitting, by the application of the computing device and to the server, the second heartbeat data. ### Claim 14 (depends on 9) The method of claim 9, comprising: generating, by the application of the computing device, first heartbeat data that is associated with the computing device; transmitting, by the application of the computing device and to an additional server, the first heartbeat data; receiving, by the application of the computing device and from the additional server, a success response that indicates the additional server successfully received the first heartbeat data; after ceasing transmitting, to the server, the second diagnostic data and in response to receiving the success response, generating, by the application of the computing device, third diagnostic data that is associated with the computing device; and transmitting, to the additional server, the third diagnostic data that is associated with the computing device. ### Claim 15 (depends on 9) The method of claim 9, comprising: receiving, by the computing device, data identifying an additional server and instructions to update the application; and updating, by the computing device, the application to specify that the application sends additional heartbeat data or additional diagnostic data to the additional server. ### Claim 16 (depends on 9) The method of claim 9, comprising: storing, by the application of the computing device, the first diagnostic data; and in response to receiving the error response, deleting, by the application of the computing device, the first diagnostic data. ### Claim 17 (depends on 9) The method of claim 9, comprising: encrypting, by the application of the computing device, the first diagnostic data, wherein transmitting, by the application of the computing device and to the server, the first diagnostic data comprises transmitting the encrypted first diagnostic data. ### Claim 18 (depends on 9) The method of claim 9, wherein the server is configured to transmit the error response in response to receiving any type of data. ### Claim 19 (depends on 9) The method of claim 9, wherein the diagnostic data includes personal identifiable information.