Method and System for Edge Cloud Native Service Organization and Consumption in High-Maneuverability Environments

Abstract

The present invention discloses a method and system for edge cloud-native service organization and consumption in a highly mobile environment. The method includes configuring initial parameters for each edge cloud-native service, generating an edge cloud-native service status management table on all edge service nodes, deploying edge cloud-native service instances that generate the lower limit number of startup service loads on each edge service node within the service deployment scope, and registering and updating them in real time into the edge cloud-native service status management table of the local edge service node. The edge service node receives and responds to the edge cloud-native service consumption requests of the application software on the edge node in real time, and matches the edge cloud-native service provider for the application software. The system includes edge cloud-native service management software, multiple edge cloud-native services, and cloud-native service proxy software. The present invention supports reliable and efficient local consumption of cloud-native services by distributed system application software, which helps to improve the communication resource utilization rate and service access timeliness of edge cloud-native service organization and consumption.

Description

Technical Field

[0001] The present invention relates to the field of edge computing technology, and in particular to a method and system for organizing and enjoying edge cloud services in a high-mobility environment. Background Art

[0002] Edge computing technology continues to make breakthroughs, and various public service businesses are extending to the edge, which in turn increases the scale and complexity of information systems and brings challenges to the organization and application of cloud services in edge environments.

[0003] In the current market, there are a large number of information devices in the edge environment for building various small and medium-sized information systems, but the software and hardware resources of these devices are uneven, the performance is different, and some are even poor. At the same time, due to the complex terrain and weather during the mobility process, the communication resources at the edge are limited and weakly connected. In order to provide more and quality-guaranteed mobility service enjoyment support to various information systems at all levels of the edge, the initial parameters of the edge cloud service configuration can be standardized, the edge cloud service instance can be elastically deployed in the edge cloud and the service backplane data can be synchronized in real time. At the same time, the edge cloud service status can be registered and updated in real time and synchronized according to the right, and the edge node can enjoy the edge cloud service to provide service instance matching. Therefore, in order to meet the application requirements of high-mobility and weak-connection scenarios, light-weight edge communication resources can be used, and distributed system applications can be supported to reliably and efficiently enjoy cloud services nearby, while taking into account the improvement of communication resource utilization and service access timeliness. The edge cloud service organization enjoyment technology that can be applied to the edge high-mobility and weak-connection communication environment has become a necessary consideration in the overall planning of the information system software service platform.

[0004] At present, there is no method for organizing and enjoying the edge cloud services required above. Therefore, it is urgently needed in the current information system construction to comprehensively design a lightweight way to synchronize service status and interactive services under high-mobility conditions at the edge using edge communication resources, and to support physically distributed system applications to enjoy cloud services nearby under weak connections, so as to reduce the risks of inefficient access to edge cloud services in distributed systems due to limited edge communication resources. Summary of the invention

[0005] Purpose of the invention: The purpose of the present invention is to provide a method and system for organizing and enjoying edge cloud services in a highly mobile environment.

[0006] Technical solution: The edge cloud service organization and enjoyment method for a high-mobility environment described in the present invention comprises the following steps:

[0007] S1: Each edge cloud service is configured with initial parameters. According to the service deployment scope and the permissions of the deployment points, the service ownership types are divided into the same type of rights for the entire network, different types of rights for the entire network, the same type of rights for each domain, different types of rights for each domain, and the same type of rights for the same location;

[0008] S2: Generate an edge cloud service status management table on all edge service nodes within the edge cloud, and register and update in real time the edge cloud service status generated by the local edge service node and the updated edge cloud service status received from other edge service nodes.

[0009] S3: Deploy and generate edge cloud service instances that start the lower limit number of service loads on each edge service node within the service deployment scope of each edge cloud service, and request edge cloud internal service floor data synchronization according to the service floor data and service deployment scope configuration, and add or relay corresponding edge cloud service instances according to the service real-time load number and service instance health status.

[0010] S4: Each edge cloud service registers and updates the edge cloud service status in real time into the edge cloud service status management table of the local edge service node, and delivers and updates it to the edge cloud service status management tables of other edge service nodes according to the weight.

[0011] S5: All edge service nodes within the edge cloud receive and respond to the edge cloud service consumption requests of the application software on the edge nodes in real time, and match edge cloud service providers for the application software from them in combination with the edge cloud service status management table, and the application software uses it to call and access the corresponding edge cloud service.

[0012] Further, the initial parameters in step S1 include service floor data, service deployment scope, service available scope, service ownership type, service load lower limit instance number, and service instance load peak number.

[0013] Further, step S1 includes:

[0014] S11: Each edge cloud service configures its service floor data, that is, configures all service floor data units in the service floor data, and the number of service floor data units ≥ 0;

[0015] S12: Each edge cloud service configures its service deployment scope, that is, configures all deployment system levels or all deployment points within the service deployment scope, the number of service deployment system levels ≥ 1, and the number of service deployment points ≥ 1;

[0016] S13: Each edge cloud service configures its service available scope, that is, configures all available system levels or all available points within the service available scope, the number of service available system levels ≥ 1, and the number of service available points ≥ 2;

[0017] S14: Each edge cloud service configures its service ownership type, that is, selects one from the whole network right same type, whole network right different type, sub-domain right same type, sub-domain right different type, and same position right same type for configuration;

[0018] S15: Each edge cloud native service configures the lower limit number of service load instances, where the lower limit number of service load instances ≥ 1, and when the lower limit number of service load instances = 2, it means dual-active primary and standby instances are enabled for the edge cloud native service;

