Performance detection method and system for electronic task reminding system

Abstract

The embodiment of the invention provides a performance detection method and system for an electronic task reminding system, and the method comprises the steps: firstly obtaining a detection task set which comprises a plurality of different reminding types and is composed of a plurality of task units with independent reminding identifiers, and enabling each task unit to comprise detailed information such as a reminding triggering condition; sending a reminding trigger instruction to the electronic task reminding system based on the detection task set, generating a reminding event record containing a trigger timestamp, and recording a response data set after the system executes a reminding operation, including an actual reminding time point, a reminding content integrity identifier, an associated object receiving state identifier and the like; and performing matching analysis on the response data set and the original task parameters, generating a performance evaluation result containing reminding timeliness deviation, content accuracy deviation and receiving coverage deviation, and outputting the performance evaluation result to the target display terminal, so that the performance of the electronic task reminding system can be comprehensively and accurately detected, and a reliable basis is provided for optimization of the electronic task reminding system.

Description

Technical Field

[0001] The present application relates to the technical field of electronic alarm clocks, and in particular to a performance detection method and system for an electronic task reminder system. Background Art

[0002] In today's highly integrated digital world of life and work, electronic task reminder systems are playing an increasingly crucial role as tools to assist people in managing their time and tasks. They not only offer the scheduled reminder functionality of traditional electronic alarm clocks, but also feature more complex and diverse reminder settings, such as event-triggered reminders, periodic recurring reminders, and multi-task linked reminders, to meet people's refined management needs in diverse scenarios. However, there is currently a lack of systematic and effective methods for testing the performance of electronic task reminder systems. Traditional testing methods for simple reminder devices (such as basic electronic alarm clocks) often focus solely on whether reminders are delivered on time, manually testing at a few fixed time points. However, this approach is far from sufficient for feature-rich electronic task reminder systems. It fails to cover the diverse and complex reminder types supported by the system, making it difficult to comprehensively evaluate the system's processing capabilities in different reminder scenarios. Furthermore, traditional methods struggle to accurately record key information such as the reminder trigger time, the completeness of the reminder content, and the reception status of associated objects (such as multiple associated devices or users). Consequently, they are unable to accurately assess key performance indicators such as reminder timeliness, content accuracy, and reception coverage. In addition, the lack of standardized testing processes and unified performance evaluation standards makes the test results obtained by different testers or in different testing scenarios lack comparability. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a performance testing method and system for an electronic task reminder system.

[0004] According to a first aspect of the present application, a performance testing method for an electronic task reminder system is provided, the method comprising: Acquire a detection task set containing different reminder types, wherein the detection task set consists of multiple task units with independent reminder identifiers, each task unit including a reminder trigger condition, reminder content information, and an associated object identifier; Sending a reminder trigger instruction to the electronic task reminder system based on the detection task set, triggering the electronic task reminder system to perform a reminder operation corresponding to each task unit, and generating a reminder event record including a trigger timestamp; Recording a response data set after the electronic task reminder system executes a reminder operation, wherein the response data set includes the actual reminder time point of each task unit, the reminder content integrity identifier, and the associated object reception status identifier; The response data set is matched with original task parameters in the detection task set for matching analysis processing, to generate a performance evaluation result including a reminding timeliness deviation, a content accuracy deviation, and a receiving coverage deviation; A performance detection report including each task unit deviation type and deviation degree is generated according to the performance evaluation result, and the performance detection report is output to a target display terminal.

[0005] According to a second aspect of the present application, a performance detection system for an electronic task reminding system is provided, which includes a processor and a readable storage medium, and the readable storage medium stores a program which, when executed by the processor, implements the performance detection method for the electronic task reminding system.

[0006] According to any one of the above aspects, the present application fully considers the complex and diverse functional characteristics of the electronic task reminding system, and through obtaining a detection task set including different reminding types, various reminding scenarios supported by the system are comprehensively covered, whether it is a simple timing reminder or a complex event triggered reminder, periodic reminder, etc., and targeted performance detection can be performed, avoiding the problem of incomplete detection caused by single task type in the traditional method. Based on the detection task set, a reminding trigger instruction is sent to the system and a reminding event record is generated, and a response data set after the system performs a reminding operation is recorded in detail, key information such as triggering time, content integrity, and associated object receiving state of the reminding is accurately obtained, the response data set is matched with original task parameters for matching analysis processing, and the system performance is quantitatively evaluated from multiple key dimensions such as reminding timeliness deviation, content accuracy deviation, and receiving coverage deviation, so that the detection result is more scientific, objective, and accurate, and can truly reflect the performance of the system in different aspects. Finally, a performance detection report is generated according to the performance evaluation result and output to a target display terminal, which provides clear and intuitive performance information for system developers, maintainers, and users, and helps to discover problems in the system in a timely manner and perform targeted optimization and improvement, thereby improving the reliability and user experience of the electronic task reminding system. BRIEF DESCRIPTION OF DRAWINGS

[0007] Figure 1 A flowchart of a performance detection method for an electronic task reminding system provided by an embodiment of the present application is shown; Figure 2 A component structure diagram of a performance detection system for an electronic task reminding system provided by an embodiment of the present application is shown. DETAILED DESCRIPTION

[0008] Figure 1A flowchart of the performance detection method for the electronic task reminding system provided in the embodiments of the present application is shown. It should be understood that in other embodiments, the order of some steps of the performance detection method for the electronic task reminding system can be exchanged according to actual needs, or some steps can be omitted or deleted. The detailed steps of the performance detection method for the electronic task reminding system are described as follows.

[0009] Step S110: Obtain a detection task set containing different reminding types, the detection task set being composed of a plurality of task units with independent reminding identifiers, each task unit containing a reminding trigger condition, reminding content information and an associated object identifier.

[0010] In the embodiments, when the performance of the electronic alarm clock system is detected, a detection task set containing different reminding types is first obtained. Different reminding types can meet the diversified use requirements of users, and each task unit has its independent reminding identifier, which facilitates subsequent accurate management and tracking of each task. The reminding trigger condition in each task unit determines when the alarm clock sends a reminder, the reminding content information specifies the specific matters of the user to be reminded, and the associated object identifier indicates the object that needs to receive the reminder. In order to describe this step in detail, an electronic alarm clock system in a family scenario is taken as an example. The electronic alarm clock system needs to remind the family members of various daily activities, such as getting up, going to work, exercising, studying, etc.

[0011] Step S111: Determine a reminding type set to be detected, the reminding type set containing a timing reminding type, a repeated period reminding type and a condition trigger reminding type.

[0012] Before obtaining the detection task set, the reminding type set to be detected needs to be determined. The specific process is as follows: Step S1111: Analyze the function specification of the electronic alarm clock system, extract the reminding function module information supported by the electronic alarm clock system, and the function module information contains a basic timing reminding module, a period management module and a condition response module.

