Service availability notification methods, devices, storage media, and MEP systems
By working with the Kong component in the service gateway, MEP enables automatic registration and availability status monitoring of edge services, solving the problem of low automation in edge service availability status observation and improving system reliability and user experience.
Patent Information
- Application Number
- CN202210246948.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-14
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-03-14
AI Technical Summary
In existing technologies, the level of automation for monitoring the availability status of edge services is low, and there is a lot of reliance on human intervention, resulting in long monitoring gaps, which can easily lead to a decline in user experience or system paralysis.
By working with the Kong component in the service gateway through the Mobile Edge Platform (MEP), automatic registration and availability status monitoring of edge services can be achieved. The availability status is obtained through active and passive inspection methods, and edge service users are notified in a timely manner through the service status change subscription interface.
It enables automatic observation and timely notification of edge service availability, reduces human intervention, and improves system reliability and user experience.
Smart Images

Figure CN116800754B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, and more particularly to a service availability notification method, apparatus, storage medium, and MEP system. Background Technology
[0002] Edge services refer to applications deployed physically close to users, devices, and data sources in edge computing scenarios, providing specific functionalities to the outside world via the network. Edge services can be accessed directly by user devices or invoked by other edge services. Given the remote, distributed deployment characteristics of edge services, service availability is difficult to guarantee, necessitating a comprehensive method for monitoring the availability status of edge services.
[0003] Existing technical solutions generally rely on manual periodic inspections, which have low levels of automation and excessive dependence on human intervention. The observation window for the availability status of edge services is long, which can easily lead to a decline in user experience or system paralysis due to the dependence on other edge services. Summary of the Invention
[0004] To address the aforementioned technical issues, embodiments of this application provide a service availability notification method, apparatus, storage medium, and MEP system, which enables automatic observation of edge service availability and timely notification to relevant users.
[0005] This application provides a service availability notification method applied to a mobile edge platform (MEP), the method comprising:
[0006] Receive edge service registration information sent by the edge service provider, and based on the edge service registration information, call a specific component in the service gateway to register the edge service provider to the service gateway;
[0007] The availability status information of the edge service provider is obtained from the specific component, and a notification message is sent to the edge service user based on the availability status information. The notification message is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0008] This application embodiment also provides a service availability notification method, applied to a specific component in a service gateway, the method comprising:
[0009] Accepting MEP calls registers the edge service provider with the service gateway;
[0010] The availability status information of the edge service provider is obtained and sent to the MEP. The availability status information is used by the MEP to send notification information to the edge service user. The notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0011] This application also provides a service availability notification method, applied to an edge service user, the method comprising:
[0012] The system receives notification information sent by the MEP, which is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0013] This application embodiment also provides a service availability notification method, applied to an edge service provider, the method comprising:
[0014] Send edge service registration information to the MEP, wherein the edge service registration information is used to trigger the MEP to call a specific component in the service gateway to register the edge service provider to the service gateway;
[0015] The specific component provides the MEP with the availability status information of the edge service provider, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0016] This application embodiment also provides a service availability notification device, applied to MEP, the device comprising:
[0017] The first receiving unit is used to receive edge service registration information sent by the edge service provider, and is also used to obtain availability status information of the edge service provider from the specific component;
[0018] The invocation unit is used to invoke a specific component in the service gateway based on the edge service registration information to register the edge service provider to the service gateway;
[0019] The first sending unit is configured to send notification information to the edge service user based on the availability status information. The notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0020] This application embodiment also provides a service availability notification device, applied to a specific component in a service gateway, the device comprising:
[0021] The registration unit is used to accept calls from the MEP to register the edge service provider with the service gateway;
[0022] The second receiving unit is used to obtain the availability status information of the edge service provider.
[0023] The second sending unit is used to send the availability status information to the MEP, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or notify the edge service provider that the availability status has changed.
[0024] This application embodiment also provides a service availability notification device, applied to an edge service user end, the device comprising:
[0025] The third receiving unit is used to receive notification information sent by the MEP, which is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0026] This application embodiment also provides a service availability notification device, applied to an edge service provider, the device comprising:
[0027] The third sending unit is used to send edge service registration information to the MEP, wherein the edge service registration information is used to trigger the MEP to call a specific component in the service gateway to register the edge service provider to the service gateway; it is also used to,
[0028] The specific component provides the MEP with the availability status information of the edge service provider, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0029] This application also provides a service availability notification device, including: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the service availability notification method described in this application.
[0030] This application also provides a computer-readable storage medium storing executable instructions, which, when executed by a processor, implement the service availability notification method described in this application.
[0031] This application also provides a MEP system, which includes a MEP and specific components in a service gateway. The MEP is used to implement the service availability notification method applied to the MEP, and the specific components in the service gateway are used to implement the service availability notification method applied to the specific components in the service gateway.
[0032] This application provides a service availability notification method, apparatus, storage medium, and MEP system. The service availability notification method includes: an edge service provider sending edge service registration information to the MEP; the MEP receiving the edge service registration information and, based on the edge service registration information, calling a specific component in the service gateway to register the edge service provider to the service gateway; the specific component in the service gateway obtaining the availability status information of the edge service provider based on the edge service registration information and sending the availability status information to the MEP; and an edge service user receiving notification information sent by the MEP. The solution provided by this application enables automatic observation of edge service availability and timely notification to relevant users. Attached Figure Description
[0033] Figure 1 A flowchart illustrating a service availability notification method provided in an embodiment of this application;
[0034] Figure 2 A flowchart illustrating the second service availability notification method provided in this application embodiment;
[0035] Figure 3 A flowchart illustrating the third service availability notification method provided in this application embodiment;
[0036] Figure 4 A flowchart illustrating the fourth service availability notification method provided in this application embodiment;
[0037] Figure 5 This is a schematic diagram of the structure of a service availability notification device provided in an embodiment of this application;
[0038] Figure 6 A schematic diagram of the structure of the second service availability notification device provided in the embodiments of this application;
[0039] Figure 7 A schematic diagram of the structure of the third service availability notification device provided in the embodiments of this application;
[0040] Figure 8 A schematic diagram of the structure of the fourth service availability notification device provided in the embodiments of this application;
[0041] Figure 9 A schematic diagram illustrating the composition of the fifth service availability notification device provided in this application embodiment;
[0042] Figure 10 This is a schematic diagram of the structure of the MEP system provided in the embodiments of this application;
[0043] Figure 11 A schematic diagram of the architecture of the service availability notification system provided in the application embodiments of this application;
[0044] Figure 12 A flowchart illustrating the service availability notification method provided in the application embodiments of this application. Detailed Implementation
[0045] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.
[0046] It should be noted that, in the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, in the embodiments of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0047] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.
[0048] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.
[0049] Edge services refer to applications deployed physically close to users, devices, and data sources in edge computing scenarios, providing specific functionalities to the outside world via the network. Edge services can be accessed directly by user devices or invoked by other edge services. Given the remote, distributed deployment characteristics of edge services, service availability is difficult to guarantee, necessitating a comprehensive method for monitoring the availability status of edge services.
[0050] Existing technical solutions generally employ manual periodic inspections, primarily using the following two methods:
[0051] Option A: Access the edge service provider from the perspective of the edge service user to check the availability of the edge service.
[0052] Option B: Access the edge service provider from the perspective of the edge service user, log in to the host where the edge service is deployed, execute commands, and check whether the edge service processes and ports are normal.
[0053] The two solutions mentioned above have the following drawbacks:
[0054] Option A: Low level of automation, and may cause system paralysis due to dependence on other edge services.
[0055] Option B: Low level of automation and excessive reliance on human intervention. Long window period for observing the availability of edge services, which may lead to a decline in user experience or system paralysis due to dependence on other edge services.
[0056] To address at least some of the aforementioned deficiencies, the following technical solutions based on embodiments of this application are proposed.
[0057] To provide a more detailed understanding of the features and technical content of this application, the implementation of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit this application. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0058] This application provides a service availability notification method applied to MEP. Figure 1 This is a flowchart illustrating a service availability notification method provided in an embodiment of this application, as shown below. Figure 1 As shown, the service availability notification method includes:
[0059] Step 101: Receive edge service registration information sent by the edge service provider, and register the edge service provider to the service gateway by calling a specific component in the service gateway based on the edge service registration information;
[0060] Step 102: Obtain the availability status information of the edge service provider from the specific component, and send notification information to the edge service user based on the availability status information. The notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0061] The European Telecommunications Standards Institute (ETSI) launched the Mobile Edge Computing (MEC) standard project in 2014. Its aim was to build a service platform at the edge of mobile networks, providing application developers and content providers with a cloud computing and Internet Technology (IT) environment. This platform would open up wireless network information, enabling high-bandwidth, low-latency service support and local management. In 2019, MEC was renamed Multi-access Edge Computing (MEC), focusing on new services and demands such as 5G, Wi-Fi, and fixed-line networks. It further open-sourced the technology using open application programming interfaces (APIs) to promote the industrialization of MEC.
[0062] A Mobile Edge Platform (MEP) refers to the set of features required to run MEC applications on a specific MEC host virtualization infrastructure and enable them to provide and use MEC services, and it can also provide several MEC services itself.
[0063] In this embodiment, the MEP, acting as a platform, directly interacts with both the edge service provider and the edge service user. It provides a service registration interface to the edge service provider and a service state change subscription interface to the edge service user. Specifically, after receiving edge service registration information from the edge service provider, the MEP's service registration interface requires the edge service provider to register with the service gateway if the edge service user wants to access the edge service.
[0064] A gateway, also known as an internetwork connector or protocol converter, is a complex network interconnection device that operates above the network layer, used only for interconnecting networks using different high-level protocols. A service gateway implements routing and filtering functions. Specifically, routing refers to the service gateway receiving all external requests and forwarding them to backend microservices. Filtering refers to a series of cross-cutting functions performed within the service gateway, such as permission verification, rate limiting, and monitoring.
[0065] In practical applications, taking permission verification as an example: if every service calls the same public service, it's equivalent to introducing the same permission verification code into each service, increasing the size of each service's JAR (Java Archive) package. Furthermore, since every service calls this public service, upgrading it becomes difficult, and the more features the public service has, the more difficult the upgrade becomes. If the permission verification method in the public service is changed, and all services are required to use the new method, all services would need to be re-imported, recompiled, and deployed—undoubtedly a tedious and repetitive task.
[0066] Based on this, a service gateway was introduced into the network device. With the service gateway, its filtering functionality allows permission checks to be written within the gateway's filters. Backend microservices don't need to concern themselves with permission check code, so the service's JAR file won't include permission check code, thus not increasing the JAR file size. Furthermore, if you want to change the permission check method, you only need to modify the permission check filter in the service gateway, without needing to upgrade all existing microservices.
[0067] In this embodiment, the MEP registers the edge service provider with the service gateway by calling a specific component within the service gateway. This specific component can be the Kong component. Kong is a highly available and easily scalable application programming interface (API) gateway project open-sourced by Mashape, based on OpenResty (Nginx + Lua modules). Built on Nginx and Apache Cassandra or PostgreSQL, Kong provides an easy-to-use REST (Representational State Transfer) API for operating and configuring the API management system. Therefore, it can horizontally scale multiple Kong servers and distribute requests evenly across services through front-end load balancing configurations to handle large volumes of network requests.
[0068] In practical applications, MEP can utilize the Kong component in the service gateway to obtain the availability status information of the edge service provider. The Kong component supports two availability status checking methods, which can be used individually or in combination.
[0069] The first type is proactive inspection, where a specific HTTP endpoint of the edge service provider is periodically requested to be accessed by the Kong component, and the availability status of the edge service provider is determined based on its response.
[0070] The second type is passive inspection, where the Kong component analyzes the accessing traffic and determines the availability status of the edge service provider based on their responses.
[0071] Based on this, in one embodiment, obtaining the availability status information of the edge service provider from the specific component includes:
[0072] Send health check information to the specific component, the health check information being used to query the availability status of the edge service provider from the specific component;
[0073] Receive availability status information of the edge service provider sent by the specific component.
[0074] In this embodiment, after the MEP sends health check information to the Kong component, the Kong component can determine the availability status of the edge service provider based on the response of the access address through active or passive checks. Based on the availability status information, it then sends notification information to the edge service user through a service status change subscription interface. Preferably, in this embodiment, the Kong component, under the call of the MEP, actively checks the edge service provider by accessing a specific HTTP endpoint (access address) and determines the availability status of the edge service provider based on the access result.
[0075] Based on this, in one embodiment, the availability status of the edge service provider is determined by the specific component in the following manner:
[0076] Access the access address of the edge service provider, and determine the availability status of the edge service provider based on the access result.
[0077] When accessing the address of the edge service provider, a Transmission Control Protocol (TCP) error, timeout, or HTTP status code may occur. A TCP error or timeout indicates a TCP connection failure, meaning the edge service provider is unavailable. An HTTP status code is a 3-digit numeric code used to indicate the HTTP response status of a web server, and can be categorized into healthy and unhealthy states. When the HTTP status code is in the unhealthy range, the edge service provider is unavailable.
[0078] Based on this, in one embodiment, if the access result is a Transmission Control Protocol (TCP) connection failure or an HTTP status within an unhealthy range, then the availability status of the edge service provider is unavailable.
[0079] If the access result indicates that the HTTP status is within the healthy range, then the availability status of the edge service provider is available.
[0080] In order to reduce network load and streamline the notification process, if the availability status of the edge service provider does not change, the edge service user may not be notified since it will not affect the edge service user.
[0081] Based on this, in one embodiment, sending notification information to the edge service user based on the availability status information includes:
[0082] Based on the availability status information, determine whether the availability status of the edge service provider has changed;
[0083] If the availability status of the edge service provider changes, the notification information is sent to the edge service user.
[0084] Furthermore, in the above embodiments, users who are edge service users only need to receive the availability status information of the edge service providers they have subscribed to.
[0085] Based on this, in one embodiment, before sending the notification information to the edge service user, the method further includes:
[0086] The system receives subscription information sent by the edge service user, which is used to subscribe to the MEP regarding the availability status of the edge service provider and / or changes in the availability status of the edge service provider.
[0087] In this process, the edge service user sends subscription information. After subscribing to the edge service provided by the relevant edge service provider, the MEP (Mobile Application Program) needs to authorize the edge service user and send notification information to the edge service user. This information is sent via a callback address, which is typically included in the subscription information.
[0088] Based on this, in one embodiment, the subscription information includes the callback address of the edge service user;
[0089] Sending notification information to edge service users based on the availability status information includes:
[0090] The callback address of the edge service user is obtained based on the subscription information;
[0091] Based on the availability status information, a notification message is sent to the callback address of the edge service user.
[0092] This application also provides a service availability notification method, which is applied to a specific component (specifically, the Kong component) in a service gateway. Figure 2 A flowchart illustrating the second service availability notification method provided in this application embodiment is shown below. Figure 2 As shown, the service availability notification method includes:
[0093] Step 201: Accept the MEP's call and register the edge service provider with the service gateway;
[0094] Step 202: Obtain the availability status information of the edge service provider and send the availability status information to the MEP. The availability status information is used by the MEP to send notification information to the edge service user. The notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0095] As described in the preceding embodiments, the specific component in the service gateway may be the Kong component. The Kong component is the core component of the service gateway, responsible for managing the file management of edge services and implementing routing for edge service calls. Furthermore, for registered edge services, the Kong component periodically checks the availability of the edge services and maintains the availability status information of the edge service providers for MEP queries.
[0096] Furthermore, taking the Kong component as an example, the embodiments of this application will be specifically described as follows:
[0097] The Kong component supports two availability status checks: active and passive. These checks can be used individually or in combination. This embodiment adopts the active check method, whereby the Kong component periodically sends access requests to a specific HTTP endpoint (access address) of the edge service provider, and the edge service provider responds based on the access requests and its availability status.
[0098] Based on this, in one embodiment, obtaining the availability status information of the edge service provider includes:
[0099] Access the access address of the edge service provider, and determine the availability status of the edge service provider based on the access result.
[0100] When accessing the address of the edge service provider, a Transmission Control Protocol (TCP) error, timeout, or HTTP status code may occur. A TCP error or timeout indicates a TCP connection failure, meaning the edge service provider is unavailable. An HTTP status code is a 3-digit numeric code used to indicate the HTTP response status of a web server, and can be categorized as healthy or unhealthy. When the HTTP status code is in the unhealthy range, the edge service provider is unavailable.
[0101] Based on this, in one embodiment, if the access result is a Transmission Control Protocol (TCP) connection failure or an HTTP status within an unhealthy range, then the availability status of the edge service provider is unavailable.
[0102] If the access result indicates that the HTTP status is within the healthy range, then the availability status of the edge service provider is available.
[0103] Specifically, the availability status of the edge service provider and / or notification information of changes in the availability status of the edge service provider need to be sent to the edge service user by the service status change subscription interface provided by the MEP.
[0104] Based on this, in one embodiment, sending the availability status information to the MEP includes:
[0105] Receive health check information sent by the MEP, the health check information being used to query the availability status of the edge service provider from the specific component;
[0106] Send the availability status information of the edge service provider to the MEP.
[0107] This application also provides a service availability notification method, applied to edge service users. Figure 3 A flowchart illustrating the third service availability notification method provided in this application embodiment is shown below. Figure 3 As shown, the service availability notification method includes:
[0108] Step 300: Receive notification information sent by MEP, the notification information being used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0109] In this context, the edge service user, as the user of the edge service, is the actual user of the edge service provider. When the edge service user needs to invoke a certain edge service, it must first obtain the registration information of the edge service provider from the MEP (Mobile Application Program) before making the actual edge service invocation.
[0110] When the edge service user needs to observe the availability status of the edge service provider and / or when the availability status of the edge service provider changes, it needs to subscribe to the availability status of the edge service provider through the service status change subscription interface provided by MEP.
[0111] Based on this, in one embodiment, before receiving the notification information sent by the MEP, the method further includes:
[0112] Send subscription information to the MEP, the subscription information being used to subscribe to the availability status of the edge service provider and / or changes in the availability status of the edge service provider.
[0113] The subscription information typically includes information such as the type of edge service subscribed by the edge service user, the callback address, the access address of the subscribed edge service, and the availability status of the subscribed edge service. After receiving the subscription information through the service status change subscription interface, the MEP saves the subscription information and periodically retrieves the availability status information of the edge service provider from the Kong component. Based on the callback address in the subscription information, it sends the notification information to the edge service user.
[0114] Based on this, in one embodiment, the subscription information includes the callback address of the edge service user, and the callback address is used by the MEP to send the notification information to the edge service user.
[0115] In this way, the edge service user can obtain the availability status of the edge service provider and / or notification information of changes in the availability status of the edge service provider, and promptly notify the operation and maintenance personnel based on the notification information. It can also take necessary protective measures to prevent a global paralysis caused by the blockage of a certain service.
[0116] This application also provides a service availability notification method, applied to an edge service provider. Figure 4 A flowchart illustrating the fourth service availability notification method provided in this application embodiment is shown below. Figure 4 As shown, the service availability notification method includes:
[0117] Step 401: Send edge service registration information to the MEP. The edge service registration information is used to trigger the MEP to call a specific component in the service gateway to register the edge service provider to the service gateway.
[0118] Step 402: Provide the MEP with the availability status information of the edge service provider through the specific component, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or notify the edge service user that the availability status of the edge service provider has changed.
[0119] The edge service provider offers specific edge services, such as data collection and analysis, including services like location services, vehicle-to-everything (V2X) services, and Internet of Things (IoT) services. After the edge service starts successfully and is ready, the MEP (Mobile Provider Interface) is invoked to register the edge service through the service registration interface. The MEP then calls a specific component in the service gateway to register the edge service provider with the service gateway, and simultaneously saves the registration information for future queries by edge service users.
[0120] The registration information should include necessary service information, such as edge service name, version number, edge service description, endpoint address, and inspection policy.
[0121] Furthermore, the availability status information of the edge service provider is determined by the access result, which is the response after the specific component accesses the access address of the edge service provider.
[0122] Based on this, in one embodiment, providing the edge service provider's availability status information to the MEP through the specific component includes:
[0123] In response to an access request from the specific component to the access address of the edge service provider, an access result is returned to the specific component. The access result is used by the specific component to determine the availability status information of the edge service provider and to provide the availability status information to the MEP.
[0124] The access result may be a Transmission Control Protocol (TCP) error, timeout, or an HTTP status code. A TCP error or timeout indicates a failed TCP connection, meaning the edge service provider's availability status is unavailable. An HTTP status code is a 3-digit numeric code used to indicate the HTTP response status of a web server, and can be categorized into healthy and unhealthy states. When the HTTP status code is within the unhealthy range, the edge service provider's availability status is unavailable.
[0125] Based on this, in one embodiment, if the access result is a TCP connection failure or an HTTP status within an unhealthy range, then the availability status of the edge service provider is unavailable.
[0126] If the access result indicates that the HTTP status is within the healthy range, then the availability status of the edge service provider is available.
[0127] This application provides a service availability notification method, wherein an edge service provider sends edge service registration information to a service access point (MEP); the MEP receives the edge service registration information sent by the edge service provider, and based on the edge service registration information, calls a specific component in a service gateway to register the edge service provider with the service gateway; the specific component in the service gateway obtains the availability status information of the edge service provider based on the edge service registration information, and sends the availability status information to the MEP; the edge service user receives the notification information sent by the MEP. The solution provided by this application enables automatic observation of edge service availability and timely notification to relevant users.
[0128] To implement the service availability notification method applied to the MEP side provided in the embodiments of this application, the embodiments of this application also provide a service availability notification device applied to the MEP. For example... Figure 5 As shown, Figure 5 This is a schematic diagram of a service availability notification device provided in an embodiment of this application. The service availability notification device includes:
[0129] The first receiving unit 501 is used to receive edge service registration information sent by the edge service provider, and is also used to obtain availability status information of the edge service provider from the specific component;
[0130] Invocation unit 502 is used to invoke a specific component in the service gateway based on the edge service registration information to register the edge service provider to the service gateway;
[0131] The first sending unit 503 is used to send notification information to the edge service user based on the availability status information. The notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0132] To implement the service availability notification method for a specific component in a service gateway provided in this application embodiment, this application embodiment also provides a service availability notification device applied to a specific component in a service gateway. For example... Figure 6 As shown, Figure 6A schematic diagram of a second service availability notification device provided in an embodiment of this application. The service availability notification device includes:
[0133] Registration unit 601 is used to accept calls from MEP to register the edge service provider to the service gateway;
[0134] The second receiving unit 602 is used to obtain the availability status information of the edge service provider.
[0135] The second sending unit 603 is used to send the availability status information to the MEP, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or notify the edge service provider that the availability status has changed.
[0136] To implement the service availability notification method for edge service users provided in this application embodiment, this application embodiment also provides a service availability notification device for edge service users. For example... Figure 7 As shown, Figure 7 This is a schematic diagram of the service availability notification device provided in an embodiment of this application.
[0137] The service availability notification device includes:
[0138] The third receiving unit 700 is used to receive notification information sent by the MEP, the notification information being used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
[0139] To implement the service availability notification method for edge service providers provided in this application, this application also provides a service availability notification device for edge service providers. Figure 8 As shown, Figure 8 This is a schematic diagram of the service availability notification device provided in an embodiment of this application.
[0140] The service availability notification device includes:
[0141] The third sending unit 800 is configured to send edge service registration information to the MEP, wherein the edge service registration information is used to trigger the MEP to call a specific component in the service gateway to register the edge service provider with the service gateway; and is also configured to,
[0142] The specific component provides the MEP with the availability status information of the edge service provider, wherein the availability status information is used by the MEP to send notification information to the edge service user, and the notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service user that the availability status of the edge service provider has changed.
[0143] Those skilled in the art should understand that Figure 5-8 The functions of each unit in the service availability notification device shown can be understood by referring to the relevant description of the aforementioned service availability notification method. Figure 5-8 The functions of each unit in the service availability notification device shown can be implemented by a program running on a processor or by specific logic circuits.
[0144] It should be noted that the service availability notification device provided in the above embodiments is only illustrated by the division of the above-described program units when performing service availability notifications. In actual applications, the above processing can be assigned to different program units as needed, that is, the internal structure of the system can be divided into different program units to complete all or part of the processing described above. In addition, the service availability notification device and the service availability notification method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.
[0145] Based on the hardware implementation of the above-mentioned program units, and in order to implement the service availability notification method provided in the embodiments of this application, the embodiments of this application also provide a service availability notification device. For example... Figure 9 As shown, Figure 9 This is a schematic diagram illustrating the composition of a fifth service availability notification device provided in this application embodiment; the service availability notification device 900 includes:
[0146] The processor 901 and memory 902 are used to store computer programs. The processor 901 is used to call and run the computer programs stored in the memory 902 to execute the service availability notification method described in the embodiments of this application, including the service availability notification method applied to MEP, specific components applied to service gateways, and edge service providers and edge service users.
[0147] In practical applications, such as Figure 9 As shown, the various components in the service availability notification device 900 are coupled together via a bus module 903. It is understood that the bus module 903 is used to implement communication between these components. In addition to a data bus, the bus module 903 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 9The general labeled all buses as bus module 903.
[0148] This application also provides a computer-readable storage medium, characterized in that it stores executable instructions, which, when executed by a processor 901, implement the service availability notification method described in this application, including the service availability notification method applied to a MEP, a specific component applied to a service gateway, and an edge service provider and an edge service user.
[0149] In some embodiments, the storage medium may be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM), etc.; or it may be a device that includes one or any combination of the above-mentioned memories.
[0150] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
[0151] As an example, executable instructions may, but do not necessarily, correspond to files in the file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files that store one or more modules, subroutines, or code sections).
[0152] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.
[0153] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0154] This application also provides a MEP system, such as Figure 10 The above, Figure 10 This is a schematic diagram of the structure of the MEP system provided in an embodiment of this application. The MEP system includes MEP1001 and a specific component 1002 in a service gateway, wherein MEP1001 is used to implement the above-described service availability notification method applied to the MEP, and the specific component 1002 in the service gateway is used to implement the above-described service availability notification method applied to a specific component in the service gateway.
[0155] The present application will be further described below with reference to application embodiments:
[0156] Figure 11 A schematic diagram of the architecture of the service availability notification system provided in the application embodiments of this application is shown below. Figure 11 As shown, the service availability notification system provided in this application embodiment includes: MEP system 1101 and third-party edge server 1102.
[0157] The MEP system 1101 includes an MEP 1001 and a specific component 1002 in a service gateway. The MEP 1001 is used to implement the service availability notification method applied to the MEP, and the specific component 1002 in the service gateway is used to implement the service availability notification method applied to a specific component in the service gateway.
[0158] The third-party edge service 1102 includes an edge service provider 11021 and an edge service user 11022. The edge service provider 11021 is used to implement the service availability notification method applied to the edge service provider, and the edge service user 11022 is used to implement the service availability notification method applied to the edge service user.
[0159] It should be noted that the specific processing procedures of MEP1101, the specific component 1002 in the service gateway, the edge service user 11022, and the edge service provider 11021 have been detailed above and will not be repeated here.
[0160] The service availability notification system provided in this application embodiment has high cohesion and loose coupling among MEP1101, specific component 1002 in the service gateway, edge service user 11022 and edge service provider 11021, which can effectively improve the maintainability of the service availability notification system and reduce the negative impact caused by the unavailability of a certain edge service.
[0161] Based on the above Figure 11 The architecture diagram shown in this application also illustrates a service availability notification method, such as... Figure 12 As shown, Figure 12 A flowchart illustrating the service availability notification method provided in the application embodiments of this application. The service availability notification method includes:
[0162] Step 1201: Edge service provider 11021 sends edge service registration information to MEP1001;
[0163] Step 1202: MEP1001 receives edge service registration information sent by edge service provider 11021, calls a specific component 1002 in the service gateway based on the edge service registration information to register the edge service provider 11021 to the service gateway, and sends health check information to the specific component 1002 in the service gateway;
[0164] Step 1203: Based on the edge service registration information, a specific component 1002 in the service gateway accesses the access address of the edge service provider 11021, obtains the availability status information of the edge service provider 11021, and sends the availability status information to MEP1001;
[0165] Step 1204: Edge service user 11022 sends subscription information to MEP1001 and receives notification information sent by MEP1001.
[0166] The service availability notification method provided in this application, through high cohesion and loose coupling between MEP1101, a specific component 1002 in the service gateway, the edge service user 11022, and the edge service provider 11021, effectively improves the maintainability of the service availability notification system. It promptly notifies the edge service user 11022 of the availability status information of the edge services it subscribes to, thereby timely notifying maintenance personnel to intervene and reduce the frequency of daily inspections and the workload of maintenance personnel, significantly alleviating maintenance work. The high cohesion and loose coupling between MEP1101, the specific component 1002 in the service gateway, the edge service user 11022, and the edge service provider 11021 also enhances user experience and the robustness of edge services. The edge service user 11022 can adjust its services promptly based on changes in the availability status of the edge service provider 11021, minimizing the impact and preventing a cascading system failure due to a single service interruption. It also saves hardware and network bandwidth resources, as the edge service user 11022 does not need to independently implement the availability status check of the edge service provider 11021, thus reducing the consumption of edge network bandwidth.
[0167] The technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.
[0168] In the several embodiments provided in this application, it should be understood that the disclosed methods and electronic devices can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0169] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.
[0170] In addition, each functional unit in the various embodiments of this application can be integrated into a second processing unit, or each unit can be a separate unit, or two or more units can be integrated into a unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.
[0171] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. A service availability notification method characterized by, Applied to the Mobile Edge Platform (MEP), the method includes: Receive edge service registration information sent by the edge service provider, and register the edge service provider to the service gateway by calling a specific component in the service gateway based on the edge service registration information; Send health check information to the specific component, the health check information being used to query the availability status of the edge service provider from the specific component; The system receives availability status information of the edge service provider sent by the specific component; the availability status information is obtained by the specific component through active inspection. The system receives subscription information sent by the edge service user, which is used to subscribe to the MEP regarding the availability status of the edge service provider and / or changes in the availability status of the edge service provider; the subscription information includes the callback address of the edge service user. The callback address of the edge service user is obtained based on the subscription information; Based on the availability status information, a notification message is sent to the callback address of the edge service user. The notification message is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
2. The method of claim 1, wherein, The availability status of the edge service provider is determined by the specific component in the following manner: Access the access address of the edge service provider, and determine the availability status of the edge service provider based on the access result.
3. The method according to claim 2, characterized in that, If the access result is a Transmission Control Protocol (TCP) connection failure or an HTTP status within an unhealthy range, then the availability status of the edge service provider is unavailable. If the access result indicates that the HTTP status is within the healthy range, then the availability status of the edge service provider is available.
4. The method of claim 1, wherein, Sending notification information to the callback address of the edge service user based on the availability status information includes: Based on the availability status information, determine whether the availability status of the edge service provider has changed; If the availability status of the edge service provider changes, the notification information is sent to the callback address of the edge service user.
5. A service availability notification method characterized by, Applied to edge service users, the method includes: Send subscription information to MEP, the subscription information being used to subscribe to the availability status of the edge service provider and / or the change in the availability status of the edge service provider, the subscription information including the callback address of the edge service user, the callback address being used by the MEP to send the notification information to the edge service user; The system receives notification information sent by the MEP, which is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed; the notification information is sent by the MEP to the edge service user based on availability status information; the availability status information is obtained by the MEP sending health check information to a specific component in the service gateway, and the MEP receives the availability status information of the edge service provider sent by the specific component; the availability status information is obtained by the specific component through active checking; the health check information is used to query the specific component for the availability status of the edge service provider.
6. A service availability notification apparatus characterized by comprising: Applied to MEP, the device includes: The first receiving unit is configured to receive edge service registration information sent by the edge service provider, and to send health check information to a specific component, wherein the health check information is used to query the specific component for the availability status of the edge service provider; receive availability status information of the edge service provider sent by the specific component, wherein the availability status information is obtained by the specific component through active checking; and receive subscription information sent by the edge service user, wherein the subscription information is used to subscribe to the MEP for the availability status of the edge service provider and / or changes in the availability status of the edge service provider; the subscription information includes the callback address of the edge service user. The invocation unit is used to invoke a specific component in the service gateway based on the edge service registration information to register the edge service provider to the service gateway; The first sending unit is configured to obtain the callback address of the edge service user based on the subscription information; and send notification information to the callback address of the edge service user based on the availability status information, wherein the notification information is used to notify the edge service user of the availability status of the edge service provider and / or to notify the edge service provider that the availability status of the edge service provider has changed.
7. A service availability notification apparatus characterized by comprising: The device, applied to edge service users, includes: The third receiving unit is configured to send subscription information to the MEP, the subscription information being used to subscribe to the availability status of the edge service provider and / or the change in the availability status of the edge service provider, the subscription information including the callback address of the edge service user, the callback address being used by the MEP to send the notification information to the edge service user; receiving notification information sent by the MEP, the notification information being used to notify the edge service user of the availability status of the edge service provider and / or the change in the availability status of the edge service provider; the notification information being sent by the MEP to the edge service user based on availability status information; the availability status information being obtained by the specific component through active checks, the health check information being used to query the specific component for the availability status of the edge service provider.
8. A service availability notification apparatus characterized by comprising: include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1-4, or the method as described in claim 5.
9. A computer-readable storage medium, characterized in that, The system stores executable instructions that, when executed by a processor, implement the method of any one of claims 1-4, or the method of claim 5.
10. A MEP system, characterized in that, The system includes specific components in the MEP and service gateway, wherein the MEP is used to implement the method of any one of claims 1-4.
Citation Information
Patent Citations
Pump provided with a vibration damping system
EP0011022A1
Identification of surface-associated Antigenes used for the diagnosis and therapy of tumours
EP2267156A2
Service detection method, rule configuration method, related equipment and medium
CN111404759A
Multi-access edge computing method, platform and system
CN111615128A