[0019] S16. The initial parameters of each edge cloud native service are packaged into the software segment package.

[0020] Furthermore, the edge cloud native service status management table in step S2 refers to a management table that records the status of all edge cloud native services in the edge cloud in real-time and is updated. It includes multiple edge cloud native service status record units. The status of each edge cloud native service in each record unit includes service ID, service name, available number of service load instances, and service instance ID, system level to which the service instance belongs, node address to which the service instance belongs, and health status of the service instance of the corresponding service load instance.

[0021] Furthermore, step S3 includes:

[0022] S31: Each edge cloud native service successively installs and deploys the edge cloud native service on each edge service node within its service deployment scope using the edge cloud native service software segment package;

[0023] S32: Each edge cloud native service successively creates the edge cloud native service on each edge service node within its service deployment scope, and initially generates and starts the corresponding number of edge cloud native service instances according to its configured lower limit number of service load instances;

[0024] S33: Each edge cloud native service successively requests real-time monitoring of changes in the service floor data within the edge cloud according to its service floor data and service deployment scope configuration on each edge service node within its service deployment scope, and immediately synchronizes the service floor data increment to all edge service nodes within the service deployment scope when changes occur;

[0025] S34: Each edge cloud native service successively monitors its real-time service load number and service instance health status on each edge service node within its service deployment scope. When the following conditions are met, a new or relay-generated and started corresponding edge cloud native service instance is added:

[0026] S34: Each edge cloud native service successively monitors its real-time service load number and service instance health status on each edge service node within its service deployment scope. When the following conditions are met, a new or relay-generated and started corresponding edge cloud native service instance is added:

[0027] ,

[0028] where, represents the available number of service load instances; Indicates the peak number of service instance loads; Indicates the real-time load number of the service.

[0029] Furthermore, the step S4 includes:

[0030] S41: When each edge cloud-born service is created, register and update the corresponding edge cloud-born service into the edge cloud-born service status management table of the local edge service node, record its service ID, service name, and the available instance number of the service load as 0;

[0031] S42: When each edge cloud-born service generates and starts each edge cloud-born service instance, register and update the corresponding edge cloud-born service instance into the edge cloud-born service status management table of the local edge service node, record its service instance ID, the system level to which the service instance belongs, the node address to which the service instance belongs, and the health status of the service instance as available. At the same time, increment the available instance number of the service load by 1;

[0032] S43: When the health status of any edge cloud-born service instance changes to overloaded, register and update the health status of the corresponding edge cloud-born service instance into the edge cloud-born service status management table of the local edge service node, record its service instance health status as overloaded;

[0033] S44: When the health status of any edge cloud-born service instance changes to faulty, register and update the health status of the corresponding edge cloud-born service instance into the edge cloud-born service status management table of the local edge service node, record its service instance health status as faulty, and at the same time decrement the available instance number of the service load by 1;

[0034] S45: When the health status of any edge cloud-born service instance resumes to available, register and update the health status of the corresponding edge cloud-born service instance into the edge cloud-born service status management table of the local edge service node, record its service instance health status as available;

[0035] S46: Update the edge cloud-born service status of the local edge service node in real time. Based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet splitting and sending response timeout retransmission mechanism thereon, deliver it to other edge service nodes in the edge cloud according to the weight. Other edge service nodes receive and update the corresponding edge cloud-born service status.

[0036] Furthermore, in the step S5, the edge nodes include edge service nodes and edge terminal nodes;

[0037] The edge cloud service consumption request is the request of the application software on any edge node to consume the edge cloud service, including the service consumption request response service ID, as well as the application ID of the application that initiates the service consumption request, the system level to which the application belongs, and the address of the node to which the application belongs;

[0038] The edge cloud service provider is an edge cloud service instance that provides services for the application software on the corresponding edge node.

[0039] Further, the step S5 includes the following steps:

[0040] S51: All edge service nodes in the edge cloud receive in real time the edge cloud service consumption request of the application software on the edge node, and use the edge cloud service instance matching formula to match an edge cloud service provider for the application software from the edge cloud service status management table, and based on the UDP connectionless transmission protocol applicable to the edge high-mobility environment and the packet splitting transmission acknowledgment timeout retransmission mechanism thereon, send the edge cloud service consumption request response to the corresponding edge node. The edge cloud service consumption request response includes the service consumption request response reply application ID, the service instance ID of its edge cloud service provider, and the service instance affiliated node address information;

[0041] S52: The edge node receives in real time the edge cloud service consumption request response from the corresponding edge service node, and according to the edge cloud service consumption request response, based on the UDP connectionless transmission protocol applicable to the edge high-mobility environment and the packet splitting transmission acknowledgment timeout retransmission mechanism thereon, sends the edge cloud service access request of the corresponding application software to the edge cloud service provider at the service instance affiliated node address and service instance ID. The edge cloud service access request includes the service access request initiating application ID, the service access request type, and the service access request content;

[0042] S53: The edge cloud service provider receives in real time the edge cloud service access request from the edge node, and according to the edge cloud service access request, based on the UDP connectionless transmission protocol applicable to the edge high-mobility environment and the packet splitting transmission acknowledgment timeout retransmission mechanism thereon, sends the service access request response to the corresponding edge node. The edge cloud service access request response includes the service access request response reply application ID, the service access request response type, and the service access request response content;

