Edge cloud generation service organization enjoying method and system oriented to high-mobility environment

Abstract

The invention discloses an edge cloud generation service organization sharing method and system for a high-mobility environment, and the method comprises the steps: configuring an initial parameter for each edge cloud generation service, and generating an edge cloud generation service condition management table on all edge service nodes, deploying and generating edge cloud generation service instances of the number of starting service load lower limit instances on each edge service node in a service deployment range, and registering and updating the edge cloud generation service instances to an edge cloud generation service condition management table of a local edge service node in real time; the edge service node receives and responds to the edge cloud generation service enjoying request of the application software on the edge node in real time, and an edge cloud generation service provider is matched for the application software; the system comprises edge cloud generation service management software, a plurality of edge cloud generation services and cloud generation service agent software. According to the method, distributed system application software is supported to reliably and efficiently enjoy the cloud generation service nearby, and the utilization rate of communication resources enjoyed by edge cloud generation service organizations and the timeliness of service access are improved.

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: 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; 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 local edge service status and the edge cloud service status generated by other edge service nodes that receive updates. S3: For each edge cloud service, deploy and generate edge cloud service instances that start the lower limit number of service load instances on each edge service node within its service deployment scope, and request edge cloud service floor data synchronization according to the service floor data and service deployment scope configuration. Then, add or relay corresponding edge cloud service instances in real time according to the real-time service 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 to update the edge cloud service status management tables of other edge service nodes according to the weight. 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. Combining with the edge cloud service status management table, match edge cloud service providers for the application software, and the application software uses it to call and access the corresponding edge cloud service.

[0007] 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.

[0008] Further, step S1 includes: 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. 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 same right type, whole network different right type, sub-region same right type, sub-region different right type, and same position same right type for configuration. S15: Each edge cloud service configures its service load lower limit instance number, and the service load lower limit instance number ≥ 1. When the service load lower limit instance number = 2, it means that the edge cloud service enables dual-active master-backup instances when starting. S16: Package the initial parameter configuration of each edge cloud service into a software segment package.

[0009] Further, the edge cloud service status management table in step S2 refers to a 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, the number of available instances of service load, and the 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 of the corresponding service load instance.

[0010] Further, step S3 includes: S31: Each edge cloud service installs and deploys the edge cloud service on each edge service node within its service deployment range in turn, using the edge cloud service software segment package. S32: Each edge cloud service creates an edge cloud service on each edge service node within its service deployment range in turn, and initially generates and starts the corresponding number of edge cloud service instances according to the configuration of its lower limit number of service load instances. S33: Each edge cloud service requests real-time monitoring of changes in the service floor data in the edge cloud according to its service floor data and service deployment range configuration on each edge service node within its service deployment range, and immediately synchronizes the service floor data increment to all edge service nodes within the service deployment range when changes occur. S34: Each edge cloud service monitors its service real-time load number and service instance health status on each edge service node within its service deployment range in turn. When the following conditions are met, a new or relay-generated and started 1 corresponding edge cloud service instance is added: S34: Each edge cloud service monitors its service real-time load number and service instance health status on each edge service node within its service deployment range in turn. When the following conditions are met, a new or relay-generated and started 1 corresponding edge cloud service instance is added: , wherein, represents the number of available instances of service load; represents the peak number of service instance loads; represents the service real-time load number.

[0011] Further, step S4 includes: S41: When each edge cloud service is created, it registers and updates the corresponding edge cloud service to the edge cloud service status management table of the local edge service node, records its service ID, service name, and the number of available instances of service load 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 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 as available, and the number of available instances of the service load is increased by 1; S43: 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; S44: when the health status of any edge cloud service instance changes to fault, 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 fault, and reduces the number of available instances of the service load by 1; S45: 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; S46: Update the edge cloud service status of the local edge service node 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 based on it, and send it to other edge service nodes in the edge cloud according to the authority. Other edge service nodes receive the updated edge cloud service status.

[0012] Further, 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.