[0013] The function specification of the electronic alarm clock system is carefully read, and the reminding function module information supported by the system is extracted. The basic timing reminding module has the function of triggering a reminder at a specific time point, for example, it can be set to remind getting up at 7 am. The period management module can trigger a reminder repeatedly according to a certain period, such as repeatedly reminding getting up at 7 am from Monday to Friday every week. The condition response module triggers a reminder according to a specific condition change, for example, reminding to add or reduce clothes when the indoor temperature reaches a certain set value.

[0014] Step S1112: Determine the corresponding alarm type based on the function module information. The timing alarm type corresponds to the single-time point trigger function of the basic timing alarm module, the repeated period alarm type corresponds to the interval repeated trigger function of the period management module, and the condition trigger alarm type corresponds to the state change trigger function of the condition response module.

[0015] The corresponding alarm type is determined according to the extracted function module information. The timing alarm type corresponds to the single-time point trigger function of the basic timing alarm module, such as setting an alarm for children to sleep at 9 pm in a home scenario. The repeated period alarm type corresponds to the interval repeated trigger function of the period management module, for example, reminding children to attend an interest class at 8 pm every Wednesday. The condition trigger alarm type corresponds to the state change trigger function of the condition response module, and if the child has completed the homework for the day, the electronic alarm clock will remind that entertainment activities can be performed.

[0016] Step S1113: Verify the matching of the alarm type with the actual supported functions of the electronic alarm clock system, and the matching verification is confirmed by the execution result of the system function test case.

[0017] In order to ensure that the determined alarm type matches the actual supported functions of the electronic alarm clock system, it is necessary to execute the system function test case. For the timing alarm type, a series of alarm tasks at different time points are set to check whether the system can trigger the alarm at the accurate time. For the repeated period alarm type, different periods and starting times are set to verify whether the system can trigger the alarm repeatedly according to the set period. For the condition trigger alarm type, various condition changes are simulated to check whether the system can accurately trigger the alarm according to the condition change.

[0018] Step S1114: Collect historical performance detection requirement data, which includes user attention frequency statistical information for different alarm types.

[0019] The historical performance detection requirement data is collected, which includes user attention frequency statistical information for different alarm types. By analyzing these data, the user's preferences and demand degree for various alarm types in the actual use process can be understood. For example, it is found through statistics that the user's use frequency of the timing alarm type is high, which indicates that the user may rely more on the alarm at a specific time point.

[0020] Step S1115: Adjust the detection priority of the alarm type according to the historical performance detection requirement data, and the detection priority is used to determine the sample quantity allocation proportion of each type when generating the subsequent task unit.

[0021] Adjust the detection priority of reminder types based on the collected historical performance testing demand data. Reminder types that are frequently noticed by users are assigned a higher detection priority, and more samples are allocated to them for testing when subsequent task units are generated. For example, if a scheduled reminder type is frequently noticed, the number of task units for this type of reminder will be increased when generating testing task units to ensure that the system's performance on this type of reminder is fully tested.

[0022] Step S1116: The finally determined timed reminder type, repetition period reminder type and condition trigger reminder type are packaged together to generate a reminder type set to be detected.

[0023] The finally determined timed reminder types, repetition period reminder types and condition trigger reminder types are collectively packaged to form a reminder type set to be detected.

[0024] Step S112: Generate a corresponding task unit template for each reminder type, wherein the task unit template includes a basic trigger condition framework, a content information structure, and an associated object identification rule.

[0025] After determining the set of reminder types to be tested, a corresponding task unit template is generated for each reminder type. For timed reminder types, the basic trigger condition framework must clearly specify the time point of the reminder. The content information structure can include the specific matters of the reminder, the degree of importance, etc. The associated object identification rules can be determined based on the identity of the family members. For example, for a timed reminder task to remind children to go to bed, the content information can include "go to bed on time and ensure adequate sleep", and the associated object identification is children.

[0026] For recurring reminders, the basic triggering framework defines the recurring period and start time. In addition to the reminder and its importance, the content structure can also include information related to the period, such as the week's activities. The rules for identifying associated objects are also determined based on family member status. For example, for a reminder every Wednesday at 8 PM for a child's interest class, the content might be "There's a painting class tonight at 8 PM. Get your painting tools ready." The associated object is identified as the child.

[0027] For conditional reminders, the basic trigger condition framework clearly specifies the trigger conditions. The content information structure varies depending on the trigger conditions, and the rules for identifying associated objects are also determined based on the responsibilities and relationships of family members. For example, a task that reminds a child to engage in recreational activities after completing homework could have the trigger condition be the homework completion status. The content information could be "Homework completed, you can play games for a while," and the associated object could be the child.

[0028] Step S113: Fill in the specific trigger condition parameters based on the task unit template, which includes the absolute time point parameter of the timing reminder, the interval period parameter of the repeated period reminder, and the state threshold parameter of the condition trigger reminder.

[0029] Based on the generated task unit template, fill in the specific trigger condition parameters. For the timing reminder type, fill in the absolute time point parameter, which is determined according to the daily schedule of the family. For example, set a reminder to get up at 7 am, and 7 am is the absolute time point parameter.

[0030] For the repeated period reminder type, fill in the interval period parameter, such as every day, every week, every month, etc., and specify the start time and end time of the repetition. For example, set a repeated reminder to get up at 7 am every Monday to Friday, and "every Monday to Friday" is the interval period parameter, the start time is Monday morning 7 am, and the end time is Friday morning 7 am.

[0031] For the condition trigger reminder type, fill in the state threshold parameter. For example, set a reminder to perform entertainment activities when the child's homework completion rate reaches 100%, and 100% is the state threshold parameter.

[0032] Step S114: Assign a unique reminder identifier to each filled task unit, which is used to establish the correspondence between the task unit and the subsequent response data.

[0033] Assign a unique reminder identifier to each task unit with filled trigger condition parameters. This reminder identifier is very important in the subsequent detection process, as it can establish the correspondence between the task unit and the subsequent response data. For example, assign a specific reminder identifier to the task unit "7 am reminder to get up", and when recording the system response data later, the corresponding task unit can be accurately found through this reminder identifier.

[0034] Step S115: Perform validity verification processing on the trigger condition parameters of the task unit, which includes logical reasonableness checking of the time parameter, triggerability checking of the condition threshold, and format specification checking of the associated object identifier.

[0035] The trigger condition parameters of the task units are subjected to validity verification processing. First, logical reasonableness check of the time parameters is performed to ensure that the time point of the timing reminder and the time setting of the repeated period reminder meet the logic. For example, it is checked whether the end time of the repeated period reminder is later than the start time. Then, the triggerability check of the condition threshold is performed to ensure that the state threshold parameter of the condition trigger reminder is reasonable and achievable. For example, it is checked whether the proportion threshold of the child completing the homework is between 0 and 100%. Finally, the format specification check of the associated object identifier is performed to ensure that the format of the associated object identifier is correct and can accurately identify the object receiving the reminder.