[0043] S54: The edge node receives in real time the edge cloud service access request response from the edge cloud service provider, and according to the edge cloud service access request response, returns the service access request response result to the corresponding application software. The service access request response result includes the service access request response type and the service access request response content.

[0044] Further, the edge cloud service instance matching formula in step S51 is as follows:

[0045] ,

[0046] where represents the serial number of the edge cloud service instance in the edge cloud service status management table; represents the edge cloud service status management table; represents the th health status of the edge cloud service instance, where = 1 indicates available, 2 indicates overloaded, and 3 indicates faulty; represents the subordination system level of the th edge cloud service instance; represents the subordination system level of the application software; represents the service ownership type of the edge cloud service for which the application software on the edge node initiates a service enjoyment request. Among them, = 1 indicates the same type of network-wide rights, 2 indicates different types of network-wide rights, 3 indicates the same type of domain-wide rights, 4 indicates different types of domain-wide rights, and 5 indicates the same type of peer rights; represents the edge cloud service provider matched for the application software from the edge cloud service status management table. When the service ownership type of the requested edge cloud service is 1, 3, or 5, the matched edge cloud service instance has an available service instance health status and the subordination system level of the service instance is closest to that of the application software. When the service ownership type of the requested edge cloud service is 2 or 4, the matched edge cloud service instance has an available service instance health status, the subordination system level of the service instance is not less than that of the application software, and is closest to that of the application software.

[0047] The edge cloud service organization enjoyment system for a highly mobile environment according to the present invention includes: deploying edge cloud service management software and multiple edge cloud services on edge service nodes, and deploying edge cloud service management software on edge nodes;

[0048] The edge cloud service management software is configured to: generate an edge cloud service status management table on all edge service nodes within the edge cloud, and register and update in real time the edge cloud service status of the local edge service node and the edge cloud service status generated by other edge service nodes that receive updates; receive and respond to in real time the edge cloud service enjoyment requests of the application software on the edge nodes for all edge service nodes within the edge cloud, and match an edge cloud service provider for the application software in combination with the edge cloud service status management table;

[0049] The edge cloud generation service is configured to: configure its initial parameters of service chassis data, service deployment scope, service available scope, service ownership type, lower limit number of service load instances, and peak number of service instance loads; deploy edge cloud generation service instances that generate the lower limit number of service loads on each edge service node within its service deployment scope, and request the synchronization of service chassis data within the edge cloud according to its service chassis data and service deployment scope, and add or relay corresponding edge cloud generation service instances according to the real-time service load number and service instance health status; register and update the edge cloud generation service status in real time to the edge cloud generation service status management table of the local edge service node, and send the update to the edge cloud generation service status management tables of other edge service nodes according to the authority;

[0050] The edge cloud generation service management software is configured to: receive in real time the edge cloud generation service enjoyment requests of the application software on the edge node, and forward the edge cloud generation service enjoyment requests of the application software to the corresponding edge service node within the edge cloud connected to the edge node; receive in real time the edge cloud generation service enjoyment request responses of the corresponding edge service node, and send the edge cloud generation service access requests of the application software to the corresponding edge cloud generation service provider according to the edge cloud generation service enjoyment request responses; receive in real time the edge cloud generation service access request responses of the corresponding edge cloud generation service provider, and return the service access request response results to the application software according to the edge cloud generation service access request responses.

[0051] Beneficial effects: Compared with the prior art, the present invention has the following remarkable advantages: In the edge high-mobility and weak-connection communication environment, the present invention standardizes the initial parameters of the edge cloud generation service configuration, elastically scales and deploys edge cloud generation service instances within the edge cloud and synchronizes the service chassis data in real time, and at the same time registers and updates the edge cloud generation service status in real time and synchronizes it according to the authority, providing service instance matching for the edge node to enjoy the edge cloud generation service; not only supports the efficient availability of the distributed system application to enjoy the cloud generation service nearby, but also realizes the scenario application of the edge cloud generation service organization for the high-mobility environment, enabling it to be applicable to business information systems such as motor vehicles, ships, and airplanes, supporting the reliable and efficient access of the distributed system application software to the cloud generation service nearby, so as to carry out relevant operations, which helps to improve the utilization rate of communication resources and the timeliness of service access for the edge cloud generation service organization to enjoy. Brief Description of the Drawings

[0052] Figure 1 It is a schematic diagram of the application scenario of the method for the edge cloud generation service organization to enjoy;

[0053] Figure 2 It is a schematic diagram of the process of standardizing and configuring service initial parameters;

[0054] Figure 3 It is a schematic diagram of the process of elastically scaling and deploying service instances;

[0055] Figure 4 Schematic diagram of the process for real-time updating and synchronizing service status;

[0056] Figure 5 Schematic diagram of the process for matching application service instances. Detailed implementation manners

[0057] The technical solution of the present invention will be further described below in conjunction with the accompanying drawings.

[0058] As Figure 1 shown, the method for enjoying edge cloud generation services in a high-mobility environment according to the present invention includes the following steps:

[0059] S1: Standardize and configure initial service parameters. Each edge cloud generation service configures its initial parameters such as service floorboard data, service deployment scope, service available scope, service ownership type, lower limit number of service load instances, peak number of service instance loads, etc. Among them, according to the service deployment scope and its deployment point permission, the service ownership type is divided into full-network right homogeneous type, full-network right heterogeneous type, domain right homogeneous type, domain right heterogeneous type, and same-position right homogeneous type.