[0013] Furthermore, step S5 comprises the following steps: S51: All edge service nodes within the edge cloud receive in real time the edge cloud native service consumption requests of the application software on the edge nodes, and use the edge cloud native service instance matching formula to match, for the application software, edge cloud native service providers from the edge cloud native service status management table, and based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet-sending response timeout retransmission mechanism thereon, send the edge cloud native service consumption request responses to the corresponding edge nodes. The edge cloud native service consumption request responses include the service consumption request response reply application ID, the service instance ID of its edge cloud native service provider, and the service instance affiliated node address information; S52: The edge nodes receive in real time the edge cloud native service consumption request responses from the corresponding edge service nodes, and according to the edge cloud native service consumption request responses, based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet-sending response timeout retransmission mechanism thereon, send the edge cloud native service access requests of the corresponding application software to the edge cloud native service providers at the addresses of the service instance affiliated nodes and the service instance IDs. The edge cloud native service access requests include the service access request initiating application ID, the service access request type, and the service access request content; S53: The edge cloud native service providers receive in real time the edge cloud native service access requests from the edge nodes, and according to the edge cloud native service access requests, based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet-sending response timeout retransmission mechanism thereon, send the service access request responses to the corresponding edge nodes. The edge cloud native service access request responses include the service access request response reply application ID, the service access request response type, and the service access request response content; S54: The edge nodes receive in real time the edge cloud native service access request responses from the edge cloud native service providers, and according to the edge cloud native service access request responses, return the service access request response results to the corresponding application software. The service access request response results include the service access request response type and the service access request response content.

[0014] Furthermore, the edge cloud native service instance matching formula in step S51 is as follows: , 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 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; Indicates the subordinate system level of the application software; Indicates the service ownership type of the edge cloud-born service for the service enjoyment request initiated by the application software on the edge node, where =1 indicates the whole-network right same type, 2 indicates the whole-network right different type, 3 indicates the domain-based right same type, 4 indicates the domain-based right different type, 5 indicates the same-position right same type; Indicates the edge cloud-born service provider matched for the application software from the edge cloud-born service status management table. When the service ownership type of the requested edge cloud-born service = 1, 3, 5, it matches the edge cloud-born service instance with the service instance health status being available and the service instance subordinate system level being closest to the application software subordinate system level. When the service ownership type of the requested edge cloud-born service = 2, 4, it matches the edge cloud-born service instance with the service instance health status being available, the service instance subordinate system level being not less than the application software subordinate system level and being closest to the application software subordinate system level.

[0015] The edge cloud-born service organization and enjoyment system for high-mobility environments according to the present invention includes: deploying edge cloud-born service management software and multiple edge cloud-born services on edge service nodes, and deploying edge cloud-born service management software on edge nodes; The edge cloud-born service management software is configured to: generate an edge cloud-born service status management table on all edge service nodes within the edge cloud, and register and update in real time the edge cloud-born service status of the local edge service node and the edge cloud-born service status generated by other edge service nodes that receive updates; receive and respond to the edge cloud-born service enjoyment requests of the application software on the edge nodes in real time for all edge service nodes within the edge cloud, and match an edge cloud-born service provider for the application software in combination with the edge cloud-born service status management table; The edge cloud-born service is configured to: configure its service floor data, service deployment scope, service available scope, service ownership type, service load lower limit instance number, service instance load peak number initial parameters; deploy and generate edge cloud-born service instances that start the service load lower limit instance number on each edge service node within its service deployment scope, and request service floor data synchronization within the edge cloud according to its service floor data and service deployment scope, and add or relay corresponding edge cloud-born service instances in real time according to the real-time service load number and service instance health status; register and update the edge cloud-born service status in real time to the edge cloud-born service status management table of the local edge service node, and send and update it to the edge cloud-born service status management tables of other edge service nodes according to the rights; The edge cloud service management software is configured as follows: the real-time agent receives the edge cloud service enjoyment requests of the application software on the edge nodes, and forwards the edge cloud service enjoyment requests of the application software to the corresponding edge service nodes in the edge cloud connected to the edge nodes; the real-time agent receives the edge cloud service enjoyment request responses of the corresponding edge service nodes, and forwards the edge cloud service access requests of the application software to the corresponding edge cloud service providers according to the edge cloud service enjoyment request responses; the real-time agent receives the edge cloud service access request responses of the corresponding edge cloud service providers, and returns the service access request response results to the application software according to the edge cloud service access request responses.

