Methods, devices, equipment and storage media for dynamic service registration in edge cloud environments

Abstract

This invention relates to the field of edge computing technology and discloses a method, apparatus, device, and storage medium for dynamic service registration in an edge cloud environment. The method includes: initializing each edge node; assigning a corresponding service ID to each edge node; generating a service SID corresponding to the service ID; when an edge node receives a route corresponding to a target service from a target terminal, checking the community attribute of the route, and if the community attribute belongs to a service SID, querying the target service SID corresponding to the route; and returning the target service SID to the target terminal. Services deployed on any edge computing node can be published to other edge nodes across the entire network. End users and devices can access services using a unified identifier through the nearest accessible edge node. Edge nodes provide the ability to forward requests from the nearest node, eliminating the need for terminals to access remote nodes across domains.

Description

Technical Field

[0001] This invention relates to the field of edge computing technology, specifically to a method, apparatus, device, and storage medium for dynamic service registration in edge cloud environments. Background Technology

[0002] In recent years, with the popularization of the Internet of Things (IoT), the development of 5G, and the rapid advancement of artificial intelligence, an increasing number of smart terminal devices have been deployed and connected to the network. The speed and volume of data collected by these devices are rapidly increasing, and the complexity of data processing is also constantly growing. Against this backdrop, more and more data needs to be analyzed and responded to in real-time or near real-time at edge nodes where terminal devices are located. Edge cloud is increasingly being adopted to meet this demand. As a new type of cloud computing model, edge cloud emphasizes deploying computing resources to the edge of the physical world to meet the requirements of low latency, high bandwidth, and real-time performance. Traditional data center cloud computing models focus on hosting applications and data in central data centers. However, for some applications, especially those requiring low latency, such as smart cities, autonomous vehicles, and telemedicine, centralized cloud computing models may suffer from real-time and performance issues. Therefore, edge cloud can address these problems by moving computing resources closer to users and devices.

[0003] In traditional data center cloud computing, a service registry is typically deployed. Microservice instances register their addresses with this registry. When accessing services within the data center, the instance address is obtained by querying the registry. When accessing services outside the data center, components like API gateways are typically used to expose internal services to external users via domain names. For example, Kubernetes' Ingress component. In edge cloud environments, the number of edge computing nodes is large and geographically dispersed. Using a unified service registry would require maintaining a large number of nodes, impacting performance. Furthermore, a unified registry cannot provide end-users and devices with the ability to find the nearest available service. Because different edge nodes have different computing resources, the service lists deployed on those nodes also differ. The node a device tries to access might not have the requested service deployed there. Summary of the Invention

[0004] In view of this, the present invention provides a method, apparatus, device and storage medium for dynamic service registration in an edge cloud environment, in order to solve the problem that edge computing nodes in existing edge cloud technologies cannot support end users to call the services they need from the nearest location.