[0060] The edge cloud generation service refers to the edge public enjoyment service generated on all edge service nodes in the edge cloud, which is identified by the edge cloud generation service ID;

[0061] The service floorboard data refers to the underlying data for operation based on the service access request response of the edge cloud generation service, which is composed of several service floorboard data units. The service floorboard data unit is identified by "edge cloud generation service ID + floorboard data unit ID";

[0062] The service deployment scope refers to the deployment point range of the edge cloud generation service. All service deployment points belong to the edge address book, and each edge address book node has system level and node address attributes. At the same time, the deployment point range is configured according to the selected system level range or the selected point range. All service deployment points are screened and obtained from the edge address book through the deployment system level range or the deployment point range;

[0063] The service available scope refers to the available point range of the edge cloud generation service, that is, the point range where the edge cloud generation service can be enjoyed by application software. All service available points belong to the edge address book, and each edge address book node has system level and node address attributes. At the same time, the available point range is configured according to the selected system level range or the selected point range. All service available points are screened and obtained from the edge address book through the available system level range or the available point range;

[0064] The full-network equal-authority type means that the edge-cloud-native service is deployed on all edge service nodes within the edge cloud, and the processing transaction authorities on each deployed edge service node are completely the same;

[0065] The full-network different-authority type means that the edge-cloud-native service is deployed on all edge service nodes within the edge cloud, but the processing transaction authorities on each deployed edge service node are different;

[0066] The domain-partition equal-authority type means that the edge-cloud-native service is deployed on all edge service nodes that belong to several but not all system levels within the edge cloud, and the processing transaction authorities on each deployed edge service node are completely the same;

[0067] The domain-partition different-authority type means that the edge-cloud-native service is deployed on all edge service nodes that belong to several but not all system levels within the edge cloud, but the processing transaction authorities on each deployed edge service node are different;

[0068] The same-position equal-authority type means that the edge-cloud-native service is deployed on the primary and standby edge service nodes that belong to the same position within the edge cloud, and the processing transaction authorities on each deployed edge service node are completely the same;

[0069] The lower-limit instance number of service load refers to the lower-limit number of service instances that the edge-cloud-native service load can respond to concurrent service access requests;

[0070] The peak number of service instance load refers to the peak number of concurrent service access requests that each instance of the edge-cloud-native service can respond to.

[0071] As Figure 2 shown, the detailed steps for standardizing and configuring the initial parameters of the service are as follows:

[0072] S11: Configure the service chassis data. Each edge-cloud-native service configures its service chassis data, that is, configures all service chassis data units in the service chassis data, and the number of service chassis data units ≥ 0.

[0073] S12: Configure the service deployment scope. Each edge-cloud-native service configures its service deployment scope, that is, configures all deployed system levels or all deployed positions within the service deployment scope. The number of deployed system levels ≥ 1, and the number of deployed positions ≥ 1.

[0074] S13: Configure the service available scope. Each edge-cloud-native service configures its service available scope, that is, configures all available system levels or all available positions within the service available scope. The number of available system levels ≥ 1, and the number of available positions ≥ 2.

[0075] S14: Configure the service ownership type. Each edge cloud-native service configures its service ownership type, that is, selects one from the following: whole-network same type, whole-network different type, domain-partition same type, domain-partition different type, and same-position same type for configuration.

[0076] S15: Configure the service load parameters. Each edge cloud-native service configures the lower limit number of instances of its service load. The lower limit number of instances of the service load ≥ 1. Generally, the lower limit number of instances of the service load = 2, that is, when the edge cloud-native service is enabled, there are active-active master-backup instances.

[0077] S16: Package the initial parameter configuration. The initial parameter configuration of each edge cloud-native service is packaged into its software segment package.

[0078] S2: Generate the service status management form. Generate the edge cloud-native service status management form on all edge service nodes within the edge cloud, which is used to register and update the local edge service node in real time and receive and update the edge cloud-native service status generated by other edge service nodes.

[0079] The edge cloud-native service status management form refers to a management form that records and updates the status of all edge cloud-native services within the edge cloud in real time. It consists of several edge cloud-native service status record units. The edge cloud-native service status recorded in each unit includes the service ID, service name, available number of service instances for the service load, and the service instance ID, system level to which the service instance belongs, node address to which the service instance belongs, and health status of the service instance corresponding to the service load instance; among them,

[0080] The available number of service instances for the service load refers to the real-time available number of service instances that the edge cloud-native service load can respond to concurrent service access requests.

[0081] The health status of the service instance refers to the real-time health status of the edge cloud-native service instance, including available, overloaded, and faulty. When there is a fault in an edge cloud-native service instance, the available number of service instances for the service load is reduced by 1.

[0082] S3: Elastically scale and deploy service instances. Each edge cloud-native service deploys and generates edge cloud-native service instances that start the lower limit number of service load instances on each edge service node within its service deployment range, and requests the synchronization of service floor data within the edge cloud according to its service floor data and service deployment range, and adds or relays corresponding edge cloud-native service instances according to the service real-time load number and the health status of the service instances.

[0083] The service real-time load number refers to the number of concurrent service access requests that the edge cloud-native service responds to in real time.

[0084] As Figure 3 shown, the detailed steps for elastically scaling and deploying service instances are as follows:

[0085] S31: Install and deploy edge cloud native services. Each edge cloud native service is installed and deployed on each edge service node within its service deployment scope in sequence, using the edge cloud native service software segment package.

