Edge cloud environment dynamic service registration method and device, equipment and storage medium

Abstract

The invention relates to the technical field of edge computing, and discloses an edge cloud environment dynamic service registration method and device, equipment and a storage medium, and the method comprises the steps: initializing each edge node; distributing a corresponding service ID for each edge node; generating a service SID corresponding to the service ID; when the edge node receives the route corresponding to the target service of the target terminal, the group attribute corresponding to the route is checked, and when the group attribute belongs to the service SID, the target service SID corresponding to the route is inquired; and returning the target service SID to the target terminal. According to the invention, services deployed at any edge computing node can be published to other edge nodes of the whole network. End users and devices can access services with unified identifications through nearby access edge nodes. The edge node provides the capability of forwarding the request nearby, and the terminal does not need to cross-domain access the far-end node.

Description

Technical Field

[0001] The present invention relates to the field of edge computing technology, and in particular to a method, device, equipment and storage medium for dynamic service registration in an edge cloud environment. Background Art

[0002] In recent years, with the popularization of the Internet of Things, the development of 5G and the rapid development of artificial intelligence, more and more intelligent terminal devices have been deployed and connected to the Internet. The speed and amount of data collected by these devices have increased rapidly, and the complexity of data processing has also increased. In this context, more and more data needs to be analyzed and responded to in real time or near real time on the edge nodes that are close to the terminal devices. Edge cloud is increasingly being adopted in this demand context. As a new type of cloud computing model, edge cloud emphasizes the deployment of computing resources to the edge of the physical world to meet the requirements of low latency, high bandwidth and real-time performance. The traditional data center cloud computing model focuses on hosting applications and data in the central data center. However, for some applications, especially those that require low latency, such as smart cities, self-driving cars and telemedicine, the centralized cloud computing model may have real-time and performance issues. Therefore, edge cloud can solve these problems by moving computing resources closer to users and devices.

[0003] In the related technology, in traditional data center cloud computing, a service registration center is generally deployed. Microservice instances register addresses with the service registration center. When accessing services within the data center, the instance address is obtained by querying the service registration center. When accessing services outside the data center, internal services are generally exposed to external use in the form of domain names through components similar to API gateways. For example, the Ingress component of K8S. In an edge cloud environment, there are many edge computing nodes, and they are distributed in different geographical locations. If a unified service registration center is used, a large number of nodes need to be maintained, which affects performance. In addition, a unified registration center cannot provide end users and devices with the ability to address services nearby. Due to the different computing resources of different edge nodes, the list of services deployed on the nodes is also different. The node that the device accesses nearby may not have the requested service deployed. Summary of the invention

[0004] In view of this, the present invention provides a method, device, equipment and storage medium for dynamic service registration in an edge cloud environment to solve the problem in existing edge cloud technology that edge computing nodes are difficult to support terminal users to call the required services nearby.

[0005] In a first aspect, the present invention provides a method for dynamic service registration in an edge cloud environment, the method comprising:

[0006] Initialize each edge node, establish routing between edge nodes, and divide the service ID range for each edge node;

[0007] Assign a corresponding service ID to each edge node;

[0008] Based on the service ID, generate the service SID corresponding to the service ID, and publish the service SID to the WAN through the BGP protocol;

[0009] When the edge node receives the route corresponding to the target service of the target terminal, it checks the community attribute corresponding to the route, and when the community attribute belongs to the service SID, it queries the target service SID corresponding to the route;

[0010] The target service SID is returned to the target terminal, so that the target terminal accesses the target service based on the target service SID.

[0011] In the present invention, unlike the unified service registration center used in the data center, when the service is deployed at the edge node, the service is automatically published to the entire network, and a service route accessible to the entire network is provided. Compared with the existing service registration mechanism based on the public domain name, it also provides the ability of nearby access, and the terminal always accesses the service through the nearest access edge node; when the accessed node does not deploy the service to be accessed, it provides the ability to forward to the edge node where the service is deployed. By using the SRv6 encoded service identifier and publishing the service SID route through BGP, the accessibility of the service at any edge node is guaranteed. By marking the SID route with the group attribute, the remote edge node can quickly filter the route. Using the lowest bit of the SRv6 encoded service ID, it is ensured that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge node through the routing table, and then determine the final destination address of the service through the detection mechanism. Using the SRv6 instruction mechanism, it is ensured that when the edge node accessed by the user does not deploy the access service, it can support nearby forwarding to the next one. Services deployed at any edge computing node can be published to other edge nodes in the entire network. End users and devices can access services with a unified identity through the nearest edge node. The edge node provides the ability to forward requests locally, and the terminal does not need to access the remote node across domains.

[0012] In an optional implementation, initializing each edge node includes:

[0013] Enable the IPV6 protocol stack and SRv6 function for each edge node, and allocate a corresponding IPV6 network segment for each edge node;

[0014] Publish the IPv6 prefix assigned by each edge node to the interconnected edge nodes through the BGP protocol;

[0015] Plan a service SID range for each edge node. The service SID range is used for service registration.

[0016] In this method, each edge node is initialized and the Locator of each edge node SRv6 instruction is set to the IPv6 address prefix assigned to the edge node. Since the address prefix of the edge node is published to the public network through BGP, the SRv6 instruction sent to the edge node can be correctly forwarded to the edge node by other nodes in the network.

[0017] In an optional implementation, assigning a corresponding service ID to each edge node includes:

[0018] Obtain a service identifier corresponding to each edge node, where the service identifier is used to represent the service identifier of the service to which the edge node belongs;