[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 routes between edge nodes, and assign a service ID range to each edge node;

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

[0008] Based on the service ID, generate the corresponding service SID, and publish the service SID to the wide area network via 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 of the route. If 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 can access the target service based on the target service SID.

[0011] Unlike data centers that use a unified service registry, this invention automatically publishes services to the entire network and provides network-wide reachable service routes when deploying services at edge nodes. Compared to existing service registration mechanisms based on public domain names, it also provides the ability to access services from the nearest available edge node. When the accessed node does not deploy the desired service, it provides the ability to forward traffic to the nearest edge node where the service is deployed. By using SRv6-encoded service identifiers and publishing service SID routes via BGP, the reachability of the service is guaranteed at any edge node. By marking SID routes with community attributes, remote edge nodes can quickly filter routes. Using the least significant bit of SRv6 to encode the service ID, it ensures that regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table, and then determine the final destination address of the service through a probing mechanism. The use of SRv6 instructions ensures that when the edge node accessed by the user does not deploy the service, it can support forwarding to the next available route. Services deployed on any edge computing node can be published to other edge nodes across the entire network. End users and devices can access services using a unified identifier through the nearest edge node. Edge nodes provide the ability to forward requests locally, eliminating the need for terminals to access remote nodes across domains.

[0012] In one alternative implementation, each edge node is initialized, including:

[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] The IPv6 prefix assigned to each edge node is published to the interconnected edge nodes via 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 approach, each edge node is initialized by setting its SRv6 command locator to the IPv6 address prefix assigned to that edge node. Since the edge node's address prefix is ​​published to the public network via BGP, the SRv6 commands sent to this edge node can be correctly forwarded to it by other nodes in the network.

[0017] In one optional implementation, a corresponding service ID is assigned to each edge node, including:

[0018] Obtain the service identifier corresponding to each edge node. The service identifier is used to represent the service to which the edge node belongs.

[0019] Request the wide area network to assign a globally unique service ID to each edge node;

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

[0021] In this approach, by adding the acquisition of service identifiers to 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 then sends the assigned service ID to the SRv6 instruction orchestrator, thereby realizing service instantiation and facilitating the triggering of the subsequent service registration process.

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

[0023] After receiving the service ID, the SRv6 instruction orchestrator at the edge node generates the SRv6 service instruction SID for the edge node.

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

[0025] The SRv6 service instruction SID is instantiated and, via the BGP protocol, the SRv6 service instruction SID is published to other edge nodes in the wide area network in the form of an IPv6 address, combined with the community attribute value corresponding to the edge node.

[0026] In this approach, service registration is achieved by generating an SRv6 service instruction SID for each edge node, writing the SID into the edge node's local service registration database, and instantiating the SID. Using the BGP protocol, this service SID is published to other nodes as a 128-bit IPv6 address with a community attribute value. Based on the community attribute value, other edge nodes within the management domain can quickly filter out address routes for service SRv6 instruction SIDs belonging to their respective management domains, which is used in the service discovery process.

[0027] In one 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] If 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, determine 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 an edge node, the routing service SID carried by the route is added to the probe list of the probe module, and the routing service SID is instantiated until the first service ID is a local service of an edge node.

[0032] When the first service ID is a local service of the edge node, determine the target service SID corresponding to the route and instantiate it on the current edge node.

[0033] In this approach, the least significant bit of SRv6 is used to encode the service ID, ensuring that regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table. A probing mechanism is then used to determine the final destination address of the service. The use of SRv6 directives ensures that if the edge node accessed by the user does not have the service deployed, the service can be forwarded to the nearest available node.

[0034] In one optional implementation, the target service SID is returned to the target terminal so that the target terminal can access the target service based on the target service SID, including:

[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, determine whether the service accessed by the target terminal is instantiated on the current edge node;

[0038] When the service accessed by the target terminal is instantiated on the current edge node, the destination address of the target terminal is updated to the address of the current edge node, and the target service is accessed.

[0039] If the service accessed by the target terminal is not instantiated on the current edge node, update the destination address of the target terminal to the address of another edge node interconnected with the current edge node, until the service accessed by the target terminal is instantiated on the edge node and the target service is accessed.

[0040] This approach satisfies users' need for proximity-based access. End users can obtain services by accessing the nearest node using a unified service identifier. The mechanism of automatically discovering the nearest next hop ensures that user-requested services can still be quickly forwarded to the nearest PoP point even when no access point is deployed, thus meeting high availability and high real-time requirements.

[0041] Secondly, the present invention provides a dynamic service registration device for an edge cloud environment, the device comprising:

[0042] The service initialization module is used to initialize each edge node, establish routes between edge nodes, and assign a service ID range to 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 a service ID based on the service ID, and publish the service SID to the wide area network via the BGP protocol;

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

[0046] The service access module 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.

[0047] Thirdly, the present invention provides a computer device, including: 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 computer instructions to perform the edge cloud environment dynamic service registration method described in the first aspect or any corresponding embodiment thereof.

[0048] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the edge cloud environment dynamic service registration method described in the first aspect or any corresponding embodiment thereof.

[0049] Fifthly, the present invention provides a computer program product, including computer instructions for causing a computer to execute the edge cloud environment dynamic service registration method described in the first aspect or any corresponding embodiment thereof. Attached Figure Description

[0050] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0051] Figure 1 This is a flowchart illustrating the dynamic service registration method for edge cloud environments according to an embodiment of the present invention.

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

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