[0086] S32: Create and enable edge cloud native services. Each edge cloud native service creates edge cloud native services on each edge service node within its service deployment scope in sequence, and initializes and starts the corresponding number of edge cloud native service instances according to its service load lower limit instance number configuration.

[0087] S33: Real-time synchronize service floor data. Each edge cloud native service requests the edge cloud data synchronization to monitor the change of service floor data in real time on each edge service node within its service deployment scope according to its service floor data and service deployment scope configuration, and instantaneously synchronizes the service floor data increment to all edge service nodes within the service deployment scope when the change occurs.

[0088] S34: Real-time relay start service instances. Each edge cloud native service monitors its service real-time load number and service instance health status on each edge service node within its service deployment scope in real time. When the following conditions are met, a new or relay-generated and started corresponding edge cloud native service instance is added:

[0089] ,

[0090] wherein, represents the available instance number of service load; represents the peak number of service instance loads; represents the service real-time load number.

[0091] S4: Real-time update and synchronize service status. Each edge cloud native service registers and updates the edge cloud native service status to the edge cloud native service status management table of the local edge service node in real time, and delivers and updates it to the edge cloud native service status management table of other edge service nodes according to the authority.

[0092] The said "according to the authority" means that the local edge service node enjoys the authority of the edge cloud native service organization of the corresponding destination other edge service nodes, that is, those edge cloud native services with corresponding edge service nodes in the available service range of the organization to enjoy the service.

[0093] Such as Figure 4 shown, the detailed steps of real-time update and synchronize service status are as follows:

[0094] S41: Register and update service creation information. When each edge cloud native service is created, it registers and updates the corresponding edge cloud native service to the edge cloud native service status management table of the local edge service node, records its service ID, service name, and the available instance number of service load as 0.

[0095] S42: Register and update service instance information. When each edge cloud service generates and starts each edge cloud service instance, it registers and updates the corresponding edge cloud service instance to the edge cloud service status management table of the local edge service node, records its service instance ID, service instance affiliated system level, service instance affiliated node address, and service instance health status is available, and the number of service load available instances is increased by 1.

[0096] S43: Register and update service instance overload. When the health status of any edge cloud service instance changes to overload, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance to the edge cloud service status management table of the local edge service node, and records that the health status of its service instance is overloaded.

[0097] S44: Register and update service instance failure. When the health status of any edge cloud service instance changes to failure, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance to the edge cloud service status management table of the local edge service node, records the health status of its service instance as failure, and reduces the number of available instances of the service load by 1.

[0098] S45: Register and update the service instance to be available. When the health status of any edge cloud service instance is restored to be available, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance to the edge cloud service status management table of the local edge service node, and records that the health status of its service instance is available.

[0099] S46: Real-time synchronous service status update. The edge cloud service status of the local edge service node is updated in real time, based on the UDP connectionless transmission protocol applicable to the edge high mobility environment and the packet sending response timeout retransmission mechanism thereon, and sent to other edge service nodes in the edge cloud according to the authority, and other edge service nodes receive the corresponding updated edge cloud service status.

[0100] S5: Matching application service instances. All edge service nodes in the edge cloud receive and respond to edge cloud service requests from applications on edge nodes in real time, and match edge cloud service providers for applications in combination with the edge cloud service status management table. Applications obtain the information and use it to call and access the corresponding edge cloud services.

[0101] The edge nodes include edge service nodes and edge terminal nodes;

[0102] The edge cloud service use request refers to a request for use of edge cloud services by application software on any edge node, including a service use request response service ID, and an application ID of the application initiating the service use request, the application belonging system level, and the application belonging node address;

[0103] The edge cloud service provider refers to the edge cloud service instance that provides services for the application software on the corresponding edge node.

[0104] As Figure 5 shown, the detailed steps for matching the application service instance are as follows:

[0105] S51: Match the application to enjoy the service instance. All edge service nodes in the edge cloud receive the edge cloud service enjoyment requests of the application software on the edge node in real time, and use the edge cloud service instance matching formula to match the edge cloud service provider for the application software from the edge cloud service status management table, and based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet splitting and sending response timeout retransmission mechanism thereon, send the edge cloud service enjoyment request response to the corresponding edge node. The edge cloud service enjoyment request response includes the service enjoyment request response reply application ID, the service instance ID of its edge cloud service provider, and the service instance affiliated node address information.

[0106] S52: Send a service access request to the service side. The edge node receives the edge cloud service enjoyment request response of the corresponding edge service node in real time, and according to the edge cloud service enjoyment request response, based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet splitting and sending response timeout retransmission mechanism thereon, sends the edge cloud service access request of the corresponding application software to the edge cloud service provider with the corresponding service instance affiliated node address and service instance ID. The edge cloud service access request includes the service access request initiating application ID, the service access request type, and the service access request content.

[0107] S53: Receive the response to reply the service access request. The edge cloud service provider receives the edge cloud service access request of the edge node in real time, and according to the edge cloud service access request, based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet splitting and sending response timeout retransmission mechanism thereon, sends the service access request response to the corresponding edge node. The edge cloud service access request response includes the service access request response reply application ID, the service access request response type, and the service access request response content.

[0108] S54: Return the service access request response result. The edge node receives the edge cloud service access request response of the edge cloud service provider in real time, and according to the edge cloud service access request response, returns the service access request response result to the corresponding application software. The service access request response result includes the service access request response type and the service access request response content.

[0109] The edge cloud service instance matching formula is as follows:

[0110] ,