[0036] Step S116: The task units that pass the validity verification are subjected to set packaging processing to generate a detection task set containing different reminder types.

[0037] The task units that pass the validity verification are subjected to set packaging processing to generate a detection task set containing different reminder types. The task units in this detection task set cover different types such as timing reminders, repeated period reminders, and condition trigger reminders, which will serve as the basis for subsequent performance detection of the electronic alarm clock system.

[0038] Step S120: Based on the detection task set, a reminder trigger instruction is sent to the electronic alarm clock system to trigger the electronic alarm clock system to perform the reminder operation corresponding to each task unit and generate a reminder event record containing a trigger timestamp.

[0039] After obtaining the detection task set containing different reminder types, a reminder trigger instruction needs to be sent to the electronic alarm clock system to prompt the system to perform the corresponding reminder operation and record the related reminder event. In the family scenario, the electronic alarm clock system needs to remind the family members of various daily activities such as getting up, going to work, exercising, and studying. In order to ensure that the reminder trigger instruction can be accurately and correctly sent and received by the system, a series of rigorous processing steps are required.

[0040] Step S121: The reminder identifier and trigger condition parameters of each task unit in the detection task set are analyzed to generate a trigger instruction datagram matching the interface protocol of the electronic alarm clock system.

[0041] The reminding identifier and trigger condition parameters of each task unit in the detection task set are analyzed in detail. First, the reminding identifier field is accurately extracted from the task unit, which is the unique identifier of the task unit and plays a key role in subsequent processing and tracking. At the same time, according to the different reminding types, the corresponding trigger condition parameters are extracted. For the timing reminding type, the absolute time point parameter is extracted, which specifies the specific time of the reminding trigger; for the repeated period reminding type, the interval period parameter and the start and end time are extracted to determine the repeating rule of the reminding; for the condition triggered reminding type, the state threshold parameter is extracted, which specifies the condition limit of the triggered reminding.

[0042] The interface protocol document of the electronic alarm system is obtained, which specifies the field definition, data type and coding format requirements of the instruction datagram. According to the field definition of the interface protocol document, the extracted reminding identifier field and trigger condition parameters are accurately mapped to the corresponding field positions of the instruction datagram. In the mapping process, it is ensured that each parameter is correctly placed to ensure that the format of the instruction datagram meets the system requirements.

[0043] The field data type of the instruction datagram is strictly checked. For the time point parameter, date and time format checking is performed to ensure that its format meets the standard that can be recognized and processed by the system; the interval period parameter is checked for integer type to ensure that it is a valid integer; the state threshold parameter is checked for numerical range to ensure that it is within a reasonable value range. Only the instruction datagram that passes the verification can be processed for the next encoding.

[0044] The instruction datagram that passes the verification is encoded to convert the instruction datagram into a specific encoding format using the system specified encoding method, generating a trigger instruction datagram containing the reminding identifier field, trigger condition parameter field and encoded data content. The encoded trigger instruction datagram can be accurately transmitted and processed in the system.

[0045] Step S122: The trigger instruction datagram is classified and grouped according to the reminding type of the task unit to generate a timing trigger group, a period trigger group and a condition trigger group.

[0046] The generated trigger instruction datagrams are classified and grouped according to the reminder types of the task units. The trigger instruction datagrams of the timing reminder type are classified into a timing trigger group. The trigger instruction datagrams of the periodic reminder type are classified into a periodic trigger group. The trigger instruction datagrams of the conditional trigger reminder type are classified into a conditional trigger group.

[0047] In the classification and grouping process, it is ensured that each trigger instruction datagram is correctly classified to avoid classification errors that may cause the reminder operation to fail to be normally executed. Meanwhile, clear identification is established for each trigger group to facilitate subsequent management and processing.

[0048] Step S123: An independent instruction sending queue is set for each trigger group, and the priority of the instruction sending queue is dynamically adjusted according to the real-time requirement of the reminder type.

[0049] An independent instruction sending queue is set for each trigger group, and each queue is used to store and manage the trigger instruction datagrams of the corresponding trigger group. The priority of the instruction sending queue is dynamically adjusted according to the real-time requirement of the reminder type. For the timing reminder type, since the accuracy of time is extremely high, the real-time requirement is also relatively high, and therefore the priority of the instruction sending queue of the timing trigger group is set to a high level. In a home scenario, for example, a timing reminder for calling a child to get up in the morning must be sent at an accurate time point, and therefore such instructions should be sent in priority.

[0050] For the periodic reminder type, the real-time requirement is relatively low, and the priority of the instruction sending queue of the periodic trigger group can be appropriately lowered. For example, a fitness reminder at a fixed time every week has a less strict time requirement than a timing wake-up reminder, and a certain time fluctuation can be allowed. For the conditional trigger reminder type, the priority of the instruction sending queue of the conditional trigger group is adjusted according to the urgency and importance of the condition. If the condition is an important condition related to safety, such as a fire alarm, the priority should be set to the highest; if the condition is a general event, such as a reminder that the indoor temperature reaches a certain range, the priority can be appropriately lowered.

[0051] During the system operation, the real-time requirement of the reminder type is monitored in real time, and the priority of the instruction sending queue is dynamically adjusted according to the actual situation to ensure that important reminder instructions can be sent in time.

[0052] Step S124: The trigger instruction datagrams in the instruction sending queue are sent to the electronic alarm clock system.

[0053] The trigger instruction datagrams in the queue are sent to the electronic alarm system in the order of priority of the instruction sending queue. During the sending process, a stable and reliable communication protocol and transmission method are used to ensure that the trigger instruction datagrams can be accurately transmitted to the system. At the same time, a sending identifier and a timestamp are added to each trigger instruction datagram for subsequent tracking and monitoring of the sending situation.

[0054] During the sending process, the network status is monitored in real time to avoid loss or failure of sending instruction datagrams due to network failure. If network instability is encountered, a retry mechanism can be adopted to attempt to send the instruction datagram multiple times until the sending is successful or the maximum number of retries is reached.

[0055] Step S125: Monitor the reception confirmation status of the trigger instruction datagrams by the electronic alarm system, record the trigger instruction datagrams that are not successfully received and perform retransmission processing.

[0056] The reception confirmation status of the trigger instruction datagrams by the electronic alarm system is monitored in real time. After receiving the trigger instruction datagrams, the electronic alarm system returns a reception confirmation information. If the system returns a confirmation information of successful reception, it indicates that the instruction datagram has been successfully sent, and the instruction datagram is marked as a successfully sent state, and the sending time and confirmation time are recorded.