[0019] Request the WAN to allocate a globally unique service ID corresponding to each edge node;

[0020] Send the service ID assigned by the WAN to the SRv6 command orchestrator of the edge node.

[0021] In this method, by adding the acquisition of service identifiers based on the original functions of the service orchestrator, the service instance orchestrator requests the central service ID orchestrator to assign a globally unique service ID to the service. The server instance orchestrator sends the assigned service ID to the SRv6 instruction orchestrator, thereby realizing service instantiation and triggering the subsequent service registration process.

[0022] In an optional implementation, based on the service ID, a service SID corresponding to the service ID is generated, and the service SID is published to the wide area network through the BGP protocol, including:

[0023] After receiving the service ID, the SRv6 instruction scheduler of the edge node generates the SRv6 service instruction SID of the edge node;

[0024] Use the SRv6 command orchestrator to write the SRv6 service command SID into the local service registration database of the edge node;

[0025] The SRv6 service instruction SID is instantiated and published to other edge nodes in the WAN through the BGP protocol in the form of an IPV6 address combined with the community attribute value corresponding to the edge node.

[0026] In this method, service registration is achieved by generating an SRv6 service instruction SID for the edge node, writing the service instruction SID into the local service registration database of the edge node and instantiating the service instruction SID. Through the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPV6 address and a community attribute value is set. Through the community attribute value, other edge nodes in the management domain can quickly filter out the address routes of the service SRv6 instruction SID that belong to the management domain for the service discovery step.

[0027] In an optional implementation, querying the target service SID corresponding to the route includes:

[0028] Extract the lowest N bits of the route as the first service ID, and query whether the first service ID exists in the local service registration database of the current edge node;

[0029] When the first service ID does not exist in the local service registration database of the current edge node, write the first service ID into the local service registration database of the current edge node, and set the local service of the current edge node to no;

[0030] When the first service ID exists in the local service registration database of the current edge node, determining whether the first service ID is a local service of the current edge node;

[0031] When the first service ID is not a local service of the edge node, the routing service SID carried by the route is added to the detection list of the detection module, and the routing service SID is instantiated until the first service ID is a local service of the edge node;

[0032] When the first service ID is a local service of the edge node, it is determined that the target service SID corresponding to the route is instantiated at the current edge node.

[0033] In this method, the lowest bit of SRv6 is used to encode the service ID, ensuring that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge node through the routing table, and then determine the final destination address of the service through the detection mechanism. The SRv6 instruction mechanism is used to ensure that when the edge node accessed by the user does not deploy the access service, it can support forwarding to the next one nearby.

[0034] In an optional implementation, returning the target service SID to the target terminal so that the target terminal accesses the target service based on the target service SID includes:

[0035] Determine whether the service accessed by the target terminal is deployed at the access point corresponding to the target terminal;

[0036] When the service accessed by the target terminal is deployed at the access point corresponding to the target terminal, the local service SID of the access point is returned to the target terminal as the target service SID;

[0037] When the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal, determining whether the service accessed by the target terminal is instantiated at the current edge node;

[0038] When the service accessed by the target terminal is instantiated at the current edge node, the destination address of the target terminal is updated to the address of the current edge node to access the target service;

[0039] When the service accessed by the target terminal is not instantiated in the current edge node, the destination address of the target terminal is updated to the address of other edge nodes interconnected with the current edge node until the service accessed by the target terminal is instantiated in the edge node and the target service is accessed.

[0040] In this way, the user's demand for nearby access can be met. The end user can obtain services by accessing the nearest node with a unified service identifier. The mechanism of automatically discovering the nearest next hop of the service ensures that the service requested by the user can be quickly forwarded to the nearest PoP point when the access point is not deployed, meeting high availability and high real-time performance.

[0041] In a second aspect, the present invention provides an edge cloud environment dynamic service registration device, the device comprising:

[0042] The service initialization module is used to initialize each edge node, establish routing between edge nodes, and divide the service ID range for each edge node;

[0043] The service instantiation module is used to assign a corresponding service ID to each edge node;

[0044] The service registration module is used to generate a service SID corresponding to the service ID based on the service ID, and publish the service SID to the wide area network through the BGP protocol;

[0045] The service discovery module is used to check the community attribute corresponding to the route when the edge node receives the route corresponding to the target service of the target terminal, and when the community attribute belongs to the service SID, query the target service SID corresponding to the route;

[0046] The service access module is used to return the target service SID to the target terminal, so that the target terminal accesses the target service based on the target service SID.

[0047] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the edge cloud environment dynamic service registration method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0048] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the edge cloud environment dynamic service registration method of the first aspect or any corresponding embodiment thereof.

[0049] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions, which are used to enable a computer to execute the edge cloud environment dynamic service registration method of the above-mentioned first aspect or any corresponding embodiment. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 It is a flow chart of a method for dynamic service registration in an edge cloud environment according to an embodiment of the present invention.

[0052] Figure 2 It is a schematic diagram of an overall architecture of service registration according to an embodiment of the present invention.

[0053] Figure 3 4 is a schematic diagram of a system architecture of an edge PoP point according to an embodiment of the present invention.

[0054] Figure 4 It is a flow chart of another edge cloud environment dynamic service registration method according to an embodiment of the present invention.

[0055] Figure 5 It is a flow chart of another method for dynamic service registration in an edge cloud environment according to an embodiment of the present invention.