[0111] wherein, represents the serial number of the edge cloud-native service instance in the edge cloud-native service status management table; represents the edge cloud-native service status management table; represents the health status of the th edge cloud-native service instance, wherein = 1 indicates available, 2 indicates overloaded, and 3 indicates faulty; represents the affiliated system level of the th edge cloud-native service instance; represents the affiliated system level of the application software; represents the service ownership type of the edge cloud-native service for which the application software on the edge node initiates a service enjoyment request, wherein = 1 indicates the whole network right homogeneous type, 2 indicates the whole network right heterogeneous type, 3 indicates the sub-domain right homogeneous type, 4 indicates the sub-domain right heterogeneous type, and 5 indicates the same position right homogeneous type; represents the edge cloud-native service provider matched for the application software from the edge cloud-native service status management table. When the service ownership type of the requested edge cloud-native service = 1, 3, or 5, it matches the edge cloud-native service instance with an available service instance health status and the closest affiliated system level between the service instance and the application software. When the service ownership type of the requested edge cloud-native service = 2 or 4, it matches the edge cloud-native service instance with an available service instance health status, the affiliated system level of the service instance not less than that of the application software and the closest to the affiliated system level of the application software.

[0112] The edge cloud-native service organization enjoyment system for a highly mobile environment according to the present invention includes deploying edge cloud-native service management software and several edge cloud-native services on edge service nodes, and deploying edge cloud-native service proxy software on edge nodes.

[0113] The edge cloud-native service management software can manage the status of all edge cloud-native services in the edge cloud and match edge cloud-native service providers for application software, and is configured to:

[0114] Generate an edge cloud-native service status management table on all edge service nodes in the edge cloud for real-time registration and update of the edge cloud-native service status of the local edge service node and the receipt of updates from other edge service nodes;

[0115] For all edge service nodes in the edge cloud, receive and respond to edge cloud-native service enjoyment requests from application software on edge nodes in real time, and match edge cloud-native service providers for application software in combination with the edge cloud-native service status management table.

[0116] The edge cloud generation service can configure service initial parameters, operate and maintain service instances, and register and update service status, and is configured to:

[0117] Configure initial parameters such as its service floor data, service deployment scope, service available scope, service ownership type, service load lower limit instance number, service instance load peak number, etc.;

[0118] Deploy and generate edge cloud generation service instances with the number of service load lower limit instances on each edge service node within its service deployment scope, and configure and request edge cloud internal service floor data synchronization according to its service floor data and service deployment scope, and add or relay corresponding edge cloud generation service instances according to the service real-time load number and service instance health status;

[0119] Register and update the edge cloud generation service status in real time to the edge cloud generation service status management table of the local edge service node, and send and update it to the edge cloud generation service status management table of other edge service nodes according to the authority.

[0120] The edge cloud generation service proxy software can proxy the edge cloud generation service enjoyment and access requests of application software on the edge node, and is configured to:

[0121] Realtime proxy to receive the edge cloud generation service enjoyment requests of application software on the edge node, and forward the edge cloud generation service enjoyment requests of the application software to the corresponding edge service node within the edge cloud connected to the edge node;

[0122] Realtime proxy to receive the edge cloud generation service enjoyment request responses of the corresponding edge service node, and deliver the edge cloud generation service access requests of the application software to the corresponding edge cloud generation service provider according to the edge cloud generation service enjoyment request responses;

[0123] Realtime proxy to receive the edge cloud generation service access request responses of the corresponding edge cloud generation service provider, and return the service access request response results to the application software according to the edge cloud generation service access request responses.

[0124] The specific implementation, deployment, and operation methods of each role in the system can refer to the description in the foregoing method process, and will not be elaborated here.

[0125] The method of the present invention is simple and easy to implement, and can provide a means for enjoying high-availability and high-reliability edge cloud generation services for edge high-mobility and weak-connection communication environments, and can support a significant improvement in the communication resource utilization rate and service access timeliness under edge high-mobility conditions.

Claims

1. A method for an edge cloud-native service organization to enjoy services in a highly mobile environment, characterized in that It includes the following steps: S1: Each edge cloud service configures initial parameters. According to different service deployment scopes and deployment point permissions, the service ownership types are divided into full-network same-type, full-network different-type, domain-partition same-type, domain-partition different-type, and same-position same-type; S2: An edge cloud service status management table is generated on all edge service nodes within the edge cloud, and the local edge service node and the edge cloud service status generated by other edge service nodes receiving updates are registered and updated in real time; S3: Each edge cloud service deploys and generates edge cloud service instances that start the lower limit of the service load on each edge service node within its service deployment scope, and requests the synchronization of service floor data within the edge cloud according to the service floor data and service deployment scope, and adds or relays corresponding edge cloud service instances according to the service real-time load number and service instance health status; S4: Each edge cloud service registers and updates the edge cloud service status in real time into the edge cloud service status management table of the local edge service node, and sends it for update to the edge cloud service status management tables of other edge service nodes according to the permissions; S5: All edge service nodes within the edge cloud receive and respond to the edge cloud service usage requests of the application software on the edge nodes in real time, and match edge cloud service providers for the application software in combination with the edge cloud service status management table. After the application software obtains it, it is used to call and access the corresponding edge cloud service; The step S4 includes: S41: When each edge cloud service is created, it registers and updates the corresponding edge cloud service into the edge cloud service status management table of the local edge service node, records its service ID, service name, and the available number of service load instances as 0; S42: When each edge cloud service generates and starts each edge cloud service instance, it registers and updates the corresponding edge cloud service instance into the edge cloud service status management table of the local edge service node, records its service instance ID, the system level to which the service instance belongs, the address of the node to which the service instance belongs, and the health status of the service instance as available. At the same time, the available number of service load instances is incremented by 1; S43: When the health status of any edge cloud service instance changes to overloaded, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance into the edge cloud service status management table of the local edge service node, and records its service instance health status as overloaded; S44: When the health status of any edge cloud service instance changes to faulty, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance into the edge cloud service status management table of the local edge service node, records its service instance health status as faulty, and at the same time decrements the available number of service load instances by 1; S45: When the health status of any edge cloud service instance resumes to available, each edge cloud service registers and updates the health status of the corresponding edge cloud service instance into the edge cloud service status management table of the local edge service node, and records its service instance health status as available; S46: Update the edge cloud service status of the local edge service node in real time, and deliver it to other edge service nodes in the edge cloud according to the right, based on the UDP connectionless transport protocol applicable to the highly mobile edge environment and the packet splitting and sending response timeout retransmission mechanism on it. Other edge service nodes receive the update and correspondingly update the edge cloud service status.

