Edge Application Server Registration for Joint EAS Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions lack the ability for vertical applications, such as Factories of the Future (FF) specific applications, to effectively utilize edge application services in edge computing environments, leading to potential miscommunication and functionality issues between application enabler clients and specific servers.
Innovation Solution
A method and system for providing additional information about the relationship between Edge Application Servers (EAS) during registration, allowing User Equipment (UE) to select appropriate servers with a consolidated view, ensuring coordinated communication between application enabler clients and specific servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is transmitted from remote devices to centralized data centers over wide area networks, then data collection capability is improved, but network congestion and latency increase
Solution Approach 1:
The patent segments the centralized data center function into distributed edge computing nodes deployed at network perimeters and local data centers. This segmentation allows data processing to occur closer to source devices, reducing the distance data must travel and thereby decreasing network latency while maintaining data collection capabilities.
Solution Approach 2:
The patent introduces a spatial dimension to data processing by distributing compute resources across multiple geographic locations (edge nodes, local data centers, central data centers) rather than relying on a single centralized location. This dimensional change enables parallel processing pathways and reduces dependency on long-distance network transmission.
2Power
If more compute resources are concentrated in centralized data centers, then processing power is improved, but network bandwidth consumption increases
Solution Approach 1:
The patent segments centralized processing power into distributed edge computing nodes and local data centers. Each segment handles local processing requirements, reducing the volume of data that must traverse wide area networks. This maintains total processing power while significantly reducing network bandwidth consumption.
Solution Approach 2:
The patent introduces edge computing nodes as intermediary processing layers between remote devices and centralized data centers. These intermediaries perform initial data processing, filtering, and aggregation locally, reducing the burden on both network bandwidth and centralized processing resources.
3Productivity
If data is pre-processed at edge locations before transmission to data centers, then network efficiency is improved, but system complexity increases
Solution Approach 1:
The patent implements universal edge computing node designs that can be deployed across multiple locations with standardized hardware and software platforms. This multi-functionality allows the same architecture to serve different purposes (data preprocessing, local analytics, caching) without increasing system complexity, while still improving network efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The embodiments herein relate to vertical application in edge computing. In an embodiment, there proposes a method (900) performed by a first network function (421) implementing Edge Enabler Server (EES) in an Edge Data Network (EDN) (402). The method may comprise at least a step of: receiving, from a second network function (422, 423) implementing Edge Application Server (EAS) in the EDN (402), aregistration request message comprising information indicating a first list of associated EAS information. With embodiments herein, based on the associated EAS information, the UE (401) may perform a joint EAS discovery and selection for vertical application in an edge deployment, thus both application enabler client (414) in the UE (401) and application specific server (424) may communicate with the same application enabler server (423).