[0056] Figure 6 It is a structural block diagram of a dynamic service registration device for an edge cloud environment according to an embodiment of the present invention.

[0057] Figure 7 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0059] In the related technology, in traditional data center cloud computing, a service registration center is generally deployed. Microservice instances register addresses with the service registration center. When accessing services within the data center, the instance address is obtained by querying the service registration center. When accessing services outside the data center, internal services are generally exposed to external use in the form of domain names through components similar to API gateways. For example, the Ingress component of K8S. In an edge cloud environment, there are many edge computing nodes, and they are distributed in different geographical locations. If a unified service registration center is used, a large number of nodes need to be maintained, which affects performance. In addition, a unified registration center cannot provide end users and devices with the ability to address services nearby. Due to the different computing resources of different edge nodes, the list of services deployed on the nodes is also different. The node that the device accesses nearby may not have the requested service deployed.

[0060] In order to solve the above problems, an edge cloud environment dynamic service registration method is provided in an embodiment of the present invention, which is used in a computer device. It should be noted that its execution subject can be an edge cloud environment dynamic service registration device, which can be implemented as part or all of a computer device through software, hardware, or a combination of software and hardware. The computer device can be a terminal, a client, or a server. The server can be a single server or a server cluster composed of multiple servers. The terminal in the embodiment of the present application can be a smart phone, a personal computer, a tablet computer, or other intelligent hardware devices. In the following method embodiments, the execution subject is a computer device as an example for explanation.

[0061] The computer device in this embodiment is suitable for use scenarios in which the number of nodes in an edge cloud environment is large and distributed in different geographical locations, and the ability to provide terminal users with nearby addressing services is provided. The present invention provides a dynamic service registration method for an edge cloud environment. Unlike the unified service registration center used in a data center, when a service is deployed at an edge node, the service is automatically published to the entire network, and a service route accessible to the entire network is provided. Compared with the existing service registration mechanism based on a public domain name, it also provides the ability to access the nearest access. The terminal always accesses the service through the nearest accessed edge node; when the accessed node does not deploy the service to be accessed, the ability to forward to the edge node where the service is deployed is provided. By using the SRv6 encoded service identifier and publishing the service SID route through BGP, the accessibility of the service at any edge node is guaranteed. By marking the SID route with a group attribute, the remote edge node can quickly filter the route. Using the lowest bit of the SRv6 encoded service ID, it is ensured that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge node through the routing table, and then determine the final destination address of the service through the detection mechanism. The SRv6 instruction mechanism ensures that when the edge node accessed by the user does not deploy the access service, it can support the nearest forwarding to the next one. Services deployed on any edge computing node can be published to other edge nodes in the entire network. End users and devices can access services with a unified identity through the nearest edge node. The edge node provides the ability to forward requests nearby, and the terminal does not need to cross domains to access remote nodes.

[0062] According to an embodiment of the present invention, an embodiment of a dynamic service registration method for an edge cloud environment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that shown here.

[0063] In this embodiment, a method for dynamic service registration in an edge cloud environment is provided, which can be used in the above-mentioned computer device. Figure 1 is a flow chart of a method for dynamic service registration in an edge cloud environment according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0064] Step S101, initializing each edge node, establishing routes between edge nodes, and dividing a service ID range for each edge node.

[0065] In one example, the Locator of the SRv6 instruction of each edge PoP point is set to the IPv6 address prefix assigned to this node. Since the address prefix of this node is published to the public network through BGP, the SRv6 instruction sent to this node can be correctly forwarded to this node by other nodes in the network. Among them, the PoP point (Point-of-Presence) is the point of entry in the enterprise network, providing Internet access, wide area connection and telephone service.

[0066] Step S102: assign a corresponding service ID to each edge node.

[0067] In one example, in an edge cloud environment, there are multiple ways to deploy services on edge nodes. A typical deployment method is to deploy a service container. Based on the original function of the service orchestrator, a new function is added to assign a corresponding service ID to each edge node for service registration.

[0068] Step S103: Based on the service ID, a service SID corresponding to the service ID is generated, and the service SID is published to the wide area network through the BGP protocol.

[0069] In one example, after receiving the assigned service ID, the SRv6 instruction scheduler generates the SRv6 service instruction SID of the current node, writes the instruction SID into the local service registration database, instantiates the SRv6 SID, and publishes the service SID.

[0070] Step S104, when the edge node receives the route corresponding to the target service of the target terminal, it checks the community attribute corresponding to the route, and when the community attribute belongs to the service SID, queries the target service SID corresponding to the route.

[0071] In one example, when the remote PoP receives a route, it checks the community attribute of the route, and if the community attribute belongs to the service SID, it performs a service discovery step.

[0072] Step S105: Return the target service SID to the target terminal, so that the target terminal accesses the target service based on the target service SID.

[0073] In one example, the terminal device sets the DNS server address as the access address of the PoP point. The terminal device initiates access. If the accessed service is instantiated locally, the destination address is updated to the container address according to the operation steps of the SRv6 instruction, and the local service is accessed. If the accessed service is not local, the destination address is updated to the service SID of the remote node according to the operation steps of the SRv6 instruction, and the request is forwarded to other nearby PoP points. After the remote PoP point receives and processes the service request, it returns it directly to the terminal.