[0054] Figure 4 This is a flowchart illustrating another dynamic service registration method for edge cloud environments according to an embodiment of the present invention.

[0055] Figure 5 This is a flowchart illustrating another dynamic service registration method for edge cloud environments according to an embodiment of the present invention.

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

[0057] Figure 7 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0059] In traditional data center cloud computing, a service registry is typically deployed. Microservice instances register their addresses with this registry. When accessing services within the data center, the instance address is obtained by querying the registry. When accessing services outside the data center, components like API gateways are typically used to expose internal services to external users via domain names. For example, Kubernetes' Ingress component. In edge cloud environments, the number of edge computing nodes is large and geographically dispersed. Using a unified service registry would require maintaining a large number of nodes, impacting performance. Furthermore, a unified registry cannot provide end-users and devices with the ability to find the nearest available service. Because different edge nodes have different computing resources, the service lists deployed on those nodes also differ. The node a device tries to access might not have the requested service deployed there.

[0060] To address the aforementioned issues, this invention provides a method for dynamic service registration in an edge cloud environment, used in a computer device. It should be noted that the executing entity can be an edge cloud environment dynamic service registration device, which can be implemented as part or all of the computer device through software, hardware, or a combination of both. The computer device can be a terminal, client, or server. The server can be a single server or a server cluster composed of multiple servers. In this embodiment, the terminal can be a smartphone, personal computer, tablet computer, or other smart hardware device. The following method embodiments all use a computer device as the executing entity for illustration.

[0061] The computer equipment in this embodiment is suitable for edge cloud environments where there are many nodes distributed across different geographical locations, providing end users with the ability to access services based on proximity. This invention provides a dynamic service registration method for edge cloud environments, which differs from the unified service registry used in data centers. When services are deployed at edge nodes, services are automatically published to the entire network, and network-wide reachable service routes are provided. Compared to existing service registration mechanisms based on public domain names, it also provides the ability to access services based on proximity, ensuring that terminals always access services through the nearest accessible edge node; when the accessed node does not deploy the desired service, it provides the ability to forward traffic to the nearest edge node where the service is deployed. By using SRv6-encoded service identifiers and publishing service SID routes via BGP, service reachability at any edge node is guaranteed. By marking SID routes with community attributes, remote edge nodes can quickly filter routes. Utilizing the least significant bit of SRv6 to encode the service ID ensures that regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table, and then determine the final destination address of the service through a probing mechanism. The SRv6 instruction mechanism ensures that when a user accesses an edge node that has not deployed the access service, the request can be forwarded to the nearest available node. Services deployed on any edge computing node can be published to other edge nodes across the network. End users and devices can access services through the nearest accessible edge node using a unified identifier. Edge nodes provide the ability to forward requests based on proximity, eliminating the need for terminals to access remote nodes across domains.

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

[0063] This embodiment provides a method for dynamic service registration in an edge cloud environment, which can be used with the aforementioned computer equipment. Figure 1 This is a flowchart of a dynamic service registration method for edge cloud environments according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0064] Step S101: Initialize each edge node, establish routes between edge nodes, and assign a service ID range to each edge node.

[0065] In one example, the Locator for SRv6 commands at each edge PoP is configured with the IPv6 address prefix assigned to this node. Since this node's address prefix is ​​advertised to the public network via BGP, SRv6 commands sent to this node can be correctly forwarded to it by other nodes in the network. A PoP (Point-of-Presence) is an entry point in an enterprise network, providing internet access, wide area network connectivity, and telephone services.

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

[0067] In one example, in an edge cloud environment, services can be deployed on edge nodes in multiple ways. A typical deployment method is deploying service containers. Based on the existing functionality of the service orchestrator, a new feature is added to assign a corresponding service ID to each edge node for service registration.

[0068] Step S103: Based on the service ID, generate the service SID corresponding to the service ID, and publish the service SID to the wide area network via the BGP protocol.

[0069] In one example, after receiving the assigned service ID, the SRv6 instruction orchestrator generates the local node's SRv6 service instruction SID. The instruction orchestrator writes this instruction SID to the local service registry database. It then 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. If the community attribute belongs to the service SID, it queries the target service SID corresponding to the route.