2. The method for an edge cloud native service organization to enjoy services in a highly mobile environment according to claim 1, wherein The initial parameters in step S1 include service chassis data, service deployment scope, service available scope, service ownership type, service load lower limit instance number, and service instance load peak number.

3. The method for edge cloud service organization and utilization for high-mobility environments according to claim 1, wherein Step S1 includes: S11: Each edge cloud service configures its service chassis data, that is, configures all service chassis data units in the service chassis data, and the number of service chassis data units ≥ 0; S12: Each edge cloud service configures its service deployment scope, that is, configures all deployment system levels or all deployment points within the service deployment scope. The number of service deployment system levels ≥ 1, and the number of service deployment points ≥ 1; S13: Each edge cloud service configures its service available scope, that is, configures all available system levels or all available points within the service available scope. The number of service available system levels ≥ 1, and the number of service available points ≥ 2; S14: Each edge cloud service configures its service ownership type, that is, selects one from the whole network right same type, whole network right different type, domain right same type, domain right different type, and same position right same type for configuration; S15: Each edge cloud service configures its service load lower limit instance number. The service load lower limit instance number ≥ 1, and when the service load lower limit instance number = 2, it means that the edge cloud service enables dual-active master-slave instances when starting; S16: Package the initial parameter configuration of each edge cloud service into a software segment package.

4. The method for an edge cloud service organization in a highly mobile environment according to claim 1, wherein In step S2, the edge cloud service status management table refers to the management table that records the status of all edge cloud services in the edge cloud in real time, including multiple edge cloud service status record units. The edge cloud service status of each record unit includes service ID, service name, service load available instance number, and the service instance ID, service instance affiliated system level, service instance affiliated node address, and service instance health status of the corresponding service load instance.

5. The method for an edge cloud native service organization in a highly mobile environment according to claim 1, characterized in that Step S3 includes: S31: Each edge cloud service successively installs and deploys the edge cloud service on each edge service node within its service deployment scope, using the edge cloud service software segment package; S32: Each edge cloud service successively creates the edge cloud service on each edge service node within its service deployment scope, and initializes and starts the corresponding number of edge cloud service instances according to its service load lower limit instance number configuration; S33: Each edge cloud service successively requests real-time monitoring of the change of the service chassis data for data synchronization in the edge cloud according to its service chassis data and service deployment scope configuration on each edge service node within its service deployment scope, and immediately synchronizes the service chassis data increment to all edge service nodes within the service deployment scope when the change occurs; S34: Each edge cloud service monitors the real-time service load and service instance health status in real time on each edge service node within the service deployment range. When the following conditions are met, a corresponding edge cloud service instance is newly added or relayed and started: ， Among them, represents the number of available instances of the service load; represents the peak number of service instance loads; represents the real-time load number of the service.

6. The method for an edge cloud native service organization to enjoy services in a highly mobile environment according to claim 1, wherein The edge nodes in step S5 include edge service nodes and edge terminal nodes; The edge cloud service use request is a request for edge cloud service use by application software on any edge node, including the service use request response service ID, the application ID of the application initiating the service use request, the application belonging system level, and the application belonging node address; The edge cloud service provider is an edge cloud service instance that provides services to the application software on the corresponding edge node.

7. The method for an edge cloud service organization in a highly mobile environment according to claim 1, wherein The step S5 comprises the following steps: S51: All edge service nodes in the edge cloud receive edge cloud service use requests from applications on edge nodes in real time, and use edge cloud service instance matching formulas to match edge cloud service providers for applications from the edge cloud service status management table, and based on the UDP connectionless transmission protocol applicable to edge high mobility environments and the packet sending response timeout retransmission mechanism thereon, deliver edge cloud service use request responses to corresponding edge nodes. The edge cloud service use request responses include service use request response reply application ID and its edge cloud service provider's service instance ID, and service instance affiliated node address information; S52: The edge node receives the edge cloud service access request response of the corresponding edge service node in real time, and according to the edge cloud service access request response, based on the UDP connectionless transmission protocol applicable to the edge high mobility environment and the packet sending response timeout retransmission mechanism thereon, sends the edge cloud service access request of the corresponding application software to the edge cloud service provider of the corresponding service instance belonging node address and service instance ID. The edge cloud service access request includes the service access request initiating application ID, service access request type, and service access request content; S53: The edge cloud service provider receives the edge cloud service access request of the edge node in real time, and according to the edge cloud service access request, based on the UDP connectionless transmission protocol applicable to the edge high mobility environment and the packet sending response timeout retransmission mechanism thereon, sends the service access request response to the corresponding edge node, and the edge cloud service access request response includes the service access request response reply application ID, the service access request response type, and the service access request response content; S54: The edge node receives the edge cloud service access request response from the edge cloud service provider in real time, and returns the service access request response result to the corresponding application software according to the edge cloud service access request response. The service access request response result includes the service access request response type and the service access request response content.