[0057] If the system does not return a confirmation information or returns a reception failure information, the trigger instruction datagrams that are not successfully received are recorded. For the instruction datagrams that are not successfully received, a retransmission processing mechanism is started. First, the reason for the unsuccessful reception is checked, which may be network problems, system failure or instruction datagram format error, etc. If it is a network problem, the instruction datagram can be re-sent after a certain time interval; if it is a format error of the instruction datagram, the instruction datagram needs to be re-verified and corrected before being sent.

[0058] The number of retransmissions and the retransmission interval time are set during the retransmission process. For example, a maximum of three retransmissions is allowed, and the retransmission interval time is a certain time length, such as one minute. If the retransmission fails after multiple attempts, the instruction datagram is marked as a sending failure, and the detailed failure reason is recorded for subsequent analysis and processing.

[0059] Step S126: When the electronic alarm system performs a reminder operation, collect a reminder event record containing a task unit reminder identifier and an actual trigger time.

[0060] When the electronic alarm system receives the trigger instruction datagram and performs the corresponding reminder operation, a reminder event record containing a task unit reminder identifier and an actual trigger time is collected in a timely manner. A special event record module is set in the system, which monitors the execution of the reminder operation in real time.

[0061] When the reminder operation is triggered, the event record module accurately records the reminder identifier of the task unit and the actual triggering time. The reminder identifier is used to uniquely identify the task unit, ensuring that the recorded reminder event corresponds to the corresponding task unit one by one. The actual triggering time reflects the time when the system actually performs the reminder operation. By comparing it with the expected triggering time, the timeliness of the system can be evaluated.

[0062] The collected reminder event records are stored in the database of the system for subsequent query, statistics and analysis. At the same time, the reminder event records are backed up regularly to prevent data loss.

[0063] Step S130: Record the response data set of the electronic alarm clock system after performing the reminder operation, which includes the actual reminder time point of each task unit, the reminder content integrity identifier and the associated object receiving state identifier.

[0064] After the electronic alarm clock system performs the reminder operation, it needs to record the response data set comprehensively, which includes the actual reminder time point of each task unit, the reminder content integrity identifier and the associated object receiving state identifier. These information is crucial for evaluating the performance of the electronic alarm clock system.

[0065] Step S131: Establish the mapping relationship between the task unit reminder identifier in the reminder event record and the task unit in the detection task set, which is established by consistent matching of the reminder identifier.

[0066] In order to accurately associate the reminder event record and the task unit in the detection task set, the mapping relationship between the task unit reminder identifier in the reminder event record and the task unit in the detection task set is established. This mapping relationship is established by consistent matching of the reminder identifier.

[0067] A special mapping module is set up in the system, which compares the reminder event record and the task unit in the detection task set one by one. Taking the reminder identifier as the key matching item, the task unit reminder identifier in the reminder event record is accurately matched with the task unit reminder identifier in the detection task set. If they are consistent, it is considered that the reminder event record corresponds to the task unit in the detection task set, and the mapping relationship is established and recorded in the mapping table.

[0068] By establishing the mapping relationship, it can ensure that the subsequent analysis and processing of the response data are based on accurate task unit correspondence, avoiding data confusion and errors.

[0069] Step S132: For each task unit with a mapping relationship, extract the actual reminder time point from the output log of the electronic alarm clock system.

[0070] For each task unit with a mapping relationship, the actual reminder time point is extracted from the output log of the electronic alarm system. The electronic alarm system records relevant operation information in the output log when performing the reminder operation, including the time of the reminder.

[0071] A log extraction module is set up in the system, which locates the output log record corresponding to each task unit according to the mapping relationship. The actual reminder time point is accurately extracted from the log record and stored in the response data record.

[0072] During the extraction process, the time format is uniformly processed to ensure that the format of the actual reminder time point meets the requirements of subsequent analysis and processing. At the same time, the extracted time data is checked to avoid incorrect or abnormal time records.

[0073] Step S133: Perform content analysis processing on the reminder content output by the electronic alarm system to generate a content element list, which contains key elements in the original reminder content information of the task unit.

[0074] The reminder content output by the electronic alarm system is subjected to in-depth content analysis processing to generate a content element list. The list contains key elements in the original reminder content information of the task unit.

[0075] A content analysis module is set up in the system, which uses natural language processing technology to process the reminder content. First, the reminder content is subjected to word segmentation processing, which splits the content into individual words or phrases. Then, according to a pre-set keyword library, key elements are screened out. The keyword library contains important words related to the reminder content, such as activity name, time, location, etc.

[0076] For example, for a reminder content "Remember to take your backpack, 8 o'clock to school for the exam", through the content analysis module, key elements such as "backpack", "8 o'clock", "school", "exam" are extracted to generate a content element list.

[0077] Step S134: Perform element matching comparison processing on the content element list and the original reminder content information of the task unit to generate a content integrity evaluation result containing the number of missing elements, and the content integrity identifier is generated according to the content integrity evaluation result.

[0078] The generated content element list is subjected to element matching comparison processing with the original reminder content information of the task unit. An element matching module is set up in the system, which compares each element in the content element list with the key elements in the original reminder content information one by one.

[0079] If the elements in the content element list are consistent with the elements in the original reminder content information, it is marked as matching; if it is inconsistent or missing, it is marked as not matching. The number of elements missing is counted to obtain the number of element missing. The content integrity evaluation result is generated according to the number of element missing.

[0080] If the number of element missing is 0, it is considered that the reminder content is complete, and the content integrity identifier is complete; if the number of element missing is small, it is within an acceptable range, and the content integrity identifier is partially missing; if the number of element missing is large, it seriously affects the effectiveness of the reminder, and the content integrity identifier is seriously missing.

[0081] Step S135: Collect the receiving state information of each associated object to the reminder operation through the feedback interface of the associated object, and the receiving state information includes received state, not received state and delayed receiving state.

[0082] The receiving state information of each associated object to the reminder operation is collected through the feedback interface of the associated object. In a home scenario, the associated object can be a family member, such as a child, a parent, etc., and each associated object has its corresponding feedback interface.

[0083] Step S1351: Determine the feedback interface type corresponding to each task unit associated object identifier, and the feedback interface type includes message confirmation interface, application notification reply interface and device state query interface.

[0084] The feedback interface type corresponding to each task unit associated object identifier is determined. Different associated objects can use different feedback interfaces, for example, a mobile phone user can use a message confirmation interface or an application notification reply interface, and a smart device can use a device state query interface.

[0085] An interface type determination module is set in the system, which determines the feedback interface type corresponding to the associated object according to its attributes and usage habits. For example, a child using a mobile phone can use a message confirmation interface, and a parent using a smart watch can use an application notification reply interface.

[0086] Step S1352: Establish a data collection channel for each feedback interface type, and the data collection channel includes interface call parameters, timeout time setting and error handling mechanism.

[0087] A data collection channel is established for each feedback interface type. A data collection channel management module is set in the system, which configures a corresponding data collection channel for each feedback interface type.