[0071] In one example, when a remote PoP receives a route, it checks the route's community attribute. If the community attribute belongs to a service SID, then a service discovery step is performed.

[0072] Step S105: 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.

[0073] In one example, the terminal device sets the DNS server address as the access address of the PoP point. When the terminal device initiates a request, if the requested service is instantiated locally, the destination address is updated to the container address according to the SRv6 instructions, allowing access to the local service. If the requested service is not local, the destination address is updated to the service SID of the remote node according to the SRv6 instructions, and the request is forwarded to another nearby PoP point. After receiving and processing the service request, the remote PoP point directly returns the result to the terminal.

[0074] In one implementation scenario, Figure 2 This is a schematic diagram of the overall service registration architecture according to an embodiment of the present invention, such as... Figure 2 As shown, each user interacts with the corresponding access point (PoP) for data exchange; the access point PoP requests a service ID from the service ID orchestrator, which then distributes the service ID of the access point PoP to the corresponding access point PoP; the access point PoP and the operator's edge routing node (PE) in the wide area network / Internet use BGP protocol for internal routing to forward service requests to the nearest PoP; after receiving and processing the service request, the remote PoP directly returns it to the terminal.

[0075] Figure 3 This is a schematic diagram of a system architecture for an edge PoP point according to an embodiment of the present invention, as shown below. Figure 3 As shown, each PoP point uses a 64-bit IPv6 address prefix. The function field of the SRv6 directive is configured as 0x00ff and is 32 bits long. The Arguments field is also 32 bits long. The service identifier uses the service domain name. PoP points can be deployed in different autonomous systems and advertise routes via the BGP protocol. After receiving the service ID from the service ID orchestrator, each edge PoP instantiates the service through the service instance orchestrator and sends the service ID to the SRv6 command orchestrator. Upon receiving the assigned service ID, the SRv6 command orchestrator generates its own SRv6 service command SID, instantiates the SRv6 SID, and writes it to the local service registration database. It then uses SRv6 encoding to identify the service identifier and publishes the service SID route via BGP. Using the least significant bit of the SRv6 encoding for the service ID, connected PoPs can quickly filter out matching remote or local nodes through the routing table and determine the final destination address of the service through a probing mechanism. The SRv6 SID is then instantiated and written to the FIB table. Finally, via the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPv6 address with a community attribute value set.

[0076] The dynamic service registration method for edge cloud environments provided in this embodiment differs from the unified service registry used in data centers. When services are deployed on edge nodes, they are automatically published to the entire network, and network-wide reachable service routes are provided. Compared to existing service registration mechanisms based on public domain names, this method also provides the ability to access services from the nearest available edge node. When the accessed node does not deploy the desired service, it provides the ability to forward traffic to the nearest edge node where the service is deployed. By using SRv6-encoded service identifiers and publishing service SID routes via BGP, service reachability on any edge node is guaranteed. By marking SID routes with community attributes, remote edge nodes can quickly filter routes. Using the least significant bit of SRv6 to encode the service ID, regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table, and then determine the final destination address of the service through a probing mechanism. The use of SRv6 instructions ensures that when the edge node accessed by the user does not deploy the service, it can support forwarding to the next available route. Services deployed on any edge computing node can be published to other edge nodes across the entire network. End users and devices can access services using a unified identifier through the nearest edge node. Edge nodes provide the ability to forward requests locally, eliminating the need for terminals to access remote nodes across domains.

[0077] This embodiment provides a method for dynamic service registration in an edge cloud environment, which can be used with the aforementioned computer equipment. Figure 4 This is a flowchart of another dynamic service registration method for edge cloud environments according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following steps:

[0078] Step S401: Initialize each edge node, establish routes between edge nodes, and assign a service ID range to each edge node.

[0079] In one alternative implementation, each edge node is initialized, including:

[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: Using the BGP protocol, publish the IPv6 prefix assigned to each edge node to the interconnected edge nodes.

[0082] Step a3: Plan the service SID range for each edge node. The service SID range is used for service registration.

[0083] In one example, the following initialization operation is performed when enabling edge PoP points:

[0084] 1) Enable the IPv6 protocol stack and SRv6 functionality for each edge PoP and allocate an IPv6 network segment. Typically, large cloud computing providers can obtain an IPv6 address pool from the carrier for each deployment node's data center. Based on the size of the allocated address pool, an available IPv6 address prefix can be allocated to the edge PoP.

[0085] 2) Points of Presence (PoPs) advertise their assigned IPv6 prefixes to interconnected PE nodes via the BGP protocol. In typical edge cloud environments, PoPs in different regions reside in different autonomous systems. Using BGP to advertise routes ensures the reachability of each PoP.

[0086] 3) Plan the SID range used for service registration. In the SRv6 protocol, the IPv6 address is typically used as an instruction, divided into three parts according to network byte order from high to low: Locator, Function, and Arguments. In this invention, the Locator of the SRv6 instruction for 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 via BGP, the SRv6 instructions sent to this node can be correctly forwarded to this node by other nodes in the network. The same Function segment is set on all edge PoP nodes to identify the dynamic service registration function. The least significant N bits are used to map the Service ID.

[0087] In this approach, each edge node is initialized by setting its SRv6 command locator to the IPv6 address prefix assigned to that edge node. Since the edge node's address prefix is ​​published to the public network via BGP, the SRv6 commands sent to this edge node can be correctly forwarded to it by other nodes in the network.

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

[0089] Specifically, step S402 includes:

[0090] Step S4021: Obtain the service identifier corresponding to each edge node.

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

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

[0093] Step S4023: Send the service ID assigned by the wide area network to the SRv6 instruction orchestrator of the edge node.

[0094] In one example, in an edge cloud environment, services can be deployed in various ways on edge nodes. A typical deployment method is deploying service containers. In this invention, based on the original functionality of the service orchestrator, the following process is added to implement service registration:

[0095] Step 1: Obtain the service identifier. The service container image sets environment parameters, including the service identifier of the service to which the container belongs. In this invention, the service identifier is identified by the service domain name, for example, service-a.tenant-A.edge.com. Here, service-a is the service name, and tenant-A is the tenant name. This invention does not impose restrictions on the service domain name identifier.

[0096] Step 2: The service instance orchestrator requests a globally unique service ID from the central service ID orchestrator. The service ID orchestrator queries the database to check if the service domain name has been registered by another instance. If it has, it returns the previously assigned service ID. If it has not been registered, it assigns an unused service ID.