8. The method for an edge cloud native service organization to enjoy services in a highly maneuverable environment according to claim 7, wherein The edge cloud service instance matching formula in step S51 is as follows: ， Among them, represents the serial number of the edge cloud native service instance in the edge cloud native service status management table; represents the edge cloud native service status management table; represents the th health status of the edge cloud native service instance, where =1 indicates available, 2 indicates overloaded, and 3 indicates faulty; represents the affiliated system level of the th edge cloud native service instance; represents the affiliated system level of the application software; represents the service ownership type of the edge cloud native service requested by the application software on the edge node. Among them, =1 indicates the same network-wide rights type, 2 indicates different network-wide rights types, 3 indicates the same sub-domain rights type, 4 indicates different sub-domain rights types, and 5 indicates the same peer rights type; represents the edge cloud native service provider matched for the application software from the edge cloud native service status management table. When the service ownership type of the requested edge cloud native service = 1, 3, or 5, it matches the edge cloud native service instance with an available service instance health status and the closest affiliated system level between the service instance and the application software. When the service ownership type of the requested edge cloud native service = 2 or 4, it matches the edge cloud native service instance with an available service instance health status, the affiliated system level of the service instance not less than that of the application software, and the closest to the affiliated system level of the application software.

9. An edge cloud native service organization sharing system for high-mobility environments, characterized in that, The method includes deploying edge cloud service management software and multiple edge cloud services on edge service nodes, and deploying edge cloud service management software on edge nodes; The edge cloud-native service management software is configured to: generate an edge cloud-native service status management table on all edge service nodes within the edge cloud, and register and update in real time the edge cloud-native service status of the local edge service node and the edge cloud-native service status generated by other edge service nodes that receive updates; For all edge service nodes within the edge cloud, receive and respond in real time to the edge cloud-native service consumption requests of the application software on the edge nodes, and match edge cloud-native service providers for the application software from the edge cloud-native service status management table; The edge cloud-native service is configured to: configure its initial parameters of service floor data, service deployment scope, service available scope, service ownership type, service load lower limit instance number, and service instance load peak number; deploy and generate edge cloud-native service instances that start the service load lower limit instance number on each edge service node within its service deployment scope, and request edge cloud-internal service floor data synchronization according to its service floor data and service deployment scope, and add or relay corresponding edge cloud-native service instances according to the service real-time load number and service instance health status; Register and update the edge cloud-native service status in real time into the edge cloud-native service status management table of the local edge service node, and deliver and update it to the edge cloud-native service status management tables of other edge service nodes according to the authority; The edge cloud-native service management software is configured to: proxy and receive in real time the edge cloud-native service consumption requests of the application software on the edge nodes, and forward the edge cloud-native service consumption requests of the application software to the corresponding edge service nodes within the edge cloud connected to the edge nodes; proxy and receive in real time the edge cloud-native service consumption request responses of the corresponding edge service nodes, and deliver the edge cloud-native service access requests of the application software to the corresponding edge cloud-native service providers according to the edge cloud-native service consumption request responses; proxy and receive in real time the edge cloud-native service access request responses of the corresponding edge cloud-native service providers, and return the service access request response results to the application software according to the edge cloud-native service access request responses; Each edge cloud-native service registering and updating the edge cloud-native service status in real time into the edge cloud-native service status management table of the local edge service node and delivering and updating it to the edge cloud-native service status management tables of other edge service nodes according to the authority includes: S41: When each edge cloud-native service is created, register and update the corresponding edge cloud-native service into the edge cloud-native service status management table of the local edge service node, record its service ID, service name, and the service load available instance number as 0; S42: When each edge cloud-native service generates and starts each edge cloud-native service instance, register and update the corresponding edge cloud-native service instance into the edge cloud-native service status management table of the local edge service node, record its service instance ID, service instance affiliated system level, service instance affiliated node address, and the service instance health status as available, and at the same time, the service load available instance number is incremented by 1; S43: When the health status of any edge cloud native service instance changes to overloaded, each edge cloud native service updates the registration of the health status of the corresponding edge cloud native service instance to the edge cloud native service status management table of the local edge service node, and records that the health status of its service instance is overloaded; S44: When the health status of any edge cloud native service instance changes to faulty, each edge cloud native service updates the registration of the health status of the corresponding edge cloud native service instance to the edge cloud native service status management table of the local edge service node, records that the health status of its service instance is faulty, and at the same time decrements the number of available instances of the service load by 1; S45: When the health status of any edge cloud native service instance returns to available, each edge cloud native service updates the registration of the health status of the corresponding edge cloud native service instance to the edge cloud native service status management table of the local edge service node, and records that the health status of its service instance is available; S46: Update the edge cloud native service status of the local edge service node in real time, and based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet splitting and sending acknowledgment timeout retransmission mechanism on it, deliver it to other edge service nodes in the edge cloud according to the weight. Other edge service nodes receive the update and update the corresponding edge cloud native service status.

Images