[0074] In one implementation scenario, Figure 2 is a schematic diagram of an overall architecture of service registration according to an embodiment of the present invention, such as Figure 2 As shown in the figure, each user User interacts with the corresponding PoP for data; the PoP applies for a service ID from the service ID orchestrator, and the service ID orchestrator sends the service ID of the PoP to the corresponding PoP; the PoP and the operator edge routing node PE in the wide area / Internet use the BGP protocol belly routing to forward the service request nearby, and the remote PoP receives and processes the service request and returns it directly to the terminal.

[0075] Figure 3 is a schematic diagram of a system architecture of an edge PoP point according to an embodiment of the present invention, such as Figure 3 As shown in the figure, each PoP point uses a 64-bit IPv6 address prefix. The function field of the SRv6 instruction is configured as 0x00ff and is 32 bits long. The Arguments field is 32 bits long. The service identifier is in the form of a service domain name. PoP points can be deployed in different autonomous domains and publish routes through the BGP protocol. After receiving the service ID sent by the service ID orchestrator, each edge PoP point instantiates the service through the service instance orchestrator and sends the service ID to the SRv6 instruction orchestrator; after receiving the assigned service ID, the SRv6 instruction orchestrator generates the SRv6 service instruction SID of this node, instantiates the SRv6 SID, and the SRv6 instruction orchestrator writes the instruction SID into the local service registration database; uses the SRv6 encoded service identifier and publishes the service SID route through BGP; using the lowest bit of SRv6 to encode the service ID, the access PoP point can quickly filter out the matching remote or local nodes through the routing table, and determine the final destination address of the service through the detection mechanism; instantiates the SRv6 SID and writes it into the FIB table; through the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPV6 address and sets the community attribute value.

[0076] The edge cloud environment dynamic service registration method provided in this embodiment is different from the unified service registration center used in the data center. When the service is deployed on the edge node, the service is automatically published to the entire network and a service route accessible to the entire network is provided. Compared with the existing service registration mechanism based on the public domain name, it also provides the ability of nearby access. The terminal always accesses the service through the nearest access edge node; when the accessed node does not deploy the service to be accessed, it provides the ability to forward to the nearest edge node where the service is deployed. By using the SRv6 encoded service identifier and publishing the service SID route through BGP, the accessibility of the service at any edge node is guaranteed. By marking the SID route with the group attribute, the remote edge node can quickly filter the route. Using the lowest bit of the SRv6 encoded service ID, it is ensured that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge node through the routing table, and then determine the final destination address of the service through the detection mechanism. Using the SRv6 instruction mechanism, it is ensured that when the edge node accessed by the user does not deploy the access service, it can support the nearest forwarding to the next one. Services deployed at any edge computing node can be published to other edge nodes in the entire network. End users and devices can access services with a unified identity through the nearest edge node. The edge node provides the ability to forward requests locally, and the terminal does not need to access the remote node across domains.

[0077] In this embodiment, a method for dynamic service registration in an edge cloud environment is provided, which can be used in the above-mentioned computer device. Figure 4 is a flow chart of another edge cloud environment dynamic service registration method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0078] Step S401, initialize each edge node, establish routing between edge nodes, and divide a service ID range for each edge node.

[0079] In an optional implementation, initializing each edge node includes:

[0080] Step a1: Enable the IPV6 protocol stack and SRv6 function for each edge node, and allocate a corresponding IPV6 network segment for each edge node.

[0081] Step a2: publish the IPv6 prefix allocated by each edge node to the interconnected edge nodes through the BGP protocol.

[0082] Step a3: plan a service SID range for each edge node, and the service SID range is used for service registration.

[0083] In one example, when enabling an edge PoP point, the following initialization operations are performed:

[0084] 1) Enable the IPV6 protocol stack and SRv6 function for each edge PoP. And allocate an IPV6 network segment. Generally, large cloud computing providers can apply for an IPv6 address pool from the operator in the computer room of each deployment node. According to the size of the address pool applied for, an available IPv6 address prefix can be allocated to the edge PoP point.

[0085] 2) The PoP point publishes the IPv6 prefix assigned by the node to the interconnected PE nodes through the BGP protocol. In a common edge cloud environment, PoP points in different regions are located in different autonomous domains. Using BGP to publish routes can ensure the reachability of each PoP point.

[0086] 3) Plan the SID range for service registration. In the SRv6 protocol, the IPV6 address is usually used as an instruction, and is divided into the following three parts from high to low in network byte order: Locator, Function, and Arguments. In the present invention, the Locator of the SRv6 instruction of each edge PoP point is set to the IPv6 address prefix assigned to this node. Since the address prefix of this node is published to the public network through BGP, the SRv6 instruction sent to this node can be correctly forwarded to this node by other nodes in the network. On all edge PoP nodes, the same Function segment is set to identify the dynamic service registration function. The lowest N bits are used to map the service ID (Service ID).

[0087] In this method, each edge node is initialized and the Locator of each edge node SRv6 instruction is set to the IPv6 address prefix assigned to the edge node. Since the address prefix of the edge node is published to the public network through BGP, the SRv6 instruction sent to the edge node can be correctly forwarded to the edge node by other nodes in the network.

[0088] Step S402: assign a corresponding service ID to each edge node.

[0089] Specifically, the above step S402 includes:

[0090] Step S4021, obtaining a service identifier corresponding to each edge node.

[0091] In the embodiment of the present invention, the service identifier is used to represent the service identifier of the service to which the edge node belongs.

[0092] Step S4022: Request the wide area network to allocate a globally unique service ID corresponding to each edge node.

[0093] Step S4023, sending the service ID allocated by the wide area network to the SRv6 instruction orchestrator of the edge node.