[0088] For each data acquisition channel, set the interface call parameters, including the format of the request, the type and value range of the parameters, etc. For example, for the message confirmation interface, the message ID, receiver ID and other parameters need to be set. At the same time, set the timeout time to avoid long waiting for unresponsive interfaces. If no response is received from the interface within the timeout time, the interface call is considered to have failed.

[0089] An error handling mechanism is established, and when an interface call error occurs, appropriate processing can be performed, such as retry, recording error information, etc. If the interface call failure is caused by network problems, a retry operation can be performed; if it is an interface parameter error, the error information is recorded and appropriate adjustments are made.

[0090] Step S1353: According to the correspondence between the reminder identifier of the task unit and the associated object identifier, a state query request is sent to the feedback interface of each associated object, and the state query request contains the reminder identifier of the task unit and the query time range parameter.

[0091] According to the correspondence between the reminder identifier of the task unit and the associated object identifier, a state query request is sent to the feedback interface of each associated object. A request sending module is set in the system, which determines the associated object corresponding to each task unit and its feedback interface according to the mapping relationship.

[0092] The state query request sent to the feedback interface contains the reminder identifier of the task unit and the query time range parameter. The reminder identifier is used to uniquely identify the task unit, and the query time range parameter is used to limit the time interval of the query to ensure that the relevant receiving state information of the task unit is queried.

[0093] For example, for a reminder task to wake up a child in the morning, the state query request sent contains the reminder identifier of the task and the query time range is the time period of getting up in the morning.

[0094] Step S1354: Receive the state response data returned by each feedback interface, which contains the actual receiving timestamp of the associated object to the reminder operation or the reason description information for not receiving.

[0095] Receive the state response data returned by each feedback interface. A response data receiving module is set in the system, which listens to the response information of each feedback interface in real time.

[0096] When the state response data returned by the feedback interface is received, the data is parsed and processed. The state response data contains the actual receiving timestamp of the associated object to the reminder operation or the reason description information for not receiving. If the associated object successfully receives the reminder, the actual receiving timestamp will be included in the response data; if it is not received, the reason for not receiving will be included, such as device shutdown, network failure, etc.

[0097] Step S1355: Analyzing the state response data, extracting the actual receiving time stamp, and calculating the time difference between the actual receiving time stamp and the actual reminding time point in the reminding event record to generate a delay receiving time value.

[0098] The state response data is analyzed to extract the actual receiving time stamp. A data analysis module is set in the system to analyze the format of the state response data and extract the actual receiving time stamp therefrom.

[0099] The extracted actual receiving time stamp is calculated with the actual reminding time point in the reminding event record to generate a delay receiving time value. A time difference calculation module is set in the system to calculate the difference between the two time points to obtain the delay receiving time value. The value reflects the degree of delay in receiving the reminder by the associated object.

[0100] Step S1356: Comparing the delay receiving time value with a preset receiving timeliness threshold to generate an identification of a received state, an un-received state, or a delay receiving state.

[0101] The delay receiving time value is compared with a preset receiving timeliness threshold. A state judgment module is set in the system to compare the delay receiving time value with the preset receiving timeliness threshold.

[0102] If the delay receiving time value is less than or equal to the receiving timeliness threshold, it is considered that the associated object has timely received the reminder, and an identification of a received state is generated; if the delay receiving time value is greater than the receiving timeliness threshold, it is considered that the associated object has delayed receiving the reminder, and an identification of a delay receiving state is generated; if the actual receiving time stamp is not included in the state response data and the un-received reason description information indicates that the associated object has not received the reminder, an identification of an un-received state is generated.

[0103] Step S1357: Associating and storing the state identification with the associated object identification and the task unit reminding identification to generate receiving state information of each task unit.

[0104] The generated state identification is associated and stored with the associated object identification and the task unit reminding identification. A data storage module is set in the system to combine the state identification, the associated object identification, and the task unit reminding identification to form the receiving state information of each task unit.

[0105] The receiving state information is stored in the database of the system for subsequent query, statistics, and analysis. At the same time, the receiving state information is regularly backed up to prevent data loss.

[0106] Step S136: The actual reminding time point, content integrity identifier and receiving status information are associated and encapsulated to generate a response data entry for each task unit, and the response data set is composed of the response data entries of all task units.

[0107] The actual reminding time point, content integrity identifier and receiving status information are associated and encapsulated. A data encapsulation module is set in the system, which combines the actual reminding time point, content integrity identifier and receiving status information of each task unit together to form a complete response data entry.

[0108] All the response data entries of the task units are summarized to form a response data set. The set is a comprehensive record of the response after the electronic alarm system performs the reminding operation.

[0109] Step S140: The response data set and the original task parameters in the detection task set are matched and analyzed to generate a performance evaluation result containing the reminding timeliness deviation, content accuracy deviation and receiving coverage deviation.

[0110] After obtaining the response data set, it needs to be matched and analyzed with the original task parameters in the detection task set to evaluate the performance of the electronic alarm system.

[0111] Step S141: The original trigger condition parameters of each task unit are extracted from the detection task set, including the expected time point of the timing reminder, the expected interval period of the repeated period reminder and the expected trigger time of the condition trigger reminder.

[0112] First, the original trigger condition parameters of each task unit are extracted from the detection task set. For the task unit of the timing reminder type, the expected time point is extracted, that is, the reminding time set by the user initially. For the task unit of the repeated period reminder type, the expected interval period is extracted, for example, whether it is a daily, weekly or monthly repeated reminder, and the starting and ending time range. For the task unit of the condition trigger reminder type, the expected trigger time is extracted, that is, the time when the reminder should be triggered when the specific condition is met.

[0113] Step S142: The actual reminding time point of each task unit is extracted from the response data set, and the time difference between the actual reminding time point and the expected time parameter in the original trigger condition parameter is calculated to generate a timeliness deviation value reflecting the degree of delay or advance of the reminder.

[0114] Then, the actual reminding time points of each task unit are extracted from the response data set. Then, the actual reminding time points are compared with the expected time parameters in the original trigger condition parameters, and the time difference value between them is calculated. If the actual reminding time is later than the expected time, it indicates that there is a reminder delay; if the actual reminding time is earlier than the expected time, there is a reminder advance. This time difference value is the timeliness deviation value, which can directly reflect the performance of the electronic alarm clock system in the accuracy of the reminding time.

[0115] Step S143: Extract the original reminding content information of each task unit from the detection task set, and the original reminding content information contains the number and sequence requirements of key content elements.

[0116] The original reminding content information of each task unit is extracted from the detection task set. The original reminding content information contains the number of key content elements and the sequence requirements of these elements. For example, a task unit reminding a child to go to school may require the original reminding content to contain key content elements such as "pack a backpack", "check homework", "remember to have breakfast", etc., and have certain sequence requirements.

[0117] Step S144: Extract the content integrity identification of each task unit from the response data set, and the content integrity identification contains the number of actual content elements and the sequence matching result.

