Edge Enabler Server Registration with DNAI for Accurate Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current edge application architectures in 3GPP networks face challenges in determining the Data Network Access Identifier (DNAI) for Edge Application Servers (EAS) and Edge Enabler Servers (EES), which hinders efficient registration, discovery, and service provisioning, as the Edge Configuration Server (ECS) lacks necessary endpoint information for EAS and EES.
Innovation Solution
Incorporating DNAIs into registration and service provisioning requests between EES and ECS, allowing the ECS to determine appropriate target EES and EAS, and utilizing EAS endpoint information for User Plane path management, enabling accurate registration, discovery, and service provisioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the ECS lacks DNAI information for EAS and EES registration, then the registration and service provisioning processes cannot determine appropriate target servers, but adding DNAI information increases the complexity of registration requests and responses
Solution Approach 1:
The DNAI information is collected and prepared in advance during the server selection process before the registration request is sent to the ECS. This preliminary preparation ensures that the ECS receives complete information needed for accurate registration without requiring the ECS to perform complex real-time determination, thus improving reliability while managing complexity.
Solution Approach 2:
The patent introduces an intermediary mechanism where the DNAI information is transported through the registration request message as a carrier. This intermediary approach allows the DNAI data to be efficiently transmitted from the client device through the network to the ECS without requiring direct complex interactions between multiple network entities, resolving the contradiction between information completeness and system complexity.
2Productivity
If the ECS does not have EAS endpoint information, then User Plane path management cannot be performed, but obtaining and managing this information increases system complexity
Solution Approach 1:
The patent extracts the EAS endpoint information and DNAI data from the complex service provisioning context and places them into dedicated information elements within the registration and service request messages. This extraction approach allows the ECS to receive and process only the necessary information for User Plane path management without being burdened by unnecessary complexity, thus improving productivity while managing information management complexity.
3Measurement precision
If DNAI information is not included in registration requests, then target EES and EAS cannot be determined accurately, but the current architecture does not define mechanisms for obtaining and transmitting this information
Solution Approach 1:
The client device performs preliminary determination of the appropriate DNAI and EAS endpoint information based on service requirements and network conditions before initiating the registration process. This preliminary action ensures that accurate server identification information is available when needed, improving measurement precision without requiring complex real-time arbitration mechanisms in the network architecture.
Solution Approach 2:
The patent makes the registration request message multi-functional by incorporating it as a carrier for multiple types of information including DNAI, EAS endpoint information, and server identification data. This universal approach allows a single message structure to handle multiple information transmission needs, improving server identification accuracy without significantly increasing architecture complexity.
Data Source
AI summary
The present disclosure provides a method in a network node implementing an Edge Enabler Server, EES. The method includes: transmitting, to an Edge Configuration Server, ECS, a registration request or a registration update request containing one or more Data Network Access Identifiers, DNAIs, associated with an Edge Application Server, EAS, or the EES. The EAS is registered with the EES.