Edge Application Server Deployment Indicators for Lower-Bandwidth Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for provisioning EAS deployment information in edge computing are problematic due to high bandwidth requirements and implementation complexity.
Innovation Solution
A method is introduced where an indicator is sent to network functions indicating whether an application requires edge application server discovery, allowing decoupling of EAS deployment information from policy control rules, reducing bandwidth and complexity by using new services like Nnef_EASDeployment to create, update, or delete EAS deployment information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If EAS deployment information is provisioned in existing solutions, then edge application service can be discovered and routed, but bandwidth requirements and implementation complexity increase significantly
Solution Approach 1:
The patent segments the EAS deployment information provisioning from the policy control rules by introducing a separate indicator field in the PCC rule. This indicator (present or absent) references to EAS deployment information stored separately in the UDR, decoupling the complex EAS discovery functionality from the basic policy control mechanism. The SMF then separately retrieves EAS deployment information from the UDR only when needed, reducing the complexity of always-provisioning comprehensive EAS data.
Solution Approach 2:
The patent extracts the EAS deployment information from the policy control rule provisioning process. Instead of provisioning full EAS deployment information along with policy rules, the system extracts only the necessary indicator (presence/absence of EAS discovery need) into the PCC rule, while storing the complete EAS deployment information separately in the UDR. This extraction reduces the bandwidth and complexity of rule provisioning while maintaining the ability to perform EAS discovery when required.
2Reliability
If EAS deployment information is provisioned in existing solutions, then edge application service can be discovered and routed, but required bandwidth increases
Solution Approach 1:
The patent extracts only the essential indicator (presence or absence of EAS discovery requirement) from the EAS deployment information and includes it in the PCC rule provisioning. The complete EAS deployment information is extracted from this provisioning process and stored separately in the UDR. This extraction dramatically reduces the quantity of data transmitted during policy control rule provisioning, lowering bandwidth requirements while preserving the capability to retrieve complete EAS information when needed.
Solution Approach 2:
The patent implements preliminary action by pre-storing EAS deployment information in the UDR before it is needed for policy control. The indicator in the PCC rule serves as a preliminary signal that triggers subsequent retrieval of EAS deployment information from the UDR by the SMF. This preliminary storage and signaling approach avoids the need to provision complete EAS deployment information during initial rule setup, reducing initial bandwidth requirements.
Data Source
AI summary
Methods and apparatuses for edge application service are disclosed. According to an embodiment, an application function (AF) sends, to a network exposure function (NEF), a request for performing an operation related to edge application server (EAS) deployment information for an application. The request is for creating, or updating, or deleting EAS deployment information. The AF receives, from the NEF, a response to the request.