[0094] In one example, in an edge cloud environment, there are multiple ways to deploy services on edge nodes. A typical deployment method is to deploy a service container. In the present invention, based on the original function of the service orchestrator, the following new functions are added to implement service registration:

[0095] Step 1, obtain the service identifier. The service container image will set the environment parameters, including the service identifier of the service to which the container belongs. In the present invention, the service identifier is identified by the service domain name, for example, service-a.tenant-A.edge.com. Where service-a is the service name, tenant-A is the tenant name, and the service domain name identifier is not limited in the present invention.

[0096] Step 2: The service instance orchestrator requests the central service ID orchestrator to assign a globally unique service ID to the service. The service ID orchestrator queries the database to check whether other instances of the service domain have been registered. If so, the previously assigned service ID is returned. If not, an unused service ID is assigned.

[0097] Step 3: The server instance orchestrator sends the assigned service ID to the SRv6 instruction orchestrator, triggering the service registration process.

[0098] In this method, by adding the acquisition of service identifiers based on the original functions of the service orchestrator, the service instance orchestrator requests the central service ID orchestrator to assign a globally unique service ID to the service. The server instance orchestrator sends the assigned service ID to the SRv6 instruction orchestrator, thereby realizing service instantiation and triggering the subsequent service registration process.

[0099] Step S403: Generate a service SID corresponding to the service ID based on the service ID, and publish the service SID to the wide area network through the BGP protocol.

[0100] Specifically, the above step S403 includes:

[0101] Step S4031: After receiving the service ID, the SRv6 instruction scheduler of the edge node generates an SRv6 service instruction SID of the edge node.

[0102] Step S4032: Use the SRv6 instruction orchestrator to write the SRv6 service instruction SID into the local service registration database of the edge node.

[0103] Step S4033, instantiate the SRv6 service instruction SID, and publish the SRv6 service instruction SID to other edge nodes in the wide area network in the form of an IPV6 address in combination with the community attribute value corresponding to the edge node through the BGP protocol.

[0104] In one example, service registration is implemented through the following steps: Step (a) After the SRv6 instruction scheduler receives the assigned service ID, it generates the SRv6 service instruction SID of this node. According to the initialization process plan, the Locator part of the SRv6 service instruction is the IPV6 address prefix of this node. The Function part is unified to one value across the entire network. The lowest N bits of the Arguments part are filled with the assigned service ID. For example, the IPV6 address prefix of this node is 2001:db8:1:: / 64. The service registration Function is defined as S, and the service ID is assigned to A. Then the SID of the SRv6 service instruction generated by this service is 2001:db8:1:S:A. The length of the service ID field is reasonably configured according to the scale of the number of services. A 32-bit service ID length can provide up to 4294967296 service IDs for registration.

[0105] Step (ii) The command scheduler writes the command SID into the local service registration database. Table 1 is an entry table of the local service registration database. The entry definition of the local service registration database is shown in Table 1:

[0106] Table 1

[0107]

[0108] The column "Whether it is a local service" identifies the instance of the service domain name and whether it is instantiated on this node. In this step, the service is instantiated by the local node, and the generated SRv6 service instruction SID is written in the column "Local Service SID".

[0109] Step (iii) instantiates the SRv6 SID and writes the following operations into the FIB table: When the destination address of the message is service SID: 2001:db8:1:S:f001 (local service SID), the operations include:

[0110] 1. The Segment Left field is reduced by 1;

[0111] 2. Update the destination address to the container address;

[0112] 3. Forward the message to the next hop.

[0113] Step (iv) publishes the service SID, and publishes the service SID to other nodes through the BGP protocol in the form of a 128-bit IPV6 address and sets a community attribute value. The purpose of setting the community attribute value is that other PoP nodes in the management domain can quickly filter out the address route of the service SRv6 instruction SID in the management domain for the service discovery step.

[0114] In this method, service registration is achieved by generating an SRv6 service instruction SID for the edge node, writing the service instruction SID into the local service registration database of the edge node and instantiating the service instruction SID. Through the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPV6 address and a community attribute value is set. Through the community attribute value, other edge nodes in the management domain can quickly filter out the address routes of the service SRv6 instruction SID that belong to the management domain for the service discovery step.

[0115] Step S404: When the edge node receives the route corresponding to the target service of the target terminal, it checks the community attribute corresponding to the route. When the community attribute belongs to the service SID, it queries the target service SID corresponding to the route. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.

[0116] Step S405: Return the target service SID to the target terminal, so that the target terminal can access the target service based on the target service SID. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.

[0117] The edge cloud environment dynamic service registration method provided in this embodiment initializes each edge node and sets the Locator of each edge node SRv6 instruction to the IPv6 address prefix assigned to the edge node. Since the address prefix of the edge node is published to the public network through BGP, the SRv6 instruction sent to the edge node can be correctly forwarded to the edge node by other nodes in the network. By adding the acquisition of service identifiers based on the original function of the service orchestrator, the service instance orchestrator requests the central service ID orchestrator to assign a globally unique service ID to the service, and the server instance orchestrator sends the assigned service ID to the SRv6 instruction orchestrator, thereby realizing service instantiation and facilitating the triggering of subsequent service registration processes. Service registration is realized by generating the SRv6 service instruction SID of the edge node, writing the service instruction SID into the local service registration database of the edge node and instantiating the service instruction SID. Through the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPV6 address and setting a community attribute value. Through the community attribute value, other edge nodes in the management domain can quickly filter out the address routes of the service SRv6 instruction SID belonging to the management domain for the service discovery step.

