Health state monitoring method, computer equipment, storage medium and product
By adding a health status monitoring interface between the MEP and ME APP instances, the mobile edge platform periodically obtains status indication information, which solves the problem of wasted resources in the existing technology and achieves efficient service instance monitoring and system stability assurance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2024-10-31
- Publication Date
- 2026-05-05
AI Technical Summary
In 5G edge scenarios, existing technologies require each MEC service instance to periodically send heartbeat messages, resulting in wasted network traffic and computing resources. Furthermore, the heartbeat mechanism implemented by ME APP for each service is not efficient enough.
A new health status monitoring interface is added between the MEP and ME APP instances. The mobile edge platform periodically sends information acquisition requests, receives and analyzes status indication information to assess the health status of application instances, and reduces the waste of network traffic and computing resources.
It improves the efficiency of monitoring service instances, reduces the waste of network traffic and computing resources, and ensures the stability and consistency of the system through anomaly indication information.
Smart Images
Figure CN121985366A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a health status monitoring method, computer device, storage medium, and product. Background Technology
[0002] In 5G edge scenarios, ME APP (Multi-access Edge Application) instances register the services they provide with MEP (Multi-access Edge Computing platform), and MEP needs to monitor the availability of MEC (Multi-access Edge Computing) services in real time.
[0003] In the current health monitoring mechanism provided by the protocol, each MEC service instance that has been registered on the MEC platform will periodically send a heartbeat message to the MEC platform to indicate that the MEC service instance is still running normally. However, the above health monitoring mechanism requires each third-party APP registered with the MEP to implement a heartbeat mechanism for each service provided by the APP. Implementing a heartbeat mechanism for each service by the APP will waste network traffic and computing resources. Summary of the Invention
[0004] This application provides a health status monitoring method, computer device, storage medium, and product, which can improve the monitoring efficiency of service instances while reducing the waste of network traffic and computing resources. The technical solution is as follows: On the one hand, a health status monitoring method is provided, which is executed by a mobile edge platform, and the method includes: The system periodically sends information retrieval requests to the first application instance through the health status monitoring interface; the first application instance is an application instance registered in the mobile edge platform, and interacts with the mobile edge platform through the health status monitoring interface. Receive status indication information from the request feedback based on the information obtained by the first application instance; The health status of the first application instance is determined based on the health status parameters in the status indication information.
[0005] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to implement the above-described health status monitoring method.
[0006] On the other hand, a computer-readable storage medium is provided, wherein at least one computer program is stored in the computer-readable storage medium, the computer program being loaded and executed by a processor to implement the above-described health status monitoring method.
[0007] On the other hand, a computer program product is provided, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform to implement the health status monitoring method provided in the various optional implementations described above.
[0008] The health status monitoring method provided in this application adds a health status monitoring interface between the application instance and the mobile edge platform. The mobile edge platform can periodically send information acquisition requests to the application instance through this health status monitoring interface, and determine the health status of the application instance based on the health status parameters in the status indication information fed back by the application instance. Through the above method, the mobile edge platform can determine the availability status of each service instance it produces based on the health status of the application instance, which improves the monitoring efficiency of service instances while reducing the waste of network traffic and computing resources.
[0009] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description
[0010] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0011] Figure 1 A flowchart of a health status monitoring method provided in an exemplary embodiment of this application is shown; Figure 2 A schematic diagram of a health status monitoring system provided in an exemplary embodiment of this application is shown; Figure 3 A flowchart illustrating another health status monitoring method provided by an exemplary embodiment of this application is shown; Figure 4 A flowchart of another health status monitoring method provided by an exemplary embodiment of this application is shown; Figure 5 An interactive schematic diagram of a health status monitoring method provided in an exemplary embodiment of this application is shown; Figure 6 A structural block diagram of a computer device illustrated in an exemplary embodiment of this application is shown; Figure 7A structural block diagram of another computer device illustrated in an exemplary embodiment of this application is shown. Detailed Implementation
[0012] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of methods consistent with some aspects of this application as detailed in the appended claims.
[0013] This application provides a health status monitoring method by adding a new interface between the MEP and the ME APP instance, namely a health status monitoring interface. This interface is used for information exchange between the MEP and the ME APP instance. Through the health status monitoring interface, the MEP can send request messages to the ME APP instance to detect the availability of all service instances produced by the ME APP instance, thereby improving the efficiency of detecting the health status of service instances while reducing the waste of network traffic and computing resources.
[0014] Figure 1 A flowchart of a health status monitoring method provided in an exemplary embodiment of this application is shown. This method can be executed by a mobile edge platform, such as... Figure 1 As shown, the method includes: Step 110: Periodically send information acquisition requests to the first application instance through the health status monitoring interface; the first application instance is an application instance registered in the mobile edge platform, which interacts with the mobile edge platform through the health status monitoring interface.
[0015] In 5G edge scenarios, mobile edge platforms need to provide service registration, discovery, and event notification functions. Application instances can register the service instances they provide with the mobile edge platform, so that the mobile edge platform can send availability change notifications of the service instances to application instances that have subscribed to the service instances. The first application instance is a mobile edge application instance registered in the mobile edge platform. In this embodiment, each application instance registered in the mobile edge platform establishes a corresponding health status monitoring interface with the mobile edge platform, so that the mobile edge platform can periodically send information acquisition requests to the first application instance through the health status monitoring interface corresponding to the first application instance. The information acquisition request is used to obtain the status indication information of the first application instance.
[0016] The period during which the mobile edge platform sends information acquisition requests to the first application instance can be customized by relevant personnel based on actual needs. The periods corresponding to different first application instances may be the same or different, and this application does not impose any restrictions on this.
[0017] Step 120: Receive status indication information from the first application instance based on the information acquisition request.
[0018] In this embodiment, the status indication information includes indication information for assessing the health status of the application instance, which can enable regular monitoring of the application's health status. The indication information can be health parameters. In step 120, the status indication information includes various health status parameters for determining the health status of the first application instance. The number and type of health status parameters can be limited based on actual needs. Therefore, determining the health status of the first application instance through status indication information can improve the comprehensiveness and accuracy of health status monitoring.
[0019] In this embodiment, the information acquisition request is used to instruct the first application instance to acquire and feedback status indication information. The information acquisition request may include the types of required health status parameters. After receiving the information acquisition request, the first application instance acquires various health status parameters indicated by the information acquisition request to form status indication information, and feeds back the status indication information to the mobile edge platform. Furthermore, the first application instance feeds back the status indication information to the mobile edge platform through the health status monitoring interface.
[0020] After receiving the status indication information, the mobile edge platform can associate and store the status indication information with the first application instance, so as to facilitate subsequent health status analysis of the first application instance based on the status indication information.
[0021] Step 130: Determine the health status of the first application instance based on the health status parameters in the status indication information.
[0022] After receiving the status indication information, the mobile edge platform can extract various health status parameters contained in the status indication information. The health status parameters are direct indicators used to evaluate the health status of application instances. Based on whether the health status parameters meet the corresponding health conditions, the health status of the first application instance under the corresponding parameter dimension can be indicated. Then, the overall health status of the first application instance can be determined based on a combination of multiple health status parameters.
[0023] In one possible implementation, different health status parameters correspond to different parameter health conditions, and these conditions can be set differently based on the judgment criteria for each parameter. When a health status parameter meets its corresponding parameter health condition, it is determined that the health status parameter passes the parameter judgment; when a health status parameter does not meet its corresponding parameter health condition, it is determined that the health status parameter fails the parameter judgment.
[0024] In one possible implementation, if the proportion of health status parameters in the status indication information that meet the corresponding health conditions exceeds a certain threshold, the health status of the first application instance is determined to be abnormal; if the proportion of health status parameters in the status indication information that meet the corresponding health conditions does not exceed the certain threshold, the health status of the first application instance is determined to be abnormal; further, if all health status parameters in the status indication information meet the corresponding health conditions, the health status of the first application instance is determined to be normal; if at least one health status parameter in the status indication information does not meet the corresponding health conditions, the health status of the first application instance is determined to be abnormal.
[0025] After determining the health status of the first application instance, the mobile edge platform can determine the availability status of each service instance produced by the first application instance based on the health status of the first application instance. By replacing service instance-level health monitoring with application instance-level health monitoring, the waste of network traffic and computing resources can be reduced.
[0026] In summary, the health status monitoring method provided in this application adds a health status monitoring interface between the application instance and the mobile edge platform. The mobile edge platform can periodically send information acquisition requests to the application instance through this health status monitoring interface, and determine the health status of the application instance based on the health status parameters in the status indication information fed back by the application instance. Through the above method, the mobile edge platform can determine the availability status of each service instance it produces based on the health status of the application instance, which improves the monitoring efficiency of service instances while reducing the waste of network traffic and computing resources.
[0027] Figure 2 A schematic diagram of a health status monitoring system corresponding to a health status monitoring method provided in an exemplary embodiment of this application is shown, such as... Figure 2 As shown, the health status monitoring system includes a mobile edge platform 210, a mobile edge application instance 220, and a mobile edge service instance 230.
[0028] The mobile edge platform 210 provides service instance registration, discovery, and event notification functions. The mobile edge application instance 220 runs as a virtual machine (VM) on top of the virtualization infrastructure provided by the mobile edge host, or it can run as a container, and it can interact with the mobile edge platform to consume and provide mobile edge services. The mobile edge application instance 220 can initiate a registration process with the mobile edge platform 210. Taking the registration process of the first application instance as an example, this registration process can be implemented as follows: The mobile edge platform receives a registration request sent by the first application instance, which contains the instance information of the first application instance; the instance information includes: application instance name, application instance identifier, Internet Protocol IP address, and health status monitoring interface information; After saving the instance information of the first application instance based on the registration request, a registration success response message is sent to the first application instance.
[0029] After each application instance is successfully registered, the mobile edge platform periodically sends information retrieval requests to each application instance based on the IP address of the application instance obtained from the registration. After receiving the information retrieval request, each mobile edge application instance constructs corresponding status indication information and sends it to the mobile edge platform, so that the mobile edge platform can determine the health status of the corresponding mobile edge application instance based on the received status indication information, and thus determine the availability status of the mobile edge services produced by the mobile edge application instance.
[0030] In one possible implementation, the health status parameters in the status indication information may include the availability status of each service instance produced by the first application instance, the generation timestamp of the information retrieval request, and the power-on timestamp of the first application instance. The generation timestamp of the information retrieval request is the timestamp when the mobile edge platform generates the request, and the mobile edge platform may include this timestamp when sending the information retrieval request to the first application instance. Based on this, the health status of the first application instance is determined to be normal if all health status parameters in the status indication information meet their corresponding health conditions; and the health status of the first application instance is determined to be abnormal if at least one health status parameter in the status indication information fails to meet its corresponding health condition. Figure 3 This application illustrates a flowchart of another health status monitoring method provided in an exemplary embodiment, which can be executed by a mobile edge platform, such as... Figure 3 As shown, the method includes: Step 310: Periodically send information acquisition requests to the first application instance through the health status monitoring interface; the first application instance is an application instance registered in the mobile edge platform, which interacts with the mobile edge platform through the health status monitoring interface.
[0031] Table 1 shows a parameter definition table for an information retrieval request provided in an exemplary embodiment of this application. As shown in Table 1, the information retrieval request may include the instance identifier of the first application instance, the service name of the service instance registered by the first application instance, and the generation timestamp of the information retrieval request. By sending the information retrieval request to the first application instance, the mobile edge platform can instruct the first application instance to provide feedback on the availability status of each service instance indicated by the information retrieval request, the power-on timestamp of the first application instance, and the generation timestamp extracted from the information retrieval request.
[0032] Table 1
[0033] Step 320: Receive status indication information from the first application instance based on the information acquisition request.
[0034] Table 2 shows a parameter definition table of status indication information provided in an exemplary embodiment of this application. As shown in Table 2, the status indication information includes the availability status of each service instance produced by the first application instance based on the information acquisition request, the generation timestamp of the information acquisition request, and the power-on timestamp of the first application instance; wherein, the generation timestamp of the information acquisition request can be extracted from the information acquisition request.
[0035] Table 2
[0036] After receiving the status indication information sent by the first application instance, the mobile edge platform can determine whether the availability status of each service instance is active, calculate the time difference between the generated timestamp and the current time, and determine whether the time difference exceeds the target duration and whether the power-on timestamp has changed. Based on the judgment results of various parameters, the health status of the first application instance is comprehensively determined. Among them, the health condition of the service instance's availability status is that the availability status is active, the health condition of the generated timestamp is that the timestamp between it and the current time has not exceeded the target duration, and the health condition of the power-on timestamp is that it has not changed.
[0037] Step 330: If the availability status of each service instance produced by the first application instance is active, the time difference between the generation timestamp of the information acquisition request and the current time is within the target duration, and the power-on timestamp of the first application instance does not change, then the health status of the first application instance is determined to be normal.
[0038] In other words, if all the above health status parameters meet the corresponding health conditions, the health status of the first application instance is determined to be normal.
[0039] Step 340: If the health status parameters contained in the status indication information satisfy any of the following conditions for the availability status of each service instance: inactivity, time difference between the generated timestamp and the current time exceeding the target duration, or power-on timestamp change, the health status of the first application instance is determined to be abnormal.
[0040] In other words, if any one or more of the above health status parameters fail to meet the corresponding health conditions, the health status of the first application instance is determined to be abnormal.
[0041] In this embodiment of the application, the mobile edge platform is further configured to, after determining the health status of the first application instance, provide feedback on the availability of the service instance to the application instance that has subscribed to the service instance produced by the first application instance based on the health status of the first application instance; in one possible implementation, in order to reduce the resource consumption required for interaction, the mobile edge platform may send an abnormal indication message to a second application instance, which is an application instance that has subscribed to the service instance produced by the first application instance, if it is determined that the health status of the first application instance is abnormal.
[0042] In other words, if the health status of the first application instance is normal, the mobile edge platform may not send information to the second application instance; if the health status of the first application instance is abnormal, it may send an abnormality indication message to the second application instance.
[0043] In one possible implementation, since health status parameters include multiple types, the health status anomaly of the first application instance may be caused by anomalies in different health status parameters. Based on this, the anomaly indication information sent by the mobile edge platform to the second application instance can be different depending on the different health status parameters that cause the health status anomaly of the first application instance. In the case where the abnormal health status is caused by the power-on timestamp in the health status parameters, this abnormality indication information is used to instruct the second application instance to update the service rules.
[0044] If the change in the power-on timestamp indicates that the health status of the first application instance is abnormal, it means that the first application instance may have been restarted due to system failure, maintenance operations, or other reasons. Since the state information of each service instance in the first application instance is reset after restarting, such as cached data, session state, temporary files, etc., configuration changes may also occur, such as configuration file updates or service version upgrades. If the second application instance still retains the service rules before the restart of the first application instance, it may lead to incompatibility between the service rules and the service instance, thereby affecting the application of the service instance by the second application instance. Therefore, when the mobile edge platform detects that the health status of the first application instance is abnormal due to the power-on timestamp, it sends an abnormal indication message to the second application instance to instruct the second application instance to update the service rules, thereby ensuring that the service rules and the state of the service instance remain synchronized, thus ensuring the normal invocation of the service instance.
[0045] Since all service instances produced by the first application instance will also restart when the first application instance restarts, the mobile edge platform can perform unified monitoring of all service instances produced by the first application instance by monitoring its power-on timestamp, thereby improving the monitoring efficiency and effectiveness of service instances.
[0046] In the event that an abnormal health status is caused by a timestamp generated in the health status parameters, this abnormality indication information is used to indicate that the service instance produced by the first application instance is unavailable.
[0047] If the time difference between the timestamp of the information retrieval request and the current time exceeds the target duration, indicating an abnormal health status of the first application instance, it means that the first application instance's response to the information retrieval request has timed out. The first application instance may have malfunctioned or experienced other anomalies, such as network interruption, application instance crash, excessive resource utilization, or configuration errors. In this case, the service instances it produces may also malfunction, and continued calls may lead to data loss, incorrect results, etc. Therefore, in order to ensure the reliability of service instances and maintain service consistency, and to prevent further risks, the mobile edge platform, when determining that the first application instance's health status is abnormal by the time difference between the timestamp of the information retrieval request and the current time exceeds the target duration, sends an anomaly indication message to the second application instance, indicating that the service instances produced by the first application instance are unavailable.
[0048] When a health status anomaly is caused by the availability status of a service instance in the health status parameters, the anomaly indication message indicates that the service instance with an inactive availability status is unavailable. In this case, when sending the anomaly indication message, the mobile edge platform can send the message to target application instances that have subscribed to inactive service instances to reduce resource consumption caused by unnecessary message transmission. This process can be implemented as follows: An exception indication message is sent to the target application instance, which indicates that the availability status of the target service instance has changed; the target application instance is an application instance that has subscribed to the target service instance in the second application instance.
[0049] In one possible implementation, if the health status of the first application instance is determined to be abnormal, information retrieval requests are continuously sent to the first application instance until the health status of the first application instance is determined to be normal based on the health status parameters in the received status indication information, and then normal indication information is sent to the second application instance.
[0050] Assuming the first application instance is registered on the mobile edge platform, even if the first application instance is determined to be abnormal, the mobile edge platform will still periodically send information retrieval requests to the first application instance. This is so that when the health status of the first application instance changes from abnormal to normal, it can promptly provide feedback on normal status to the second application instance that has subscribed to the service instance produced by the first application instance, so that the second application instance can make normal calls to the service instance and ensure the stability of the system.
[0051] In one possible implementation, upon receiving a deregistration request from a first application instance, the saved instance information of the first application instance is deleted, and the sending of information retrieval requests to the first application instance is stopped.
[0052] When the mobile edge platform receives a deregistration request from the first application instance, indicating that the first application instance is no longer providing services, the mobile edge platform releases the resources it occupies by deleting the instance information of the first application instance, thereby ensuring the effective utilization of platform resources. The mobile edge platform also does not need to continuously monitor the first application instance. Therefore, it stops sending information retrieval requests to the first application instance to reduce the resource consumption caused by meaningless information transmission.
[0053] In summary, the health status monitoring method provided in this application adds a health status monitoring interface between the application instance and the mobile edge platform. The mobile edge platform can periodically send information acquisition requests to the application instance through this health status monitoring interface, and determine the health status of the application instance based on the health status parameters in the status indication information fed back by the application instance. Through the above method, the mobile edge platform can determine the availability status of each service instance it produces based on the health status of the application instance, which improves the monitoring efficiency of service instances while reducing the waste of network traffic and computing resources.
[0054] Furthermore, if the health status of the first application instance is determined to be abnormal, the mobile edge platform can send an abnormality indication message to the second application instance that has subscribed to the service instance produced by the first application instance based on the cause of the abnormality. This allows the second application instance to respond to the abnormal situation of the first application instance based on the abnormality indication message, thereby ensuring the stability and consistency of the system.
[0055] Corresponding to Figure 1 or Figure 3 The embodiment shown, Figure 4 A flowchart of another health status monitoring method provided by an exemplary embodiment of this application is shown. This method can be executed by a first application instance registered in a mobile edge platform, such as... Figure 4 As shown, the method includes: Step 410: Periodically receive information acquisition requests sent by the mobile edge platform through the health status monitoring interface; the mobile edge platform and the first application instance exchange information through the health status monitoring interface.
[0056] Step 420: Based on the information acquisition request, status indication information is fed back to the mobile edge platform so that the mobile edge platform can determine the health status of the first application instance based on the health status parameters in the status indication information.
[0057] In one possible implementation, the health status parameters include the availability status of each service instance produced by the first application instance, the timestamp of the generation of the information retrieval request, and the power-on timestamp of the first application instance.
[0058] Before the mobile edge platform monitors the first application instance, the first application instance needs to register on the mobile edge platform. This process includes: A registration request is sent to the mobile edge platform. The registration request contains the instance information of the first application instance. The instance information includes: application instance name, application instance identifier, IP address, and health status monitoring interface information. Receive registration success response information; this registration success response information is sent by the mobile edge platform after it has completed the instance information saving operation of the first application instance based on the registration request.
[0059] For details regarding steps 410 and 420, please refer to [link / reference]. Figure 1 , Figure 2 or Figure 3 The relevant content corresponding to the first application instance in the illustrated embodiment will not be repeated here.
[0060] In summary, the health status monitoring method provided in this application adds a health status monitoring interface between the application instance and the mobile edge platform. The mobile edge platform can periodically send information acquisition requests to the application instance through this health status monitoring interface, and determine the health status of the application instance based on the health status parameters in the status indication information fed back by the application instance. Through the above method, the mobile edge platform can determine the availability status of each service instance it produces based on the health status of the application instance, which improves the monitoring efficiency of service instances while reducing the waste of network traffic and computing resources.
[0061] Figure 5 This illustration shows an interactive diagram of a health status monitoring method provided in an exemplary embodiment of this application. The method is interactively executed by a first application instance, a mobile edge platform, and a second application instance, as shown below. Figure 5 As shown, the method includes: S501, the first application instance sends a registration request to the mobile edge platform; correspondingly, after the mobile edge platform is powered on, it receives the registration request sent by the first application instance.
[0062] The registration request contains instance information for the first application instance, including the application instance name, application instance identifier, IP address, and health status monitoring interface information; wherein, changing the IP address may include at least one of IPv4 address and IPv6 address.
[0063] S502, the mobile edge platform saves the instance information of the first application instance.
[0064] After receiving the instance information of the first application instance, the mobile edge platform can confirm the received instance information and save it if it is correct.
[0065] S503, the mobile edge platform sends a registration success response to the first application instance; correspondingly, the first application instance receives the registration success response.
[0066] After verifying that the instance information of the first application instance is correct, the mobile edge platform sends a registration success response to the first application instance.
[0067] Furthermore, the mobile edge platform sets the initial health status of the first application instance to normal.
[0068] S504, the mobile edge platform periodically sends information acquisition requests to the first application instance through the health status monitoring interface, and correspondingly, the first application instance periodically receives information acquisition requests sent by the mobile edge platform through the health status monitoring interface.
[0069] The mobile edge platform can send information retrieval requests to the first application instance based on the saved IP address of the first application instance. When using IP addresses, the priority of using IPv4 addresses is higher than that of using IPv6 addresses. That is, IPv4 addresses are used first. If there is no IPv4 address but there is an IPv6 address, then the IPv6 address is used.
[0070] The information retrieval request may include the application instance identifier, the service name of the service instance that the application instance has registered, and the timestamp of the information retrieval request generation.
[0071] S505, the first application instance sends status indication information back to the mobile edge platform, and the mobile edge platform receives the status indication information sent back by the first application instance.
[0072] The status indication information includes the availability status of each service instance it produces, the generation timestamp obtained from the information retrieval request, and the power-on timestamp of the first application instance.
[0073] S506, if the availability status of each service instance produced by the first application instance in the health status parameters is active, the time difference between the generation timestamp of the information acquisition request and the current time is within the target duration, and the power-on timestamp of the first application instance does not change, the mobile edge platform determines that the health status of the first application instance is normal.
[0074] S507, if the power-on timestamp in the health status parameters changes, the mobile edge platform determines that the health status of the first application instance is abnormal.
[0075] S508, the mobile edge platform sends an exception indication message to the second application instance, indicating that the service rules need to be updated.
[0076] The second application instance is an application instance that has subscribed to the service instance produced by the first application instance.
[0077] S509, if the time difference between the generated timestamp in the health status parameters and the current time exceeds the target duration, the mobile edge platform determines that the health status of the first application instance is abnormal.
[0078] S510, the mobile edge platform sends an exception indication message to the second application instance, indicating that the service instance produced by the first application instance is unavailable.
[0079] S511, if the health status parameter indicates that the target service instance is inactive, the mobile edge platform determines that the health status of the first application instance is abnormal.
[0080] S512, the mobile edge platform sends an exception indication message to the target application instance, indicating that the availability status of the target service instance has changed.
[0081] The target service instance is one of the various service instances produced by the first application instance; the target application instance is an application instance in the second application instance that has subscribed to the target service instance.
[0082] S513, the mobile edge platform continues to send information retrieval requests to the first application instance.
[0083] Regardless of whether the health status of the first application is normal or abnormal, the mobile edge platform will periodically send information retrieval requests to the first application instance to monitor its health status. This allows for timely handling of any changes in the health status of the first application instance. Specifically, if the first application instance changes from a normal health status to an abnormal health status, an abnormal indication message will be sent to the second application instance. If the first application instance changes from an abnormal health status to a normal health status, a normal indication message will be sent to the first application instance.
[0084] S514, the first application instance sends a deregistration request to the mobile edge platform, and the mobile edge platform receives the deregistration request accordingly.
[0085] S515, the mobile edge platform deletes the saved instance information of the first application instance and stops sending information retrieval requests to the first application instance.
[0086] Figure 6A structural block diagram of a computer device 600 illustrated in an exemplary embodiment of this application is shown. This computer device can be implemented as a mobile edge platform as described above, or as a mobile edge host carrying application instances. The computer device 600 includes a processor (e.g., a central processing unit (CPU)) 601, a system memory 604 including random access memory (RAM) 602 and read-only memory (ROM) 603, and a system bus 605 connecting the system memory 604 and the processor 601.
[0087] The computer device 600 also includes a mass storage device 606 for storing an operating system 609, application instances 610, and other program modules 611. Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 604 and the mass storage device 606 mentioned above can be collectively referred to as memory.
[0088] According to various embodiments of this application, the computer device 600 can also be connected to a remote computer on a network, such as the Internet. That is, the computer device 600 can be connected to a network 608 via a network interface unit 607 connected to the system bus 605, or the network interface unit 607 can be used to connect to other types of networks or remote computer systems (not shown).
[0089] The memory also stores at least one computer program, by which the processor 601 executes all or part of the steps in the health status monitoring methods shown in the above embodiments.
[0090] Figure 7 This illustration shows a structural block diagram of another computer device 700 according to an exemplary embodiment of this application. The computer device 700 can be implemented as a mobile edge host carrying application instances as described above. For example, the computer device can be an Android terminal device; typically, the computer device 700 includes a processor 701 and a memory 702. The memory 702 may include one or more computer-readable storage media for storing at least one instruction, which is executed by the processor 701 to implement all or part of the steps in the data processing result verification method shown in the method embodiments of this application. In some embodiments, the computer device 700 may also optionally include a peripheral device interface 703 and at least one peripheral device. The processor 701, memory 702, and peripheral device interface 703 can be connected via a bus or signal line. Various peripheral devices can be connected to the peripheral device interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 704, a display screen 705, a camera assembly 706, an audio circuit 707, and a power supply 708. In some embodiments, the computer device 700 also includes one or more sensors 709. The one or more sensors 709 include, but are not limited to: an accelerometer 710, a gyroscope 711, a pressure sensor 712, an optical sensor 713, and a proximity sensor 714. Those skilled in the art will understand that... Figure 7 The structure shown does not constitute a limitation on the computer device 700, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.
[0091] In one exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one computer program that is loaded and executed by a processor to implement all or part of the steps in the health status monitoring method described above. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, or optical data storage device, etc.
[0092] In one exemplary embodiment, a computer program product is also provided, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer, cause the computer to perform the above-described actions. Figure 1 , Figure 3 , Figure 4 or Figure 5 All or part of the steps of the embodiments shown in any of the embodiments.
[0093] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the claims.
[0094] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A method for monitoring health status, characterized in that, The method is executed by a mobile edge platform, and the method includes: The system periodically sends information retrieval requests to the first application instance through the health status monitoring interface; the first application instance is an application instance registered in the mobile edge platform, and interacts with the mobile edge platform through the health status monitoring interface. Receive status indication information from the request feedback based on the information obtained by the first application instance; The health status of the first application instance is determined based on the health status parameters in the status indication information.
2. The method according to claim 1, characterized in that, Determining the health status of the first application instance based on the health status parameters in the status indication information includes: If, in the health status parameters, the availability status of each service instance produced by the first application instance is active, the time difference between the generation timestamp of the information acquisition request and the current time is within the target duration, and the power-on timestamp of the first application instance remains unchanged, then the health status of the first application instance is determined to be normal. If the health status parameters satisfy any of the following conditions: the availability status of each service instance includes inactivity, the time difference between the generated timestamp and the current time exceeds the target duration, or the power-on timestamp changes, the health status of the first application instance is determined to be abnormal.
3. The method according to claim 2, characterized in that, The method further includes: If the health status of the first application instance is determined to be abnormal, an abnormality indication message is sent to the second application instance, which is an application instance that has subscribed to the service instance produced by the first application instance.
4. The method according to claim 3, characterized in that, If the abnormal health status is caused by an abnormal power-on timestamp in the health status parameters, the abnormality indication information is used to instruct the second application instance to update the service rules.
5. The method according to claim 3, characterized in that, In the case where the abnormal health status is caused by the generation of a timestamp in the health status parameters, the abnormality indication information is used to indicate that the service instance produced by the first application instance is unavailable.
6. The method according to claim 3, characterized in that, If the health status anomaly is caused by an abnormality in the availability status of the service instance in the health status parameters, the method further includes: The exception indication information is sent to the target application instance, and the exception indication information is used to indicate that the availability status of the target service instance has changed; the target application instance is the application instance in the second application instance that has subscribed to the target service instance.
7. The method according to claim 3, characterized in that, The method further includes: If the health status of the first application instance is determined to be abnormal, the information acquisition request is sent to the first application instance again until the health status of the first application instance is determined to be normal based on the health status parameters in the received status indication information, and then normal indication information is sent to the second application instance.
8. The method according to claim 1, characterized in that, The method further includes: Receive a registration request sent by the first application instance, the registration request containing instance information of the first application instance; the instance information includes: application instance name, application instance identifier, Internet Protocol IP address, and health status monitoring interface information; After saving the instance information of the first application instance based on the registration request, a registration success response message is sent to the first application instance.
9. A method for monitoring health status, characterized in that, The method is executed by a first application instance registered in the mobile edge platform; the method includes: The system periodically receives information acquisition requests from the mobile edge platform through a health status monitoring interface; the mobile edge platform and the first application instance interact with each other via the health status monitoring interface. Based on the information acquisition request, status indication information is fed back to the mobile edge platform, so that the mobile edge platform can determine the health status of the first application instance based on the health status parameters in the status indication information.
10. The method according to claim 9, characterized in that, The health status parameters include the availability status of each service instance produced by the first application instance, the generation timestamp of the information acquisition request, and the power-on timestamp of the first application instance.
11. The method according to claim 10, characterized in that, The method further includes: A registration request is sent to the mobile edge platform. The registration request contains instance information of the first application instance. The instance information includes: application instance name, application instance identifier, IP address, and health status monitoring interface information. Receive registration success response information; the registration success response information is sent by the mobile edge platform after it has completed the instance information saving operation of the first application instance based on the registration request.
12. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one computer program, which is loaded and executed by the processor to implement the health status monitoring method as described in any one of claims 1 to 11.
13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to implement the health status monitoring method as described in any one of claims 1 to 11.
14. A computer program product, characterized in that, The computer program product includes a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions that, when executed by a computer device, cause the computer device to perform the health status monitoring method as described in any one of claims 1 to 11.