[0118] The content integrity identification of each task unit is extracted from the response data set. The content integrity identification reflects the number of content elements contained in the actual reminding content and the sequence matching result of these elements with the original content elements. For example, the actual reminding content may only contain part of the key content elements, or the sequence of the elements is inconsistent with the original requirements.

[0119] Step S145: Calculate the difference value between the actual content element number and the original key content element number to generate the content element missing deviation value; calculate the matching degree of the actual content element sequence and the original sequence requirement to generate the content sequence deviation value; and perform weighted sum processing on the content element missing deviation value and the content sequence deviation value to generate the content accuracy deviation value.

[0120] The difference between the number of actual content elements and the number of original key content elements is calculated, which is the content element missing deviation value, which reflects the missing key content elements in the actual reminder content. At the same time, the matching degree of the actual content element sequence and the original sequence requirement is calculated to obtain the content sequence deviation value, which reflects the accuracy of the content element sequence. In order to comprehensively evaluate the accuracy of the content, the content element missing deviation value and the content sequence deviation value are weighted and summed. The specific weighting coefficient can be set according to the actual situation, for example, the content element missing deviation value can be given a higher weight, because the element missing may have a greater impact on the effectiveness of the reminder. The result obtained by weighted summation is the content accuracy deviation value.

[0121] Step S146: Extract the associated object identifier set of each task unit from the detection task set, which contains all object identifiers that need to receive reminders.

[0122] The associated object identifier set of each task unit is extracted from the detection task set. The associated object identifier set contains the identifiers of all objects that need to receive reminders for the task unit. In the electronic alarm clock system of the home scenario, the associated objects may be family members such as children, parents, etc., and each associated object has its corresponding identifier.

[0123] Step S147: Extract the receiving state information of each task unit from the response data set, calculate the proportion of the number of associated objects in the received state to the total number of associated object identifier sets to generate a receiving coverage proportion value; calculate the difference between the receiving coverage proportion value and the preset full-coverage target value to generate a receiving coverage deviation value.

[0124] The receiving state information of each task unit is extracted from the response data set. The number of associated objects in the received state is counted, and the proportion of this number to the total number of associated object identifier sets is calculated to obtain the receiving coverage proportion value. This proportion value reflects the coverage degree of the system reminder among the associated objects. Then, the receiving coverage proportion value is compared with the preset full-coverage target value, and the difference between them is calculated, which is the receiving coverage deviation value. The full-coverage target value is usually set to the proportion of all associated objects that can receive reminders in the ideal case.

[0125] Step S148: Perform associated integration processing on the timeliness deviation value, content accuracy deviation value and receiving coverage deviation value to generate a performance evaluation result containing each deviation type and corresponding deviation value.

[0126] Finally, the timeliness deviation value, the content accuracy deviation value and the receiving coverage deviation value are associated and integrated. The three types of deviation and the corresponding deviation values are combined to form a complete performance evaluation result. The performance evaluation result clearly shows the performance of the electronic alarm clock system in terms of timeliness, content accuracy and receiving coverage.

[0127] Step S150: generating a performance detection report containing the deviation types and the deviation degrees of each task unit according to the performance evaluation result, and outputting the performance detection report to the target display terminal.

[0128] After obtaining the performance evaluation result, a performance detection report needs to be generated according to the result, and the report needs to be output to the target display terminal.

[0129] Step S151: performing grade division processing on the timeliness deviation value in the performance evaluation result, the grade division processing being based on a preset deviation value range threshold, and generating a timeliness deviation grade containing a timely grade, a delay grade and an advance grade.

[0130] The timeliness deviation value in the performance evaluation result is subjected to grade division processing. According to a preset deviation value range threshold, the timeliness deviation value is divided into different grades. If the timeliness deviation value is within a smaller range, it indicates that the reminder time is accurate, and can be divided into a timely grade; if the deviation value is positive and exceeds a certain range, it indicates that the reminder is delayed, and is divided into a delay grade; if the deviation value is negative and exceeds a certain range, it indicates that the reminder is advanced, and is divided into an advance grade. For example, a smaller time range is preset as the boundary of the timely grade, and exceeding this range is divided into the delay grade or the advance grade according to the positive or negative situation.

[0131] Step S152: performing quality grading processing on the content accuracy deviation value in the performance evaluation result, the quality grading processing being based on a comprehensive evaluation standard of the number of missing content elements and the sequence matching degree, and generating a content accuracy deviation grade containing a complete grade, a partial missing grade and a serious missing grade.

[0132] The content accuracy deviation value in the performance evaluation result is subjected to quality grading processing. A set of evaluation standards is formulated by comprehensively considering the number of missing content elements and the sequence matching degree. If the number of missing content elements is small and the sequence matching degree is high, it can be divided into a complete grade; if there is a certain number of missing content elements or the sequence matching degree is general, it is divided into a partial missing grade; if the number of missing content elements is large and the sequence matching degree is very low, it is divided into a serious missing grade. Through this grading processing, the accuracy degree of the reminder content can be intuitively reflected.

[0133] Step S153: performing coverage classification processing on the reception coverage deviation value in the performance evaluation result, the coverage classification processing being based on the interval range of the reception coverage proportion value, to generate a reception coverage deviation category including a full-coverage class, a partial-coverage class and a low-coverage class.

[0134] The reception coverage deviation value in the performance evaluation result is subjected to coverage classification processing. According to the interval range of the reception coverage proportion value, it is divided into different categories. If the reception coverage proportion value is close to or reaches the preset full-coverage target value, it is classified into the full-coverage class; if the reception coverage proportion value is at a medium level, it is classified into the partial-coverage class; if the reception coverage proportion value is low, it is classified into the low-coverage class. This classification processing helps the evaluation system to remind the coverage effect in the associated object.

[0135] Step S154: establishing a deviation information summary table for each task unit, the deviation information summary table including the reminder identifier of the task unit, the reminder type, the timeliness deviation level, the content accuracy deviation level and the reception coverage deviation category.

[0136] A deviation information summary table is established for each task unit. The deviation information summary table includes the reminder identifier of the task unit, the reminder type, and the deviation level or category in terms of timeliness, content accuracy and reception coverage. Through this summary table, the performance of each task unit can be clearly seen. For example, for a task unit of “reminding to sleep at night”, the summary table will record its reminder identifier, reminder type (timed reminder), timeliness deviation level (such as timely level), content accuracy deviation level (such as complete level) and reception coverage deviation category (such as full-coverage class).

[0137] Step S155: performing statistical analysis processing on the deviation information summary table to generate a performance statistical result, the performance statistical result including the average timeliness deviation level, the average content accuracy deviation level and the average reception coverage deviation category of each reminder type.