[0118] In this embodiment, a method for dynamic service registration in an edge cloud environment is provided, which can be used in the above-mentioned computer device. Figure 5 is a flowchart of another edge cloud environment dynamic service registration method according to an embodiment of the present invention. Figure 5 As shown, the process includes the following steps:

[0119] Step S501: Initialize each edge node, establish routing between edge nodes, and divide the service ID range for each edge node. Figure 4 Step S401 of the illustrated embodiment will not be described in detail here.

[0120] Step S502: assign a corresponding service ID to each edge node. Figure 4 Step S402 of the illustrated embodiment will not be described in detail here.

[0121] Step S503: Generate a service SID corresponding to the service ID based on the service ID, and publish the service SID to the WAN through the BGP protocol. Figure 4 Step S403 of the illustrated embodiment will not be described in detail here.

[0122] Step S504, when the edge node receives the route corresponding to the target service of the target terminal, it checks the community attribute corresponding to the route, and when the community attribute belongs to the service SID, queries the target service SID corresponding to the route.

[0123] Specifically, the above step S504 includes:

[0124] Step S5041: extract the lowest N bits of the route as the first service ID, and query whether the first service ID exists in the local service registration database of the current edge node.

[0125] In an example, this step is explained in detail.

[0126] Step S5042: when the first service ID does not exist in the local service registration database of the current edge node, write the first service ID into the local service registration database of the current edge node, and set the local service of the current edge node to no.

[0127] Step S5043: When the first service ID exists in the local service registration database of the current edge node, it is determined whether the first service ID is a local service of the current edge node.

[0128] Step S5044, when the first service ID is not a local service of the edge node, the routing service SID carried by the route is added to the detection list of the detection module, and the routing service SID is instantiated until the first service ID is a local service of the edge node.

[0129] Step S5045: when the first service ID is a local service of the edge node, it is determined that the target service SID corresponding to the route is instantiated at the current edge node.

[0130] In one example, when the remote PoP receives a route, it checks the community attribute of the route. If the community attribute belongs to the service SID, a service discovery step is performed, including: Step 1: According to the setting of the initialization step, the lowest N bits are extracted from the received route belonging to the service SID as the service ID.

[0131] Step 2: Query the local service registration database. If the service ID does not exist, request the service ID compiler to obtain the service domain name of the ID and write it into the local service registration database. At the same time, set the local service column to "No". If the local service ID exists, proceed to step 3.

[0132] Step 3: According to the query of the local service registration library entry, if the service ID is a local service, that is, the service has been instantiated on this node, there is no need to instantiate the SRv6 instruction. If the service ID is not a local service, the service SID carried by this route is added to the detection list of the detection module, and step 4 is performed.

[0133] Step 4: The service detection module maintains a list of candidate service SIDs for each service ID. This list is the node service SIDs corresponding to the service ID published by other PoPs. The detection module periodically detects and selects the service SID with the best quality based on parameters such as latency, and writes it into the "remote service SID" of the local service registration database. Table 2 is a table of database entries written into the local service registration database. The database entries are shown in Table 2:

[0134] Table 2

[0135]

[0136] Service domain name Service ID Local service SID Remote service SID Container address Local service: s1.t1.edge.com0x0000f001 2001:db8:3:S:f001 2001:db8:1:S:f001 fa80::1 No. Each time a database entry is updated, the SRv6 orchestrator is triggered to proceed to step five.

[0137] Step 5: Instantiate the SRv6 SID and write the following operations into the FIB table: When the destination address of the message is the local service SID: 2001:db8:3:S:f001 (local service SID). The operations include:

[0138] 1. The Segment Left field is reduced by 1;

[0139] 2. Update the destination address to the service SID of the currently selected remote PoP point;

[0140] 3. Forward the message to the next hop.

[0141] In this method, the lowest bit of SRv6 is used to encode the service ID, ensuring that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge node through the routing table, and then determine the final destination address of the service through the detection mechanism. The SRv6 instruction mechanism is used to ensure that when the edge node accessed by the user does not deploy the access service, it can support forwarding to the next one nearby.

[0142] Step S505: Return the target service SID to the target terminal, so that the target terminal accesses the target service based on the target service SID.

[0143] In an optional implementation, returning the target service SID to the target terminal so that the target terminal accesses the target service based on the target service SID includes:

[0144] Step b1, determining whether the service accessed by the target terminal is deployed at the access point corresponding to the target terminal.

[0145] Step b2: when the service accessed by the target terminal is deployed at the access point corresponding to the target terminal, the local service SID of the access point is returned to the target terminal as the target service SID.

[0146] Step b3: when the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal, it is determined whether the service accessed by the target terminal is instantiated at the current edge node.

[0147] Step b4: when the service accessed by the target terminal is instantiated at the current edge node, the destination address of the target terminal is updated to the address of the current edge node to access the target service.

[0148] Step b5, when the service accessed by the target terminal is not instantiated in the current edge node, the destination address of the target terminal is updated to the address of other edge nodes interconnected with the current edge node until the service accessed by the target terminal is instantiated in the edge node and the target service is accessed.

[0149] In one example, service access is achieved through the following steps: Step 1: The terminal device sets the DNS server address to the access address of the PoP point. When a request for a service domain name is initiated, the DNS query is sent to the access PoP point. The access PoP queries the local service database. If no entry is found, it means that the service has not been deployed in the network, or has been deployed but not synchronized to the node. If an entry is found, the local service SID is used as the ipv6 address and returned to the terminal device.

