System, method, apparatus and computer program product for managing and synchronizing independent computing resources

Abstract

To provide an improved system, apparatus, method and computer program product for managing and synchronizing independent computing resources.SOLUTION: The method comprises receiving an enrollment management request comprising a subscriber data object, transmitting a third party enrollment status request data object associated with the subscriber identifier data object to a third party device management system, receiving a third party enrollment status response data object comprising third party enrollment status data from the third party device management system, and comparing the third party enrollment status response data object data with second enrollment status data in the system.SELECTED DRAWING: Figure 4A

Description

[Technical Field]

[0001] The present disclosure generally relates to a system, method, and apparatus for device protection program management. More specifically, the present invention relates to an independent Concerning parallel operation of computing systems. [Background technology]

[0002] Various computing devices, such as those associated with device protection program management The system provides convenient access to subscribers and operates efficiently while providing communicating the bulk data with one or more third-party computing systems; and In addition, the data received in response to failed transmissions between various systems must be synchronized. Communication errors can cause the system to terminate or not function efficiently. Applicant has identified several deficiencies and problems associated with such systems. Solutions including embodiments of the present disclosure solve many of these identified problems, many of which Many examples are described in detail herein. Summary of the Invention

[0003] In general, the embodiments of the present disclosure provided herein are implemented using independent computing resources. SYSTEM, METHOD, APPARATUS, AND COMPUTER PROCESS FOR MANAGING AND SYNCHRONIZING DATA - Patent application Additionally, at least some embodiments include robust and / or to manage and synchronize independent computing resources in an efficient manner. Other systems, devices, methods, and computers are provided for processing actions of The computer program product, and similar functions, can be seen by examining the following drawings and detailed description. All such modifications will be or become apparent to those skilled in the art. Additional systems, devices, methods, computer program products, and features are described within this description. , within the scope of this disclosure, and protected by the following claims. is intended.

[0004] According to one aspect of the present disclosure, a first exemplary method for detecting network communication synchronization errors is provided. In at least one exemplary embodiment, a first exemplary system is provided. The system includes at least one processor and at least one memory, and One memory contains computer-coded instructions in memory. The instructions, when executed by at least one processor, cause a first exemplary system to: A device protection program is provided, and a subscriber data object including a subscriber identifier data object is provided. The first exemplary system is configured to receive a registration management request including the object. sends the Third Party Registration Status Request Data object to the Third Party Device Manager. and further configured to transmit the third-party registration status request data to a management system. The object is associated with a subscriber identifier data object. The system receives a third-party registration status response from the third-party device management system. The third-party registration status response device is further configured to receive a data object. The answer data object includes third-party registration status data. The system sends the third-party registration status response data object data to the system. The first exemplary system is further configured to compare the second registration status data with the second registration status data in the system. The system provides third-party enrollment status data and device protection program management systems. Detect network communication synchronization errors based on the difference between the registration status in The first exemplary system is further configured to: It is further configured to initiate a system synchronization event.

[0005] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the registration management request data object is a registration subscription request or Contains a cancel record request data object and causes the system to initiate a system synchronization event. To achieve this, the system identifies DPPMS subscribers based on a subscriber identifier data object. Identifies profile data objects and third-party registration status response data Update the DPPMS subscriber profile data object based on the data object It is configured as follows.

[0006] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the system converts the third-party registration status data into a second registration status. It is configured to compare data in real time.

[0007] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the registration management request data object includes a registration subscription request; The subscriber identifier data object and the associated third-party subscriber profile data Third-party device management systems do not contain identified data objects. Third-party registration status indicates and triggers the system to initiate a system synchronization event. To do this, the third-party device management system must have a subscriber identifier data object and associated Third-party subscriber profile data objects attached to the third-party device Third-party subscriber registration request data objects configured to be created by the device management system The system is configured to transmit the object.

[0008] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the enrollment management request data object is a cancellation enrollment request data object. a third-party subscriber profile containing a subscriber identifier data object and associated with the subscriber identifier data object. Identifying that a file data object contains a third-party device management system To indicate the third-party registration status and initiate a system synchronization event, A third-party device management system may have a subscriber identifier data object associated with it. The third-party subscriber profile data object is then passed to the third-party device manager. Third-party subscriber cancellation request data configured to cause the management system to cancel The system is configured to transmit the data object.

[0009] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the system includes a third-party registration manager in a third-party device management system. and attempting to transmit a management request data object and in response to an attempt to transmit a third-party registration management request data object to the system; Receive a transmission error indicating an error communicating with the third-party device management system and identifying an error classification associated with the transmission error, wherein the error classification is , including retryable errors, identifying, determining a request retry time, and After the retry time has elapsed, the third-party device management system Transmitting a registration status request data object and third-party device management receiving a second third-party registration status response data object from the system; and second third-party registration status response data object in real time. and analyzing the second third-party registration status associated with the subscriber identifier data object. and identifying a second identified third-party registration status data. and initiating a second system synchronization event based on the second system synchronization event. .

[0010] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the third-party device management system may include a second third-party device management system. the system receives registration management information from a first third-party device management system. The server is configured to receive a processing request.

[0011] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the system performs third-party data entry based on a subscriber identifier data object. The device management system is further configured to identify the device management system.

[0012] Additionally or alternatively, some exemplary implementations of the first exemplary system include: In an embodiment, the system receives a queue length associated with the action queue. and the action queue contains at least a third-party registration status request. receiving a queue length threshold; identifying a queue length threshold; and receiving a queue length threshold based on the queue length and the queue length threshold. , identifying a queue relationship and determining that the queue relationship meets a queue length threshold. and an executed action that contains at least one executed action process instance. Identifying a set of action process instances and determining which ones are running based on queue length and further configured to update the set of process instances that are included in the action. can be.

[0013] According to another aspect of the present disclosure, a first exemplary method for detecting network communication synchronization errors is provided. A computer-implemented method is provided. The computer-implemented method is hardware, software, firmware, and / or combinations thereof. At least one exemplary embodiment includes operations performed by calculating the alignment. In one embodiment, a first exemplary computer-implemented method illustrates a device protection program, receiving a registration management request including a subscriber data object including a subscriber identifier data object; The first exemplary computer-implemented method includes: and transmitting the device request data object to the third-party device management system. and the third-party registration status request data object includes subscriber identifier data. The first exemplary computer-implemented method is to Receives a third-party registration status response data object from the device management system. and further including transmitting a third-party registration status response data object to the support. The method further includes third-party registration status data. Third-party registration status response data object data to a second and comparing the registration status data of the first exemplary computer implementation with the registration status data of the second exemplary computer implementation. The method involves third-party enrollment status data and device protection program management systems. It also detects network communication synchronization errors based on the difference between the registered status of the A first exemplary computer-implemented method includes: and initiating a system synchronization event.

[0014] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment of the present invention, the enrollment management request data object includes a registration subscription. Contains a request or cancel registration request data object and initiates a system synchronization event a DPPMS subscriber profile based on a subscriber identifier data object; Identifying the data object and the third-party registration status response data object updating a DPPMS subscriber profile data object based on the object; Includes:

[0015] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, the third-party registration status data is used to The data comparison is performed in real time.

[0016] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment of the present invention, the enrollment management request data object includes a registration subscription. The third-party subscriber profile containing the request and associated with the subscriber identifier data object. Ensure that third-party device management systems do not include profile data objects. The identified third-party registration status indicates and initiates a system synchronization event. and provides the third-party device management system with a subscriber identifier data object and associated Third-party subscriber profile data objects attached to the third-party device Third-party subscriber registration request data objects configured to be created by the device management system This includes transmitting the object.

[0017] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, the enrollment management request data object includes a cancellation enrollment request data object. a third-party data object associated with a subscriber identifier data object. Third-party device management systems include a subscriber profile data object The identified third-party registration status indicates that the system is synchronized. a third-party device management system to provide a subscriber identifier data object; Third-party subscriber profile data objects associated with the Third-party subscriber cancellations configured to cause the device management system to cancel The method includes transmitting a cancel request data object.

[0018] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, a computer-implemented method includes: attempting to transmit a third-party registration management request data object to the server; Third-party device management system to receive a third-party registration management request data object. Errors communicating with third-party device management systems in response to attempts to transmit receiving a transmission error indicative of the transmission error; and identifying an error classification associated with the transmission error. and identifying the error classification including a retryable error; and and after the request retry time has elapsed, the third-party device management system transmitting a second third-party registration status request data object to the server; Second-party registration status response data from the third-party device management system receiving a second third-party registration status response data object; analyzes the object in real time to identify the subscriber identifier data object and associated identifying a registration status of two third parties; and initiating a second system synchronization event based on the registration status data; and This includes:

[0019] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, the third-party device management system receiving a registration management request from a first third-party device management system; From the device management system.

[0020] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, a computer-implemented method includes: and further comprising identifying a third-party device management system based on the third-party device management system.

[0021] Additionally or alternatively, some of the first exemplary computer-implemented method In an exemplary embodiment, a computer-implemented method includes: receiving a queue length, the action queue being receiving a status request, identifying a queue length threshold, and identifying a queue relationship based on the queue length threshold and the queue length threshold; A determination that the condition is met and at least one action is taken. Identifying a set of action process instances to be executed, including queues updating a set of action process instances to be executed based on the length of the action process instances; Further includes:

[0022] According to another aspect of the present disclosure, a first exemplary method for detecting network communication synchronization errors is provided. In at least one exemplary embodiment, a computer program product is provided. A first exemplary computer program product includes a program carrying computer program instructions. at least one non-transitory computer-readable storage medium having a computer program thereon; The program instructions, when executed by the processor, indicate a device protection program and and a data object configured to receive a registration management request including a subscriber data object. The first exemplary computer program is configured to: further configured to transmit the request data object to the third-party device management; The Third Party Registration Status Request data object is a Subscriber Identifier data object. The first exemplary computer program is associated with a third-party device. Receive a third-party registration status response data object from the device management system and a third-party registration status response data object is further configured to The first exemplary computer program includes third-party registration status data. Third-party registration status response data object data for the second registration in the system The first exemplary computer program is further configured to compare the status data. Gram is a third-party enrollment status data and device protection program management system to detect network communication synchronization errors based on the difference between the registration status in The first exemplary computer program is further configured to: The system is further configured to initiate a system synchronization event based on the error.

[0023] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the registration management request data object is Contains the subscription request or cancellation request data object and is a system synchronization event. Initiating the DPPMS subscriber profile based on the subscriber identifier data object Identifying file data objects and third-party registration status response data Update the DPPMS subscriber profile data object based on the object. Includes and.

[0024] Additionally or alternatively, any of the first exemplary computer program products In some example embodiments, the third-party registration status data is used to The comparison with the status data is performed in real time.

[0025] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the registration management request data object is The third-party subscriber identifier data object associated with the subscriber request. Third-party device management systems do not include entrant profile data objects The identified third-party registration status indicates that the system is synchronized. a third-party device management system to provide a subscriber identifier data object; Third-party subscriber profile data objects associated with the Third-party subscriber registration request data configured to be created by the device management system This includes transmitting data objects.

[0026] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the enrollment management request data object includes a registration cancellation request. The third party data object includes a request data object and is associated with a subscriber identifier data object. Third-Party Subscriber Profile Data Objects for Third-Party Device Management Systems The identified third-party registration status indicates that the system synchronization event This allows a third-party device management system to access the subscriber identifier data object. Third-party subscriber profile data objects associated with the third-party project. Third-party subscriptions configured to have the third-party device management system cancel them The method includes transmitting a cancel request data object to the user.

[0027] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the computer program product may include a third-party device Attempts to transmit a third-party registration management request data object to the database management system. and providing third-party registration management request data to the third-party device management system. communicate with a third-party device management system in response to an attempt to transmit the object. receiving a transmission error indicative of an error at the time of transmission; and an error classification associated with the transmission error. wherein the error classification includes a retryable error; Determine the request retry time and, after the request retry time has elapsed, transmitting a second third-party registration status request data object to the service management system; and receiving a second third-party registration status from the third-party device management system. receiving a second third-party registration status response data object; Analyze data objects in real time to identify subscriber identifier data objects and their associations identifying a second third-party registration status associated with the second identified sub-subscription; Initiate a second system synchronization event based on third-party registration status data and

[0028] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the third-party device management system a first third-party device management system, wherein receiving a registration management request This comes from the Service Device Management System.

[0029] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the computer program product includes a subscriber identifier data object. Computer-based identification of third-party device management systems based on the object The memory further includes program instructions.

[0030] Additionally or alternatively, any of the first exemplary computer program products In some exemplary embodiments, the computer program product provides a method for generating a sequence of actions associated with the action cue. receiving an associated queue length, wherein the action queue is at least a third receiving a party registration status request and identifying a queue length threshold; Identifying queue relationships based on queue lengths and queue length thresholds; and determining whether the queue relationships are queues. determining that a queue length threshold has been met and determining that at least one action plan has been taken Identifies the set of action process instances that will be executed, including the process instance Update the set of action process instances to be executed based on the queue length. and further comprising computer program instructions for performing the steps of:

[0031] According to one aspect of the present disclosure, a second exemplary method for detecting network communication synchronization errors is provided. A system is provided that includes computer code instructions stored on at least one memory. In at least one embodiment, the computer coded instructions are When running on a third-party device, the system can be The second example is configured to attempt to transmit a registration management request data object. The representative system shall provide a third-party Detecting transmission errors associated with attempted transmissions to a service device management system The second exemplary system is further configured to: The second exemplary system is further configured to identify a classification based on the error classification. The second exemplary system is further configured to identify an error handling instruction set based on the error handling instruction set. The system is further configured to execute the error handling instruction set.

[0032] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, a trained error classification machine learning model is identified and the trained error classification The machine learning model is configured to identify the error classification.

[0033] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the identified error classification, retryable errors, and error handling instruction set are To execute, the system must identify the escalation queue and retry the request. It is configured to add any possible errors to the escalation queue.

[0034] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the identified error classification is a retryable error, and the error handling instruction set To perform the test, the system must identify a maximum retry threshold and the number of retry attempts. determining a retry relationship between a maximum retry threshold and a number of retry attempts; The attempt relationship determines whether the maximum retry threshold is met and determines the requested retry time. and adds the failed transmission to the request queue and returns the failed transmission after the request retry time has elapsed. and attempting to retransmit the missed transmission.

[0035] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, to determine the requested retry time, the system calculates the requested time based on the number of retry attempts. Additionally or alternatively, the second In some exemplary embodiments of the exemplary system, a method for determining a request retry time is , the system is configured to update the request retry time based on an exponential backoff.

[0036] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the identified error classification includes an escalation error, and the error handling instructions Configure the system to add failed transmissions to the transmission queue to execute the set will be done.

[0037] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the identified error classification from the error classification set is used to determine the escalation. This is an error that requires the system to escalate to execute a set of error handling instructions. The third-party error handling system may be configured to transmit the error request to the third-party error handling system.

[0038] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the system includes a third party registration status request data object associated with the receiving a queue length associated with the attached action queue; and a queue length threshold. and identifying queue relationships based on queue lengths and queue length thresholds. and determining that the queue relationship satisfies a queue length threshold. Executed action process instances, including the action process instances that are executed Identifying the process instance and determining the action to be taken based on the queue length and updating the dresser set.

[0039] 2 is a second exemplary computer-implemented method for detecting network transmission errors. According to another aspect of the present disclosure, a computer-implemented method is provided for implementing the computer-implemented method described herein. Implemented through operating hardware, software, and / or firmware A second exemplary computer-implemented method is provided in at least some embodiments for The Act requires the third-party device management system to provide a third-party registration management request data object. The second computer-implemented method includes attempting to transmit the object. To a third-party device management system indicating the occurrence of at least one error during transmission detecting a transmission error associated with the attempted transmission of the second control signal. The computer-implemented method further includes identifying an error classification associated with the transmission error. A second computer-implemented method identifies an error handling instruction set based on the error classification. The second computer-implemented method further includes executing a set of error handling instructions. It further includes:

[0040] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment of the present invention, identifying the error classification comprises using trained error classification machine learning. Identifying the model and performing error classification using a trained error classification machine learning model and identifying.

[0041] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment, the identified error classification includes retryable errors, error handling instruction sets, and The execution of the task identifies the escalation queue and retryable errors. to an escalation queue.

[0042] Additionally or alternatively, some exemplary implementations of the second exemplary system include: In an embodiment, the identified error classification is a retryable error, and the error handling instruction set Executing the test includes identifying a maximum retry threshold and identifying a number of retry attempts. ,determining a retry relationship between a retry maximum threshold and a number of retry attempts, and the retry relationship is determining that a maximum retry threshold has been met, determining a requested retry time, and Adds failed transmissions to a request queue and retry the failed transmissions after the request retry time has elapsed. and attempting to transmit.

[0043] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment, determining the request retry time comprises determining the request retry time based on the number of retry attempts. Additionally or alternatively, a second exemplary embodiment may include updating the request retry time. In some exemplary embodiments of the computer-implemented method, determining a request retry time updating the request retry time based on an exponential backoff.

[0044] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment, the identified error classification includes an escalation error, Executing the error handling instruction set includes adding the failed transmission to the transmission queue. .

[0045] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment, the identified error classifications identified from the error classification set are It is an escalation error, and executing the error handling instruction set is the error escalation. The method includes transmitting the request to a third-party error handling system.

[0046] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment of the present invention, a computer-implemented method includes: Receives the action queue and associated queue length associated with the data object. identifying a queue length threshold; and based on the queue length and the queue length threshold, Identifying a queue relationship and determining that the queue relationship meets a queue length threshold and an action to be executed that contains at least one action to be executed process instance. Identifying a set of application process instances and determining which ones to run based on queue length and updating the action process instance set.

[0047] According to another aspect of the present disclosure, a second exemplary method for detecting network transmission errors is provided. In at least one exemplary embodiment, a computer program product is provided. Two exemplary computer program products include computer program instructions and The computer program instructions transmit the third-party registration management request data object to the third party. The second computer is configured to attempt to transmit the The data program product shall provide a service Detecting transmission errors associated with transmission attempts to third-party device management systems The second computer program product is further configured to: The second computer program is further configured to identify the error classification. The product is further configured to identify an error handling instruction set based on the error classification. The second computer program product further comprises: It is composed.

[0048] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, identifying the error classification comprises using a trained error classifier. Identifying the error using a machine learning model and classifying the error using a trained error classification machine learning model and identifying the classification.

[0049] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, the identified error classification, retryable errors, error handling Executing the instruction set identifies the escalation queue and the retryable and adding the error to an escalation queue.

[0050] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, the identified error classification is a retryable error; Executing the error handling instruction set includes identifying a maximum retry threshold and determining whether to retry the error. and determining a retry relationship between a maximum retry threshold and the number of retry attempts. and determining that the retry relationship satisfies the maximum retry threshold, and Decide whether to add the failed transmission to the request queue and retry it after the request retry time has elapsed. , and attempting to retransmit the failed transmission.

[0051] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, determining the request retry time is based on the number of retry attempts. Additionally or alternatively, updating the request retry time for the second In some exemplary embodiments of the exemplary computer program product, the request retry time Determining the interval includes updating the request retry time based on an exponential backoff.

[0052] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, the identified error classifications include escalation errors. The only way to do this is to execute a set of error handling instructions, which will result in the failed transmission being added to the transmission queue. Includes:

[0053] Additionally or alternatively, a second exemplary computer program product In some exemplary embodiments, the identified error classifications identified from the set of error classifications are is an escalation error, and executing the error handling instruction set resolves the error error. and transmitting the scalation request to a third-party error handling system.

[0054] Additionally or alternatively, some of the second exemplary computer-implemented method In an exemplary embodiment of the present invention, a computer-implemented method includes: Receives the action queue and associated queue length associated with the data object. identifying a queue length threshold; and based on the queue length and the queue length threshold, Identifying a queue relationship and determining that the queue relationship meets a queue length threshold and an action to be executed that contains at least one action to be executed process instance. Identifying a set of application process instances and determining which ones to run based on queue length and updating the action process instance set.

[0055] According to yet another aspect of the present disclosure, a first method for fulfilling claims for unregistered devices is provided. Three exemplary systems are provided. The third exemplary system is a computer-coded The instruction causes the billing data object associated with the subscriber identifier data object to be and a billing data object configured to receive a device identification data object. A third exemplary system includes a device protection program associated with the system. The subscriber profile associated with the subscriber identifier data object is stored in the program subscriber database. The third exemplary embodiment is further configured to query the profile data object. The system is such that the device protection program database is The method is further configured to receive result data indicating that the object does not include the object. A typical system would forward a third-party registration status request to a third-party device management system. and further configured to transmit to the system a third-party registration status request data object. The object contains a subscriber identifier data object and a device identifier data object. A third exemplary system receives subscriber identification from a third-party device management system. Third-party registration status associated with the child data object. and further configured to receive a third-party registration status response data object. The registration status of the third-party device is stored in the third-party device management system. 1 shows a subscriber profile data object. A billing data object associated with a billing data object without a profile data object. The device is further configured to initiate a set of requested processing instructions.

[0056] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the system includes at least one Identifying an anti-tamper instruction set that includes an anti-tamper event and executing the anti-tamper instruction set. The method is further configured to:

[0057] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the system receives a queue length associated with the action queue. wherein the action queue includes at least a subset of the requested data objects; receiving a queue length threshold; identifying a queue length threshold; and determining whether to process the queue length threshold based on the queue length and the queue length threshold. to identify queue relationships and determine whether the queue relationships meet a queue length threshold. and an executed process that contains at least one executed action process instance. Identifying a set of action process instances and determining which ones to run based on queue length The action process instance set is updated and further configured to will be done.

[0058] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the billing data object is received from a first third-party device management system. and a third-party registration status request is received from a second third-party device management Additionally or alternatively, the third exemplary system In some exemplary embodiments, the system may include a subscriber identifier data object. The device is further configured to identify a third-party device management system.

[0059] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the billing data object is configured to communicate with a third party carrier device management system. or a first third-party device, including a third-party vendor device management system a third-party registration status request is received from the third-party service management system and The billing data object is transmitted to the device management system and includes a billing type identifier data. and the system is configured to determine whether the billing type identifier data object is a device Device location applications in situations representing lost or stolen device claims To get the device location application status associated with This allows the device location application to access the device location. The application status indicates the device location and Get the device lost status associated with the application and determining that the loss status is set to a lost state, is initiated in response to determining that the device lost status is set to a lost state , determining, and performing, and the billing type identifier data object is In situations representing device damage claims, Get device location application status and The device location application status indicates that the application is inaccessible. determining whether the device location is indicative of a device status; The device location application status indicates that the application is inaccessible. and further configured to perform a determining step initiated in response to determining that the status indicates It is done.

[0060] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the billing data object is configured to communicate with a third party carrier device management system. or a first third-party device, including a third-party vendor device management system a third-party registration status request is received from the third-party service management system and The billing data object is transmitted to the device management system and includes a billing type identifier data. and the system is configured to determine whether the billing type identifier data object is a device Device location applications in situations representing lost or stolen device claims To get the device location application status associated with This means that the device location application is inaccessible. The application status indicates the billing instruction set and the device location. The device location application indicates that the application is inaccessible. The status indicates that the request is initiated in response to a decision to obtain, and In situations where the Claim Type Identifier data object represents a device damage claim, the Device Location The device location application status associated with the application to obtain device location information and that the device location application is inaccessible. determining that the device location application status indicates The billing instruction set is inaccessible to the device location application. and the device location application status indicates that The device is further configured to:

[0061] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the billing data object is configured to communicate with a third-party manufacturer device management system. a third-party registration status received from a first third-party device management system, the third-party registration status being The status request is transmitted to a second third-party device management system, which then retrieves the billing data object. The object includes a claim type identifier data object, and the system In situations where the child data object represents a lost or stolen device claim, The device location application associated with the and obtaining the access status of the device location application. The device location application status indicates that the device is available for billing. The instruction set tells the device that the device location application is inaccessible. Initiated in response to a determination that the location application status indicates and the claim type identifier data object is a device damage claim. The device location application and associated device location information are used in situations that represent a request for Get the location application status and the device location application The device location application status indicates that the application is inaccessible. determining that the billing processing instruction set indicates that the device location application The device location application status indicates that the application is inaccessible. and determining, initiated in response to a determination that indicates .

[0062] Additionally or alternatively, some exemplary implementations of the third exemplary system include: In an embodiment, the system may include a subscriber profile data object stored in the device. and further configured to receive a transmission error that is not stored in the protection program database. Additionally or alternatively, some exemplary embodiments of the third exemplary system may be implemented as follows: In an embodiment, the system may generate a third-party registration status response based on the third-party registration status response data object. The system is further configured to initiate a system synchronization event based on the received signal.

[0063] According to another aspect of the present disclosure, a third example for fulfilling a claim for an unregistered device is provided. A third exemplary computer-implemented method is provided. As described in the specification, the hardware, software, firmware, and / or Some implementations include operations performed by computing In one embodiment, the computer-implemented method is a process performed by the third exemplary device described above. For example, in at least one embodiment, a third exemplary computer-implemented method The law requires that at least a subscriber identifier data object and an associated billing data object be receiving a billing data object from a device identification data object; receiving and enrolling in the Device Protection Program associated with the system, including the The subscriber database contains a subscriber profile associated with the subscriber identifier data object. The Device Protection Program database queries the device data object. receiving result data indicating that the result data does not include the subscriber profile data object; and transmits a third-party registration status request to the third-party device management system. wherein the third party registration status request data object includes a subscriber identification transmitting the child data object and the device identification data object; Associated with subscriber identifier data objects from third-party device management systems Third-party registration status response data object indicating the status of the third-party registration received. receiving the object, and the third-party registration status is Third-party subscriber profile data objects stored in a device management system and billing data without a subscriber profile data object. and initiating a set of claim processing instructions associated with the data object. Additionally or alternatively, a third exemplary computer-implemented method includes: may include any of the operations described above performed by any of the exemplary apparatus embodiments. do.

[0064] According to another aspect of the present disclosure, a third example for fulfilling a claim for an unregistered device is provided. A third exemplary computer program product is provided. The product comprises computer programs stored on at least one non-transitory computer-readable storage medium. In some embodiments, the third exemplary computer program The program product is configured to perform the operations performed by the third exemplary device described above. For example, in at least one embodiment, A third exemplary computer program product includes at least a subscriber identifier data object. receiving a billing data object associated with the object, The object includes a device identification data object, and receives and associates with the system. The subscriber identifier data object is stored in the associated Device Protection Program subscriber database. querying the subscriber profile data object associated with the object; The device protection program database includes a subscriber profile data object. and receiving result data indicating that the Third Party Registration Status Request has not been and transmitting the third-party registration status to a third-party device management system. The service request data object includes the subscriber identification data object and the device identification data object. and to transfer, including data objects, from third-party device management systems. A subgroup that indicates the third-party registration status associated with the subscriber identifier data object. receiving a third-party registration status response data object, The registration status of the third-party device is stored in the third-party device management system. Receiving a subscriber profile data object indicating a subscriber profile Claim Processing Instructions associated with a Claim Data Object without a Claim Data Object Additionally or alternatively, The third exemplary computer program product comprises a third exemplary apparatus embodiment configured The device may be configured for any of the above operations to be performed by any of the devices.