[0138] The deviation information summary table is subjected to statistical analysis processing. The average timeliness deviation level, the average content accuracy deviation level and the average reception coverage deviation category of each reminder type are calculated. For example, the timeliness deviation levels of all task units of the timed reminder type are counted, and the average value is obtained to get the average timeliness deviation level of the timed reminder type. Through these average data, the performance of different reminder types in the overall performance can be understood.

[0139] Step S156: The deviation information summary table and the performance statistics are processed in a report format, a performance detection report containing table view, graphical view and text description is generated, and the performance detection report is sent to the target display terminal. The table view is used to show the deviation information of specific task units, the graphical view is used to show the trend distribution of performance, and the text description is used to explain the key deviation points and potential impact.

[0140] The deviation information summary table and the performance statistics are processed in a report format. The generated performance detection report contains table view, graphical view and text description. The table view is used to show the deviation information of each task unit in detail, so that the user can intuitively see the performance of specific tasks. The graphical view shows the trend distribution of performance through charts and other forms, such as comparison of average deviation levels of different reminder types, etc., so that the user can more clearly understand the overall trend of system performance. The text description part is used to explain the key deviation points and the potential impact of these deviations. For example, if the average timeliness deviation level of a certain reminder type is the delay level, the text description can analyze the possible reasons and the impact on user experience. Finally, the generated performance detection report is sent to the target display terminal, such as the user's mobile phone, computer and other devices, to facilitate the user to view and understand the performance of the electronic alarm system.