[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 approach, by adding the acquisition of service identifiers to 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 then sends the assigned service ID to the SRv6 instruction orchestrator, thereby realizing service instantiation and facilitating the triggering of the subsequent service registration process.

[0099] Step S403: Based on the service ID, generate the service SID corresponding to the service ID, and publish the service SID to the wide area network via the BGP protocol.

[0100] Specifically, step S403 includes:

[0101] Step S4031: After the SRv6 instruction orchestrator of the edge node receives the service ID, it generates the 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, combined 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 (I) After receiving the assigned service ID, the SRv6 instruction orchestrator generates the SRv6 service instruction SID for this node. According to the initialization process, the Locator part of this SRv6 service instruction is the IPv6 address prefix of this node. The Function part is unified to a single 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. If the service registration Function is defined as S and the service ID is assigned as A, then the SID of the SRv6 service instruction generated for this service is 2001:db8:1:S:A. The length of the service ID field is configured reasonably according to the scale of the number of services. A 32-bit service ID length can provide up to 4,294,967,296 service IDs for registration.

[0105] Step (II) The instruction orchestrator writes the instruction SID into the local service registry database. Table 1 is the entry table of the local service registry database, and the entry definitions of the local service registry database are shown in Table 1:

[0106] Table 1

[0107]

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

[0109] Step (3) Instantiate the SRv6 SID and write the following operations into the FIB table: When the destination address of the packet is the service SID: 2001:db8:1:S:f001 (local service SID), the operations include:

[0110] 1. Decrease the Segment Left field by 1;

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

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

[0113] Step (iv) Publish the service SID. Using the BGP protocol, publish the service SID as a 128-bit IPv6 address with the community attribute value set to other nodes. The purpose of setting the community attribute value is to allow other PoP nodes within the management domain to quickly filter out address routes for service SRv6 command SIDs belonging to this management domain, which are then used in the service discovery process.

[0114] In this approach, service registration is achieved by generating an SRv6 service instruction SID for each edge node, writing the SID into the edge node's local service registration database, and instantiating the SID. Using the BGP protocol, this service SID is published to other nodes as a 128-bit IPv6 address with a community attribute value. Based on the community attribute value, other edge nodes within the management domain can quickly filter out address routes for service SRv6 instruction SIDs belonging to their respective management domains, which is used in the service discovery process.

[0115] Step S404: When the edge node receives the route corresponding to the target service of the target terminal, it checks the community attribute of the route. If the community attribute belongs to the service SID, it queries the target service SID corresponding to the route. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again 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. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0117] The dynamic service registration method for edge cloud environments provided in this embodiment initializes each edge node and sets the SRv6 command locator of each edge node to the IPv6 address prefix assigned to that edge node. Since the address prefix of the edge node is published to the public network via BGP, the SRv6 commands sent to this edge node can be correctly forwarded to it by other nodes in the network. By adding the acquisition of service identifiers to the existing functions of the service orchestrator, the service instance orchestrator requests a globally unique service ID from the central service ID orchestrator. The server instance orchestrator sends the assigned service ID to the SRv6 command orchestrator, realizing service instantiation and facilitating the triggering of subsequent service registration processes. By generating an SRv6 service command SID for the edge node, writing the service command SID to the edge node's local service registration database, and instantiating the service command SID, service registration is achieved. Through the BGP protocol, the service SID is published to other nodes in the form of a 128-bit IPv6 address with a community attribute value set. By using community attribute values, other edge nodes within the management domain can be quickly filtered to identify address routes for service SRv6 instruction SIDs belonging to this management domain, which are then used for service discovery.

[0118] This embodiment provides a method for dynamic service registration in an edge cloud environment, which can be used with the aforementioned computer equipment. Figure 5 This is a flowchart of another dynamic service registration method for edge cloud environments according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes the following steps:

[0119] Step S501: Initialize each edge node, establish routes between edge nodes, and assign a service ID range to each edge node. For details, please refer to [link to relevant documentation]. Figure 4 Step S401 of the illustrated embodiment will not be described again here.

[0120] Step S502: Assign a corresponding service ID to each edge node. For details, please refer to [link to relevant documentation]. Figure 4 Step S402 of the illustrated embodiment will not be described again here.

[0121] Step S503: Based on the service ID, generate the service SID corresponding to the service ID, and publish the service SID to the wide area network via the BGP protocol. For details, please refer to [link to relevant documentation]. Figure 4 Step S403 of the illustrated embodiment will not be described again 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. If the community attribute belongs to the service SID, it queries the target service SID corresponding to the route.

[0123] Specifically, 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] The steps are explained in detail in one example.

[0126] Step S5042: If 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, determine 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 an edge node, add the routing service SID carried by the route to the probe list of the probe module, and instantiate the routing service SID until the first service ID is a local service of an edge node.

[0129] Step S5045: When the first service ID is a local service of the edge node, determine the target service SID corresponding to the route to be instantiated on the current edge node.

[0130] In one example, when a remote PoP receives a route, it checks the route's community attribute. If the community attribute belongs to a service SID, a service discovery step is performed, including: Step 1: Based on the settings in the initialization step, extract the lowest N bits from the received routes 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 domain name of the ID from the service ID orchestrator and write it to the local service registration database. Simultaneously, set the local service column to "No". If the local service ID exists, proceed to Step 3.

[0132] Step 3: Based on the retrieved local service registry entry, if the service ID is a local service (meaning the service has already been instantiated on this node), then there is no need to instantiate the SRv6 command again. If the service ID is not a local service, then add the service SID carried by this route to the probe module's probe list and proceed to Step 4.