[0065] According to yet another aspect of the present disclosure, a device is provided with computer-coded instructions for execution. A fourth exemplary system includes at least one processor and at least one memory. In at least one exemplary embodiment, a fourth exemplary system is provided. A computer receives a queue length associated with an action queue by coded instructions. The fourth exemplary system is further configured to identify a queue length threshold. A fourth exemplary system is configured to determine queue length based on a queue length and a queue length threshold. The fourth exemplary system is further configured to identify a cue relationship. The fourth exemplary system is further configured to determine whether a threshold queue length is met. An action is a set of executed actions that contains at least one executed action process instance. The fourth exemplary embodiment is further configured to identify a set of application process instances. The system then determines the set of action process instances to be executed based on the queue length. The method is further configured to update

[0066] Additionally or alternatively, some exemplary implementations of the fourth exemplary system include: In an embodiment, the queue length threshold comprises a queue length maximum threshold, and the queue relationship comprises a maximum queue relationship. and a system associated with a set of action process instances to be executed. Identifying the number of instances executed and the action process instance counter Identifying maximum instances and the number of instances and action process instances that will be executed determining a maximum process instance relationship based on a process count maximum threshold; Max Process Instance Relation Meets Action Process Instance Count Max Threshold and determining that the system meets the requirements. To update the set of action process instances, the system Executing a process instance and running a new action process instance It is further configured to add the action process instance to the set of actions that are executed. It is done.

[0067] Additionally or alternatively, some exemplary implementations of the fourth exemplary system include: In an embodiment, the queue length threshold comprises a queue length minimum threshold, and the queue relation comprises a minimum queue relation. and a system associated with a set of action process instances to be executed. Identifying the number of instances executed and the action process instance counter Identifying the minimum number of instances to be executed and the action process instances determining the minimum process instance relationship based on the minimum process instance count; The small process instance relationship meets the action process instance count minimum. and determining that the system is The system determines the actions to be taken to update the process instance set. Selected action process instance to be executed from the process instance set. It is configured to terminate the process.

[0068] Additionally or alternatively, some exemplary implementations of the fourth exemplary system include: In an embodiment, a system is configured to update the set of action process instances to be executed. The system is associated with at least one outstanding action in the action queue. identifying an action type, the action type being a first action priority; and a second action priority associated with the second action priority. Execution containing the process threads configured to handle the action type identifying an action process instance to be executed, the first action taking priority; a priority of the first action determined to be higher than a second action priority; The action to be executed is to clear the process thread from the process instance and The action performed runs a new process thread for the process instance. and the new process thread is configured to execute an outstanding action associated with the first action type. configured to process administrative actions, and configured to perform can be.

[0069] According to another aspect of the present disclosure, a fourth exemplary computer-implemented method is provided. The exemplary computer-implemented method may be implemented in hardware, software, or both, as described herein. by computing software, firmware, and / or combinations thereof In some embodiments, the computer-implemented method includes the steps of: 4 includes operations performed by an exemplary apparatus. For example, in at least one embodiment A fourth exemplary computer-implemented method includes at least one action cue associated with the action cue. receiving a queue length that has been determined; identifying a queue length threshold; and determining the queue length and the queue length threshold. identifying a queue relationship based on a queue length threshold; and determining whether the queue relationship satisfies the queue length threshold. and determining that at least one action process instance is being executed. identifying a set of action process instances to be executed, including the queue length; and updating a set of action process instances to be executed based on the Additionally or alternatively, the fourth exemplary computer-implemented method includes: Any of the above-described operations performed by any of the above-described embodiments of the four exemplary devices may include:

[0070] According to another aspect of the present disclosure, a fourth exemplary computer program product is provided. A fourth exemplary computer program product is a program for at least one non-transitory computer program. Some embodiments include computer program instructions stored on a data-readable storage medium. Now, the fourth exemplary computer program product is a program for executing the fourth exemplary device described above. For example, the computer program instructions may include instructions configured to perform the operations performed by the For example, in at least one embodiment, a fourth exemplary computer program product comprises: At least receiving a queue length associated with the action queue; and and identifying queue relationships based on queue lengths and queue length thresholds. determining that the queue relationship satisfies a queue length threshold; and Action process instances to be executed, including the action process instances to be executed. Identifying the process instance and determining the action to be taken based on the queue length. and updating the stance set. Additionally, a fourth exemplary computer program product is provided for a fourth exemplary device configured It may be configured for any of the above operations to be performed by the embodiment. [Brief explanation of the drawings]

[0071] [Figure 1] 1 illustrates an exemplary system in which embodiments of the present disclosure may operate. [Figure 2] 1 illustrates a block diagram of a system that may be specially configured within which embodiments of the present disclosure may operate. [Figure 3] 1 illustrates a block diagram of an apparatus that may be specially configured in accordance with an exemplary embodiment of the present disclosure. [Figure 4A] 1 illustrates a flowchart depicting operations performed according to an example exemplary embodiment of the present disclosure. [Figure 4B] 1 illustrates a flowchart depicting operations performed according to an example exemplary embodiment of the present disclosure. [Figure 4C] 1 illustrates an example data flow diagram depicting a system and operation for registration synchronization according to an example embodiment of the present disclosure. [Figure 5] 1 illustrates a flowchart depicting operations performed in accordance with an exemplary embodiment of the present disclosure. [Figure 6] 1 illustrates a flowchart depicting operations performed in accordance with an exemplary embodiment of the present disclosure. [Figure 7] 1 illustrates a block diagram depicting modules specially configured in accordance with an exemplary embodiment of the present disclosure. [Figure 8A] 1 illustrates a flowchart depicting operations performed in accordance with an exemplary embodiment of the present disclosure. [Figure 8B] 1 illustrates a flowchart depicting operations performed in accordance with an exemplary embodiment of the present disclosure. [Figure 9] 1 illustrates a block diagram of a system that may be specially configured within which embodiments of the present disclosure may operate. DETAILED DESCRIPTION OF THE INVENTION

[0072] Embodiments of the present invention are described herein in terms of some, but not all, implementations of the disclosed embodiments. In practice, implementations of the present disclosure may be practiced in various ways, as described more fully below with reference to the accompanying drawings, in which: The embodiments may be embodied in many different forms and are not limited to the embodiments set forth herein. Rather, these embodiments should not be construed as limiting the scope of the present disclosure to the applicable legal Like numbers refer to like elements throughout.

[0073] Overview The Device Protection Program protects subscriber devices if they are damaged, broken, lost, or Protects subscribers if stolen or otherwise affected. While a third party may offer to enroll in one or more device protection programs, all third parties The Company will also be responsible for all claims brought in connection with the Device Protection Program. We do not honor or otherwise process claims submitted to us. A party may register new subscribers associated with one or more device protection programs. However, such third parties may use the Devices controlled by the Provider Entity. Relying on the Data Protection Program Management System (DPPMS) to proactively enforce claims. In some embodiments, a provider entity associated with the DPPMS may may provide supplemental device protection in addition to the protection provided by the third party. This is the DPPMS computing system and the primary device protection provider's This may require a high degree of cooperation between the computing systems. As such, the inventors have identified numerous independently operated systems, including DPPMS and third-party systems. Independent computer systems related to the management of the computing systems and databases used Maintaining synchronization and consistency of computing systems and eliminating redundant or unnecessary tasks Requires a large amount of update and processing activity with frequent changes without placing undue strain on individual systems We have identified several solutions to the key problems.