[0016] 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 service configuration, elastically scales and deploys edge cloud service instances in the edge cloud and synchronizes the service floor data in real time, and at the same time registers and updates in real time and synchronizes the edge cloud service status according to the permissions, providing service instance matching for the edge nodes to enjoy the edge cloud services; not only supports the efficient availability of distributed system applications to enjoy cloud services nearby, but also realizes the scenario application of edge cloud service organization enjoyment for high-mobility environments, enabling it to be applicable to business information systems such as motor vehicles, ships, and aircraft, supporting distributed system application software to reliably and efficiently enjoy cloud services 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 edge cloud service organization enjoyment. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 FIG. is a schematic diagram of the application scenario of the method for edge cloud service organization enjoyment; Figure 2 FIG. is a schematic diagram of the process for standardizing the configuration of service initial parameters; Figure 3 FIG. is a schematic diagram of the process for elastically scaling and deploying service instances; Figure 4 FIG. is a schematic diagram of the process for real-time updating and synchronizing service status; Figure 5 FIG. is a schematic diagram of the process for matching application service instances. DETAILED DESCRIPTION OF THE INVENTION

[0018] The technical solution of the present invention will be further described below with reference to the accompanying drawings.

[0019] As Figure 1 shown, the method for edge cloud service organization enjoyment for high-mobility environments according to the present invention includes the following steps: S1: Standardize the configuration of service initial parameters. Each edge cloud service configures its initial parameters such as service backplane data, service deployment scope, service availability scope, service ownership type, service load lower limit instance number, service instance load peak number, etc. According to the service deployment scope and its deployment point permissions, the service ownership type is divided into full network ownership type, full network ownership type, domain ownership type, domain ownership type, and co-location ownership type.

[0020] The edge cloud service refers to the edge public service generated on all edge service nodes in the edge cloud, which is identified by the edge cloud service ID; The service backplane data refers to the self-maintained underlying data used by the edge cloud service to respond to the service access request for calculation, and is composed of several service backplane data units. The service backplane data unit is identified by "edge cloud service ID + backplane data unit ID"; The service deployment range refers to the deployment point range of edge cloud services. All service deployment points belong to the edge address book, and the edge address book nodes have 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; The service available range refers to the available point range of edge cloud services, that is, the point range of edge cloud services that can be used by application software. The service available points belong to the edge address book, and the edge address book nodes have 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; The same rights across the entire network means that the edge cloud service is deployed on all edge service nodes in the edge cloud and the transaction processing rights on each deployed edge service node are all the same; The full network rights heterogeneity refers to the fact that the edge cloud service is deployed on all edge service nodes in the edge cloud, but the processing transaction rights on each deployed edge service node are different; The domain-based rights homogeneity means that the edge cloud service is deployed on all edge service nodes belonging to several but not all system levels in the edge cloud, and the transaction processing rights on each deployed edge service node are all the same; The domain rights heterogeneity refers to the fact that edge cloud services are deployed on all edge service nodes belonging to several but not all system levels in the edge cloud, but the processing transaction rights on each deployed edge service node are different; The same-location rights and types refer to that the edge cloud service is deployed on the primary and backup edge service nodes belonging to the same point in the edge cloud and the processing transaction rights on each deployed edge service node are all the same; The lower limit number of service instances of the 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; The peak number of service instance loads refers to the peak number of concurrent service access requests that each instance of the edge cloud native service can respond to.

[0021] As Figure 2 shown, the detailed steps for standardizing and configuring the initial parameters of the service are as follows: 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.

[0022] S12: Configure the service deployment scope. Each edge cloud native 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.

[0023] 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 points within the service available scope. The number of service available system levels ≥ 1, and the number of service available points ≥ 2.

[0024] S14: Configure the service ownership type. Each edge cloud native service configures its service ownership type, that is, selects one from the whole network right homogeneous type, whole network right heterogeneous type, sub - domain right homogeneous type, sub - domain right heterogeneous type, and same - position right homogeneous type for configuration.

[0025] S15: Configure the service load parameters. Each edge cloud native service configures its lower limit number of service instances of the service load. The lower limit number of service instances of the service load ≥ 1. Generally, when the lower limit number of service instances of the service load = 2, it means that the edge cloud native service enables dual - active primary - standby instances when it is started.

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

[0027] 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.

[0028] The edge cloud service status management table refers to a management table that records in real time all the edge cloud service statuses within the edge cloud. It consists of several edge cloud service status record units. The edge cloud service status recorded in each unit includes service ID, service name, the number of available instances of the service load, and the 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 of the corresponding service load. Among them, The number of available instances of the service load refers to the real-time available number of service instances that the edge cloud service load can respond to concurrent service access requests. The health status of the service instance refers to the real-time health status of the edge cloud service instance, including available, overloaded, and faulty. When there is a fault in an edge cloud service instance, the number of available instances of the service load is reduced by 1.