[0133] Step 4: The service detection module maintains a list of candidate service SIDs for each service ID. This list consists of node service SIDs published by other PoPs for that service ID. The detection module periodically probes and selects the highest quality service SID based on parameters such as latency, writing it into the "Remote Service SID" in the local service registration database. Table 2 shows the database entries written to the local service registration database.

[0134] Table 2

[0135]

[0136] Service Domain Name Service ID Local Service SID Remote Service SID Container Address Local Service: s1.t1.edge.com 0x0000f001 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 perform step five.

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

[0138] 1. Decrease the Segment Left field 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 approach, the least significant bit of SRv6 is used to encode the service ID, ensuring that regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table. A probing mechanism is then used to determine the final destination address of the service. The use of SRv6 directives ensures that if the edge node accessed by the user does not have the service deployed, the service can be forwarded to the nearest available node.

[0142] Step S505: 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.

[0143] In one optional implementation, the target service SID is returned to the target terminal so that the target terminal can access the target service based on the target service SID, including:

[0144] Step b1: Determine 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: If the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal, determine whether the service accessed by the target terminal is instantiated on the current edge node.

[0147] Step b4: When the service accessed by the target terminal is instantiated on the current edge node, update the destination address of the target terminal to the address of the current edge node and access the target service.

[0148] Step b5: If the service accessed by the target terminal is not instantiated on the current edge node, update the destination address of the target terminal to the address of another edge node interconnected with the current edge node, until the service accessed by the target terminal is instantiated on 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 indicates that the service has not yet been deployed in the network, or has been deployed but has not yet been synchronized to this node. If an entry is found, the local service SID is returned to the terminal device as the IPv6 address.

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

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

[0152] Step 4: After receiving and processing the service request, the remote PoP point returns the result directly to the terminal.

[0153] This approach satisfies users' need for proximity-based access. End users can obtain services by accessing the nearest node using a unified service identifier. The mechanism of automatically discovering the nearest next hop ensures that user-requested services can still be quickly forwarded to the nearest PoP point even when no access point is deployed, thus meeting high availability and high real-time requirements.

[0154] The dynamic service registration method for edge cloud environments provided in this embodiment utilizes the least significant bit of SRv6 to encode the service ID. This ensures that regardless of which edge node the service is deployed on, the accessing edge node can quickly filter out matching remote or local edge nodes through its routing table, and then determine the final destination address of the service through a probing mechanism. The use of SRv6 instructions ensures that if the edge node accessed by the user does not have the service deployed, it can support forwarding to the nearest next hop. This meets the user's need for proximity access; end users can obtain the service by accessing the nearest node using a unified service identifier. The automatic discovery mechanism for the nearest next hop ensures that even if the access point does not have the service deployed, the user's requested service can still be quickly forwarded to the nearest PoP point, satisfying high availability and high real-time requirements.

[0155] This embodiment also provides a dynamic service registration device for an edge cloud environment. This device is used to implement the above embodiments and preferred embodiments, and details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

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

[0157] Service initialization module 601 is used to initialize each edge node, establish routes between edge nodes, and assign a service ID range to each edge node. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0158] Service instantiation module 602 is used to assign a corresponding service ID to each edge node. For details, please refer to [link to relevant documentation]. Figure 1 Step S102 of the illustrated embodiment will not be described again here.

[0159] Service registration module 603 is used to generate a service SID corresponding to a service ID based on the service ID, and publish the service SID to the wide area network via the BGP protocol. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0160] Service discovery module 604 is used to check the community attribute of a route when an edge node receives a route corresponding to a target service from a target terminal. If the community attribute belongs to a service SID, it queries the target service SID corresponding to the route. For details, please refer to [link to details]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0161] 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. For details, please refer to [link to relevant documentation]. Figure 1 Step S105 of the illustrated embodiment will not be described again here.

[0162] In some alternative 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 to allocate a corresponding IPv6 network segment for each edge node.

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

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

[0166] In some alternative 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. The service identifier is used to represent the service to which the edge node belongs.

[0168] The Service ID Request Unit is used to request the WAN to assign a globally unique Service ID to each edge node.

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

[0170] In some alternative 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 using the SRv6 instruction orchestrator.

