5 Functional Description for Supporting Edge Computing

23.5483GPP5G System Enhancements for Edge ComputingRelease 17Stage 2TS

5.1 EASDF

5.1.1 Functional Description

The Edge Application Server Discovery Function (EASDF) includes one or more of the following functionalities:

– Registering to NRF for EASDF discovery and selection.

– Handling the DNS messages according to the instruction from the SMF, including:

– Receiving DNS message handling rules and/or BaselineDNSPattern from the SMF.

– Exchanging DNS messages from the UE.

– Forwarding DNS messages to C-DNS or L-DNS for DNS Query.

– Adding EDNS Client Subnet (ECS) option into DNS Query for an FQDN.

– Reporting to the SMF the information related to the received DNS messages.

– Buffering/Discarding DNS messages from the UE or DNS Server.

– Terminates the DNS security, if used.

The EASDF has direct user plane connectivity (i.e. without any NAT) with the PSA UPF over N6 for the transmission of DNS signalling exchanged with the UE. The deployment of a NAT between EASDF and PSA UPF is not supported.

Multiple EASDF instances may be deployed within a PLMN.

The interactions between 5GC NF(s) and the EASDF take place within a PLMN.

5.1.2 EASDF Discovery and Selection

The EASDF discovery and selection is defined in clause 6.3 in TS 23.501 [2].

5.2 Edge DNS Client (EDC) Functionality

5.2.1 Functional Description

The Edge DNS Client (EDC) functionality is a 3GPP functionality in the UE that ensures that DNS requests from applications are sent to the DNS Server’s (e.g. EASDF/DNS resolver) IP address received from the SMF in the ePCO. The EDC functionality in the UE is a UE capability that ensures the usage of the EAS discovery and re-discovery functionalities defined in clause 6.2.

NOTE 1: A UE without EDC functionality can use the EAS (re-)discovery functionalities provided by EASDF, but the usage of the EASDF cannot be ensured since it may use a different DNS server from the DNS server provided by the operator.

Figure 5.2-1 depicts the Edge DNS Client (EDC) functionality in the UE.

Figure 5.2-1: EDC functionality in the UE

NOTE 2: Whether EDC functionality is provided to the consumer directly or via/by the UE’s operating system is implementation specific. The APIs between EDC consumer and EDC functionality are out of scope of 3GPP.

A UE that hosts the EDC functionality indicates its capability in the PCO during the PDU Session Establishment and the PDU Session Modification procedures. The EDC functionality includes the following functionalities:

– Configures the DNS server address with the DNS Server’s (e.g., EASDF/DNS resolver) address received from the SMF in the ePCO.

– DNS Client:

– Provides the capability to the consumer in the UE to resolve FQDN using DNS Queries towards the DNS Server (e.g., EASDF/DNS resolver) indicated by the SMF.

– Sends DNS Queries towards the DNS Server indicated by the SMF via the related PDU session.

– Forwards EAS IP addresses and other relevant information included in the DNS responses received from the DNS Server to the consumer in the UE.

– Provision of DNS settings (Optional):

– Provides to the consumer in the UE the IP address of the DNS Server (e.g., EASDF/DNS resolver) received from the SMF. The consumer in the UE can explicitly request the DNS Server’s IP address and/or can subscribe/unsubscribe to receive updates of the DNS Server’s IP address.

When the UE performs an FQDN resolution request for an application, the UE shall use the EDC functionality to perform the DNS resolution in one of the following cases:

– the application mapped onto the PDU Session explicitly requests the use of the EDC functionality and the SMF indicated, at PDU Session Establishment or at PDU Session Modification, that the use of the EDC functionality is allowed for that PDU session; or

– the SMF indicated, at PDU Session Establishment or at PDU Session Modification, that the use of the EDC functionality is required for the PDU Session for the specific DNN. In this case, the UE shall use the EDC functionality for all the applications mapped onto that PDU Session.

NOTE 3: Whether the specific DNN(s) is applied is based on the agreement between the MNO and the application provider.

NOTE 4: User preferences at OS level related to the use of DNS server do not apply when the EDC functionality is used.

NOTE 5: It is subject to local regulatory requirements whether the MNO can force the UE to use EDC functionality.