[0141] Further, Figure 2 A hardware structure schematic diagram of a performance detection system 100 for an electronic task reminder system for implementing the method provided by the embodiments of the present application is shown. As shown in Figure 2 The performance detection system 100 for the electronic task reminder system can include at least one processor 102 (the processor 102 can include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, a transmission device 106 for communication function, and a controller 108. Those skilled in the art can understand that Figure 2 The structure shown is only a schematic, which does not limit the structure of the performance detection system 100 for the electronic task reminder system. For example, the performance detection system 100 for the electronic task reminder system can also include more or less components than Figure 2 or have a different configuration than Figure 2 .

[0142] The memory 104 can be used to store software programs of application software and modules, such as program instructions corresponding to the method embodiments described above in the embodiments of the present application. The processor 102 performs various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the above-mentioned performance detection method for the electronic task reminding system. The transmission device 106 is used to obtain or send data via a network.

[0143] Those skilled in the art can understand that all or part of the steps of the above-mentioned embodiments can be completed by hardware, or by programs instructing relevant hardware to complete. The above-mentioned programs can be stored in a computer readable storage medium, and the above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

Claims

1. A performance testing method for an electronic task reminder system, characterized in that: The method comprises: Acquire a detection task set containing different reminder types, wherein the detection task set consists of multiple task units with independent reminder identifiers, each task unit including a reminder trigger condition, reminder content information, and an associated object identifier; Sending a reminder trigger instruction to the electronic task reminder system based on the detection task set, triggering the electronic task reminder system to perform a reminder operation corresponding to each task unit, and generating a reminder event record including a trigger timestamp; Recording a response data set after the electronic task reminder system executes a reminder operation, wherein the response data set includes the actual reminder time point of each task unit, the reminder content integrity identifier, and the associated object reception status identifier; Perform matching analysis on the response data set and the original task parameters in the detection task set to generate a performance evaluation result including a deviation in reminder timeliness, a deviation in content accuracy, and a deviation in reception coverage; A performance test report including the deviation type and deviation degree of each task unit is generated according to the performance evaluation result, and the performance test report is output to a target display terminal.

2. The performance testing method for an electronic task reminder system according to claim 1, characterized in that: The acquisition includes a set of detection tasks of different reminder types, including: Determine a set of reminder types to be detected, wherein the set of reminder types includes a timed reminder type, a recurring period reminder type, and a conditional trigger reminder type; Generate a corresponding task unit template for each reminder type, the task unit template including a basic trigger condition framework, content information structure and associated object identification rules; Fill in specific trigger condition parameters based on the task unit template, the trigger condition parameters including the absolute time point parameter of the scheduled reminder, the interval period parameter of the repetitive period reminder and the state threshold parameter of the conditional trigger reminder; Assign a unique reminder identifier to each filled task unit, which is used to establish a corresponding relationship between the task unit and subsequent response data; Performing validity verification on the trigger condition parameters of the task unit, wherein the validity verification includes checking the logical rationality of the time parameter, the triggerability of the condition threshold, and the format standardization of the associated object identifier; The task units that have passed the validity verification are encapsulated in a set to generate a detection task set containing different reminder types.

3. The performance testing method for the electronic task reminder system according to claim 2, characterized in that: The step of determining a set of reminder types to be detected includes: Analyze the function specification of the electronic task reminder system and extract the reminder function module information supported by the electronic task reminder system, wherein the function module information includes a basic timing reminder module, a cycle management module and a conditional response module; Determine the corresponding reminder type based on the functional module information, the scheduled reminder type corresponds to the single time point trigger function of the basic scheduled reminder module, the repeated periodic reminder type corresponds to the interval repeated trigger function of the period management module, and the conditional trigger reminder type corresponds to the state change trigger function of the conditional response module; Verify the compatibility between the reminder type and the actual supported functions of the electronic task reminder system, wherein the compatibility verification is confirmed by the execution results of the system function test case; Collect historical performance testing demand data, wherein the historical performance testing demand data includes statistical information on the frequency of users' attention to different reminder types; Adjust the detection priority of the reminder type according to the historical performance detection demand data, and the detection priority is used to determine the distribution ratio of the number of samples of each type when subsequent task units are generated; The finally determined timed reminder type, recurring period reminder type and condition trigger reminder type are collectively packaged to generate a reminder type set to be detected.

4. The performance testing method for an electronic task reminder system according to claim 1, characterized in that: The sending of a reminder trigger instruction to the electronic task reminder system based on the detection task set, triggering the electronic task reminder system to perform a reminder operation corresponding to each task unit, and generating a reminder event record including a trigger timestamp, includes: Parsing the reminder identifier and trigger condition parameters of each task unit in the detection task set, and generating a trigger instruction datagram that matches the interface protocol of the electronic task reminder system; Classify and group the trigger instruction datagram according to the reminder type of the task unit to generate a timing trigger group, a periodic trigger group and a conditional trigger group; An independent instruction sending queue is set for each trigger group, and the priority of the instruction sending queue is dynamically adjusted according to the real-time requirements of the reminder type; sending the trigger instruction datagram in the instruction sending queue to the electronic task reminder system; Monitoring the reception confirmation status of the trigger instruction datagram by the electronic task reminder system, recording the trigger instruction datagram that has not been successfully received and performing retransmission processing; When the electronic task reminder system performs a reminder operation, a reminder event record including a task unit reminder identifier and an actual triggering time is collected.

5. The performance testing method for the electronic task reminder system according to claim 4, characterized in that: The step of parsing the reminder identifier and trigger condition parameters of each task unit in the detection task set to generate a trigger instruction datagram matching the interface protocol of the electronic task reminder system includes: Extracting a reminder identification field of each task unit in the detection task set; Extracting trigger condition parameters of each task unit in the detection task set, wherein the trigger condition parameters include time point parameters, interval period parameters or status threshold parameters according to different reminder types; Obtaining an interface protocol document of the electronic task reminder system, wherein the interface protocol document includes field definitions, data types, and encoding format requirements of the instruction datagram; According to the field definition of the interface protocol document, the reminder identification field and the trigger condition parameter are mapped to the corresponding field positions of the instruction datagram; Performing verification processing on the field data types of the instruction datagram, the verification processing includes date and time format verification of the time point parameter, integer type verification of the interval period parameter, and value range verification of the status threshold parameter; The instruction datagram that has passed the verification is encoded and a trigger instruction datagram is generated, which includes a reminder identification field, a trigger condition parameter field and encoded data content.

6. The performance testing method for an electronic task reminder system according to claim 1, characterized in that: The response data set after recording the electronic task reminder system performing the reminder operation includes: Establishing a mapping relationship between the task unit reminder identifier in the reminder event record and the task unit in the detection task set, wherein the mapping relationship is established by matching the reminder identifiers; For each task unit having a mapping relationship, extracting an actual reminder time point from an output log of the electronic task reminder system; Performing content analysis on the reminder content output by the electronic task reminder system to generate a content element list, wherein the content element list includes key elements in the original reminder content information of the task unit; Performing element matching and comparison processing on the content element list and the original reminder content information of the task unit to generate a content integrity assessment result including the number of missing elements, wherein the content integrity identifier is generated according to the content integrity assessment result; Collecting the reception status information of each associated object for the reminder operation through the feedback interface of the associated object, wherein the reception status information includes the received status, the unreceived status and the delayed reception status; The actual reminder time point, content integrity identifier and receiving status information are associated and packaged to generate response data entries of each task unit. The response data set is composed of the response data entries of all task units.

7. The performance testing method for an electronic task reminder system according to claim 6, characterized in that: The collecting of the receiving status information of each associated object to the reminder operation through the feedback interface of the associated object includes: Determine the feedback interface type corresponding to the object identifier associated with each task unit, the feedback interface type including a message confirmation interface, an in-application notification receipt interface, and a device status query interface; Establish a data collection channel for each feedback interface type, which includes interface call parameters, timeout settings and error handling mechanisms; According to the correspondence between the reminder identifier of the task unit and the identifier of the associated object, a status query request is sent to the feedback interface of each associated object, wherein the status query request includes the reminder identifier of the task unit and a query time range parameter; Receive status response data returned by each feedback interface, wherein the status response data includes a timestamp of the actual receipt of the reminder operation by the associated object or a description of the reason for non-reception; Parsing the status response data, extracting the actual receiving timestamp and the actual reminder time point in the reminder event record, calculating the time difference, and generating a delayed receiving time value; Comparing the delayed reception time value with a preset reception timeliness threshold, generating an identification of a received state, a non-received state, or a delayed reception state; The state identifier is associated with the associated object identifier and the task unit reminder identifier and stored to generate receiving state information of each task unit.

8. The performance testing method for an electronic task reminder system according to claim 1, characterized in that: The matching and analyzing processing of the response data set and the original task parameters in the detection task set to generate a performance evaluation result including a reminder timeliness deviation, a content accuracy deviation, and a reception coverage deviation includes: Extracting original trigger condition parameters of each task unit from the detection task set, wherein the original trigger condition parameters include an expected time point of a scheduled reminder, an expected interval period of a repeated periodic reminder, and an expected triggering moment of a conditional triggered reminder; Extracting the actual reminder time point of each task unit from the response data set, calculating the time difference between the actual reminder time point and the expected time parameter in the original trigger condition parameter, and generating a timeliness deviation value reflecting the degree of reminder delay or advance; Extracting original reminder content information of each task unit from the detection task set, wherein the original reminder content information includes the quantity and sequence requirements of key content elements; Extracting a content integrity identifier of each task unit from the response data set, wherein the content integrity identifier includes the number and sequence matching results of actual content elements; Calculating the difference between the actual number of content elements and the original number of key content elements to generate a content element missing deviation value; calculating the degree of matching between the actual content element sequence and the original sequence requirement to generate a content sequence deviation value; performing a weighted summation process on the content element missing deviation value and the content sequence deviation value to generate a content accuracy deviation value; Extracting a set of associated object identifiers of each task unit from the detection task set, wherein the set of associated object identifiers includes all object identifiers that need to receive reminders; Extracting the reception status information of each task unit from the response data set, counting the ratio of the number of associated objects in the received state to the total number of the associated object identifier sets, and generating a reception coverage ratio value; calculating the difference between the reception coverage ratio value and a preset full coverage target value, and generating a reception coverage deviation value; The timeliness deviation value, content accuracy deviation value and reception coverage deviation value are correlated and integrated to generate a performance evaluation result including each deviation type and corresponding deviation value.

9. The performance testing method for an electronic task reminder system according to claim 8, characterized in that: Generating a performance test report including the deviation type and deviation degree of each task unit according to the performance evaluation result, and outputting the performance test report to a target display terminal, includes: Performing a grading process on the timeliness deviation value in the performance evaluation result, wherein the grading process is performed based on a preset deviation value range threshold to generate a timeliness deviation grade including a timely grade, a delayed grade, and an early grade; Performing quality grading on the content accuracy deviation values ​​in the performance evaluation results, the quality grading being based on a comprehensive evaluation standard of the number of missing content elements and the degree of sequence matching, to generate content accuracy deviation grades including complete, partially missing, and severely missing grades; Performing coverage classification processing on the reception coverage deviation value in the performance evaluation result, wherein the coverage classification processing is performed based on the interval range of the reception coverage ratio value to generate reception coverage deviation categories including full coverage class, partial coverage class, and low coverage class; Establish a deviation information summary table for each task unit, wherein the deviation information summary table includes the task unit's reminder identifier, reminder type, timeliness deviation level, content accuracy deviation level, and reception coverage deviation category; Performing statistical analysis on the deviation information summary table to generate performance statistics, wherein the performance statistics include the average timeliness deviation level, the average content accuracy deviation level, and the average reception coverage deviation category for each reminder type; The deviation information summary table and performance statistical results are formatted in a report format to generate a performance test report containing a table view, a graphical view and a text description, and the performance test report is sent to the target display terminal. The table view is used to display the deviation information of a specific task unit, the graphical view is used to display the trend distribution of performance, and the text description is used to illustrate key deviation points and potential impacts.

10. A performance testing system for an electronic task reminder system, characterized in that: The system comprises a processor and a readable storage medium, wherein the readable storage medium stores a program, and when the program is executed by the processor, the performance detection method for the electronic task reminder system according to any one of claims 1 to 9 is implemented.

Images