[0173] The Service Command SID Instantiation Unit is used to instantiate the SRv6 Service Command SID and, through the BGP protocol, publish the SRv6 Service Command SID in the form of an IPv6 address, combined with the community attribute value corresponding to the edge node, to other edge nodes in the wide area network.

[0174] In some alternative 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 when the first service ID does not exist in the local service registration database of the current edge node, and to set the local service of the current edge node to no.

[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 to 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 the instantiation of the target Service SID corresponding to the route on the current edge node when the first Service ID is a local service of the edge node.

[0180] In some alternative 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 on the access point corresponding to the target terminal.

[0182] The first target service determination unit is used to return 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 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 on the current edge node when the service accessed by the target terminal is not deployed on the access point corresponding to the target terminal.

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

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

[0186] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

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

[0188] This invention also provides a computer device having the above-described features. Figure 6 The shown is a dynamic service registration device for edge cloud environments.

[0189] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 7 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 7 Take a processor 10 as an example.

[0190] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0191] The memory 20 stores instructions executable by at least one processor 10 to cause the at least one processor 10 to perform the method shown in the above embodiments.

[0192] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0193] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or 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, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

[0195] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the computer device, such as a touchscreen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touchscreen.

[0196] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0197] A portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0198] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall 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 includes: Initialize each edge node, establish routes between the edge nodes, and assign a service ID range to each edge node; Assign a corresponding service ID to each of the aforementioned edge nodes; 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 via the BGP protocol; 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. If the community attribute belongs to the service SID, it queries the target service SID corresponding to the route. The target service SID is returned to the target terminal so that the target terminal can access the target service based on the target service SID.

2. The method according to claim 1, characterized in that, The initialization of each edge node includes: Enable the IPv6 protocol stack and SRv6 function for each edge node, and allocate a corresponding IPv6 network segment for each edge node; Using the BGP protocol, each edge node publishes its assigned IPv6 prefix to the interconnected edge nodes; 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, Assigning a corresponding service ID to each edge node includes: Obtain the service identifier corresponding to each edge node, wherein the service identifier is used to represent the service identifier of the service to which the edge node belongs; Request the wide area network to assign 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 orchestrator of the edge node.

4. The method according to claim 3, characterized in that, The step of generating a service SID corresponding to the service ID based on the service ID, and publishing the service SID to the wide area network via the BGP protocol, includes: After receiving the service ID, the SRv6 instruction orchestrator of the edge node generates the SRv6 service instruction SID of the edge node; The SRv6 instruction SID is written into the local service registration database of the edge node using the SRv6 instruction orchestrator. The SRv6 service instruction SID is instantiated, and then, via the BGP protocol, the SRv6 service instruction SID is published to other edge nodes in the wide area network in the form of an IPv6 address, combined with the community attribute value corresponding to the edge node.

5. The method according to claim 4, characterized in that, The query for the target service SID corresponding to the route includes: 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; If 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. If the first service ID exists in the local service registration database of the current edge node, determine 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, 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. When the first service ID is a local service of the edge node, the target service SID corresponding to the route is determined to be instantiated on the current edge node.

6. The method according to claim 5, characterized in that, The step of returning the target service SID to the target terminal so that the target terminal can access the target service based on the target service SID includes: Determine 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, the local service SID of the access point is returned to the target terminal as the target service SID; If the service accessed by the target terminal is not deployed at the access point corresponding to the target terminal, determine whether the service accessed by the target terminal is instantiated on the current edge node; When the service accessed by the target terminal is instantiated on the current edge node, the destination address of the target terminal is updated to the address of the current edge node, and the target service is accessed. If the service accessed by the target terminal is not instantiated on the current edge node, update the destination address of the target terminal to the address of another edge node interconnected with the current edge node, until the service accessed by the target terminal is instantiated on 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 includes: The service initialization module is used to initialize each edge node, establish routes between the edge nodes, and divide the service ID range for each edge node. The service instantiation module is used to assign a corresponding service ID to each of the edge nodes. 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 via the BGP protocol; 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 query the 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 can access the target service based on the target service SID.

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

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the 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, Includes computer instructions for causing a computer to execute the edge cloud environment dynamic service registration method according to any one of claims 1 to 6.

Images