[0029] S3: Elastic scaling deployment of service instances. Each edge cloud service deploys and generates edge cloud service instances with the lower limit number of service load instances to be started on each edge service node within its service deployment scope, and requests data synchronization of the service floor within the edge cloud according to its service floor data and service deployment scope configuration, and newly adds or relays corresponding edge cloud service instances in real time according to the real-time service load number and the health status of the service instance.

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

[0031] As Figure 3 shown, the detailed steps of elastic scaling deployment of service instances are as follows: S31: Install and deploy the edge cloud service. Each edge cloud service installs and deploys the edge cloud service on each edge service node within its service deployment scope in turn, using the edge cloud service software segment package.

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

[0033] S33: Real-time synchronization of service floor data. Each edge cloud service requests real-time monitoring of service floor data changes for data synchronization 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 there is a change.

[0034] S34: Real-time relay to start service instances. Each edge cloud-native service monitors its service real-time load count 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 corresponding edge cloud-native service instance is newly created or relayed to be started: , wherein, represents the number of available service load instances; represents the peak service instance load count; represents the service real-time load count.

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

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

[0037] As Figure 4 shown, the detailed steps for real-time update and synchronization of service status are as follows: 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 number of available service load instances as 0.

[0038] S42: Register and update service instance information. When each edge cloud-native service generates and starts each edge cloud-native service instance, it registers and updates the corresponding edge cloud-native service instance to the edge cloud-native service status management table of the local edge service node, records its service instance ID, service instance subordination system level, service instance subordination node address, and the service instance health status as available, and at the same time, the number of available service load instances is incremented by 1.

[0039] S43: Register and update service instance overload. When the health status of any edge cloud-native service instance changes to overload, each edge cloud-native service registers and updates 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 its service instance health status as overload.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] The edge nodes include edge service nodes and edge terminal nodes; 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; The edge cloud service provider refers to an edge cloud service instance that provides services for application software on the corresponding edge node.

[0045] like Figure 5 As shown in the figure, the detailed steps for matching application service instances are as follows: S51: Match the application to enjoy the service instance. All edge service nodes within the edge cloud receive in real time the edge cloud-native service enjoyment requests of the application software on the edge nodes, and use the edge cloud-native service instance matching formula to match, from the edge cloud-native service status management table, the edge cloud-native service providers for the application software, and based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet-sending response timeout retransmission mechanism thereon, send the edge cloud-native service enjoyment request response to the corresponding edge node. The edge cloud-native service enjoyment request response includes the service enjoyment request response reply application ID, its edge cloud-native service provider's service instance ID, and the service instance affiliated node address information.

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

[0047] S53: Receive the response to reply to the service access request. The edge cloud-native service provider receives in real time the edge cloud-native service access request from the edge node, and according to the edge cloud-native service access request, based on the UDP connectionless transport protocol applicable to the edge high-mobility environment and the packet-sending response timeout retransmission mechanism thereon, send the service access request response to the corresponding edge node. The edge cloud-native 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.

[0048] S54: Return the service access request response result. The edge node receives in real time the edge cloud-native service access request response from the edge cloud-native service provider, and according to the edge cloud-native service access request response, return 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.

[0049] The edge cloud-native service instance matching formula is as follows: , where, 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 means available, 2 means overload, 3 means fault; Indicates The system level to which each edge cloud service instance belongs; Indicates the system level to which the application software belongs; Indicates the service ownership type of the edge cloud service initiated by the application software on the edge node. =1 means the same rights for the whole network, 2 means different rights for the whole network, 3 means the same rights for each domain, 4 means different rights for each domain, 5 means the same rights for the same position; It indicates 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 = 1, 3, 5, the matched one is the edge cloud service instance whose service instance health status is available and whose service instance system level is closest to the application software system level. When the service ownership type of the requested edge cloud service = 2, 4, the matched one is the edge cloud service instance whose service instance health status is available and whose service instance system level is not less than the application software system level and is closest to the application software system level.

[0050] The edge cloud service organization and sharing system for high-mobility environments described in the present invention includes deploying edge cloud service management software and several edge cloud services on edge service nodes, and deploying edge cloud service agent software on edge nodes.