[0150] Step 2: The terminal device initiates access. If the accessed service is instantiated locally, the destination address is updated to the container address according to the operation steps of the SRv6 instruction, and the local service is accessed.

[0151] Step 3: If the accessed service is not local, according to the operation steps of the SRv6 instruction, the destination address is updated to the service SID of the remote node, and the request is forwarded to other nearby PoP points.

[0152] Step 4: After the remote PoP receives and processes the service request, it returns it directly to the terminal.

[0153] In this way, the user's demand for nearby access can be met. The end user can obtain services by accessing the nearest node with a unified service identifier. The mechanism of automatically discovering the nearest next hop of the service ensures that the service requested by the user can be quickly forwarded to the nearest PoP point when the access point is not deployed, meeting high availability and high real-time performance.

[0154] The dynamic service registration method for the edge cloud environment provided in this embodiment uses the lowest bit of SRv6 to encode the service ID to ensure that no matter which edge node the service is deployed on, the accessed edge node can quickly filter out the matching remote or local edge nodes through the routing table, and then determine the final destination address of the service through the detection mechanism. The mechanism of using SRv6 instructions ensures that when the edge node accessed by the user has not deployed the access service, it can support forwarding to the next one nearby. It can meet the user's demand for nearby access. The terminal user can obtain the service by accessing the nearest node with a unified service identifier. The mechanism of automatically discovering the nearest next hop of the service ensures that the service requested by the user can still be quickly forwarded to the nearest PoP point when the access point is not deployed, meeting high availability and high real-time performance.

[0155] In this embodiment, a dynamic service registration device for an edge cloud environment is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated here. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0156] This embodiment provides a dynamic service registration device for an edge cloud environment, such as Figure 6 As shown, including:

[0157] The service initialization module 601 is used to initialize each edge node, establish routing between edge nodes, and divide the service ID range for each edge node. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.

[0158] The service instantiation module 602 is used to assign a corresponding service ID to each edge node. Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.

[0159] The service registration module 603 is used to generate a service SID corresponding to the service ID based on the service ID, and publish the service SID to the wide area network through the BGP protocol. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.

[0160] The service discovery module 604 is used to check the community attribute corresponding to the route when the edge node receives the route corresponding to the target service of the target terminal, and when the community attribute belongs to the service SID, query the target service SID corresponding to the route. Figure 1 Step S104 of the illustrated embodiment will not be described in detail here.

[0161] The service access module 605 is used to return the target service SID to the target terminal, so that the target terminal can access the target service based on the target service SID. Figure 1 Step S105 of the illustrated embodiment will not be described in detail here.

[0162] In some optional implementations, the service initialization module 601 includes:

[0163] The network segment allocation unit is used to enable the IPV6 protocol stack and SRv6 function for each edge node and allocate a corresponding IPV6 network segment to each edge node.

[0164] The prefix publishing unit is used to publish the IPv6 prefix allocated by each edge node to the interconnected edge nodes through the BGP protocol.

[0165] The service partitioning unit is used to plan a service SID range for each edge node, and the service SID range is used for service registration.

[0166] In some optional implementations, the service instantiation module 602 includes:

[0167] The service identifier acquisition unit is used to acquire the service identifier corresponding to each edge node, where the service identifier is used to represent the service identifier of the service to which the edge node belongs.

[0168] The service ID request unit is used to request the wide area network to allocate a globally unique service ID corresponding to each edge node.

[0169] The service ID sending unit is used to send the service ID allocated by the wide area network to the SRv6 instruction scheduler of the edge node.

[0170] In some optional implementations, the service registration module 603 includes:

[0171] The service instruction SID generation unit is used to generate the SRv6 service instruction SID of the edge node after the SRv6 instruction orchestrator of the edge node receives the service ID.

[0172] The service instruction SID writing unit is used to write the SRv6 service instruction SID into the local service registration database of the edge node by using the SRv6 instruction orchestrator.

[0173] The service instruction SID instantiation unit is used to instantiate the SRv6 service instruction SID, and publish the SRv6 service instruction SID to other edge nodes in the wide area network in the form of an IPV6 address in combination with a community attribute value corresponding to the edge node through the BGP protocol.

[0174] In some optional implementations, the service discovery module 604 includes:

[0175] The service ID extraction unit is used to extract the lowest N bits of the route as the first service ID, and query whether the first service ID exists in the local service registration database of the current edge node.

[0176] The first service ID writing unit is used to write the first service ID into the local service registration database of the current edge node and set the local service of the current edge node to no when the first service ID does not exist in the local service registration database of the current edge node.

[0177] The local service determination unit is used to determine whether the first service ID is a local service of the current edge node when the first service ID exists in the local service registration database of the current edge node.

[0178] The service detection unit is used to add the routing service SID carried by the route to the detection list of the detection module when the first service ID is not a local service of the edge node, and instantiate the routing service SID until the first service ID is a local service of the edge node.

[0179] The service SID instantiation unit is used to determine that a target service SID corresponding to the route is instantiated at the current edge node when the first service ID is a local service of the edge node.

[0180] In some optional implementations, the service access module 605 includes:

[0181] The access point determination unit is used to determine whether the service accessed by the target terminal is deployed at the access point corresponding to the target terminal.

[0182] The first target service determination unit is configured to return a local service SID of the access point as a target service SID to the target terminal when the service accessed by the target terminal is deployed at the access point corresponding to the target terminal.