[0074] The DPPMS can interact with one or more third-party systems, A third-party system is associated with a third-party entity. Party entities may decide their level of control over subscriber devices (e.g., software may refer to software and hardware (only, software and hardware, firmware, etc.). The third-party system may be associated with a mobile carrier, for example. In addition, mobile carriers may use certain software and / or services associated with subscriber devices. or firmware only. Other third-party systems may, for example, In this case, the device manufacturer is associated with the subscriber device. Control the software, firmware, and / or hardware attached to it. Some third-party systems are managed through a third-party device management system. Subscribers associated with or enrolled in any of the above device protection programs a server configured to maintain a subscriber profile data object associated with the This includes third-party device management systems. Users can manage new or existing devices. Subscribe to and / or currently enroll in one or more Device Protection Programs may cancel the enrollment in the Device Protection Program for the subscriber device. The third-party device management system communicates with the DPPMS to manage the third-party devices. One or more registration management request data associated with a subscriber change that occurred via the data management system. In other embodiments, the user may provide a data object directly through the DPPMS. or through a second, third-party device management system. Users may subscribe and / or cancel registration to the program. For example, The application or cancellation occurs through the carrier system and is not forwarded to DPPMS. This can be communicated from the carrier system to the manufacturer system (or vice versa). The Request Data Object is used to communicate between the DPPMS and one or more third-party systems. The subscriber registration data can be synchronized between the third-party systems. Independently maintaining one or more data objects associated with the device and the subscriber. can be done.

[0075] In some embodiments, one or more third party systems may provide a subscriber-to-device Incident data (e.g., lost, stolen, damaged, or otherwise incidents associated with a subscriber device) The subscriber is configured to receive information indicating another event of interest. May report incidents either directly or through third-party systems For example, a subscriber may access a reporting interface (e.g., For example, via a web interface or mobile application), or Incidents may be reported via a call center request. The system is configured to authenticate a user associated with a reported incident. For example, a third-party system may require a user to provide a username and password. authenticates the user by using a pre-determined two-factor authentication method The third party system may authenticate the user, for example, by using a third party user identity. Information indicating that the user has successfully authenticated to the DPPMS in the form of an authentication token. The third-party user identity authentication token may provide information about the third-party The user who reported the device incident associated with the case was notified by a third party. Verify that the third-party case was successfully authenticated by the may be included as part of the third-party case information.

[0076] In response to a reported incident, third parties, such as device manufacturers, may: Third-party device management systems, such as device manager profiling systems You may initiate a third-party case associated with the reported incident through the Therefore, third-party device management systems should be able to track reported incidents, Obtain, receive, and / or otherwise obtain information associated with a user device, subscriber, etc. In some embodiments, the information may be associated with a third-party case. The third-party device management system may store the device information so that it is accessible to the public. For example, to obtain real-time device information associated with a subscriber device and The system device information may be stored in a third-party case.

[0077] DPPMS will process new and / or cancelled subscribers and associated third parties. from a first-party device management system or a first-party device management system from the system and a second third-party device management system associated with the DPPMS, A registration management request data object may be received, for example, from a first third-party device. The management system identifies the mobile device and the associated product for that mobile device type. The second third-party device management system may be the manufacturer's system, and the second third-party device management system may be the to receive subscription registrations and cancellations associated with your mobile device. The registration management request data object may be a third-party device. Indicates new subscribers registered through the service management system and provides subscriber profile data. object, subscriber device identifier, subscriber name (if any), subscriber contact information, etc. a subscriber identifier data object that uniquely identifies the device to the device protection program. It may also include information associated with the new subscriber. A registration management request indicating a new subscriber registered via a third-party device management system. The data object indicates that the third-party device management system has successfully authenticated the subscriber. The authentication token may include a third-party identity authentication token for use in verifying identity.

[0078] Alternatively, the registration management request data object may be used to allow the subscriber to access the third-party device. Indicate that you have cancelled your enrollment in the Device Protection Program via your management system and Subscriber profile data objects, subscriber device identifiers, etc. Cancelled enrollment in the Device Protection Program, such as a user identifier data object Additionally or alternatively, the information may include information associated with a third party. A subscription management request indicating that the subscriber has cancelled the subscription via the device management system. The data object indicates that the third-party device management system has successfully authenticated the subscriber. The authentication token may include a third-party identity authentication token for use in verifying identity.

[0079] An exemplary DPPMS is a third-party system, such as a third-party device management system. one or more for storing outstanding actions and / or requests received from the system The DPPMS contains an action queue for received registration management request data objects. , based on the registration management request data object and the associated instruction set. Protocols can be identified and implemented.

[0080] In an exemplary system, the DPPMS may transmit a signal at one or more predetermined times (e.g., every week, on specific days of the week, at specific times), and from specific third-party device management systems The DPPMS receives the management request data object. The DPPMS may store the processing request data object in an action queue. Action processes can be executed and maintained, where each action process The service retrieves outstanding actions (e.g., registration management request data) from the action process queue. One or more running process threads configured to process a data object include.

[0081] For example, in the exemplary system, the DPPMS processes outstanding actions stored in the action queue. One or more action instance processes configured to handle the action An action instance process can start with a single outstanding action type (e.g. For example, an outstanding registration management request data object) or various outstanding action types. Processes data objects (e.g., outstanding enrollment management requests, outstanding claims, etc.) It can be configured as follows.

[0082] Additionally or alternatively, the exemplary embodiment DPPMS may include third-party Third-party cases by creating, maintaining, and processing claims corresponding to the cases For example, the DPPMS is configured to manage device manufacturer systems and mobile device Receive third-party case information from third-party systems, such as a carrier system Additionally, the DPPMS may collect user case information associated with a third-party case. The user may receive information about the incident (e.g., the date of the incident, the user's description of the incident, etc.).

[0083] DPPMS uses Third Party Case Information and User Case Information to A claim associated with the party case may be generated. The claim may include third-party case information. and user case information. The DPPMS may then add the claim to an action queue for fulfillment. and an action queue for processing the registration management request data object. Additionally or alternatively, the DPPMS may be One or more action process instances to process claims from the corresponding action queue. It may include instances.

[0084] DPPMS receives new third-party cases from one or more third-party systems. For example, the DPPMS may receive one or more device manufacturer systems and one or more Each third party system may communicate with a mobile carrier system, e.g., a third party system. Submitted by the user through an interface associated with the party system Configured to initiate new third-party cases in response to incident reports Additionally or alternatively, third parties such as device manufacturer systems may The service system may be configured to perform user authentication. In an embodiment, the DPPMS may provide the third party case information as part of the third party case information or In addition to transmitting identity information, the system may also receive user authentication information, such as a user authentication token. User credentials are configured so that the third-party system can access the third-party resource. This can be used to verify that the user has authenticated the account.

[0085] After receiving the third-party case information, DPPMS will For example, a user may be configured to receive user case information associated with a DPP. through an interface generated by the MS or associated system. Incident information (e.g., incident date, incident time, incident In some embodiments, the DPPMS may provide third-party Generate a claim based on the case information and user case information.

[0086] The DPPMS may then store the request in an action queue for processing and fulfillment. The MS will then process one or more actions configured to process the outstanding claim. The DPPMS may initiate and / or maintain instances of claims and associated claims. One or more modules and / or subsystems configured to identify positive risks Based at least on the risk of fraud, claims may be approved (deemed not fraudulent). may be accepted (if accepted) or rejected (if deemed fraudulent).

[0087] Alternatively or additionally, in some embodiments, the DPPMS may be A claim requirement associated with the claim may be identified. Each claim requirement may be further actioned by the user. For example, the claim requirements for a given claim may be associated with the claim. In some embodiments, the DPPMS may include user acceptance of one or more disclaimers. , and associated with billing, such as user requirements, within a predetermined billing completion period (e.g., 30 days). All information provided must be received in accordance with the billing requirements and / or related to the billing. If the other information provided is not received from the user within the predetermined time period for completing the claim, The DPPMS may automatically close claims due to lack of action.

[0088] When DPPMS approves, denies, or closes a claim, it The claim status may be configured to set the corresponding claim status when the claim is approved. Once the claim is approved, the DPPMS may set the corresponding claim status of that claim to "Approved." Alternatively, if a claim is denied or closed due to lack of action, the DPP MS will set the corresponding claim status of that claim to "Denied" or "Closed," respectively. It can be determined.

[0089] In some embodiments, the DPPMS may communicate with one or more third party systems to configure The third-party case is configured to update based on the status of the claim. The DPPMS may be controlled by a particular entity, e.g., a provider entity. The provider entity provides a number of features associated with the device protection program. Create, control, or otherwise utilize a DPPMS that ensures claims are not fraudulent while ensuring that such systems process claims in a robust and efficient manner. do.

[0090] In an exemplary aspect, for example, the DPPMS may provide insurance, warranties, etc. for mobile devices. Manage device protection programs for devices such as The PPMS may be a first service of one or more third-party systems, e.g., a carrier system. communicate with a second third-party system and the manufacturer system Manages subscriber enrollment in various device protection programs. Users can use DPPMS or is a subscriber to a device protection program fulfilled through an associated entity Users can register for a device subscription program. If a device covered by the Device Protection Program is damaged, lost, or The device has been stolen or similar (e.g., reduced functionality to access the device, or another event resulting in other malfunctions), In exchange for a DPPM number, you may submit claims related to the Device Protection Program. S and / or associated systems process the claim and fulfill the claim (new data providing a new device, repairing an existing device, etc.) or making a claim fraudulent or unfulfillable (e.g., For example, the user can reject the event because they are not eligible for it.

[0091] In such situations, the DPPMS will take the necessary enforcement actions in response to legitimate user requests. DPPMS will verify that the user is enrolled in the Device Protection Program at the time of the claim. However, the user may make an inquiry to determine whether the device is Device protection at various times, including certain events, or when desired You can register for the program at any time, or alternatively at any time. In addition, the user may cancel the registration at the carrier system, manufacturer system, or Enroll in the Device Protection Program either through the DPPMS or directly through the DPPMS. Therefore, the registration maintained by the DPPMS may be cancelled. The database of subscribers that DPPMS has access to determines whether to fulfil received claims and and / or may not be up to date at the time of determining how to fulfill a received claim.

[0092] Therefore, the DPPMS requires that each subscriber profile data object contains at least one Enrolled in one Device Protection Program, with which DPPMS interfaces A database of subscriber profile data objects separate from third-party systems The DPPMS may establish and maintain a system through one or more third-party systems. Subscriber profile data objects to register and / or cancel registrations The DPPMS may manage one or more third-party device management systems. communicate with these third-party systems to communicate with the subscriber profile data object and Determine the associated third-party registration status and register one or more third-party devices. A registration management request data object (e.g., a new subscriber registration request) from the service management system. or a new subscriber cancellation request). An account may be associated with a human subscriber, a subscriber device, and / or both.

[0093] However, the subscriber profile data objects in the DPPMS are not the corresponding third-party subscriber profile data object stored in the system. may not accurately match the registration status. Enroll in the Device Protection Program through your device management system or If you cancel your program enrollment, DPPMS may not be updated until later. In this regard, one or more third-party device management systems ( ) is an important data object that holds the registration management request data object and communicates with the DPPMS. Avoid constant availability of network resources and other computing resources For example, some third-party device management systems require new registration management The requested data objects may be transmitted to the DPPMS in batches, such as once a week at a specific time. Therefore, if a user changes their enrollment status with respect to the Device Protection Program ( For example, when you subscribe or cancel, you may be asked to sign up for a new subscription. Third-party device management systems can be reached through batch transmission of management request data objects. The corresponding DPP The MS may not reflect this status.

[0094] If there is a communication failure between the systems, it is not possible to ensure that the DPPMS reflects accurate subscriber registrations. Further problems can arise in handling signaling errors and received registration requests. Transmission errors, including errors in received from a third-party device management system without detecting that an error has occurred. They may fail to update the DPPMS based on the information, especially the Device Protection Program registration. In the enrollment aspect, for example, one or more third-party device management systems may implement enrollment management requirements. The request data object is transmitted to the DPPMS to create a subscriber profile data object. However, the DPPMS may update its databases, lists, or other data stores. , for example, network failures or network interface issues of components of the DPPMS. Additionally or alternatively, a failure to receive a transmission may occur due to an interface failure. Instead, the DPPMS may process transmissions received due to corrupted or inconsistent data. If the third-party device cannot The device management system may not or cannot detect the error. In some cases, DPPMS has updated the registration database appropriately, but such updates were not successful. Therefore, DPPMS and third parties may continue to operate on the assumption that The subscriber profile data object maintained by the device management system is If the system is unable to detect such a situation, There is.

[0095] The DPPMS identifies the appropriate enrollment status associated with the subscriber to the Device Protection Program. If the claim does not reflect the device protection program, the DPPMS will or other transactions may be improperly processed. For example, the DPPMS may Cancel a subscriber's enrollment in the Device Protection Program via the device management system. Subscriber profile data objects associated with the subscribers of the Device Protection Program who have signed up If the object involves a DPPMS, the DPPMS may improperly execute the claim. The MS may provide subscriber profile data associated with the subscriber to the Device Protection Program. If the object is not included, the subscriber must If you are enrolled in a device protection program, your claim may be improperly defaulted.

[0096] Thus, various embodiments of the present disclosure provide real-time third-party device management. configured to verify subscriber registration status with the system, via the DPPMS; , COMPUTER PROGRAM PRODUCT, AND SYSTEM FOR SUBSCRIBER REGISTRATION MANAGEMENT - Patent application Specifically, some embodiments of the present disclosure may send a registration status request to a third-party device. the third-party device management system and the third-party device management system Receive a registration status response data object and the third-party registration status The response data object is analyzed to determine the third-party registration status associated with the subscriber. configured to identify a status or subscriber identifier data object in real time Additionally, some embodiments may include a method for identifying a third party registration status. Therefore, the present disclosure provides a method for initiating a system synchronization event based on the received signal. The form is to prevent inappropriate communication between the DPPMS and one or more third-party device management systems. Provides a solution to synchronization.

[0097] Unlike traditional server-client or master-slave architectures, DPP MS separates control of data between network systems. DPPMS is a previously stored or other third-party devices networked with DPPMS Do not automatically trust data previously stored by the management system. Due to the nature of data transmissions, certain transmissions from third-party device management systems Trusted and untrusted by DPPMS, DPPMS subsystems, or other third-party devices It can be used to update the management system.

[0098] In addition, due to the nature of receiving batch transmissions, the system may not be able to process outstanding actions. processing resources based on the volume of transactions (e.g., claims, enrollment management request data objects, etc.) During batch transmission, outstanding actions may be queued for processing. However, there are still outstanding actions in each action queue. The maintenance action process instance configured to handle the There may not be enough resources allocated to process the outstanding actions. The waiting time for the DPP MS may function inefficiently. Similarly, in some situations, action keys When the queue length is short, the action queue may be allocated more processing resources than necessary. This situation can lead to wasted processing resources and overall system inefficiency. leads to.

[0099] Thus, various embodiments of the present disclosure may include one or more action cues associated with the action cues. a method for utilizing a scaling service for managing process instances of Some embodiments of the present disclosure relate to computer program products, and systems. Based on the queue length and the identified queue relationships, the action to be taken is determined. For example, some embodiments may be configured to update the queue instance set. Identify the maximum queue relationship based on the queue length and queue length maximum threshold, and a small number of processors configured to process outstanding actions stored in an action queue. Executes a new action process instance containing at least one processing thread. This updates the set of action process instances to be executed. Alternatively, some embodiments may determine the queue length based on the queue length and the queue length minimum threshold. and based on the minimum queue relationship, determine the action process to be performed. Selected action process instances to be executed from the process instance set By terminating, the set of action process instances to be executed is updated. Therefore, embodiments of the present disclosure provide a solution to DPPMS processing resource inefficiencies. provide.

[0100] In addition to this, transmissions between the DPPMS and third-party systems may fail. Such transmission failures may include loss of connection, power outages, or other technical and / or communications infrastructure. The DPPMS will report transmission errors in response to failed transmissions. Without a robust means of handling received transmission errors, the DPPMS Continues to lose sync with and / or become ineffective with any of the following third-party device management systems: It can function efficiently.

[0101] Thus, various embodiments of the present disclosure provide a method for preventing failures to third-party device management systems. In response to a failed transmission, the DPPMS provides a robust method for handling received transmission errors. Some embodiments relate to a method, a computer program product, and a system for: receiving a transmission error, identifying an error classification associated with the transmission error, and and configured to identify a set of error handling instructions associated with the error handling instruction. The instruction set includes at least one error handling event and includes an error handling instruction set. Represents an error handling protocol that executes and initiates at least one error handling event. In some embodiments, the error classifications are "retryable error" classification and "escalation error." The error classifications are from a set of identified error classifications that may include the "error classification" classification. A typical embodiment may include, if a transmission error is classified as a retryable error, at least: If a transmission error is classified as a retryable error, it must be at least equal to the maximum retry threshold. Identifying a number of retry attempts; and determining a relationship between a maximum retry threshold and the number of retry attempts. determining a retry relationship between the two nodes and determining that the retry relationship satisfies a maximum retry threshold; determining a request retry time; and determining whether a failed transmission has occurred after the request retry time has elapsed. and adding the received packet to a request queue for retransmission after the packet has been received. Additionally or alternatively, exemplary embodiments may further include a method for determining whether a transmission error is an escalation error. configured to add transmission errors to an escalation queue if the Therefore, embodiments of the present disclosure improve DPPMS error handling.

[0102] As mentioned above, the DPPMS is associated with one or more device protection programs. Manage subscriber enrollment and billing associated with one or more device protection programs For example, subscribers to a device protection program may be able to manage damaged, lost, or You may file a claim for a stolen or otherwise affected subscriber device. In some circumstances, the charges may be fraudulent. For example, the subscriber may If the claim is valid, the claim will be processed by the corresponding device. It may be implemented in conjunction with a protection program (e.g., a replacement device is provided to a subscriber). However, if the billing is fraudulent (e.g., the subscriber has access to the device), If the claim is received, the DPPMS should not fulfil the claim. or may utilize information that is known at the time the claim is processed, but such information may be It may be insufficient to enable the DPPMS to determine whether it is fraudulent.

[0103] Thus, various embodiments of the present disclosure may include a method for generating a set of instructions in response to receiving a request. A method, computer program product, and system for implementing an anti-fraud protocol including The system of some embodiments provides a method for managing a device based on real-time device information. and an anti-tamper protocol including an instruction set for at least one anti-tamper event. In some embodiments, the system identifies a subscriber device associated with the claim. For example, some embodiments may Retrieves information associated with the device location application and The application receives the subscriber device location when the user accesses the application. In an embodiment of the system, the anti-tamper protocol is configured to: For example, a third-party device management system may send a request to a subscriber associated with the request. to determine whether the system has attempted to locate a subscriber device associated with the Real-time device location to get the latest device location and application usage In some embodiments, the system includes at least a real-time device Making informed fraud determinations (e.g., whether a claim is fraudulent or not) (determining the

[0104] definition As used herein, the terms "data," "content," "information," and and similar terms may refer to capturing, transmitting, receiving, displaying, and may be used interchangeably to refer to data that can be called and / or stored. Therefore, use of such terms should be taken to limit the spirit and scope of the present disclosure. Furthermore, a computing device may not When described herein as receiving data, the data may be received by another computing device. The information may be received directly from the device or, for example, from a network, referred to herein as a "network." may include one or more servers, relays, routers, network access points, may be received indirectly via one or more intermediate computing devices, such as a base station Similarly, it will be understood that transmitting data to another computing device When a computing device for performing the processing is described herein, the data may be transferred to another computer. The information may be transmitted directly to a computing device or may be transmitted to, for example, one or more servers, relays, or one or more intermediate computers, such as a router, network access point, or base station It will be appreciated that the information may be transmitted indirectly via a mobile device.

[0105] The term "device protection program" refers to one or more user devices (e.g., This refers to an indemnification or protection program for a Subscriber Device (as defined in this subsection). The Protection Program responds to damage, failure, and / or loss of a subscriber device by Device Protection Programs may facilitate device replacement, repair, or other fulfillment options. is a service where subscribers subscribe at a fixed rate at predetermined intervals (e.g., monthly or yearly). Repair, replace, or otherwise modify the Customer Device to restore it to working condition In some cases, you may be able to file a claim to replace the device. At , our Device Protection Program is a primary or supplemental insurance, extended warranty, or device In some embodiments, the system may include other compensation for potential loss or damage of the The Device Protection program can insure multiple devices associated with a single user. This can be done.

[0106] The term "Subscriber Device" refers to a device that is enrolled in the associated Device Protection Program. or electronic computing devices associated with a currently registered user. In some embodiments, a subscriber device The DPPMS Management Identifier, International Mobile Equipment Identifier (IMEI), serial number, and subscriber device, including but not limited to, the subscriber identity module (SIM) number; An example of a subscriber device is a device The following devices are associated with the protection program: personal devices, entertainment devices, Enterprise devices, mobile phones (smartphones, etc.), personal computers, Laptop computers, tablets, consumer electronics, network equipment, automobiles, etc. Contains one of the following:

[0107] The term "Subscriber Identifier Data Object" refers to a device that subscribes to the Device Protection Program. The specific subscriber profile data objects and / or device protection profiles A text string containing a unique identifier associated with a particular device subscribed to the program. Refers to a string, number, code, or other data type. The object is a specific access to the device protection program associated with a particular subscriber device. An alphanumeric string associated with a subscription. The customer identifier data object is an IMEI, an Internet Protocol address (IP or IP number), other device identifiers, randomly generated numbers and / or alphanumeric characters The at least one from the group including a unique identifier of a character, etc. In the above, the subscriber identifier data object further includes:

[0108] The term "Subscriber Information" refers to the Subscriber Information associated with a particular Device Protection Program. Device protection program management system associated with the device and / or subscriber user. Subscriber information refers to data or information that can be used by the system. The data object, subscriber name, subscriber contact information, etc. , subscriber information is associated only with a particular subscriber device or is associated with a particular group of devices and the corresponding subscriber user (e.g., subscriber device Any information regarding the human owner and / or controller of the device(s) In some such embodiments, the subscriber device does not include any information associated with the subscriber device. The received billing data object identifies the user associated with the subscriber device. In another exemplary embodiment, the subscriber information may require supplemental information to A subscription that uniquely identifies the subscriber and / or subscriber device associated with the program Contains a user identifier data object.

[0109] The term "subscriber profile data object" refers to a user or a particular subscriber Stored information containing information about your device and its associated enrollment in a device protection program. In some embodiments, a subscriber profile data object The request consists of an entity or username, one or more contact information identifiers (e.g., email address), , phone number, address, etc.), device type, device identifier (e.g., IMEI), One or more of the following: a subscriber identifier data object, a subscription identifier, or other subscriber information The subscriber profile data object contains the subscriber profile data object. object (e.g., a subscriber device associated with a subscriber profile data object) Claim data object (claim data object requesting repair and / or replacement of Contains information for analysis when a data object is received. Some data objects identify only a subscriber device (or a subscriber device group). In some embodiments, to facilitate processing, a request object associated with the submitted claim data object is Associated additional information may be required. For example, in some embodiments, billing data In situations where the object is submitted through a claims processing call center system, at least also requires the billing data object to provide associated invoice and shipping information for processing. Additionally or alternatively, in some embodiments, ,The billing data object is submitted via a web portal (e.g., a client In the situation where the subscriber device is Information identifying a specific owner, billing information, shipping information, and / or additional billing information may be transmitted via a web portal for processing.

[0110] The term "enrollment management request data object" refers to a subscriber profile data object. Data received by the device protection program management system to modify the An exemplary registration management request data object is In the system management system, a new subscriber profile is created that is associated with the selected device protection program. represents a request to create a profile data object. The registration management request data object is a "registration subscription request data object." This includes a "new subscriber" associated with the selected device protection program. In some embodiments, the registration subscription request data object represents a request to register a The object must have at least: (1) a device identifier (e.g., IMEI, MSN, MEI) D), and / or (2) a subscriber profile identifier (e.g., account number) and use such information to process future submitted claim data objects (singular or Identifying a specific subscriber profile data object for processing In another example, an exemplary registration management request data object may include a device protection program. The program management system will then display the registered device associated with the selected device protection program. Represents a request to cancel a DPPMS subscriber profile data object. For example: In some embodiments, an exemplary enrollment management request data object may include a registration cancellation request. The device protection program includes a file request data object, which is associated with the selected device protection program. In some embodiments, the registration The management request data object identifies the corresponding subscriber profile data object. In some embodiments, the enrollment management request data object includes: Contains subscriber information that identifies the corresponding subscriber device.

[0111] The terms "Device Protection Program Management System" and "DPPMS" refer to controlled by a provider entity and configured to facilitate device protection programs. A hardware and / or software system, or a combination of hardware and software This refers to a combination of software and communication and synchronization with one or more third-party systems. The device protection program management system may be configured to manage the device protection program. Subscriber registration of the DPPMS subscriber profile data object associated with the program; Billing fraud prevention and / or device protection associated with the Device Protection Program The program may perform one or more of the following: fulfillment of subscriber claims associated with the program. In an embodiment, the device protection program management system includes at least an enrollment management subsystem. In some embodiments, the system includes a fraud prevention subsystem, a fulfillment subsystem, and a The Device Protection Program Management System is a payment subsystem and / or policy subsystem. In some embodiments, the DPPMS includes a payment subsystem or In some embodiments, D The PPMS is a system that manages the Enrollment Management Subsystem, the Fraud Prevention Subsystem, or the Fulfillment Subsystem. One of the subsystems includes a payment system. In some embodiments, A PMS can be an enrollment management subsystem, a fraud prevention subsystem, or a fulfillment subsystem. One of these subsystems includes a policy subsystem or equivalent service.

[0112] The term "DPPMS Subscriber Profile Data Object" refers to the DPPMS, D The subscriber profile stored in the subsystem or associated data store within the PPMS. file data object, or equivalent information. In an exemplary embodiment, one or more The database stores DPPMS subscriber profile data objects in a specific format. The stored information set is stored by a user or a client device. Contains information about the subscription to the device protection program associated with the device.

[0113] The term "third-party device management system" refers to third-party information and and / or any hardware managed by a third party that is configured to provide the Service. In some exemplary aspects, the term refers to hardware and / or software systems. For example, the third-party system may provide at least one or more subscriber profile data objects. Store, retrieve, access, and / or otherwise process the object In some embodiments, third-party profiling is configured to manage The system uses third-party data to manage subscriber profile data objects. In some embodiments, the third party device management system is a subsystem within the device management system. The third-party device management system uses third-party subscriber profile data objects. Store, retrieve, access, and / or share with others information equivalent to In some embodiments, the DPPMS may be configured to manage the application By using Application Programming Interfaces (APIs), third parties Device management system or to communicate with many third-party device management systems It is configured as follows.

[0114] The term "Third Party Subscriber Profile Data Object" means a third party a subscriber profile data object stored in a device management system or the like An exemplary third-party subscriber profile data object is When a new user device is purchased, the user may purchase device insurance through the mobile carrier. When you enroll in a carrier subscriber profile maintained by your mobile carrier, It is a profile data object.

[0115] In some embodiments, multiple systems may use a single subscriber profile data object. Multiple instances of a project or multiple instances associated with a subscriber or subscriber device It should be understood that the profile data objects stored in the In an embodiment, the DPPMS and the third party each have a specific subscriber or subscriber device. the profiles associated with the device, e.g., multiple protection programs associated with the same device. (e.g. warranties and extended warranties provided by the manufacturer or through DPPMS) In some implementations, In this situation, the third party may provide subscriber profile data objects that are unrelated to the protection product. may store information about a service providing wired or wireless communication services to a subscriber device. carrier or retailer that stores customer information associated with a subscriber device). Additionally, many systems may have many instances of a single subscriber profile data object. In some embodiments that store instances, each instance may be in the format of the other instances. For example, in an exemplary embodiment, the DPPM S is the DP associated with the selected subscription to the Device Protection Program. Stores PMS subscriber profile data objects and allows third-party device management systems The system is connected to a third party with the same subscription to the Device Protection Program. In this exemplary embodiment, the party subscriber profile data object is stored. , the DPPMS subscriber profile data object is a first profile format The third-party subscriber profile data object may be stored according to the second The profile may be stored according to the profile format.

[0116] The term "Third Party Registration Status" refers to a Third Party Subscriber Profile Data object that indicates whether it exists in a third-party device management system. In some embodiments, third-party registration status refers to A specific third-party profile associated with a specific identity (e.g., subscriber information) Indicates whether the device is present in a third-party device management system.

[0117] The term "Third Party Enrollment Status Request Data Object" is used in the DPPMS specific subscriber identifier data object sent by the and (b) providing a third party with a stored profile data object associated with the object. Specifies the data or information that a device management system is required to identify if it contains Certain third-party registration status request data objects are The device management system stores the associated third-party subscriber profile data object. query a third-party profile database for the object. In this form, numerous attempts have been made to transmit a third-party registration status request data object. are made, with each attempt being identifiable based on the number of attempts associated with the transmission. (e.g., first third-party registration status request data object, second third-party Party Registration Status Request Data Object, Third Party Registration Status request data object, etc.

[0118] The term "Third Party Registration Status Response Data Object" refers to a Third Party Responds with a third-party registration status request data object containing the third-party registration status and data sent to DPPMS by third-party device management systems. In some embodiments, the third-party registration status response data object The object is a third-party subscriber profile data object, or a third-party Contains equivalent information associated with the Tee Registration Status Request data object.

[0119] The term "Third Party Subscriber Registration Request Data Object" is used by the DPPMS. and sent to the third-party device management system system based on the third-party subscriber registration request data object. Data configured to create or update a subscriber profile data object In some embodiments, the third party subscriber registration request data object The object contains subscriber information and provides the third-party device management system with to create or update a third-party subscriber profile data object based on the In some embodiments, a third party subscriber registration request data object is transmitted. Multiple attempts are made to transmit the data, each of which is identifiable based on the number of attempts associated with the transmission. (e.g., a first third-party subscriber registration request data object, a second Third-party subscriber registration request data object, third-party subscriber registration request data object, etc.

[0120] The term "Third Party Subscriber Registration Response" refers to a Third Party Device Management System Determines whether the system successfully created the third-party subscriber profile data object. 3. The third party device responds to a third party subscriber registration request data object indicating This refers to the data or information sent by the Device Management System to the DPPMS.

[0121] The term "Third Party Subscriber Cancellation Request Data Object" refers to the DPPM S to the third-party device management system, which then Cancel the subscription by deleting the subscriber profile data object. In some embodiments, a third party may provide a third-party service. The subscriber registration request data object contains subscriber information and is used by the third-party device management The system contains a third-party subscriber profile data object associated with the subscriber information. Identify and eliminate the object.

[0122] The term "Third Party Subscriber Cancellation Response" refers to a Third Party Device Management The system successfully cancels the third-party subscriber profile data object. In response to a third-party subscriber registration request data object indicating whether refers to data or information transmitted by a Party Device Management System to DPPMS .

[0123] The term "Third Party Registration Management Request Data Object" generally refers to a third party Third Party Subscriber Registration Request Data Object, Third Party Subscriber Cancellation Request Data Object Refers to an object, or the data or information equivalent of any request.

[0124] The term "Third Party Registration Management Response" generally refers to a Third Party Subscriber Registration Response. a response, a third-party subscriber cancellation response, or the equivalent data of either response or Refers to information.

[0125] The term "transmission error" refers to an incomplete transmission between the DPPMS and a third-party system. , refers to unreadable, corrupted, or inaccurate communication. An exemplary transmission error is a DP Incomplete or corrupted third-party software between the PMS and the third-party device management system Another exemplary transmission error is a DPPM Incomplete third-party subscriber conversations between the S and third-party device management systems Another non-limiting example of a transmission error is a third-party System errors (e.g., a third-party system receiving the request and / or (indicating that the system is unable to respond to a call), protection program duplication error (e.g., subscriber registration When a registration request is sent in association with a device protection program, the subscriber is already Indicates that the device is enrolled in the Device Protection Program or Associated Device Protection Program. request processing errors (e.g., the transmitted request data object cannot be processed at this time) could not be completed), and / or a request timeout error (e.g., A response signal associated with a request data object is received for longer than the request timeout threshold. (indicating that the

[0126] The term "Third Party Subscriber Cancellation Response" refers to a Third Party Device Management The system successfully cancels the third-party subscriber profile data object. In response to a third-party subscriber registration request data object indicating whether refers to data or information transmitted by a Party Device Management System to DPPMS .

[0127] The term "Third Party Subscriber Registration Error" refers to a Third Party Subscriber Registration Request Data The transmission of the data object to the third-party device management system is unsuccessful. Third-party subscriptions that are missing, incomplete, or otherwise unsuccessful. Data or information received by the DPPMS in response to a User Registration Request Data Object Refers to news.

[0128] The term "Transmission Error Data Object" refers to a previously transmitted error data object to a third-party system. Received by the DPPMS in response to a transmission error, indicating that an attempted transmission failed. In some embodiments, the DPPMS refers to data or information stored in a third party database. Receiving a transmission error in response to transmitting a registration status request data object In some embodiments, the DPPMS may include a third party subscriber registration request data object. In some embodiments, the method further includes receiving a transmission error data object in response to the transmission error data object. The transmission error occurred for a specific third-party registration status request data object that failed. or information identifying the particular third-party subscriber registration request data object that failed. In some embodiments, the transmission error data Objects are used when sending information to a third-party system or In response to the DPPMS detecting a transmission error when receiving information from the system , generated by the DPPMS. For example, when a third-party system communicates with the DPPMS If the message is incomplete or insufficient information is received, A transmission error data object may be created.

[0129] The term "error classification set" refers to one or more classes to which a received error can be associated. Refers to predefined error classifications. An exemplary set of error classifications is "Retryable Errors" " and "Escalation Errors". In certain instances, as retryable errors The identified error is processed by a first set of error handling instructions (e.g., determining a request retry time, subsequent transmission attempts of a failed request after the retry time has elapsed), Escalation errors are associated with a second set of error handling instructions (e.g. For manual intervention, error reports can be sent to specific subsystems of the DPPMS or to third parties. (transmitted to the service system).

[0130] The term "error classification data object" refers to the error type and the error handling protocol. The corresponding error handling instruction set representing the call received by the DPPMS is identified. In an exemplary embodiment, a particular error classification is: Identifies retryable errors, and the second error classification identifies escalation errors. .

[0131] The term "Request Retry Time" is used by DPPMS to provide a service to third-party device management systems. Third-party registrations are notified in response to a retryable error received after a failed transmission to the system. Status Request Data Object or Third Party Subscriber Registration Request Data Object This refers to the amount of time that must elapse between subsequent transmission attempts, such as a ping.

[0132] The term "retry attempts" applies to both DPPMS and third-party device management systems. In an exemplary embodiment, The DPPMS tracks the number of retry attempts and identifies the number of failed transmissions using the number of retry attempts. It becomes possible to distinguish

[0133] The term "maximum retry threshold" refers to the maximum number of retries allowed in response to a particular retryable error. In an exemplary embodiment, the DPPMS is configured to Determinable retry thresholds to prevent a missed transmission from being attempted to be retransmitted beyond a maximum retry threshold. Set a maximum threshold (e.g., 10 retry maximum).

[0134] The term "retry relationship" refers to a comparison or other relationship between the number of retry attempts and a retry threshold. In some embodiments, the retry relationship refers to a "retry relationship result data object" ", which is related to electronically managed data, e.g., when a retry relationship is satisfied. Refers to a Boolean data value that indicates whether the DPPMS has determined that some In an embodiment, the retry relationship represents a comparison between the retry attempt count and the retry maximum threshold. The corresponding retry relationship result data object is embodied by the "retry max relation" , the retry attempt count is less than the maximum retry threshold or is less than or equal to the maximum retry threshold. In another specific example, the retry relationship is , which is embodied by a "retry minimum relation" that represents a comparison between the retry attempt count and the retry minimum threshold. The corresponding retry related result data object is generated and the retry attempt count is The relationship is satisfied if it is greater than the maximum threshold or greater than or equal to the retry maximum threshold. It will show that:

[0135] The term "Error Handling Instruction Set" refers to an attempt to provide a third-party device management system One or more of the following the DPPMS executes in response to receiving an error in response to a detected transmission: Refers to computer code instructions and / or electronic data that represent the actions of some In this embodiment, different sets of error handling instructions are associated with different error classifications. In some embodiments, the error handling instruction set may include a single retry of a failed transmission. A retry protocol is defined that includes these attempts. For example, in an exemplary embodiment, The retry time is determined by an exponential backoff, with the requested retry time for subsequent transmission attempts being longer than the previous is determined by doubling the requested retry time (e.g., before retransmission attempt number 1). Wait 5 minutes, wait 10 minutes before retransmission attempt number 2, wait 20 minutes between retransmission attempts number 3 (and wait 40 minutes between retransmission attempts of 4). Alternatively or additionally, The error handling instruction set includes determining a maximum retry threshold. In an embodiment, the DPPMS adjusts the maximum retry threshold according to the identified error handling instruction set. and configured to track the number of retry attempts, and In the exemplary embodiment, the retry relationship can be determined based on The PMS is configured to determine whether the retry relationship meets the maximum retry threshold. For example, in an exemplary embodiment, the retry relationship is: If they are equal, the maximum retry threshold is met. The protocol is variable and depends on the DPPMS and / or third-party systems. In some embodiments, the server load may be Use it to determine if either system is saturated or if The error handling protocol determines the action to be taken depending on whether the response time is too long or not. In some embodiments, the third party system may implement an error handling protocol. The DPPMS may be instructed to set or change the value.

[0136] The term "error handling event" refers to an error that is initiated as part of a set of error handling instructions. Refers to data transmission, data conversion, or other actions performed by the DPPMS. In this embodiment, a particular set of error handling instructions is provided for a retransmission received in response to a failed transmission. Triable errors (e.g., failed third-party subscriber registration request data object an error handling program for responding to a third-party subscriber registration error received in response to The error handling command sequence embodies a number of error handling events that define the error handling protocol. The set consists of the following error handling events: [1] Identifying the maximum retry threshold [2] [3] Identifying the number of retry attempts; [4] Identifying the number of retry attempts based on the number of retry attempts and the maximum retry threshold. Determine the row relation [4] Determine whether the retry relation meets the maximum retry threshold (e.g., comparing whether the number of retry attempts is equivalent to an identified maximum retry threshold) (by comparing the [6] If a retryable error is encountered, or if the error is It means to add to.

[0137] The term "escalation queue" refers to the process of escalating according to an error handling instruction set. Stored errors, such as escalated errors and / or retryable errors In some embodiments, the escalation queue refers to a set of transmission errors. In some embodiments, the DPPM is stored in a data store associated with the PMS. S is an escalator configured to store one or more third-party transmission errors. In some embodiments, the escalation queue is The DPPMS transmits third-party transmission errors or equivalent information to one or more third-party Storing third-party transmission errors until a determined time for transmission to an error processing system In some embodiments, the escalation queue allows a human operator to Third-party transmission errors remain until you perform the manual action associated with the third-party transmission error. Remember.

[0138] The term "Error Escalation Request" refers to the request made by the DPPMS to processing subsystem, the error handling system associated with the DPPMS, or a third-party This refers to data or information sent to a service error handling system. The DPPMS may execute and / or The error handling event triggers the error escalation as part of the initiated set of error handling instructions. In some embodiments, the DPPMS transmits a retry request. If the row maximum threshold is equal to the specified value, an error is generated in the error handling event as part of the error handling instruction set. Transmit a user escalation request.

[0139] The term "Third Party Case" refers to a device instance associated with a subscriber device. generated, retrieved, and / or otherwise obtained by third-party systems in response to an incident For example, a user may report a loss incident (e.g., The system may report the loss or theft of the user device to a third-party system. In this system, the third-party system is associated with the subscriber device and the loss incident. In some embodiments, the third-party case The case includes "Third Party Case Information." Third Party Case Information is a refers to information stored in or associated with a third-party case In an exemplary embodiment, the case information includes a third-party case identifier, a subscriber identifier data, and a data object and / or subscriber device identifier, subscriber name, subscriber reporting type In addition, in some embodiments, Third-party case information is used when a third-party system reports a device incident. The subscriber authentication information is used to verify that the user is authenticated.

[0140] The terms "billing data object" and "billing" are used in conjunction with the Device Protection Program. Requests for coverage for subscriber devices in response to associated loss or policy incidents. Electronic Management Information (EMI) containing information sets generated or received by the DPPMS associated with a request. In some embodiments, the billing data object refers to at least one ) device identification information and / or corresponding sub-devices associated with a particular subscriber device; (2) the subscription profile, (3) the claim date, and (4) the timestamp of the loss. Type (e.g., loss, theft, accidental damage, mechanical failure, etc.). In this form, a claim data object is (1) associated with a corresponding third-party case; and / or (2) additional subscription information. , subscription profile, or subscription profile identifier In some embodiments, the billing data object is transmitted via the DPPMS to: For example, a web portal accessed by a user via a client device In some embodiments, the billing data object is received directly via the DPPM. S receives user case information associated with the received third-party case information. The billing data object is generated after the subscriber device is compensated, repaired, or replaced. This may be associated with a request for exchange.

[0141] The term "billing information" refers to information generated in connection with the Device Protection Program. Additionally, in some embodiments, billing information refers to data related to a bill. information associated with the claim, the subscriber associated with the claim, the subscriber information associated with the claim In an exemplary embodiment, the billing information includes the subscriber device associated with the billing. At a minimum, the system must include third-party case information received from the third-party system. nothing.

[0142] The term "claims processing protocol" refers to the procedures implemented to execute, process, or fulfill a claim. In some embodiments, the DPPMS, or DP The fulfillment subsystem of the PMS is responsible for processing claims associated with claims and / or claim information. Additionally or alternatively, some In an embodiment, the DPPMS (e.g., the fulfillment subsystem of the DPPMS) The system is configured to execute the protocol.

[0143] The term "Device Information" refers to a Subscriber Device, one or more components of a Subscriber Device, and / or data, information, etc. associated with the use of the Service Component and / or Subscriber Device. Examples of device information include one or more of a device identifier, serial number, component component identifier or serial number, device model or manufacturing information. Further examples of device information include location data associated with the subscriber device, Application access information (e.g., the last recorded run of a particular application) , subscriber device settings, etc.

[0144] The term "real-time" refers to the desired time or immediate or near-immediate delivery of data. Depending on the requirements of the use (e.g., within a certain time frame, e.g., within 5 seconds, within 1 minute, etc.), In some embodiments, the device information refers to obtaining real-time information. In some embodiments, the D PPMS retrieves real-time device information from third-party device management systems However, third-party device management systems (1) provide real-time communication with subscriber devices; configured to identify real-time device information by contacting the 2) At a time prior to this, for example, a third-party device management system was connected to the subscriber device. Real-time device information from subscriber devices when associated billing notifications are issued The method may be configured to acquire and store some or all of the information.

[0145] In some embodiments, the real-time device information includes a device identifier, a MAC address, This includes real-time captured device identification information such as address, IP address, etc. Alternatively or additionally, in other embodiments, the real-time device information includes: Refers to information associated with the usage of a subscriber device (e.g., when one or more apps are active on the device). whether one or more apps are accessed, when one or more apps are accessed, and (e.g., whether more than one location setting was enabled).

[0146] For example, in some embodiments, the device location application may Accessible from the user device, the device location application and configured to provide a location associated with the visitor device. In some embodiments, the real-time device information is provided when a user accesses a third-party device. When you submit an incident to the Device Location Management System or DPPMS Device location application indicating whether the application was enabled In some embodiments, the lost device application includes a second The lost device application is accessible from the user device and The device may be unable to access some or all of the features associated with the subscriber device. and / or display information associated with the subscriber (e.g., contact information) By setting a device lost status to indicate that the device is lost, and / or set device lost status to indicate that the subscriber device is not lost Restore the device lost application status and associated functionality by Thus, in some embodiments, real-time device information is , including the device loss status associated with the device loss application. In some embodiments, a lost device application and a device location application The application may be delivered via a single software application, web module, etc. Please understand that this is provided.

[0147] Additionally or alternatively, in some embodiments, a real-time device The information may be associated with the subscriber device and / or associated subscriber. This refers to information related to a previous incident reported by a real-time The device information is the subscriber device and its associated open remediation list (subscriber device the remaining list of incidents, and / or or previous replacement status (related to a third-party device management system or DPPMS) (Indicating whether the subscriber device has previously been replaced, such as via linked billing) nothing.

[0148] The term "Fraud Prevention Protocol" refers to the process that DPPM performs in response to receiving billing information. S or one that a subsystem within the DPPMS (e.g., fraud prevention subsystem) executes Anti-fraud protocols are designed to detect fraudulent billing information. Specific examples of anti-tamper protocols include one or many actions. Includes fraud prevention events.

[0149] The term "Anti-Fraud Event" refers to any data transmission, data transformation, or DPPMS or The subsystem within the DPPMS (e.g., the anti-fraud subsystem) implements the anti-fraud protocol. Examples of specific anti-fraud protocols include: fraud prevention events, i.e., [1] the latest device location from the subscriber device; Obtaining real-time device information associated with application usage and [2] whether the real-time device information is within the acceptable device discovery threshold. In an exemplary embodiment, the fraud prevention event includes identifying the subscriber device. In real time, from the system linked to the device or subscriber device, Get the latest usage information for software applications that are configured to locate , determining a relationship between the latest usage information and the device discovery threshold, and Identifying whether the obtained usage information meets a device discovery threshold.

[0150] The terms "action process" and "action process instance" refer to Fulfilling certain types of incoming requests transmitted from third-party systems or other by the DPPMS or a sub-module within the DPPMS configured to process microservices, software module instances, etc. that are run or managed by An example action process is a third-party action process, such as a mobile carrier system. software configured to process one or more new registration requests received from a network system; In some embodiments, the action process processes one or more outstanding actions stored in one or more action queues It runs in one or more process threads configured to

[0151] Many action process instances ("action processes") may be running at any given time. Therefore, the term "number of instances running" refers to the number of instances that can be executed. This represents the total number of action processes that will be executed.

[0152] "Process thread(s)" or "Thread(s)" The term refers to a single computing instance or many computing instances. a processor, or one or more processing modules within a processor. simultaneously on one or more processors distributed across one or more servers associated with the It refers to one or more streams of tasks that are executed simultaneously or semi-simultaneously. The node is configured to complete a registration request transmitted from a third-party system. In some embodiments, the action process to be executed is transmitted to the action process. In some embodiments, the process includes one or more process threads for completing received requests. ,Action Process is a process that can be executed in association with a specific action process. This is associated with the "Maximum Process Thread Count" which represents the total number of process threads. The term "process thread count" refers to the number of times a particular action has been performed by a process or Refers to the total number of process threads that are otherwise associated with a particular action process.

[0153] The term "action queue" refers to a queue that is processed by one or more action processes. Unfulfilled request sets received by one or more third-party systems that will be An example action cue is provided by a third-party device management system, etc. Configured to store registration requests transmitted to the DPPMS by third-party systems The action queue indicates the number of pending requests in the corresponding action queue. Associated with the queue length it points to.

[0154] The term "queue relationship" refers to a specific mathematical or A queue relation refers to a comparison by a queue relation result data object. This is related to the "data" that is managed electronically, e.g., queue relationships. Refers to a Boolean data value that indicates whether the DPPMS has determined that the condition is met. In this case, the queue relation is the "max queue relation" which represents the comparison between the queue length and the queue length maximum threshold. " and the queue length is less than or equal to the maximum queue threshold. The corresponding cue relation result data object indicates that the relation is satisfied if In another particular example, the queue relationship is the ratio between the queue length and the queue length minimum threshold. The minimum queue relation is embodied in the comparison, and the queue length is greater than the minimum queue threshold. The corresponding cue relation result indicates that the relation is satisfied if the cue threshold is equal to or greater than the minimum cue threshold. The data object will show:

[0155] The term "queue length threshold" refers to the time when the queue length of a particular action queue is satisfied. When satisfied, triggers DPPMS to update the action process instance set In the specific example, the queue length threshold is the "maximum queue length threshold" and the action It represents the maximum queue length within which the set of process instances must be updated. In an embodiment, if the maximum queue relation indicates that the queue length exceeds a queue length maximum threshold, The maximum queue relation satisfies a queue length maximum threshold. In some embodiments, the maximum queue relation If a queue manager meets the maximum queue length threshold, such as by exceeding the maximum queue length threshold, The action process instance is executed by the DPPMS and / or In the specific example, the queue length threshold is The minimum length threshold is the minimum length that must be met before the action process instance set is updated. In some embodiments, the minimum queue relationship represents a small queue length. The minimum queue relation satisfies the queue length minimum threshold if it represents a value less than the small threshold. In some embodiments, the minimum queue relationship is when the queue length is less than a minimum queue length threshold. For example, if the queue length minimum threshold is met, the selected action process instance is executed. The action performed is terminated from the process instance set.

[0156] In some embodiments, the queue length threshold, the queue length minimum threshold, and / or the queue length The maximum thresholds are each determined, identified, or otherwise established numbers (e.g., For example, 20). In some embodiments, the queue length maximum threshold and the queue length minimum threshold are In some embodiments, the queue length maximum threshold and the queue length The minimum thresholds are set to unequal numbers. For example, in certain embodiments, the queue length minimum threshold The value must be less than the queue length maximum threshold (for example, a queue length minimum threshold of 20 and a queue length minimum threshold of 100). In some embodiments, all outstanding actions in the action queue are When the action is resolved, the action process instance that is executed is scaled down. As shown, the queue length minimum threshold is zero.

[0157] The term "Action Process Instance Count Maximum" refers to the maximum number of processes that can be initialized and run at one time. In an exemplary embodiment, each action The transaction process is associated with the number of API transactions that are performed and The maximum action process instance count is the maximum count of all executed action processes or or associated with a particular action queue or with a particular type of outstanding action The number of API transactions allowed per unit time for all actions performed. The maximum number of sessions is set according to the

[0158] The term "Action Process Instance Count Minimum" refers to the number of processes that are initialized and executed at one time. This refers to the minimum number of action processes that can be executed at a time. Determines the minimum process instance count. In some embodiments, the action The process instance count minimum is predetermined.

[0159] The term "maximum process instances relationship" refers to the number of instances that are executed and the action that is performed. A mathematical or algorithmic relationship between the maximum process instance count threshold and the The maximum process instance relationship refers to a comparison between electronically managed data, e.g. Indicates whether the DPPMS determined that the maximum process instance relationship is satisfied Associated with "Maximum Process Instance Relationship Result Data Object" that points to a Boolean data value In some embodiments, the maximum process instance relationship is The number of instances that are displayed is less than or equal to the maximum action process instance count. If so, the comparison satisfies the maximum action process instance count value.

[0160] The term "minimum process instance relationship" refers to the number of instances that are executed and the actions that are performed. A mathematical or algorithmic relationship between the minimum and maximum process instance count thresholds. The maximum process instance relationship refers to a comparison between electronically managed data, e.g. Indicates whether the DPPMS has determined that the minimum process instance relationships are met Associated with the "Minimal Process Instance Relationship Result Data Object" that points to a Boolean data value In some embodiments, the process instance relationships are associated with the corresponding executed If the number of instances is greater than the minimum action process instance count value, , a comparison that satisfies the action process instance count minimum threshold.

[0161] The term "System Synchronization Event" refers to a third-party subscriber profile data object. Synchronize one or more DPPMS subscriber profile data objects according to the object This is performed by one or more subsystems within the DPPMS or DPPS to For example, in an exemplary embodiment, the DPPMS uses consistency Third-Party Subscriber Profile Data Objects and DPPMs containing information that is not Identifying a subscriber profile data object, and The data object is the information in the third-party subscriber profile data object. configured to synchronize DPPMS subscriber profile data objects based on Alternatively or additionally, in another exemplary embodiment, the DPPMS is Based on the received third-party registration status response data object, the subscriber identity is Cancels the third-party subscriber profile data object associated with the identifier. Identifies the third-party device management system that has been installed and includes a subscriber identifier data object. Cancels the DPPMS subscriber profile data object associated with the object. In some embodiments, a system synchronization event is configured to include one or more registered For example, in some embodiments, the DPPMS may transmit a registration management request. Third-Party Subscriber Registration Request Data Object or Third-Party Subscriber Cancellation Transmitting a request data object to synchronize a third-party device management system In another embodiment, the DPPMS may synchronize one or more subscriber processes during a system synchronization event. Updates a file or subscriber profile for one or more subsystems.

[0162] System Architecture The disclosed methods, apparatus, systems, and computer program products are applicable to a variety of systems. The system architecture may be embodied by any of a variety of devices. For example: The method, apparatus, system, and computer program product of the exemplary embodiments are one or more devices, such as a customer device, a third-party device, and one or more third-party devices One of the servers or other entities configured to communicate with the party server The exemplary embodiment may be embodied by the above network devices. This includes a variety of networked devices that operate in addition to or instead of In addition, exemplary embodiments of the methods, apparatus, systems, and / or computers The data program product may be implemented as disclosed herein and connected to a network. Runs on one or more hardware modules or systems, such as one or more servers One or more software modules configured to perform some or all of the operations This can be embodied by

[0163] In this regard, FIG. 1 illustrates a simplified exemplary system in which embodiments of the present disclosure may operate. Specifically, the system includes a device protection program management server. 102 and third-party device management systems 118A to 118C. The party device management system may communicate with the party device management system over a network such as the communication network 116. , may be connected to at least the device protection program management server 102 .

[0164] The device protection program management server 102 is connected to a large number of circuit modules 104 to 114. In some embodiments, each of the modules 104-114 may be associated with a device. The device protection program is implemented by hardware that communicates with the device protection program management server 102. Specifically configured to perform the operations associated with the modules of. In a typical system, some of the modules 104-114 are device protection program managers. a second server or hardware component configured to communicate with the management server 102; It is embodied by software running on the client.

[0165] The device protection program management server 102 includes one or more software and / or Subscription to a device protection program using hardware modules or other means The device may be configured to perform various tasks associated with managing the device options. The device protection program management server 102 is associated with various device protection programs. The subscribers may be configured to store and / or maintain a data store of the subscribers. can be a person associated with one or more devices, or a specific device itself Subscribers and associated registration subscriptions and / or cancellation requests will be processed at the One or more users and / or subscription devices, such as client devices 120 It may be received directly from the device or from one or more third-party servers. The device protection program management server 102 receives a new subscriber associated with a device protection plan. In addition, for example, the device protection program administrator may be configured to register subscribers. The management server 102 is configured to cancel a subscriber associated with a device protection plan. It can be done.

[0166] The device protection program management server 102 is a third-party device management system Registration of third-party subscriber profile data objects, such as 18A-118C and / or one or more third-party device management systems configured for management may be configured to communicate with (e.g., associated with a third-party device management system) Third-party profiling systems or third-party device management Through the system's subsystems). On some systems, the device protection program The management server 102 communicates with a third-party device management system to manage one or more subscriptions. may validate, verify, receive, and / or synchronize registration status associated with a user. For example, the third-party device management systems 118A to 118C are each independently , registration subscription requests, and / or registrations related to one or more device protection programs. Each third party device may receive an associated cancel registration request data object. The device management system may be associated with purchasing and / or securing the device. For example, The third-party device management system includes a device protection program management server 102 and One or more device protection processes performed by an associated provider entity Device vendors and device manufacturers who register users and / or devices in the program , mobile carriers, or other entities.

[0167] The device protection program management server 102 also registers subscriptions. Request Data Object(s) and / or Cancel Registration Request Data Object(s) It may provide synchronization and / or processing of an object(s). For example, The subsystem protection program management server associates each of the subsystems with stored information. and / or communicates with the component to obtain the subscriber profile(s), and / or Corresponding information managed by each subsystem can be synchronized. For example, device protection The program management server 102 may also provide subscriber profile registration data to third party subscribers. together with the customer profile data to payment systems and / or invoice processing systems (as shown in (without exception) to ensure that such information is current and relevant. By synchronizing such systems, the device protection program management server 102 ,The system communicates and,associates with the Device Protection Program when a charge occurs. To ensure that a particular subscriber's registration can be verified. In this regard, the Device Protection Program Administrator The management server 102 and / or the third-party device management system may For the purposes of verifying your enrollment in the program and initiating the performance of the appropriate services, Synchronized data such as:

[0168] New devices or device controllers may be installed through third-party entities. Once subscribed to the Device Protection Program, third-party device management systems The system manages its registrations and allows subscribers associated with the corresponding third parties to register. Therefore, the device protection program management server 1 can be configured to reflect the 02 communicates with each third-party device management system to manage all third-party The system may be configured to maintain a data store of all subscribers registered via the system. In other words, the device protection program management server 102 is a third-party device management system. The subscriber may cancel through a third party by communicating with each of the systems 118A to 118C. In this case, the subscriber data store associated with the device protection program management server 102 You may cancel and / or remove your subscriber from the service and / or third party services. The new subscriber communicates with each of the service device management systems 118A to 118C. When registering through a third-party system, the device protection program management server 102 New subscribers can be added to the associated subscriber data store.

[0169] Examples of processes and operations performed in association with subscriber registration management are further described herein. Therefore, the foregoing description is intended to provide an illustrative overview. and are not intended to limit the scope or spirit of the embodiments of the present disclosure.

[0170] In some embodiments, the DPPMS device protection program management server 102 includes: By means of one or more software and / or hardware modules, Perform various tasks associated with managing billing related to the Device Protection Program. The device protection program management server 102 may be configured to execute, for example, configured to process one or more claims associated with one or more device protection programs For example, a subscriber may utilize a client device to access a third-party system. The device protection program management server 102 may receive the device protection program via the device protection program management server 102 or directly from the device protection program management server 102. Next, the device protection program management server 10 2 is configured to store one or more actions to be performed associated with the claim. The action queue may be maintained.

[0171] The device protection program management server 102 includes modules 104 to 114. Associated with this, the operations described above and further herein may be performed. For example, the registration module 104, or a means for implementing the registration module 104, may include a registration sub-module. The present invention may be configured to perform subscription and / or cancellation. In some embodiments, the registration module 104, or a device that implements the registration module 104, The means by which the device is subscribed is by communicating with one or more third-party device management systems. a self-service server configured to perform operations associated with maintaining a user data store; The recovery framework 110 includes a self-healing sub-module.

[0172] Additionally or alternatively, the fraud prevention module 106 or the registration module The means for implementing rule 104 may analyze the claim and determine the claim, as further described herein. The device may be configured to perform one or more operations to determine whether the device is fraudulent. For example, in some embodiments, the anti-tamper module 106 may implement an anti-tamper protocol. and to perform one or more fraud prevention steps in accordance with the fraud prevention protocol. It is composed.

[0173] Additionally or alternatively, fulfillment module 108 or fulfillment module 1 The means embodying Item 08 may include: For example, in some embodiments, In this embodiment, the fulfillment module 108 responds to the request by associating the device with a protection program. The system is configured to execute one or more fulfillment events associated with the execution of the execution.

[0174] Additionally or alternatively, an error classification module 112, or an error classification The means for implementing module 112 performs one or more operations to identify transmission errors. For example, the device protection program management server 102 may be configured to If the connection to the third-party device management system fails or is lost, the device The device protection program management server 102 may receive a transmission error. Rule 112 identifies an error classification associated with a received transmission error, and / or may perform one or more actions based on the identified error classification. 9 and 10. The error classification module 112 then performs one of the following steps: It can be configured to perform the above operations.

[0175] Additionally or alternatively, a workflow management module 114, or The means for implementing the workflow management module 114 maintains one or more action queues. For example, a workflow management model may be configured to perform one or more operations for Jul 114 will see the action queue for defaulted claims, pending new subscription registrations, Action queue for subscription requests, and pending cancel subscription request data objects In some embodiments, the workflow may be configured to manage a queue of actions. The row management module 114 is associated with managing the corresponding action queue. The system may manage one or more action processes configured to perform one or more actions. In certain embodiments, the workflow management module 114 may include the It may be configured to perform one or more of the operations described below with respect to FIG. 7B.

[0176] In some embodiments, the device protection program management server 102 may include various or It may be associated with one or more other subsystems for special purposes. In an embodiment, the device protection program management server 102 may include a device protection program associated with a registered subscriber. Payment profile, transaction information, and / or other payment processing information or capable of communicating with the DPPMS payment subsystem for managing the DPPMS otherwise associated with the payment subsystem. Additionally or alternatively, In some embodiments, the device protection program management server 102 may Policy profile, policy rules and / or requirement information associated with the subscriber or other DPPMS policy subsystem for managing device protection policy information system or otherwise associated with the DPPMS Policy Subsystem. Additionally or alternatively, in some embodiments, device protection The program management server 102 manages fulfillment of claims associated with the device protection program. Replacement devices (e.g., unused and / or DPP to manage inventory of client devices (client devices that are configured to use Communicate with or be associated with the DPPMS inventory subsystem. It can be done.

[0177] FIG. 2 is a block diagram of an exemplary system that may be specially configured in accordance with an embodiment of the present disclosure. Specifically, the depicted system is a DPPMS (DPPMS) 202 , third-party system 216, third-party system 222, and client The devices include devices 228, 230, and 232. Each of these devices is connected to a network. The network 234 is configured to communicate with the network 234.

[0178] Client devices 228, 230, and 232 interact with the network The present invention may include one or more processors, memory, and communication interfaces for The client may be embodied in any computing device known in the art. The information received from the ant devices 228, 230, and 232 may be in various forms, and may be provided via a variety of methods, such as via client devices 228, 230, and 232 is a laptop computer, including any of the devices described herein. computers, smartphones, netbooks, tablet computers, wearable devices The data may be provided by these consumer devices. In some systems, the cluster may be provided and received via various modes of data transmission. One or more of the client devices 228, 230, and 232 may be any of the devices described herein. In other embodiments, the client device may be a subscriber device according to the embodiment. The devices 228, 230, and 232 communicate with at least one device via the DPPMS 202. It may be another device controlled by a subscriber user enrolled in the security program. In some embodiments, among the client devices 228, 230, and 232 billing, registration subscription request, and registration cancellation request data using one or more of the following: object, etc., to a third party, such as a third party system 216 or 222 In an exemplary system, the The client or user device is the subscriber device and the device used to transmit billing. The device may be both a

[0179] Third-party systems 216 and 222 are responsible for enrolling in and managing the Device Protection Program. and / or to perform at least one action associated with canceling a registration. As illustrated, each third-party system may be configured to Third-party servers, such as servers 218 and 224, and third-party databases 220 and 226. In the example, a third-party system is a third-party server and a third-party The database is used to determine whether a given subscriber is registered through a third party. configured to perform additional actions such as a registration status check to determine if obtain.

[0180] Third party servers, such as third party servers 218 and 224, Third-party systems such as the network 234 and the Each third-party system can be configured to allow communication with any network. The system utilizes a corresponding third-party server to communicate with the client device 228, 2 30, and 232. Additionally or alternatively, the Third Party System may A service server may be used to communicate with the DPPMS 202.

[0181] Each third party server also includes a third party database, such as 220 and 226. may be associated with or connected to a corresponding third-party database of Other methods of communication may be possible. Third party databases may be integrated with corresponding servers. In some systems, third-party data The database contains at least one of the subscribers associated with the third-party system. Subscriber information may be stored, for example, for each subscriber registered through a third-party system. allows a third-party system to act as a third-party device management system. associated with subscriber information stored in a third-party database, as configured Additionally or alternatively, the third-party server may Utilizing the party database, the client devices 228, 230, and 232 In response to a request received from a client device (e.g., a subscriber device) , or perform an action in response to one or more requests received from the DPPMS 202. Specifically, the client device may be configured to communicate with the third-party server 22. 4 through communication with the third-party system 222 to register for the device protection program. The third-party server 224 may store the third-party database 226 Third-party systems can be used to register users who store their subscriber information. The system 222 utilizes a third-party server 224 and a third-party database 226. to use this new Subscriber information may be communicated to the DPPMS 202 .

[0182] The third-party databases 226 are each a network-attached storage (NAS) database. data storage device(s), such as a separate database server The third party database 220 and the third party database 222 may be embodied as one or more 26 respectively include, among other data, user data, subscriber data, subscriber information, subscription This may include a customer identifier data object, subscriber device information, or other data. Each of third-party databases 220 and 226 may be a single database, multiple databases, or a database, or a combination of several components configured to store information It will be readily apparent that each type stored may be different. The data and / or information may reside in separate storage components.

[0183] DPPMS or DPPMS202 is a system for subscriber registration, subscriber cancellation, and error handling. Perform a myriad of actions associated with device protection program management, such as managing device protection policies, billing, and more. Thus, the DPPMS 202 may include various means for performing the functions described herein. Various software and / or hardware components configured to perform one or more of the operations described herein. For example, as illustrated, the DPPMS 202 may include , an enrollment management subsystem 204, a fraud prevention subsystem 206, and a fulfillment subsystem. 208. Additionally or alternatively, one or all of the subsystems may include In some cases, the data store 210 may be configured to communicate with one or more data stores. As described herein, the circuits and subsystems of the DPPMS 202 in conjunction with software that configures the device to perform the operations described in this document. The physical device may be collectively embodied in the above, and the device may be connected to a provider entity. and may operate locally or remotely.

[0184] The Enrollment Management Subsystem 204 manages the subscribers and / or participants in the device protection program. configured to perform various tasks associated with managing customer device enrollment. This may include software and / or hardware means, such as a registration authority. The management subsystem 204 interacts with other subsystems and / or the data store 210. and may be configured to facilitate registration subscription to the Device Protection Program. In other words, the entitlement management subsystem 204 is In cooperation with Datastore 210, the new Device Protection Program covers and / or Subscriber and / or Subscriber Device enrolled in the Device Protection Program; Lists and / or stored data of registered subscribers and / or subscriber devices The registration functionality may be configured to facilitate adding subscribers to the service's data ledger. New subscriber registrations to third-party device management systems and added to DPPMS The first situation is for records and the second situation is for DPPMS and the service when a discrepancy occurs between the two systems. This applies both to the second situation for synchronization between third-party device management systems and In addition, the registration management subsystem 204 may receive notifications from the device protection program. Software and / or hardware configured to perform registration cancellations In other words, the enrollment management subsystem 204 may include other subsystems. In conjunction with the system and / or data store 210, the subscriber and / or the subscriber device Subscriber and / or Subscriber Device from a Device Protection Program in which the Subscriber is currently enrolled In some embodiments, the system may be configured to facilitate cancellation of the Registration subscription and / or cancellation can be performed on the client device 228, 2 30, or 232, and one or more third-party systems 216 and 222; This may occur due to user communications with third-party systems, such as communications with A user may access a third party via a client device 228 (e.g., a mobile device). communicate with the third party system 216 to communicate with the third party system (e.g., device protection program (through the mobile device carrier associated with the mobile device) The third-party system can then communicate with the DPPMS202. In addition to this, or this, the Alternatively, to cancel, the user may access the client device 228 (e.g., communicate with the third-party system 216 via the third-party device through the system (e.g., the mobile device carrier associated with the mobile device) You may cancel your subscription associated with the Device Protection Program and the Service. The third-party system then communicates with the DPPMS202 to allow the user to configure device protection. You may be able to identify that you have cancelled your subscription to the program. Subscribers and / or subscriber devices are registered with the particular Device Protection Program in which they are enrolled. The claim can then be appropriately processed (e.g., through performance). The record management subsystem 204 may store accurate subscriber and / or subscriber data so that The device may be configured to perform other operations to maintain the device list.

[0185] The fraud prevention subsystem 206 prevents fraudulent charges associated with the device protection program. means, such as software and / or hardware, configured to detect For example, the fraud prevention subsystem 206 may respond to receiving a bill or billing information by The anti-fraud subsystem may be configured to identify and implement anti-fraud protocols in response to the anti-fraud message. The system runs in conjunction with the Fulfillment Subsystem and / or the Registration Subsystem to process claims. Fraud prevention protocols may detect fraudulent activity in the fulfillment and / or registration process. , may include one or more anti-fraud events, each of which may include an anti-fraud sub-event. This may affect the fraud determination of the system 206. The fraud prevention subsystem 206 is associated with or associated with the subscriber device. Get real-time device information from the to perform a specific fraud prevention event by determining the action to be taken. It is composed.

[0186] For example, the fraud prevention subsystem 206 may respond to a claim submission or indication of fraudulent activity. , real-time device information from third-party device management systems via one or more APIs For example, the fraud prevention subsystem 206 may obtain device information via one or more APIs. and communicate with third-party device management systems to ensure billing is handled by DPPMS or third-party Captured from the subscriber device as reported to the third-party device management system Real-time device information may be obtained.

[0187] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. The management system notifies the device location application when an incident is reported. Device location application status that can indicate whether the application was enabled The fraud prevention subsystem 206 obtains the device location information in real time. Use application status to manage at least one third-party device management system. and associated device location application status and third-party Based on the identity of the claimant, the claimant may decide to reject the claim as a fraud risk. For example, in some embodiments, a third-party device management system may If it is a manufacturer system (e.g., an OEM system), the device location application The device location application status indicates that the application is not valid (and Therefore, the device location application can be used to locate the subscriber device. If the fraud prevention subsystem 206 determines that the transaction is fraud-specific, the fraud prevention subsystem 206 determines whether the transaction is fraud-specific or not, based on the fraud risk. The court may reject the claim on the basis of the

[0188] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. The management system set the device lost status to lost before the incident was reported. Lost Device Status, which indicates whether a lost device application was used to determine In some embodiments, the anti-fraud subsystem 206 at least Device Lost Status and / or at least Device Lost Status and Device Location Based on application status, billing and In an exemplary embodiment, the fraud risk associated with the service where the claim occurred is determined. If a third-party device management system is the device manufacturer, the device location account The application is enabled, but the corresponding device loss status is set to Lost Mode. If the device location application status indicates that the device is not The suspension subsystem 206 may suspend approving the claim. The device lost status is displayed in the system and and / or stored by a database to identify device lost status. may be accessed by the anti-fraud subsystem 206. In this state, the device lost status is reported in real time from the system and / or database. It can be obtained in time.

[0189] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. third-party identity associated with the management system, claim type (e.g., loss Lost claims, stolen claims, damaged claims, etc.), device location application status The allowability of the claim may be determined based on the device loss status. In some embodiments, the billing information is associated with the third-party device management system that generated the billing information. The third-party identity provided is a mobile carrier system and is associated with If the claim is a loss or theft claim, the associated claim is Location application is not accessible to device location app may only be approved if application status indicates otherwise. For example, the services associated with the third-party device management system that generated the claim. If the third-party identity is the device manufacturer and the associated claim is a loss claim, If the claim is a theft or theft claim, the associated claim will also include: (1) device location; The device location application indicates that the application is inaccessible. or (2) when the device location application is accessed. The device location application status indicates that the device is available for access, and It can only be acknowledged if the device loss status is set to lost. Additionally or alternatively, in some embodiments, the third party from which the claim originated may Regardless of the third-party identity associated with your device management system If the associated claim is a damage claim, the associated claim is The device location application indicates that the application is inaccessible. It can only be approved if the application status indicates so.

[0190] In some embodiments, the anti-fraud subsystem 206 may include one or more third-party Communicate with the device management system(s) to retrieve pending billing data objects The subscriber device associated with the Fulfilled third-party billing data objects managed by a service device management system In this regard, the information may be configured to identify whether the information is associated with an object. , the fraud prevention subsystem 206 may analyze such data. situations where subscriber devices are maintained across two separate systems. The claim to determine which pending claim data object is associated with In situations where the data object is acquired in real time at the time of processing, or Such data captured and analyzed in real time may be used to identify previously associated subscriber devices. In situations where the claim data object indicates that the claim has already been fulfilled, there is a possibility of fraud. Reject and / or reject any outstanding billing data objects for further consideration due to Additionally or alternatively, the fraud prevention subsystem 206 may , communicate with one or more third-party device management systems to enroll The customer device is associated with a third-party device management system(s). one or more repair and / or replacement actions performed by a third-party entity In this regard, the present invention may be configured to identify whether the application is associated with the The fraud prevention subsystem 206 may, for example, be connected to the fulfillment subsystem 208 and / or one or more During the processing of the billing data object by the associated subsystem on Capture and analyze data in real time, and the captured data is then distributed to all subscriber devices. It should have already been serviced and no longer be owned by the associated user. For further consideration, due to circumstances indicating that fraud may occur may be configured to reject and / or mark unprocessed billing data objects .

[0191] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. The repair list is retrieved in real time from the management system and is then sent to the subscriber device. This includes any currently pending repairs associated with the device. Therefore, the open repair list is available. The fraud prevention subsystem then allows subscribers to access their devices through a third-party device management system. It may determine whether it has already initiated billing associated with the subscriber device. In some embodiments, the anti-tamper subsystem 206 may process open requests captured in real time. If the subscriber device is already associated with an open claim based on the online repair list, The system is configured to reject the claim after making a decision.

[0192] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. The incident remaining list containing the incidents available for consumption is retrieved from the management system. The incidents available for consumption are acquired by a specific device within a specific time interval. A policyholder may define the number of claim types allowed under the policy. For example, incident The remaining list remains available and / or subscriber profiles are registered. This may include one or more claim types that were previously processed under the device protection program. In an exemplary aspect, the device protection program allows registered subscribers to A first number of claim data objects of a first claim type over a given time interval, e.g., 24 months. a second claim type (e.g., unlimited machine breakdown claims) and a second number of claim data for a second claim type. It may be possible to submit a data object (e.g., two accidental damage claims) and The device protection program may be configured to handle any of a myriad of billing types, for example, in some embodiments: Now, a third number of claim data objects of a third claim type (e.g., four lost claims) ) in the remaining incident list. Billing data for certain billing types processed by third-party device management systems The fraud prevention subsystem 206 may include an incident remaining list. analyzes whether newly submitted claim data objects are , which returns the allowed claim data objects processed for the associated claim type. The claim data object may determine whether it exceeds the remaining incident list. If the fraud prevention subsystem 206 determines that the transaction should be processed using the The system 206 adjusts the remaining incident list (e.g., by adding newly received billing data objects). Decodes the remaining instance count for the remaining incident list associated with the object. storing an updated list of remaining incidents; and / or or notify third-party device management systems of an updated list of remaining incidents. The fraud prevention subsystem 206 may, for example, detect and / or correct any remaining data when processing billing data objects. Real-time data capture and analysis of incident lists Enhance fraud detection with data analytics to ensure subscribers enrolled in device protection programs The subscriber violated the device protection program enrollment program and obtained two billing data objects. It can identify when an attempt is made to process

[0193] Additionally or alternatively, the fraud prevention subsystem 206 may Analyzes the existing list and routes received billing data objects to the appropriate system For example, the fraud prevention subsystem 206 may operate alone or in conjunction with the fulfillment subsystem 206. In conjunction with 08, newly submitted claim data objects for a specific claim type are added to the You may request a third party to process your personal information based on the corresponding device protection program for which you are enrolled. or forwarded to a third party system such as a DPP In an exemplary aspect, the device The protection program defines a set of claims routing rules, e.g. The number of claim data objects of a particular type that are included (e.g., the first two accidental damage claims) The data object is processed by a third-party device management system for subsequent Defines all accidental damage claims data objects processed by the DPPMS The fraud prevention subsystem 206 and / or the fulfillment subsystem 208 may Analyze the incident list to see if the claim data object matches the claim routing rule set. Determine whether the device should be routed to a third-party device management system based on the It can be determined.

[0194] In some embodiments, the anti-tamper subsystem 206 may be configured to manage third-party device management. The management system will then determine whether the subscriber device is connected to the DPPMS and / or third-party devices. Previous exchanges, indicating whether they have been previously associated with the claim and exchanged through the management system. Therefore, in some embodiments, the exchange status is obtained in real time. The cancellation subsystem 206 cancels the subscription associated with the claim based on the previous exchange status. The customer device is associated with a third-party device management system. already provided by the provider entity or by DPPMS through a previous claim In some embodiments, the anti-tamper sensor is configured to identify that the The service system 206 may identify subscribers who have already been replaced as being associated with fraud risk. The device is configured to reject a received claim associated with the device.

[0195] In some embodiments, the fraud prevention subsystem 206 may perform a combination of the received information. In some embodiments, the fraud prevention subsystem may be used to identify fraud risks. If the fraud risk assessment determines that a claim is fraudulent based on the identified fraud risk, The prevention subsystem 206 may deny the claim or prevent it from being processed by another subsystem or otherwise. The claim may be rejected in this way.

[0196] The fulfillment subsystem 208 receives the claim and takes the necessary actions to fulfill the claim. software configured to perform a task (e.g., one or more fulfillment events); and / or hardware. In other words, the fulfillment subsystem 2 08 is lost, damaged, stolen, or will be repaired, replaced, or added. Action must be taken to otherwise restore device functionality to the subscriber. To resolve claims associated with other affected subscriber devices that are not affected by the For example, the system may process, track, and / or otherwise perform one or more steps related to the claim. To complete the method, the fulfillment subsystem 208 may include a DPPMS and / or one or more communicate with one or more associated subsystems of the third-party system on the and synchronization between systems, and the fulfillment subsystem 208 It may operate in conjunction with subsystem 206 and / or enrollment management subsystem 204 .

[0197] The DPPMS may, in some embodiments, provide a variety of other specific functionalities and / or data. It includes an additional DPPMS subsystem (not shown) for data management. For example, some In an embodiment, the DPPMS includes a DPPMS payment system. Alternatively, in some embodiments, the DPPMS may implement a DPPMS policy system. Additionally or alternatively, in some embodiments, a DPPMS subsequence One or more of the systems may include a registration management subsystem 204, a fraud prevention subsystem 206, , and / or fulfillment subsystem 208, or a combination thereof. This is further embodied by the business system.

[0198] Data store 210, as well as DPPMS subscriber profile data object data database 212, connectivity database 214, and error handling database 215. Each of the individual component databases is stored on a Network Attached Storage (NAS) device. data storage device(s), such as a computer, a network device, or a separate database server In addition, each of these components may be embodied as We may use the information provided by the Subscriber and / or Subscriber Devices, Third Party Systems (including Third Party connectivity to device management systems, transmission error classification and / or handling, etc. For example, in the exemplary system, the DPPM The subscriber profile data object database 212 contains, among other data, User data, subscriber data, subscriber information, subscriber identifier data object, subscription The data may include user device information, or other data. The database 214 may store, among other data, third-party system data, service Third-party system identifiers, third-party system IP addresses, or other data Additionally, in the exemplary system, the error handling database 215 may include an error log. The data store 21 may contain error logging, error classification data, error codes, or other data. 0 retrieves data from one or more of these component databases and receives The collected data is sent to the registration management subsystem 204, the fraud prevention subsystem 206, and the communication and / or communication with one or more component subsystems, such as the row subsystem 208. The data store 210 and / or the DPPMS subscriber may be configured to transmit A profile data object database 212, a connectivity database 214, and Each of the and / or error handling databases 215 may be a single database, multiple databases, or a A base, or a combination of several components configured to store information It will be readily apparent that in some embodiments, each type of data and The information and / or the information may be stored in a separate storage component.

[0199] The DPPMS 202 may be implemented using one or more DPPMS devices, such as one or more of the DPPMS devices 300 shown in FIG. The present invention may be embodied by one or more computing systems. As illustrated in FIG. The device 300 includes a processor 302, a memory 304, input and / or output modules 306, communication module 308, data store management module 310, registration module 3 12, a fulfillment module 314, a fraud module 316, and an error module 318 The apparatus 300 may include the components described above with respect to the DPPMS of Figures 1 and 2 and Figure 4A. 10. These components 302 to 318 are described with respect to functional limitations. It should be understood that a particular implementation necessarily involves the use of specific hardware. Some of these components 302-318 may be similar or have common hardware. It should also be understood that two modules may both include the same processor. By utilizing the use of sensors, network interfaces, storage media, etc., each module The present invention can perform their associated functions such that no duplicate hardware is required.

[0200] Thus, the terms "module" and "modules" used herein in reference to components of a device and "circuitry" refers to the particular modules and / or circuits being described. It includes specific hardware configured to perform the functions associated with the mechanism. The terms "module" and "circuitry" are understood broadly to include hardware. In some embodiments, the circuitry and / or modules may be It may also include software for configuring the hardware. For example, in some embodiments "Module" and / or "circuitry" refers to processing circuitry, storage media, network The device may include a network interface, input and / or output devices, etc. In some embodiments, other elements of device 30 provide the functionality of a particular module or modules. For example, the processor 302 may provide processing functionality, The memory 304 may provide storage functionality, and the communication module 308 may provide network It can provide a user interface functionality, etc.

[0201] Indeed, in some embodiments, one or more modules may be a separate device, server, and / or associated device that may communicate with one or more of the It should be understood that the present invention may be associated with other computing hardware. In some embodiments, the registration module 312 is included on a separate computing device. and / or embodied by a separate computing device. The device may, in some embodiments, be similarly named as described with respect to device 300. Memory, processor, input / output modules that function similarly to the components named , a communications module, a data store management module, and / or any combination thereof. The computing device of the separate registration module 312 may be, for example, a hardware Perform registration-related actions through software, hardware, or a combination thereof. Instantiate one or more action process instances to execute and / or process Additionally or alternatively, some embodiments may In this embodiment, the fulfillment module 314 may also include a memory, a processor, an input / output module, a communications module, a data store management module, and / or any combination thereof contained on a separate computing device containing the The separate fulfillment module 314 computing device may be used to implement, for example, through hardware, software, or a combination thereof. One or more action process instances to perform and / or process related actions. Additionally or alternatively, the device may be specially configured to embody the In some embodiments, the fraud module 316 may also include memory, a processor, and an input / output module, communication module, data store management module 310, and / or and / or contained on a separate computing device containing any combination thereof. or a separate computing device. The computing device may be, for example, hardware, software, or a combination thereof. one or more devices to perform and / or process fraud-related actions through The separate device may be specifically configured to implement the above action process instances. Each of the devices may include one or more applications for performing functionality as described herein. The software may be specially configured to perform the application, or a portion thereof.

[0202] Additionally or alternatively, in some embodiments, an error module The module 318 may also include memory, a processor, input / output modules, communication modules, and and / or any combination thereof, and / or embodied by the error module. 318 may be included in and / or shared by one or more of the separate devices. In this regard, each of the separate devices may be an independent component or a shared Utilizing the components described herein with respect to the error module 318 The processor may be configured to perform some or all of the processor processing functions.

[0203] Each separate computing device may, in some embodiments, comprise multiple subcomponents. A component may be embodied by an entity, a sub-device, a subsystem, etc. For example, some In an embodiment, each separate computing device is a diverse, distributed, specially configured In some embodiments, the computer One or more of the routing devices may be implemented as described below with respect to FIG. Each separate computing device is specifically configured as an action processing instance. A subcomponent, subdevice, and / or subsystem of a may be able to communicate with each other via a direct connection and / or one or more networks Additionally or alternatively, in some embodiments, a separate computer Each of the computing devices may be capable of communicating with each of the other separate computing devices.

[0204] In some embodiments, the processor 302 (and / or co-processor, or processor Any other processing circuitry that assists or is otherwise associated with a processor. The communication mechanism communicates with the memory 304 via a bus for passing information between components of the device. The memory 304 may be non-transitory, e.g., one or more volatile and / or In other words, for example, the memory may include an electronic storage device (e.g., The memory 304 may be a memory device (e.g., a computer-readable storage medium) that allows the device to perform the exemplary embodiments of the present disclosure. The information, data, content, etc. may be used to enable various functions of the various embodiments to be performed. The memory may be configured to store content, applications, instructions, etc.

[0205] The processor 302 may be embodied in several different ways, for example, independently executing Additionally or alternatively, the device may include one or more processing devices configured to: Additionally, the processor may support independent execution of instructions, pipelines, and / or multi-threading. The system includes one or more processors configured in tandem via a bus to enable Use of the terms "processing module" and / or processing circuitry refers to a single-core processor. processor, multi-core processor, multiple processors within a device, and / or one or more This may be understood to include separate, remote, or "cloud" processors.

[0206] In an exemplary embodiment, the processor 302 may include a processor 304, a processor 306, a processor 308, a processor 309, a processor 310, a processor 311, a processor 312, a processor 313, a processor 314, a processor 315, a processor 316, a processor 317, a processor 318, a processor 319, a processor 320, a processor 321, a processor Alternatively, the method may be configured to execute instructions accessible to the processor. Alternatively or additionally, the processor 302 may be configured to execute hard-coded functionality. Therefore, it may be configured by hardware or software. Whether comprised of a program or a combination of hardware and software, The processor is an engine that, when appropriately configured, is capable of performing operations according to embodiments of the present disclosure. Alternatively, it may represent a separate entity (e.g., physically embodied in circuitry). As an example, if the processor is embodied as an executor of software instructions, the instructions may be The instructions, when executed, perform the algorithms and / or operations described herein. The processor may be specifically configured to:

[0207] In some embodiments, the device 300 includes an input and / or output module 306. The input and / or output module 306 may include a processor 302 and and in some embodiments, The input and / or output module 306 may receive an indication from the user. interfaces, including web user interfaces, mobile applications, The display may include a device display, which may include an application, a client device, etc. In some embodiments, the input and / or output module 306 may include a keyboard, a mouse, Joystick, touch screen, couch area, soft keys, microphone, may include a speaker, or other input and / or output mechanism. The user interface circuitry that configures the processor is accessible to the processor. Computer program instructions (e.g., one or more user interfaces via the The interface element may be configured to control one or more functions of the interface element.

[0208] The communication module 308 may be configured to communicate with the network and / or any Receive and / or transmit data to or from other devices, circuitry, or modules Any hardware or combination of hardware and software configured to The present invention may be implemented by any device, module, or circuitry embodied in any of the following: In this regard, the communication module 308 may be, for example, a wired or wireless communication network. The device may include a network interface for enabling communication with a network. The module 308 may include one or more network interface cards, antennas, buses, , switches, routers, modems, and supporting hardware and / or software or any other device suitable for enabling communication over a network. Additionally or alternatively, the communication module 308 may include an antenna (single interacting with the antenna(s) to cause transmission of a signal via the antenna(s). or to process the reception of signals received via the antenna(s). For this purpose, the antenna may include circuitry for interacting with the antenna(s). The signal is transmitted by the device 300 in accordance with Bluetooth (registered trademark) v1.0 to v3.0, Bluetooth Low Energy (BLE), Infrared Radio (e.g., IrDA) FREC Several wireless personal area networks, such as IEEE 802.11b, IEEE 802.11b, IEEE 802.11c, IEEE 802.11d, IEEE 802.11b ... In addition, these signals may be transmitted using any of the following technologies: Wi-Fi, Personal Area Network (PAN), and Wi-Fi. Wi-Fi, Near Field Communication (NFC), and Worldwide Interoperability of Microwave Access (WiMA) X), or other proximity-based communication protocols. stomach.

[0209] In some embodiments, the communication module 308 may be a one or more client devices and / or subscriber devices, and / or with one or more third-party systems and / or third-party device management systems; For example, the communication module 308 may facilitate communication between a client device and and / or transmit information requests and / or responses to third party systems and / or from client devices and / or third-party systems. This may facilitate receiving information requests and / or responses.

[0210] The data store management module 310 manages the data store associated with the device 300. It may be any means that facilitates communication and / or management of a data store. For example: The device 300 stores (1) a subscriber list, (2) a third-party system connectivity list, and and (3) manage a data store containing an error handling data list. The module 310 identifies the data in these lists and / or configured to add, cancel, delete, or otherwise manage one or more of In some embodiments, the data store management module 310 Specific data store management operations associated with the operations performed by each of 2 through 318 To achieve this, the processor 302, the registration module 312, the fulfillment module 314, Associated with one or more of the fraud module 316 and / or error module 318 It can be attached.

[0211] The registration module 312 registers subscribers associated with one or more device protection programs. Any hardware and / or software that facilitates the addition, cancellation, and other management of In some embodiments, the registration module 31 may be embodied by software means. 2 is a hardware implementation of the enrollment management subsystem 204, as illustrated in FIG. and / or software. For example, the registration module 312 may include a data store manager. The management module 310, in cooperation with the processor 302, etc., communicates subscriber information with the subscriber device. The new subscriber must be identified with the corresponding device protection program that they have enrolled in. Add subscriber information to a subscriber list associated with a subscriber and / or subscriber device. configured to enroll new subscribers in the device protection program, such as by Additionally or alternatively, the registration module 312 may The module 310 cooperates with the processor 302 to cancel the device protection program. marking the subscriber information in the subscriber list associated with the program; The subscriber information associated with the device protection program may be removed from the subscriber list. or the subscriber information has taken an action that indicates cancellation of the Device Protection Program. Cancel an existing subscription from the Device Protection Program, for example, by running It can be configured as follows.

[0212] The registration module 312 also cooperates with the processor 302, the communication module 308, etc. and one or more third-party systems, such as one or more third-party device management systems. The device may communicate with the system to facilitate synchronization with a third-party device management system. For example, the registration module 312 may generate a third-party registration status request data object and associated with the subscriber or subscriber device within a third-party device management system. Third-party registration status response data object indicating the associated registration status Additionally or alternatively, a registration module may be configured to receive 312 transmits a third-party registration management request data object and The customer device or subscriber information has been successfully added to the third-party device management system. The third-party registration management system may be configured to receive a third-party registration management response indicating whether the third-party registration management system has been successfully registered.

[0213] In some embodiments, the registration module 312 may update the pending registration action queue. Additionally or alternatively, in some embodiments, a registration module The action process controlled by the registration module 312 is Processes a registration management request data object from the registration action queue of the otherwise perform steps to process the record management request data object, Create one or more action processes associated with an outstanding registered action queue. , execute, clear, allocate, or otherwise manage outstanding registration actions. As the length of the sequence increases, the registration module 312 may According to the or execute a new action process to process the pending registered action received. from the pending registration action queue, such as a pending registration management request data object. In addition, or in addition, the device may be configured to increase the rate at which the particles are removed from the device and processed. Alternatively, according to certain embodiments described herein, the registration module 312: If the outstanding registration action queue meets a lower value, e.g., outstanding registration management request data When the number of data objects is below a certain lower threshold, a certain action is performed. Decrease the number of running threads in the application process or reduce the number of action processes being performed. The process may be configured to terminate.

[0214] The fulfillment module 314 fulfills the received claims associated with the device protection program. Any hardware and / or software that facilitates receiving and / or fulfilling may be embodied by software means. In some embodiments, the fulfillment module 314 is the hardware that implements the fulfillment subsystem 206, as illustrated in FIG. and / or software. For example, the fulfillment module 314 may include a processor 30 2. In cooperation with the data store management module 310, etc., to process billing and related information received from subscribers. Identifying an associated device protection program and / or The claim processing protocol may identify and execute a claim processing protocol that includes an instruction set associated with the claim processing protocol. In some embodiments, the fulfillment module 314 may manage a queue of outstanding claim actions. Additionally or alternatively, in some embodiments, fulfillment module 31 4 indicates that the action process controlled by the fulfillment module is Processes claims from the queue or takes steps to fulfill claims requests. One or more actions associated with the outstanding claim action queue are executed in the following way: The application process may be created, executed, deleted, allocated, or otherwise managed. As the length of the processing claim action queue increases, the registration module 314 According to the specific embodiment described, additional actions are performed via the currently running action process. thread or execute a new action process to clear any outstanding claims configured to increase the rate at which outstanding registered actions are removed from the queue and fulfilled. Additionally or alternatively, certain embodiments described herein may If so, the fulfillment module 314 detects when the outstanding claim action queue reaches a lower threshold. When a particular action is performed, the number of threads in the process is reduced. , or may be configured to terminate the action process being performed.

[0215] In some embodiments, the fulfillment module 314 processes the billing data object. one or more devices, alone or in conjunction with one or more subsystems, in response to For example, the fulfillment module 314 may be configured to execute the acquisition process. For the purpose of replenishing inventory, we may transmit one or more device-acquired signals to third parties. The information may be transmitted to one or more third-party systems, such as a third-party device management system. In an exemplary aspect of the present invention, the fulfillment module 314 fulfills the billing data object; and In response to providing a particular device associated with the billing data object, automatically generate device acquisition signals and / or transmit device acquisition signals to third-party systems. The device acquisition signal may be transmitted to the fulfillment module 314 or associated This results in the provision of new devices to the device inventory managed by the associated subsystem. In some embodiments, the device acquisition signal is generated by a third party system. and the third-party entity ( device manufacturers) in response to their requests, and to registered subscribers. To provide new devices that conform to the specific device specifications associated with the device. Additionally or alternatively, the fulfillment module 314 may, for example, Obtain invoice data from third-party systems used to obtain access; and Processed by the fulfillment module 314 and / or associated invoice management subsystem associated with newly acquired devices by storing billing data for processing. In certain exemplary aspects, the system may automatically acquire and / or process the received billing data. For example, a billing data object can be processed and the fulfillment module 314 In response to the received and processed billing data object, the exchange device (e.g., The same model, memory size, and / or or other mobile devices) to subscriber users. Continuing with this exemplary aspect, in some embodiments, the fulfillment module 314 Additionally or alternatively, you may purchase a replacement device from any third-party software associated with the device. system (e.g., a third-party system managed by the manufacturer of the replacement device) a device acquisition signal to the device to acquire a new device having the same device specifications as the replacement device. automatically starts offering devices and therefore the availability of devices that match these device characteristics. The stock can be automatically replenished.

[0216] In some embodiments, the action process performed associated with the fulfillment and the registration The action process that is performed is separate from the action process associated with other actions, such as recording. It should be understood that in other embodiments, a single action process may be executed. The execution associated with the fulfillment may be performed so that both the registration action and the fulfillment action may be performed. The action process that is performed and associated with other actions, such as registration Similarly, in some embodiments, a single combined action process may be shared. The queue of actions held by the application contains both outstanding registration actions and outstanding fulfillment actions. While the method may store the pending registered actions, in other embodiments, a particular action queue may store the pending registered actions. A particular action queue may be dedicated to the execution of outstanding actions. Each action queue may be dedicated to one action of that type. Configured to process a specific type of action from the corresponding action queue above In addition, the execution of one or more processing instances may be associated with the execution of the processing instance. Alternatively, the fulfillment module 314 may execute one or more actions, as described below. Scale the number of action process instances that are executed that are associated with an action queue. The system may be configured to manage one or more scaling services configured to scale the do.

[0217] The fraud module 316 detects fraudulent claims associated with subscribers to the device protection program. Any hardware and software that facilitates identifying or otherwise detecting requests In some embodiments, the fraudulent module may be implemented by software and / or hardware means. Module 316 embodies the anti-tamper subsystem 206, as illustrated in FIG. This may include hardware and / or software. For example, the fraud module 316 may The processor 302, the data store management module 310, and the like cooperate to allow the subscriber to submit a bill. The device protection program issued by the Additionally or alternatively, the fraud module 316 may One or more fraudulent events, such as one or more fraud prevention events associated with an anti-fraud protocol The fraud module 316 may be configured to perform preventative actions, such as, for example, Real-time data associated with the device or directly from the subscriber device For example, the fraud module 316 may be configured to extract real-time data. Real-time device information can be obtained from third-party device management systems via the above APIs. An example of real-time device information is device location information. Application application status, device lost status, open repair list, and / or incident remaining lists. The module 316 utilizes one or more portions of the real-time device information to Determine the fraud risk associated with a claim and / or manage the claim accordingly reject or accept the request.

[0218] The error module 318 receives the transmission errors, classifies the transmission errors, and / or any hardware that allows subsequent error handling associated with a transmission error. The error module 318 is embodied by hardware and / or software means. includes a registration module 312, a fulfillment module 314, a fraud module 316, and / or or one or more modules from a group of communication modules 308 to communicate and and / or operate with third-party systems, such as third-party device management systems A transmission error may be identified that results from a failed attempted transmission to For example, failure to connect to a third-party system, loss of connection to the third-party system during, before, or after transmission of information to the system; received in response to your request or in response to the transmission of information to a third-party system. In an exemplary embodiment, the error module 318 includes one or more error classifications. The error classification set may be configured to identify an error classification set.

[0219] Each error classification can be associated with one or more sets of error handling instructions. In an embodiment, the error handling instruction set identifies or otherwise determines an error classification. For example, Error Module 3 can be identified based on a set of business rules for 18 provides a method for determining the error classification associated with a received transmission error. In some embodiments, each error configuration may be If met, a specific business rule indicates that the error classification is associated with a transmission error. Additionally or alternatively, in some embodiments, Error Handling An error handling instruction set contains one or more algorithms for identifying error classifications. identified based on a learning model, statistical learning model, and / or machine learning model For example, in some embodiments, error classification may be performed using a myriad of machine learning implementations. In some exemplary aspects, errors can be identified using unsupervised learning models. In another exemplary aspect, a supervised learning model may be used to identify error classifications. can be identified.

[0220] In some such embodiments, algorithmic learning models, statistical learning models, The model and / or machine learning model utilizes a variety of inputs. In this form, the input used for error classification is information associated with the transmission error, DPPM. Preferences associated with S, third-party device management systems, In some embodiments, algorithmic learning models may be used. In addition to or in addition to these, statistical learning models and / or machine learning models may Alternatively, you may use the Service in conjunction with a billing, subscriber, DPPMS, or third-party device management system. Other information attached may be used.

[0221] In some embodiments, the errors are based on different error classifications in a set of error classifications. For example, the error classification set may be the error classification for "retryable errors" and An error classification of "escalation error" may include a retryable error. It puts the failed transmission back on the queue to attempt a subsequent transition, waits the retry period, and then returns the failed transmission to One or more of the following: determining the retry time to wait before queuing for subsequent transmission An error handling protocol containing the error handling events associated with the In some embodiments, the retry time may be based on the number of failed transmission attempts. For example, the retry time may be initially set to 5 minutes or so upon the first failed transmission. For each subsequent failed transmission, the retry time is twice The retry time after the first failed transmission is 10 minutes, and the retry time after the third failed transmission is 10 minutes. is 20 minutes, the retry time after the third failed transmission is 40 minutes, etc. , can be doubled. In other embodiments, a different relationship may be used to retry based on the number of transmissions. In yet another embodiment, the relationship may be used to identify a predetermined length of time. A retry time that does not utilize the number of transmissions may be identified, such as by always waiting for the next transmission.

[0222] The error module 318 includes an instruction set associated with an escalation error. escalation error handling protocol, The protocol may include one or more error handling events. The rule escalates errors and / or transmission errors, including failed transmissions. The error handling instructions are defined by a set of error handling instructions, including adding the For example, the escalation queue may require an error handling system and / or or transmitted to a third-party processing system or otherwise communicated, transmission There may be a queue of errors and / or associated failed transmissions. In an embodiment, the transmission error and / or the associated failed transmission is communicated to and / or control any third-party systems associated with the transmission errors received. or a third-party entity otherwise associated with a third-party system. The error is transmitted to a third-party error handling system associated with the system. In this system, the third-party system that was the intended recipient of the failed transmission is escalated. It is also a third-party system to which the error is transmitted. Any errors reported and / or corresponding failed transmissions may be attributable to third party errors. - transmitted to a third-party error processing system for electronic processing by the processing system Alternatively or additionally, escalated errors may be handled by a human operator. and / or may be processed by a human operator.

[0223] In some embodiments, the error module 318 may include a processor 316 for processing errors associated with transmission errors. The error configuration may include at least an error code, an error In some embodiments, the classification may include a maximum retry threshold. The error module 318 may utilize the error configuration service to identify the error configuration. Thus, the error module is associated with an error configuration service.

[0224] Specific Components of the Devices and Systems of the Exemplary Embodiments Concerning the Present Disclosure Having described certain exemplary operations performed by embodiments of the present disclosure, reference is now made to FIGS. As described below in relation to FIG.

[0225] Exemplary Process Operations 4A and 4B illustrate a self-healing method based on a received entitlement management request data object. 4A illustrates exemplary operations performed in a process for registration. 1 illustrates an exemplary operation of a self-healing registration based on a received registration subscription request. 4B shows a self-healing process based on a received registration cancellation request data object. 4A and 4B illustrate exemplary operations of registration. device management system, and / or client devices such as subscriber devices DPPMS equipment configured to communicate with one or more third-party systems, such as Various devices and / or equipment within a networked system, such as device 300 The operations discussed below are described with respect to the DPPMS apparatus 300. Although shown, operation may be similar to or different from DPPMS apparatus 300 within the scope of this disclosure. Various different devices and / or alternative components from the DPPMS apparatus 300 may be used. It should be understood that this may be implemented using any number of components.

[0226] Additionally or alternatively, in some embodiments, the DPPMS apparatus 300 based on registration notifications received from certain third-party device management systems. It may be configured to synchronize more than one subscriber profile(s). For example, one or more specific third-party device management systems may implement a device protection program. In an exemplary aspect, for example, a third-party device may be trusted to be associated with the The device management system provides the Device Protection Program service to registered subscribers. New devices received by a third-party device management system may be associated with Registration allows the device 300 and / or subsystems within the device 300 to be registered without subsequent verification. In such a situation, the device 300 should be used to synchronize Newly registered third-party subscriber profiles from the third-party device management system one or more registrations, subscription notifications, and / or third-party One or more newly cancelled subscriptions associated with the subscriber profile. A subscription cancellation notification may be received. and / or registration cancellation notice(s) by the device 300. For example, the device 300 or the device 300 may be configured to perform one or more synchronization events. Synchronize one or more DPPMS subscriber profiles for one or more subsystems In some embodiments, the device 300 may receive some or all of the information contained in the received notification. or all of them to identify associated data to use in such synchronization events. (e.g., the notification may include one or more additional device identifiers for processing, such as the IMEI. One such as a device serial number for use in identifying and / or retrieving the child (This may include one or more device identifiers.)

[0227] Referring first to FIG. 4A, in block 402A, the device 300 includes a registration module 312 , the processor 302, the communication module 308, etc., receives a registration subscription request. The registration subscription request may be sent to, for example, a currently unregistered device. and / or unregistered users subscribed to the Device Protection Program (say In other words, a new subscriber has been added who is associated with a specific device protection program. In some embodiments, the received registration subscription request may indicate: Enroll currently unenrolled devices in the Device Protection Program or enroll them in other ways. The received subscriber information is associated with the device protection program. A subscriber identifier data object that uniquely identifies the associated human subscriber or subscriber device. An example of a received subscriber identifier data object is a subscriber Name (e.g., person or entity name), subscriber contact information, subscriber device IP address the subscriber device International Mobile Equipment Identity (IMEI) number, or a combination of these. In an exemplary embodiment, the registration subscription request includes IMEI, which uniquely identifies the client device subscribed to the protection program In some embodiments, the registration subscription request includes This can be done directly in the DPPMS interface by the party or by the registered subscriber. The crypto request is sent to blocks 404A, 406A, 408A, 410A, 412A, 4 14A, and by third-party systems that may be the same as or different from 416A. For example, in some embodiments, block 402A The request is associated with the wireless carrier or vendor from which the subscriber device was purchased. The manufacturer system may transmit the information to a third-party device management system. It can be verified and synchronized in the subsequent block, and the subsequent block can be used to PMS (and / or subsystems of DPPMS), or device manufacturers or A second third party associated with another entity associated with a device protection plan The device management system may be synchronized.

[0228] In block 404A, the device 300 registers the associated a registration module 312 for identifying a registered third-party device management system; , processor 302, data store management module 310, etc. In an embodiment, the device 300 may derive a third-party registration subscription request from the received registration subscription request. In other embodiments, the device management system may include means for extracting a device management system identifier. The device 300 may register a third-party device based on the received registration subscription request. The third-party device management system identifier may be determined. may be used to transmit to third-party device management systems or Third-party device management systems associated with the device management system identifier In a particular example, the user may be able to determine a communication protocol for communicating with the or a client device is newly subscribed to the Device Protection Program via Third-party entities and associated third-party device management systems (e.g., mobile carrier systems, device manufacturers, and sales systems).

[0229] In block 406A, the device 300 includes a registration module 312, a processor 302, a communication a third-party registration module 308 in a third-party device management system, means for transmitting a status request data object. The Status Request Data Object provides the third-party device management system with the subscriber identity. Information in the registration / subscription request, such as a distinguishing data object or other subscriber information obtain and / or otherwise identify third-party status associated with the information; In an exemplary embodiment, the device 300 may be configured to extract information such as an IMEI. The third-party subscriber profile associated with the provided subscriber identifier data object. Third-party registration status to determine if a file data object exists A request data object may be created.

[0230] At block 408A, the device 300 includes a registration module 312, a processor 302, a communication Third-party registration from a third-party device management system, such as module 308 means for receiving a status response data object. The status response data object contains the transmitted third-party registration status request data. The third-party subscriber profile associated with the information provided in the data object. It may indicate the third-party registration status, such as whether the data object exists. For example, if a third-party subscriber profile data object exists, The Third Party Registration Status Response Data Object contains the third party subscriber profile. Third-party subscriber profile data object information A subset (e.g., a third-party subscriber profile data, not the entire profile) Part of the Subscriber Profile Data Object, or a third-party subscriber profile data object The information may include equivalent information in either the object or a subset of the information. Instead, the third-party registration status response data object is Registration status and associated status flags, e.g., third-party subscriber profiles Verify that the file data object does not exist in the third-party device management system. 0 represents, and the third-party subscriber profile data object is a third-party It may contain a bit flag where 1 indicates presence in the device management system. Alternatively or additionally, in some embodiments, a third-party registration status The response data object contains the subscriber device being compensated, the device status, and the protection profile. Program status (e.g., warranty status), subscription coverage timestamp group(s) (e.g., compensation interval spanning two timestamps), and / or or identify the registration contract information associated with the subscriber profile; The information may include information associated with the

[0231] At decision block 410A, the flow determines whether the received third-party registration status is Indicates whether a third-party subscriber profile data object exists. In either case, the device 300 continues based on whether the received third-party registration Based on the status, one or more system synchronization events may be configured to be performed. For purposes of illustration, blocks 412A and 416A represent two specific aspects of a system synchronization event. Provide specific examples.

[0232] At decision block 410A, the third party registration status is set to third party subscriber profile. The profile data object must not exist in any third-party device management system If so, flow continues to block 412A. System synchronization, such as the registration module 312, the processor 302, and the communication module 308 Events, specifically those that are sent to third-party device management systems Some embodiments include means for transmitting a subscriber registration request data object. , the apparatus 300 also generates a third-party subscriber registration request data object; and / or third-party device management systems to provide subscriber identifier data objects. The extracted subscriber information and associated third-party subscriber profile data, such as includes a means for configuring a third-party registration request to create a data object. In other embodiments, the device 300 may be connected to a third-party device management system in other ways. The system then stores a data object associated with the extracted subscriber information, such as a subscriber identifier data object. A server configured to create a third-party subscriber profile data object. Determine the third-party subscriber registration request data object. The third-party subscriber registration request data object is then transmitted, e.g., over a network, e.g., Transmitted to a third-party device management system.

[0233] At block 414A, the device 300 includes a registration module 312, a processor 302, a communication The module 308 includes a means for receiving a third-party subscriber registration response. The Third Party Subscriber Registration Response is used by the Third Party Device Management System to register the Third Party Information, data, etc. indicating successful creation of the subscriber profile data object. The third party subscriber registration response may include third party subscriber profile data. The data object is associated with extracted subscriber information, such as a subscriber identifier data object. Therefore, the third-party subscriber registration response may include information indicating that the third-party subscriber registration response is attached to the third-party subscriber. is then associated with the extracted subscriber information, such as a subscriber identifier data object. The subsequent third-party registration status response data object will be This may indicate that the data will identify a subscriber profile data object. Thus, in some embodiments, the apparatus 300 then generates a subscriber identifier data object and other subscriber information to create a new third-party subscriber profile data set. Get the data object or the newly created third-party subscriber profile. You can retrieve the third-party registration status associated with a mobile data object. can.

[0234] Returning to decision block 410A, the third party registration status is set to third party subscription. If the user profile data object indicates that it exists, the flow blocks. 416A. At block 416A, the device 300 registers the registration module 312, the processor Specifically, third-party participants, such as the DPPMS subscriber profile data object based on the subscriber profile data object In a particular example, the device 300 includes a means for updating a third-party object. Based on the subscriber profile data object or other information received, device 30 DPPMS subscriber profiles that are directly managed or otherwise controlled by the Alternatively, the method may include means configured to update the data object. In some embodiments, device 300 may be associated with or connected to device 300. Identifying one or more subsystems that are otherwise capable of communicating with the For some or all of the systems, the D associated with the identified subsystems Updates or causes updates to a PPMS subscriber profile data object. In a particular example, the device 300 may include means configured to a payment subsystem associated with the device 300; and a policy subsystem associated with the device 300. , the device 300 may then identify the first D associated with the payment subsystem. Associated with the PPMS subscriber profile data object and policy subsystem and a second DPPMS subscriber profile data object, or In some embodiments, the device 300 may be configured to generate updates from the identification. A new DPPMS subscriber profile associated with the identified DPPMS subsystem By creating or causing the creation of a data object, the device 30 DPPMS subscriber profile data object associated with a particular subsystem of 0 In other embodiments, the device 300 may be configured to update the subsystems. Identifies the associated DPPMS subscriber profile data object and DPPMS subscriber profile based on party subscriber profile data object By synchronizing the data objects associated with the DPPMS subsystem, The DPPMS subscriber profile data object may be configured to update the DPPMS subscriber profile data object. In the exemplary system, the device 300 directly controls each subsystem independently and / or or sub-systems so that each subsystem can be controlled by the same provider entity. Communicate with the system.

[0235] The system synchronization events described above with respect to blocks 412A, 414A, and 416A are examples and may involve alternative system synchronization events or system synchronization that utilize additional steps. It should be understood that other events may also be performed. For example, in some embodiments, The block 416A includes one or more DPPMS subscriber profile data objects. The third-party subscriber registration response is updated after block 414A. Therefore, the spirit and scope of the disclosure herein is limited to the exemplary embodiment illustrated in FIG. The details of the block are not limited to the specifics.

[0236] Referring now to FIG. 4B, at block 402B, the device 300 registers the , the processor 302, the communication module 308, etc., The cancel registration request data object includes means for receiving the cancel registration request data object, for example: The user and / or client device is subscribed to a device protection program. may indicate that they are canceling the session (in other words, the subscriber (The device will no longer be actively covered by the device protection program.) In the received cancel registration request data object, the received cancel registration request data object includes subscriber information. The collected subscriber information is associated with the device protection program and the human subscriber or subscribers. The received subscription may include a subscriber identifier data object that uniquely identifies the device. Examples of user identifier data objects include subscriber names (e.g., person or entity names) ) Subscriber contact information, subscriber device IP address, subscriber device International Mobile Equipment Identifier The present invention may be embodied in any one or a combination of the following: In this case, the Cancel Registration Request Data Object is used to cancel the subscription to the Device Protection Program. The registration function in Figure 4A includes an IMEI that uniquely identifies the registered client device. Similarly, a cancellation request may be made at any time.

[0237] At block 404B, the device 300 includes a registration module 312, a processor 302, a data The data store management module 310, etc., receives the cancellation request data object. The device management system may include means for identifying a third-party device management system associated with the device. In some embodiments, the apparatus 300 may include a cancel registration request data object. The method may include means for extracting a third-party device management system identifier from the object. In another embodiment, the apparatus 300 may include a Based on the information, a third-party device management system identifier may be determined. The device management system identifier is available for transmission to a third-party device management system. or a service associated with a third-party device management system identifier. Used to determine the communication protocol for communicating with third-party device management systems In certain examples, the third-party device management system may and / or the client device subscribes to the Device Protection Program via (e.g., mobile carrier systems, device manufacturers, and sales systems, etc.) associated with a third-party entity (via

[0238] In block 406B, the device 300 includes a registration module 312, a processor 302, and a , a third-party device management system, such as a communication module 308, means for transmitting a registration status request data object. The Enrollment Status Request data object is used to notify the third-party device management system about the enrollment status. in the registration / subscription request, such as a subscriber identifier data object or other subscriber information obtain and / or identify third-party status associated with your information; In an exemplary embodiment, the device 300 may be configured to retrieve an extracted ID, such as an IMEI. the third-party subscriber profile associated with the subscriber identifier data object Third-party registration status request data that determines whether a data object exists A data object may be created.

[0239] At block 408B, the device 300 includes a registration module 312, a processor 302, a communication Third-party registration from a third-party device management system, such as module 308 means for receiving a status response data object. The status response data object contains the transmitted third-party registration status request data. The third-party subscriber profile associated with the information provided in the data object. It may indicate the third-party registration status, such as whether the data object exists. For example, if a third-party subscriber profile data object exists, The Third Party Registration Status Response Data Object contains the third party subscriber profile. Third-party subscriber profile data object information A subset (e.g., a third-party subscriber profile data, not the entire profile) Part of the Subscriber Profile Data Object, or a third-party subscriber profile data object The information may include equivalent information in either the object or a subset of the information. Instead, the third-party registration status response data object is Registration status and associated status flags, e.g., third-party subscriber profiles Verify that the file data object does not exist in the third-party device management system. 0 represents, and the third-party subscriber profile data object is a third-party It may contain a bit flag where 1 represents presence in the device management system.

[0240] Flow then continues to decision block 410B. At decision block 410B, flow continues to decision block 410B. The third-party registration status reported is stored in the third-party subscriber profile data object. In either case, device 3 continues based on whether the 00 synchronizes one or more systems based on the received third-party registration status For illustrative purposes, blocks 412B, 414B, and 416B provide two specific examples of system synchronization events.

[0241] At decision block 410B, the third party registration status is determined to be a third party subscriber profile. Verify that the profile data object exists in the third-party device management system. If so, flow continues to block 412B. At block 412B, device 300 System synchronization events, such as module 312, processor 302, and communication module 308. specifically, to provide third-party access to third-party device management systems. means for transmitting an admission cancellation request data object. In this embodiment, the device 300 also stores a third-party subscriber cancellation request data object. Generate and / or provide subscriber identifier data objects to third-party device management systems. Third-party subscriber profiles associated with the extracted subscriber information, such as This may include deleting or otherwise terminating the file data object. and means for configuring the third-party registration request to be canceled. In this embodiment, the device 300 may communicate the subscriber identity to a third-party device management system in other ways. Third-party data objects associated with the extracted subscriber information, such as identifier data objects Deleting or otherwise terminating a subscriber profile data object A third-party subscriber registration request data object configured to cause cancellation may include: Generated or determined third-party subscriber cancellation request data The object can then be sent to a third-party device management system, such as over a network. is transmitted to.

[0242] At block 414B, the device 300 includes a registration module 312, a processor 302, a communication a means for receiving a third-party subscriber cancellation response, such as module 308; The Third Party Subscriber Registration Response is used by the Third Party Device Management System to register the Third Party Information indicating successful cancellation of the party subscriber profile data object , data, etc. Thus, the third-party subscriber cancellation response may include the subscriber Subsequent third-party data objects associated with the extracted subscriber information, such as identifier data objects, A party registration status response data object exists associated with the subscriber information. indicates that there are no third-party subscriber profile data objects associated with it. It can be shown that

[0243] At decision block 410B, the third party registration status is determined to be a third party subscriber profile. The profile data object must not exist in any third-party device management system If so, flow continues to block 416B. To perform system synchronization events, such as the registration module 312, the processor 302, etc. Specifically, one or more DPPMS subscriber profile data objects (single or multiple) For example, the device 300 may include a means for canceling a plurality of Identifies one or more DPPMS subsystems to which it is attached, and For some or all identified subsystems, the DPPMS participants associated with means configured to cancel an entrant profile data object. In a particular example, the device 300 may include a DPPMS payment subsystem associated with the device 300. and the DPPMS policy subsystem associated with the device 300. The device 300 then connects to the first DPP associated with the DPPMS payment subsystem. Associated with MS subscriber profile data object and DPPMS policy subsystem The second DPPMS subscriber profile data object is set to cancel the In some embodiments, the device 300 may be associated with a subsystem. Cancel and erase the DPPMS subscriber profile data object that has been By marking it as otherwise terminated, the DPPMS subsystem and its associated Configured to cancel the attached DPPMS subscriber profile data object. Thus, in some embodiments, after a system synchronization event, device 3 00 and / or the DPPMS managed by one or more subsystems of device 300 The subscriber profile data object is used to store the subscriber's profile information from the device protection program. In the exemplary system, the device 300 and each associated subsystem The systems are controlled by the same provider entity.

[0244] The system synchronization events described above with respect to blocks 412B, 414B, and 416B are examples and may involve alternative system synchronization events or system synchronization that utilize additional steps. It should be understood that other events may also be performed. For example, in some embodiments, Block 416B is configured to allow one or more DPPMS subscriber profile data objects to be Block 41 4B. Therefore, the spirit and scope of the disclosure herein is not limited to the example shown in FIG. Do not be limited to the details of the example blocks shown.

[0245] FIG. 4C illustrates an exemplary data flow for registration synchronization, according to an exemplary embodiment of the present disclosure. Illustrative diagrams illustrate exemplary data flows between the DPPMS and / or third parties. DP to synchronize the subscriber profile(s) in the device management system Depicts the actions performed by a subsystem of a PMS or DPPMS. The actions of the Service or a particular Service may be at the discretion of the DPPMS or any part of the DPPMS. Performed, executed, or simulated by a subsystem For example, the registration service 450C and / or the cancellation service 452C may This may be performed by the DPPMS embodied by the device 300. C can be used to enroll an unregistered device into the device protection program. For example, The device identifier is used to register the corresponding unregistered device with one or more device protection programs (single The device may be received in association with an unregistered device to register with the device (one or more devices).

[0246] For example, as illustrated, FIG. 4C depicts a registration service 450C. Service 450C is performed by the DPPMS or any subsystem within the DPPMS ( perform, execute, or start, and device identifier, subscription DPPMS and third-party systems based on user identifiers (e.g., specific IMEI) Additionally or alternatively, in some embodiments, the registration Recording service 450C may be performed by the DPPMS or any subsystem within the DPPMS. perform, execute, or initiate a particular subscriber identification DPP based on registration subscription request associated with child, device identifier, etc. The MS may synchronize with a third-party system. The cancellation service 452C is shown as DPPMS or DPPM Perform, execute, by any subsystem in S, or initiated to communicate with the DPPMS and third parties based on device identifiers, subscriber identifiers, etc. Additionally or alternatively, some implementations may In form, cancellation service 452C is a cancellation service for the DPPMS or any sub-service within the DPPMS. Performed, executed, or initiated by the system , cancel subscriptions associated with a particular subscriber identifier, device identifier, etc. The DPPMS may synchronize with third-party systems based on application requests. In the illustrated embodiment, the registration service 450C and / or the cancellation service 452C may include one or more DPPMS subsystems 452C and / or third-party devices. The management systems 454C may be synchronized.

[0247] In an exemplary aspect, in some embodiments, the registration service 450C or cancellation Service 452C is used during subscriber registration, billing fraud analysis, or initiation of billing processing protocols. For example, in some embodiments, the DPPMS may include a device identifier data object. The device may receive a billing data object associated with the device identifier data object. The data object uses the subscriber identifier data object to process the billing data object. It may be associated with a subscriber identity data object or may represent a subscriber identity data object. The PMS stores subscriber profile data associated with the subscriber identifier data object. Query the Device Protection Program subscriber device database for the object and The device protection program database does not contain a subscriber profile data object. In this regard, the registration service 450 or the cancellation service 450 may receive result data indicating that The rule service 452C may be initiated upon receipt and / or analysis of the results data.

[0248] Referring first to the registration service 450C, in block 402C, the device 300 module 312, fulfillment module 314, fraud module 316, error module 31 8, processor 302, etc., or a combination thereof. In some embodiments, the device identifier includes means for receiving a device identifier. , a third-party device management system that provides information for the registration of new subscribers, e.g. For example, it may be received from a third-party device management system 458C. The device 300 identifies or obtains a device identifier as part of a routine synchronization service. For example, a device identifier may be received by a DPPMS or a subroutine within the DPPMS. At specific intervals (e.g., daily, weekly, etc., at a specific time), the system The device may synchronize the registration of all device identifiers in use.

[0249] In block 404C, the device 300 executes the registration module 312, the fulfillment module 314, Any of the fraud module 316, the error module 318, the processor 302, etc. Registered through a third-party device management system, such as one or a combination of Included are means for receiving a registration status. As illustrated, for example, The information may be obtained from a third-party device management system 456C. The device management system 456C associates the device identifier obtained in block 402C with Specific third-party devices associated with the Device Protection program on the device For example, a third-party device management system 456 may be implemented. C may embody a system, server, etc. associated with the device manufacturer. The DPPMS uses the subscriber profile stored by the DPPMS to manage the device. Third-party subscriber profile data managed independently from the file data object In some embodiments, the device 300 may store a third-party The enrollment status is reported to the device management system by transmitting an enrollment status request. Get it.

[0250] The registration service 450C then determines the flow of operations based on the obtained registration status. For example, as depicted, the obtained registration status may be determined based on the device identifier indicates that the device is registered by a third-party device management system 456C (e.g. For example, if there is an associated third-party subscriber profile data object If so, flow may continue at block 406C. 300 includes a registration module 312, a fulfillment module 314, a fraud module 316, an error module 318, processor 302, etc., or a combination thereof. Registration status received from a third-party device management system 456C, such as Synchronize the DPPMS and / or one or more DPPMS subsystems based on the For example, registration status may be recorded in a third-party subscriber profile. It can contain data objects or corresponding data, which can be used to a corresponding subscriber profile data object managed by the MS and / or One or more subscriber profiles managed by one or more subsystems of the DPPMS For example, the device 300 may synchronize data objects. The information stored in each subscriber profile data object in 54C may be used by third parties. D to match the information associated with the subscriber profile data object. The subscriber profile data objects of each of the PPMS subsystems 454C are synchronized. It is possible.

[0251] The flow instead checks whether the registration status is correct and whether the device identifier is a third-party device. indicates that it is registered with the service management system 456C (e.g., the associated service If the third-party subscriber profile data object does not exist, Block 404C may be followed by block 408C. In an exemplary embodiment, In this situation, the device 300 includes a registration module 312, a fulfillment module 314, a fraud module 316, and a 316, error module 318, processor 302, etc., or Device identification via a third-party device management system, such as a combination of these In this regard, the device 300 may include means for requesting one or more , and transmits a signal to the third-party device management system 456C to identify the device. Causes the creation of a third-party subscriber profile data object associated with the child In response to such attempt(s), the device 300 may The successful creation of a Party Subscriber Profile Data object or one or more A confirmation may be received in return indicating that the above transmission error(s) occurred.

[0252] In some embodiments, the registration service 450C may also include a classify the error handling instructions (single or multiple) and / or one or more associated error handling instruction sets (single or multiple) The system may be configured in association with an error handling system for performing one or more of the following: , the received error may be classified and / or handled by one or more actions. The processing action is performed by an error handling system associated with the registration service 450C. may occur and / or arise.

[0253] Additionally or alternatively, in some embodiments, the device identifier may be A billing data object representing a user bill may include means for initiating a billing processing instruction set. A billing instruction set may be associated with one or more system synchronization events. In an exemplary aspect of the Mobile Device Pro, the billing instruction center The company will verify that the charge is not fraudulent or provide services to the mobile device. , for processing and / or transmitting information for exchanging mobile devices, etc.; A billing instruction set may contain one or more billing processing events. Subscriber profile data objects (which may be created and / or synchronized later) It can be started without

[0254] In some embodiments, registration 450C may be performed by a trusted third-party device management system. From the system, for example, from a third-party device management system 456C instead of 458C You receive the device identifier directly from the device in the form of a registration subscription notification. In such an embodiment, the registration service 450C may register one or more system synchronization events as with subsequent approval by the third-party device management system from which it was received In this regard, in some such embodiments, the registration service 45 0C will create new and / or existing subscription profiles (single or multiple) ) to one or more new devices identified by the received registration subscription notification. By enrolling in the Device Protection Program, you are granting access to the DPPMS and / or one or more DP The process may proceed immediately to block 406C to synchronize the PMS subsystems.

[0255] Referring now to the registration service 452C, in block 410C, the device 300 module 312, fulfillment module 314, fraud module 316, error module 31 8, processor 302, etc., or a combination thereof. In some embodiments, the device identifier includes means for receiving a device identifier. From a third-party device management system that provides information for new subscriber registration For example, a third-party device management system 458C may receive the device information. The device 300 identifies or obtains a device identifier as part of a routine synchronization service. For example, a device identifier may be received by a DPPMS or a subroutine within the DPPMS. The system will automatically generate new cancellations at specific intervals (e.g., at specific times each day or week). All device identities associated with the registered subscriber profile data object. Cancelled registrations of children may be synchronized.

[0256] In block 412C, the device 300 executes the registration module 312, the fulfillment module 314, Any of the fraud module 316, the error module 318, the processor 302, etc. Registered through a third-party device management system, such as one or a combination of Included are means for receiving a registration status. As illustrated, for example, The information may be obtained from a third-party device management system 456C. The device management system 456C associates the device identifier obtained in block 402C with Specific third-party devices associated with the Device Protection program on the device For example, a third-party device management system 456 may be implemented. C may embody a system, server, etc. associated with the device manufacturer. The DPPMS uses the subscriber profile stored by the DPPMS to manage the device. Third-party subscriber profile data managed independently from the file data object In some embodiments, the device 300 may store a third-party The enrollment status is reported to the device management system by transmitting an enrollment status request. Get it.

[0257] The cancellation service 452C then determines the flow of action based on the obtained registration status. For example, as shown, the obtained registration status may determine the Verify that the identifier is not registered by a third-party device management system 456C. indicates (e.g., the associated third-party subscriber profile data object If so, flow may continue at block 414C. In this example, the device 300 includes a registration module 312, a fulfillment module 314, and a fraud module 316. 16, error module 318, processor 302, etc., or received from a third-party device management system 456C, such as a combination of Based on registration status, the DPPMS and / or one or more DPPMS subsystems For example, the device 300 may include a DPPMS and / or a 1 One or more existing subscriber profiles managed by one or more DPPMS subsystems Identify the subscriber profile data object, delete the subscriber profile data object, and delete Mark each registered or subscriber profile data object as It can be marked as not available.

[0258] The flow instead checks whether the registration status is correct and whether the device identifier is a third-party device. indicates that it is registered with the service management system 456C (e.g., the associated service If the third-party subscriber profile data object does not exist, Block 412C may be followed by block 416C. In such a situation, the device 300 may: Registration module 312, fulfillment module 314, fraud module 316, error module 318, processor 302, or the like, or a combination thereof. Cancel the registered device identifier through your third-party device management system. In this regard, the device 300 may include means for attempting to receive one or more requests, signals, etc. and transmit the device identifier and associated information to the third-party device management system 456C. Clears the attached third-party subscriber profile data object and marks it as unregistered. Such an attempt ( In response to the third party subscriber profile data, the device 300 The object is either successfully erased or canceled, or one or more A confirmation may be received in return indicating what was indicated as a transmission error(s).

[0259] In some embodiments, the cancellation service 452C may be a trusted third party. From a device management system, for example, a third-party device management system instead of the 458C The device identifier is received directly from the system 456C in the form of a registration cancellation notice. In one such embodiment, the cancellation service 452C may include one or more system synchronization The event is then forwarded to the third-party device management system from which it was received. In this regard, in some such embodiments, Cancellation service 452C proceeds immediately to block 414C to retrieve the corresponding registered sub- By canceling your subscription profile, you are agreeing to the terms and conditions of the DPPMS and / or One or more DPPMS subsystems may be synchronized.

[0260] Error Classification and Handling FIG. 9 illustrates an exemplary system within which embodiments of the present disclosure may operate in accordance with the disclosure herein. 9 illustrates a block diagram of a system for detecting a failed transmission.

[0013] An example of a method for receiving, classifying, and / or managing received transmission errors resulting from a transmission As illustrated, the entitlement management subsystem 902 includes an exemplary It may communicate with a third-party device management system 912. The hardware is used to facilitate error management and reporting, as described below. and / or software running on hardware In some embodiments, the enrollment management system 902 may include a number of services that may be provided. Maintenance and tracking on the Registration Management System without loss of functionality to the rest of the PPMS It functions and communicates with one or more other It can run as a separate service that can be maintained independently of the other services. In an embodiment, the enrollment management subsystem 902 may be implemented, for example, as described with respect to FIG. One or more executed actions run in a process instance.

[0261] In an exemplary embodiment, the enrollment management subsystem 902 is configured to manage the device 300 or the device 30 0, one or more modules, such as the registration module 312, the processor 302, the error In other embodiments, the enrollment management subsystem may be embodied by the enrollment management module 318 or the like. System 902 may be a subsystem associated with device 300. In this case, the enrollment management subsystem 902 and / or one of the enrollment management subsystems 902 The above components may be one or more specifically configured with the components listed therein. For configured cloud systems including remote and / or "cloud" servers Similarly, in some embodiments, execution and / or One or more microservice subsystems for fraud prevention are deployed via specially configured remote The software may be implemented on a remote and / or cloud server.

[0262] The registration management subsystem 902 communicates with third party devices via a network 914. The device management system 912 may be configured to communicate with a third-party device management system. The system is enrolled in the Device Protection Program via a third-party device management system. one or more third-party subscriber profile data associated with one or more subscribers For example, the third-party device management system 912 may Enrolled in the Device Protection Program through a third-party system or entity A database or database containing all third-party subscriber profile data objects The device may be configured to maintain a list.

[0263] The registration management subsystem 902 communicates with a third-party device management system 912. one or more DPs containing one or more DPPMS subscriber profile data objects. It may verify, validate, or update a PMS subsystem, e.g., Registration Management Subsystem 9 02 communicates with the third-party device management system 912 to generate a new registration management request data. The registration management request data object being received and / or processed. The third-party registration status associated with the object may be configured to validate the third-party registration status associated with the object.

[0264] As illustrated, the registration management subsystem 902 includes a registration processing microservice 904. , an error handling service 908, an error configuration service 906, a data store 910, and The registration processing microservice 904 may include a reporting solution 909. maintain an action queue configured to store record management request data objects; Additionally or alternatively, a registration processing microservice 9 04 processes any outstanding registration management request data objects from the action queue. The process may be configured to manage one or more action process instances configured as follows: do.

[0265] Sends outstanding actions, such as registration management request data objects, to the registration processing microservice. During processing via network 910, enrollment management subsystem 902 4. The Enrollment Management Subsystem The system 902 may, for example, provide a third-party device management system 912 with Registration Status Request Data Object, Third Party Subscriber Registration Request Data Object object, a third-party subscriber cancellation request data object, or other subscription management request The request may be configured to transmit one or more from a group containing the data object.

[0266] However, there are countless computer problems involving networking, communications, power, or other issues. Due to routing issues, transmissions may be blocked by the third-party device management system 912. and / or a third-party device management system 912 As a result of the failed transmission, the registration management subsystem System 902 identifies and receives transmission errors resulting from failed transmissions or other A failed transmission may be due to software failure, hardware failure, and / or may experience various types of transmission errors, including but not limited to third-party submission failures. It can come from Ra.

[0267] The error handling service 908 identifies the occurrence of such transmission errors, receives, or Additionally or alternatively, some In this embodiment, the error handling service 908 may comprise error handling logic. In certain embodiments, the error handling logic associated with the error handling service 908 includes: The system may be configured to associate a transmission error with an error configuration. The linking is used to classify received transmission errors and / or to identify transmission errors. One or more error handling actions may be identified to perform in response.

[0268] The error handling service 908 utilizes the error configuration service 906 to handle errors based on transmission errors. For example, the error handling service 908 may be configured to identify an error configuration based on the , the error code and / or or error message, where the error code, error message , or a combination thereof, to identify the associated error configuration. The configuration shall include at least the error code and / or error message of the associated transmission error. messages and associated error classifications associated with transmission errors, or In some embodiments, the error configuration may also include an error handling protocol. associated with or identifying an error handling instruction set that embodies For example, in some embodiments, the error configuration may include information that distinguishes between errors that are executed. The maximum retry threshold for use in the error processing instruction set may be included.

[0269] The error handling logic works in conjunction with the error configuration service 906 to configure one or more error handling Identify, determine, or specify an error handling instruction set that represents an error handling protocol, including events. For example, the error handling service 908 may retrieve an error associated with a transmission error. Associated with information contained in or otherwise identified in the error configuration, such as classification The error handling instruction set may be identified.

[0270] The error handling service 908 generates one or more error handling instructions based on the identified error handling instruction set. The error configuration can be configured to perform an error handling event. In the specific case where a transmission indicates a possible error, the error handling service may decide to Identifies whether the associated maximum retry threshold has been exceeded, and if not, Identifies the request retry time and sends the failed transmission back to the transmission queue after the determined retry time. The error configuration can be configured to treat a transmission error as an escalation error. Another specific example shows that the error handling service escalates a failed transmission. The escalation queue may be configured to add or otherwise insert the escalation queue. The application queue can be routed to a third-party entity or another third-party for error handling. It may store one or more failed transmissions that require attention by the system. In an embodiment, the error handling service 908 may process one or more errors associated with a transmission error. The device may be configured to generate or identify a report.

[0271] The error handling service utilizes a data store 910 to store and and / or manage one or more action cues. The data store 910 allows one or more users to interact with the registration management subsystem to create a reporting solution. The error report is stored so that it can be retrieved via the solution 909. For example, the reporting solution 909 may be configured to access the data store 910. The reporting solution 909 may be configured to allow users to: The service detects one or more transmission errors, such as an escalation error in the escalation queue. The system may be configured to allow escalation to a third-party entity. For example, the reporting solution 909 allows error escalation requests to be forwarded to a third-party device. a third party error management system 912, or a third party error system (not shown). the third party device management system 912 and another third party system associated with the By sending a message, you can escalate a transmission error in the escalation queue. In some embodiments, the escalation queue may be configured to Errors in the calculations can be handled via one or more human operators, and the queue can be may be changed or otherwise updated via advertising solution 909.

[0272] FIG. 5 illustrates an error classification and propagation method received by a DPPMS in accordance with the present disclosure herein. 1 illustrates acts in a simplified exemplary process for handling transmission errors. The operations illustrated and described with respect to 5 are implemented using the registration management subsystem illustrated in FIG. 9 and described above. The device 300 includes hardware and / or software embodying the system 902. For example, certain exemplary embodiments may be implemented by a DPPMS embodied in In this example, the registration module 312, the error module 318, the processor 302, the communication module The data store management module 310, the data store management module 310, and / or a combination thereof may , configured to embody the enrollment management subsystem 902 as described above with respect to FIG. obtain.

[0273] In block 502, the device 300 sends a failed request to a third-party device management system. an error module 318 for receiving a third-party transmission error in response to the transmission; The device 30 includes a processor 302, a communication module 308, and other means. The DPPMS embodied by 0 is a Third Party Enrollment Management Request Data Object to a third-party device management system, lose connection, or otherwise Receive a corresponding third-party enrollment management response from the third-party device management system. Therefore, without receiving such a response, the device The DPPMS embodied by 300 allows third-party device management systems to Respond to the third-party registration management request data object and successfully perform the required action may remain unaware as to whether or not

[0274] At block 504, the device 300 may include an error module 318, a processor 302, etc. means for identifying an error classification associated with a third-party transmission error; In certain embodiments, the apparatus 300 may generate an error classification set including one or more error classifications. and identifying an error classification from the error classification set. Examples of error classification sets include: Some examples include "retryable errors" and "escalation errors." In an embodiment, the device 300 may detect a failed transmission, a third party transmission error, a failed transmission, Identifying error classifications based on the subscriber information associated with the In some embodiments, the device 300 may include an error module 318, a processor The system includes a means for identifying an error configuration associated with a transmission error, such as a transmission error detection unit 302 . In some embodiments, the error configuration comprises at least one error configuration, each error configuration associated with a transmission error. Also includes an error classification, and a maximum retry threshold.

[0275] In an exemplary aspect, the errors are "retryable errors" and "escalation errors." A classification may include one or more sub-classifications. For example, the device 300 may escalation that identifies the specific third-party error handling device intended to An example of such an error classification is the "Point of sale escalation error" and "manufacturer escalation error" were cited. Point of sale escalation errors include, but are not limited to: Third-party devices, such as third-party device management systems, that embody point-of-sale systems Poorly formatted, incomplete, or otherwise unusable media from your system. This may indicate that unusable or bad data has been received. A management escalation error is a failure to report a request to the carrier entity that transmitted the initial request for manual intervention. escalation to a third-party error handling system, such as a system controlled by an entity Manufacturer Escalation Errors may be associated with an error configuration requiring escalation. For example, a third-party entity associated with a particular subscriber device manufacturer entity. It can indicate that the request requires data that is available from the data system, and is a third-party error handling system controlled by a third-party entity This may be associated with a configuration that requires escalation of the error to

[0276] Similarly, the device 300 may generate retryable errors associated with a particular set of error handling instructions. Error classification can be maintained, e.g., if a subsequent retry of a failed transmission is unsuccessful. In such cases, the error handling instruction set further defines the error handling protocol. Examples of classifications are "system retryable errors" and "ineligible errors after retry" Retryable errors in the system include, but are not limited to, failures in transmission. It may indicate that the field format and / or data format contains errors. and continuously based on one or more retry protocols, such as using exponential backoff. Retry may be possible. Any ineligible errors after a retry may be resolved through one or more retry attempts. If not, it can indicate that no action can be taken on the error. before being marked as ineligible or receiving a new ineligible error. The request may be retried up to a maximum retry threshold (eg, one retry in some embodiments). An ineligible error is one in which no action is required to handle such an error. may not be associated with any particular configuration that does not include any error handling instruction set. For example, the following may be related to a subscriber device that cannot be enrolled in a particular device protection program: A related ineligible error may be received.

[0277] At block 506, the device 300 may, for example, include an error module 318, a processor 300, 2, defined by the error handling instruction set associated with the identified error classification. Each error category includes one or more error handling protocols. It may be associated with one or more error handling protocols, including the above error handling events. For example, the error handling protocol associated with the "retryable" error classification is at least In both cases, it is possible to identify a retry time and to allow a failed transmission to be attempted for transmission after the retry time has elapsed. This may include queuing for a retry and waiting a retry time. The error classification and associated error handling protocols are used to classify transmission errors as errors. In some embodiments, the device 300 may include inserting the , for example, by accessing an error database via a data store to retrieve the identified errors. An error handling protocol associated with the class may be identified.

[0278] At block 508, the device 300 may include an error module 318, a processor 302, etc. , initiate one or more of the error handling events contained in the identified error handling protocol. For example, the device 300 may include means for initiating a retry for a retryable error. Identifies the time at which a failed transmission is placed on the transmission queue for retransmission after the retry time has elapsed. The apparatus 300 may also include means configured to place the For escalation errors, the transmission error is configured to be inserted into the escalation queue. The present invention may include a means for performing the above-mentioned steps.

[0279] At block 510, the device 300 may include an error module 318, a processor 302, etc. means for generating an error report based on a received third-party transmission error; Error reports include information about third-party transmission errors, error classifications, and identified errors. It may contain information and / or metadata related to the processing instruction set, etc.

[0280] At block 512, the device 300 may include an error module 318, a processor 302, etc. , and means for storing the generated report in an error database. In an embodiment, a single data store stores error reports along with all other stored data. In other embodiments, the error database is configured to store other data. The error report is separate from the type of subsequent third-party transmission of the same type. Capture errors as they occur and classify and / or process such transmission errors Error reports are sent to the third party so that they can be used to improve the efficiency of the The party may store associated information and / or metadata based on the transmission error. In another embodiment, the error database acts as an error log of received errors. As such, an error report is generated and added to the error database.

[0281] A DPPMS, such as the DPPMS embodied by device 300, may be provided by a third-party device. Attempted transmission to a third party system, such as an Internet service management system, e.g., Figures 4A and 4B. and transmission errors, or any other messages received during the process illustrated by FIG. 4B. A transmission received in response to a transmission error received related to a message or synchronization failure. To handle the error, one or more of the actions illustrated in FIG. 5 may be performed. Therefore, Figure 6 shows the registration management and execution to improve the robustness and efficiency of the overall system. A DPP such as a DPPMS embodied by apparatus 300 configured for raster processing 1 illustrates an exemplary detailed process including operations that may be performed by an MS.

[0282] In block 602, the device 300 sends a failed request to a third-party device management system. an error module 318 for receiving a third-party transmission error in response to the transmission; The processor 302, the communication module 308, etc. The DPPMS embodied by the device 300 receives the third party registration management request data object. Transferring objects to a third-party device management system and losing connectivity or other Third-party registration management according to the law through third-party device management systems It may be impossible to receive a response.

[0283] At optional block 604, the device 300 may include an error module 318, a processor 30 To generate error reports based on received third-party transmission errors, such as In optional block 606, the device 300 includes an error module 304. 18, the processor 302, the data store management module 310, etc., generated errors means for storing the report in an error database; The error may be recorded in an error database for future audit and / or error handling. For example, a user may submit one or more error reports for errors they have received but have not categorized. Error classification and / or processing determined by the user as appropriate to consider and handle transmission errors. Or, a corresponding error configuration including an error handling instruction set may be allocated.

[0284] At block 608, the device 300 may include an error module 318, a processor 302, etc. means for identifying an error classification associated with a third-party transmission error; In the illustrated example, as described above, the error classification is at least "retryable" errors. -classification and "escalation" error classification. In other embodiments, additional or alternative error classifications may be included in the set of error classifications. - Processing classification includes information and / or data associated with transmission errors and / or failed transmissions. For example, in some embodiments, device 300 may be identified based on the metadata. may extract an error identifier from the transmission error for use in identifying the transmission error. In another embodiment, the device 300 determines the transmission type associated with the failed transmission. and transmission type alone or in combination with other factors such as error identifiers to determine the error classification. It can be used in combination with information.

[0285] At block 610, the device 300 may include an error module 318, a processor 302, etc. means for identifying an identified error classification and an associated error handling protocol; The error handling protocol may be represented by a set of instructions for resolving the error. In some embodiments, the error handling protocol instruction set begins at block 612. may include retry and / or escalation instructions, such as the following exemplary protocol: The identified error handling protocol is determined at decision block 608, as illustrated. For example, as illustrated, escalation error handling The protocol may be identified in association with an escalation error classification, where escalation The localization error handling protocol includes at least one or more error handling blocks, such as block 614. Alternatively, as illustrated, a retryable error handling process may be used. Protocols may be identified in association with retryable error classifications, where retryable The error handling protocol includes at least one of blocks 616-630 and 614. Includes the above error handling events.

[0286] Referring to decision block 612, the identified error classification is used to determine whether the error classification is correct (e.g., the received transmission error). The error code and / or error message of the transmission error are used to identify the error configuration. If the error is an escalation error (from the creation of the flow), the flow This is followed by block 614, which implements a single error handling event in the protocol. At 614, the third-party transmission error is added to an escalation queue. In some embodiments, the device 300 manages an escalation queue and configured to transmit errors in the application queue to one or more third-party servers In some embodiments, the device 300 may report the error to a third-party error handling system. and automatically escalate responses from third-party error handling systems In other embodiments, the escalation queue may also include means for receiving the escalation information. The calibration error occurs when a DPPMS, such as the DPPMS embodied by the device 300, is Human operators through a third-party error handling system The escalation error is resolved by manual intervention, such as by a supervisor. The error handling protocol ends here, but other escalation error handling protocols continue. , it should be understood that additional or alternative error escalation steps may be included.

[0287] Returning again to decision block 612, if the error classification is determined to be a retryable error, If so, flow continues to block 616, where blocks 616-630 and 614 The instantiated error handling protocol associated with the instantiated retryable error. Implements the first error handling event in

[0288] At block 616, the device 300 may include an error module 318, a processor 302, etc. , means configured to identify a maximum retry threshold. The maximum retry threshold is determined by the device 30 0 defines the maximum number of retransmission attempts that can be made for a particular transmission error. In an embodiment, all retryable errors are associated with a predetermined maximum retry threshold. In other embodiments, the maximum retry threshold associated with a retryable error may be: Current date timestamp, server load, escalation queue length, retransmission queue length This may be determined based on various factors such as:

[0289] In some embodiments, the maximum retry threshold is the number of times the device 300 detects a received transmission error and A timestamp representing a particular length of time that the associated failed transmission may continue to be retried. The time period embodied by the maximum retry threshold represents the time between retry attempts. may represent a predetermined timestamp interval set by the user. In addition, the maximum retry threshold is based on the current date timestamp, server load, and escalation. by the device 300 based on one or more factors such as the transmission queue length, retransmission queue length, etc. It may represent a timestamp interval to be determined.

[0290] At block 618, the device 300 may include an error module 318, a processor 302, etc. , means for identifying the number of retry attempts. Configured to track the number of transmission attempts that represent the number of retry attempts associated with a failed transmission Thus, in some embodiments, the DPP embodied by the device 300 If the MS has not yet attempted to retransmit a failed transmission, it is assigned a retry attempt count of zero. In other embodiments, the number of retry attempts may be set to a predetermined number (e.g., 5 attempts). The number of retry attempts is set to 0 (retry attempts) and decremented after each retry. It may represent the number of remaining retry attempts.

[0291] At block 620, the device 300 may include the error module 318, the processor 302, etc. Identifying a retry-related result data object based on a retry maximum threshold and a number of retry attempts. The retry relationship result data object includes means for distinguishing between the retry relationship and the retry result data object. Identified by comparing the number of retry attempts to a maximum retry threshold, or determined in some other way. For example, a retry-related result data object may contain a retry attempt number. is greater than (or greater than) the maximum threshold, or is less than (or equal to) the maximum retry threshold. It can show whether

[0292] Alternatively, in some embodiments, the number of retry attempts may be determined for a particular failed transmission. In this regard, the number of retry attempts represents the total time spent on all retry attempts. It may be incremented by the wait time for the row iteration (if any). In the present specification, the apparatus 300 may be implemented in hardware and / or software. One or more clocks and / or timers may be configured to track the number of retry attempts. In yet another embodiment, the device 300 tracks the number of transmission attempts and is used to determine the previous wait time for one or more previous retry attempts. In such an embodiment, the retry-related result data object may include a retry attempt count, a maximum retry count, or a maximum retry count. whether a high threshold is exceeded (e.g., data showing the total time spent on retries is allowed) In some embodiments, the retry-related result data may represent the maximum time allowed for the retry. The data object is set to true when the number of retry attempts falls below the maximum retry threshold. Indicates that it will be fulfilled.

[0293] At decision block 622, the device 300 determines whether the error module 318, the processor 302, etc. Which retry relationship result data object indicates that the retry relationship is satisfied In some embodiments, for example, the retry relationship includes means for determining whether The number of retry attempts, as indicated by the retry relationship result data object, is the maximum number of retries. In another embodiment, the retry attempt count is less than a maximum threshold of retries. If the value is greater than the threshold (for example, the number of retry attempts is decremented and the maximum retry threshold is zero), or boundary number), the retry relationship is satisfied.

[0294] For example, the maximum retry threshold represents the timestamp interval, and the number of retry attempts represents the number of retry attempts after all retry attempts. In another embodiment, the number of retry attempts represents the total time spent in the retry attempt. is less than (or equal to) the maximum retry threshold indicated by the relevant result data object. The retry relationship is satisfied when the number of retry attempts is less than or equal to the number of retry attempts. If it is greater than the maximum threshold (e.g., the number of retry attempts is decremented based on the wait time), If the retry condition is met, the retry relationship is satisfied.

[0295] If it is determined that the retry relationship is not satisfied, flow continues at block 614. For example, if the retry relationship does not meet the maximum retry threshold, a retryable error is returned. The request is scalated and placed in an escalation queue, as shown in block 614. In other embodiments, retryable errors are added to an escalation queue. Before this, it may be reclassified as an escalation error.

[0296] Instead, the number of retry attempts incremented for each transmission attempt is less than the maximum retry threshold. If the retry relationship is determined to be satisfied, such as if the At block 624, the device 300 may continue with the error module 318, The retry time includes a means for determining the requested retry time, such as processor 302. The amount of time the system must wait before attempting to retransmit a failed transmission In some embodiments, the request retry time is determined based on the number of retry attempts. For example, the request retry time is relative to the previous attempt, starting from the minimum retry time. This may be based on an exponential backoff algorithm that doubles the requested retry time. For example, If the number of retry attempts is zero (e.g., the wait time before the first retry attempt), device 3 The minimum retry time is set to 5 minutes, so 00 determines the retry time to be 5 minutes. Then, if the number of retry attempts is 1 (e.g., before the second retry attempt), Retry time is 10 minutes and retry attempts is 2 (for example, before the third retry attempt) In other embodiments, the retry time is doubled so that the retry time is 20 minutes. , Alternative algorithms or rules may be utilized to determine the retry time.

[0297] At block 626, the device 300 may include the error module 318, the processor 302, etc. , and means for waiting the determined retry time. 00 may track the time elapsed since the previous transmission or retransmission attempt. By attempting other transmissions and / or performing other operations while waiting for the execution time. etc., may continue to operate.

[0298] At block 628, the device 300 may include the error module 318, the processor 302, etc. , and means for adding a failed transmission to a transmission queue. The transmission queue is a queue in which the device 300 , may include means configured to process and transmit as identified herein above and below. It may include outstanding requests to be transmitted to one or more third-party systems. After reaching the head of the queue, the DPPMS embodied by the device 300 Process the transmission and attempt to transmit it again.

[0299] At decision block 630, the device 300 determines whether the error module 318, the processor 302, A communication module, such as the communication module 308, may be used to determine whether a failed transmission has been successfully retransmitted. If the transmission was unsuccessful, flow may return to block 618. In this case, the number of retry attempts is incremented. A third-party transmission error is received and is marked as a retryable error based on the previous error classification. Alternatively, in some embodiments, the flow may continue at block 602 Other third-party transmission errors can be returned to the Whether the error is also a retryable error or a new escalation error occurs Returning to decision 630, the transmission may be reclassified to determine whether it was successfully transmitted. If so, the process ends.

[0300] A DPPMS configured to perform the operations described with respect to FIG. 6 may include processing resources effectively allocates and reduces the amount of errors that escalate unnecessarily, thus reducing the Improves the completion time for processing an administrative request data object or action such as a claim. Please understand that this can be improved.

[0301] The error handling protocol illustrated in Figure 6 and the specific error handling events illustrated in Figure 6 It should also be understood that the above are examples. error handling events, different procedures for error handling steps, and / or additional error handling events. Therefore, the spirit and scope of the disclosure of this specification is not limited to blocks 612-63. However, the present invention is not limited to the details of the exemplary error handling protocol exemplified by .

[0302] Example Scaling Service The DPPMS embodied by the apparatus 300 is a system, subsystem, or combination of systems described herein. In connection with one or more of the systems and processes, one or more receiving and / or It may include means for processing triggered actions and / or requests, for example: Registration management request data objects, claims, etc. are used by the device 30 to achieve a particular goal. This may require processing by the DPPMS embodied by .0. For example, registration subscriptions The option request confirms registration with the third-party device management system and requires DPPMS membership. Create and / or add entrant profile data objects to the DPPMS, and and / or associated with one or more DPPMS subsystems associated with the DPPMS. Processing resource for canceling a DPPMS subscriber profile data object The cancel registration request data object may require a third-party device Confirm cancellation from the DPPMS subscription management system and link to DPPMS. Cancel a User Profile Data Object and / or one or more DPPMs Key DPPMS subscriber profile data objects associated with the S subsystem. A claim may require a process to be processed to cancel the claim. to implement claims processing protocols, such as by implementing fraud prevention protocols; In some embodiments, the claim processing protocol may require the device to process a particular claim. The claim processing instruction set includes a set of instructions associated with the claim data object to be initiated.

[0303] Processing these actions requires significant processing resources and / or can be quite time consuming. In addition, in some embodiments, the pending action may require additional time. may be received in very large batches, and the action queue of outstanding actions may be It went from little to no action in the queue to significant activity in a short period of time. This can rapidly expand to a large number of outstanding actions. One or more of the third-party systems that are used to process bulk requests (e.g., during a predetermined time period during the day) time), large batches of various activities can be transmitted quickly and shall be processed without undue delay or burden to Subscriber or any third party. Therefore, the DPPMS embodied by the device 300 One or more actions associated with processing outstanding actions stored in the action queue. To manage the above action process instances, a scaled process is used as illustrated in Figure 7. It may consist of a ring service.

[0304] Referring to FIG. 7, a scaling service 702, an action queue 716, and Contains a set of action process instances, specifically the action processes that are executed. An example system is shown including instances 704, 706, and 708. Each process instance has a set of process threads 710, 712, and a set of process threads to be executed, such as 714. Scaling Service 7 02 is the maximum action process instance count, which is equal to 3 in the illustrated example , or "maximum action process." The scaling service 702 Also, the action process instance count minimum is equal to 1 as shown in the example. or "Minimum Action Process." Additionally or alternatively: , the scaling service 702 may be associated with a process thread count maximum value. Each executed action process instance must have a process thread count greater than or equal to the maximum. Process thread counts below, or in some embodiments non-inclusively below, the maximum process thread count. In some embodiments, the number of process threads for each action process executed may be The process instance is initialized with an initial number of threads based on the maximum process thread count. and / or otherwise executed. The initial number of threads in a instance may be equal to the process thread count maximum.

[0305] The action queue 716 contains one or more outstanding actions and / or outstanding It may be associated with an action type or a request type. For example, in certain embodiments, The action queue 716 is a queue of single requests, such as outstanding registration management request data objects. The request server may be configured to maintain outstanding requests associated with a request type. The action queue 716 may contain a number of request types, e.g., pending registration management request data. Data objects, escalated error transmission requests, and / or processing required It may be configured to maintain outstanding requests associated with other actions.

[0306] Each of the action process instances 704, 706, and 708 that are executed: It may be configured to process one or more request types from the action queue 716. For example, the action process instance 704 that is executed receives outstanding registration management request data. Therefore, the scaling service 70 2 indicates that at least the action process instances 704, 706, and 707 are executed. 08, which is configured to maintain a set of executed action process instances. obtain.

[0307] Each executed action process instance is Executed processes, such as the set of executed process threads 710 associated with the instance 704. The action process instance may contain a set of process threads that are executed. ,each process thread is utilized to execute actions from the action queue 716 at a particular rate. Processes any outstanding actions in a process instance, e.g., an action to be executed For 704, each executed process thread in the set of executed process threads 710 Red can be configured to process a certain number of outstanding actions per minute. Therefore, the process threads executed in a particular executed action process instance As the number of actions associated with a process instance increases, the number of actions that are executed incre...

Claims

1. 1. A system configured to detect network communication synchronization errors, comprising at least Also includes one processor and at least one memory, includes computer code instructions in said memory, said computer code instructions comprising: which, when executed by the at least one processor, provides the system with: A subscriber data object indicating a device protection program and including a subscriber identifier data object. receiving a registration management request including an object; Third Party Registration Status Request Data Object to Third Party Device Management transmitting the third-party registration status request data object to the system; a subscriber identifier data object associated with said subscriber identifier data object; 、 third-party registration status response data from said third-party device management system; receiving the third-party registration status response data object; receiving an object containing third-party registration status data; The third-party registration status response data object data is stored in the system. and comparing the second registration status data with the second registration status data. said third-party registration status data and a device protection program management system; Detecting a network communication synchronization error based on a difference in registration status; initiating a system synchronization event based on the network communication synchronization error; A system configured to:

2. The registration management request data object is a registration subscription request or a registration cache request. The system synchronizes the event to the system. In order to do so, the system Based on the subscriber identifier data object, DPPMS subscriber profile data is identifying a data object; Based on the third-party registration status response data object, the DPPM and updating the subscriber profile data object. The system of claim 1 .

3. The system converts the third-party registration status data into the second registration status data.

10. The system of claim 1, configured to compare the data with the network data in real time.

4. The registration management request data object includes a registration subscription request, Third-party subscriber profile data associated with the subscriber identifier data object. the identification that the third-party device management system does not include the data object, The third-party registration status indicates that the system synchronizes the event. In order to initiate the the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriber registrations configured to be created by a third-party device management system The system of claim 1 , configured to transmit a request data object. 。

5. The registration management request data object includes a registration cancellation request data object. and a third-party subscriber profile associated with said subscriber identifier data object. The third-party device management system includes a file data object. The identified third-party registration status indicates the system synchronization event to be initiated. To achieve this, the system the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriptions configured to have the third-party device management system cancel them 2. The method of claim 1, further comprising transmitting a user cancellation request data object. The system.

6. The system comprises: a third-party registration management request data object to the third-party device management system; attempting to transmit the project; The third-party device management system receives the third-party registration management request data. and a third-party device management system in response to the attempt to transmit the object. receiving a transmission error indicative of an error in communicating; identifying an error classification associated with the transmission error, Identifying errors, including those that are retryable; determining a request retry time; After the request retry time has elapsed, the third-party device management system is notified of a second transmitting a third-party registration status request data object; a second third-party registration status response from the third-party device management system; receiving an answer data object; The second third-party registration status response data object is analyzed in real time. and analyzing the second third party registration associated with the subscriber identifier data object. identifying the registration status; and determining whether the second system is configured to synchronize the second system based on the second identified third-party registration status data.

10. The system of claim 1, further configured to: Stem.

7. The third-party device management system includes a second third-party device management system. a system for receiving the registration from a first third-party device management system; The system of claim 1 , configured to receive an administration request.

8. The system comprises: Based on the subscriber identifier data object, the third-party device management system The system of claim 1 , further configured to identify a stem.

9. The system comprises: receiving a queue length associated with an action queue, receiving a queue containing at least the third-party registration status request; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length. The system of claim 1 , further configured to:

10. 1. A computer-implemented method for detecting network communication synchronization errors, comprising: A subscriber data object indicating a device protection program and including a subscriber identifier data object. receiving a registration management request including an object; Third Party Registration Status Request Data Object to Third Party Device Management transmitting the third-party registration status request data object to the system; a subscriber identifier data object associated with said subscriber identifier data object; 、 third-party registration status response data from said third-party device management system; receiving the third-party registration status response data object; receiving an object containing third-party registration status data; The third-party registration status response data object data is stored in the system. and comparing the second registration status data with the second registration status data. the third-party registration status data and the device protection program management system; Detecting network communication synchronization errors based on the difference between the registration status in the 、 initiating a system synchronization event based on the network communication synchronization error; 11. A computer-implemented method comprising:

11. The registration management request data object is a registration subscription request or a registration cache request. a cancel request data object and initiates a system synchronization event, Based on the subscriber identifier data object, DPPMS subscriber profile data is identifying a data object; Based on the third-party registration status response data object, the DPPM and updating the subscriber profile data object. Computer-implemented methods of.

12. comparing the third-party registration status data with the second registration status data; The computer-implemented method of claim 10 , wherein the step of:

13. The registration management request data object includes a registration subscription request, Third-party subscriber profile data associated with the subscriber identifier data object. The identified data object is not included in the third-party device management system. The registered third-party registration status indicates that the system synchronization event can be initiated. 、 the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriber registrations configured to be created by a third-party device management system The computer-implemented method of claim 10, further comprising transmitting a request data object. Law.

14. The registration management request data object includes a registration cancellation request data object. and a third-party subscriber profile associated with said subscriber identifier data object. The third-party device management system includes a file data object. The identified third-party registration status indicates the system synchronization event to be initiated. That is, the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriptions configured to have the third-party device management system cancel them 11. The computer-implemented method of claim 10, further comprising transmitting a cancel request data object to the computer. Computer implementation method.

15. The computer-implemented method comprises: a third-party registration management request data object to the third-party device management system; attempting to transmit the project; The third-party device management system receives the third-party registration management request data. and a third-party device management system in response to the attempt to transmit the object. receiving a transmission error indicative of an error in communicating; identifying an error classification associated with the transmission error, Identifying errors, including those that are retryable; determining a request retry time; After the request retry time has elapsed, the third-party device management system is notified of a second transmitting a third-party registration status request data object; a second third-party registration status response from the third-party device management system; receiving an answer data object; The second third-party registration status response data object is analyzed in real time. and analyzing the second third party registration associated with the subscriber identifier data object. identifying the registration status; a second system based on the second identified third-party registration status data; and initiating a system synchronization event. method.

16. The third-party device management system includes a second third-party device management system. receiving the registration management request includes receiving the registration management request from a first third-party device management system; The computer-implemented method of claim 10 , wherein the first and second inputs are from a stem.

17. The computer-implemented method comprises: Based on the subscriber identifier data object, the third-party device management system The computer-implemented method of claim 10 further comprising identifying a stem.

18. The computer-implemented method comprises: receiving a queue length associated with an action queue, receiving a queue containing at least the third-party registration status request; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length. The computer-implemented method of claim 10 , further comprising: updating the

19. 1. A computer program product for detecting network communication synchronization errors, comprising: At least one non-transitory computer-readable storage device carrying computer program instructions a medium, the computer program instructions, when executed by a processor, A subscriber data object indicating a device protection program and including a subscriber identifier data object. receiving a registration management request including an object; Third Party Registration Status Request Data Object to Third Party Device Management transmitting the third-party registration status request data object to the system; a subscriber identifier data object associated with said subscriber identifier data object; 、 third-party registration status response data from said third-party device management system; receiving the third-party registration status response data object; receiving an object containing third-party registration status data; The third-party registration status response data object data is stored in the system. and comparing the second registration status data with the second registration status data. the third-party registration status data and the device protection program management system; Detecting network communication synchronization errors based on the difference between the registration status in the 、 initiating a system synchronization event based on the network communication synchronization error; 2. A computer program product configured for:

20. The registration management request data object is a registration subscription request or a registration cache request. a cancel request data object and initiates a system synchronization event, Based on the subscriber identifier data object, DPPMS subscriber profile data is identifying a data object; Based on the third-party registration status response data object, the DPPM and updating the subscriber profile data object. computer program products.

21. comparing the third-party registration status data with the second registration status data; 20. The computer program product of claim 19, wherein the step of: 。

22. The registration management request data object includes a registration subscription request, Third-party subscriber profile data associated with the subscriber identifier data object. The identified data object is not included in the third-party device management system. The registered third-party registration status indicates that the system synchronization event can be initiated. 、 the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriber registrations configured to be created by a third-party device management system 20. The computer program of claim 19, further comprising transmitting a request data object. Rum products.

23. The registration management request data object includes a registration cancellation request data object. and a third-party subscriber profile associated with said subscriber identifier data object. The third-party device management system includes a file data object. The identified third-party registration status indicates the system synchronization event to be initiated. That is, the third-party device management system, the subscriber identifier data object and The third party subscriber profile data object is associated with the third party. Third-party subscriptions configured to have the third-party device management system cancel them 20. The computer-implemented method of claim 19, further comprising transmitting a cancel request data object to the computer. Computer program products.

24. the computer program product comprising: a third-party registration management request data object to the third-party device management system; attempting to transmit the project; The third-party device management system receives the third-party registration management request data. and a third-party device management system in response to the attempt to transmit the object. receiving a transmission error indicative of an error in communicating; identifying an error classification associated with the transmission error, Identifying errors, including those that are retryable; determining a request retry time; After the request retry time has elapsed, the third-party device management system is notified of a second transmitting a third-party registration status request data object; a second third-party registration status response from the third-party device management system; receiving an answer data object; The second third-party registration status response data object is analyzed in real time. and analyzing the second third party registration associated with the subscriber identifier data object. identifying the registration status; a second system based on the second identified third-party registration status data; and initiating a system synchronization event.

20. The computer program product of claim 19.

25. The third-party device management system includes a second third-party device management system. receiving the registration management request includes receiving the registration management request from a first third-party device management system; 20. The computer program product of claim 19, wherein the nucleic acid sequence is from a stem.

26. the computer program product comprising: Based on the subscriber identifier data object, the third-party device management system 20. The method of claim 19, further comprising computer program instructions for identifying a stem. Computer program products.

27. the computer program product comprising: receiving a queue length associated with an action queue, receiving a queue containing at least the third-party registration status request; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

20. The method of claim 19, further comprising computer program instructions for: Computer program products.

28. 1. A system configured to detect network transmission errors, comprising: a processor and at least one memory, the at least one memory including: and computer code instructions in said memory, said computer code instructions including: When executed by the at least one processor, the system: A third-party registration management request from the system to a third-party device management system Attempting to transmit a data object; the third-party device indicating the occurrence of at least one error during the attempted transmission; detecting a transmission error associated with said attempted transmission to a device management system. and, identifying an error classification associated with the transmission error; identifying an error handling instruction set based on the error classification; and executing the error handling instruction set. Tem.

29. To identify the error classification, the system: Identifying a trained error classification machine learning model; identifying the error classification using the trained error classification machine learning model; and 29. The system of claim 28, configured to:

30. The identified error classification retryable error, and the error handling instruction set are executed. To this end, the system identifying an escalation queue; adding the retryable error to the escalation queue.

29. The system of claim 28, configured to:

31. the identified error classification is a retryable error, and the error handling instruction set In order to perform the above, the system identifying a maximum retry threshold; Identifying a number of retry attempts; determining a retry relationship between the maximum retry threshold and the number of retry attempts; determining that the retry relationship satisfies a maximum retry threshold; determining a request retry time; Add the failed transmission to a request queue and retry the failed transmission after the request retry time has elapsed. and attempting to retransmit the transmission that was missed.

9. The system described in 8.

32. To determine the request retry time, the system: and updating the requested retry time based on the number of retry attempts.

32. The system of claim 31.

33. To determine the request retry time, the system: and updating the request retry time based on an exponential backoff.

32. The system of claim 31.

34. The identified error classification includes an escalation error, and the error handling instruction center To execute the task, the system 29. The method of claim 28, configured to add the failed transmission to a transmission queue. system.

35. The identified error classification from the error classification set is an error in the execution of the error handling instruction set, Configured to transmit error escalation requests to a third-party error handling system 29. The system of claim 28, wherein

36. The system comprises: an action queue associated with the third-party registration request data object; receiving an associated queue length; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

30. The system of claim 28, further configured to:

37. 1. A computer-implemented method for detecting network transmission errors, comprising: Sends a third-party registration management request data object to a third-party device management system. attempting to transmit a the third-party device indicating the occurrence of at least one error during the attempted transmission; detecting a transmission error associated with said attempted transmission to a device management system. and, identifying an error classification associated with the transmission error; identifying an error handling instruction set based on the error classification; and executing the set of error handling instructions.

38. identifying the error classification, Identifying a trained error classification machine learning model; identifying the error classification using the trained error classification machine learning model; and 38. The computer-implemented method of claim 37, comprising:

39. The identified error classification retryable error, and the error handling instruction set are executed. That is, identifying an escalation queue; adding the retryable error to the escalation queue.

38. The computer-implemented method of claim 37.

40. the identified error classification is a retryable error, and the error handling instruction set To execute identifying a maximum retry threshold; Identifying a number of retry attempts; determining a retry relationship between the maximum retry threshold and the number of retry attempts; determining that the retry relationship satisfies a maximum retry threshold; determining a request retry time; Add the failed transmission to a request queue and retry the failed transmission after the request retry time has elapsed. and attempting to retransmit the transmission that was received. Data implementation method.

41. determining the request retry time; 41. The method of claim 40, further comprising updating the requested retry time based on the number of retry attempts.

2. The computer-implemented method of claim 1 .

42. determining the request retry time; 41. The method of claim 40, further comprising updating the request retry time based on an exponential backoff. The computer-implemented method described herein.

43. The identified error classification includes an escalation error, and the error handling instruction center To execute the 38. The computer program of claim 37, further comprising adding the failed transmission to a transmission queue. Data implementation method.

44. The identified error classification from the error classification set is an error in the processing of the program; and executing the error handling instruction set. including transmitting error escalation requests to a third-party error handling system.

38. The computer-implemented method of claim 37.

45. The computer-implemented method comprises: an action queue associated with the third-party registration request data object; receiving an associated queue length; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

38. The computer-implemented method of claim 37, further comprising: updating the

46. A computer program product for detecting network transmission errors, comprising: At least one non-transitory computer-readable storage medium carrying computer program instructions. wherein the computer program instructions, when executed on a processor, Sends a third-party registration management request data object to a third-party device management system. attempting to transmit a the third-party device indicating the occurrence of at least one error during the attempted transmission; detecting a transmission error associated with said attempted transmission to a device management system. and, identifying an error classification associated with the transmission error; identifying an error handling instruction set based on the error classification; and executing the error handling instruction set. Program products.

47. identifying the error classification, Identifying a trained error classification machine learning model; identifying the error classification using the trained error classification machine learning model; and 47. The computer program product of claim 46, comprising:

48. The identified error classification retryable error, and the error handling instruction set are executed. That is, identifying an escalation queue; adding the retryable error to the escalation queue.

47. The computer program product of claim 46.

49. the identified error classification is a retryable error, and the error handling instruction set To execute identifying a maximum retry threshold; Identifying a number of retry attempts; determining a retry relationship between the maximum retry threshold and the number of retry attempts; determining that the retry relationship satisfies a maximum retry threshold; determining a request retry time; Add the failed transmission to a request queue and retry the failed transmission after the request retry time has elapsed. and attempting to retransmit the transmission that was received. Program products.

50. determining the request retry time; 49. The method of claim 48, further comprising updating the requested retry time based on the number of retry attempts.

2. The computer program product according to claim 1 .

51. determining the request retry time; 50. The method of claim 49, further comprising updating the request retry time based on an exponential backoff.

2. The computer program product of claim 1 .

52. The identified error classification includes an escalation error, and the error handling instruction center To execute the 47. The computer program of claim 46, further comprising adding the failed transmission to a transmission queue. Program products.

53. The identified error classification from the error classification set is an error in the processing of the program; and executing the error handling instruction set. including transmitting error escalation requests to a third-party error handling system.

47. The computer program product of claim 46, comprising:

54. the computer program product comprising: an action queue associated with the third-party registration request data object; receiving an associated queue length; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

47. The method of claim 46, further comprising computer program instructions for: Computer program products.

55. 1. A system configured to fulfill claims for unregistered devices, comprising at least Each includes a processor and at least one memory, the library includes computer code instructions in the memory, the computer code instructions when executed by the processor, the system Receiving a billing data object associated with a subscriber identification data object wherein the billing data object includes a device identification data object. , receiving; A device protection program subscriber database associated with the system includes the subscriber's A subscriber profile data object associated with a subscriber identifier data object. Inquiry regarding The device protection program database includes the subscriber profile data object. receiving result data indicating that the Transmitting a third-party registration status request to a third-party device management system wherein the third party registration status request data object is a transmitting data object including a user identifier data object and said device identification data object; And, the subscriber identifier data object from the third-party device management system; Third-Party Registration Status Response that indicates the third-party registration status associated with receiving an answer data object, the third party registration status being: a third-party subscriber profile stored in the third-party device management system; receiving a data object representing the data; the billing data object without the subscriber profile data object and initiating an associated set of billing processing instructions. ,system.

56. The system comprises: Including at least one anti-fraud event for obtaining real-time device information. identifying a set of anti-tamper instructions; and executing the fraud prevention instruction set. Item 56. The system described in Item 55.

57. The system comprises: receiving a queue length associated with an action queue, receiving a queue containing at least a subset of said billing data objects; 、 identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

56. The system of claim 55, further configured to:

58. The billing data object is received from a first third-party device management system. and the third-party registration status request is sent to a second third-party device management system.

56. The system of claim 55, wherein the signal is transmitted to a system.

59. The system comprises: Based on the subscriber identifier data object, the third-party device management system 56. The system of claim 55, further configured to identify the stem.

60. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier a data object, the system comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The service indicates, obtains, and a device lost status associated with the device location application; and determining that the device lost status is set to a lost state; The set of billing instructions may be configured to process a device when the device loss status is set to a lost state. determining, initiated in response to said determining that the In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device location application is disabled. and a claim initiated in response to the determination. Item 56. The system described in Item 55.

61. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier a data object, the system comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is inaccessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to a decision to get something done, and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. and a claim initiated in response to the determination. Item 56. The system described in Item 55.

62. The billing data object includes a third party manufacturer device management system. a third-party registration status received from one third-party device management system; a request for billing data is transmitted to a second third-party device management system; and wherein the object includes a billing type identifier data object, and the system further comprises: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to a decision to get something done, and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. and a claim initiated in response to the determination. Item 56. The system described in Item 55.

63. The system comprises: The system stores the subscriber profile data object in the device protection program. and receiving a transmission error that is not stored in the RAM database.

56. The system of claim 55.

64. The system comprises: System synchronization event based on the third-party registration status response data object 56. The system of claim 55, further configured to initiate a vent.

65. 1. A computer-implemented method for fulfilling claims for an unregistered device, comprising: Receiving a billing data object associated with a subscriber identification data object wherein the billing data object includes a device identification data object. , receiving; A device protection program subscriber database associated with the system includes the subscriber's A subscriber profile data object associated with a subscriber identifier data object. Inquiry regarding The device protection program database includes the subscriber profile data object. receiving result data indicating that the Transmitting a third-party registration status request to a third-party device management system wherein the third party registration status request data object is a transmitting data object including a user identifier data object and said device identification data object; And, the subscriber identifier data object from the third-party device management system; Third-Party Registration Status Response that indicates the third-party registration status associated with receiving an answer data object, the third party registration status being: a third-party subscriber profile stored in the third-party device management system; receiving a data object representing the data; the billing data object without the subscriber profile data object and initiating the associated set of claims processing instructions.

66. The computer-implemented method comprises: Including at least one anti-fraud event for obtaining real-time device information. identifying a set of anti-tamper instructions; and executing said tamper-resistant instruction set. Computer implementation method.

67. The computer-implemented method comprises: receiving a queue length associated with an action queue, receiving a queue containing at least a subset of said billing data objects; 、 identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

66. The computer-implemented method of claim 65, further comprising: updating the

68. The billing data object is received from a first third-party device management system. and the third-party registration status request is sent to a second third-party device management system.

66. The computer-implemented method of claim 65, wherein the information is transmitted to a system.

69. The computer-implemented method comprises: Based on the subscriber identifier data object, the third-party device management system 66. The computer-implemented method of claim 65, further comprising identifying the stem.

70. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier the data object, the computer-implemented method further comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The service indicates, obtains, and a device lost status associated with the device location application; and determining that the device lost status is set to a lost state; The set of billing instructions may be configured to process a device when the device loss status is set to a lost state. determining, initiated in response to said determining that the In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable.

66. The computer of claim 65, comprising: determining, initiated in response to the determination. How to implement it.

71. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier the data object, the computer-implemented method further comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is inaccessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to the determination, including obtaining; and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable.

66. The computer of claim 65, comprising: determining, initiated in response to the determination. How to implement it.

72. The billing data object includes a third party manufacturer device management system. a third-party registration status received from one third-party device management system; a request for billing data is transmitted to a second third-party device management system; the computer-implemented method further comprising: Furthermore, the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to the determination, including obtaining; and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable.

66. The computer of claim 65, comprising: determining, initiated in response to the determination. How to implement it.

73. The computer-implemented method comprises: The system stores the subscriber profile data object in the device protection program.

66. The method of claim 65, further comprising receiving a transmission error that is not stored in a RAM database. The computer-implemented method described herein.

74. The computer-implemented method comprises: System synchronization event based on the third-party registration status response data object 66. The computer-implemented method of claim 65, further comprising initiating a vent.

75. A computer program product for fulfilling claims for unregistered devices, at least one non-transitory computer-readable storage medium carrying computer program instructions; a storage medium, the computer program instructions, when executed by a processor, Receiving a billing data object associated with a subscriber identification data object wherein the billing data object includes a device identification data object. , receiving; A device protection program subscriber database associated with the system includes the subscriber's A subscriber profile data object associated with a subscriber identifier data object. Inquiry regarding The device protection program database includes the subscriber profile data object. receiving result data indicating that the Transmitting a third-party registration status request to a third-party device management system wherein the third party registration status request data object is a transmitting data object including a user identifier data object and said device identification data object; And, the subscriber identifier data object from the third-party device management system; Third-Party Registration Status Response that indicates the third-party registration status associated with receiving an answer data object, the third party registration status being: a third-party subscriber profile stored in the third-party device management system; receiving a data object representing the data; the billing data object without the subscriber profile data object and initiating an associated billing instruction set. Computer program products.

76. the computer program product comprising: Including at least one anti-fraud event for obtaining real-time device information. identifying a set of anti-tamper instructions; and executing the tamper-resistant instruction set.

76. The computer program product of claim 75, further comprising:

77. the computer program product comprising: receiving a queue length associated with an action queue, receiving a queue containing at least a subset of said billing data objects; 、 identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length.

76. The method of claim 75, further comprising computer program instructions for: Computer program products.

78. The billing data object is received from a first third-party device management system. and the third-party registration status request is sent to a second third-party device management system.

76. The computer program product of claim 75, wherein the computer program product is transmitted to a system.

79. the computer program product comprising: Based on the subscriber identifier data object, the third-party device management system 76. The method of claim 75, further comprising computer program instructions for identifying a stem. Computer program products.

80. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier a data object, said computer program product comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The service indicates, obtains, and a device lost status associated with the device location application; and determining that the device lost status is set to a lost state; The set of billing instructions may be configured to process a device when the device loss status is set to a lost state. and for determining, initiated in response to said determining that In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. and computer program instructions for determining, initiated in response to the determination.

76. The computer program product of claim 75, further comprising:

81. the billing data object is a third party carrier device management system or First, third-party device management, including third-party vendor device management systems a third-party registration status request is received from a second third-party system; the billing data object is transmitted to the device management system, the billing data object comprising a billing type identifier a data object, said computer program product comprising: the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is inaccessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to a decision, for obtaining, and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. and computer program instructions for determining, initiated in response to the determination.

76. The computer program product of claim 75, further comprising:

82. The billing data object includes a third party manufacturer device management system. a third-party registration status received from one third-party device management system; a request for billing data is transmitted to a second third-party device management system; the computer program includes a billing type identifier data object; The product is the claim type identifier data object is a lost device claim or a stolen device claim In a situation where Device location applications and associated device location applications obtaining a location status of the device location application; The device location application status indicates that the application is accessible. The The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. Initiated in response to a decision, for obtaining, and In the situation where the claim type identifier data object represents a device damage claim, a device location application associated with the device location application; Obtaining application status; The device location application is inaccessible. determining a location application status indicating: The billing instruction set is accessed by the device location application. The device location application status indicates that the device is unavailable. and computer program instructions for determining, initiated in response to the determination.

76. The computer program product of claim 75, further comprising:

83. the computer program product comprising: The system stores the subscriber profile data object in the device protection program. Computer program instructions for receiving transmission errors that are not stored in a RAM database 76. The computer program product of claim 75, further comprising instructions.

84. the computer program product comprising: System synchronization event based on the third-party registration status response data object 76. The method of claim 75, further comprising computer program instructions for initiating a vent. Computer program products.

85. 1. A system including at least one processor and at least one memory, the at least one memory includes computer code instructions therein; The computer coded instructions, when executed by the at least one processor, In the system, receiving a queue length associated with an action queue; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length. A system configured to update and cause the system to:

86. The queue length threshold includes a queue length maximum threshold, and the queue relationship includes a maximum queue relationship. wherein the system comprises: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying a maximum action process instance count value; The number of instances executed and the maximum number of action process instance counts determining a maximum process instance relationship based on a large threshold; The maximum process instance relationship is the maximum of the action process instance count. determining that a major threshold is met; To cause the system to update the set of executed action process instances. To this end, the system Executing a new action process instance; The new action process instance is used as the action process instance to be executed. and adding to the instance set. system.

87. The queue length threshold includes a queue length minimum threshold, and the queue relationship includes a minimum queue relationship. wherein the system comprises: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying an action process instance count minimum; The number of instances executed and the maximum number of action process instance counts determining a minimum process instance relationship based on the minimum value; The minimum process instance relationship is the minimum of the action process instance count. determining that the minimum value satisfies the minimum value; To cause the system to update the set of executed action process instances. To this end, the system A selected action to be executed from the set of action process instances to be executed 86. The system of claim 85, configured to terminate an operation process instance. Stem.

88. To update the set of action process instances to be executed, the system M, An action associated with at least one unprocessed action in the action queue identifying an action type, wherein the action type is a first action priority; Associated with degrees, identifying and configured to process a second action type associated with a second action priority; The action process instance to be executed, including the process thread that was created to be executed. and identifying the first action priority as the second action priority. and identifying the Remove the process thread from the executed action process instance. And, Execute a new process thread for the action process instance to be executed. the new process thread performs a process associated with the first action type. and executing the associated outstanding action.

86. The system of claim 85, configured to:

89. 1. A computer-implemented method comprising: receiving a queue length associated with an action queue; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length. and renewing the computer-implemented method.

90. The queue length threshold includes a queue length maximum threshold, and the queue relationship includes a maximum queue relationship. the computer-implemented method comprising: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying a maximum action process instance count value; The number of instances executed and the maximum number of action process instance counts determining a maximum process instance relationship based on a large threshold; The maximum process instance relationship is the maximum of the action process instance count. determining that a major threshold has been met; updating the set of action process instances to be executed; Executing a new action process instance; The new action process instance is used as the action process instance to be executed. and adding the instance set to the instance set. 。

91. The queue length threshold includes a queue length minimum threshold, and the queue relationship includes a minimum queue relationship. the computer-implemented method comprising: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying an action process instance count minimum; The number of instances executed and the maximum number of action process instance counts determining a minimum process instance relationship based on the minimum value; The minimum process instance relationship is the minimum of the action process instance count. determining that the minimum value satisfies the minimum value; updating the set of action process instances to be executed; A selected action to be executed from the set of action process instances to be executed 90. The computer of claim 89, further comprising terminating an action process instance. How to implement it.

92. updating the set of action process instances to be executed; An action associated with at least one unprocessed action in the action queue identifying an action type, wherein the action type is a first action priority; Associated with degrees, identifying and configured to process a second action type associated with a second action priority; The action process instance to be executed, including the process thread that was created to be executed. and identifying the first action priority as the second action priority. and identifying the Remove the process thread from the executed action process instance. And, Execute a new process thread for the action process instance to be executed. the new process thread performs a process associated with the first action type. and executing the associated outstanding action.

90. The computer-implemented method of claim 89, comprising:

93. At least one non-transitory computer-readable storage medium carrying computer program instructions. a computer program product including a storage medium, the computer program instructions ,When executed on the processor, receiving a queue length associated with an action queue; identifying a queue length threshold; identifying a queue relationship based on the queue length and the queue length threshold; determining that the queue relationship satisfies the queue length threshold; An action execution process that contains at least one action execution process instance. identifying a set of application process instances; Update the set of action process instances to be executed based on the queue length. A computer program product configured to:

94. The queue length threshold includes a queue length maximum threshold, and the queue relationship includes a maximum queue relationship. wherein the computer program product comprises: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying a maximum action process instance count value; The number of instances executed and the maximum number of action process instance counts determining a maximum process instance relationship based on a large threshold; The maximum process instance relationship is the maximum of the action process instance count. determining that the high threshold is met; and Including, updating the set of action process instances to be executed; Executing a new action process instance; The new action process instance is used as the action process instance to be executed. and adding the instance to the instance set. Product.

95. The queue length threshold includes a queue length minimum threshold, and the queue relationship includes a minimum queue relationship. wherein the computer program product comprises: The executed action process instance set is associated with the executed action process instance set. identifying the number of instances; Identifying an action process instance count minimum; The number of instances executed and the maximum number of action process instance counts determining a minimum process instance relationship based on the minimum value; The minimum process instance relationship is the minimum of the action process instance count. and determining that the minimum value is satisfied. fruit, updating the set of action process instances to be executed; A selected action process instance from the set of action processes to be executed 94. The computer-implemented method of claim 93, further comprising terminating an action process instance. Program products.

96. updating the set of action process instances to be executed; An action associated with at least one unprocessed action in the action queue identifying an action type, wherein the action type is a first action priority; Associated with degrees, identifying and configured to process a second action type associated with a second action priority; The action process instance to be executed, including the process thread that was created to be executed. and identifying the first action priority as the second action priority. and identifying the Remove the process thread from the executed action process instance. And, Execute a new process thread for the action process instance to be executed. the new process thread performs a process associated with the first action type. and executing the associated outstanding action.

94. The computer program product of claim 93, comprising:

Images