[0051] The edge cloud service management software is capable of managing the status of all edge cloud services in the edge cloud and matching edge cloud service providers for application software, and is configured as follows: Generate an edge cloud service status management table on all edge service nodes in 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 service status generated by other edge service nodes; Receive and respond to edge cloud service requests from applications on edge nodes in real time for all edge service nodes in the edge cloud, and match edge cloud service providers for applications based on the edge cloud service status management table.

[0052] The edge cloud service can configure service initial parameters, run and maintain service instances, and register and update service status, and is configured as follows: Configure initial parameters such as service backplane data, service deployment scope, service availability scope, service ownership type, service load lower limit instance number, service instance load peak number, etc. Deploy edge cloud generation service instances that generate the lower limit number of startup service loads on each edge service node within its service deployment scope, and configure and submit the synchronization of service floor data within the edge cloud according to its service floor data and service deployment scope, as well as add or relay corresponding edge cloud generation service instances in real time according to the real-time load number of the real-time situation service and the health status of the service instances; Register and update the real-time status of the edge cloud generation service to the edge cloud generation service status management table of the local edge service node in real time, and send and update it to the edge cloud generation service status management table of other edge service nodes according to the authority.

[0053] The edge cloud generation service proxy software can proxy the enjoyment and access requests of the edge cloud generation service of the application software on the edge node, and is configured as: Realtime proxy receives the request for enjoying the edge cloud generation service of the application software on the edge node, and forwards the request for enjoying the edge cloud generation service of the application software to the corresponding edge service node within the edge cloud connected to the edge node; Realtime proxy receives the response to the request for enjoying the edge cloud generation service of the corresponding edge service node, and forwards the request for accessing the edge cloud generation service of the application software to the corresponding edge cloud generation service provider according to the response to the request for enjoying the edge cloud generation service; Realtime proxy receives the response to the request for accessing the edge cloud generation service of the corresponding edge cloud generation service provider, and returns the result of the response to the service access request to the application software according to the response to the request for accessing the edge cloud generation service.

[0054] 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.

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

Claims

1. A method for organizing and enjoying edge cloud services in a high-mobility environment, characterized in that: The steps include: 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; S2: Generate an edge cloud service status management table on all edge service nodes in the edge cloud, register and update the local edge service node in real time, and receive and update the edge cloud service status generated by other edge service nodes; S3: Each edge cloud service deploys and generates edge cloud service instances with the minimum number of instances of the service load on each edge service node within its service deployment scope, and requests the synchronization of service backplane data in the edge cloud according to the service backplane data and service deployment scope configuration, and adds or relays corresponding edge cloud service instances in real time according to the real-time service load and service instance health status; S4: Each edge cloud service registers and updates the edge cloud service status in real time to the edge cloud service status management table of the local edge service node, and updates it to the edge cloud service status management table of other edge service nodes according to the authority delivery; S5: All edge service nodes in the edge cloud receive and respond to edge cloud service usage 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. After obtaining the edge cloud service providers, applications use them to call and access corresponding edge cloud services.

2. The method for organizing and enjoying edge cloud services in a high-mobility environment according to claim 1, characterized in that: The initial parameters in step S1 include service backplane data, service deployment range, service availability range, service ownership type, service load lower limit instance number, and service instance load peak number.

3. The method for organizing and enjoying edge cloud services for high mobility environments according to claim 1, characterized in that: The step S1 comprises: S11: Each edge cloud service configures its service backplane data, that is, configures all service backplane data units in the service backplane data, and the number of service backplane data units is ≥ 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 availability range, that is, configures all available system levels or all available points within the service availability range, 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 of the following configurations: uniform ownership of the entire network, heterogeneous ownership of the entire network, uniform ownership of different domains, heterogeneous ownership of different domains, and uniform ownership of the same location; S15: Each edge cloud service is configured with its service load lower limit instance number, the service load lower limit instance number ≥ 1, the service load lower limit instance number = 2, that is, the active-active master-standby instance when the edge cloud service is enabled; S16. The initial parameter configuration of each edge cloud service is packaged into a software segment package.

4. The method for organizing and enjoying edge cloud services for high mobility environments according to claim 1, characterized in that: The edge cloud service status management table in step S2 refers to a management table that records the edge cloud service status of all edge cloud services in the edge cloud in real time, including multiple edge cloud service status recording units. The edge cloud service status of each recording unit includes the service ID, service name, number of available service load instances, and service instance ID of the corresponding service load instance, service instance system level, service instance node address, and service instance health status.