[0183] The service instantiation determination unit is used to determine whether the service accessed by the target terminal is instantiated at the current edge node when the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal.

[0184] The first address updating unit is used to update the destination address of the target terminal to the address of the current edge node to access the target service when the service accessed by the target terminal is instantiated at the current edge node.

[0185] The second address updating unit is used to update the destination address of the target terminal to the address of other edge nodes interconnected with the current edge node when the service accessed by the target terminal is not instantiated in the current edge node, until the service accessed by the target terminal is instantiated in the edge node and the target service is accessed.

[0186] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0187] The edge cloud environment dynamic service registration device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0188] The embodiment of the present invention also provides a computer device having the above Figure 6 The edge cloud environment dynamic service registration device is shown.

[0189] See also Figure 7 , Figure 7 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 7 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.

[0190] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0191] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0192] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0193] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0194] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 7 The example of connecting through bus is taken in the following.

[0195] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0196] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0197] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0198] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for dynamic service registration in an edge cloud environment, characterized in that: The method comprises: Initialize each edge node, establish routing between the edge nodes, and divide the service ID range for each edge node; Allocating a corresponding service ID to each of the edge nodes; Based on the service ID, generate a service SID corresponding to the service ID, and publish the service SID to the wide area network through the BGP protocol; When the edge node receives a route corresponding to a target service of a target terminal, it checks a community attribute corresponding to the route, and when the community attribute belongs to the service SID, it queries a target service SID corresponding to the route; The target service SID is returned to the target terminal, so that the target terminal accesses the target service based on the target service SID.

2. The method according to claim 1, characterized in that The initializing of each edge node includes: Enabling the IPV6 protocol stack and SRv6 function for each edge node, and allocating a corresponding IPV6 network segment for each edge node; Publishing the IPv6 prefix allocated by each edge node to the interconnected edge nodes through the BGP protocol; A service SID range is planned for each edge node, and the service SID range is used for service registration.

3. The method according to claim 2, characterized in that The assigning a corresponding service ID to each edge node includes: Obtaining a service identifier corresponding to each edge node, where the service identifier is used to represent a service identifier of a service to which the edge node belongs; Requesting the wide area network to allocate a globally unique service ID corresponding to each edge node; The service ID assigned by the wide area network is sent to the SRv6 instruction scheduler of the edge node.

4. The method according to claim 3, characterized in that The generating, based on the service ID, a service SID corresponding to the service ID, and publishing the service SID to a wide area network through a BGP protocol, includes: After the SRv6 instruction scheduler of the edge node receives the service ID, generating an SRv6 service instruction SID of the edge node; Using the SRv6 instruction orchestrator to write the SRv6 service instruction SID into the local service registration database of the edge node; The SRv6 service instruction SID is instantiated, and the SRv6 service instruction SID is published to other edge nodes in the wide area network in the form of an IPV6 address in combination with a community attribute value corresponding to the edge node through the BGP protocol.

5. The method according to claim 4, characterized in that The querying of the target service SID corresponding to the route includes: Extracting the lowest N bits of the route as a first service ID, and querying whether the first service ID exists in a local service registration database of the current edge node; When the first service ID does not exist in the local service registration database of the current edge node, write the first service ID into the local service registration database of the current edge node, and set the local service of the current edge node to no; When the first service ID exists in the local service registration database of the current edge node, determining whether the first service ID is a local service of the current edge node; When the first service ID is not a local service of the edge node, adding the routing service SID carried by the route to the detection list of the detection module, and instantiating the routing service SID until the first service ID is a local service of the edge node; When the first service ID is a local service of the edge node, it is determined that the target service SID corresponding to the route is instantiated at the current edge node.

6. The method according to claim 5, characterized in that The returning the target service SID to the target terminal so that the target terminal accesses the target service based on the target service SID includes: Determining whether the service accessed by the target terminal is deployed at the access point corresponding to the target terminal; When the service accessed by the target terminal is deployed at the access point corresponding to the target terminal, returning the local service SID of the access point as the target service SID to the target terminal; When the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal, determining whether the service accessed by the target terminal is instantiated at the current edge node; When the service accessed by the target terminal is instantiated at the current edge node, updating the destination address of the target terminal to the address of the current edge node to access the target service; When the service accessed by the target terminal is not instantiated in the current edge node, the destination address of the target terminal is updated to the address of other edge nodes interconnected with the current edge node until the service accessed by the target terminal is instantiated in the edge node and the target service is accessed.

7. A dynamic service registration device for an edge cloud environment, characterized in that: The device comprises: A service initialization module, used to initialize each edge node, establish routing between the edge nodes, and divide the service ID range for each edge node; A service instantiation module, used to assign a corresponding service ID to each edge node; A service registration module, used to generate a service SID corresponding to the service ID based on the service ID, and publish the service SID to the wide area network through the BGP protocol; A service discovery module, configured to check a community attribute corresponding to a route corresponding to a target service of a target terminal when the edge node receives the route corresponding to the route, and query a target service SID corresponding to the route when the community attribute belongs to the service SID; The service access module is used to return the target service SID to the target terminal, so that the target terminal accesses the target service based on the target service SID.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the edge cloud environment dynamic service registration method according to any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the edge cloud environment dynamic service registration method according to any one of claims 1 to 6.

10. A computer program product, characterized in that It includes computer instructions, and the computer instructions are used to enable a computer to execute the edge cloud environment dynamic service registration method described in any one of claims 1 to 6.

Images