hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.2.3 Procedures | Figure 6.2.3-1: Procedure of edge computing handling by local SMF
1. Steps 1-11 of the UE-requested PDU Session Establishment procedure is performed as described in clause 4.3.2.2.1 of TS 23.502 [3], with the following change:
- In step 4, the central SMF retrieves indication of L-SMF selection from the Session Managem... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.2.4 Impacts on existing services, entities and interfaces | AMF:
- L-SMF selection indicated by DNN of the PDU Session Establishment Request.
- Providing the PCF address and EASDF address from Central SMF to L-SMF.
- Providing the PSA CN Tunnel Info to L-SMF.
- Providing the UL CL/BP CN Tunnel Info to SMF.
SMF:
- Providing PCF address and EASDF address to AMF.
PCF:
- Providing ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3 Solution #3: Reducing impact of DNS message handling on central SMF for EAS (re)discovery based on offload to L-SMF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.1 Key Issue mapping | This solution is proposed to solve KI#1. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.2 General Description | The existing EASDF based EAS (re-)discovery mechanism requires the SMF to select and determine the suitable EDNS Client Subnet option or Local DNS server, and DNAI information during the DNS message handling procedure. To support this work, the SMF need be aware several information, e.g. the EAS deployment information,... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3.1 EAS Deployment Information and BaselineDNSPattern Management in the EASDF by L-SMF | The EAS deployment information provisioned from AF to 5GC, i.e. UDR, is same as the procedure defined in clause 6.2.3.4.2 of TS 23.548 [5].
The L-SMF subscribes to EAS Deployment Information Change Notification from the NEF using the procedure same as one defined in clause 6.2.3.4.3 of TS 23.548 [5].
The L-SMF manages ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3.2 EAS discovery procedure with EASDF | Figure 6.3.3.2-1: EAS discovery procedure with EASDF
The EAS Discovery with EASDF, i.e. option A/B type discovery, is executed as following:
1. L-SMF has created BaselineDNSPattern at the EASDF using the procedure as defined in clause 6.3.3.1.
2. Except the enhancement of DNS context, DNS context creation Procedure is ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3.3 EAS discovery procedure with Local DNS Server/Resolver | Figure 6.3.3.3-1: EAS Discovery Procedure with Local DNS Server/Resolver
The EAS Discovery Procedure with Local DNS Server/Resolver, i.e. option C/D type discovery, is executed as following:
1. Same as step 1 in clause 6.2.3.2.3 of TS 23.548 [5].
2. The SMF selects L-SMF:
- The SMF may select the L-SMF before the UE se... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3.4 EAS rediscovery at Edge Relocation | This procedure is used by the SMF to trigger the EAS rediscovery procedure when a new connection to EAS need to be established. This rediscovery can be triggered in three cases:
- SMF triggered: SMF determines that L-PSA relocation/removal may be needed, e.g. UE moves out of the service area of one L-SMF. The SMF queri... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.3.4 Mobility Handling | The L-SMF is located after the anchor SMF. Hence the mobility handling does not need the L-SMF reallocation. After UE mobility, SMF evaluation whether the L-SMF need reallocated or removed. If it is need, the EAS rediscovery can be triggered. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.3.4 Impacts on services, entities and interfaces | EASDF
- Receive enhanced BaselineDNSPatterns information from the L-SMF.
- Associate the DNS handling rule with the enhanced BaselineDNSPattern information to generate the concrete DNS detection template.
- Notify the candidate L-SMF to SMF when it notifies the matched DNS message to SMF. This requires the EASDF to be ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4 Solution #4: Enhanced EC Architecture with SMF selecting local SMF storing EC related information | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.1 Key Issue mapping | This solution addresses following aspects of KI#1:
- Whether and which edge computing related information (e.g. UPF and EAS deployment information, DNAIs) can be locally managed to support EAS (re)discovery and UPF (re)selection.
- How to manage the above identified edge computing related information, e.g. locally, cen... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.2 Description | Figure 6.4.2-1: Enhanced architecture with Local SMF
A Local SMF is introduced to manage the Local PSA UPF locally, it stores following EAS discovery related information:
- ECS (EDNS Client Subset) option;
- Local configuration associated with the (DNN, S-NSSAI, Internal Group Identifier) of the PDU Session;
- EAS Depl... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.3.1 Local SMF and Local PSA insertion procedure (new) | Figure 6.4.3.1-1: Local SMF and Local PSA insertion procedure
1. SMF determines to add Local SMF for a UE's PDU Session based on the UE Requested DNN/selected DNN and S-NSSAI, or based on the AF influence information, which can happen during Application Function influence procedure (clauses 4.3.6.2 and 4.3.6.4 of TS 23... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.3.2 Local SMF and Local PSA Removal procedure (new) | Figure 6.4.3.2-1: Local SMF and Local PSA Removal procedure
1. The SMF determines to remove the Local SMF and Local PSA UPF, which can happen during Application Function influence procedure (clause 4.3.6.2 and 4.3.6.4 of TS 23.502 [3]), PDU Session Establishment procedure (clause 4.3.2 of TS 23.502 [3]) or PDU Session ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.3.3 EAS Discovery with EASDF procedure | Figure 6.4.3.3-1: EAS Discovery with EASDF procedure (clause 6.3.2.2.2 of TS 23.548 [5])
In step 8, after receiving the Neasdf_DNSContext_Notify Request message, the SMF needs to forward the received DNS message report from EASDF to Local SMF to retrieve the EAS discovery related information from Local SMF:
- ECS (EDNS... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.3.4 EAS Rediscovery procedure | The EAS rediscovery procedure depicted in clause 6.3.3.4 can be applied to this solution. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.4.4 Impacts on services, entities and interfaces | Local SMF (new entity):
- Stores the EAS discovery related information and provides the EAS discovery related information to SMF when receives the request from SMF.
- Selects the Local PSA UPF for a PDU Session and sends the User Plane tunnel information to SMF.
- Trigger the EAS rediscovery procedure.
Impact to SMF:
-... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5 Solution #5: Enhanced EC architecture with AMF selecting local SMF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.1 Key Issue mapping | Key issue #1. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.2 Description | This solution corresponds to Key Issue #1 and addresses the following aspects:
- How to establish PDU Session that supports local offloading control including (i) how to decide the need of the local offloading control (how to decide to insert local SMF), and (ii) how to authorize the PDU Session to support local offloa... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.3.1 PDU Session Establishment/EAS discovery with local offloading control and local SMF | Figure 6.5.3.1-1: PDU Session Establishment with supporting local offloading control
1. During the Registration procedure, the AMF gets the Local Offloading Control allowed indication from the UDM
2-3. During the PDU Session Establishment procedure, if the AMF receives the Local Offloading Control allowed indication, t... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.3.2 Handling local SMF notification service toward the AF | Figure 6.5.3.2-1: Notification of user plane management event when local SMF is used
The Figure 6.5.3.2-1 shows the procedure for a notification of UP management event for case 2 in clause 6.5.2 when runtime coordination is enabled.
1. A condition for a notification to the AF (e.g. DNAI change is needed) has been met.
... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.5.4 Impacts on services, entities and interfaces | AMF may be configured with the local offloading control service area.
If the service area of the selected SMF includes the current UE location, but the UE location is in the area of the local offloading control service area.
AMF
- checks if the local offloading control is allowed, and if allowed, selects the local SMF.... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6 Solution #6: Local management of EAS Deployment Information with local SMF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.1 Key Issue mapping | Key issue #1. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.2 Description | This solution is for Key Issue #1, which addresses how to locally manage the edge computing related information.
This solution assumes the deployment scenario where SMF is deployed in a central data centre while NEF and a NF (in this solution, the NF refers to local SMF) locally manages edge computing related informati... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.3.1 Provisioning EAS Deployment Information to local SMF without involvement of SMF | Figure 6.6.3.1-1: Provisioning EAS Deployment Information to local SMF without involvement of SMF
Precondition: Local SMF and SMF are set up to decide to support local offloading control.
1-2. Local SMF subscribes EAS Deployment Information Change Notification from the NEF by providing information (e.g. DNN and/or S-NS... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.3.2 Provisioning EAS Deployment Information to local SMF with involvement of SMF | Figure 6.6.3.2-1: Provisioning EAS Deployment Information to local SMF with involvement of SMF
Precondition: Local SMF and SMF are set up to decide to support local offloading control.
1-2. The SMF subscribes EAS Deployment Information Change Notification from the NEF by providing information (e.g. DNN and/or S-NSSAI a... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.6.4 Impacts on services, entities and interfaces | SMF:
- Delegates EASDF and local UPF configuration related to DNS handling to the local SMF.
- Modifies the existing subscription to EDI notification to delegate EDI management to the local SMF.
Local SMF newly introduced:
- Handles EDI locally, and configures EASDF and local UPF based on the locally managed EDI
NEF:
-... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7 Solution #7: EAS deployment information report from L-SMF/L-UPF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.1 Description | This solution is for key issue 1.
This solution is enhancement of Option D in TS 23.548 [5]. The current Option D is quoted below:
- Option D: If the SMF has been configured that DNS Queries for an FQDN (range) query can be locally routed on the UL CL, then the subsequent DNS Queries for the FQDN (range) will be locall... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.2 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.2.1 No L-SMF insertion | Figure 6.7.2.1-1: No L-SMF insertion
0. The N4 Node level Association is established between the SMF and the L-PSA. During this procedure, the L-PSA provides the S-NSSAI, DNN, FQDN(range) that can be served by the L-PSA, Local DNS server address and associated DNAI.
1. The UE establishes a PDN session towards the SMF. ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.2.2 L-SMF insertion after the I-SMF | Figure 6.7.2.2-1: L-SMF insertion after the I-SMF
1. The SMF subscribes the notification of new L-SMF serving the target S-NSSAI and DNN newly registered in the NRF, or L-SMF profile has been updated.
2. The L-SMF is registered in the NRF. The NF profiles includes the S-NSSAI, DNN, FQDN(range) that can be served by the... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.2.3 L-SMF insertion after the SMF | Figure 6.7.2.3-1: L-SMF insertion after the SMF
1. The SMF subscribes the notification of new L-SMF serving the target S-NSSAI and DNN newly registered in the NRF, or L-SMF profile has been updated.
2. The L-SMF is registered in the NRF. The NF profiles includes the S-NSSAI, DNN, FQDN(range) that can be served by the L... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.7.3 Impacts on services, entities and interfaces | L-PSA:
- The L-PSA is enhanced to reports the FQDN range that can be handled by the L-PSA, the associated Local DNS Server address and associated DNAI to L-SMF.
L-SMF(New NF):
- The L-SMF is introduced to control the L-PSA.
- L-SMF registers the FQDN range, the associated Local DNS Server address and associated DNAI in... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.8 Solution #8: Selecting an EAS server leveraging analytics | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.8.1 Key Issue mapping | Editor's note: This clause lists the key issue(s) addressed by this solution.
This solution addresses the objectives of Key Issue #2 and in particular selecting the most suitable local UPF and EAS considering end to end delay. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.8.2 Description | Editor's note: This clause will describe the solution principles and architecture assumptions for corresponding key issue(s). Clause(s) may be added to capture details.
Currently, TS 23.548 [5] specifies how a UE DNS request can be routed via EASDF. The procedure to route UEs DNS request is as follows (as described in ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.8.3 Procedures | Editor's note: This clause describes high-level procedures and information flows for the solution.
The procedure is described below:
Figure 6.8.3-1: Procedure for selecting an EAS server
1. A UE establishes a PDU session as described in TS 23.502 [3].
2. During the PDU session establishment procedure the SMF selects an... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.8.4 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing and/or new 3GPP nodes and functional elements.
SMF requesting existing analytics using the information in DNS request or DNS response as input data.
SMF selects an EAS based on the analytics response (i.e. a list of EAS server address and its associated performanc... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9 Solution #9: local UPF and EAS (re)selection jointly considering N6 delay and EAS load | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.1 Description | Per existing design of TS 23.548 [5], the (re)selection of the EAS and local PSA by 5GC is based on the UE location and EAS Deployment Information, which only considers the topology information of UE, UPF and EAS. Nevertheless, dynamic information especially the N6 delay between the local PSA and EAS, and EAS load, whi... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.3.1 Enhancement on EAS Deployment Information Management | The EAS deployment information provisioned from AF to 5GC as defined in clause 6.2.3.4 of TS 23.548 [5] is used for local UPF and EAS (re)selection. It is proposed to enhance this information as following:
Table 6.9.3.1-1: Additional information of EAS Deployment Information
Parameters
Description
…
….
Delay-sensitive ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.3.2 EAS/L-PSA discovery procedure with EASDF | Normally the EAS load can be converted to the processing delay (e.g. https://ieeexplore.ieee.org/abstract/document/9253665). Hence when the EAS reports how much percentage of load EAS reaches, based on the local configuration, the percentage of load can be converted to the how much processing delay the EAS needs.
The p... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.3.3 EAS/L-PSA rediscovery at Edge Relocation | It is assumed that the SMF, which re-discovers the EAS/L-PSA, can be other NF per the discussion of KI#1.
Figure 6.9.3.3-1: EAS/L-PSA rediscovery procedure at Edge relocation
This procedure is used to trigger the EAS (or L-PSA) rediscovery procedure when a new connection between EAS and L-PSA need to be established. Th... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.9.3 Impacts on services, entities and interfaces | AF/NEF:
- Provide enhanced EDI information as described above.
- Provide the EAS load information (e.g. percentage of the load or EAS processing delay) to SMF per event subscription.
- Provide AF influence related information as described above.
SMF:
- Get enhanced EDI information and EAS load information (e.g. percent... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.10 Solution #10: L-PSA and EAS (re)selection based on N6 one-way and two-way delay measurement | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.10.1 Key Issue mapping | This solution is related to the KI#2. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.10.2 Functional Description | This solution is applied in 5GS architecture for non-roaming scenario supporting Edge Computing as Figure 4.2-1 or Figure 4.2-2 of TS 23.548 [5].
In this solution, SMF performs L-PSA UPF and EAS (re)selection based on the measured N6 delay. The measurement of N6 delay is as follows:
- In the case for uplink (UL) N6 del... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.10.3 Procedures | Figure 6.10.3-1: Procedure of L-PSA and EAS reselection based on N6 delay measurement
1. The EAS discovery procedure is performed as described in clause 6.2.3.2.2 or clause 6.2.2.2 of TS 23.548 [5].
2. PCF based on local configuration, sends N6 delay measurement requirement to AF via NEF, including N6 delay measurement... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.10.4 Impacts on existing services, entities and interfaces | SMF:
- Sending N6 delay measurement request to L-PSA to request UL/DL/RT N6 delay measurement.
- Sending request to PCF if determines N6 delay is exceeded N6 delay threshold.
- Performing EAS re-discovery procedure at edge relocation based on N6 delay.
L-PSA:
- Sending N6 delay measurement packet or N6 delay measuremen... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.11 Solution #11: Provision weight factor of DNAIs from AF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.11.1 Description | This solution is for key issue #2.
The following NOTE is quoted from TS 23.548 [5]:
NOTE 12: If multiple candidate DNAIs are available after considering the UE location, network topology and EAS deployment, the SMF selects one DNAI from the multiple ones based on operator's policy. For examples, the SMF can select the ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.11.2 Procedures | Figure 6.11.2-1: EAS Deployment Information management in the AF procedure
1. The AF invokes the Nnef_EASDeployment_Create/Update service operation. This request may contain the following additional information:
- Selection weight factor per DNAI: selection weight for each DNAI when there are more than one DNAIs provid... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.11.3 Impacts on services, entities and interfaces | The EAS Deployment information is enhanced to include the selection weight factor per DNAI, average delay over N6 interface per DNAI.
The SMF is enhanced to use the new information in the EAS Deployment information to select DNAI. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12 Solution #12: NWDAF and SMF-based EAS and local UPF (re)selection | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.1 Key Issue mapping | The following solution corresponds to the key issue key issue #2 on enhancement of EAS and local UPF (re)selection. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.2 Description | The AF may request EAS discovery based on N6 delay and/or EAS load. The SMF determines the N6 delay between each candidate PSA UPF and EAS via indicating PSA UPF to report the N6 delay measurements or receives delay analysis information from NWDAF, or determines the EAS load based on the information received from NWDAF... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.3.1 NWDAF and SMF-based EAS and local UPF (re)selection | Figure 6.12.3.1-1: Procedure for NWDAF and SMF-based EAS and local UPF (re)selection
1. [Optional] The AF request in step 1 of figure 4.3.6.2-1 in TS 23.502 [3] is used to request EAS discovery based on N6 delay and/or EAS load. The AF request may include Indication for N6 delay based EAS discovery, Indication for EAS ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.3.2 N6 delay measurement and reporting | Figure 6.12.3.2-1: procedure for N6 delay measurement and reporting
The steps 1-2 of Figure 6.12.3.1-1 are performed.
1. TSMF sends the N4 message to the PSA UPF with the EAS information (e.g. list of EAS IP addresses), which indicates the PSA UPF to measure the N6 delay between the UPF and each EAS.
2. The UPF receive... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.12.4 Impacts on services, entities and interfaces | SMF:
- Determines the N6 delay or EAS load should be taken into consideration for EAS and local UPF selection based on local policy or PCC rule.
- Determines one or more candidate PSA UPF(s) and EAS(s), and configures PSA UPF to report the N6 delay between each candidate PSA UPF and EAS, and/or retrieves delay informat... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13 Solution #13: EAS Discovery taking account of EAS load in EASDF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13.1 Key Issue mapping | This solution addresses EAS Discovery considering EAS load aspects of KI#2. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13.2 Description | The EAS load information can be known by AF (Application Function), AF can update the EAS load information to EASDF or DNS Server in some interval or range threshold which can be configured in AF. Then during the EAS discovery procedure (in Figure 6.13.2-1), the EASDF can discover and select a suitable EAS by taking ac... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13.3 Procedures | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13.3.1 EAS load subscription and notification procedure | Figure 6.13.3-1: EAS load subscription and notification procedure
1. EASDF subscribes to AF for EAS load change notification per EAS identifier. The operator can configure the EASDF to serve a list of AFs and EASs, the EASDF subscribes to the selected AFs based on the configured list of AFs.
2. AF is configured with no... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.13.4 Impacts on services, entities and interfaces | Impact to EASDF:
- EASDF subscribes to AF for EAS load notification per EAS identifier.
- EASDF stores the EAS load information and selects a suitable EAS for the received EAS Discovery request from UE taking account of EAS load information.
Impact to AF:
- AF collects and stores EAS load information.
- AF notifies EAS... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.14 Solution #14: EAS selection considering DNS historical handling records | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.14.1 Key Issue mapping | Key issue #2. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.14.2 Description. | This solution is for Key Issue #2 to address the issue on how to consider EAS load for enhanced EAS selection.
This solution proposes to consider DNS historical handling records by enhancing EASDF. As EAS load information itself is dynamic and resides in the management system of EAS, it would be hard and burdensome for... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.14.3 Procedures | This solution addresses a scenario where the EASDF receives multiple EAS IP addresses from the DNS system.
Figure 6.14.3-1: EAS selection considering DNS historical handling records
1. The EASDF performs the DNS resolution as described in TS 23.548 [5]. The EASDF creates the DNS historical handling records by storing t... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.14.4 Impacts on services, entities and interfaces | EASDF:
- creates and provides DNS historical handling records to the SMF.
SMF:
- performs EAS selection considering DNS historical handling records received from the EASDF. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.15 Solution #15: The local EASDF assist for the EAS and local UPF (re)selection based on the AF provided N6 delay and EAS load information | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.15.1 Description | The 5GC not considering the network metrics(e.g. N6 delay) and the compute metrics(e.g. EAS load) has the possibility to provide suboptimal EAS address to the UE and result in redundant EAS rediscovery or Edge relocation.
The N6 delay for each DNAI which is not constant and the EAS load status information subject for f... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.15.2 Procedures | Figure 6.15.2.1: EAS re-discovery based on the N6 delay and the EAS load information
1. The AF registers its available data (i.e. N6 delay and the EAS load information) to the NEF via OAM and the NEF updates its NF Profile to the NRF to register that it supports exposure of AF available data (i.e. N6 delay and EAS load... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.15.3 Impacts on Existing Nodes and Functionality | AF:
- Registers its available data at the NEF including the N6 delay and the EAS load information.
- Sends notification to the EASDF via NEF for the event with the N6 delay and the EAS load information.
SMF:
- Instructs the local EASDF to subscribe and manage the N6 delay and the EAS load information to be taken into a... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.16 Solution #16: Local UPF and EAS (re)selection considering access network delay and N6 delay information by 5GC or AF | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.16.1 Key Issue mapping | This solution addresses Key Issue #2: Enhancement of EAS and local UPF (re)selection and proposes enhancements on Local UPF/DNAI and EAS (re)selection considering access network delay and N6 delay information. |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.16.2 Description | In Rel-18, QoS Monitoring for packet delay can be used to determine the access delay in 5GS. QoS Monitoring for packet delay can be applied based on AF request or PCF policy control or both (see clause 5.33.3 of TS 23.501 [2]). The measurement of the UL/DL packet delay between NG-RAN and PSA UPF can be performed on dif... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.16.3 Procedures | In case 1 (5GC performs N6 delay measurements), AF-provided assistance information that includes N6 measurement configuration information related to EAS(es) on the data network (measurement endpoint(s), protocol, keys, etc.) can be provided via EAS Deployment Information service or AF Traffic Influence service.
In case... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.16.4 Impacts on services, entities and interfaces | Application Function (AF):
- (for the case where 5GC performs measurements) provides requirements for reporting results for QoS monitoring over N6 delay.
- (for the case where 5GC performs measurements) provides assistance information related to data network endpoints for N6 delay measurement.
- (for the case where AF ... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.17 Solution #17: EC Traffic Routing between local part of DN and central part of DN with IP replacement in EAS | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.17.1 Key Issue mapping | This solution addresses following aspects of KI#3:
- How to determine and route the application traffic between the EAS in the local part of DN and the Application Server in the central part of DN for both UL and DL in case there is no direct connectivity between the local DN and central part of DN.
- How is the 5GC aw... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.17.2 Description | Per current 5G system design, the UL CL (Uplink Classifier) User Plane Function (UPF) decides whether to route uplink traffic to local PDU Session Anchor (PSA) UPF based on the Destination IP address and/or Port number of the uplink traffic from the Next Generation Radio Access Network (NG-RAN) node based on the routin... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.17.3 Procedures | During the currently defined AF influence or UL CL addition procedure, the enhanced traffic routing rule may have been configured in UL CL by SMF. Below figure shows an example procedure of AF triggered routing rule configuration or update procedure.
Figure 6.17.3-1: Example procedure for supporting traffic routing bet... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.17.4 Impacts on services, entities and interfaces | Impact to UL CL UPF:
- The UL CL becomes Uplink/Downlink Classifier (UL/DL CL) because it needs to inspect both uplink and downlink traffic, as well as traffic injected by the local EAS. The SMF configures the UL/DL CL UPF with packet filters not only for uplink traffic arriving from the UE side, but also for traffic a... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.18 Solution 18: Supporting traffic routing between local DN and central DN within a PDU Session | |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.18.1 Description | This solution resolves KI#3 about traffic routing between L-DN and central DN based on the scenario that the application traffic is required to be processed at different locations. The following aspects are included:
1) UL/DL traffic handling
For the UL traffic, after receiving traffic from the UE, the traffic is route... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.18.2 Procedures | Figure 6.18.2-1: Procedure for supporting traffic routing between local DN and central DN
0. UE establish a PDU Session as described in clause 4.3.2.2.1 of TS 23.502 [3]. For the UP path of the PDU Session, two scenarios are described as following:
- The PDU Session accesses the local part of DN, e.g. for Distributed A... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.18.3 Impacts on services, entities and interfaces | SMF:
- For Distributed Anchor model, the SMF may insert a central UPF and UL CL/BP for the PDU Session.
- Generate traffic routing rule as described above.
UPF:
- Detect traffic between local DN and central DN and route the traffic to L-PSA or PSA.
- Perform IP replacement of the source IP address for UL traffic and ta... |
6753a40002e493e011686d9e8fc7ebf6 | 23.700-49 | 6.19 Solution #19: Traffic Routing between local DN and central DN over session breakout model |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.