5. The method for organizing and enjoying edge cloud services for high mobility environments according to claim 1, characterized in that: The step S3 comprises: S31: Each edge cloud service installs and deploys the edge cloud service on each edge service node within its service deployment range in turn using the edge cloud service software segment package; S32: Each edge cloud service creates an edge cloud service on each edge service node within its service deployment range in turn, and initially generates and starts a corresponding number of edge cloud service instances according to the lower limit instance number configuration of its service load; S33: Each edge cloud service, in turn, on each edge service node within its service deployment scope, in accordance with its service backplane data and service deployment scope configuration, requests the data synchronization within the edge cloud to monitor service backplane data changes in real time, and synchronizes service backplane data increments to all edge service nodes within the service deployment scope in real time when changes occur; 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: ， in, Indicates the number of available instances for the service load; Indicates the peak load of the service instance; Indicates the real-time load of the service.

6. The method for organizing and enjoying edge cloud services in a high-mobility environment according to claim 1, characterized in that: The step S4 comprises: S41: when each edge cloud service is created, the corresponding edge cloud service registration is updated to the edge cloud service status management table of the local edge service node, and its service ID, service name, and the number of available instances of the service load are recorded 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 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 as available, and the number of available instances of the service load is increased by 1; S43: 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; S44: when the health status of any edge cloud service instance changes to fault, 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 fault, and reduces the number of available instances of the service load by 1; S45: 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; S46: Update the edge cloud service status of the local edge service node 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 based on it, and send it to other edge service nodes in the edge cloud according to the authority. Other edge service nodes receive the updated edge cloud service status.

7. The method for organizing and enjoying edge cloud services in a high-mobility environment according to claim 1, characterized in that: 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.

8. The method for organizing and enjoying edge cloud services in a high-mobility environment according to claim 1, characterized in that: 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.

9. The method for organizing and enjoying edge cloud services in a high-mobility environment according to claim 1, characterized in that: The edge cloud service instance matching formula in step S51 is as follows: ， in, Indicates the sequence number of the edge cloud service instance in the edge cloud service status management table; Represents the edge cloud service status management table; Indicates The health status of edge cloud service instances, where =1 means available, 2 means overload, 3 means fault; Indicates The system level to which each edge cloud service instance belongs; Indicates the system level to which the application software belongs; Indicates the service ownership type of the edge cloud service initiated by the application software on the edge node. =1 means the same rights for the whole network, 2 means different rights for the whole network, 3 means the same rights for each domain, 4 means different rights for each domain, 5 means the same rights for the same position; It indicates 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 = 1, 3, 5, the matched one is the edge cloud service instance whose service instance health status is available and whose service instance system level is closest to the application software system level. When the service ownership type of the requested edge cloud service = 2, 4, the matched one is the edge cloud service instance whose service instance health status is available and whose service instance system level is not less than the application software system level and is closest to the application software system level.

10. An edge cloud service organization and sharing system for a high mobility environment, 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 service management software is configured to: generate an edge cloud service status management table on all edge service nodes in the edge cloud, register and update the local edge service node and receive updates of the edge cloud service status generated by other edge service nodes in real time; Receive and respond to edge cloud service requests from applications on edge nodes in real time for all edge service nodes in the edge cloud, and match edge cloud service providers for applications based on the edge cloud service status management table; The edge cloud service is configured to: configure its service backplane data, service deployment scope, service availability scope, service ownership type, service load lower limit instance number, and service instance load peak number initial parameters; deploy and generate edge cloud service instances with the service load lower limit instance number on each edge service node within its service deployment scope, and request the synchronization of service backplane data in the edge cloud according to its service backplane data and service deployment scope configuration, and add or relay corresponding edge cloud service instances in real time according to the real-time service load number and service instance health status; Register and update the edge cloud service status in real time to the edge cloud service status management table of the local edge service node, and update it to the edge cloud service status management table of other edge service nodes according to the authority delivery; The edge cloud service management software is configured as follows: the real-time agent receives the edge cloud service usage request of the application software on the edge node, and forwards the edge cloud service usage request of the application software to the corresponding edge service node in the edge cloud connected to the edge node; the real-time agent receives the edge cloud service usage request response of the corresponding edge service node, and according to the edge cloud service usage request response, the edge cloud service access request of the application software is delivered to the corresponding edge cloud service provider; the real-time agent receives the edge cloud service access request response of the corresponding edge cloud service provider, and returns the service access request response result to the application software according to the edge cloud service access request response.

Images